1) The polling interval was increased because 5 minutes was causing the
Netview server to get overloaded with ping requests and hang.
2)There are 2500 objects that Netview knows about.
3)There are over 30 subnets. With the slowest connection being 10mb
ethernet.
Should the ping timeout values be changed I left those at the default?
Or am I going about this all wrong I figured putting more MLM's out would
allow me to distribute the load.
-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Tuesday, August 10, 1999 6:27 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: Node status
In order to answer this question you have to answer several prior ones.
(1) Why does it take you 15 minutes to know a node is down if netmon is
polling
every node at 5 minute intervals (the default)? If you changed the polling
interval, why did you do it?
(2) How big is your network? Do ovobjprint -S to find out how many objects
NetView knows about.
(3) People usually put MLMs where it makes sense to put them -- i.e on
remote
subnets grouped by location. How is your network configured. Many subnets?
A
few large ones?
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Dearman, Richard" <rdearm1@UIC.EDU> on 08/10/99 07:21:33 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Node status
Currently it takes me 15 minutes before I know a node is down. I want to
decrease this time to less than 5 minutes. I plan on deploying MLM's to
reduce the load on my Netview server but I don't know how many to deploy to
get the status level I desire of less than 5 minutes notice. Is there any
document, chart or rule I can use to esitmate how many MLM's to deploy to
get a desired response time.
Thanks
Brian
|