[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

215.0. "Some T1.1.18 polling and autodiscovery question" by ZUR01::SCHNEIDERR () Wed Apr 28 1993 04:26

Hello,

We run HUBwatch T1.1.18 and agent X 1.75. I tried and found the following:

1. When I unplug a DS90 xx, and have the poller running. On the terminal screen
I can see the message 
(W) DS90: SNMP timeout in fp poll group.
(W) status poll: can't reach slot 1
But on the graphical screen the module don't disapeare. For my opinions it
should. Why doesn.t it?

2. When I change a DR90x into an other slot, then the poller doesn't see that and
the graphical screen doesn/t change anything. Why?

3. When I restart the HUBwatch the two unpluged modules appeares as unknown
modules. The new DR90 appeares in the new slot. Thats fine but why doesn't work
it realtime?

4. From time to time I can't reach the DB90 in my hub. then I can see a timeout-
message and no information is returned from the bridge. But on the HUBwatch
screen the bridge is still visible. In this status I can't do anything on 
the bridge. I have to restart HUBwatch. Sometimes after the restart, the
connection to the bridge is here again, sometimes not.


It is impossible to use HUBwatch with such conditions.

Regards  Roland
T.RTitleUserPersonal
Name		DateLines
215.1"impossible to use"?SLINK::HOODJust add waterWed Apr 28 1993 11:5230
(1) Hardware limitation with old terminal servers:
    Unfortunately, the DS90L and the DS90L+ do not autoconfigure, so the
    DECagent90 has no way of knowing whether or not they exist unless the
    user explicitly tells the agent they've been added or removed.  HUBwatch
    uses the agent's slot table for the HUBwatch display.
    The newer terminal servers (90TL w/4meg and new firmware, 90M, and the
    90L+2) all do autoconfig, so if you unplug one of those, it will 
    disappear and if it's plugged-in, it will automatically appear.

(2 and 3)
    Out of rev or mis-configured bridge:
    Again, HUBwatch can only display what it's told to display, and in the
    case of the repeaters, most of that information comes from your bridge.
    You've probably got old bridge firmware which doesn't do RBMS protocol.
    The latest bridge firmware will correctly handle repeaters, and will,
    therefore, allow HUBwatch to correctly display the status of your
    repeaters.  You must also make sure hub management is ENABLED in the
    bridge.

(4) Like the DS90L and DS90L+, the DB90 must be manually configured in the
    DECagent's slot table.  As far as the agent knows, the bridge is still
    there, so it keeps it in its slot table.

The newer hub modules are almost all quite a bit smarter than the original
modules, and they will allow more "automatic" management.  Additionally,
alarming is not yet implemented in HUBwatch 1.1, so the HUBwatch console
messages need be monitored from time-to-time to check on SNMP timeouts.

Tom Hood
HUBwatch development
215.2It sees the DS goneZUR01::SCHNEIDERRThu Apr 29 1993 03:4429
Tom,

The first I want to thank you for all your answers.

>>>1.
The agent and sees the DS gone. The border on the terminalscreen changes. Also
the HUBwatch terminalwindow says (W) DS90: SNMP timeout in fp poll group.
				 (W) status poll: can't reach slot 1

Why do we change the graphic view of the hub to "not reachable" or something
like that ? We see that the module is not reachable. All our customers want to
see if there is a defect module in the hub.

>>>2 and 3

My bridgerev is: HW+V1.0 ROM=V1.0 SW=V3.1.  I mean, HUBwatch sees the DR in the
new slot, but only after restart of HUBwatch. The old slot, where the DR was
before, shows "unknown". Thats o.k. but like in >>>1. If the repeater goes defect,
we would like to see that. I can only simulate it with disconnecting the DR. If
I disconnect it. the DR is still seen as up and running in the graphical 
interface. It does not disapear in my installation !!!!!

>>>4.
Its no problem to add the bridge. The connection to the bridge terminates from
time to time (the bridge it self works but it is from the management point of
view sleeping).


Roland
215.3SuccessZUR01::SCHNEIDERRThu Apr 29 1993 06:5014
I've done some more testings.

The DS90TL now reacts to unplud or slotchanges. The same on DR90*. But all
modules with no autodiscovery functions do not react on unpluging. But only in
the graphic interface. The poller sees that it is unpluged and says 

(W) DS90: SNMP timeout in fp poll group.
(W) status poll: can't reach slot 1


Is there a possibility to display this in the graphical view, too?


Roland
215.4Maybe for version 2.0SLINK::HOODJust add waterThu Apr 29 1993 11:257
re: polling timeouts:
	That's a reasonable thing to display when polling is enabled.
	I've added that to our HUBwatch 2.0 wish-list.  It's too late
	to get anything like that into 1.1.

Tom Hood
HUBwatch Kitmeister