Allen,
For a given polling period, it is a failure of all pings that will result
in this status/trap.
If you have some servers that seem to give you this when they are actually
up, you may need to adjust the timeout and/or retry count. I don't know
if you are on AIX or Windows, but with either, you can adjust both numbers.
Don't increase either by hugh numbers...a little goes a long way. For
example changing retry from 3 to 5 for a particular server usually fixes
it. You don't have to change the default numbers, you can put entries in
for just your problem servers that might be behind a slow or overused link.
that is something else to look at. if you have a set that does this
together, do they have anything in common? Do you have a particular
trunk, switch, router, cable that is impacting performance and causing slow
pings, but is not causing it to be down all the time.
Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931
http://www.redbooks.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|