1. Alarms and Maintenance Guide
  2. LSMS Overview

2 LSMS Overview

This chapter provides an overview of LSMS system architecture, proactive termination and re-establishment of LSMS connectivity, hardware and software design features that provide high availability of the LSMS, and third-party and Oracle software components used by the LSMS.

Introduction

The LSMS is a secure and reliable Local Number Portability (LNP) system that enables customers to administer their LNP data in a central place. The LSMS provides the following functions:

  • Receives LNP data from Number Portability Administration Centers (NPACs)

  • Enables customers to enter locally provisioned data such as Override Global Title Translation (OGTT) data

  • Forwards all NPAC and locally provisioned data to up to eight EAGLE systems

For more information about the LNP functions provided by the LSMS, refer to Database Administrator's Guide and LNP Database Synchronization User's Guide.

This chapter provides an overview of:

  • LSMS system architecture

  • Proactive termination and re-establishment of LSMS connectivity

  • Hardware and software design features that provide high availability of the LSMS

  • Third-party and Oracle software components used by the LSMS

For additional information about the hardware, refer to Application B Card Hardware and Installation Guide.

LSMS Connectivity

The main function of the LSMS is to provision LNP data through the ELAP to the EAGLE. To perform this task, the LSMS maintains active connections with one or more NPAC region servers and one or more EAGLE nodes. While it is the goal of the LSMS to maintain active connections to each NPAC server and EAGLE node as nearly full-time as possible, the more important goal is to reliably forward the data from the NPAC to the EAGLE as quickly as possible. To that end, a number of protective problem detection and recovery mechanisms are built into the LSMS design. Several of these protections actually allow for the termination of application connectivity in order to gracefully restore full connectivity and guarantee total recovery of data.

The performance of the LSMS is based on network connectivity that meets a Quality of Service expectation. The expectations by Oracle for network Quality of Service are as follows:

  • Network RTT latency of <= 70ms and network loss due to network error <= 0.1%

OR

  • Network RTT latency of <= 120ms and network loss due to network error <= 0.01%

In the following situations, the LSMS proactively terminates and re-establishes application connectivity with the NPAC and EAGLE nodes:

  • If the LSMS detects network level connectivity failures with either the NPAC or EAGLE, the respective LSMS processes terminate the socket level connection and then reconnect. This disconnect and reconnect occurs in a matter of seconds. Built in resynchronization mechanisms ensure data recovery. The data transmission is delayed by the time required to disconnect and reconnect, but the execution of the recovery procedures prevents data loss.
  • If the LSMS detects critical internal errors that would cause system outages, the LSMS processes are designed to terminate and allow the LSMS sentry process to restart them. This is only done for significant internal errors that jeopardize internal LSMS communications. Once the sentry process restarts the LSMS processes, resynchronization provides full data recovery.

LSMS Hardware Overview

Table 2-1 provides an overview of LSMS hardware.

Table 2-1 LSMS Hardware Components

Qty Hardware Item For more detail, see:

2

E5-APP-B-02 cards (P/N 870-3096-02), one for each LSMS server; each card includes the following components:

  • Dual Core 2.66 Gigahertz (GHz) 64-bit processor
  • Active/Trial BIOS architecture
  • 1333 Megahertz (MHz) processor front side bus speed
  • 8 Gigabyte (GB) DDR2 DRAM
  • Light Emitting Diode (LED) status display
  • Hardware monitors that read and report:
    • Supply and core voltages
    • Fan alarm inputs
    • Ambient and processor temperatures
  • Two drive modules (Field-replaceable units (FRUs))
  • Four serial interfaces
  • One USB port
  • Fan alarm
  • Four 1 Gigabit (Gb) Ethernet ports

LSMS runs on E5-APP-B cards with Oracle Communications Tekelec Platform (TPD) 7 (64 bit).

Application B Card Hardware and Installation Guide

1

E5-APP-B-02 card (P/N 870-3096-02) for Oracle Communications LSMS Network Attached Storage (NAS)

NAS runs on an E5-APP-B card with TPD 7 (64 bit).

NAS Overview

Table 2-2 LSMS Hardware Components

Qty Hardware Item For more detail, see: To replace, see:

2

Tekelec 1100 AS main unit; each unit has the following cards added during manufacturing:

  • One quad-port gigabit Ethernet Peripheral Component Interconnect (PCI) cards

  • Two dual-port gigabit Ethernet PCI cards

  • One Out-of-Band-Management (OOBM) PCI card that contains:

    • One serial port

    • One modem interface

    • One Ethernet port

    • One interface for alarm relays

Each Tekelec 1100 AS main unit has 8 gigabytes of Random Access Memory (RAM) installed and available.

Tekelec 1100 Application Server Hardware Manual

Tekelec 1100 Application Server Hardware Manual

1

Network Attached Storage (NAS)

1

lsms-overview1.html#GUID-B23FC904-D733-4BD7-B8B9-28CAA1D2A065__35904

Contact the Tekelec Customer Care Center.

1

Breaker panel (for DC version only)

Tekelec 1100 Application Server Hardware Manual

2

Power Distribution Units (for AC version only)

Tekelec 1100 Application Server Hardware Manual

Tekelec 1100 Application Server Hardware Manual

E5-APP-B Card LEDs

This section describes the LEDs found on the front face of the E5-APP-B card.

Figure 2-1 shows the E5-APP-B card LEDs on the front panel

Figure 2-1 E5-APP-B Card LEDs


img/card_overview-2.jpg

The following light-emitting diode (LED) status indicators can be found on the E5-APP-B card:

  • One Server Status indicator (A)
  • Four E-Net link and Active LED status indicators (B)
  • Two drive module status indicators (C)
  • One Card Eject status indicator (D)

Table 2-3 E5-APP-B LED Table

LED Name HW/SW Controlled Description
Server Status SW

Solid Red - Server is halted

Flashing Red - Server is booting

Solid Amber - TKLC configuration beginning

Solid Green - TPD loaded/operational state

Flashing Green - Server is shutting down
Drive 1 Status SW/HW

HW: Flashing Green - Drive activity

SW: Flashing Red - Impending drive removal

SW: Steady red - Drive ready for removal
Drive 2 Status SW/HW

HW: Flashing Green - Drive activity

SW: Flashing Red - Impending drive removal

SW: Steady red - Drive ready for removal
Eject Status SW

Red - Card ready for extraction

Flashing Red - Card preparing for extraction

Off - Card is not ready for extraction
Act LED A1 HW Flashing Green - Link Activity
Act LED A2 HW Flashing Green - Link Activity
Act LED B1 HW Flashing Green - Link Activity
Act LED B2 HW Flashing Green - Link Activity
Link LED A1 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed
Link LED A2 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed
Link LED B1 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed
Link LED B2 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed

NAS Overview

LSMS uses NAS on E5-APP-B for network backup of the system logs, application logs, and databases.

  • Hardware Modifications

    The E5-APP-B NAS uses a two-drive RAID configuration to save the LSMS logs and database. The E5-APP-B NAS uses the TPD 7 OS.

  • Keys Exchange

    The key exchange feature provided by TPD is used to exchange keys between LSMS and NAS. This feature facilitates user access to NAS from LSMS and to LSMS from NAS without providing a user ID and password.

  • Backup

    Both manual and automatic backup are supported. The LSMS interface is used to initiate the manual backup. The automatic backup is scheduled at 23:55 and cannot be rescheduled. A maximum of 4 backups are retained on NAS.

  • Class Type for Storage Data

    The class type of data must be known before storing the data. The class type can be defined specific to the server being backed up, or it can be files/data to be backed up on different servers based on the state of the system. For example, 'database' can be used to back up the database regardless of which server is performing the back up. The class types available are:

    • logs
    • DB
    • lsmspri
    • lsmssec
    • logs_lsmspri
    • logs_lsmssec
  • Restore

    You have the option to restore the backups stored on NAS to LSMS. The restore operation is performed on the LSMS server.

  • Alarms

    The NAS sends SNMP traps to LSMS, which in turn raises an alarm on LSMS. Multiple alarms can be raised simultaneously, which are triggered upon failure of a service. The NAS monitors two services:

    • Free space

      The free space service monitors the available space on a mounted device (/Volumes), and sends an alert when the free space is less than 5%.

    • RAID

      The RAID service monitors RAID set degradation and rebuilds.

    An alarm is cleared when a service makes the state transition from failure to success, if a corresponding alarm was previously sent.

  • Login

    After configuring NAS with LSMS, you can log into it by using the ssh backupserver command or the minicom nas command from the LSMS command line interface.

LSMS Software Overview

Figure 2-2 shows the layered organization of third party and Oracle application software used in the LSMS system. For more information about the LSMS applications, see LSMS Applications.

Figure 2-2 Software Allocation on the LSMS Platform


img/c_lsms_software_overview_mm-fig1.jpg

Following are descriptions of the various software elements by layer.

Operating System Layer

The following elements appear in the Operating System Layer.

Oracle Communications Tekelec Platform (TPD)

TPD is the operating system used for LSMS on E5-APP-B. The TPD software is installed on one internal disk drive and mirrored to a second internal disk for each server.

Redundant Array on Inexpensive Disks (RAID)

The TPD uses Linux RAID for monitoring disks and recovery from disk problems. RAID provides the following benefits:

  • Redundancy

  • Recoverability from hard-disk crashes

Base Platform Software

Following are the elements of the base platform software.

OSI Stack

This package implements the OSI protocol to allow communications between the LSMS and the NPACs.

LSMS HA

LSMS High Availability (HA) is software for a two-node cluster that provides automated switchover from an active server to a standby server when a server or monitored application experiences a failure. In the LSMS, the two servers are peers: either server can act as the active server (although only one server at a time can be the active server). When either automatic or manual switchover causes the standby server to become the active server, it can continue to be the active server until another switchover is needed.

Note:

After switchover, the state of the previously active server is UNINITIALIZED "INHIBITED". As soon as possible, you need to perform the procedure described in Starting a Server to return the state of that server to STANDBY so that it is available when switchover is needed again.

Support/Base Utilities Components

The following elements make up the Support/Base software utilities.

Apache

The Apache process (httpd) is a Web server. When the optional IP User Interface feature is enabled, theThe Apache process serves the GUI based on Java™ 1.7 technology to client browsers.

MySQL

The MySQL 5.6.31 database was selected for the LNP database to store all the LNP and service provider data. This database consists of a runtime application programming interface (API) and data files. The data files are organized as follows:

  • One database that stores locally provisioned data

  • One database for each supported NPAC region

  • A resynchronization database that is used for automatic resynchronizations with network elements; this database can store up to one million data objects

Whenever the two LSMS servers are in active/standby mode, all databases are replicated between the two servers, with the active server acting as the master and the standby server acting as the slave.

SSH/SSL

SSH/SSL is a robust, commercial-grade, and full-featured toolkit that implements the security and network encryption.

SSH/SSL provides secure data transmission through encryption keys. Encryption is required for the connection between the NPAC and the LSMS. The LSMS has a key for each NPAC that it services. For more information about keys, refer to the Configuration Guide.

LSMS Applications

The LSMS applications work together as shown below.

Figure 2-3 LSMS Applications


img/c_lsms_applications_mm-fig1.jpg

The LSMS applications provide the following functions:

Local Services Manager

The Local Services Manager (lsman) is responsible for providing an interface between the Local GUI and the web-based GUIs and other LSMS processes. It acts as a gateway to the GUIs for processes (EBDA, Report Manager, and NPAC agents) that do not have direct access to the GUI, using Extensible Markup Language (XML) messages to communicate.

The Local Services Manager also manages how many users can be running simultaneously. The maximum number of users allowed on the LSMS system is eight. A user is defined as a GUI session.

The Support for Additional Users optional feature enables you to have a maximum of 25 simultaneous users.

If you attempt to exceed the maximum allowable number of GUI sessions, an error message displays. For example, if you do not have the optional Support for Additional Users feature enabled and you start LSMS GUI sessions on eight different terminals and then attempted to start a ninth GUI session on another terminal, the following error message displays stating that the maximum number of users had been reached: 


Maximum number of users reached.

Local Data Manager

The Local Data Manager (supman) is responsible for:

  • Provisioning of LSMS configuration information and local data

  • Communicating with the GUIs using XML messages

  • Broadcasts all locally provisioned LNP data updates using a Reliable Multicast Transport Protocol (RMTP II) multicast mechanism on a single channel

  • Updating the resynchronization database with locally provisioned data to facilitate automatic resynchronization with Element Management Systems (EMSs) at the supported network elements

NPAC Agents

The NPAC Agent application (npacagent) is responsible for:

  • Connecting with a single NPAC system using the Q.3 protocol and providing all functions required by published NPAC standards

  • Broadcasting all its updates using the RMTP II multicast mechanism over one broadcast channel

  • Communicating with the GUIs through the Local Services Manager

One instance of the npacagent process exists for each enabled NPAC region.

EAGLE Agents

The EAGLE Agent application (eagleagent) is responsible for:

  • Subscribing to the broadcast channels to receive all NPAC and local data updates

  • Connecting with a single EAGLE node using the High Speed Operations Protocol (HSOP) and forwarding LNP updates to the EAGLE

  • Filtering LNP data based on the provisioned filter information before forwarding it to the EAGLE (for more information, refer to the Database Administrator's Guide)

  • Performing automatic resynchronization with an EAGLE node upon connection establishment (for more information, refer to the LNP Database Synchronization User's Guide)

One instance of the eagleagent process exists for each supported EAGLE node.

RMTPManager

The RMTPManager (rmtpmgr) is responsible for facilitating the reliable multicast mechanism that allows LNP data updates to reach every EAGLE agent. It acts as a top node in an RMTP broadcast tree. A maximum of 9 broadcast channels exists (up to 8 channels for NPAC agents and 1 for the Local Data Manager).

RMTPAgent

The RMTPAgent (rmtpagent) is responsible for keeping the broadcast mechanism flowing even when no EAGLE agents are running. The RMTPAgent subscribes to all (up to 9) broadcast channels.

Local GUI

The Local GUI application is responsible for providing a graphical user interface to allow operation of the LSMS by users who are logged into the LSMS administration console or a network-connected workstation through which they have made a telnet connection to the LSMS. Multiple instances of the Local GUI can exist.

Web-Based GUI

The Web-based GUI application runs outside of the LSMS system on a client platform. It provides an IP-based GUI to operate the LSMS and has the same appearance and functionality as the local GUI. Multiple instances of the Web-based GUI can exist.

Report Manager

The Report Manager (reportman) is responsible for producing reports on demand. It can produce up to 10 reports simultaneously.

EBDA

The Enhanced Bulk Download and Audit process (ebda) is responsible for providing the capability of performing audits, reconciles, bulk loads and user-initiated resynchronizations of an EAGLE LNP database. Multiple instances of the ebda process can exist for different EAGLE nodes.

Sentry

The Sentry process (sentryd) monitors other software processes and attempts to restart them automatically in certain failure conditions. For more information about the Sentry application, see “Automatically Restarting Software Processes”.

Surveillance

The LSMS Surveillance process (survMon) continually surveys the LSMS hardware and software and sends surveillance notifications to the server’s serial port. Users who want to display surveillance notifications on an administration console can connect Serial Port 3 to the administration console (see Configuring a Customer-Provided Administration Console).

Surveillance is also responsible for monitoring and restarting the sentryd and Service Assurance processes. For more information, see “Understanding the Surveillance Feature”.

Service Assurance

The Service Assurance feature allows an external system to access subscription version data from the LNP databases in the LSMS. For more information, see “Understanding the Service Assurance Feature”.

SNMPAgent

The SNMPAgent (lsmsSNMPAgent) is a process running on the LSMS platform that supports only the SNMPv1 and SNMPv3 trap operation. This process receives (through UDP Linux sockets) LSMS notification events from other LSMS processes and formats these events into trap requests. For more information, see “Understanding the SNMP Agent Process”.

Logger

The Logger process (lsmslogd) is responsible for:

  • Receiving log entries from application processes

  • Storing them in appropriate log files

  • Starting new log files every midnight

Overview of High Availability

To provide a high likelihood of the LSMS being able to function (high availability), the LSMS is implemented with hardware redundancies and with software that monitors hardware status and allows the LSMS functions to be run on either server (but not both at once).

Hardware Redundancies

Each server contains two internal mirrored disks.

The LSMS is implemented with a pair of redundant servers and the following redundant heartbeat connections between them:

  • A bonded pair of Ethernet connections for heartbeats

  • A serial cable connection for heartbeats

    Figure 2-4 LSMS Servers Connected with Heartbeat Links


    img/c_hardware_redundancies_mm-fig1.jpg

Redundant Servers

Two servers, one active and one standby, provide redundancy in processing. If the active server fails, the LSMS can run on the standby server.

Changing from one server to another is called switchover. The server on which the LSMS is running at a given time is called the active server and the other server is called the standby server.

For some types of failure on the active server, the LSMS automatically attempts to switch over. You can also manually switch over at any time. For more information about switching over, see the following:

Redundant Data

The LSMS is designed with the following data redundancies:

  • Each server contains mirrored disks. If both sides of the mirrors fail on the active server, the LSMS automatically attempts to switch over to the standby server. For more information, see Automatic Switchover Due to Hardware-Related Failure.

  • The database on the active server is replicated by the standby server.

Redundant Heartbeats

The servers use heartbeats to monitor each other. The servers are connected by a pair of redundant Ethernet connections and a serial connection. As long as each server is functioning, it sends its heartbeat to the other server over these connections. These two Ethernet connections are implemented on separate Ethernet cards, so that the failure of one Ethernet card does not prevent heartbeats from being sent.

The heartbeats are monitored by the Surveillance feature. If a heartbeat cannot be detected, one of the following notifications is posted:


LSMS4015|14:58 Jun 22, 2000|xxxxxxx|Notify:Sys Admin - Heartbeat 1 failure


LSMS4016|14:58 Jun 22, 2000|xxxxxxx|Notify:Sys Admin - Heartbeat 2 failure

Software Availability Design

The following LSMS software design features enhance the availability of the LSMS:

  • The LSMS HA utility monitors the states of both servers, detects failure conditions, and automatically switches over for certain failures on the active server. For more information, see Managing Server States

  • The Surveillance feature monitors critical processes and interfaces and posts notifications. For more information, see “Understanding the Surveillance Feature”.

  • The sentryd feature detects certain application failures and automatically attempts to restart the failed applications. Full functionality of this feature requires that the Surveillance feature be enabled. For more information about sentryd, see Restarting Software Processes

  • The LSMS provides the following automatic attempts to reassociate and resynchronize after outages between NPACs and the LSMS or between the LSMS and network elements (when automatic recovery is not possible, notifications are posted, and operator-initiated recovery procedures are documented as indicated):

    • Automatic reassociation with an NPAC after some association outages (for operator-initiated recovery procedures, refer to the Configuration Guide)

    • Automatic resynchronization of NPAC and LSMS data after reassociation (when automatic resynchronization is not possible, notifications are posted, and operator-initiated recovery procedures are documented in “Resynchronizing After an Outage Between an NPAC and the LSMS”)

    • Automatic resynchronization of the LSMS and network element data after outage (when automatic recovery is not possible, notifications are posted, and operator-initiated recovery procedures are documented in the LNP Database Synchronization User's Guide)

Enhancing High Availability with a Shadow LSMS

To further enhance the availability of LSMS functions, you can choose to implement a shadow LSMS, where a shadow LSMS is an entire LSMS (with its own service provider ID) located in a separate geographical location from the main LSMS. Having a shadow LSMS available reduces the time needed to restore service in situations of severe error or disaster, such as fire or flood. The following types of shadow strategies are available:

  • Active shadow—a shadow LSMS that is connected to NPACs

  • Inactive shadow—a shadow LSMS exists but is not connected to NPACs

For more information about a shadow LSMS, and recovery procedures for each strategy, see Recovering from Site Failures. This chapter also describes the procedure for restoring a main LSMS after a site failure when no shadow is available.

Understanding the Surveillance Feature

On each server, the LSMS Surveillance feature continually surveys the LSMS hardware and software and sends surveillance notifications to Serial Port 3 on each server. The Surveillance feature also logs all surveillance notifications in the file survlog.log in the/var/TKLC/lsms/logs directory. The Surveillance feature starts when LSMS starts.

Figure 2-5 T1100 - Rear View - Showing Serial Ports


img/c_understanding_the_surveillance_feature_mm-fig1.jpg

The Surveillance feature also monitors network interfaces. For information about configuring the Surveillance feature for this purpose, refer to the Configuration Guide.

The Surveillance feature enables remote personnel to monitor the LSMS and detect conditions that require immediate action. Some surveillance notifications are sent only when the event occurs; other notifications are sent both when the event first occurs and also every five minutes thereafter until the condition is cleared. Every five minutes, the Surveillance feature also sends a keep alive notification to the Surveillance serial port and logs the keep alive in the file survlog.log.

The following topics are described in this section:

Configuring a Customer-Provided Administration Console

If customers desire a local administration console for displaying Surveillance notifications, they can attach their own administration console to Serial Port 3 on each of the LSMS servers. The following requirements are needed to provide and configure a customer-provided administration console:

  • A workstation that can display text
  • Two cables that connect to the RJ-45 interface used by Serial Port 3 on each LSMS server
  • Configure the connections as:
    • 115200 baud
    • Parity 8E1
  • Software running on the workstation that can determine from which cable the Surveillance notification is arriving (the Surveillance notifications do not identify which server is generating them)

Controlling the Surveillance Feature

The Surveillance feature starts on each server when the server starts. The following topics explain how to use LSMS commands to start, stop, and check the status of the Surveillance feature.

Note:

These commands affect only the server on which they are entered.
Starting the Surveillance Feature

Use the lsmssurv start command to start the Surveillance feature on the server that you are logged into.

  1. Log in as root on either server.
  2. Type the following command to start surveillance:
    lsmssurv start

    Either of the following messages appears, depending on whether surveillance was already running: 

    
LSMS Surveillance feature started
LSMS Surveillance feature is currently running
  3. Repeat this procedure for the other server, if desired.
Stopping the Surveillance Feature

Use the lsmssurv stop command to stop the Surveillance feature on the server that you are logged into.

  1. Log in as root on either server.
  2. Type the following command to stop surveillance:
    lsmssurv stop

    Either of the following messages appears, depending on whether surveillance was already stopped: 

    
LSMS Surveillance feature stopped
LSMS Surveillance feature is not currently running
  3. Repeat this procedure for the other server, if desired.
Determining the Surveillance Status

Use the lsmssurv status command to check the status of the Surveillance feature. This command allows you to determine if the Surveillance feature is already running or has already been stopped.

  1. Log in as root on either server.
  2. Type the following command to get surveillance status:
    # lsmssurv status

    You will receive one of the following messages: 

    
LSMS Surveillance feature is currently started
LSMS Surveillance feature is currently stopped
  3. Repeat this procedure for the other server, if desired.
Returning the Surveillance Feature to Last Valid State

Use the lsmssurv last command to return the Surveillance feature to its last valid state. If the Surveillance Monitor should be running but it is not for any reason, then lsmssurv last will start it.

  1. Log in as root on either server.
  2. Type the following command:
    lsmssurv last

    The following messages appears: 

    
LSMS Surveillance feature started
  3. Repeat this procedure for the other server, if desired.

Understanding Surveillance Notifications

Introduction provides information about the format of Surveillance notifications and how they correlate to GUI notifications and traps. In addition, for each Surveillance notification, ordered by its event number, the appendix provides the following information:

  • It output text string
  • Explanation of possible cause, beyond the text that fits into the notification text string
  • Suggested recovery actions
  • Source from which the notification is sent
  • Frequency with which the notification appears

Logging Surveillance Notifications

In addition to displaying Surveillance notifications, the Surveillance feature logs all Surveillance notifications in the file survlog.log in the/var/TKLC/lsms/logs directory.

If the LSMS Surveillance feature becomes unable to properly report conditions, it logs the error information in a file, named lsmsSurv.log, in the /var/TKLC/lsms/logs directory on each server’s system disk. When the size of lsmsSurv.log exceeds 1MB, it is copied to a backup file, named lsmsSurv.log.bak, in the same directory. There is only one LSMS Surveillance feature backup log file, which limits the amount of log disk space to approximately 2MB.

Understanding the Service Assurance Feature

The Service Assurance feature allows an external system to access subscription version data from the LNP databases in the LSMS. This information is useful in verifying correct porting of data, and helps in troubleshooting problems. There is one LNP database for each of the NPACs associated with the LSMS.

The external system uses Service Assurance Manager (SAM) application software to initiate service assurance data requests and associations. Single or multiple SAMs may exist on the external computer system. The SAM communicates with the LSMS through the Service Assurance Agent (SAA) application software that resides in the LSMS. The SAM application software is not Oracle software and is only resident on the external system.

The SAA decodes the queries from the SAM and then accesses the LNP database. The SAA forms the subscription version data into a message and that message is sent to the SAM making the query.

Service Assurance works in conjunction with the Surveillance feature. The Surveillance feature issues the command to start the Service Assurance agent (part of the Service Assurance feature that is described in this document), and it monitors the status of the Service Assurance agent.

A maximum of eight SAM/SAA sessions are allowed at one time.

Figure 2-6 Service Assurance System within a Network


img/c_understanding_the_service_assurance_feature_mm-fig1.jpg

The architecture used to provide the access is a Connection Oriented Manager/Agent using Common Management Information Protocol (CMIP). CMIP provides an industry standard interface between Manager and Agent applications. This allows you to use standard products and tool kits to develop applications.

Service Assurance Terminology

The following terms are used to describe Service Assurance:

  • Service Assurance Manager (SAM): Initiator of service assurance associations and data requests. This is not part of the LSMS application. A SAM application runs on a computer but is not the computer itself. Multiple SAMs can run on the same computer, or each SAM can run on a different computer.
  • Service Assurance Agent (SAA): Software residing on the LSMS and considered part of the LSMS application. This software consists of one or more Linux processes and one or more Linux scripts.
  • NPAC Database: This refers to the database stored on the NPAC.
  • LNP Database: This refers to the database that contains subscriptionVersions, Service Provider Network, Service Provider LRN and Service Provider NPA-NXX objects. This database resides on the LSMS. Each NPAC has one LNP Database on the LSMS.
  • Manager/Agent: This term describes the two peer processes that work together to implement the Service Assurance feature. The Manager is the customer’s application, which is used to initiate the association and send the query to the Agent process. The Agent process decodes the query message, then accesses the LNP Database.

    The Agent extracts the data from the database, then builds and sends the reply to the Manager. This feature allows the Manager to send a single subscription TN or list of subscription TNs to query. The Agent extracts each instance that it can find from the LNP Database and returns a response to the Manager.

The architecture is connection oriented to restrict access to the LNP databases. This system is assumed to be within the customer’s private network, so no encryption security is included. The CMIP protocol defines the method for establishing and terminating associations. This application uses the access control and user data space in the association messages to restrict access to the system.

The SAM is restricted to querying subscription versions by the subscriptionTN field. Up to four SAMs can query the LSMS at the same time.

The Service Assurance feature interfaces to the LSMS by means of a 10 Mbps Ethernet interface. The Application WAN is also used as the interface for the X-terminals connected to the LSMS. The network connecting the Service Assurance systems to the LSMS is the responsibility of the customer.

Interface Implementation

The LSMS Service Assurance interface is implemented over a standard CMIP/CMISE-based OSI protocol stack (Q.3). RFC1006 is used for the transport layer.

This interface is limited to the retrieve capabilities of the local LSMS database. The object to be retrieved is the subscription Version defined in NPAC SMS Interoperable Interface Specification, NANC Version 1.5, September 1997.

Allowed Functions on the Interface

The LSMS responds to association (bind) requests, release (unbind) requests, aborts, and subscription query (m-get) messages. No other functions are allowed over this interface and will be rejected.

Support of OSI Addresses

The LSMS supports four OSI address connections for Service Assurance interfaces, which correspond to eight domains.

Each Service Assurance system needs to establish only the associations it requires, without regard to whether the LSMS is operating with the primary or secondary server. Upon switchover, the association is momentarily lost. The Service Assurance system tries to reestablish the association. When the active system finishes coming up, it then responds to the Service Assurance system association requests. The Service Assurance system does not know whether the primary or secondary system is running.

Association information is specified by Oracle. This information must be present in the bind request. This data in the association information, such as the system name, is used to verify the source of a bind request. Bind requests with invalid association information are rejected.

Establishment of association between the LSMS and the Service Assurance system is initiated by the Service Assurance Manager. This applies to initial association as well as to reestablishing the association after outages (regardless of the cause of the loss of association). When it does not have an association, the Service Assurance system periodically tries to establish the association until a successful response is received from the LSMS. The minimum retry interval is one minute.

The LSMS provides a response to the bind request to indicate:

  • Successful connection
  • Access control failure (authority violation - unknown address requesting association)
  • LSMS data access failure
  • Resource failure (maximum number of associations already established)

Number of Associations Per Service Assurance System

The LSMS supports one association per Service Assurance system.

If a Service Assurance agent within the LSMS is unable to establish a connection with the LSMS NPAC database, the association with the Service Assurance system is aborted.

Notification Upon Loss of Association

The LSMS provides a notification when the association with any of the Service Assurance Manager is lost or established.

Understanding the SNMP Agent Process

The optional Remote Monitoring feature provides the capability for the LSMS to report certain events and alarms to a remote location, using the industry-standard Simple Network Management Protocol (SNMP). The LSMS implements an SNMP agent with the SNMP agent process running on the LSMS platform.

Customers can use this feature to cause the LSMS to report events and alarms to another location, which implements an SNMP Network Management System (NMS). An NMS is typically a standalone device, such as a workstation, which serves as an interface through which a human network manager can monitor and control the network. The NMS typically has a set of management applications (for example, data analysis and fault recovery applications). The SNMP feature must be enabled while configuring the NMS.

Overview of SNMP Protocols

An SNMP agent, such as that implemented by the LSMS, is responsible for SNMP managed objects; each managed object represents a data variable. A collection of managed objects is called a management information base (MIB). A copy of the MIB is maintained both at the SNMP agent and also at the NMS. The MIB can be read with a text editor.

An SNMP agent can do the following:

  • Respond to requests from the NMS for information and/or action. The SNMP architecture defines a limited set of management commands and responses. The NMS can issue Get, GetNext, and Set messages to retrieve single or multiple object variables or to modify the value of a single variable. The SNMP agent sends a response message to complete the Get, GetNext, or Set. This release of the LSMS does not support these functions.
  • Send event notifications, called trap requests, to the NMS to identify the occurrence of conditions, such as the failure or restoration of a link interface.

The SNMP protocol uses the User Datagram Protocol (UDP) transport protocol in a TCP/IP network. UDP is a connectionless protocol and does not guarantee reliable delivery of data. Therefore, SNMP does not use a preestablished connection to send data and does not guarantee reliable delivery of data.

MIB Structure

Figure 2-7 MIB Structure


img/c_mib_structure_lsms_alarms.jpg

New Object definition: 


sourceIP    OBJECT-TYPE
       SYNTAX      OCTET STRING 
   MAX-ACCESS  read-only
   STATUS      current
   DESCRIPTION
            "Th“ source ip of the device where event was generated."
 ”  ::= { tekelecLSMSEventObjects 44 }

resyncVar   OBJECT-TYPE
       SYNTAX  INTEGER(0..1)
   MAX-ACCESS  read-write
   STATUS  current
   DESCRIPTION "Th“ object is available to be set by the NMS to indicate a request for alarm resynchronization.
                 Object value=0 indicates a request to stop an ongoing resnchronization and Object value=1 indicates a resynchronization request."
:”= { tekelecLSMSEventObjects 45 }

resyncEventCnt        OBJECT-TYPE
       SYNTAX      Unsigned32
   MAX-ACCESS  read-only
   TUS      current
   DESCRIPTION "Th“ total number of Resync alarms to be sent."
 ”  { tekelecLSMSEventObjects 46 }


   alarmSequence    OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
            "Un“que sequence number identifying an SNMP Alarm Trap instance."
 ”  ::= { tekelecLSMSEventObjects 48 }

lsmsUptime   OBJECT-TYPE
       SYNTAX      TimeTicks
   MAX-ACCESS  read-only
   STATUS      current
   DESCRIPTION
            "Ti“e since LSMS is up."
      ::={ tekelecLSMSEventObjects 49 }

specificOid   OBJECT-TYPE
SYNTAX      OCTET STRING
MAX-ACCESS      read-only
STATUS      current
DESCRIPTION "Trap ID."
::= { tekelecLSMSEventObjects 50 }

currentTimeOBJECT-TYPE
SYNTAX      OCTET STRING
MAX-ACCESS      read-only
STATUS      current
DESCRIPTION "Date and time  string."
::= { tekelecLSMSEventObjects 51 }


         resyncErrCode   OBJECT-TYPE
    SYNTAX  OCTET STRING
    MAX-ACCESS  read-only
    STATUS  current
    DESCRIPTION
            "errorCode = 0, Resynchronization completed successfully.
             errorCode = 1, Resynchronization aborted by NMS.
             errorCode = 2, Resynchronization already in progress for the NMS.
             errorCode = 3, Resynchronization Aborted, Database error occurred.
             errorCode = 4, Resynchronization not in progress."
    ::= { tekelecLSMSEventsVer 218 }

New Trap Definition:

Existing traps defined for SNMP v1 are modified to include the following for the MIB for SNMP v3:

  1. sourceIP
  2. alarmSequence

New SNMPv3 MIB Traps: 

tekelecLSMSEventsV3 OBJECT IDENTIFIER ::= { tekelecLSMSEvents 3 }

resyncStartTrap    NOTIFICATION-TYPE
    OBJECTS   { lsmsUptime, sourceIP }
    DESCRIPTION "The trap is sent by the LSMS to NMS when the LSMS is about to start resynchronization"
    ::= {tekelecLSMSEventsV3 212 }

resyncStopTrap    NOTIFICATION-TYPE
    OBJECTS   { lsmsUptime, sourceIP, resyncEventCnt, resyncErrCode }
    DESCRIPTION "The trap is sent by the LSMS to NMS when resynchronization is complete"
    ::= {tekelecLSMSEventsV3 213 }

resyncRejectTrap    NOTIFICATION-TYPE
    OBJECTS   { lsmsUptime, sourceIP, resyncErrCode }
    DESCRIPTION "The trap is sent by the LSMS to NMS when a resynchronization request is rejected by LSMS "
    ::= {tekelecLSMSEventsV3 214 }

resyncRequiredTrap    NOTIFICATION-TYPE
    OBJECTS   { lsmsUptime, sourceIP }
    DESCRIPTION "The trap is sent by the LSMS to NMS when the LSMS is rebooted or LSMS is started"
    ::= {tekelecLSMSEventsV3 215 }

heartBeatTrap    NOTIFICATION-TYPE
    OBJECTS   { lsmsUptime, sourceIP }
    DESCRIPTION "The trap is sent by the LSMS to NMS periodically to indicate that the LSMS is up"
    ::= {tekelecLSMSEventsV3 216 }

lsmsAlarmTrapV3    NOTIFICATION-TYPE
    OBJECTS   { currentTime,specificOid ,sourceIP, alarmSequence,specificAlarm}
    STATUS  current
    DESCRIPTION "The trap will indicate that the following information is for a particular event"
    ::= {tekelecLSMSEventsVer 217 }

The MIB "choice fields" is added to accept a different number of arguments at runtime: 

SPECIFICALARM::=
        CHOICE{
                OBJECTID-VALUE
                        TEKELECLSMSEVENTSVER
                }

Varbinds "sourceIP" and "alarmSequence" are added as a part of SNMPv3 and will be fixed varbinds to keep SNMPv1 backward compatible. SNMPv1 information will be passed as a part of "choice field."

A "currentTime" field conveys information about time when an alarm is triggered.

Current definition for SNMPv3 Trap: 

LSMSALARMTRAPV3    NOTIFICATION-TYPE
    OBJECTS   { CURRENTTIME, SPECIFICOID ,SOURCEIP, ALARMSEQUENCE,SPECIFICALARM}
    STATUS  CURRENT
    DESCRIPTION "THE TRAP WILL INDICATE THAT THE FOLLOWING INFORMATION IS FOR A PARTICULAR EVENT"
    ::= {TEKELECLSMSEVENTSVER 217 }

Description of different varbinds of SNMPv3 Trap:

Table 2-4 Description of Different Varbinds of SNMPv3 Trap

MIB OBJECTS OID Description
currentTime 1.3.6.1.4.1.323.5.3.4.1.1.51.0 Time when alarm is generated.
specificOid 1.3.6.1.4.1.323.5.3.4.1.1.50.0 Oid which uniquely identifies a SNMPV3 alarm
sourceIP 1.3.6.1.4.1.323.5.3.4.1.1.44.0 IP address of active alarm
alarmSequence 1.3.6.1.4.1.323.5.3.4.1.1.48.0 Sequence number of triggered alarm
specifcAlarm List of OID for different varbinds List of oid for different varbind and values

Sample SNMPv3 trap for alarm 4021: 

DISMAN-EVENT-MIB::SYSUPTIMEINSTANCE = TIMETICKS: (44365220) 5 DAYS, 3:14:12.20
SNMPV2-MIB::SNMPTRAPOID.0 = OID: SNMPV2-SMI::ENTERPRISES.323.5.3.4.2.0.217
SNMPV2-SMI::ENTERPRISES.323.5.3.4.1.1.51.0 = STRING: "02/01/10 20:31:31"  SNMPV2-S
MI::ENTERPRISES.323.5.3.4.1.1.50 .0= STRING: "1.3.6.1.4.1.323.5.3.4.2.0.40"
SNMPV2-SMI::ENTERPRISES.323.5.3.4.1.1.44.0 = STRING: "192.168.59.30"      SNMPV2-S
MI::ENTERPRISES.323.5.3.4.1.1.48.0 = GAUGE32: 44  SNMPV2-SMI::ENTERPRISES.323.5.3.
4.1.1.1.0 = INTEGER: 4021       SNMPV2-SMI::ENTERPRISES.323.5.3.4.1.1.17.0 = STR
ING: "LMGRD" 
MIB FOR ALARM 4021
===============
LSMSAPPSNOTRUNNING NOTIFICATION-TYPE
    OBJECTS     { EVENTNBR, PROCESSNAME, SOURCEIP, ALARMSEQUENCE }
    STATUS      CURRENT
    DESCRIPTION
            "THIS NOTIFICATION INDICATES THAT A SPECIFIC LSMS APPLICATION
            OR SYSTEM DAEMON IS NOT RUNNING."
    ::= {TEKELECLSMSEVENTSVER 40 }

Decoding SNMPv3 Trap for alarm 4021:

Table 2-5 Decode SNMPv3 Trap for Alarm 4021

OID MIB OBJECT Value
1.3.6.1.4.1.323. 5.3.4.2.0.217 lsmsAlarmTrapV3 (Indicating SNMPv3 Alarm) NO value
1.3.6.1.4.1.323.5.3.4.1.1.51.0 currentTime 02/01/10 20:31:31
1.3.6.1.4.1.323.5.3.4.1.1.50.0 specificOid (unique oid of lsms alarm) 1.3.6.1.4.1.323.5.3.4.2.0.40
1.3.6.1.4.1.323.5.3.4.1.1.44.0 sourceIP 192.168.59.30
1.3.6.1.4.1.323.5.3.4.1.1.48.0 alarmSequence 44
1.3.6.1.4.1.323.5.3.4.1.1.1.0, 1.3.6.1.4.1.323. 5.3.4.1.1.17.0 eventNbr,processName(variable varbinds) 4021,lmgrd

Note:

There is no SNMPv3 trap for event numbers 8102 to 8105 and 8110 to 8118, as there is no trap definition for these events. These events will exhibit SNMPv1 behavior.

TKLC-LSMS-MIB

TEKELEC-LSMS-TRAP-MIB DEFINITIONS ::= BEGIN-- Copyright 2015 Oracle Corporation IMPORTS       tekelecLSMS     FROM TEKELEC-TOPLEVEL-REG    NOTIFICATION-TYPE,           OBJECT-TYPE,    IpAddress,    TimeTicks,    Unsigned32,    CHOICE      FROM SNMPv2-SMI;-- LSMS Object group sub-tree tekelecLSMSObjects OBJECT IDENTIFIER ::= { tekelecLSMS 1 }-- LSMS Product Events sub-tree tekelecLSMSEvents OBJECT IDENTIFIER ::= { tekelecLSMS 2 }-- LSMS Events Object group sub-tree tekelecLSMSEventObjects OBJECT IDENTIFIER ::= { tekelecLSMSObjects 1 }-- LSMS SNMP Events compatible for both version1 and version3tekelecLSMSEventsVer OBJECT IDENTIFIER ::= { tekelecLSMSEvents 0 }specificAlarm ::=	CHOICE{		objectID-value			tekelecLSMSEventsVer		}---- OBJECTS DEFINITIONS--eventNbr OBJECT-TYPE    SYNTAX  INTEGER (1..2147483647)     MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Tekelec specific unique identifier for the notification	     error number. The value can be any positive integer	     value except 0"    ::= { tekelecLSMSEventObjects 1 }	    -- Varying in length from 0 to 65535 for SNMPv1 OCTET STRINGnPACRegion OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "a string indicating the name of the NPAC Region."    ::= { tekelecLSMSEventObjects 2 }	        -- Varying in length from 0 to 65535 for SNMPv1 OCTET STRINGneCLLI OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "a string indicating the network element CLLI."    ::= { tekelecLSMSEventObjects 3 }	npacId OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "a string that identifies the specific LSMS NPAC              association. Valid values are: primary,secondary."    ::= { tekelecLSMSEventObjects 4 }	npacRegionId OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "A 2 character string 2 that uniquelly identifies each              NPAC region. Valid value are:	     	     MW - Midwest	     MA - Mid-Atlantic	     NE - Northeast	     SE - Southeast             SW - Southwest	     WE - West Regional	     WC - West Coast	     CA - Canada "    ::= { tekelecLSMSEventObjects 5 }		     	     oldNPA OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The old number planning area (area code) value."    ::= { tekelecLSMSEventObjects 6 }		     newNPA  OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The new number planning area (area code) value."    ::= { tekelecLSMSEventObjects 7 } 	     nXX   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The exchange code value (NXX). "    ::= { tekelecLSMSEventObjects 8 } npacRecoveryRetryInterval   OBJECT-TYPE    SYNTAX  OCTET STRING    MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Positive integer value indicating the NPAC recovery retry interval."    ::= { tekelecLSMSEventObjects 9 } retryTimes   OBJECT-TYPE    SYNTAX  OCTET STRING    MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Integer values indicating the number of retries."    ::= { tekelecLSMSEventObjects 10 } fromPeriod   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Beginning time specification YYYYMMDDhhmmss "    ::= { tekelecLSMSEventObjects 11 } toPeriod   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Ending time specification YYYYMMDDhhmmss "    ::= { tekelecLSMSEventObjects 12 } controllerId   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The specific controller number (either 0 or 1)."    ::= { tekelecLSMSEventObjects 13 } driveSpecId   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Disk drive specification."    ::= { tekelecLSMSEventObjects 14 } shareDriveId   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Shared disk drive physical Id."    ::= { tekelecLSMSEventObjects 15 } hotSpareDriveId   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Hot-spare disk drive physical id."    ::= { tekelecLSMSEventObjects 16 } processName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Name of the process (either lsmsagent or supagent)."    ::= { tekelecLSMSEventObjects 17 } diskVolName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Disk Volume name."    ::= { tekelecLSMSEventObjects 18 } backUpType   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "DATABASE or FILESYSTEM."    ::= { tekelecLSMSEventObjects 19 } volumeName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The specific problem disk volume."    ::= { tekelecLSMSEventObjects 20 } 	     fileSystem   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Specific LSMS filesystem with problem."    ::= { tekelecLSMSEventObjects 21 } 	     logFileName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "The EMS log file name."    ::= { tekelecLSMSEventObjects 22 } 	     errorCode   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "errorCode = 2 , the LOG_DIR in the ShadowAudit.cfg does not exist. 	     errorCode = 3, LSMS_DIR is not set in the global.shrc file. 	     errorCode = 4, VERSANT_ROOT or VERSANT_REL is not set in the global.shrc file. 	     errorCode = 6, the /usr/local/etc/global.shrc file does not exist. 	     errorCode = 7, the ShadowAudit.cfg file does not exist in the $LSMS_DIR/config directory. 	     errorCode = 8, the lsmsmate entry in the /etc/hosts file does not exist or is inaccessible. 	     errorCode = 9, the LSMS is unable to use the SecureShell keys or the authorized_keys file on the shadow LSMS is missing.	     errorCode = 10, the directory /var/TKLC/lsms/logs does not have at least 20 megabytes of available disk space."    ::= { tekelecLSMSEventObjects 23 } 	     servAssuranceMgrName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Service assurance manager name."    ::= { tekelecLSMSEventObjects 24 } 	     queueMgrName   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Queue manager name."    ::= { tekelecLSMSEventObjects 25 } 	     operationCode   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "create, delete, modify"    ::= { tekelecLSMSEventObjects 26 } 	     npanxxValue   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "NPA-NXX"    ::= { tekelecLSMSEventObjects 27 } 	     effectiveTimeStamp   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "YYYYMMDDhhmmss"    ::= { tekelecLSMSEventObjects 28 } 	     sPID   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "4 digits alphanumeric value."    ::= { tekelecLSMSEventObjects 29 } 	     nPANXX   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "npanxx value being created or deleted."    ::= { tekelecLSMSEventObjects 30 } 	     npacIP   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "NPAC IP address."    ::= { tekelecLSMSEventObjects 31 } 	     lRN   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Local Routing Number (LRN) value being created, modified or deleted."    ::= { tekelecLSMSEventObjects 32 } id2   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Second id."    ::= { tekelecLSMSEventObjects 33 } 	     hostname   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Name or IP address of host."    ::= { tekelecLSMSEventObjects 34 } alarmBitMask   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Bit mask of Eagle alarm."    ::= { tekelecLSMSEventObjects 35 } svNpbUsage   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Usage of SV/NPB storage database."    ::= { tekelecLSMSEventObjects 36 } dbReplErr   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Error message from database replication."    ::= { tekelecLSMSEventObjects 37 } dbMonErr   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Error message from database monitor daemon."    ::= { tekelecLSMSEventObjects 38 } eagleAgentDataErr  OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Error message preventing record from being sent to network element."    ::= { tekelecLSMSEventObjects 39 } svNpbThreshold   OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "SV/NPB configurable usage threshold."    ::= { tekelecLSMSEventObjects 40 } oldMySQLPortNumber   OBJECT-TYPE    SYNTAX  OCTET STRING    MAX-ACCESS  read-only    STATUS  current    DESCRIPTION            "Old MySQL Port Number."    ::= { tekelecLSMSEventObjects 41 }newMySQLPortNumber   OBJECT-TYPE    SYNTAX  OCTET STRING    MAX-ACCESS  read-only    STATUS  current    DESCRIPTION            "New MySQL Port Number."    ::= { tekelecLSMSEventObjects 42 }binlogsThreshold  OBJECT-TYPE    SYNTAX  OCTET STRING      MAX-ACCESS  read-only    STATUS  current    DESCRIPTION	    "Threshold of forceful binlogs purge."    ::= { tekelecLSMSEventObjects 43 } sourceIP    OBJECT-TYPE    SYNTAX      OCTET STRING    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION            "The source ip of the device where event was generated."    ::= { tekelecLSMSEventObjects 44 }resyncVar   OBJECT-TYPE    SYNTAX  INTEGER(0..1)    MAX-ACCESS  read-write    STATUS  current    DESCRIPTION "The object is available to be set by the NMS to indicate a request for alarm resynchronization.                 Object value=0 indicates a request to stop an ongoing resnchronization and Object value=1 indicates a resynchronization request."    ::= { tekelecLSMSEventObjects 45 }resyncEventCnt        OBJECT-TYPE    SYNTAX      Unsigned32    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "The total number of Resync alarms to be sent."    ::= { tekelecLSMSEventObjects 46 }resyncErrCode          OBJECT-TYPE    SYNTAX      INTEGER    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "Enumerated value that indicates the reason for the trap."    ::= { tekelecLSMSEventObjects 47 }alarmSequence    OBJECT-TYPE    SYNTAX      Unsigned32    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "Unique sequence number identifying an SNMP Alarm Trap instance."    ::= { tekelecLSMSEventObjects 48 }lsmsUptime   OBJECT-TYPE    SYNTAX      TimeTicks    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "Time since LSMS is up."    ::= { tekelecLSMSEventObjects 49 }specificOid   OBJECT-TYPE    SYNTAX      OCTET STRING    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "Trap ID."    ::= { tekelecLSMSEventObjects 50 }currentTime	OBJECT-TYPE    SYNTAX      OCTET STRING    MAX-ACCESS      read-only    STATUS      current    DESCRIPTION "Date and time  string."    ::= { tekelecLSMSEventObjects 51 }--	    -- TRAP DEFINITIONS--	    	     eagleAgentStarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS	current    DESCRIPTION	    "This notification indicates that the eagleagent              process has been started. "     ::= {tekelecLSMSEventsVer 1 }	     eagleAgentStoppedbyscript NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS	current    DESCRIPTION	    "This notification indicates that the eagleagent              process has been stopped by the sup script."     ::= {tekelecLSMSEventsVer 2 }	     	     nPACagentStarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS 	current    DESCRIPTION	    "This notification indicates that the NPACagent              for the region has been started."     ::= {tekelecLSMSEventsVer 3 }	     	     lsmsCommandStoppedNPACagent NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPACagent              process has been stopped using the lsms command."     ::= {tekelecLSMSEventsVer 4 }	     primaryEMSAssocLostSecEstablished NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has lost              association with the primary EMS, switching to              secondary EMS association."     ::= {tekelecLSMSEventsVer 5 }	     	     npacAssocEstablished NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacRegionId, npacId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC              association was successfully established."     ::= {tekelecLSMSEventsVer 7 }	     primaryEMSAssocEstablished NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS              has established the primary association with              the EMS."     ::= {tekelecLSMSEventsVer 8 }	     	     npacAbortByUser NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacRegionId, npacId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC              association has been aborted by the user."     ::= {tekelecLSMSEventsVer 9 }npaSplitActOk NOTIFICATION-TYPE    OBJECTS	{ eventNbr, oldNPA, newNPA, nXX  }    STATUS      current    DESCRIPTION	    "This notification indicates that the              activated split was successful."     ::= {tekelecLSMSEventsVer 10 }switchOverStarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the active 	    server has initiated an automatic switchover 	    to the inactive server."    ::= {tekelecLSMSEventsVer 11 }switchOverCompleted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS service Switchover process has completed."    ::= {tekelecLSMSEventsVer 12 }switchOverFailed NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS 	    service Switchover could not be switched over 	    to the inactive server."    ::= {tekelecLSMSEventsVer 13 }diskContrService NOTIFICATION-TYPE    OBJECTS	{ eventNbr, controllerId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the disk 	    controller <controllerId> is out of service 	    and is affecting shared storage. This notification 	    is only valid on E3000 systems."    ::= {tekelecLSMSEventsVer 14 }npacInterfaceFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates an NPAC interface 	    failure. Its is generated when the ping 	    utility has not receive a response from 	    the interface associated with the NPAC."    ::= {tekelecLSMSEventsVer 15 }    emsInterfaceFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr   }    STATUS      current    DESCRIPTION	    "This notification indicates an EMS Ethernet 	    interface failure. Its is generated when the 	    ping utility has not receive a response from 	    the interface associated with the EMS."    ::= {tekelecLSMSEventsVer 16 }    appsInterfaceFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Ethernet 	    interface used to connect to the APPLICATION 	    network has a problem."    ::= {tekelecLSMSEventsVer 17 }adminInterfaceFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Ethernet 	    interface used to connect to the ADMINISTRATION network has a problem."    ::= {tekelecLSMSEventsVer 18 }survFeatureOn NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Surveillance	    feature is running."    ::= {tekelecLSMSEventsVer 19 }systemDiskSynch NOTIFICATION-TYPE    OBJECTS	{ eventNbr, driveSpecId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the system disk has 	    lost synchronization, possibly due to a hardware problem."    ::= {tekelecLSMSEventsVer 20 }dataReplError NOTIFICATION-TYPE    OBJECTS	{ eventNbr, dbReplErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that database replication has failed."    ::= {tekelecLSMSEventsVer 21 }dbMonitorFail NOTIFICATION-TYPE    OBJECTS	{ eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the DB process monitor has failed."     ::= {tekelecLSMSEventsVer 22 }internalDiskError NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that Volume Manager does not 	    recognize a shared disk that was logically replaced by the 	    hot-spared disk."    ::= {tekelecLSMSEventsVer 23 }hotSparedDataResynch NOTIFICATION-TYPE    OBJECTS	{ eventNbr, shareDriveId, hotSpareDriveId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the hot-spare feature 	    has completed automatic data resynchronization."    ::= {tekelecLSMSEventsVer 24 }dbReplInfo NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbReplErr  }    STATUS      current    DESCRIPTION            "This notification indicates that DB replication delay threshold has crossed."    ::= {tekelecLSMSEventsVer 25 }cpuUtilizationOver60 NOTIFICATION-TYPE    OBJECTS	{ eventNbr, processName, id2  }    STATUS      current    DESCRIPTION	    "This notification indicates that the eagleagent agent 	    or an NPACagent for a specific region is utilizing 79 	    percent or more of the LSMS's CPU resource."    ::= {tekelecLSMSEventsVer 26 }primaryServerInhibited NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the primary servers 	    state is inhibited."    ::= {tekelecLSMSEventsVer 27 }secondaryServerInhibited NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the secondary servers state is inhibited."    ::= {tekelecLSMSEventsVer 28 }heartbeatLinkDown NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that a Heartbeat link is down."    ::= {tekelecLSMSEventsVer 29 }heartbeatLinkTwoDown NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Heartbeat 2 link is down."    ::= {tekelecLSMSEventsVer 30 }lsmsNtwkConfigError NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS network configuration is incorrect."    ::= {tekelecLSMSEventsVer 31 }networkConfigNotSupported NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS network configuration 	    is not supported or recommended."    ::= {tekelecLSMSEventsVer 32 }emsRequiresResynchWithLSMS NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that an EMS (OAP) requires 	    a resynchronization with the LSMS. See customer documentation 	    for database synchronization procedure."    ::= {tekelecLSMSEventsVer 33 }resynchLogMidFull NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the network element 	    resynchronization database contains more then 1000000 	    entries. Run devresync utility."    ::= {tekelecLSMSEventsVer 34 }primaryEMSAssocLostNoSec NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has lost association 	    with the primary EMS and the secondary association is not established."    ::= {tekelecLSMSEventsVer 36 }lostNPACAssoc NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association was 	    disconnected gracefully by the user."    ::= {tekelecLSMSEventsVer 37 }diskVolume95Usage NOTIFICATION-TYPE    OBJECTS	{ eventNbr, diskVolName  }    STATUS      current    DESCRIPTION	    "This notification indicates that the disk volume specified by 	    diskVolName has exceeded the 95 percent usage threshold."    ::= {tekelecLSMSEventsVer 38 }swapSpaceCritical NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the server's system check 	    has raised a swap space critical alarm."    ::= {tekelecLSMSEventsVer 39 }lsmsAppsNotRunning NOTIFICATION-TYPE    OBJECTS	{ eventNbr, processName  }    STATUS      current    DESCRIPTION	    "This notification indicates that a specific LSMS application 	    or system daemon is not running."    ::= {tekelecLSMSEventsVer 40 }backupCompleted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, backUpType  }    STATUS      current    DESCRIPTION	    "This notification indicates that a backup of the specified 	    LSMS disk (DATABASE or FILESYSTEM) has completed successfully."    ::= {tekelecLSMSEventsVer 41 }backupFailed NOTIFICATION-TYPE    OBJECTS	{ eventNbr, backUpType  }    STATUS      current    DESCRIPTION	    "This notification indicates that a backup of the specified 	    LSMS disk (DATABASE or FILESYSTEM) has failed."    ::= {tekelecLSMSEventsVer 42 }emsPendingQueueHalfFull NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the pending queue used 	    to hold the transactions to send to the network element is over half full."    ::= {tekelecLSMSEventsVer 43 }emsPendingQueueMaxReached NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the pending queue used to hold 	    the transactions to send to the network element is completely full."    ::= {tekelecLSMSEventsVer 44 }failedNPACConnectivity NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS is not able to 	    confirm the physical connectivity with the NPAC whose NPAC region is npacRegionId"    ::= {tekelecLSMSEventsVer 45 }eagleAgentIgnoreRecord NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, eagleAgentDataErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that there was a data error in a record	    preventing the eagleagent from sending it to the network element"    ::= {tekelecLSMSEventsVer 46 }primaryServerNotOnline NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the primary LSMS server is not online."    ::= {tekelecLSMSEventsVer 63 }secServerNotPreparedForTakeover NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the secondary LSMS server 	    is not prepared to take over LSMS service."    ::= {tekelecLSMSEventsVer 64 }secServerProvidingLSMSService NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the secondary LSMS 	    server is currently providing the LSMS service."    ::= {tekelecLSMSEventsVer 65 }secServerCannotDeterminePrimAvail NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the secondary LSMS 	    server cannot determined the availability of the LSMS 	    service on the primary server."    ::= {tekelecLSMSEventsVer 66 }serviceAssuranceAgentStarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Service Assurance 	    agent has started successfully."    ::= {tekelecLSMSEventsVer 67 }establishServAssuranceMgrAssoc NOTIFICATION-TYPE    OBJECTS	{ eventNbr, servAssuranceMgrName  }    STATUS      current    DESCRIPTION	    "This notification indicates that the association with 	    the Service Assurance manager has been established successfully."    ::= {tekelecLSMSEventsVer 68 }servAssuranceMgrAssocBroken NOTIFICATION-TYPE    OBJECTS	{ eventNbr, servAssuranceMgrName  }    STATUS      current    DESCRIPTION	    "This notification indicates that the association with 	    the Service Assurance manager has been stopped or disconnected."    ::= {tekelecLSMSEventsVer 69 }servAssuranceAgentNotRunning NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Service 	    Assurance agent is not currently running."    ::= {tekelecLSMSEventsVer 70 }noPhysicalConnectivityToDCM NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS is not 	    able to confirm physical connectivity with the DCM."    ::= {tekelecLSMSEventsVer 73 }lsmsEagleAgentFailed NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS eagleagent 	    process has failed. The sentry daemon process will attempt to restart."    ::= {tekelecLSMSEventsVer 74 }lsmsEagleAgentRestarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS eagleagent 	    process has been successfully restarted by the sentry daemon process."    ::= {tekelecLSMSEventsVer 75 }failureToRestartEagleAgent NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the sentry daemon 	    process was unable to restart the eagleAgent."    ::= {tekelecLSMSEventsVer 76 }nPACagentForRegionFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPACagent process 	    for the region specified by nPACRegion has failed. The sentry 	    daemon will attempt to restart the NPACagent process."    ::= {tekelecLSMSEventsVer 78 }nPACagentForRegionRestarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPACagent process 	    for the region specified by nPACRegion has been successfully 		restarted by the sentry daemon."    ::= {tekelecLSMSEventsVer 79 }failureToRestartNPACagentRegion NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS      current    DESCRIPTION	    "This notification indicates that the sentry daemon process 	    was unable to restart the NPACagent process for the region specified by nPACRegion."    ::= {tekelecLSMSEventsVer 80 }osiDeamonFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the one of the Sunlink OSI daemons, 	    either osinetd or osilogd, has failed. The lsmssentry process 	    will attempt to restart."    ::= {tekelecLSMSEventsVer 88 }osiDeamonRestarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the osinetd or osilogd, 	    daemon has been successfully restarted by the lsmssentry process."    ::= {tekelecLSMSEventsVer 89 }osiDeamonRestartFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the lsmssentry process was not 	    able to restart the osinet or osilogd daemons."    ::= {tekelecLSMSEventsVer 90 }lsmssentryFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Surveillance feature 	    has detected that the sentry daemon process is no longer running."    ::= {tekelecLSMSEventsVer 91 }iddAgentRestarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the surveillance process 	    has detected that the Legacy lddAgent process has restarted and all 	    functionality has resumed."    ::= {tekelecLSMSEventsVer 92 }scpmsIddAgentRestarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the surveillance process has 	    detected that the SCPMS lddAgent process has restarted and all 	    functionality has resumed."    ::= {tekelecLSMSEventsVer 93 }npacRejectedAssocAccessCtrlFail NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC aborted association 	    because it received a message from LSMS that failed security checks."    ::= {tekelecLSMSEventsVer 95 }npacRejectedAssocInvalidData NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC aborted 	    the association because NPAC received invalid data from LSMS."    ::= {tekelecLSMSEventsVer 96 }emaAssociationAbortedQueueFull NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that all associations to 	    the EMS are aborted, since the pending queue used to hold 	    transactions to be send to the EMS/NE is full."    ::= {tekelecLSMSEventsVer 97 }emsAssocAbortedMaxResend NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that all associations to the EMS 	    are aborted, since the eagleagent has already tried resending 	    the same message the maximum number of times."    ::= {tekelecLSMSEventsVer 98 }assocRespNPACTimeout NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS did not receive 	    an association response from the NPAC within the timeout period. 	    The LSMS will attempt the association with the NPAC again after 	    configurable amount of time."    ::= {tekelecLSMSEventsVer 100 }assocRejectedRetrySameHost NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association 	    was rejected by the NPAC, and the LSMS was informed to 	    attempt the NPAC association again to the same NPAC host 	    after configurable amount of time."    ::= {tekelecLSMSEventsVer 101 }assocRejectedRetryOtherHost NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association was 	    rejected by the NPAC, and the LSMS was informed to attempt 	    the NPAC association again to the other NPAC host after after 	    configurable amount of time."    ::= {tekelecLSMSEventsVer 102 }    nwtkProblemRetryNPACAssoc NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that a problem exists in 	    the network connectivity. The LSMS will attempt the association 	    with the NPAC again after configurable amount of time."    ::= {tekelecLSMSEventsVer 103 }lsmsAbortedNPACassocDowRecFail NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS received 	    three consecutive responses from the NPAC with a download 	    status of failure from a recovery request. The LSMS 	    has aborted the associations and will attempt to associate 	    again after configurable amount of time. The LSMS will retry 	    the recovery action after the association is reestablished."    ::= {tekelecLSMSEventsVer 104 }nwtkConnProblemNPACAssocAborted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association was 	    aborted due to a network connectivity loss between the LSMS and the NPAC."    ::= {tekelecLSMSEventsVer 105 }assocRejDueToAccessControl NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC rejected 	    the association request because it could not validate access control."    ::= {tekelecLSMSEventsVer 106 }npacAssocRejDuetoAccessDenied NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC rejected 	    the association with an indication of access denied."    ::= {tekelecLSMSEventsVer 107 }npacConnFailedCMIP NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC connection 	    attempt failed, because the userInfo value in the cmipUserInfo 	    portion of the NPAC association response CMIP message is invalid."    ::= {tekelecLSMSEventsVer 108 }npacAssocGracefullyTerminated NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association 	    was terminated gracefully by the NPAC."    ::= {tekelecLSMSEventsVer 109 }lsmsDataLostBadResynch NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS was not 	    resynchronized properly with the NPAC. There are multiple 	    steps in recovery. All steps failed."    ::= {tekelecLSMSEventsVer 112 }badNPACresynchTime NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS was not 	    resynchronized properly with the NPAC. There are 	    multiple steps in recovery. Some steps failed."    ::= {tekelecLSMSEventsVer 113 }assocAbortedBadKeys NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS aborted 	    the NPAC association because the LSMS received a message 	    from the NPAC that did not have the correct LSMS key signature."    ::= {tekelecLSMSEventsVer 114 }scpmsMqSeriesFault NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LDD SCPMS Confirmation 	    of Arrival message retry attempts have been exhausted. 	    The MQSeries interface is not operational or network connectivity 	    to the remote system is lost."    ::= {tekelecLSMSEventsVer 116 }scpmsNotActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LDD SCPMS system 	    has not provided a response within the time limit specified 	    by the LDD_SCP_SYSTEM_RESPONSE_TOMEOUT configuration parameter. 	    The SCPMS system is not active."    ::= {tekelecLSMSEventsVer 117 }legacyMqSeriesFault NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LDD Legacy Confirmation 	    of Arrival message retry attempts have been exhausted. 	    The MQSeries interface is not operational or network connectivity 	    to the remote system is lost."    ::= {tekelecLSMSEventsVer 118 }scpmsLegacyNotActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LDD Legacy system 	    has not provided a response within the time limit specified 	    by the LDD_SCP_SYSTEM_RESPONSE_TOMEOUT configuration parameter. 	    The SCPMS system is not active."    ::= {tekelecLSMSEventsVer 119 }mqQeriesQueueManagerNotActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr, queueMgrName  }    STATUS      current    DESCRIPTION	    "This notification indicates that A connection could not 	    be made to the MQSeries local queue manager. The local 	    queue manager is not started or operational."    ::= {tekelecLSMSEventsVer 120 }npacAutoAssociationRetryCanceled NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that an NPAC automatic associations 	    retry has been canceled."    ::= {tekelecLSMSEventsVer 122 }npacRecoveryFailureResourceLimitation NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId, retryTimes, npacRecoveryRetryInterval  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS received a response 	    from the NPAC with a download status of failure from a recovery 	    action request. The NPAC is unable to process the recovery action 	    due to a temporary resource limitation. The LSMS will retry the 	    request after five minutes."    ::= {tekelecLSMSEventsVer 123 }npacAssocPeriodDowm NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId, fromPeriod, toPeriod  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPAC association will be 	    down for the specified period of time due to NPAC-scheduled down time."    ::= {tekelecLSMSEventsVer 124 }npacAssocRequestSentAfterRetryTimer NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId, npacRegionId  }    STATUS      current    DESCRIPTION	    "This notification indicates that an associate request has been 	    sent to the NPAC after retry timer has expired."    ::= {tekelecLSMSEventsVer 125 }npanxxGTTValueNotFound NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the NPANXX GTT creation, deletion or modification transaction, 	    and the NPANXX value in the transaction could not be determined."    ::= {tekelecLSMSEventsVer 126 }npanxxGTTValueRejected NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode, npanxxValue  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the NPANXX GTT creation, deletion or modification transaction 	    for the specified NPANXX value."    ::= {tekelecLSMSEventsVer 127 }overrideGTTValueNotFound NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the Override GTT creation, deletion or modification transaction, 	    and the LRN value in the transaction could not be determined."    ::= {tekelecLSMSEventsVer 128 }overrideGTTValueRejected NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode, lRN  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the Override GTT creation, deletion or modification transaction 	    for the specified LRN value."    ::= {tekelecLSMSEventsVer 129 }secondaryEMSAssocLost NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has lost association 	    with the secondary EMS, the primary association is still up."    ::= {tekelecLSMSEventsVer 130 }unableToCompleteAutoResynch NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS was not able to complete 	    automatic synchronization with the EMS/NE."    ::= {tekelecLSMSEventsVer 131 }autoResynchNEStarted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has started its 	    automatic synchronization with the EMS/NE."    ::= {tekelecLSMSEventsVer 132 }dbResynchCompleted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, npacId  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Automatic resynchronization 	    of databases after an outage between the LSMS and the NPAC has 	    completed successfully."    ::= {tekelecLSMSEventsVer 133 }secondaryEMSAssocEstablished NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has established 	    the second association with the EMS. This association is 	    only established if a primary association already exists."    ::= {tekelecLSMSEventsVer 134 }emsShortSynchCompleted NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS has completed 	    Short Synchronization with the EMS."    ::= {tekelecLSMSEventsVer 138 }transactionToSecondary NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Primary EMS association 	    is either down or is inhibited, such that transaction sent to 	    the primary EMS will not be received by the network element. 	    Transactions are being sent to the secondary EMS instead of the primary EMS."    ::= {tekelecLSMSEventsVer 139 }pendingQueueHalfFullClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS Pending Queue is less than half full."    ::= {tekelecLSMSEventsVer 141 }pendingQueueFullClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS Pending Queue is no longer full."    ::= {tekelecLSMSEventsVer 142 }dcmConnectionRestored NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that physical connection has been 	    restored with the DCM."    ::= {tekelecLSMSEventsVer 143 }connToMqSeriesQueueMngrRest NOTIFICATION-TYPE    OBJECTS	{ eventNbr, queueMgrName  }    STATUS      current    DESCRIPTION	    "This notification indicates that the connection to the MQSeries 	    local queue manager has been established following an outage."    ::= {tekelecLSMSEventsVer 144 }npaNxxOpenedForPortabilityAtTS NOTIFICATION-TYPE    OBJECTS	{ eventNbr, sPID, nPANXX, effectiveTimeStamp  }    STATUS      current    DESCRIPTION	    "This notification indicates that the specified NPA-NXX is opened 	    for portability starting at value of the EffectiveTimeStamp field."    ::= {tekelecLSMSEventsVer 145 }npaNxxPortedAtTS NOTIFICATION-TYPE    OBJECTS	{ eventNbr, sPID, nPANXX, effectiveTimeStamp  }    STATUS      current    DESCRIPTION	    "This notification indicates that the first telephone number in 	    the specified NPA-NXX is ported stating at the value of 	    the EffectiveTimeStamp field."    ::= {tekelecLSMSEventsVer 146 }ebdaAuditActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that an Audit is currently running."    ::= {tekelecLSMSEventsVer 147 }ebdaAuditSuccess NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that an Audit has completed successfully."    ::= {tekelecLSMSEventsVer 148 }ebdaAuditFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that an Audit has failed."    ::= {tekelecLSMSEventsVer 149 }ebdaAuditAbortedByUser NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that an Audit has been aborted by 	    the user prior to completion."    ::= {tekelecLSMSEventsVer 150 }ebdaReconcileActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a reconcile is currently running."    ::= {tekelecLSMSEventsVer 151 }ebdaReconcileSuccess NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a reconcile has completed successfully."    ::= {tekelecLSMSEventsVer 152 }ebdaReconcileFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a reconcile has failed."    ::= {tekelecLSMSEventsVer 153 }ebdaReconcileAbortedByUser NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a reconcile has been 	    aborted by the user prior to completion."    ::= {tekelecLSMSEventsVer 154 }ebdaBulkLoadActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a bulk load is currently running."    ::= {tekelecLSMSEventsVer 159 }ebdaBulkLoadSuccess NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a bulk load has completed successfully."    ::= {tekelecLSMSEventsVer 160 }    ebdaBulkLoadFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a bulk load has failed."    ::= {tekelecLSMSEventsVer 161 }ebdaBulkLoadAbortedByUser NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a bulk load has been 	    aborted by the user prior to completion."    ::= {tekelecLSMSEventsVer 162 }ebdaResyncActive NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a re-sync is currently running."    ::= {tekelecLSMSEventsVer 163 }ebdaResyncSuccess NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a re-sync has completed successfully."    ::= {tekelecLSMSEventsVer 164 }ebdaResyncFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a re-sync has failed."    ::= {tekelecLSMSEventsVer 165 }ebdaResyncAbortedByUser NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI  }    STATUS      current    DESCRIPTION	    "This notification indicates that a re-sync has been aborted 	    by the user prior to completion."    ::= {tekelecLSMSEventsVer 166 }sprintIddAgentCommFailureLegSys NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Sprint lddAgent has failed 	    to communicate with the Sprint Legacy System."    ::= {tekelecLSMSEventsVer 167 }sprintIddAgentCommFailureScpmsSys NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Sprint lddAgent has failed 	    to communicate with the Sprint SCPMS System."    ::= {tekelecLSMSEventsVer 168 }lsmsMirroringInconsistance NOTIFICATION-TYPE    OBJECTS	{ eventNbr, volumeName  }    STATUS      current    DESCRIPTION	    "This notification indicates an LSMS mirroring inconsistentane."    ::= {tekelecLSMSEventsVer 169 }lsmsFilesystemNotWritable NOTIFICATION-TYPE    OBJECTS	{ eventNbr, fileSystem  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS filesystem is not writeable."    ::= {tekelecLSMSEventsVer 170 }automaticFileTransferFeatureFailure NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Automatic File 	    Transfer feature has a failure."    ::= {tekelecLSMSEventsVer 171 }npaSplitActFailed NOTIFICATION-TYPE    OBJECTS	{ eventNbr, oldNPA, newNPA, nXX  }    STATUS      current    DESCRIPTION	    "This notification indicates the failure of an NPASplit activation."    ::= {tekelecLSMSEventsVer 172 }activeSplitsPastEndDates NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that some active splits are past 	    their End Dates and should be deleted."    ::= {tekelecLSMSEventsVer 173 }lddScpmsAgentSwitchToBackupScpms NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates the LDD SCPMS agent is switching from 	    primary to backup SCPMS system."    ::= {tekelecLSMSEventsVer 174 }lddScpmsAgentSwitchFromBackupToPrim NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates the LDD SCPMS agent is switching 	    from backup to primary SCPMS system."    ::= {tekelecLSMSEventsVer 175 }lddScpmsPrimary NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates the LDD SCPMS current system is primary SCPMS."    ::= {tekelecLSMSEventsVer 176 }lddScpmsBackup NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates the LDD SCPMS current system is backup SCPMS."    ::= {tekelecLSMSEventsVer 177 }emsNeRejNpaNxxSplitNotDetermined NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the NPANXX Split creation or deletion transaction, and 	    the NPANXX value in the transaction could not be determined."    ::= {tekelecLSMSEventsVer 178 }emsNeRejectedNpaNxxSplit NOTIFICATION-TYPE    OBJECTS	{ eventNbr, neCLLI, operationCode, nPANXX  }    STATUS      current    DESCRIPTION	    "This notification indicates that the EMS/NE has rejected 	    the NPANXX Split creation or deletion transaction for 	    the specified NPANXX value."    ::= {tekelecLSMSEventsVer 179 }physicalConnectivityWithQueryServerLost NOTIFICATION-TYPE    OBJECTS	{ eventNbr, hostname  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS is not able to confirm	    the physical connectivity with the Query Server for the specified	    hostname."    ::= {tekelecLSMSEventsVer 180 }queryServerConnectionWithLsmsLost NOTIFICATION-TYPE    OBJECTS	{ eventNbr, hostname  }    STATUS      current    DESCRIPTION	    "This notification indicates that the Query Server identified by	    the hostname does not have a connection with the LSMS."    ::= {tekelecLSMSEventsVer 181 }nPACagentStopRegDBaccessFault NOTIFICATION-TYPE    OBJECTS	{ eventNbr, nPACRegion  }    STATUS      current    DESCRIPTION	    "This notification indicates that the NPACagent process has been	    stopped due to fault in accessing the regional database."    ::= {tekelecLSMSEventsVer 189 }swapSpaceWarning NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the server's system check has 	    raised a swap space warning alarm."    ::= {tekelecLSMSEventsVer 190 }minorPlatAlarmMask NOTIFICATION-TYPE    OBJECTS	{ eventNbr, alarmBitMask  }    STATUS      current    DESCRIPTION	    "This notification indicates that minor Platform alarms have	    been raised as indicated by the alarm BitMask."    ::= {tekelecLSMSEventsVer 191 }majorPlatAlarmMask NOTIFICATION-TYPE    OBJECTS	{ eventNbr, alarmBitMask  }    STATUS      current    DESCRIPTION            "This notification indicates that major Platform alarms have	    been raised as indicated by the alarm BitMask."    ::= {tekelecLSMSEventsVer 192 }criticalPlatAlarmMask NOTIFICATION-TYPE    OBJECTS	{ eventNbr, alarmBitMask  }    STATUS      current    DESCRIPTION	    "This notification indicates that critical Platform alarms have	    been raised as indicated by the alarm BitMask."    ::= {tekelecLSMSEventsVer 193 }svNpbPercentUsage NOTIFICATION-TYPE    OBJECTS	{ eventNbr, svNpbThreshold, svNpbUsage  }    STATUS      current    DESCRIPTION	    "This notification indicates that the SV/NPB storage database        has exceeded the configured percent usage threshold."    ::= {tekelecLSMSEventsVer 194 }dataReplClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr, dbReplErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the system is ready for database replication."    ::= {tekelecLSMSEventsVer 195 }dbMonitorClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the DB process monitor has been cleared."     ::= {tekelecLSMSEventsVer 196 }    minorPlatAlarmClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the server's system check process has cleared all minor platform alarms."     ::= {tekelecLSMSEventsVer 197 }    majorPlatAlarmClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the server's system check process has cleared all major platform alarms."     ::= {tekelecLSMSEventsVer 198 }    criticalPlatAlarmClear NOTIFICATION-TYPE    OBJECTS	{ eventNbr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the server's system check process has cleared all critical platform alarms."     ::= {tekelecLSMSEventsVer 199 }dbCorruptIndex NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION	    "This notification indicates that the LSMS database has corruption."    ::= {tekelecLSMSEventsVer 200 }invalidSnapshot NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION            "This notification indicates that the LSMS server has an Invalid Snapshot."    ::= {tekelecLSMSEventsVer 201 }invalidSnapshotClear NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION            "This notification indicates that the Invalid Snapshot has been cleared from the LSMS server."    ::= {tekelecLSMSEventsVer 202 }fullSnapshot NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION            "This notification indicates that the snapshot space usage is greater than the MAX_USAGE percent."    ::= {tekelecLSMSEventsVer 203 }fullSnapshotClear NOTIFICATION-TYPE    OBJECTS   { eventNbr, dbMonErr  }    STATUS      current    DESCRIPTION            "This notification indicates that the snapshot full space usage Error is cleared."    ::= {tekelecLSMSEventsVer 204 }mateServerDown NOTIFICATION-TYPE    OBJECTS   { eventNbr  }    STATUS      current    DESCRIPTION        "This notification indicates that mate server is Down."    ::= {tekelecLSMSEventsVer 205 }mateServerUp NOTIFICATION-TYPE    OBJECTS   { eventNbr  }    STATUS      current    DESCRIPTION        "This notification indicates that mate server is Up."    ::= {tekelecLSMSEventsVer 206 }svNpbBelowLimit NOTIFICATION-TYPE    OBJECTS	{ eventNbr, svNpbThreshold, svNpbUsage  }    STATUS      current    DESCRIPTION	    "This notification indicates that the SV/NPB storage database         usage is below the configured percent usage threshold."    ::= {tekelecLSMSEventsVer 207 }mysqlPortUpdated NOTIFICATION-TYPE    OBJECTS   { eventNbr, oldMySQLPortNumber, newMySQLPortNumber  }    STATUS      current    DESCRIPTION        "This notification indicates that the MySQL Port has been updated. LSMS application restart is required."    ::= {tekelecLSMSEventsVer 208 }queryServerResetConfiguration NOTIFICATION-TYPE    OBJECTS   { eventNbr, oldMySQLPortNumber, newMySQLPortNumber  }    STATUS      current    DESCRIPTION        "This notification indicates that the MySQL Port has been updated. Query Server configuration needs to be updated."    ::= {tekelecLSMSEventsVer 209 }purgeConfirmRequired NOTIFICATION-TYPE    OBJECTS   { eventNbr  }    STATUS      current    DESCRIPTION        "This notification indicates that at least one of the directly connected query server is out of sync and binary log purging requires confirmation from the user."    ::= {tekelecLSMSEventsVer 210 }purgeImminent NOTIFICATION-TYPE    OBJECTS   { eventNbr, binlogsThreshold  }    STATUS      current    DESCRIPTION            "This notification indicates that the disk usage is reaching the threshold and forceful purge of binary logs is imminent."    ::= {tekelecLSMSEventsVer 211 }resyncStartTrap    NOTIFICATION-TYPE    OBJECTS   { lsmsUptime, sourceIP }    STATUS      current    DESCRIPTION "The trap is sent by the LSMS to NMS when the LSMS is about to start resynchronization"    ::= {tekelecLSMSEventsVer 212 }resyncStopTrap    NOTIFICATION-TYPE    OBJECTS   { lsmsUptime, sourceIP, resyncEventCnt, resyncErrCode }    STATUS      current    DESCRIPTION "The trap is sent by the LSMS to NMS when resynchronization is complete"    ::= {tekelecLSMSEventsVer 213 }resyncRejectTrap    NOTIFICATION-TYPE    OBJECTS   { lsmsUptime, sourceIP, resyncErrCode }    STATUS      current    DESCRIPTION "The trap is sent by the LSMS to NMS when a resynchronization request is rejected by LSMS "    ::= {tekelecLSMSEventsVer 214 }resyncRequiredTrap    NOTIFICATION-TYPE    OBJECTS   { lsmsUptime, sourceIP }    STATUS      current    DESCRIPTION "The trap is sent by the LSMS to NMS when the LSMS is rebooted or LSMS is started"    ::= {tekelecLSMSEventsVer 215 }heartBeatTrap    NOTIFICATION-TYPE    OBJECTS   { lsmsUptime, sourceIP }    STATUS      current    DESCRIPTION "The trap is sent by the LSMS to NMS periodically to indicate that the LSMS is up"    ::= {tekelecLSMSEventsVer 216 }lsmsAlarmTrapV3    NOTIFICATION-TYPE    OBJECTS   { currentTime,specificOid ,sourceIP, alarmSequence,specificAlarm}    STATUS  current    DESCRIPTION "The trap will indicate that the following information is for a perticular event"    ::= {tekelecLSMSEventsVer 217 }resyncErrCode   OBJECT-TYPE    SYNTAX  OCTET STRING    MAX-ACCESS  read-only    STATUS  current    DESCRIPTION            "errorCode = 0, Resynchronization completed successfully.             errorCode = 1, Resynchronization aborted by NMS.             errorCode = 2, Resynchronization already in progress for the NMS.             errorCode = 3, Resynchronization Aborted, Database error occurred.             errorCode = 4, Resynchronization not in progress."    ::= { tekelecLSMSEventsVer 218 }END

LSMS-NAS-MIB

LSMS-NAS-MIB DEFINITIONS ::= BEGIN-- Copyright 2000 Tekelec CorporationIMPORTS    enterprises     FROM RFC1155-SMI    OBJECT-TYPE     FROM RFC-1212    TRAP-TYPE       FROM RFC-1215;tekelecCorp OBJECT IDENTIFIER ::= { enterprises 323 }tekelecPrivate          OBJECT IDENTIFIER ::= { tekelecCorp  1 }tekelecRegistration     OBJECT IDENTIFIER ::= { tekelecCorp  2 }tekelecGeneric          OBJECT IDENTIFIER ::= { tekelecCorp  3 }tekelecCapabilities     OBJECT IDENTIFIER ::= { tekelecCorp  4 }tekelecProductGroups    OBJECT IDENTIFIER ::= { tekelecCorp  5 }tekelecRequirements     OBJECT IDENTIFIER ::= { tekelecCorp  6 }tekelecExperimental     OBJECT IDENTIFIER ::= { tekelecCorp  7 }tekelecCallCenterGroup  OBJECT IDENTIFIER ::= { tekelecProductGroups  1 }tekelecDiagnosticsGroup OBJECT IDENTIFIER ::= { tekelecProductGroups  2 }tekelecSwitchingGroup   OBJECT IDENTIFIER ::= { tekelecProductGroups  3 }experimental            OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  1 }generic                 OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  2 }tekelecEAGLE            OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  3 }tekelecLSMS             OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  4 }tekelecOAP              OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  5 }tekelecIP7              OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  6 }tekelecINSIGHT7         OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  7 }tekelecTALON            OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  8 }tekelecVOX              OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  9 }tekelecSCP              OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  10 }tekelecIVR              OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  11 }tekelecNetworkSwitch    OBJECT IDENTIFIER ::= { tekelecSwitchingGroup  12 }-- LSMS Object group sub-treetekelecLSMSObjects OBJECT IDENTIFIER ::= { tekelecLSMS 1 }-- LSMS Product Events sub-treetekelecLSMSEvents OBJECT IDENTIFIER ::= { tekelecLSMS 2 }-- LSMS Events Object group sub-treetekelecLSMSEventObjects OBJECT IDENTIFIER ::= { tekelecLSMSObjects 1 }-- LSMS SNMPv1 EventstekelecLSMSEventsV1 OBJECT IDENTIFIER ::= { tekelecLSMSEvents 0 }        volumeNearlyFull TRAP-TYPE        ENTERPRISE       tekelecLSMSEventsV1        DESCRIPTION                "At least one volume is more than 95% full.                The string sent with the trap gives the                name of the volume or volumes which exceed                the threshold."        ::= 212        volumeRepaired  TRAP-TYPE        ENTERPRISE      tekelecLSMSEventsV1        DESCRIPTION                "All volumes are now under 95% full."        ::= 213        diskFailed      TRAP-TYPE        ENTERPRISE      tekelecLSMSEventsV1        DESCRIPTION                "One or more disks failed.                The trap includes a string describing the failed disk(s)."        ::= 214        diskRepaired    TRAP-TYPE        ENTERPRISE      tekelecLSMSEventsV1        DESCRIPTION                "The failed disks have been repaired."        ::= 215END

The LSMS SNMP Agent Implementation

The LSMS SNMP agent process supports only the SNMP version 1 trap operation. The SNMP agent receives (through UDP Linux sockets) LSMS notification events from the following processes and formats these events into trap requests:

  • The Surveillance process, which continually monitors the LSMS hardware and software.
  • The LSMS graphical user interface (GUI) process.
  • One or more regional agent (npacagent) processes, each of which receives commands from Number Portability Administration Centers (NPACs) and the GUI process, interprets those commands, and initiates appropriate LSMS activities to manage regional NPAC data. The LSMS can support up to eight regions; each region corresponds to an NPAC.
  • One or more eagleagent processes, each of which receives commands from the GUI process, interprets those commands, and initiates appropriate LSMS activities to send data to the network elements. The LSMS can support up to eight pairs of network elements.
  • The Local Data Manager (supman) process, which manages locally provisioned data that is entered through the GUI and sent to the network elements which the LSMS supports.

The LSMS SNMP agent formats the information received from these processes into an SNMPv1 trap protocol data unit (PDU) and sends the trap request to one or more NMSs. Each NMS (provided by the customer) has a local copy of the LSMS MIB. When the NMS receives a trap request from the LSMS, it compares the information in the trap request to information in its own MIB to determine what event has occurred at the LSMS.

For information about the format of a trap and which events are reported in traps, see Automatic Monitoring of Events

Configuring the SNMP Agent

If you install the optional Remote Monitoring feature, refer to the Configuration Guide to configure the IP addresses and community names for each of the NMSs to which you want the LSMS to send trap requests. You can also perform this procedure if you want to add or delete NMSs after you have started the LSMS. The LSMS can support up to five NMSs simultaneously.

Controlling the SNMP Agent

If the optional Remote Monitoring feature is installed, it is managed by the sentry process (sentryd) and can also be controlled by the user.

After the LSMS boots up, the sentry process (sentryd) constantly monitors the LSMS SNMP agent process. If the SNMP agent process exits abnormally, the sentry process (sentryd) restarts it.

Any user who belongs to the lsmsadm permission group can use the lsmsSNMP command to start, stop, or display status of the LSMS SNMP agent.

Stopping the SNMP Agent

Perform the following procedure to stop the SNMP agent process:

  1. Log in to the active server as a member of the lsmsadm permission group.
  2. To stop the SNMP agent, enter the following command:
    $LSMS_DIR/lsmsSNMP stop

Starting the SNMP Agent

Perform the following procedure to start the SNMP agent process:

  1. Log in to the active server as a member of the lsmsadm permission group.
  2. To start the SNMP agent, enter the following command:
    $LSMS_DIR/lsmsSNMP start

Determining the Status of the SNMP Agent

Perform the following procedure to determine the status of the SNMP agent process:

  1. Log in to the active server as a member of the lsmsadm permission group.
  2. To retrieve the status of the SNMP agent, enter the following command:
    $ $LSMS_DIR/lsmsSNMP status

    Output similar to the following appears:

    
Checking the status of the LSMS SNMP Agent...
LSMS SNMP agent is running.
LSMS SNMP AGENT PROCESS STATUS

TOTAL SUCCESSFUL TRAP REQUEST = 2926

TOTAL FAILED TRAP REQUEST = 0


== IP-ADDRESS == == STATUS ==

SNMP SESSION ESTABLISHED 10.250.54.19
finish

LSMS SNMP Resync is running.

LSMS Heartbeatsender is running.
    This output provides the following information:
    • A title line to indicate that the output is LSMSSNMP agent process status
    • The total number of successful SNMP trap requests sent by the LSMSSNMP agent since it started
    • The total number of failed SNMP trap requests sent by the LSMSSNMP agent since it started
    • The status of each UDP socket session to an NMS, along with the IP address of the NMS:
      • Failed indicates that an SNMP session was never established
      • SNMP Session Established indicates that the session was successfully established

Logging SNMP Agent Actions

When the LSMS SNMP agent process starts, stops, or sends a trap request, it logs information about the action in a log file. The log file is named lsmsSNMP.log<MMDD>, where <MMDD> represents the current month and day. The log file is stored in the directory /usr/TKLC/lsms/logs/snmp and is automatically deleted after 7 days. If either the log file or its directory does not already exist, the agent process creates the file or the directory, or both, when one of these actions occurs.

The log file has a maximum size of 5 MB. After the log is completely filled, its contents are copied to a backup file lsmsSNMP.log.backup in the same directory, and actions are logged from the beginning of a fresh lsmsSNMP.log file.

For more information about what is logged in this file, see “Logging SNMP Agent Actions”.

Configuring the SNMP Agent

To configure trap forwarding, follow these general steps:

  1. Set the SNMP global mode as needed.

    See SNMP Global Mode.

    If the SNMPv1 ONLY mode is set, skip to step 5.

    Note:

    SNMPv1 provides no authentication and no privacy.
  2. Configure SNMPv3 views.

    See SNMPv3 Access View Management.

  3. Configure one or more SNMPv3 groups that use the SNMPv3 views.

    See SNMPv3 Group Management.

  4. Configure SNMPv3 users associated with the SNMPv3 groups.

    See SNMPv3 User Management.

  5. Configure the NMS on LSMS.

    See NMS Configuration.

  6. Configure the NMS.

    To see what was configured in step 5, use SNMP Configuration, and then NMS Configuration, and then Show.

SNMP Global Mode

LSMS supports three SNMP global modes:

  • SNMPv1 ONLY
  • SNMPv3 ONLY
  • Both

By default after a fresh installation or upgrade/re-installation, LSMS supports only the SNMPv3 ONLY global mode. SNMPv3 trap forwarding is recommended because of the encryption and secured authentication mechanisms provided.

For SNMPv1 trap forwarding, you can choose to change the SNMP global mode setting to Both or SNMPv1 ONLY.

Note:

SNMPv1 provides no authentication and no privacy.
The lsmsmgr user can change the SNMP global mode setting via menu option SNMP Configuration, and then SNMP Global Mode, and then choosing the Edit button. The following screen is displayed:

Figure 2-8 Set Global Mode


img/set_global_mode.jpg

Following are details on the SNMP global modes:

  • SNMPv1 ONLY

    Selecting this mode results in LSMS supporting only SNMPv1 as follows:

    • LSMS will forward SNMPv1 traps to only NMS(s) configured to support SNMPv1.
    • LSMS will allow addition of any new NMS that supports SNMPv1, and will not allow modification of an existing SNMPv1-based NMS to SNMPv3.
    • Prior to changing the mode to SNMPv3 ONLY, any NMS(s) configured (as in NMS Configuration) to support SNMPv1 must be removed.
  • SNMPv3 ONLY (recommended mode)

    Selecting this mode results in LSMS supporting only SNMPv3 as follows:

    • LSMS will forward SNMPv3 traps to only NMS(s) configured to support SNMPv3.
    • LSMS will allow addition of any new NMS that supports SNMPv3, and will not allow modification of an existing SNMPv3-based NMS to SNMPv1.
    • Prior to changing the mode to SNMPv1 ONLY, any NMS(s) configured (as in NMS Configuration) to support SNMPv3 must be removed. Changing the mode to SNMPv1 ONLY is not recommended.
  • Both

    Selecting this mode results in LSMS supporting both SNMPv1 and SNMPv3 as follows:

    • LSMS will forward traps to all NMS(s) configured to support SNMPv1 or SNMPv3.
    • LSMS will allow addition of any new NMS that supports SNMPv1 or SNMPv3.
    • LSMS will allow update of any NMS that supports SNMPv1 or SNMPv3.
    • Prior to changing the mode to SNMPv3 ONLY, any NMS(s) configured (as in NMS Configuration) to support SNMPv1 must be removed.
    • Prior to changing the mode to SNMPv1 ONLY, any NMS(s) configured (as in NMS Configuration) to support SNMPv3 must be removed. Changing the mode to SNMPv1 ONLY is not recommended.

SNMPv3 Access View Management

To support view-based access control for SNMPv3, LSMS provides the SNMP Configuration, and then SNMPv3 View Configuration, and then Add/Delete/Edit/Show menu options. These menu options are accessible only when the SNMP Global Mode is set to SNMPv3 ONLY or Both. Following is an example of the Add menu.

Figure 2-9 Add SNMPv3 View Screen


img/add_snmpv3_view.jpg

The SNMP Configuration, and then SNMPv3 View Configuration submenus include fields for the View Name and the OID of the associated LSMS MIB object.

View names must be unique, 1 - 32 alphanumeric characters in length, and are case sensitive. The OID associated with a view is mandatory.

The resyncVar object with OID 1.3.6.1.4.1.323.5.3.4.1.1.45 is the only object available in the LSMS MIB for read/write operations by a NMS. By default, LSMS provides a view named resyncVarView that is sufficient for controlling read/write access to the resyncVar object. The resyncVarView cannot be modified or deleted. Use of another OID for view configuration is not restricted.

A view that is associated to any group cannot be deleted. For information about groups, see SNMPv3 Group Management.

SNMPv3 Group Management

To support user-based security for SNMPv3, LSMS provides the SNMP Configuration, and then Group Configuration, and then Add/Delete/Edit/Show menu options. These menu options are accessible only when the SNMP Global Mode is set to SNMPv3 ONLY or Both. Following is an example of the Add menu.

Figure 2-10 Add Group Screen


img/add_group.jpg

The Group Name must be unique, 1 - 32 alphanumeric characters in length, and is case sensitive.

The Security Level is mandatory. Valid values are noAuthNoPriv, AuthNoPriv, and AuthPriv as shown in Table 2-6.

Table 2-6 SNMPv3 Security Levels

Level Authentication Encryption Details
noAuthNoPriv

(no authentication, no privacy)

 Username No Uses a username match for authentication
AuthNoPriv

(authentication, no privacy)

 Yes (SHA) No Provides authentication based on the algorithms available in the net-snmp API
AuthPriv (authentication and privacy) Yes (SHA) Yes (DES/AES) Provides authentication and encryption based on the algorithms available in the net-snmp API

The Read View name is optional, and must be specified exactly as configured in the view. The specified view must already be configured to be added to the group. If a read view is not selected for a group, the group will not have read access to any of the LSMS MIB objects.

The Write View name is optional, and must be specified exactly as configured in the view. The specified view must already be configured to be added to the group. If a write view is not selected for a group, the group will not have write access to any of the LSMS MIB objects.

A group that is associated with any user cannot be deleted. For information about users, see SNMPv3 User Management.

SNMPv3 User Management

To support user-based security for SNMPv3, LSMS provides the SNMP Configuration, and then User Configuration, and then Add/Delete/Edit/Show menu options. These menu options are accessible only when the SNMP Global Mode is set to SNMPv3 ONLY or Both. Following is an example of the initial Add menu.

Figure 2-11 Initial Add User Screen


img/add_user.jpg

The User Name must be unique, 1 - 50 alphanumeric characters in length, and is case sensitive.

The Group Name must be already configured to be specified for a user, and must exactly match (case sensitive) a configured group name.

After specifying valid values for the User Name and Group Name and selecting OK, display of another screen depends on the security level configured for the specified group:
  • If the security level configured for the specified group is noAuthNoPriv, user configuration is complete.
  • If the security level configured for the specified group is AuthNoPriv or AuthPriv, a second screen is displayed containing the configured security fields for the specified group. Following is an example for a group having the AuthPriv security level:

    Figure 2-12 Add User Screen for AuthPriv


    img/add_user2.jpg

    Note:

    When the security level configured for the specified group is AuthNoPriv, input fields Priv Protocol, and Priv Password will not be displayed.

    Select or specify the Auth Protocol, Auth Password, Priv Protocol, and Priv Password fields as needed:

    • The default and only valid value for Auth Protocol is SHA.
    • Valid values for Priv Protocol are DES and AES.
    • The Auth Password and Priv Password fields must be 8 - 255 characters in length. Valid characters include alphanumeric characters and the following special characters:
      • @
      • #
      • $
      • !

      The Auth Password and Priv Password fields are encrypted in the database.

A user that is associated with any NMS cannot be deleted. For information about associating a user with an NMS, see NMS Configuration.

NMS Configuration

To configure the NMS with which LSMS will interact to send alarms, LSMS provides the SNMP Configuration, and then NMS Configuration, and then Add/Delete/Edit/Show menu options. The specific screen/submenu displayed depends upon the SNMP global mode set in SNMP Global Mode (the default mode is SNMPv3 ONLY).

The following fields are common to all modes:
Name
The Name is a unique logical name for the NMS server consisting of 5 - 20 alphanumeric, case-sensitive characters. The Name is mandatory for SNMPv3 configuration and optional for SNMPv1 configuration.
IP
The IP must be non-empty and unique.
Port
The Port must be a valid value in the range 1 - 65535, excluding the pre-defined ports.
For the SNMPv1 ONLY mode, in addition to the common fields, the SNMP Community String field is also displayed. The SNMP Community String is mandatory and consists of 1 - 127 alphanumeric characters or the following special characters:
  • @
  • #
  • $
  • !

Figure 2-13 Add an NMS Server Screen for SNMPv1 ONLY


img/add_nms_v1.jpg

The community string is stored in encrypted form in the database.

For the SNMPv3 ONLY mode, in addition to the commone fields, the HeartBeat (sec) and User fields are also displayed.

Figure 2-14 Add an NMS Server Screen for SNMPv3 ONLY


img/add_nms_v3.jpg

Valid values for the HeartBeat (sec) field are 0 or between 5 - 7200, with a default value of 60.

The User field is mandatory, and must be specified exactly (case sensitive) as previously configured (see SNMPv3 User Management).

If the SNMP Global Mode is Both, all previous fields are displayed along with the SNMP Version field. Either v3 or v1 must be selected for SNMP Version.

Figure 2-15 Add an NMS Server Screen for Both


img/add_nms_both.jpg

When the SNMP Global Mode is Both, the SNMP Community String and User fields are mutually exclusive. The HeartBeat (sec) field is applicable only for SNMPv3.

Autonomous Events Trap Forwarding

The LSMS SNMP agent forwards all autonomous events generated at the LSMS, in the form of SNMPv1 traps to an NMS configured for SNMPv1 or SNMPv3 traps to an NMS configured for SNMPv3. A circular queue is maintained to support asynchronized trap requests so that traps are not missed if an NMS is disconnected from LSMS for any reason.

Trap forwarding from LSMS to an SNMPv3-based NMS is the same as to an SNMPv1-based NMS, except for the following:

  • A new varbind currentTime is introduced in the LSMS MIB to indicate the time when an alarm was generated.
  • A new varbind sourceIp is introduced in the LSMS MIB to include the source IP address of the network element in traps.
  • A new varbind alarmSequence is introduced in the LSMS MIB to maintain a sequence number with traps. The minimum sequence number value is 1 and the maximum value is 4294967295, after which the value will roll over.
  • The trap PDU includes additional information related to the USM entry for the NMS.
  • LSMS sends heartbeat traps to an NMS periodically to indicate that the connection is still up. The periodicity of the heartbeat trap is the HeartBeat (sec) value configured for the NMS.

Resynchronization

The MIB element resyncVar is supported and its value used to coordinate the alarm resynchronization process. The value is set to 1 to start resynchronization. Get and set operations are allowed only for resyncVar.

Connectivity between LSMS and NMS

LSMS listens at SNMP agent standard port 161 for Get/Set messages. When a Get/Set message is received, LSMS checks the Set message for validity (whether the v3 user that sent the Set request for resyncVar is valid and has permission to set the variable). If the request is valid, resyncVar is set and thereafter the alarm resynchronization mechanism (including error scenarios) between LSMS and the v3-based NMS will start.