What version, what platform, how many objects? Seedfile with
oids in it? Are you having other performance problems with the box?
Is you ovwdb cache size set high enough for the number of objects?
I guess you have to assume that netmon really is that far behind, and it is
not just this router. That can be caused by slow name resolution, among
other things, so some tuning is in order. Try using this tool to check and
see how many nodes it is behind (if you are on unix).
#!/bin/ksh
#set -x
cat /dev/null > /usr/OV/log/netmon.trace
netmon -a 12
sleep 6
if [ -f /usr/OV/log/netmon.trace ]; then
echo "Netmon is " `grep [-].*[:] /usr/OV/log/netmon.trace | wc -l `
"behind in status pinging";
else
echo "Netmon is too busy to report now. Try later."
fi
exit
See the man page for netmon for the various -a options.
It is not unusual for it to report that it is a thousand or so behind,
and then catch up quickly. If netmon has just started, it could be much
further behind.
I would turn on tracing in netmon at startup to see what it is doing.
Once you are familiar with what is in there and how far behind it
really is, if you don't figure it out, you should consider calling
Support.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Peter_Chow@TD.COM
To: nv-l@lists.tivoli.com
05/14/2002 03:56 cc:
PM Subject: [nv-l] nv-l Digest 13
May 2002 22:38:51 -0000 Issue 70
Demand poll indicates that a ping is being used.
When I log on to the router and status the interface, it does indicate that
it is down.
The only thing peculiar about this setup is that there is a very large
amount of unmanaged devices. Could this be causing the delay?
Regards, Peter.
----- Forwarded by Peter Chow/CA/TDBFG/TDGROUP on 05/14/02 03:51 PM -----
----------------------------------------------------------------------
Date: Mon, 13 May 2002 18:31:18 -0400
To: nv-l@lists.tivoli.com
From: "Leslie Clark" <lclark@us.ibm.com>
Subject: Re: [nv-l] Netview Traps - Time to post
Message-ID: <OF21AA9E5A.72FB0C2E-ON85256BB8.007B8B26@raleigh.ibm.com>
By any chance are you polling that device via SNMP as opposed to ping?
You can tell when you do a demandpoll. If it is SNMP, the status of each
interface is displayed in terms of ifAdmin and ifOper status.
Is it possible that the device itself believes that the interface is up and
reports it as up, for that long?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
=============================================================================
I agree that this is not normal and thank God that its not happening in our
production environment.
If I ping the interface object after I pull the cable, the status will
change to down and a trap is received right away.
If I do nothing, then no status update or trap is received for a long
period (2.5 hrs)..
SNMP Polling Info is : timeout 4.0; retry 3 ; polling 3m.
The IP interface is represented and managed.
Any suggestions on what may be wrong?
=============================================================
Well, that's not good. Fortunately it is not normal, either!
When you pull the cable, can you still ping the address
of that interface from the Netview box? And what is the
polling interval set to? That is in Options...SNMP configuration
and defaults to 5 minutes. Is the IP address of the interface
represented on the map, and is it managed? You should see
at least an Interface Down event in trapd.log for that interface
within one polling cyle.
I would have to say there is a lot more to this story than
what you have told us so far. Tell us more...
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Peter_Chow@TD.COM
To:
nv-l@lists.tivoli.com
05/13/2002 10:55 cc:
AM Subject: [nv-l] Netview
Traps - Time to post
We're performing some testing with Netview traps in a lab environment.
One of the tests was to pull out the interface cable on a router and see
how long it would take to receive the interface down trap on netview.
We expected to receive the trap within minutes but instead received the
trap almost two and a half hours later!!!
What is going on here? How can we minimize this 'turnaround time' to
within minutes?
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
|