What I do is to put that address in the seedfile with % in front of it.
This
tells netmon that it is an intentional duplicate, sort of like an HSRP
interface,
and it moves it around less. Otherwise, you will see it move from box to
box
to box every time netmon starts up, every time you do a demandpoll, and
at every daily configuration poll. This is not a perfect solution, but it
helps.
The other thing you can do is to find the oid entry for that device type in
the /usr/OV/conf/oid_to_type file and give it the I flag. That tells netmon
to treat these devices as if they were non-snmp after discovery. So it does
not go inspecting the interface and address tables at each of those
periods named above. This was the old way of handling such problems,
and it istill works.
Also, that interface, by getting delete and added, causes the devices
to be continually promoted to routers, another reason to put a stop to
it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Paqui Martinez
Moreno/OPENSOLUTIONS" To:
nv-l@lists.tivoli.com
<Paqui.Martinez@openso cc:
lutions.es> Subject: [nv-l] interface
deleted and add
07/23/2002 07:54 AM
Hi:
Netview 6.0.3 Aix 4.3.3
I'm monitoring the brigges 3COM Superstack II. These bridgges are
configured the interface ETH and an interface type SLIP serial line IP.
All the brigges are the same configuration and the same ip address for the
interface SLIP.
The Netview deleted and add te interface to some briddges, depending on the
one who does the call for this interface
There is some solution for this problem?
Paqui Martinez Moreno
E-mail: paqui.martinez@opensolutions.es
Tfno.914160562
|