Conference netcad::hub_mgnt

1383.0. "Probewatch/HUBwatch for windows - Problemlist" by RULLE::BHANSSON () Wed Sep 07 1994 10:41

We have been installing a "Network Watch KIT" on a PC for monitoring a 
TRUCK Construction Plant NETWORK. This kit consists of PC with Probewatch 
and HUBWATCH for windows. We would like to list a couple of problems which 
has strong importance for us:
	
	* PROBEwatch *

	1) What is the calculationmethod for the statistic value "AVERAGE"?
	   (variable independent)
	   What timeslot is in that calculation? Since Probe init?
	   Since Segment Zoom start? Since PC reboot? Other?

	2) Is there a way of seeing all predefined watchdogs? Today You have
	   to know about the watchdogsetup or scroll all possiblities to find 
	   out. This must not be the proper way.

	3) When setting up a trap, and using an nordic character (O with dotts)
	   in the descriptionfield - Like: (translated from swedish) "Now 
	   there is a raising error rate on the blue segment...". The trap is 
	   just rejected and setup with blanks in the rest of the formularfield.
	   No errorcode or equal - just dropping the whole entry.

	4) More from the watchdog...In the watchdog setup menu there is a
	   "AGENT" buttom. This one is not possible to use. You get no
	   information and instead an error message when it is pressed.

	5) We have problem when printing the graphs from the 
	   "longterm hist" and "short term history" fields. The errors
	   appear (in swedish and translated): "GREHIST caused by general
	   protection failure in module GRLHIST (longterm) GRSHIST (short
	   term) at 0001:2ec4 (long term case). Is this something related
	   to the product, PC, DOS or windows? 

	6) The last point in the Probewatchlist is more like cosmetic. 
	   When we want a graph printout from the "cumulative statistic part" 
	   and only "util" is selected as variable, there is no information 
	   in the printout about what data is presented. Bug?
	   The information do appear if You select more than one variable. 
	   However in this case no current and average 3dbar are presented, but
	   that's another story...


	* HUBwatch *

	1) We have not been successful when forcing in a DECserver 90TL in
	   a DECHUB90 via HUBwatch. The SNMP agent is running on the 
	   DECserver. PING from PC to DECserver works OK. But the DECserver
	   is not discovered in the HUB automaticly and it is not possible 
	   to put it there by force. Is there anything obvious here? As 
	   an addition the DECHUb contains a DECbridge90FA as the "known" 
	   module.

    
	* BOTH HUBwatch and Probewatch *

	Are there any advise of how to configure the PC for best 
	performance and functionality when using both HUBwatch and
	Probewatch in the same PC at the same time. Now and then the
	PC hangs and will only be cured by ctl-alt-del.

	We are very pleased to get help with our installation.
	The Construction Plant has strong desire of these products.


	Thanks in advance!

	Johan and Bosse