To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] 7.1.4 and TEC 3.7 |
From: | Christopher Haynes <haynesch@us.ibm.com> |
Date: | Thu, 15 Jan 2004 10:07:48 -0500 |
Delivery-date: | Thu, 15 Jan 2004 15:15:37 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OF63C5BEC5.50FA7ACF-ON85256E1C.00508DDF-05256E1C.00514443@mead.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Chris, The use of state correlation basically does two things: 1) Appends fqhostname on events 2) Generates Service Impact events (related to the 7.1.4 servmon daemon). Since you are still at TEC 3.7 you have no need for either of these two things as that level of TEC knows nothing about them nor what to do with them by default. thanks, Chris Haynes haynesch@us.ibm.com Tivoli Quality Assurance Manager (919) 224-1217
Alrighty then, Having commented out those two lines in the tecint.conf I am now receiving at the TEC server my events. The two lines I comments out have to do with the fqhostname? Are these new implementations in 7.1.4? If I leave them commented out what functionality am I removing from forwarding? And lastly do these lines have anything to do with Switch Analyzer, which we are also using? Thanks to all for the information and the help. Chris Petrina |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] 7.1.4 and TEC 3.7, Christopher J Petrina |
---|---|
Next by Date: | Re: [nv-l] Has anyone implemented the full TEC integration (correlation rules) NV 7.1.4 and TEC 3.9, Christopher Haynes |
Previous by Thread: | RE: [nv-l] 7.1.4 and TEC 3.7, Christopher J Petrina |
Next by Thread: | [nv-l] Has anyone implemented the full TEC integration (correlation rules) NV 7.1.4 and TEC 3.9, Van Order, Drew \(US - Hermitage\) |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web