SBGW EventModel Name Displays as Ascii Decimals with SNMP V2 Traps

Products

• Network Observability
• Spectrum

Issue/Introduction

When using the Southbound Gateway (SBGW) integration in DX Spectrum to process SNMP V2 traps, the EventModel names are created using a string of decimals (e.g., 49.48.46.49) instead of the expected hostname or string value.

This typically occurs when map_traps_to_this_ip_using_header is set to true on the EventAdmin model.

Environment

Product: DX NetOps Spectrum
Component: Southbound Gateway (SBGW) / SpectroSERVER

Cause

The sending application or device is appending an extra .0 OID suffix to the end of the trap varbinds (e.g., 1.3.6.1.4.1.2544.1.13.1.1.1.9.0 instead of .9).

In SNMP V2, this trailing .0 indicates an instance variable that Spectrum may not recognize as a table attribute. This malformed OID prevents the SBGW from correctly converting the trap to a V1 format internally, causing it to fall back to an Ascii-encoded decimal representation of the network address for the model name.

Resolution

To resolve this issue, the incoming trap format must be corrected at the source:

1. Modify Trap Source: Configure the sending device or application to remove the trailing .0 from all varbind OIDs in the SNMP V2 trap.
2. Verify Correction: Use a packet capture tool (like tcpdump or Wireshark) to ensure the OIDs now end at the correct leaf node without the extra suffix.
3. Switch to SNMP V1 (Alternative): If the device configuration cannot be altered, switching the application to send SNMP V1 traps will also resolve the naming issue, as V1 traps are handled differently during the SBGW conversion process
4. Cleanup: Delete the incorrectly named EventModel objects in Spectrum. Upon the next trap arrival, Spectrum will recreate the models using the correct string name.