1. EAGLE LNP Application Processor LNP Database Synchronization User's Guide
  2. LSMS GUI Messages

A LSMS GUI Messages

This section lists the messages that can appear in the LSMS GUI, and provides a description and recovery for each message.

Introduction

This appendix lists, in alphabetical order, the messages that can appear when you are using the LSMS graphical user interface (GUI) functions described in this book. For each message, this appendix shows the probable cause for the message, which LSMS LNP Database Synchronization GUI functions the message can appear for, and suggested recovery steps if the message indicates an error situation.

For information about other messages that may occur during the procedures described in this manual, refer to one of the following:

GUI Messages

A TN filter has not been assigned to the EMS

May Occur During: Any LNP database synchronization operation

Explanation

The attempted operation cannot be performed until a TN filter is assigned to the EMS. The operation is not started.

Recovery

Assign one or more regional TN filters or a single custom TN filter to the EMS for which the operation is being performed (for information about assigning TN filters, refer to the Database Administrator's Guide for LSMS) and try the operation again.

An LNP DB synchronization operation is already in progress for NE

May Occur During: Any LNP database synchronization operation

Explanation

The attempted operation cannot be performed because another LNP database synchronization operation is already in progress for that network element. Only one bulk load, audit, or re-synchronization operation for a given network element can be initiated at one time.

Recovery

Wait until the LNP database synchronization operation currently in progress completes and try the operation again. If the error persists, contact your system administrator to determine whether a user at another location may still have an LNP database synchronization operation window open for this network element.

Audit input queue failure

May Occur During: Audit

Explanation

The auditor was attempting to read LSMS data to be audited, but that queue had a failure. The audit is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Audit input queue shutdown

May Occur During: Audit

Explanation

The auditor was attempting to read LSMS data to be audited, but that queue was shut down. The audit is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Audit input queue timeout. Please contact Technical Services.

May Occur During: Audit

Explanation

The auditor was attempting to read LSMS data to be audited, but that queue has stayed empty too long. The audit is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Audit NE input queue failure.

May Occur During: Audit

Explanation

The auditor was attempting to read network element data to be audited, but that queue had a failure. The audit is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Audit NE input queue shutdown

May Occur During: Audit

Explanation

The auditor was attempting to read data to be audited from the network element, but that queue was shut down. The audit is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Audit NE input queue timeout. Please contact Technical Services.

May Occur During: Audit

Explanation

The auditor was attempting to read data to be audited from the network element, but no response was received in the allowed time. The audit is not completed.

Recovery

Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Auditing of <objType> is not supported by the NE

May Occur During: Audit

Explanation

An audit was attempted to be performed on a network element that does not support the object type indicated by <objType>, where <objType> is one of the following:

  • NPA Split

  • Number Pool Blocks

  • Subscription Versions

  • Default GTTs

  • Override GTTs

The audit is not performed.

Recovery

Select “All Database Objects in Specified Ranges” radio button and select only the object types that are supported by the version of software running on the network element.

Bulk Load is required. NE's LNP DB timestamp (<timestamp>) is invalid

May Occur During: Reconcile

Explanation

The network element's LNP database timestamp (DBTS) is invalid. The operation is not started.

Recovery

A bulk download is required. Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Bulk Load is required. NE's LNP DB timestamp (<timestamp>) is older than 7 days

May Occur During: Reconcile

Explanation

The LSMS user attempted to reconcile or resynchronize a network element's LNP database whose DBTS is older than seven days. (The transaction logs needed to perform this operation go back only seven days.) The operation is not started.

Recovery

A bulk download is required.

Connection already in use at NE '<IP address>'

May Occur During: Any non-ELAP-based LNP database synchronization operation

Explanation

An attempt was made to start an LNP database synchronization operation to a network element for which an LNP database synchronization operation is already running. The operation is not performed.

Recovery

  1. Examine the notifications area of the LSMS GUI to determine whether another LNP database synchronization operation is already running.

    Note:

    Look for event numbers 8066 through 8085 and read the message text to determine what has occurred

    If another LNP database synchronization operation is in progress, wait until it has completed, and try your operation again.

  2. If this error still occurs, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Connection already in use or operation not enabled at NE '<IP address>'

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to start an LNP database synchronization operation to a network element for which one of the following is true:

  • An LNP database synchronization operation is already running

  • The ELAP is not enabled to receive the operation

The operation is not performed

Recovery

  1. Examine the notifications area of the LSMS GUI to determine whether another LNP database synchronization operation is already running.

    Note:

    Look for event numbers 8066 through 8085 and read the message text to determine what has occurred

    If another LNP database synchronization operation is in progress, wait until it has completed, and try your operation again.

  2. Contact the NE operator to determine whether the ELAP has been enabled for this synchronization operation.

  3. If this error still occurs, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Disk space in <directory> is insufficient for operation

May Occur During: Audit

Explanation

The directory identified by <directory> is used for storing temporary files. It does not have sufficient space to perform the operation. The audit is not performed.

Recovery

Remove all unnecessary files from the specified directory (to determine the amount of disk space needed for the operation, look at the LSMSTrace.log). Try the operation again.

EBDA session ID already in use. Retry operation

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to start an LNP database synchronization operation to a network element using a session ID that was already in use by another LNP database synchronization operation. The operation did not start.

Recovery

Try the operation again.

ELAP architecture does not support LNP quantity requested

May Occur During: Feature Activation

Explanation

The EAGLE prevents the feature quantities from being enabled and activated without the proper ELAP operating system.

Recovery

Check the version of the ELAP operating system and the Service Module cards installed. Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463 to verify the requirements.

Error in receiving NE data (errno=<nnn>)

May Occur During: Any LNP database synchronization operation

Explanation

An error occurred while waiting to receive a message from the network element. The operation is not completed. The connection was probably dropped.

Recovery

Find out why the error occurred and try it again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed aborting operation in progress

May Occur During: Any LNP database synchronization operation

Explanation

The operation in progress cannot be aborted.

Recovery

Look in the LSMSTrace.log for the reason for the failure. Correct the problem and retry the operation. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed committing data downloaded to the NE

May Occur During: Any LNP database synchronization operation

Explanation

The operation was not completed. One of the following may have occurred:

  • The NE operator canceled the download

  • A timeout occurred while waiting for an acknowledgement

  • The connection has been dropped

Changes have not been committed, so the download has had no effect.

Recovery

Try the operation again.

Failed connecting to NE '<IP address>'

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to start an operation to a network element, but an error prevented the establishment of the connection. The operation is not performed.

Recovery

Verify that the displayed IP address is correct. Then, try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed discarding data downloaded to the network element’s LNP database

May Occur During: Any LNP database synchronization operation

Explanation

The operation was not completed. One of the following may have occurred:

  • A timeout occurred while waiting for an acknowledgement

  • The connection has been dropped

  • The network element operator has canceled the download

Recovery

Try the operation again.

Failed initializing EBDA process

May Occur During: Any LNP database synchronization operation

Explanation

An error occurred during the initialization of the EBDA process. The operation is not performed.

Recovery

Look in the LSMSTrace.log for the reason for the failure. Correct the problem and retry the operation. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed receiving data over normal update connection with NE (errno=<nn>)

May Occur During: Audit only or audit and reconcile

Explanation

An attempt was made to read a message from the network element, but no response was received in the allowed time. The cause may be a dropped connection with the network element. The operation is not performed.

Recovery

Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed sending data over normal update connection with NE (errno=<nn>

May Occur During: Audit and reconcile

Explanation

A failure occurred while auditing or reconciling the network element’s LNP database using the normal update connection with the network element. The operation is terminated.

Recovery

To determine the reason for failure, look in the LSMSTrace.log. Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Failed starting operation

May Occur During: Any LNP database synchronization operation

Explanation

The requested operation failed to start.

Recovery

Look in the LSMSTrace.log for the reason for the failure. Correct the problem and retry the operation. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

LSMS’s normal update connection with NE is not currently established

May Occur During: Audit and Reconcile

Explanation

The LSMS user attempted to perform an operation that requires the normal update, but that connection is not currently established. The normal update connection is the connection between the LSMS and one of the following at the MPS. The operation is not started.

Recovery

Establish the connection and try the operation again.

Maximum number of discrepancies has been reached - Bulk Load required

May Occur During: Audit

Explanation

The maximum number of discrepancies that can be detected in the network element’s LNP database by an audit before a bulk load is required has been reached. The operation is terminated.

Recovery

Perform a Bulk Load operation to the network element (for more information, see “Choosing a Synchronization Procedure”).

Maximum number of simultaneous Bulk Load LNP DB synchronization operations has been reached

May Occur During: Bulk Load

Explanation

The LSMS user attempted to perform a Bulk Load LNP database synchronization operation while the maximum permitted number of Bulk Load operations are currently in progress. The operation was not started.

Recovery

Try the operation again.

Maximum number of simultaneous LNP DB synchronization operations has been reached

May Occur During: Any LNP database synchronization operation

Explanation

The LSMS user attempted to perform an LNP database synchronization operation while the maximum permitted number of LNP database synchronization operations are currently in progress. The operation was not started.

Recovery

Try the operation again.

NE dropped the connection (errno=<nn>)

May Occur During: Any LNP database synchronization operation

Explanation

A message was sent to the network element, but the network element dropped the connection without sending a response message. The operation has failed.

Recovery

Try the operation again. If the problem persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

NE has reset the connection (errno=<nn>)

May Occur During: Any LNP database synchronization operation

Explanation

A message was sent to the network element, but the network element reset the connection without sending a response message. The operation has failed.

Recovery

Try the operation again. If the problem persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Network element is currently being re-synced with the LSMS. Operation terminated.

May Occur During: Audit only or audit and reconcile

Explanation

The user attempted to perform an operation that uses the normal update connection with the network element while an automatic resynchronization (also called a short synchronization) is in progress. The operation is not started.

Recovery

  1. Use one of the listed methods:

    • Method A

      Look in the notifications area of the LSMS GUI console window for the listed notifications, where <CLLI> is the Common Language Location Identifier for the network element for which you wish to perform the operation.

      1. Verify that this notification has been posted:

        
[Major]: <Timestamp> 8054 <CLLI>: Short Synchronization Started

      2. Wait until this notification is posted before trying the operation again:

        
[Cleared]: <Timestamp> 8059 <CLLI>: Short Synchronization Complete

    • Method B

      Perform these steps to determine whether the eagle agent process is currently using the normal update connection:

      1. Log in to the active server as lsmsadm.

      2. Enter the command:

        $LSMS_DIR/eagle status <CLLI>

      3. Examine the output to determine whether the eagle agent is currently resynchronizing with the network element.

  2. Try the operation again.

One or more NPAC regions in the regional TN filter are set inactive

May Occur During: Any LNP database synchronization operation

Explanation

The regional TN filters for the EMS of this network element include at least one NPAC region that is currently set to inactive. The operation is not performed.

Recovery

  1. Use one of the listed methods:

    • Method A

      Activate all NPAC regions that are selected in the EMS’s regional TN filter:

      1. On the LSMS GUI console window, right-click anywhere in the NPAC status area and ensure that all NPAC regions are selected.

        This ensures that even inactive regions are displayed on the console window.

      2. From the main menu, select LSMS, and then EMS Routing, and then View.

      3. Determine whether any of the NPAC regions highlighted in the View EMS Routing window have an inactive status on the console.

      4. Activate those NPAC regions by right-clicking the NPAC status icon and selecting Associate.

    • Method B

      Deselect all inactive NPAC regions that are selected in the EMS’s regional TN filter :

      1. On the LSMS GUI console window, right-click anywhere in the NPAC status area and ensure that all NPAC regions are selected.

        This ensures that even inactive regions are displayed on the console window

      2. From the main menu, select LSMS, and then EMS Routing, and then View.

      3. Select only the NPAC regions that have active status on the console.

      4. Click OK.

  2. Try the operation again.

One or more NPAC regions must be set active

May Occur During: Any LNP database synchronization operation

Explanation

There are currently no active NPAC regions. The operation is not performed.

Recovery

  1. Activate all NPAC regions that are selected in the EMS’s regional TN filter, by right-clicking anywhere in the NPAC status area in the LSMS GUI console window and ensuring that all NPAC regions are selected.

    This ensures that even inactive regions are displayed in the console window.

  2. From the main menu, select LSMS, and then EMS Routing, and then View.

  3. Determine whether any of the NPAC regions highlighted in the View EMS Routing window have an inactive status on the console.

  4. Activate those NPAC regions by right-clicking the NPAC status icon and selecting Associate.

  5. Try the operation again.

Operation automatically terminated - client unexpectedly disconnected

May Occur During: Any LNP database synchronization operation (only recorded in log file)

Explanation

The operation in progress is terminated. The Local Service Manager (lsman) server process terminated its connection with the EBDA process.

Recovery

Verify that the lsman process is running using the sup status command (for information about using this command, refer to the Maintenance manual for LSMS.

  • If the lsman process is currently running, it may have been automatically restarted since the LNP database synchronization operation was attempted. Try the operation again.

  • If the lsman process is not currently running, it should be restarted automatically within a few minutes. Wait a few minutes and repeat the sup status command. If it is now running, try the operation again.

If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Operation forcefully terminated by external process

May Occur During: Any LNP database synchronization operation (only recorded in log file)

Explanation

The operation in progress is terminated. The LSMS user has logged out while an LNP database operation is in progress.

Recovery

Log back in and try the operation again.

Out of memory

May Occur During: Audit

Explanation

The operation process discovered it was out of heap space when sending a message to another thread within this operation. The operation is not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Problem with the NE connection (errno=<nn>)

May Occur During: Any LNP database synchronization operation

Explanation

An attempt to send a message to the network element failed with an unexpected error. The operation did not complete.

Recovery

Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Protocol violation on connection with NE. Please contact Technical Services.

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to send a message to the network element, but the network element was not in the proper state to accept that kind of message. Probably the network element is in a reset state because the connection was dropped or the network element operator issued a chg-db:action=canceled command. The operation was not completed.

Recovery

Try the operation again. A different error message should appear. Follow the recovery procedure recommended for that error message.

Re-sync operation is not permitted while the LSMS is connected with the NE

May Occur During: User-initiated resynchronization

Explanation

The user attempted to initiate a resynchronization when the LSMS is connected to the network element.

Recovery

When the LSMS has a connection to the MPS, there is no need for a user-initiated resynchronization. If the connection to the MPS is down and this error still appears, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Received unexpected response from the NE

May Occur During: Audit

Explanation

A message that is neither a normal response nor any of the expected error responses was received from the network element in response to an audit request. The audit is not completed.

Recovery

Try the operation again. If the problem persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Received unexpected response over normal update connection - protocol violation

May Occur During: Audit only or audit and reconcile

Explanation

A message that is neither a normal response nor any of the expected error responses was received from the network element over the normal update connection in response to an audit or update request. The operation is terminated.

Recovery

Try the operation again. If the problem persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

The entire range of NPA Splits must be selected if auditing NPBs, SVs and/or Default GTTs

May Occur During: Audit

Explanation

The user attempted to initiate an audit of one or more of the following without specifying the entire range of NPA Splits:

  • Default GTTs

  • NPBs by NPA-NXX range

  • SVs by NPA-NXX range

The operation is not started. (An audit by time range or of NPBs by NPA-NXX-X range and/or SVs by TN range does not require or support auditing of NPA Splits.)

Recovery

Select one of the following values for the Old NPA range and try the operation again:

  • ALL

  • 200-999

Timeout connecting to NE. IP-address '<IP address>' (errno=<nnn>)

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to start an operation to a network element, but the connection was not established because of an unexpected error. The operation is not performed.

Recovery

Verify that the displayed IP address is correct, then try again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Timeout receiving data from the NE

May Occur During: Any LNP database synchronization operation

Explanation

An attempt was made to read a message from the network element (NE), but no response was received in the allowed time. The operation is not completed. The connection was probably dropped.

Recovery

Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Timeout sending data to NE (errno=<nn>)

May Occur During: Any LNP database synchronization operation

Explanation

Too much time elapsed while trying to send a message to the network element. The operation is not completed. The connection was probably dropped.

Recovery

Find out why the timeout occurred, and try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Unable to access normal update connection

May Occur During: Audit only or audit and reconcile

Explanation

The EBDA process was not able to connect to an eagle agent process to perform the requested synchronization operation to an NE’s LNP database. Either the eagle agent is not running or it is currently performing an automatic resynchronization with the LSMS. The operation is not performed.

Recovery

Do the following:

  1. Use the eagle status command to verify that the eagle agent process is running (for information about using this command, refer to the Maintenance manual for LSMS).

  2. If the eagle agent process is not running, contact the system administrator to determine whether the eagle agent process was manually stopped. If it was not manually stopped, it should be automatically restarted soon.

  3. Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Unable to connect to EBDA process

May Occur During: Any LNP database synchronization operation

Explanation

Although the EBDA process started when the LNP database synchronization operation was started through the GUI, by the time the Local Services Manager (lsman) needed to connect to an EBDA process to start the requested synchronization operation to an NE’s LNP database, it was unable to connect. The operation is not performed.

Recovery

Do the following:

  1. Log in to the active server as root.

  2. Determine whether the EBDA process is running by entering the following command, where <CLLI> is the Common Language Location Identifier for the network element for which you wish to perform an LNP database synchronization operation:

    ps -ef|grep ebda|grep -v <CLLI>

  3. If no output appears, the EBDA process is no longer running, so try the operation again.

  4. If output appears, the EBDA process is running although the lsman process is unable to connect to it. Enter the following command to kill the EBDA process (where <pid> is the process ID returned by the command in step 2), and then try the operation again.

    kill -SIGKILL <pid>

  5. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Unable to start EBDA process

May Occur During: Any LNP database synchronization operation

Explanation

The Local Services Manager (lsman) was not able to start an EBDA process for the requested synchronization operation to an NE’s LNP database. The operation is not performed.

Recovery

Try the operation again. If the error persists, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Unknown EBDA session ID. Connection to EBDA process has been lost

May Occur During: Any LNP database synchronization operation

Explanation

In the course of performing the operation, the EBDA process died. The operation was not completed.

Recovery

Contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

User is not authorized to perform operation to NE’s LNP database

May Occur During: Any LNP database synchronization operation

Explanation

SPID security is enabled. The LSMS user is not authorized to perform the LNP database synchronization operation for the specified network element. The operation was not started.

Recovery

Contact your system administrator to be given authorization to access the data of the login SPID.