Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[NV\-L\]\s+Invalid\s+SNMP\s+trap\s+from\s+1841\s+router\s+usingTCL\s+generated\s+trap\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[NV\-L\]\s+Invalid\s+SNMP\s+trap\s+from\s+1841\s+router\s+usingTCL\s+generated\s+trap\s*$/: 2 ]

Total 2 documents matching your query.

1. [NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap (score: 1): Author: Sue Young <syoung AT westpac.com DOT au>; Date: Thu, 12 Apr 2007 19:03:26 +1000; Hi, Has anyone experienced the following invalid SNMP trap message from a TCL generated trap message from 1841 routers. 1176366284 7 Thu Apr 12 18:24:44 2007 <none> T WARNING: invalid SNMPTrap packet; /usr/local/webapp/mharc-adsm.org/html/nv-l/2007-04/msg00039.html (13,992 bytes)
2. Re: [NV-L] Invalid SNMP trap from 1841 router usingTCL generated trap (score: 1): Author: James Shanks <jshanks AT us.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 th; /usr/local/webapp/mharc-adsm.org/html/nv-l/2007-04/msg00040.html (11,826 bytes)

Current List: 1 - 2
Page: [1]