Scott,
I used to have my trapd queue size set to 30000. However, it just consumed
memory I needed for user interfaces. If there was a trap storm or major
network outage - it never did much good. I lowered it to 5000 and I seldom
have trouble if I watch my trap rate. I'd leave the receive buffer size
alone.
Ray Westphal
Enterprise Rent-A-Car
-----Original Message-----
From: Bursik, Scott {PBSG} [mailto:Scott.Bursik@pbsg.com]
Sent: Friday, March 21, 2003 3:04 PM
To: nv-l@lists.tivoli.com
Subject: RE: [nv-l] Ruleset Lag Time
I see that the trapd queue size is set to 30000. Is this too high? Also the
receive buffer size is set to 9216. Is this OK?
Scott Bursik
Pepsico Business Solutions Group
Event Systems Management
972-334-3757
scott.bursik@pbsg.com
-----Original Message-----
From: Bursik, Scott {PBSG}
Sent: Friday, March 21, 2003 2:56 PM
To: nv-l@lists.tivoli.com
Subject: RE: [nv-l] Ruleset Lag Time
Thanks Ray,
I have checked what you mentioned and so far everything looks OK. I will
continue to look at it. It seems to be OK at the moment. I have created a
rule that triggers all Node Up and Node Down traps and sends then to syslog
and I don't see more than a 20 second lag in the two at the moment.
Scott Bursik
Pepsico Business Solutions Group
Event Systems Management
972-334-3757
scott.bursik@pbsg.com
-----Original Message-----
From: Ray Westphal [mailto:westphal2002@charter.net]
Sent: Friday, March 21, 2003 2:17 PM
To: Bursik, Scott {PBSG}; nv-l@lists.tivoli.com
Subject: RE: [nv-l] Ruleset Lag Time
Hello Scott,
What is your trap rate? NV support has told me that if it is greater than
10/second for an extended amount of time, trap processing will be delayed. I
run the trapd -T command, wait about 30 seconds, run the trapd -T command
again. Then check for the number of queued events in the
/usr/OV/log/trapd.trace file. (You may want to clear the file first. Then go
to the end of the file.) Look for a line like "application queue size 1 of
5,000 events" The latter is number is set when you configure trapd. If this
queue size is greater than 1 and growing, for instance "application queue
size 200 of 5,000 events" then you may be receiving too many traps.
Remember - the trap rates include those traps that are not logged as well.
Hope this helps.
Ray Westphal
Enterprise Rent-A-Car
-----Original Message-----
From: Bursik, Scott {PBSG} [mailto:Scott.Bursik@pbsg.com]
Sent: Friday, March 21, 2003 1:50 PM
To: nv-l@lists.tivoli.com
Subject: [nv-l] Ruleset Lag Time
NetView 6.0.3 AIX 4.3.3
I have about 14 different rulsets starting in ESE.automation. I have been
running this configuration for almost 3 years. In several of these rulesets
I have timers that hold a node down event for 15 minutes and send it if the
node up doesn't come before the timer expires. It was recently brought to my
attention that we are getting events quite some time after the actual event
occurs. Here is an example:
In the trapd.log I see that hostx had a Node Down event at 20:35:06 and the
Node Up event is 21:25:43
In my ruleset I am grabbing the node down event and holding it for 15
minutes and then issuing a logger -p command to send the trap attributes to
the syslog daemon.
In the syslog the timestamp of the node down event is 23:44:28 and the node
up is 00:30:21
I have been checking other events in other rulesets as well and I have seen
similar symptoms but the time lag seems to vary. Can the daemons get that
far behind?
Has anyone seen this sort of behavior happen before?
Scott Bursik
Pepsico Business Solutions Group
Event Systems Management
972-334-3757
scott.bursik@pbsg.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)
---------------------------------------------------------------------
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)
---------------------------------------------------------------------
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)
---------------------------------------------------------------------
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)
|