[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

2836.0. "What causes DB900MX port restarts" by KAOFS::S_HYNDMAN (Ride life's curves) Thu Oct 05 1995 14:30

    
    
    	I have one port on a DECbridge 900MX V1.5 which keeps restarting
    2-3 times per day.  Frequently the bridge also records a forward
    transition. However it is not one to one.  The errorlog contains no
    entries.
    
    	What causes the port to restart?
    
    
    Scott
T.RTitleUserPersonal
Name
DateLines
2836.1Absence of traffic will result in a port restartNETCAD::BATTERSBYThu Oct 05 1995 15:2115
    Scott, Which port is it that is "restarting"? Is it one of the
    UTP ports or one of the 2 AUI ports.
    
    A flakey MAU could cause the port to leave the forwarding state 
    & restart as you call it, as well as a flakey cable.
    Basically when a port sees no active traffic on the LAN it is/was
    connected to, it will drop out of the forwarding state and then
    restart the pre-forwarding, learning, and then back to forwarding
    process.
    Other possibilities are that the port that occasionally restarts
    is detecting a loop that comes and goes (a parallel connection that 
    perhaps some user on another bridged LAN may use infrequently during 
    the day), by plugging & un-plugging a cable elswhere.
    
    Bob
2836.2KAOFS::S_HYNDMANRide life's curvesThu Oct 05 1995 16:3416
    
    
    Bob,
    
    	Thanks for the quick reply.  The port in question is port 7 which
    is the bottom AUI port.
    
    	The port counters from Hubwatch are showing the port restarts
    counter and forwarding transitions incrementing.  I don't think I have a 
    bridging loop but a bad mau or cable is a possibility.
    
    	Is it possible to have a hardware problem on this one port on the
    switch?  Would a hardware problem on the switch have to be logged in
    the error log?
    
    Scott
2836.3Some more suggestions to try.....NETCAD::BATTERSBYThu Oct 05 1995 18:5012
    Well there's always the possibility of a flakey solder connection
    at the AUI connector, transformer, etch, LANCE Chip for the receive path
    for port 7. One way to verify this would be to change your LAN 
    connection to the other AUI port (if it's currently unused), then on
    port 7 put an AUI loopback. Then keep tabs on port 7 to see if 
    there are any restarts on port 7. Also now that you are using the
    other AUI port (port 2), if the problem is in fact a flakey MAU,
    the problem should move to port 2. So by doing the above steps
    you should be able to pin down whether the problem is internal to
    port 7 or whether it is related to a bad MAU or cable.
    
    Bob