[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

164.0. "Problems with HUBwatch and DB90" by MAIL::CLAYTON (Merlin Clayton DTN 445-7217) Thu Feb 18 1993 11:45

I'm having problems managing my demo hub configuration with T1.1.8.  The
problems encountered are as follows:

1.  When showing the DECbridge 90 attributes I always get the "Response
    Time Out" window immediately.  The only information that is ever shown
    is the Identification and Status information.  Everything else is 
    blank or zero.

    When I manually configured the bridge, I did not put a password in 
    since the user guide said it was optional.

2. I have manually configured the hub as follows:

	Slot 8	DECbridge 90
	Slot 7  DECagent 90
	Slot 6  DECrepeater 90C
	Slot 5  DECrepeater 90T
	Slot 4  DECserver 90L
	Slot 1  DECserver 90TL

    After doing this manual configuration, I select the Refresh Polling 
    option from the pull down menu, and the modules in Slots 1, 5, & 6
    disappear.  The other ones are still there.

3.  Autodiscovery does not work.  According to Sec 3.1.2 of the Use guide
    "After you configure the DECbridge 90 module, the autodiscovery feature 
     will automatically configure the repeater modules."

    This may be related to problem 1 above.

Any suggestions as to how to rectify these problems will be appreciated.

Thanks.

Merlin
T.RTitleUserPersonal
Name		DateLines
164.1Try this.SLINK::HOODJust add waterThu Feb 18 1993 16:5917
As far as autodiscovery, you might want to check that hub_management is enabled
in the bridge itself.  If you can't get there thru hubwatch, then connect
to the bridge thru the DECagent90's console, and do a SHOW BRIDGE.  If
Hub Management is not enabled, do a SET BRIDGE HUB_MANAGE ENABLE command,
and that will get the autodiscovery going (for the repeaters only!)

DECserver90L's, DECserver90L+'s, and 1MEG DECserver90TL's do not autoconfigure
and must all be manually added.

If your 90TL is disappearing on Refresh Polling, it hasn't be correctly
added to the slot table.  This can *only* be done thru HUBwatch...
	* Use the Configure pull-down and get to the Add menu.
	* Using the Add menu, add the 90TL to the hub.  You must make sure
	  the Enable Status Polling button is in the OUT (off) position, or
	  it will be thrown out by the Agent at the next slot polling cycle.

Tom
164.2Still Not WorkingMAIL::CLAYTONMerlin Clayton DTN 445-7217Fri Feb 19 1993 09:4737
RE: -1...

>> As far as autodiscovery, you might want to check that hub_management is enabled
>> in the bridge itself.  If you can't get there thru hubwatch, then connect
>> to the bridge thru the DECagent90's console, and do a SHOW BRIDGE.  If
>> Hub Management is not enabled, do a SET BRIDGE HUB_MANAGE ENABLE command,
>> and that will get the autodiscovery going (for the repeaters only!)


I did the above and made sure that the bridges hub management flag was 
enabled - still does not work.

However, I brought HUBwatch wup from a terminal window this time and have
more information on the errors that are occuring.

After the hub configuration is displayed, I doubleclick on the bridge (slot 8)
and I get the following error message in the terminal window:

	ERROR:  failed to get IF interface

however, the detailed bridge management window comes up with no values in
any field.  At that point, I click on the <REFRESH> button and get the 
following error:

	ERROR: snmp: failed build of GET reguest (nobjs2)
	       unrecognized hub management state

then I get the basic status information and ID information as discussed in
.0.

I hope this sheds some light on the situation, and gives you more to work
with.

Thanks.

Merlin
164.3Working with New FirmwareMAIL::CLAYTONMerlin Clayton DTN 445-7217Fri Feb 19 1993 16:469
The problem was the firmware version of the bridge I had in the demo center
hub.  I put a new version of firmware - actually a new bridge - in the hub,
(V3.0) and it now works.

Thanks for the help Tom.

Merlin