[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

633.0. "workgroup/backbone port down" by ODIXIE::RICHARDSON (Are we there yet??) Tue Jan 18 1994 11:58

    I've sure been putting my share of entries in here lately - but here
    goes another....
    
    I have a bridge90 that keeps giving "workgroup port down", "backbone
    port down" errors using Hubwatch for Windows software.  
    
    The Agent is V1.1, the Bridge is V3.1 firmware.  From the agent's point
    of view (console) the bridge has the correct MAC address and I can
    connect to it with no problem.  The bridge is working correctly and has
    been powered cycled since the agent was added (the entire hub was
    cycled with the agent and bridge in the hub).  They are in slot 7 and
    8.
    
    I did initialize the database and do an auto discovery and it finds the
    bridge along with all the other repeater 90T's in the hub.  Everything
    looks fine until the first time the bridge gets "polled" and I get the
    red light with the two errors mentioned above.  The thinwire port
    onethe bridge is connected to a DELNI which in turn is connected to the
    backbone and all the PC's on the repeaters in the hub can talk to the
    servers on the backbone so I really don't think that both the backbone
    and workgroup ports are down.
    
    So...I'm all out of ideas.  The HUBwatch version is 1.1.
    
    Any Suggestions?
    
    Cindy
T.RTitleUserPersonal
Name		DateLines
633.1Couple of Things to TryLEVERS::DRAGONTue Jan 18 1994 12:1617
    
    Cindy,
    
    	A couple of things which you might try.
    
    1) Using the DECagent 90 V1.1 console see what the DECagent 90 says about
       the DECbridge's port status
    
    2) Perform a MOP connect to the DECbridge (from the DECagent 90) in 
       question and use its console command to see what the DECbridge says 
       about its port 1 and 2 status (SHOW PORT 1 and SHOW PORT 2). Also see 
       if you get any loopback diagnostic failure messages (pg 4-21 DECbridge 
       90 Owner's Manual) which may indicate configuration/cabling problems. 
       Also, do the DECbridge's LEDs indicate any problems?
    
    Hope this helps,
    Bob
633.2Common Problem?ALBANY::BARTLEYThu Jan 20 1994 12:4229
    I too have seen the same scenario as Cindy. I upgraded the DECagent 90
    to V1.1 and the DECbridge 90 to V3.1 and am running HUBwatch V1.1 on 
    a DECstation 333 (a little slow for HUBwatch).
    
    I connected to the bridge through the DECagent and showed both ports. 
    Disabled state:0 and Broken state:0 on both ports.
    
    Port 1: 08-00-2b-31-cb-64
    Port 2: 08-00-2b-71-cb-64
    
    I went back to the DECagent and did a Show Module. The agent showed the 
    bridge as having an address of 08-00-2b-32-67-87. Where it got this
    address I don't know. I changed the address in the agent and went back 
    to HUBwatch and got the same results. 
    
    Alarms were:
    
    Agent - (min) Threshold:SNMPOutGenErrs
    Bridge- (maj) Bridge Backbone Port is Down
    Bridge- (maj) Bridge Workgroup Port is Down
    Module2-(min) Threshold:DS90lDot3StMultiColl
    Module2-(min) Threshold:DS90lIllglMutlicast
    
    All LEDs Green (no errors).
    
    What are we doing wrong??
    
    Dave
633.3Methinks the agent is confusedQUIVER::GAUDETThu Jan 20 1994 17:099
    That's very strange.  Can you remove and re-add the bridge, either at
    the agent's console or through HUBwatch?  I have no idea where the
    agent would be coming up with an obscure address for the bridge.
    
    Failing that, perhaps a bit more detail about your configuration would
    help us figure out what's going on.
    
    Roger Gaudet
    DECagent 90 devo
633.4It's our DEMO HubALBANY::BARTLEYThu Jan 20 1994 19:4218
    
    
    
    DEChub 90
    
    Slot 1 - Empty
    Slot 2 - DECserver 90L+
    Slot 3 - Empty
    Slot 4 - Empty
    Slot 5 - DECrepeater 90T
    Slot 6 - DECrepeater 90C
    Slot 7 - DECagent 90 Firmware V3.1 (pulled off Network)
    Slot 8 - DECbridge 90 Firmware V1.1 (pulled off Network)
    
    HUBwatch V1.1
    
    Hub backplane terminated. This is a demo hub here in our office. Any
    more specific info you might need is easily gotten.
633.5ALBANY::BARTLEYThu Jan 20 1994 19:454
    Someone here in the Office suggested to SET BRIDGE HUB_MANAGE DISABLE.
    I tried this, and no change.
    
    Dave