[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

3855.0. "unwanted thinwire connection" by HLFS00::ESSER_W (Wim Esser) Tue Sep 10 1996 11:20

I have a customer with following problem.

He created a new LAN in the DEChub 900 (the 6e).
Than he select a port of his DECrepeater 900TP (port 17)
to the so far unused group 2. Than he connects this group
2 to the new created LAN.
Although the new LAN is only connected to port 17 of the 
DECrepeater 900TP there was a lot of traffic on that port.
After analyzing this it looks as if this data is coming
from the Thinwire segment of that HUB. (We see bridge 
multicasts with source address of the DECswitch 900EE
port 2 which is in the same DEChub connected to the Thinwire).
This also happened after we disconnected the thinwire connection
of the DECrepeater 900TP (this connection was not in use
because group 1 of this repeater was not used).

DEChub 900         V4.2.0
DECswitch 900EE    V1.1.1
DECrepeater 900TP  V2.1.1

Did anyone have seen this behaviour before ?
    
    
    Wim Esser
    MSC Gouda
    Netherland
T.RTitleUserPersonal
Name		DateLines