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 AT UIC DOT EDU> on 08/10/99 07:21:33 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT 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