[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

1945.0. "DECswitch 900 quits working as HUB master..." by PFSVAX::MCELWEE (Opponent of Oppression) Sat Jan 28 1995 01:43

    	HUBwatch/ DOS 3.1, DECswitch 900EF slot 8 DEChub 900 set as Hub
    manager, all components at latest f/w rev.
    
    	Problem 1: cannot connect to hub via HUBwatch "No response from
    agent" using in-band IP address asssigned to slot 8. Can connect to 
    IP address of 900EF.
    
    	Problem 2: DEChub900 display shows Slot 8: DECswitch 900 status:
    "unknown" at the time of HUBwatch failure to connect to the agent. As 
    long as Slot 8 status is "up" no problem. "Up" status only occurs only 
    after the DECswitch 900 is power failed and reprogrammed as hub master, 
    but disappears over time.
    
    	Questions: Is the DECswitch defective i.e. "losing it's mind as 
    hub master"? Or should I suspect the hub's mgt. module?  Gotta admit
    I neglected to try pinging the agent's address....
    
    	Configuraton: the DECswitch in question is dual homed to another
    hub containing two FDDI concentrators. The LEDs on the FDDI ports
    always look normal on both, but the HUB manager components cease...
    
    	I will investigate further and report back. My frst choice is to
    swap the DECswitch EF..
    
    Phil
T.RTitleUserPersonal
Name
DateLines
1945.1NETCAD::DOODYMichael DoodyTue Jan 31 1995 17:3215
    
    If the DECswitch is crashing, this will cause problem #1. In order
    to manage the the DEChub via its in-band address, you must have 
    a module providing IP services up and running. Is there another module
    in the hub you can use to test with when the problem occurs?
    
    Check the error log of the switch in slot 8, see if there is something
    "interesting" logged at the time the status becomes "unknown". Also,
    has the switch been "disabled" using hubwatch?
    
    Not sure what you mean by "hub master" as the DEChub 900MS has its own
    integral management - in this case it looks like you are using slot 8
    for IP services (not hub management).
    
    md
1945.2Thanks. Cannot reproduce at this time.PFSVAX::MCELWEEOpponent of OppressionThu Feb 02 1995 01:3114
    	Michael, thanks for your reply. The problem has not recurrred since
    the DECswitch was swapped; the original has not failed after
    installation into another hub.
    
    	Sorry for the confusion of calling it "hub master" vs. IP services.
    We have decided it is a better strategy to assign the DECrepeater 900
    in the hub as the in-band IP services device since the DECswitch 900
    will lose its backplane connections if removed from the DEChub 900
    making management more difficult.
    
    	I will update this note if further problems surface.
    
    Phil