To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] Ruleset problem with Netview 7.1.4 running RedHat Linu x AS 2.1 |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Fri, 22 Apr 2005 08:49:55 -0400 |
Delivery-date: | Fri, 22 Apr 2005 13:50:31 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <AD79F859134E49439B1BF655B50EB1DE011C07E8@pccsseaex01.pemcocorp.net> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Attribute 2 is appropriate only for NetView traps. The best way to understand what your ruleset is doing is to trace. The command nvcdebug will let you do that. There's a man page for it. But I usually recommend that you just issue "nvcdebug -d all" while testing. Then you can examine the nvcorrd.alog/blog and see what's going on. You'll see an eyecatcher "Received a trap" and "Finished with the trap". Everything in between is nvcorrd running that trap through your ruleset and any others that are active. The smartset query has plenty y of trace message to tell you what the issue is. "nvcdebug -r" will reset tracing to nothing. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] Ruleset problem with Netview 7.1.4 running RedHat Linu x AS 2.1, Paul |
---|---|
Next by Date: | [nv-l] SNMPv3, Steve Lyons |
Previous by Thread: | Re: [nv-l] Ruleset problem with Netview 7.1.4 running RedHat Linu x AS 2.1, Paul |
Next by Thread: | RE: [nv-l] Ruleset problem with NetView 7.1.4 running RedHat Linu x AS 2.1, Glen Warn |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web