[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

834.0. "Decbridge90 in Dechub900 with Decagent90" by KERNEL::WARDJO () Thu Mar 17 1994 06:15

    I am trying to use a Decagent 90 to manage 90 modules in a dechub900
    (specifically the decbridge 90). 
    
    With Agent v1.1 I install the agent and then add the bridge. As I don't
    add the bridge in slot 7 or 8 the console prompts me if the hub is a
    900 to which I answer yes.
    
    The bridge is added but flashes on the display, indicating that the
    agent cant poll it (I think). If I connect to the bridge and do a show 
    repeater, the bridge responds with "This bridge is not the Hub
    manager" (The bridge is running V3.1 and Hub management is set to 1).
    
    Can anyone explain why I can't do this? I have factory reset the agent
    & bridge but with the same results.
    
    If I use Hubwatch (for VMS V2.0) I can use this agent to manage the
    bridge.
    
    With agent V2 (T2.0.0) there is no option to add the bridge and it is not
    automatically picked up. I can't even tell the agent it is in a Hub900.
    
    From hubwatch I can't manage the bridge 90 and trying to tell the agent
    it is in a hub900 fails.
    
    Am I missing something here or am I trying to do something that is not
    possible.
    
    The bottom line question is "How do I manage a decbridge 90 located in
    a dechub 900 using the decagent 90?"
    
    Any help or pointers appreciated.
    
    Thanks 
    
    Jon

T.R Title User Personal
Name Date Lines

834.1 some pointers QUIVER::SLAWRENCE Thu Mar 17 1994 11:01 14

T.R	Title	User	Personal Name	Date	Lines
834.1	some pointers	QUIVER::SLAWRENCE		`Thu Mar 17 1994 11:01`	14
	First, your Agent V2 is very old; the SSB release is available now (see recent notes here for pointers). Upgrade that. Have you assigned any IP address to the DEChub900 built-in agent? If so, it will not allow any line card to send or receive management polls, which would cause the bridge to respond as you describe. The HUBwatch installation guide has step-by-step instructions on how to configure this; also check there. If you have a DECserver90L+ in the hub it may have a bug that can also make the DECbridge show the same symptom; it is corrected in ROM version 5.4, which was released recently and I believe you can get one.

    
    First, your Agent V2 is very old; the SSB release is available now (see
    recent notes here for pointers).  Upgrade that.
    
    Have you assigned any IP address to the DEChub900 built-in agent?  If
    so, it will not allow any line card to send or receive management
    polls, which would cause the bridge to respond as you describe.
    
    The HUBwatch installation guide has step-by-step instructions on how to
    configure this; also check there.
    
    If you have a DECserver90L+ in the hub it may have a bug that can also
    make the DECbridge show the same symptom; it is corrected in ROM
    version 5.4, which was released recently and I believe you can get one.