[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

2393.0. "DECBridge 90 SNMP failures" by RDGENG::GREID (Hook.....in....mouth!) Mon Jun 19 1995 13:21

    Can anyone help with the following DECBridge 90 problem.
    
    Here is the configuration :=
    
    	DECHUB 90
    		 8 	DECBridge 90
    		 7 	DECAgent 90
    		 6	DEC Repeater 90c
    		 5	DEC Repeater 90c
    		 4	DEC Repeater 90c
    		 3	DEC Repeater 90c
    		 2	DEC Repeater 90c
    		 1	DEC Repeater 90c
    
    	The Agent 90 is also managing five other DECHub 90 communities.
    
    	All of sudden all the repeaters in the above Hub have disappeared 
    	from the Hub when viewed with Hubwatch V3.1. I can change community
    	using the Agent Table to the other managed communities on this
    	Agent and they are all ok. So I know the DECagent 90 is ok.
    
    	I have tried rebooting the Bridge but this makes no difference as
    	the repeaters don't get rediscovered. I noticed that two of the
        LEDs have gone off on the Bridge and only come back on if I delete
    	the Bridge from slot 8 and readd it, and even then they go off when 
    	I change away to another community and then back again, to see if
    	the repeaters will appear again. I have tried replacing the Bridge
    	but I still get the same problem and after a while I get the old
    	favourite meesage of not being able to SNMP to the Bridge.
    
    	The LEDs that are off are the fourth from the top and the sixth
        from top which are normally GREEN on all the Bridges in other Hubs 
    	that I have (and I have 25 Hub 90s).
    
    	The Bridge is definitely working ok and the same LEDs are ok on
    	the Bridge when you look at it, just not through Hubwatch.
    
    	I have had many problems with a high failure rate of DECBridge 90s
    	, including have to add the odd one via the MAC address of its
        second port in Hubwatch as SNMP couldn't talk to the MAC address
    	on the label.
    
    	Any ideas as to the problem above.
    
    	Giles.
T.RTitleUserPersonal
Name		DateLines
2393.1HUBwatch V3.1 crashes after SNMP fails to BridgeRDGENG::GREIDHook.....in....mouth!Tue Jun 20 1995 10:1412
    Further to the base note it seems that within a minute of readding the
    Bridge I can no longer SNMP to it and on repeated attempts Hubwatch
    crashed with :-
    
      Major opcode of failed request:  61 (X_ClearArea)
      Value in failed request:  0xffff8011
      Serial number of failed request:  128864
      Current serial number in output stream:  128939
    
    Help ????? 
    
    Giles.
2393.2What firmware?ROGER::GAUDETBecause the Earth is 2/3 waterTue Jun 20 1995 15:1611
Giles,

I have to ask the obligatory question: what firmware version of the DECagent and
DECbridge?  FWIW, there is new firmware for both devices in the latest release
of the DEChub Consolidated Firmware kit (see note 2).

BTW, the 4th and 6th LEDs on the bridge are the network activity LEDs, the 4th
for the workgroup side and the 6th for the backbone side.  These should not be
solid green unless you have a lot of traffic passing through the bridge.

...Roger...
2393.3Bridge/Agent firmware + LEDsRDGENG::GREIDHook.....in....mouth!Wed Jun 21 1995 03:4615
    Roger,
    
    	Sorry I should have posted the firmware levels. They are for
    Bridge, DEWGB V2.1 and FPROM V3.1 and for the DECagent 90, V2.1.3.
    
    	I will try putting the new firmware up, however when I flip around
    communities I notice that both the LEDs mentioned are always shown as
    ON via Hubwatch when realistically only the 4th LED on the Bridge is
    actually ON with traffic, that's why I was puzzled when looking at 
    the manual.
    
    	Is it just my hubs or does everyone see the Bridge via Hubwatch
    with all these LEDs on.?
    
    Giles.
2393.4SLINK::HOODMaine State Bird: The black flyWed Jun 21 1995 12:072
HUBwatch cannot get the current "real" state of the activity leds, so it
paints them as on.
2393.5DECagent is hub master ... should see repeatersROGER::GAUDETBecause the Earth is 2/3 waterWed Jun 21 1995 13:4012
Giles,

The repeaters in the hub that the DECagent is in are not managed through the
bridge like in the remote communities.  Since you're running V2.1.3 firmware,
the DECagent is the bus master of that hub and performs the management
functions.  If the repeaters are disappearing it is because the DECagent is
somehow losing contact with them.  The bridge should have nothing to do with it. 
FYI, if you can wait a week or so, a new DECagent image is coming out (V3.0.1)
which fixes a fairly major bug in V3.0.0 (which shipped with the DEChub
Consolidated Firmware kit V4.0) with respect to repeater management.

...Roger...
2393.6RDGENG::GREIDHook.....in....mouth!Thu Jun 22 1995 03:488
    Roger,
    
    	Ok, no problem, I will wait for the new image and try it again after
    upgrading.
    
    	Thanks,
    
    	Giles
2393.7RDGENG::GREIDHook.....in....mouth!Thu Jun 22 1995 03:5111
    Roger,
    
    	Actually the reason I didn't suspect the DECagent was because it
    is managing four other Hubs with DECrepeater 90Cs in and it hasn't lost
    sight of those, just the 90Cs in the HUB the Agent resides in.
    
    	Anyhow I will load the new image and see if they become visible.
    
    	Cheers,
    
    	Giles.
2393.8Can you reset the DECagent?ROGER::GAUDETBecause the Earth is 2/3 waterThu Jun 22 1995 09:3810
Yeah, as I said I'd be suspicious of the DECagent only because the management of
the repeaters in the same hub as the DECagent is different than in the remote
hubs.  And since the problem you are seeing is within the DECagent's hub, it is
possible that for some unknown reason the DECagent has decided to stop talking
to the repeaters.

Would it be possible to reset the DECagent (if you haven't already tried this)
to see if it sees the repeaters again?

...Roger...
2393.9RDGENG::GREIDHook.....in....mouth!Thu Jun 22 1995 09:5912
    Roger, 
    
    	I will do the reset and let you know the results.
    
    	I've noticed with three DECHub 900s we have onsite that after 
    	several days of activity their Agents go unreachable and can't
    	even be Pinged. I'll check the REV levels and upgrade them,
    	but I'm not sure whether this is a common problem with some 
    	that are shipping or not. A power off/on of the Hub seems to
    	be the only fix.
    
    	Giles.
2393.10V3.0.0 on Agent RDGENG::GREIDHook.....in....mouth!Tue Jun 27 1995 11:196
    
    	For the record - upgrading Agent using BOOTP/TFTP to V3.0.0
    	has fixed the problem and the repeaters in the Hub are again
    	visible.
    
    	Giles.