| 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 |
****************************************************************
Cross posted in HUB_MGNT & POLYCENTER NETVIEW conf
****************************************************************
A major DEChub 900 customer and a historical user of DECbridges
(100/150/200/500/600) has asked us about some functionality they
have lost with DEChub 900 switching modules from what they feel
they had with DECbridges and DECelms.
It seems that with DECelms (aka: RBMS at one time) they could
use wild cards for bridge names and cause a command to be
executed on all the bridges defined in the DECelms database.
They used this capability to search for duplicate addresses
on the extended LAN by entering a command (something like)
SHOW KNOWN PORTS ADDRESS MU-MB-LE-MU-MB-LE which would execute
on each bridge. This helped them see/find duplicate addresses.
Thinking about it, this must be DECnet-style MAC addresses
(i.e.; AA-00-04-mu-mb-le) that they are looking for, since it's
impossible to have duplicate MAC physical addresses (right?).
They are un-happy that they cannot find a similar function with
DEChubs, DECswitches and HUBwatch.
Can anyone suggest other ways to look for duplicate MAC addresses
as seen from multiple bridge/switches? I'm aware that HUBwatch
has some kind of 'find address' application but I've never understood
in what devices (repeaters? switches?) it searches and/or I
understand it to be within a single hub.
Is there any hack utility or features within POLYCENTER Netview that
can be used to hop thru a list of bridges looking for the existance
of a MAC address off of any of it's ports? Does the Netview SNMP
browser allow a macro operation like this on a group of agents? We're
certainly willing to write scripts to achieve this if necessary.
... or another way for this network management group to assure no
duplicate DECnet addresses are allowed to be setup in a network?
Dave
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3437.1 | Data General sniffer can be an alternative | BACHUS::KNEUTS | Erwin Kneuts DTN 856-8726 | Thu Apr 11 1996 04:03 | 11 |
I can not answer your basic question, but an alternative would be the "sniffer" from Data General. The sniffer detects duplicates. The mechanism is based on the interval between DECnet hello messages. If 2 or more decnet nodes have the same address, they will all send DECnet hello messages. The probability that they will send these messages in sync, so that the sniffer will see equal intervals between subsequent messages is very low. If the sniffer sees different intervals, it gives a warning that there are duplicate addresses. Erwin Kneuts | |||||