RE: [nv-l] Copying traps--could use an expert explanation

[James Shanks <jshanks@us.ibm.com>]

You mean copying the trap definitions
in trapd.conf using a node list to distinguish them?

The traps will have the same specific
trap number  but you have to give them different names,  and
you should then be able to give them different TEC event classes and different
slot maps.  

Did you know that you can create a file
of sources and put only the file name in trapd.conf?  That is a lot
easier to maintain

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Van Order, Drew \(US - Hermitage\)" <dvanorder@deloitte.com>
Sent by: owner-nv-l@lists.us.ibm.com

08/05/2004 05:59 PM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc
Subject	RE: [nv-l] Copying traps--could use an expert explanation

Thank you for jumping in James.
 
Copying traps in NV and sending
them as different TEC events.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On Behalf Of James Shanks
Sent: Thursday, August 05, 2004 4:11 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Copying traps--could use an expert explanation


I'm confused about the mechanism here. 
Copying traps in NetView and sending them as different TEC events or copying
traps in TEC and sending them back to reception? 

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Van Order, Drew \(US - Hermitage\)" <dvanorder@deloitte.com>
Sent by: owner-nv-l@lists.us.ibm.com

08/05/2004 12:45 PM

Please respond to
nv-l

To	<nv-l@lists.us.ibm.com>
cc
Subject	[nv-l] Copying traps--could use an expert explanation

Hi all,

We are being asked to use NetView for more than device polling and up/down status. The big push is to save some $$ by using NV to receive traps from servers for HP Insight Manager events, and possibly expand to other applications that send traps, rather than using say NetIQ AppManager or MOM. Everything has to become a TEC event, so this means tying it into TEC_ITS, which we already do with other external trap sources. I have Compaq traps in, mib2trapped, are receiving test traps fine.

Here's where trap copying comes in. We send TEC events to a help desk system based on the event class only, no other method available at this time. We normally send all Compaq events to one team, so no problem, that means one event class will do. Now, we will need to send Compaq events for 98% of servers to one team, but 1% to a second, and 1% to a third. So, we can copy traps, change the name and TEC event class, and assign a source file for the small server groups. Since the trap number itself can't change (or can it) when you copy a trap I think we will now create 2 TEC events when traps from server group 2 come in--one in team one, one in team two. This is because the original trap has no source defined--which is not reasonable in this case because it's hundreds of servers. And the trap numbers are the same, so TEC_ITS will forward both, assuming I've added a node to the ruleset based on specific trap number, rather than a trap settings node.

I hope I explained this decently. I searched the archives, and haven't seen a post like this. I think it will all become clear when I understand how the trap coming in is matched to the trap name, number, etc. Maybe this can't be done, but I have to try because the cost savings are exceptional and I don't think OpenView can do any better.

Thanks--Drew

Drew Van Order
Deloitte Services LP
Tel: +1 615 882 7836
www.deloitte.com

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.

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.