Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 359014
Smarts: Trap Adapter is not receiving V2c Traps from Avaya system
Last update date:
3/22/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Smarts Trap Adapter is not receiving V2c Traps from Avaya system
Cause
These traps which are in violation of RFC 3416:4.2.6. The SNMPv2-Trap-PDU... The first two variable bindings in the variable binding list of an SNMPv2-Trap-PDU are sysUpTime.0 [RFC 3418] and snmpTrapOID.0 [RFC 3418] respectively.The Smarts trap manager parser, checks within the V2c traps that the first varbind is SysUpTime (".1.3.6.1.2.1.1.3.0"), and that the 2nd is the TrapOID (".1.3.6.1.6.3.1.1.4.1.0"). If this is not the case, the first test for sysuptime fails, and an exception is raised which causes the packet not to be parsed further, resulting in the packet being discarded. This RFC requirement is specific to V2c (V1 is not affected).
Resolution
This is a vendor issue. Traps need to be in the correct format before the Smarts trap adapter can process them. As a temporary workaround, you can configure the device to only forward V1 traps. However, the primary V2c issue needs to be reported to the vendor.
