The SpectroSERVER was unable to bind to a trap port

Products

• Network Observability

Issue/Introduction

You are seeing far fewer traps than normal and after a SpectroSERVER restart receive the alarm "The SpectroSERVER was unable to bind to a trap port"

netstat shows the SpectroSERVER is bound on 162.

sudo netstat -ulnp | grep :162
udp6       0      0 :::162                  :::*                                2743/SpectroSERVER

Testing on a specific device with a specific trap, with alertManager debug enabled and a TCPdump running on the SpectroSERVER, we see traps hitting the SS on 162 but we see nothing in the AlertManager debug.

Cause

Port 162 was also being used by sysEdge on the SpectroSERVER.

Resolution

We stopped the sysEdge agent and then the traps appeared as expected.
We changed the trap-sending port in the sysEdge configuration to 1692.