Frank!
That indeed would work, and use that for our heartbeat events. The
script provided by support had throttling and bursting logic built-in,
so we wanted to take advantage. I copied/pasted the trapd.trace output
into the script and added \x where needed. It now generates perfectly
formatted traps that provide all the TEC_ITS slot info, etc. Very cool,
and we are now hammering failover server from trap reception to TEC
every 10 minutes.
Thanks for the suggestion, though--Drew
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
On Behalf Of Frank W. Hansen
Sent: Wednesday, June 02, 2004 12:00 PM
To: nv-l@lists.us.ibm.com
Cc: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Hex code for a Node or Interface Down Internal NV
Trap
Hi Drew. Not to be a simpleton...but how about just using:
/usr/OV/bin/event -e IDWN_EV -h NETVIEWTEST
/usr/OV/bin/event -e NDWN_EV -h NETVIEWTEST
Thanks
Frank
> Hi all,
>
> A kind person from support supplied us with a Perl script to generate
> traps, the current variable is:
>
> $trap = "\x30\x2f\x02\x01\x00\x04\x06\x70\x75\x62\x6c\x69\x63".
> "\xa4\x22\x06\x0c\x2b\x06\x01\x04\x01\x02\x03\x01\x02\x01\x01".
> "\x03\x40\x04\xcf\x2e\xe6\xda\x02\x01\x04\x02\x01\x00\x43\x04".
> "\x01\xa2\xdd\x67\x30\x00";
>
> This generates IBM authentication failure traps. We'd like to change
it
> so it generates a node or interface down trap. Might anyone know which
> hex values to change in order to accomplish this?
>
> Thanks!--Drew
>
>
>
> 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.
>
--
Best Regards,
Frank W. Hansen
www.EnterpriseInnovations.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.
|