Re: [NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap

Subject:	Re: [NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap
From:	James Shanks <jshanks AT us.ibm DOT com>
To:	Tivoli NetView Discussions <nv-l AT lists.ca.ibm DOT com>
Date:	Thu, 12 Apr 2007 09:03:10 -0400

Without seeing the raw hex it would be hard to say why NetView thinks this trap is invalid.

If you set the "hex dump all packets" option on trapd so that it runs with the -x option, and then start the trapd.trace (you can toggle it on and off from the command line with "trapd -T"), trapd will write the incoming packet in hex to the trace file. Then you can send the trace to NetView Level 2 for analysis. The trace may also provide an error message as to what was considered invalid in the trap but at 7.1.3, I don't know how complete that function is.

James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Network Availability Management
Network Management - Development
Tivoli Software, IBM Corp

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

<Prev in Thread]	Current Thread	[Next in Thread>
[NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap, Sue Young Re: [NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap, James Shanks <=