.svg?sv=2022-11-02&spr=https&st=2024-12-22T12%3A20%3A21Z&se=2024-12-22T12%3A30%3A21Z&sr=c&sp=r&sig=q3003zyRj6If9AVY%2FHPGxUiBCzIsNmZT%2FF5aJauXyXE%3D){kind=logo}
SNMP Agent Management
- 26 Sep 2024
- 5 Minutes to read
- Contributors
- Print
- PDF
SNMP Agent Management
- Updated on 26 Sep 2024
- 5 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This article provides information regarding an SNMP agent in relation to Legacy orchestrator and explains how to set up an SNMP trap configuration job that can be applied to all managed Provider Connectivity Assurance Sensors.
SNMP Agent on Legacy orchestrator
Legacy 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.
| Monitoring Point | MIB | Object / Table |
|---|---|---|
| CPU Load for all Processors | HOST-RESOURCES-MIB | hrProcessorTable |
| Temperature for the Processors | LM-SENSORS-MIB | lmTempSensorsTable |
| RAID Controller Status | LSI-AdapterSAS-MIB | physicalDriveTable virtualDriveTable |
| Power Supply Status | ACD-DESC-MIB | acdDescPwrEntry.10 192: Both Power Supplies normal 064: Power supply 1 abnormal 032: Power supply 2 abnormal 000: Both power supplies abnormal |
| Disk Utilization for the root (/) and data (/data) Partitions | HOST-RESOURCES-MIB UCD-SNMP-MIB | hrStorageTable dskTable |
| Disk I/O Load | UCD-DISKIO-MIB | diskIOTable |
| Network I/O | RFC-1213MIB | ifTable |
| Memory | UCD-SNMP-MIB | memory |
| Fan Speeds | LM-SENSORS-MIB | lmFanSensorsTable |
| Active Processes | HOST-RESOURCES_MIB | hrSWRunPath The following processes should be monitored for their presence: /opt/accedian/skylight/jdk/bin/java /opt/accedian/skylight/jdk/bin/java /usr/local/mysql/bin/mysqld |
Legacy orchestrator SNMP Alarm Forwarding
Legacy 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 Assurance Sensors.
MIB Structure
Legacy orchestrator events are defined in the following file:
ACD-EMS-MIB.mib
which is located in the following directory on the Legacy orchestrator appliance:
/opt/accedian/skylight/snmpmibs directory
The MIB file defines three events that can be sent by Legacy orchestrator:
alarmRaiseEvent, alarmClearEvent and keepAliveEvent.
The tables below describe the bindings for each of the three events.
alarmRaiseEvent
Represents a new alarm detected by Legacy orchestrator. This event contains the following bindings:
| Binding Name | Description |
|---|---|
| eventType | X.733 event type of the alarm |
| eventTime | Timestamp of the alarm, as defined in SNMPv2-TC |
| eventCount | Count of all events generated to this receiver by this system |
| managedElementName | DNS name of the network element, as displayed in Legacy orchestrator under the NE Name column of the Managed Elements tab. |
| managedObjectInstance | MOI. Unique identifier for the entity that caused the alarm on an element. Maps to the Source Entity field of alarms in the Legacy orchestrator web interface, prefixed by the managedElementName. For Legacy orchestrator alarms, the managedElementName is the Legacy orchestrator system name, as defined for the receiver. |
| probableCause | Probable Cause displayed in the Legacy orchestrator web interface. |
| perceivedSeverity | Displayed in the Severity field in the Legacy orchestrator web interface. |
| serviceAffecting | Indicates if this alarm has an impact on the capacity of the network to carry traffic. Displayed in the Service Affecting field in the Legacy orchestrator web interface. |
| additionalText | A text describing the alarm. Displayed in the Description field in the Legacy orchestrator web interface. |
| notificationId | Maps to the alarm number generated by the network element. Combined with MOI, this value uniquely identifies an alarm in the network. The same alarm reported by multiple Legacy orchestrator systems will have the same MOI and notificationId values. |
alarmClearEvent
Represents a clear alarm condition detected by Legacy orchestrator. This event contains the same bindings as the alarmRaiseEvent, with one difference; it contains correlatedNotificationId.
| Binding Name | Description |
|---|---|
| correlatedNotificationId | Maps to the alarm number, as generated by the network element. Combined with the managedObjectInstance, this value can be used to uniquely identify the alarm in the network for which this clear event is intended. The same clear reported by multiple Legacy orchestrator systems will have the same MOI and correlated notification ID values. |
keepAliveEvent
Represents a heartbeat from the Legacy orchestrator system. Keep alive events are always sent as notification messages. They contain the following bindings:
| Binding Name | Description |
|---|---|
| eventType | Will always be set to communications. |
| eventTime | Timestamp of the keep alive event. |
| eventCount | Count of all events generated to this receiver by this system. |
| totalAlarmCount | Indicates the total count of alarms in Legacy orchestrator at the time of the event. |
| criticalAlarmCount | Indicates the total count of critical alarms in Legacy orchestrator at the time of the event. |
| majorAlarmCount | Indicates the total count of major alarms in Legacy orchestrator at the time of the event. |
| minorAlarmCount | Indicates the total count of minor alarms in Legacy orchestrator at the time of the event. |
| warningAlarmCount | Indicates the total count of warning alarms in Legacy orchestrator at the time of the event. |
| locAlarmCount | Indicates the total count of loss of connectivity alarms in Legacy orchestrator at the time of the event. Note: These alarms are a subset of the warning alarms and are not counted in the totalAlarmCount value. |
Setting Up a Configuration Job for SNMP Alarm Handling
In order for Legacy orchestrator to receive alarms from Assurance Sensors in a timely fashion, the SNMP trap destinations of the Assurance Sensors should be configured to send their traps to Legacy orchestrator.
To use Legacy orchestrator as default SNMP trap receiver
By default, Legacy 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 Legacy orchestrator web user interface.
Access the SNMP trap receiver configuration in Admin ▶ SNMP ▶ Configuration page under the SNMP fault receiver configuration section:
Use Legacy orchestrator as default SNMP fault receiverEnsure you check the checkbox to enable the use of Legacy orchestrator as the default trap receiver for all managed elements.
Click Apply, then Close.
Use Legacy orchestrator as default SNMP fault receiverTo create a configuration job to set Legacy orchestrator as an SNMP trap receiver
If you choose to disable Legacy orchestrator as the default SNMP trap receiver, you can set up a configuration job to set up an SNMP trap receiver on all managed Assurance Sensors.
The image below shows how you can create a configuration job in Legacy orchestrator that can be applied to all Assurance Sensors that Legacy orchestrator is monitoring. The job will configure the Assurance Sensors to send their traps to Legacy orchestrator.
This setup is only a guideline. It assumes that the SNMP agents on your Assurance Sensors 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 Legacy orchestrator Features and User Material section.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks
Was this article helpful?