- Print
- PDF
Legacy orchestrator can receive SNMP messages (about alarms and other events) from managed elements and send them to various destinations, typically Operations Support Systems (OSS).
Legacy orchestrator's support for handling messages via SNMP includes the following:
- SNMPv2 and SNMPv3 formats.
- Four SNMP destinations with IP addresses in IPv4 or IPv6 format.
- User-based Security Model (USM) users with different security profiles (SNMPv3 only).
Note: Legacy orchestrator also receives alarms from managed elements via permanent CLI sessions. For more information, see "Alarms".
Overview of SNMP Configuration on Legacy orchestrator
The following diagram gives an overview of the SNMP messaging you are aiming to set up on the network and how to configure it in Legacy orchestrator. The UDP ports shown are the default settings.
Configuring Legacy orchestrator to handle SNMP messages consists of these tasks:
- Configuring Legacy orchestrator to:
- Receive alarms from managed elements. See Configuring Legacy orchestrator to Receive SNMP Messages from Elements.
- Forward alarms to northbound destinations (up to four OSS). See "Configuring Legacy orchestrator to Send SNMP Messages Northbound".
- For SNMPv3, creating USM users in Legacy orchestrator that match USM users on the OSS systems.
- Configuring managed elements to send SNMP messages to Legacy orchestrator (or to other systems).
- By default, Legacy orchestrator is an SNMP trap receiver for all managed elements. You can check or change this setting. See "Using Legacy orchestrator as Default SNMP Receiver for All Elements".
- If necessary, you can set up a configuration job to configure one or more trap receivers on managed elements. See "Setting Up an SNMP Trap Configuration Job".
Locating the SNMP Configurations
SNMP is configured in the Admin ▶ SNMP page. The SNMP page includes two tabs: Configuration and USM Users.
Configuring Legacy orchestrator to Receive SNMP Messages from Elements
You configure Legacy orchestrator to receive messages from managed elements in the Configuration tab of the Admin ▶ SNMP page.
Note: Legacy orchestrator periodically resynchronizes the alarms from managed elements. Alarms will be received and displayed in real time via SNMP when Legacy orchestrator is configured as explained in this section.
To configure Legacy orchestrator to receive SNMP traps from elements
Select Admin ▶ SNMP to access the SNMP page (the Configuration tab is on top).
Enter values in the System name, Community string and UDP port fields. For more information on specific parameters, see the following table.
Click Apply.
SNMP configuration (Admin ▶ SNMP Configuration)
Parameter | Description |
---|---|
System name | Name that will be used as the source parameter in messages sent by Legacy orchestrator. Default system name: visionems. You can change it as required. |
Community string | The community string (like a password for SNMP) that will be used when Legacy orchestrator receives messages from managed elements. The value entered here on Legacy orchestrator must match the value used on all elements managed by Legacy orchestrator. See Note below the table. |
UDP port | UDP port on Legacy orchestrator for receiving SNMP messages from managed elements. The default UDP port for incoming messages is 1163. |
Note: You can test that you have entered the correct value for the community string by raising an alarm on an element. The alarm should be received and displayed in Legacy orchestrator within five seconds. If the alarm is not received, check the community string used on one of the managed elements and enter it in this field.
Using Legacy orchestrator as Default SNMP Receiver for All Elements
Legacy orchestrator is the default SNMP trap receiver for all its managed elements.
You can change or check this setting in the Admin ▶ SNMP page.
- Check or uncheck the box to enable or disable the use of Legacy orchestrator as the default trap receiver for all managed elements.
Configuring Legacy orchestrator to Send SNMP Messages Northbound
Legacy orchestrator can forward the alarms that it receives from managed elements or generates internally to four destination systems.
Typically, the destinations are Operations Support Systems (OSS).
You configure Legacy orchestrator to send messages to northbound systems in the four Trap receiver tabs at the bottom of the Configuration page.
Configuring Trap Receivers in the Admin ▶ SNMP (Configuration tab)
The messages sent to the destination system(s) include all events received from managed elements, as well as any loss of connectivity (LOC) events generated by Legacy orchestrator itself. If there are no communication issues between Legacy orchestrator and the destination systems, all events will have a corresponding clear event.
Outgoing SNMP messages can be sent as traps (unacknowledged) or as informs (require acknowledgement) in SNMP version 2c or version 3 format.
You can configure Legacy orchestrator to send keep-alive events to the destination systems periodically. Keep-alive events contain the following information:
- The name of the Legacy orchestrator system
- A counter for all events sent to the destination trap receiver since it was enabled.
Note: Restarting Legacy orchestrator or reconfiguring the trap receiver resets the counter to zero. - Counters for all active alarms on the network (Total, Critical, Major, Minor, Warning, LoC [Loss of Contact]).
Keep-alive events help detect a lost connection and events missed by the destination system. The destination system can compare its count of received events with the keep-alive event count. It can also compare its current alarm count with alarms reported by Legacy orchestrator. See the Legacy orchestrator Administration Guide for a description of the MIB that defines keep-alive events for SNMP.
To configure northbound destinations (trap receivers)
Access the page Administration ▶ SNMP. The Configuration page is displayed.
Complete the parameters for one or more destinations (Trap receiver 1 to Trap receiver 4), as required. For more information on specific parameters, see the following table.
Click Apply.
Administration ▶ Configuration (Trap receivers for northbound destinations)
Trap receiver 1 to Trap receiver 4 Parameters:
Receiver state:
Check this box to enable sending SNMP messages from Legacy orchestrator to the trap receiver on the destination system.
SNMP version:
Determines the SNMP version that Legacy orchestrator will use when sending messages to the destination system.
Set this to the SNMP version expected by the destination system.
Possible values:
- SNMPV2c
- SNMP3
Notification type:
Determines the type of notification that Legacy orchestrator will send to the destination system.
Set this to the type of SNMP message that the destination system is configured to receive.
Possible values:
- Notification: Select this option to send a trap (a message that does not require an acknowledgment).
- Inform: Select this option to send an inform (a message that requires an acknowledgment).
Community string:
This field is only active if SNMPv2c is selected as the SNMP version.
Community string that Legacy orchestrator uses when sending SNMP messages to the destination system.
The value entered here on Legacy orchestrator must match the value used on the destination system.
Keep-alive:
Check this box to send keep-alive messages to the destination system.
Note: In order for keep-alive messages to be sent, the Receiver state checkbox must also be checked.
USM user:
This field is only active if SNMPv3 is selected as the SNMP version.
Select a user that is defined on the destination system. A user account with the same credentials and security settings must also be defined in Legacy orchestrator.
The values available in this field are the users that have been defined in the USM Users tab. For more information on creating and managing USM users, see "Managing USM Users (SNMPv3)".
UDP port:
Establishes the port on the destination system to which Legacy orchestrator will send messages.
Set this to the UDP port that is set up on the destination system for receiving SNMP messages.
The default value is 162.
IP address:
IP address of the destination system.
Keep-alive frequency (s):
The frequency at which keep-alive messages are sent.
A value in seconds.
Keep-alive events are not affected by the volume of alarm messages sent.
Inform timeout (ms):
This field is only active if:
- SNMPv2 is selected as the SNMP version; and
- SNMP inform is selected as the Notification type.
The amount of time that Legacy orchestrator will wait for an acknowledgment from the destination system before attempting to resend the message.
Inform retries:
This field is only active if:
- SNMPv2 is selected as the SNMP version; and
- SNMP inform is selected as the Notification type.
The number of times that Legacy orchestrator will attempt to resend the message. If the message is not acknowledged after this number of retries, Legacy orchestrator will stop trying to send the message.
© 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