SSP not sending SNMP traps

Products

• SSP-S410 PLATFORM

Issue/Introduction

SSP Appliance are failing to send SNMP traps. 

Cause

Investigation reveals gaps in the SNMP implementation. This is particularly a first time implementation.

Resolution

Note that SNMP traps send notification to the server when appropriate conditions are met.

If the SNMP setup is new, we recommend to follow the step-by-step guidance detailed in the Tech. Doc, with URL below, to verify your configurations and ensure they match the steps herein. 

Integrated Secure Gateway 2.4

To enable SNMP trap in ISG, on the SSP-S410 appliance, execute the CLI commands in the Tech. Doc. withy the URL below.

Configure SNMP Traps

For how the customer may configure targets that will receive notification, refer to the CLI commands detailed in the Tech. Doc. with the URL below.

Configure targets that will receive notifications

So, to ensure the appliance sends SNMP traps, ensure the following:

1. The SNMP system is configured, as recommended. Follow the guidance provided herein, to validate the configuration.
2. Define and enable the trap. Follow the guidance provided herein, to validate the configuration.
3. Configure the targets that will receive the notification.
4. Port 162 is opened, accordingly. refer to guidance in the Tech. doc. with URL: ISG Required Ports, Protocols, and Services

With the SNMP system configuration done, as guided, we expect the SNMP trap to be sent.

You may run a PCAP on the SSP appliance, for trap enabled for, say, CPU utilization, for certain metric value, say 70%. As this utilization is reached, and with all configurations correctly done, as guided, stop and collect the PCAP, and the customer may share the same with us, if further technical intervention would be required. If there are any specific errors, you may share the same with Technical Support as well.