| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
On my customer site I'm experiencing a couple of problems on Hub-
watch apllications , that maybe someone can easily solve or give
me some hints to.
Configuration:
Dechub900 FW 4.1.0 Decswitches and other modules at latest
FW version .
Hubwatch for Windows 3.1 vers. 4.1.1. running on a Venturis 486/66
with "only" 8 MB of memory.
The hubs has in slot 8 a DECbridge 900MX (FDDI) that works as the
management module for the MAM (but thay don't yet have an IP addr
for theyself. Only MAM's has it. We actually have 8 hubs on the
ring.
THE PROBLEMS :
1. 'Find IP' address doesn't work. I got a message that sounds like
"cannot resolve IP address..." right 5 seconds after having
issued the request.
The IP address that I search for test, is the one that belongs
to a Station connected to a DecRepeater900TM on one of the hubs,
and that is surely talking. This test has been done with different
machines/addresses on different repeaters on different hubs, with
the same results.
Same problem with the Ethernet MAC address (08-00....) search.
The only find working is the DECnet one ( AA-00-04...) but unfor-
tunately, I cannot use it on HP's, Sun's and most of the PC's !
2. 'Find duplicates' comes out with tenths of 'false' duplicate addr.
I've read Notes about this problem, but even if the explanation
were quite clear, none says how this feature can be useful to
determine 'REAL' duplicates.
Anyone's help will be a lot appreciated !
Sergio
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3291.1 | Hope this helps | LEMAN::PAIVA | Hawkeye - Network Support @GEO | Sat Feb 17 1996 03:36 | 18 |
The find IP addresses will never work. See help in HUBwatch V4.1.2
(don't know if this is also in V4.1.1 but probably).
You say that it doesn't work for Ethernet MAC addresses but it works
for "DECnet" MAC addresses. This is not possible. Do not forget that a
host with a 08-00-2B-... adapter (or any other) will have its MAC address
modified into AA-00-04-00-xy-zw where zwxy is the hexa conversion of
1024*area + nodenumber.
Regarding the duplicates, what do you mean by "false duplicates",
routers. This is good news! Where you expecting many duplicates?
Cheers,
Pedro
| |||||
| 3291.2 | Find IP will never work ??!?!? | MLNCSC::CAREMISE | and then they were ...four ! | Wed Feb 21 1996 05:59 | 36 |
> The find IP addresses will never work. See help in HUBwatch V4.1.2
> (don't know if this is also in V4.1.1 but probably).
I wonder wath is the meaning of an application that will never
work !! Remove it should be more elegant, at least to avoid
expectation from the customers.
- The question about the MAC address is related to NON DECnet CPU's.
An HP or SUN station will never be ping-able in any manner, if
IP and MAC find address doesn't work ( and as MAC I mean the only
address that a Non-DEC Station could issue : 08-00-09-6D-49-00 for
example of an HP. )
> Regarding the duplicates, what do you mean by "false duplicates",
> routers. This is good news! Where you expecting many duplicates?
As reported somewhere else in the conference, a false duplicate
means that the result of a find duplicate on the net, will output
a situation like :
STATION AGENT MODULE
------------------- ----- ------
AA-00-04-00-01-2A AGENT#1 SLOT 7 PORT D4
AA-00-04-00-01-2A AGENT#4 SLOT 3 PORT A5
AA-00-04-00-01-2A AGENT#6 SLOT 2 PORT B1
where in truth, the station is only attached on one of the 3 ,
and the other 2 are FALSE ( becuase there are no station connected
on that repeater and on that specific port )
How can I troubleshoot duplicate addresses on the net, with such a
tricky situation from HubWatch : that's my question.
Thanks.
Sergio.
| |||||