You still need to have it on. NetView (netmon) and the MLMs automatically
"share" status polling. Netmon polls every MLM to make sure it's still
working. If it's not, you'll see an "MLM Down" trap, and netmon
automatically takes over the status polling for the nodes that the MLM was
polling. When the MLM is back up, you'll see an "MLM Up" trap, and netmon
gives the status polling back to the MLM.
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)456-4231 * mailto:Joel.Gerber AT USAA DOT com "
From: Gregory Adams [SMTP:gadams AT US.IBM DOT COM]
Sent: Tuesday, February 29, 2000 12:24
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: status monitoring from TME10 NetView via mlm
We are a running a configuration that consists of a top level NV6k server
on AIX 4.3.2 running NV6000 v5.1.2. We have a couple of other NV6K server
machines that are remote, they are running NV6000 v5.1.2 with MLM
configured. ( trapd is listening on port 162 and forwarding specific traps
to midmand who is listening on port 165 the destination table is set to
send traps to the top level manager on port 162)
On the top level machine we want to off load status polling to the mlm
machines. We have configured netmon to use an mlm seed file and have
created collections that contain the devices we want status checked via
mlm. We can see that the collections that we created have been translated
to create the alias tables and status monitoring tables on each mlm
Also, on the top level machine we have specified yes to have netmon use
system monitor MLM for polling.
I have a questions regarding this configuration,
1. With the netmon configuration set this way does that status polling
setting in /usr/OV/bin/nmpolling dialog need to be turned on or off?