[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

216.0. "flashing bridge on DECagent and no response on HUBwatch" by MEO78A::BARNHOORN (Barney to his friends) Wed Apr 28 1993 04:29


I have a 4 DEcagents and 14 DEChubs. The agents are configured with mutiple 
communities. Eg An agent on one floor looks after all the hubs (with bridges) on
that floor.


The agents are running V1.0 of the software and the bridges are running V3.0

I've connected a terminal to the DECagent and [8] change default community to another
 hub that contains repeaters and bridge module. If I [1] show community and 
display the hub view, the bridge module is flashing.  The manual for the decagent
states the module does not respond to the poller.  What is required to get the 
module to communicate again?


From HUBwatch for Ultrix, I get a message of "Respone time out" on the repeaters.
and "Failed to get bridge management information"

I cannot reset the bridge because its in production.

Any suggestions??

thansk Mark

T.R	Title	User	Personal Name	Date	Lines
216.1	Upgrade DECagent code.	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Wed Apr 28 1993 12:18`	7
	Try upgrading the firmware in the DECagent to V1.1 (X.177) is the latest I think. I have not seen any problems on either the DECagent console or on HUBWATCH for OpenVMS with regards to switching communities yet. That doesn't mean I won't find any, but so far things are not too bad. dave
216.2	Have upgraded to X1.77 and still the same	MEO78A::BARNHOORN	Barney to his friends	`Wed May 12 1993 03:04`	13
	I've installed X1.77 of the Agent software but the same problem of the bridge module flashing (in some hubs) still occurs. Resetting the bridge does not always clear the problem. What version of the bridge code should I be running? I have both DEWGB (AUI/TW) and DEWGF (AUI/FL) Mark.
216.3	Some things to try	QUIVER::GAUDET		`Wed May 12 1993 14:22`	24
	A couple of suggestions: Check the MAC address of the bridge and be sure that it is the same one that the DECagent thinks it is (use [13] Show Module on the agent console and select the bridge's slot). Delete the bridge from the community (at the agent console, you don't have to physically remove the bridge from the hub), then re-add it use [14] Add Module. See if the bridge comes "online" at the agent console after about a minute or so. Use the console [18] Connect command to MOP into the bridge and check to be sure that HUB MANAGEMENT is enabled (use the SHOW BRIDGE command and check that 'Hub mgmt enable' is "1"). Also when you connect to the bridge, if it responds with a pound sign (#), that means a password is set. If the DECagent does not display a password when you do a [13] Show Module of the bridge on the agent console, then the agent is not attempting to use a password to query the bridge. In this case, the agent will think the bridge is unreachable. Bridge V3.1 is recommended for use with the latest DECagent firmware. I'm sure there's a pointer somewhere in this file. ...Roger...
216.4	upgraded to bridge V3.1 firmware and resets work	MEO78A::BARNHOORN	Barney to his friends	`Mon May 24 1993 21:12`	7
	I've upgraded to V3.1 of the bridge firmware and most of the problems have gone away. But occasionally it still occurs, the way I have found to fix the problem is to reset the agent and everything works again. Mark.
216.5	the upgraded the Bridge90FL to V3.1	DESS01::WITTAYAJ		`Wed Jul 21 1993 03:35`	2
	Where is firmware V3.1 of the bridge90FL stay ? Thank you.
216.6	DECbridge 90FL already has V3.1	NAC::FORREST		`Wed Jul 21 1993 19:19`	3
	The DECbridge 90FL shipped from the beginning with V3.1 firmware. There should be no need to upgrade it.