[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
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 |
90.0. "Status daemon not showing down hubs" by GUCCI::DMCCLOUD (Dennis McCloud - SOA ANC) Mon Nov 30 1992 13:31
I just returned from a customer site where we installed HUBwatch for
MSU and have problems with the status polling daemon. The customer
configuration is ~20 DEChubs and 5 agents with ~4 communities per agent.
S/W versions are MSU V1.1, HUBwatch V1.0, WGBV29.
The DH90_hub_statusd successfully shows status on a single community
agent but does not show status correctly on the 2-4 communities. In
MSU I setup multiple icons for the different HUBs and set the community
string to match the second, third, and fourth communities using the
address of the agent. The DEChub90 group is used.
The symptoms are as follows:
1) If all HUBs are up and available when the DH90_hub_statusd is
started then all icons are notes as UP (Green). OK.
2) If a HUB other than the one with the agent is down when
DH90_hub_statusd is started it show up as being NOT POLLED (Black)
instead of what you would expect NO RESPONSE (Brown). OK
3) If the HUB with the agent is disconnected then all icons show
NO RESPONSE (Brown). OK.
4) If a HUB other that the one with the agent is unplugged the
status stays UP (Green) and does not change to NO RESPONSE (Brown)
as expected. NOT OK.
The customer would really like to see a status change on a HUB when
it goes down.
Any Suggestions?
Thanks,
Dennis
T.R | Title | User | Personal Name | Date | Lines
|
---|