Scott,
Did your company switch to Windows DNS Servers. We have found that
by default they do not do reverse tables. Reverse is very important to
NetView. Run a dns query for an ip address on several of your nodes, if
you find missing reverse records, this could definitely be part of the
problem.
Paul
Bursik, Scott {PBSG} wrote:
Good point Scott. We have made a change recently to our DNS and that may be
the issue. Do you have a suggestion for testing the response from DNS?
Scott Bursik
Pepsico Business Solutions Group
Event Systems Management
972-334-3757
scott.bursik@pbsg.com
-----Original Message-----
From: Barr, Scott [mailto:Scott_Barr@csgsystems.com]
Sent: Friday, March 21, 2003 3:03 PM
To: Bursik, Scott {PBSG}; nv-l@lists.tivoli.com
Subject: RE: [nv-l] Ruleset Lag Time
The only time I have seen this is due to delays in DNS caused event flows to
slow down significantly. I have about 20+ rulesets and I think that makes
the situation worse not better. See if you can find something in DNS that
"hangs" and causes very slow/no response.
-----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)
|