| 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 |
I am working with a customer who is evaluating both HUBwatch and VCS
and the question arose as to whether HUBwatch could be set up to be an
icon from a VCS session (as opposed to being launched from
Polycenter400). They are also wondering about alarm and event trapping
capabilities in HUBwatch; can you write code that will page someone
(assuming you have DECtalk) if a significant event occurs?
Does anyone have any experience with HUBwatch and VCS running
simultaneously on a VS4000-60? What sort or system resources should be
dedicated to HUBwatch?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 213.1 | I need an answer too. | EVTW13::POULLEAU | Gilles - Enjoy Romanee-Conti | Tue May 11 1993 12:46 | 15 |
Hello, Designing Control Centers which manages commonly Network System and Applications, We have a big interest to catch events from whatever they come. Hubwatch is one of the products we plan to use but it would be more efficient if we could integrate it in our common event treatment. The operator would operate the event using hubatch but he would have detected it in the same manner as a VCS, Watchdog, DECmmc .. event. So is there a way to trap events outside Hubwatch. Bests Regards Gilles | |||||
| 213.2 | V1.1 of the DECagent supports 4 traps | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Fri May 28 1993 02:21 | 10 |
V1.1 of the DECagent code provides four traps that can be sent to any
of 8 addresses. To quote from the SPD (EMDS::MANAGEMENT:AGENT.SPD)
Version 1.1 supports the following MIB II TRAPs:
Cold Start Warm Start Authentication Failure
It also supports one enterprise-specific TRAP to indicate a hub
configuration change.
| |||||