SNMP On Tellabs OLTs

Introduction

Document Number

ENG-010622

Purpose

This document will define how to configure SNMP on Tellabs ONTs. It will cover how to enable the SNMP agent, set up credentials, and trap listeners.

Applies To

All Tellabs OLAN OLTS.

OLAN SNMP MIB Support

SNMP Support on Tellabs OLTs

The Tellabs OLT supports a standard SNMPv2/SNMPv3 interface at the OLT. This interface provides surveillance of the state of the UNI and NNI ports of the system. It also supports the emitting of traps for all events and alarms in the system. This allows using standard SNMP tools to monitor and get surveillance of the ports. Counters are also available at SNMP.

Tellabs is interoperable with all SNMP tools like Solar Winds, HP Openview, NNMi, etc. SNMP is also used by many of the Policy Engines like Cisco ISE, Forescout CounterAct, and Aruba ClearPass.

Tellabs is primarily managed by the EMS and does not give write access to many of the attributes within the SNMP MIB. For the most part the writable attributes are limited to port Admin States to allow remotely enabling and disabling ports.

Configuring SNMP on Tellabs OLTs

This section will define the steps to configure Tellabs OLTs to allow SNMP access.SNMP is disabled by default and must be enabled, and trap hosts configured for proper operation.

To access the SNMP screen in the Panorama GUI and configure SNMP, go to the following menu.

Right click on the corresponding OLT in the common tree->Properties->SNMP Tab.

The Admin can be set to any value desired and defaults to the IP address of the OLT.

• Add SNMP User: This button allows the creation of users that are used when SNMPv3 is utilized that allow SNMPv3 user authentication of the incoming SNMP requests.
• SNMPv3 Engine ID / Admin String: The SNMP Engine ID is a unique identifier for the SNMP agent and must be unique within a domain. The type is an Admin string and is by default the OLT IP address. It can be changed to any value desired when using the Custom option.
• Enable SNMP Agent: If the Enable SNMP Agent button is not greyed out, click it to enable the agent, no requests will be honored or traps sent unless the Agent is enabled.
• TrapHostName: Give a meaningful name to the TrapHost to help identify it. This is the name of hosts which you wish to send traps to.
• Parameter: Add a Trap Parameter to identify the user to be used in Traps for V3. This will be shown in the next screen.

Go to SNMP User Administration and add a used to allow access to the SNMP agent. The SNMP User MUST be created prior to the SNMP Parameter needed for Traps as the user is a part of the trap parameter.

Press Add to Create a new SNMP User.

• Name: Enter the User Name to be used in SNMPv3 authentication. Typically, this user is used for both SNMP GET/SETs and Traps.
• Security Model: Security model should be USM for SNMPv3.
• Community String: This is only used for SNMPv2 and will not be editable if USM is selected. USM is the SNMv3 User Security Model.
• Security Level: AUTH_PRIV is used for SNMPv3

Note: Additional SNMPv3 hash above SHA1 and crypto options above AES128 are only available in EMS SR31.4.0.AA and OLT SR31.4_604101 and above.  Cisco variants can only be configured from the CLI at this time.

Authen Protocol: The OLT supports the following auth protocols:

• HMAC-SHA1-96 (Equates to SHA-1 on most systems).
• HMAC-MD5-96 (Should not be used, hash is very weak)
• SHA-224
• SHA-256
• SHA-384
• SHA-512

Authen Password: Enter the same password used in setting up ForeScout.

Priv Protocol: The following privacy protocols are supported:

• CBC-DES - Not recommended, weak encryption
• AES-128 industry standard
• AES-192 industry standard
• AES-256 industry standard 
• AES-192-CISCO
• AES-256-CISCO
• Priv Password: Should match the privacy password on ForeScout.
• Role: Select a Role from the drop-down list to agree with the level of access you want to grant to the SNMP user. An Admin user role will be needed to enable write access to the system.

If not already created, press SNMP Parameter to create the Trap User.

• Name: Give a meaningful name to the Trap User.
• SNMP Model: V2 or V3 is supported, V3 is recommended and shown in this example.
• SNMP User: A previously created SNMP user should be selected.
• Storage Type: NONVOLATILE.

You can now Add a destination to the list of destination trap hosts.

If it has not already been enabled, Enable the SNMP agent by pushing the corresponding button.

Push Apply to apply all the settings to the OLT.

Example Solar Winds SNMPv3 Setup

The following example configuration shows an example configuration that will work with the Solar Winds when configured as shown above.

1. Set the SNMPv3 Credentials as agreed with your local administrator.
2. Set the SNMPv3 Authentication Method to match that chosen on the OLT.   Note HMAC-SHA-96 on the OLT equates to SHA1 on the Solar Winds configuration.
3. Set the SNMP Privacy / Encryption to match what is configured on the OLT and set the password as appropriate.
4. Duplicate the settings in the Read / Write SNMPv3 Credentials.
5. Once setup and connectivity is present, Solar Winds should start doing surveillance and receiving traps from the OLT.

Credentials in SNMPv3 Traps

The OLT will include the proper SNMPv3 credentials in SNMPv3 traps sent to trap receivers. Many trap receivers ignore them and receive the trap whether or not the credentials are present. Tellabs OLT works with either type of trap receiver.

Summary

The steps to configure SNMP are outlined above. If any issues are encountered during configuration, feel free to contact Technical Assistance at the contact info listed below. Also there is a separate document detailing the SNMP MIBs supported and a zip file with all the MIB files.

Video