RE: [nv-l] Netview and TEC Integration

2004-09-21 17:38:00
Subject: RE: [nv-l] Netview and TEC Integration
From: "Van Order, Drew \(US - Hermitage\)" <dvanorder AT deloitte DOT com>
To: <nv-l AT lists.us.ibm DOT com>
Date: Tue, 21 Sep 2004 16:23:05 -0500
I think you've got it Jane.

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
On Behalf Of Jane Curry
Sent: Tuesday, September 21, 2004 11:25 AM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Netview and TEC Integration

Hi John,
I'm not aware of any out-of-the-box integration for  Ack'ing in NetView 
and getting automatic ACKs in TEC.  The simple (but I suspect WRONG 
answer) is to forward NetView ACK TRAPs to TEC.  I think you will find 
these are unconfigured by default in both trapd.conf and in TEC_ITS.rls.

The reason I suspect it is wrong (or at least, not quite right!) is that

this is what TEC sends to NetView in the Synchronization rules in 
netview.rls - you would then end up forwarding the ACK TRAP back to TEC 
again........    Perhaps with an extra rule in TEC that filters this ACK

TRAP out if it is a recent status change???  You'd then need a simple 
TEC rule that changed the status of all recent events from the same node

/ interface, to ACK.

Just thinking off the top of my head....... anyone else?


John Altman wrote:

>Does anyone have the Netview and TEC integration working where you can
>acknowlege devices within netview and have them update the TEC console
>the acknowledgement?  I have it working where we can acknowledge an
>from the TEC and it will update the netview maps, but not both ways.
>John M. Altman III
>Ahold Information Services
>(Embedded image moved to file: pic26919.gif)
>IBM Certified Deployment Professional
>TEC V3.8 Network Management

Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry AT skills-1st.co DOT uk>.  All rights

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message.  Any 
disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited.

<Prev in Thread] Current Thread [Next in Thread>