[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 |
1923.0. "HUBwatch v3.1 agent times out when 900ee gets a load." by HACMAN::HACK (Don Hack, NIS) Mon Jan 23 1995 19:38
The HUBwatch v3.1 PC is plugged into a 900tm. A 2nd 900tm defined as
the network mgr for the DH900. A 900ee is also on the hub. A grand
total of 2 PC are plugged into the hub, one into each 900tm. When we
take a DECXM-M, which is connected to the customer's network, and plug
it into one of the AUI ports on the 900ee, we often get a "agent did
not respond" (not exact text) message. While I understand that we are
pretty much going from near zero activity on the 900ee to probably
seeing their entire network, why should the agent (which is on one of
the 900tm's) not respond.
This happened 4 of the 5 times we hooked in the live network.
We often had to reboot the HUBwatch station to talk to the agent again.
Any ideas?
-Don
T.R | Title | User | Personal Name | Date | Lines
|
---|