When you configure netmon, you will see an option to support secondary
addresses.
This is on by default in V6 (it was off by default in earlier releases). It
is required to be
on to support HSRP discovery and management. In certain kinds of network
configs
this retrieval of arp cache is pretty painful. You can reduce the pain by
reducing the
frequency of new node discovery. In 6.01 you will also see a new kind of
demandpoll
that just pings all of the interfaces and skips the expensive snmp polls.
If you are not
doing HSRP, and if your routers only have one address assigned to each
interface,
then you can probably live without secondary address support. I would not
turn it off,
however, until you were pretty satisfied with your basic network discovery.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

"Treptow, Craig" <Treptow.Craig AT principal DOT com>@tkg.com on 07/28/2000
04:31:46 PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "NetView List (E-mail)" <nv-l AT tkg DOT com>
cc:   "Treptow, Craig" <Treptow.Craig AT principal DOT com>
Subject:  [NV-L] ARP cache retrieval?



Hi.  We are running Netview v6 on AIX.  We just did a test by doing a
test->demand poll on a couple of routers and watched as their CPU
utilization
went to the high 90's and sometimes 100%.  It appeared to be the worst
during
the "Getting ARP table data for discovery of secondary interfaces" phase
(or
something close to that verbage).

Can we prevent this ARP cache dumping?  If we can, will it prevent
discovery
of new devices?

Also, where/how may I search the archives of this list?

Thanks for any help!

Craig Treptow
Principal Financial Group
I/S Network Administration
(515) 247-6207

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l