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
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.
Tel: +1 615 882
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.