[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

183.0. "" by CSC32::R_ROMMES () Fri Mar 12 1993 12:23


		Polling does not appear to work well on hubwatch 11E/MSU.
	Are there any known restrictions..?? I have my polling intervals
	set to 5 seconds, is this too low. I can swap ports on a decrepeater 90c
and not notice the change until I refresh the screen, even though polling IS 
enabled.



							Thanks, Rich.

T.R	Title	User	Personal Name	Date	Lines
183.1		QUIVER::WILSON		`Fri Mar 12 1993 14:28`	10
	As a guideline I would not set the polling interval to be anything less than 10 seconds. Otherwise there is just too much traffic to the bridge. But this depends on how much network traffic the bridge is already seeing. This is just a general observation that I've made. Also having a polling interval less than this will also degrade HUBwatch's performance. Karen
183.2	HUBwatch knows when the agent knows...	SLINK::HOOD	Just add water	`Fri Mar 12 1993 15:52`	2
	Another thing to keep in mind is that HUBwatch gets its repeater info from the DECagent, which is only polling every 20 seconds or so.
183.3	Hubwatch Timed out...	CSC32::R_ROMMES		`Tue Mar 16 1993 09:43`	10
	I've adjusted the polling to 20 seconds, accurate updates are sporadic and not very reliable however.... I get repeater timed out messages occasionally as well, even though a ping will work... Thanks, Rich.