.svg?sv=2022-11-02&spr=https&st=2024-11-01T00%3A09%3A20Z&se=2024-11-01T00%3A19%3A20Z&sr=c&sp=r&sig=ExyNn2DzK0T3c9otHJcKVPz9QayAGT71BadsdNAVML8%3D){kind=logo}
Managing the SNMP Agent
- 25 Sep 2024
- 5 Minutes to read
- Contributors
- Print
- PDF
Managing the SNMP Agent
- Updated on 25 Sep 2024
- 5 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
You can configure an SNMP agent so that it provides an interface to an SNMP-based management system (for get and set commands). The SNMP agent also allows the Cisco Provider Connectivity Assurance Sensor Control to send SNMP traps to a receiver. The receiver is usually used to monitor the conditions of many units.
Enabling the SNMP Agent
The SNMP Agent is used to generate SNMP traps and to provide OID information. Use this page to configure how the SNMP agent is enabled.
Some SNMP queries can require an extended period of time to execute fully, due to the large quantity of data to provide. If your SNMP MIB browser times out while walking through the MIB tables, consider increasing the timeout value to at least 10 seconds. Extending the timeout value will allow the SNMP Agent to serve the request instead of timing out and retrying until the configured number of retries is exhausted. It will reduce the amount of SNMP traffic going through your network.
To enable the SNMP agent
Access the page System ▶ Agent ▶ SNMP.
Complete the required fields, then click Apply.
For more information on specific parameters, refer to the following table.
SNMP Agent (System ▶ Agent ▶ SNMP)
| Parameter | Description |
|---|---|
| Enable agent | Enables the Sensor Control’s SNMP agent. |
| Use host name as system name | Uses host's name as system-name. |
| SNMP system name | The name to identify the Sensor Control. By convention, this is the unit's fully-qualified domain name. |
| Contact information | Contact information for the Sensor Control (typically an email address). |
| System location | Physical location of the host of the Sensor Control. |
| Agent UDP port | UDP port that the SNMP agent uses for all interfaces. Note: Changing this value restarts the SNMP agent. |
| Read-Only community | The community string to control read-only access to the Sensor Control. |
| Read-Write community | The community string used to control read/write access to the Sensor Control. |
| Enable authentication trap generation | Enables the Sensor Control to generate a trap when authentication of the agent fails. |
| Enable link trap generation | Enables trap generation when the link status changes. Maps to generic traps 2 (1.3.6.1.6.3.1.1.5.3 linkDown) and 3 (1.3.6.1.6.3.1.1.5.4 linkUp). |
Setting Up the SNMP Trap Receivers
You can configure the Sensor Control to send SNMP traps to different notification receivers. The notification receiver is usually used to monitor conditions of many units.
Note: The SNMP agent must be enabled before you can configure and use the SNMP Trap Receiver.
The Sensor Control can be configured to send SNMP v1 traps to one or two receivers, and to send SNMP v2c traps to up to ten receivers.
Using the Auto trap receiver, you can also configure the Sensor Control to send SNMP traps (v1 or v2c) to other compatible notification receivers. With the Auto trap receiver, the IP address of the compatible notification receiver is automatically updated when the receiver connects to the Sensor Control and sends the appropriate CLI commands. Refer to the CLI Command Guide for information on the CLI command.
To configure the SNMP trap receiver information
Access the page System ▶ Agent ▶ Traps.
A list of all current SNMP Trap receiver information is displayed.
Click the ID of the trap receiver you want to edit.
Complete the required fields, then click Apply.
For more information on specific parameters, refer to the following table.
Trap Receivers (System ▶ Agent ▶ Traps)
| Parameter | Description |
|---|---|
| Type | The type of SNMP Trap Receiver may be either SNMPv1 or SNMPv2c. |
| ID | ID number of the trap receiver. Note: The Auto trap receiver is configurable via the CLI only. |
| State | The state of this SNMP trap: Enabled or Disabled. |
| Enable trap | Enables the Sensor Control to send SNMPv1 or SNMPv2c traps to a specified notification receiver. |
| Notification receiver host name | The IP address or host name of the device that receives SNMP traps and/or notifications. The Sensor Control sends a Cold Start trap when starting up. |
| Community string | The community string required to send traps to the notification receiver. |
| Host UDP port | The UDP port used by the Sensor Control to send traps to the notification receiver. The widely used SNMP trap port 162 is the default port. |
Enabling SNMP For Retrieving Statistics
This section describes how to enable the SNMP agent on Sensor Control to retrieve the data through a third-party Network Management Software (NMS) application. Accedian Networks provides private Management Information Bases (MIBs) for integration into an NMS to retrieve bandwidth policing data, statistics per flow, SFP digital diagnostics information, alarms, a full description of the firmware version, port information, and also data gathered by the Performance Assurance Agent (PAA).
Statistics per flow are results based on set filters such as VLAN ID, Priority, DSCP, MAC address, IP address, and Ethertype. The PAA will provide the latency, jitter, and packet loss of the network. These precise measurements are gathered live from the network without affecting the throughput.
The private MIBs are:
- ACD-ALARM-MIB
- ACD-CFM-MIB
- ACD-DESC-MIB
- ACD-FILTER-MIB
- ACD-PORT-MIB
- ACD-RDEV-MIB
- ACD-TID-MIB
To enable SNMP for retrieving statistics
Retrieve the Accedian private MIB files.
Log in to the unit using the management Web interface.
Go to System ▶ Agent ▶ SNMP.
- Enter the parameters, and then click Apply.
Note: Be sure to select Enable agent and enter "public" in Read-only community.
- Go to System ▶ Agent ▶ Traps, and then click SNMPv1 ID of 1.
Enter the parameters, and then click Apply.
Use the IP address of the host for the MIB browser application (NMS) in Notification receiver.
Note: Be sure to enter "public" in Community string.Open the MIB browser application.
For the Traps section, you will notice an alarm notification saying that there was a coldStart. This is normal.
Access the iso/org/dod/internet/private/enterprise/accedianMIB page and browse through.
Connect an RJ-45 cable to the Network port of the unit.
You will see an SNMP Trap Notification saying Generic: linkUp after the soaking time for an alarm has been reached.
Unplug the cable. A Generic: linkDown notification appears after the soaking time for an alarm is reached.
© 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?