Re: [NV-L] Can we break down the var bind further and represent it on the event viewer?

[Francois Le Hir <flehir@ca.ibm.com>]

Hi Rajesh,

The only way I know of is to call a script automatically when this trap is received (automatic action - configured in trapd.conf or via xnmtrap) and have the script break the data the way you want and generate a new trap with the varbin you need so that this trap can be displayed in the event viewer.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Technology Services


"Do not go where the path may lead; go instead where there is no path and leave a trail." - Ralph Waldo Emerson.
"Lakka, Rajesh Kumar" <Rajesh.Lakka@in.unisys.com>

"Lakka, Rajesh Kumar" <Rajesh.Lakka@in.unisys.com>
Sent by: nv-l-bounces@lists.ca.ibm.com

11/24/2008 01:34 AM

Please respond to
Tivoli NetView Discussions <nv-l@lists.ca.ibm.com>

To	<nv-l@lists.ca.ibm.com>
cc
Subject	[NV-L] Can we break down the var bind further and represent it on the event viewer?

Hi,
        I am receiving a trap as follows on the Tivoli netview 7.1.5.

Received at the destination as follows:
Source:
192.62.182.203
Timestamp:
3408 hours 44 minutes 46 seconds
Enterprise:
.1.3.6.1.4.1.3183.1.1
SNMP Version:
1
Specific:
1378048
Generic:
enterpriseSpecific

Variable Bindings:
 
Name:
.1.3.6.1.4.1.3183.1.1.1
Value:
(OctetString)0x00 0x65 0xF4 0x80 0xB6 0x35 0x10 0x00 0xB1 0x18 0x08 0x00
0x0B 0x1A 0x00 0x26 0x00 0x36 0x14 0x79 0xF1 0x18 0xFF 0xFF 0x20 0x20
0x02 0x81 0x60 0x00 0x00 0x80 0x00 0xFF 0x00 0x00 0x00 0x00 0x00 0x19
0x00 0x00 0x00 0xDF 0x04 0xC0 0xC1





My question is can we further breakdown the Octetstring which is in
binary, like the first 16 bytes represent are the system GUID. Next 2
bytes are for the sequence number and so on..... 


How do we capture these bytes coming from the single octet string
separately, break it down further as to what exactly the byte informs,
and then represent in a user readable format on the Tivoli netview event
viewer?

Earlier have been trying to represent var bindings directly but in this
case we need to read the bytes and then form the message based on the
content of the bytes.

Thanks,
Rajesh

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to internal IBM'ers only)

_______________________________________________
NV-L mailing list
NV-L@lists.ca.ibm.com
Unsubscribe:NV-L-leave@lists.ca.ibm.com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)