Tellabs Proprietary SNMP MIB

Introduction

This App Note documents the Tellabs proprietary SNMP MIB (Management Information Base) used to report alarms and events via SNMP traps and notifications.

Document Number

      ENG-010677

Applies To

All Tellabs OLAN OLTS. The Tellabs OLAN SNMP interface supports monitoring, limited provisioning, polling performance statistics, and trap management. The SNMP versions supported are SNMPv1, SNMPv2c, and SNMPv3. This application note applies to the SNMP interface in FP28.0 and newer software versions.

The tlab1150NotifyMIB Module

The Tellabs OLAN Network Element (NE) interface supports the standard MIBs (Interface, RMON, and MIB II) used in monitoring, limited provisioning, and polling of performance statistics. The MIB files (zipped) can be downloaded from here.

Included in this archive is the Tellabs proprietary MIB definition file (TLAB1150-NOTIFY-MIB.txt). This file contains the module tlab1150NotifyMIB. This module was written using an adapted subset of OSI's Abstract Syntax Notation One (ASN.1). It defines a related collection of items (MIBs, objects, notifications, and textual-conventions, etc.) that, together, provide a framework used to report SNMP traps and notifications for alarms and events occurring at the OLT. This document covers only those items defined to handle SNMP traps for OLT alarms. You can review all the definitions in this module by reading the text file.

OID

• An OID is a sequence of integers that uniquely identifies a managed object by defining a path to that object through a tree-like structure called the OID tree. The OID for the tlab1150NotifyMIB module is shown below:
• iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).tellabs(1397).tellabsProducts(2). tlab1150(29).tlab1150NotifyMIB(2)
• --or--
• 1.3.6.1.4.1.1397.2.29.2

The OID is constructed from the OID tree as follows:

-- iso              OBJECT IDENTIFIER ::= { 1 }
-- org              OBJECT IDENTIFIER ::= { iso 3 }
-- dod              OBJECT IDENTIFIER ::= { org 6 }
-- internet         OBJECT IDENTIFIER ::= { dod 1 }
-- private          OBJECT IDENTIFIER ::= { internet 4 }
-- enterprises      OBJECT IDENTIFIER ::= { private 1 }
tellabs             OBJECT IDENTIFIER ::= { enterprises 1397 }
tellabsProducts     OBJECT IDENTIFIER ::= { tellabs 2 }
tlab1150            OBJECT IDENTIFIER ::= { tellabsProducts 29 }
tlab1150NotifyMIB   OBJECT IDENTIFIER ::= { tlab1150 2 }
Module Definitions

The tlab1150NotifyMIB module defines a set of related items (MIBs, objects, notifications, and textual-conventions, etc.) used to collect and report SNMP traps and notifications for events and alarms occurring at the Tellabs OLT. The following items are defined by the module.

Textual-Conventions

Textual conventions are the way datatypes are defined in SNMP. This definition provides constraints placed upon the interpretation of the data, describing the representation, interpretation and structure for values that may be stored by a MIB object. The following textual-conventions are defined by the tlab1150NotifyMIB module:

indeterminate (0)      
critical (1)      -- CR
major (2)         -- MJ
minor (3)         -- MN
cleared (4)       -- CL
notAlarmed (5)    -- NA
notReported (6)   -- NR
ServiceAffecting

unknown  (0)                
serviceAffecting (1)     -- SA
notServiceAffecting (2)  -- NSA

Objects

The tlab1150NotifyMIB module defines objects used for SNMP. These objects can be variable objects used to hold a single value, notification objects that aggregate data for SNMP transmission, and separate MIBs used to categorize SNMP data. The objects defined by the tlab1150NotifyMIB module are summarized in the following table:

Alarms

Once configured, the OLT reports alarms using SNMP traps and notifications. For details on setting up SNMP, see the App Note:

SNMP on Tellabs OLTs.

The following table lists all OLT alarms reported by SNMP. It shows the object names and values in the trap/notification sent for each alarm. The description column explains what the alarm means and when it is set and cleared. The legend maps the name of each attribute to its data type and OID.

Example

The following screen-shot illustrates a capture of an SNMP message sent from a tellabs OLT. Pay attention to the OIDs and Values. Looking at the data (OIDs and values) we can tell that this message is an SNMP trap showing a clear of an ONT communications failure alarm.

The values show us the following:

• The version field shows us that the SNMP version being used is v2c.
• The community field shows that the community string being used is "Tellabs-1".
• The message is a trap, not a notification. Firstly, because this is a UDP message and notifications are sent using TCP. Secondly because the data field clearly tells us in the value of 7 (snmpV2-trap).
• The first object in the message is a sysUpTime. It holds the TimeTicks value of 120291720. The sysUpTime object is not defined by the Tellabs MIB. It is an object defined in a standard SNMP MIB that has the OID: {iso(1).identified-organization(3).dod(6).internet(1).mgmt(2).mib-2(1).system(1).sysUpTime(3)} or (1.3.6.1.2.1.1.3). According to the description in the defining MIB module, this value is: "The time (in hundredths of a second) since the network management portion of the system was last re-initialized." This tells us that the system has been up for approximately 118 days.
• The second object in the message is an snmpTrapOID. It holds the value "1.3.6.1.4.1.1397.2.29.2.0" which is a string representation of a tlab1150Notifications OID. This object is not defined by the Tellabs MIB. It is an object defined in a standard SNMP MIB that has the OID: iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) snmpMIB(1) snmpMIBObjects(1) snmpTrap(4) snmpTrapOID(1) or (1.3.6.1.6.3.1.1.4.1). According to the description in the defining MIB module: "This variable occurs as the second varbind in every SNMPv2-Trap-PDU and InformRequest-PDU."
• The tlab1150NotificationCode object (OID = 1.3.6.1.4.1.1397.2.29.2.1.2.0) has a value of "4" (cleared)
• The tlab1150aid object (OID = 1.3.6.1.4.1.1397.2.29.2.1.1.0) has an AID value of "MDS1-1-1-6" (ONT AID)
• The tlab1150conditionType (OID = 1.3.6.1.4.1.1397.2.29.2.1.3.0) has a value of "CONTCOM" (Communications Failure)
• The tlab1150serviceAffecting object (OID: 1.3.6.1.4.1.1397.2.29.2.1.4.0) has a value of "1" (serviceAffecting)