[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

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

1023.0. "TGV MultiNet V3.3 & HUBwatch alarms" by SLINK::HOOD (I'd rather be surfing) Tue May 24 1994 17:10

A problem has been found with the alarms component of HUBwatch for OpenVMS
VAX V3.0 running with TGV MultiNet V3.3 TCP/IP software.  If TGV MultiNet
V3.3 is used on the workstation from which HUBwatch is run, the HUBwatch
alarms component's Event Daemon process (NMS_EVENTD) will consume most of
the CPU of the workstation.

If TGV MultiNet V3.3 is in use, do not use the HUBwatch alarms components.
This problem does not affect any other HUBwatch for OpenVMS V3.0 components.

This is NOT a problem for customers running UCX, nor for customers running
TGV MultiNet V3.2.

If TGV MultiNet V3.3 is in use:

    o During HUBwatch installation, answer NO to the question:
		* "Automatically start the HUBwatch poller?"

    o During the HUBwatch IVP, answer <CTRL/Z> to the following prompt:
		"* Hit the <Return> key to invoke the HUBwatch events viewer, or
		   <ctrl/z> to abort:"

    o Do NOT use the following DCL commands:
		WATCH /POLLER
		WATCH /VIEWER

    o Do NOT use the following items from the HUBwatch Applications menu:
		Alarms -> Alarm Setup
		Alarms -> Start Poller
		Alarms -> Stop Poller
		Alarms -> Viewer

This problem will be corrected in a future HUBwatch for OpenVMS VAX release.

T.R	Title	User	Personal Name	Date	Lines