| 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 |
A customer is using Hubwatch V3.1 on OpenVMS. He is wondering if it is possible to manage his DECserver models 300 and 500 with Hubwatch. As far as I know, the DECserver 500 does not implement a TCP/IP protocol stack, so I assume that this one cannot be managed via Hubwatch/SNMP. The DECserver 300 V2.2A SPD states that it is manageable using the SNMP-protocol. The only question that remains is if Hubwatch makes this possible for the DSV300 (although it's not mentioned in the SPD) ? Thanks in advance, Pim.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3120.1 | HUBwatch won't do it. You need TSM. | SLINK::HOOD | My God, what have I done to my spleen? | Thu Jan 04 1996 14:47 | 14 |
No, only hub-based DECservers can be managed with HUBwatch. HUBwatch is not a general-purpose SNMP manager. It knows about specific module types and their charactistics. It then uses plain vanilla SNMP to manage that list of known devices. TSM provides highly specialized management for DECservers and is the only management software for the servers you mentioned.. Even when you've got a hub-based DECserver, TSM is a good compliment to HUBwatch, because it has access to DECserver features and functions that aren't completely available through HUBwatch. Tom Hood clearVISN apps | |||||
| 3120.2 | His other question were on ... TSM ... | UTRTSC::VELZEN | Pim van Velzen, CS/SSO Holland | Thu Jan 04 1996 16:17 | 2 |
Very clear, thanks a lot Tom. | |||||