Operational Defect Database
BugZero updated this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 362511
Smarts IP: Receive 'mangled or incorrect packet; parsing aborted and data' error when running sm_snmpwalk
Last update date:
4/16/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Receive "mangled or incorrect packet; parsing aborted and data" error when running sm_snmpwalkMessage similar to the following is seen from the Smarts IP system command line when running sm_snmpwalk: D:\InCharge7\IP\smarts\bin>sm_snmpwalk.exe --fmt="walk" -c xxx fw302lu.abc.def.eu.intSaving MIB walk to file(s) 'fw302lu.abc.def.eu.int.walk' ...SNMP-N-EPARSER-Mangled or incorrect packet; parsing aborted and datadiscarded; in file"L:/FOUNDATION-7.0.2.X-HF/17/smarts/snmp/lib/SNMP_Parser.c" at line 1211 The OID generating the problem is found in the Smarts IP dump file to be .1.3.6.1.4.1.94.1.21.1.10.5.0 as follows: VarBind -> SEQUENCE (0x30), 20 bytes: OBJ-ID (0x06), 12 bytes == ".1.3.6.1.4.1.94.1.21.1.10.4.0" GAUGE-32 (0x42), 4 bytes == 1995011748 VarBind -> SEQUENCE (0x30), 21 bytes: OBJ-ID (0x06), 12 bytes == ".1.3.6.1.4.1.94.1.21.1.10.5.0" UNKNOWN(71) (0x47), *Error!* Incorrect data type. The .1.3.6.1.4.1.94.1.21.1.10.5.0 OID belongs to ipsoKernMaxMem and the Data Type defined for this OID in the device's MIB definition has SYNTAX UInteger32 as in the following: ipsoKernMaxMem OBJECT-TYPE SYNTAX UInteger32UNITS "Bytes"MAX-ACCESS read-onlySTATUS currentDESCRIPTION "The maximum amount of kernel memory. "
Cause
The Smarts sm_snmpwalk utility does not support the UInteger32 deprecated Data Type. The UInteger32 is defined in RFC 1442 dated April 1993. In RFC 1902 dated Jan 1996, UInteger32 was removed from the standard SMIv2 data types and replaced by Unsigned32.
Resolution
Smarts is working as designed. Contact your SNMP agent vendor to resolve this issue.
Related Information
The device does not show that error when walking it with a third party tool but the OID ".1.3.6.1.4.1.94.1.21.1.10.5.0" is not present in the walk output.
