| 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 |
Hi,
1. I have a customer who has some 90TS repeaters configured within
a sub-community which are not seen by the AGENT running on a
remote HUB.
Platform: VAX 4000-60
OS: OpenVMS V5.5-2
HUBwatch: V3.0
2. Also, when this customer tries to set TRAPS, he claims the devices
disappear from the "known devices" displayed on his screen. I have
tried this (without the sub-communities) and it all seems OK.
BUT;
I am not really 100% certain what the exact nature of his problem is,
so please bear with me and I may be able to clarify this more
tomorrow. (He has several outstanding calls with this gear and I am
not overly familiar with it either [yet]).
Are these known problems?
I understand HUBwatch V3.1 is due next month (Sep-1994) so maybe
this is what is needed?
TIA,
Harry E.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1361.1 | Some suggestions | NACAD2::HAROKOPUS | Wed Aug 31 1994 14:30 | 20 | |
From your note I am implying that these 90TS modules are in remote
DEChub 90s and the DECagent 90 is located somewhere else on the LAN.
If this is the case then there are a couple of things to check.
1) Make sure that his DECagent 90 is running firmware version V2.1.3
2) The hubs containing the 90TS need a DECbridge 90 to do the
autodiscovery of the other modules in the hub.
Finally, your customer will want to upgrade to HUBwatch V3.1 when
it's available. Although V3.0 has latent support for the 90TS it
is not offically supported until V3.1.
If I have misunderstood the configuration then post more
information.
Thanks,
Bob
| |||||