|
Jeannie,
Find Duplicate Addresses queries the agent in the HUBwatch Agents
File to see if any of them are reporting that they have seen the
same MAC address. If they have, then HUBwatch reports the locations
being reported for that address. If you have a station (PC)
connected to a port on a repeater, then the MAC address of that
station will be reported by all ports which have received packets
with that station's MAC as the source address, which is what you
are seeing.
This is not an indication that anything is necessarily wrong. However,
if you see the MAC being reported off of more than one port on the
same repeater (for example), then this could indicate a problem
such as a loop or >1 stations with the same MAC (curious if anyone
has ever run into this?).
It sound by what you have described that things are OK. If you look
at the addresses reported and it looks like a map of repeater ports
that the station is tied to then that's normal and healthy.
Regards,
Bob
|
|
Jeannie,
The addresses are stored in erptrAddrDBPortAddrtable, which has a
limited capacity, so that the repeaters may not be able to store
all the addresses seen. Given this, for an address to show up
as a duplicate it has to presently be in the table of 2 or more
repeaters when they are queried. By the time the 2nd repeater's
agent is queried the address may have been replaced by that of another
station if the table was full. Also, according to the erptr MIB,
addresses which have not been seen for "a reasonable amount of time"
may be flushed. The size of the erptrAddrDBPortAddrtable and the
existance of address flushing are implementation dependent. Perhaps
someone could provide these implementation details.
If the same addresses continually show up, then my guess would be
that they are either the only or the heaviest talkers on the
Ethernet. If they are the heaviest talkers, then I'd expect to
see other addresses show up occasionally.
Hope this helps,
Bob
|