SNMP Agent Management

This article provides information regarding an SNMP agent in relation to Skylight orchestrator and explains how to set up an SNMP trap configuration job that can be applied to all managed Skylight elements.

SNMP Agent on Skylight orchestrator

Skylight orchestrator appliances have an active SNMP agent that can be used to retrieve statistics on the appliance itself.

The agent is configured to run on port 161 of the MGMT interface. The read community string for the agent is: accedian

The following table lists the monitoring points that can be retrieved from this interface. These monitoring points can be retrieved at a maximum frequency of five minutes. Polling at higher intervals may interfere with regular operations of the appliance.

Skylight orchestrator SNMP Alarm Forwarding

Skylight orchestrator can forward its raise and clear events as SNMP (v2 or v3) notifications or informs.

This section describes the structure of the MIB used in conjunction with these events.
It also explains how to set up an SNMP trap configuration job that can be applied to all managed Skylight elements.

MIB Structure

Skylight orchestrator events are defined in the following file:
ACD-EMS-MIB.mib
which is located in the following directory on the Skylight orchestrator appliance:
/opt/accedian/skylight/snmpmibs directory
The MIB file defines three events that can be sent by Skylight orchestrator:
alarmRaiseEvent, alarmClearEvent and keepAliveEvent.

The tables below describe the bindings for each of the three events.

alarmRaiseEvent

Represents a new alarm detected by Skylight orchestrator. This event contains the following bindings:

alarmClearEvent

Represents a clear alarm condition detected by Skylight orchestrator. This event contains the same bindings as the alarmRaiseEvent, with one difference; it contains correlatedNotificationId.

keepAliveEvent

Represents a heartbeat from the Skylight orchestrator system. Keep alive events are always sent as notification messages. They contain the following bindings:

Setting Up a Configuration Job for SNMP Alarm Handling

In order for Skylight orchestrator to receive alarms from Skylight elements in a timely fashion, the SNMP trap destinations of the Skylight elements should be configured to send their traps to Skylight orchestrator.

To use Skylight orchestrator as default SNMP trap receiver

By default, Skylight orchestrator is the default SNMP trap receiver for all its managed elements.

You can change or check this setting in the Alarm Management application in the Skylight orchestrator web user interface.

1. Access the SNMP trap receiver configuration in Admin ▶ SNMP ▶ Configuration page under the SNMP fault receiver configuration section:
   Use Skylight orchestrator as default SNMP fault receiver

2. Ensure you check the checkbox to enable the use of Skylight orchestrator as the default trap receiver for all managed elements.

3. Click Apply, then Close.

To create a configuration job to set Skylight orchestrator as an SNMP trap receiver

If you choose to disable Skylight orchestrator as the default SNMP trap receiver, you can set up a configuration job to set up an SNMP trap receiver on all managed Skylight elements.

The image below shows how you can create a configuration job in Skylight orchestrator that can be applied to all Skylight elements that Skylight orchestrator is monitoring. The job will configure the Skylight elements to send their traps to Skylight orchestrator.

This setup is only a guideline. It assumes that the SNMP agents on your Skylight elements are already enabled and that the V2C-1 slot is not used for other purposes. You should adapt it accordingly.

For detailed information on how to set up configuration jobs, see the Skylight orchestrator Features / User Material section.