To: | <nv-l@lists.us.ibm.com> |
---|---|
Subject: | RE: [nv-l] Var for severity? |
From: | "Treptow, Craig" <Treptow.Craig@principal.com> |
Date: | Fri, 5 Mar 2004 09:35:43 -0600 |
Delivery-date: | Fri, 05 Mar 2004 15:58:55 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Thread-index: | AcQCxqAP70M2zt6LRdyVIApSJm+ooAAAFJtA |
Thread-topic: | [nv-l] Var for severity? |
No,
there is not, since severity is not a part of the trap itself but a constructed
value, an add-on you put in the trapd.conf.
And since NetView severities do not match TEC severities one-for-one (there is no HARMLESS in NetView for example) you would need to specify them exactly in any case. I trust that Level 2 explained that the severities were removed because the new TEC rules derive the event severity and change it depending on circumstances. You might want to follow that lead and use TEC rules to set the severities on incoming NetView events, unless you just want them to be static. Hope this helps somewhat. I am sorry that you were caught by this problem, Craig, but I am a bit surprised that you did not know about the severity issue before you migrated, since it has been a hot topic here since 7.1.4 hit the street. Thanks
for clearing this up James. I'll will have to work more with our internal
TEC support folks to investigate this further. We seem to be
abnormal with regards to how we handle Netview events in
TEC.
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [nv-l] Var for severity?, James Shanks |
---|---|
Next by Date: | [nv-l] Netview Unix Client install failure, Meyos Yemveng |
Previous by Thread: | Re: [nv-l] Var for severity?, James Shanks |
Next by Thread: | [nv-l] Netview Unix Client install failure, Meyos Yemveng |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web