SNMPv3 traps not appearing in TrapX log or in Spectrum as alarms

Products

• Network Observability
• Spectrum

Issue/Introduction

F5 SNMPv3 traps not appearing in TrapX due to User ID mismatch

SNMPv3 traps sent from an F5 device are not appearing in TrapX or Spectrum, despite being visible in packet captures (PCAP) arriving at the server.

TrapX and SpectroSERVER (SS) are running on same host. The SS is listening for traps on custom port 1691 while TrapX is listening for traps on port 162.

SYMPTOMS:

• Traps arrive at server interface (confirmed via tcpdump/Wireshark)

• Traps do not appear in TrapX logs (traps.log)

• Traps do not appear in OneClick Console

• Device polling works correctly via SNMPv3

Environment

Network Observability DX NetOps Spectrum with TrapX

Cause

The device was sending traps using a different SNMPv3 User ID than the one configured for polling in Spectrum. TrapX relies on the SpectroSERVER to provide the SNMP Profile details to decode and translate SNMPv3 traps. If the credentials (User ID) in the incoming trap do not match the profile known to Spectrum, TrapX cannot decode the packet and will reject or ignore the trap.

Resolution

The SNMPv3 profile credentials used by the device to send traps must match the SNMPv3 Profile defined in Spectrum for that device.

1. VERIFY SPECTRUM CONFIGURATION

   Locate the device in Spectrum OneClick. Check the SNMPv3 Profile assigned to the device model. Note the User ID and Security Level configured.

2. VERIFY DEVICE TRAP CONFIGURATION

   Check the trap destination configuration on the network device. Confirm the SNMPv3 User ID being used to send traps.

3. CORRECT THE MISMATCH

   Update the device configuration to send traps using the exact same User ID and credentials defined in the Spectrum SNMPv3 Profile.

   NOTE: Some devices (like F5) may allow setting different User IDs for polling versus trap generation. Both must match the Spectrum profile for TrapX to successfully decode the engine ID and process the trap.

4. VERIFY RESOLUTION

   Send a test trap from the device. Check the TrapX logs to confirm receipt and processing. Verify the alarm appears in Spectrum.