1. EAGLE LNP Application Processor LNP Database Synchronization User's Guide
  2. Auditing and Reconciling Network Elements from the LSMS

5 Auditing and Reconciling Network Elements from the LSMS

This chapter describes how to audit network element data. In most cases, an audit of the subscription data contained on the network element can be initiated from the LSMS. An audit compares the subscription version data at the network element with that at the LSMS.

Introduction

This chapter describes auditing and optional reconciling of network element data. An audit compares the LNP data at the network element with that at the LSMS. At any time, except as noted in Audit and Reconcile Function Summary.

You can also choose to reconcile any discrepancies found during an audit. Reconciling allows you to update only the LNP database records that are found to be different during an audit.

Although auditing without reconciling does not result in synchronized LNP databases, you can perform an audit without a reconcile for information purposes.

Methods of Auditing and Reconciling

You can perform audits and optional reconciles in either of the following ways:

Operator Action at Network Element

An audit does not require any operator action at the network element. However, it is possible for the NE operator to disable the ability to process an audit. This is sometimes necessary when the NE operator is trying to debug a problem. If the NE operator has disabled the ability to process an audit, the LSMS will receive a rejection that is posted on the GUI as the following error message: 

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

If this message occurs, perform the procedure described in Enabling RTDBLSMS Audit on ELAP.

Types of Data to Audit and Reconcile

The LSMS offers the following types of audits that compare records in the LSMS to records in a specified network element:

  • Single SV/NPB Audit—This type allows you to audit a single subscription version or number pool block per supported network element at any time. If the audit reveals any discrepancy, you can choose to reconcile immediately.

  • Range Audit—You can audit the following types of ranges:

    • Time Range Audit—One or both of the following types of regional data found to have been created, modified, or deleted by the LSMS between the specified start and end date and time for the audit (which must be during the previous seven days.)

      • Subscription version data

      • Number pool block data

    • Object Range Audit—One or more of the following types of data that are stored in the LSMS databases within the specified range of starting and ending values:

      • Subscription version data

        • All TNs in the network element’s LNP database

        • All TNs within an NPA-NXX range

      • Number pool block data

        • All NPBs in the network element’s LNP database

        • Single SV/NPB

        • All NPBs within an NPA-NXX range

      • NPA Split data

        • All TNs in the network element’s LNP database with a specified Old NPA

        • All TNs within a specified Old NPA range

      • Default GTT data

        • All default GTTs in the network element’s LNP database with a specified NPA-NXX

        • All default GTTs within an NPA-NXX range

      • Override GTT data

        • All override GTTs in the network element’s LNP database with a specified LRN

        • All override GTTs within an LRN range

For more information about these types of data, refer to the Database Administrator's Guide for LSMS.

How Records Are Compared During an Audit

LNP data is determined to be out of synchronization by calculating a CRC (Cyclic Redundancy Check)-32 checksum for each specified type of LNP data record at both the LSMS and at the network element, and then comparing the checksums. If the checksums do not match, it is assumed that the records do not match.

Because some network element LNP database objects may contain attributes that are not stored in the LSMS LNP database, and vice versa, the computation of a checksum may not include all attributes. In addition, some attributes, such as LNP type, that are common to both the LSMS and network element LNP databases but which have different values, are not included in the computation of the checksums. Table 5-1 shows which attributes are included in checksums for each type of LNP data object.

Table 5-1 LNP Data Type Attributes Included in Checksums

LNP Data Type Attributes Included in Checksum Attributes Not Included in Checksum

NPA Split

  • Old NPA (Numbering Plan Area)

  • New NPA

  • NXX

  • Start PDP (Permissive Dialing Period)

  • End PDP

Number Pool Block

  • NPA-NXX-X

  • LRN (Location Routing Number)

  • DPC (Destination Point Code)

  • SSN (Subsystem Number)

  • LNP (Local Number Portability) type

  • SPID

Subscription Version

  • TN (Telephone Number)

  • LRN

  • DPC

  • SSN

  • LNP type

  • SPID

Default GTT

  • NPA-NXX

  • AIN (Advanced Intelligent Network)

  • IN (Intelligent Network)

  • TT (Translation Type)

  • DPC

  • SSN

  • RI (Routing Indicator)

  • XLAT (Translate Indicator)

  • NGT (New Global Title Translation Type); the LSMS stores the NGT as part of the NPA-NXX object, while the NE stores the NGT per point code

Override GTT

  • LRN

  • SPID

  • TT

  • DPC

  • SSN

  • RI

  • NGT

  • RGTA (Replace Global Title Address)

  • XLAT

Discrepancies Detected by Audit

An audit can detect the discrepancies shown in Table 5-2. Each discrepancy is counted, displayed on the GUI, and recorded in the audit log file (see Audit Error Messages).

Table 5-2 Audit Data Discrepancies

Discrepancy Type Description

Different

Mismatching checksums indicate that the network element has the LNP data object in its database; however, one or more attributes of the object are different from the equivalent attributes on the LSMS.

Missing

The network element’s LNP database does not contain this object, but the LSMS LNP database does contain it; the LSMS did not receive a checksum for this object.

Extra

The network element’s LNP database contains an object that the LSMS LNP database does not contain; the LSMS received a checksum for an object not in its database.

Duplicate Data Detected by Audit

In addition to detecting these discrepancies, all types of audit except auditing by time range also detect whether duplicate data resides in the LSMS and network element LNP databases. Duplicate data is not considered to be a discrepancy and cannot be corrected by performing a reconcile operation. Each duplicate LNP data object detected is counted and recorded in the audit log file. If duplicate LNP data is detected, contact the unresolvable-reference.html#GUID-4DCE85D7-E15B-482F-B188-B54BBCAD7463.

Note:

It is recommended that you correct any duplicates as soon as they are found, even before performing a reconcile. If the duplicates are not corrected, future audits may show these duplicates as different types of discrepancies at different times, and it will be more difficult to determine whether the discrepancies have been caused by originally duplicate data.

Displaying Audit Results

Results of an audit are made available in the following ways:

Reconciling

Any discrepancies detected during an audit can be optionally reconciled as soon as the audit completes in one of the following ways:

Starting with LSMS 8.X, any discrepancies detected during an Object Range audit can also be reconciled up to seven days later by selecting the Save Reconcile button at the completion of the audit and then later initiating a Post-Audit Reconcile (see Post-Audit Reconcile from the GUI).

Audit and Reconcile Function Summary

Table 5-3 shows the functions performed for each type of audit.

Table 5-3 Audit Types and Functions

Audit Type Rate Generates Audit Log Generates Full-Detail Discrepancy Log for SVs and NPBs Records Interrupted Audit Results Can Be Reconciled Later

Object Range

24 million records per hour

Yes

Yes

Yes

Yes

Time Range

100 records per second1

Yes

Yes

No

Yes

Single SV/NPB1

100 records per second1One record per second2

Yes

Yes

No

No

1Single SV/NPB Audits use the normal update channel, which can process 50 records per second, but performance of Single SV/NPB is limited by how fast the GUI can process the display, which may take up to five seconds.

Audit Restrictions

Before starting any audit, consider the following restrictions:

  • Only one Single SV/NPB audit of a given network element can be performed at a time. If you attempt to start a Single SV/NPB audit of a network element that is already performing a Single SV/NPB audit or reconcile, an error message will be posted and no additional audit action will occur. You can perform a Single SV/NPB audit for each supported network element simultaneously, and a Single SV/NPB audit can be performed on a given network element at the same time as a Range Audit is performed for that network element.

  • Only one Range audit or bulk load of a given network element can be performed at a time. If you attempt to start a Range audit of a network element that is already performing any other database synchronization operation, an error message will be posted and no additional audit action will occur. You can perform a Range audit for each supported network element simultaneously, subject to the restrictions described in Maximum Number of Simultaneous Synchronization Operations.

  • An audit performed at the same time that automatic resynchronization is occurring between the LSMS and the network element may result in false discrepancies because some of the LSMS data may not have been sent yet over the normal update connection to the network element. At the end of an audit, it is recommended that you determine whether an automatic resynchronization (also called short resynchronization) has occurred (look at the notifications area of the GUI). If an automatic resynchronization has occurred or is currently running, it is recommended that you perform another audit when the automatic resynchronization has completed.

  • A Range audit may time out at other times, for example, when the network element is busy or when synchronization is occurring between the Number Portability Administration Center (NPAC) and the LSMS. (For more information about when NPAC-to-LSMS synchronization occurs, refer to the Alarms and Maintenance Guide). If the LSMS is processing a lot of other data, the audit may eventually time out, a time-out message will be posted, and no audit action will occur.

In addition, consider the following usage note about Audit by Time Range:

  • Except in the case of a SV and/or NPB that has been deleted, the SV and/or NPB to audit will be retrieved from the LSMS database. For the case where an NPA Split has been created that changes the SV and/or NPB residing in the LSMS database, this feature will only audit the new, post-split SV and/or NPB. This is the case both during the NPA Splits’s permissive dialing period and after the period ends. For more information about NPA Splits, refer to the Database Administrator's Guide for LSMS.

Audit and Reconcile Timeline

This section provides an overview of how audit and reconcile is performed.

Single SV/NPB Audit and Reconcile Timeline

Figure 5-1 illustrates how data is sent to a network element before, during, and after a Single SV/NPB audit followed by a reconcile.

Figure 5-1 Timeline for a Single SV/NPB Audit with Reconcile


img/c_audit_and_reconcile_timeline_dbs-fig1.jpg

The following describes the stages in more detail:

T1

Single SV/NPB audit begins: The LSMS user decides to initiate a Single SV/NPB audit. To start the audit at the LSMS, see Managing Audit and Reconcile from the LSMS GUI. No action is required at the network element.

A single SV/NPB audit completes very quickly; the LSMS user cannot abort the operation.

When this stage is complete, the LSMS user can choose to reconcile immediately discrepancies that were found in the network element’s LNP database, start another audit, or terminate the audit session.

T2

Reconcile: The LSMS user decides to reconcile. To choose to reconcile, see 8 in Range Audit and Optional Reconcile from LSMS GUI . No action is required at the network element.

During this stage, a modify command is sent to the network element if the SV or NPB is identified as different or missing in the NE’s database, or a delete command is sent if the SV or NPB is identified as being extra in the NE’s LNP database (but not existing in the LSMS LNP database).

T3
Normal operations resume

Range Audit and Reconcile Timeline

Figure 5-2 illustrates how data is sent to a network element before, during, and after a range audit followed by a reconcile.

Figure 5-2 Timeline for a Range Audit with Reconcile


img/c_audit_and_reconcile_timeline_dbs-fig2.jpg

The following describes the range audit and reconcile stages in more detail:

T1

Range audit begins: The LSMS user decides to initiate a range audit. To start the audit at the LSMS, see Managing Audit and Reconcile from the LSMS GUI, 8. No action is required at the network element.

At any time during this stage, the LSMS user can choose to abort the operations. If aborted, the user can choose to terminate the operation (closing the Range Audit window), or start another range audit (either with the same ranges or different ranges).

Note:

Starting with LSMS Release 8.X, whenever an audit is interrupted, the LSMS records both completely and partially audited records in the Audit Log file. The user can examine the audit log file to determine which records have not yet been audited and perform another audit of a smaller set of records. For more information, see Continuing an Interrupted Object Range Audit.

When this stage is complete, the LSMS user can choose to reconcile immediately discrepancies that were found in the network element’s LNP database, start another audit, or terminate the audit session.

Note:

Starting with LSMS Release 8.X, the user can also choose to reconcile discrepancies at a later time.

T2

Reconcile: The LSMS user decides to reconcile. To choose to reconcile, see Range Audit and Optional Reconcile from LSMS GUI.

During this stage, modify commands are sent to the network element for all data identified as different and missing in the NE’s database, and delete commands are sent to the NE for all data identified as being extra in the NE’s LNP database (but not existing in the LSMS LNP database).

Some differences between the LSMS and NE databases (such as capacity) may cause the NE to reject some of the downloaded commands. These rejections would also occur during a normal update. All commands rejected by the network element are recorded in the audit log file (see Audit Error Messages).

At any time during this stage, the LSMS user can choose to abort the operations. If aborted, this operation can be either restarted or terminated.

T3
Normal operations resume.

Managing Audit and Reconcile from the LSMS GUI

This section describes the following audit and reconcile procedures you can perform through the LSMS GUI.

You can also perform certain audit and reconcile functions of SVs or NPBs or both using the lsmsclaa AUDIT function (see Performing an Audit Using the Command Line).

Audit Error Messages

For a listing of error messages that can appear on the GUI, along with explanation of possible cause and suggested recovery, see LSMS GUI Messages.

Single SV/NPB Audit and Optional Reconcile from LSMS GUI

Use the following procedure to manage from the LSMS user interface an audit and optional reconcile of a single subscription version or number pool block at a network element.

  1. Ensure that none of the restricted situations described in Audit and Reconcile Function Summary is occurring.
  2. Log in as a member of the lsmsadm, lsmsuser, lsmsuext, lsmsview, or lsmsall user group.

    Note:

    If you plan to perform a reconcile if one is needed, log in as a member of thelsmsuser,lsmsuext, orlsmsall user group.
  3. Because a Single SV/NPB Audit requires very little time, it is unlikely that an NPA Split will occur at the same time.
    However, if you plan to perform a reconcile, to ensure that the reconcile and NPA Split do not interfere, perform the following substeps:

    Note:

    Automatic split activation during a reconcile can cause the network element to be out of synchronization with the LSMS database.
    1. Generate an NPA Split Report.
      Select Pending for Status and All NPAC Regions for NPAC Region. For information about creating and viewing NPA Split Data Reports, refer to the Database Administrator's Guide for LSMS, (Chapter 5, “LSMS Reports”).
    2. Determine whether NPA Splits are scheduled to be activated during the time the audit and reconcile are to be performed:

      • If no Pending NPA Splits were listed in the report in Step 3a, or if none of the Pending NPA Splits has a PDP Start Date that occurs within the time period required to complete the audit and reconcile, go to 4.

      • If any Pending NPA Split has a PDP Start Date that occurs within the time period required to complete the audit and reconcile, continue with next substep.

    3. If any NPA Split is scheduled to be activated within the planned resynchronization period, delay the reconcile until after the NPA Split has been activated.
  4. Start the Audit window using either of the following:
    1. From the main menu on the LSMS Console window, select LSMS-> LNP Database Synchronization-> Single SV/NPB Audit -><CLLI>, where <CLLI> is the Common Language Location Identifier for the network element to be audited.
    2. Right-click the LSMS Console window’s EMS status icon that corresponds to the network element to be audited, and select LNP Database Synchronization-> Single SV/NPB Audit.
      The Single SV/NPB tab of the Audit window displays. If a different tab displays, click the Single SV/NPB tab. An example of this window is shown in Figure 5-3.

      Figure 5-3 Single SV/NPB Audit Window, Audit Range Tab


      img/t_single_sv_npb_audit_and_optional_reconcile_from_lsms_gui_dbs-fig1.jpg
  5. Do one of the following:
    1. Click the Single SV Object radio button and type the 10-digit TN value for the object you want to audit.
    2. Click the Single NPB Object radio button and type the 7-digit NPA-NXX-X value for the object you want to audit.
  6. To initiate the audit, click the Start button.
    The display automatically changes to the Audit Results tab.

    Note:

    It is generally not necessary to perform any action at the network element before starting an audit. However, it is possible for the NE operator to disable the ELAP’s ability to be audited. If the following error message is returned, contact the NE operator to request that the procedure described inEnabling RTDBLSMS Audit on ELAP be performed:
    Connection already in use or operation not enabled at NE ‘<IP address>’
    A single audit completes very quickly, and the popup message shown in Figure 5-4 displays.

    Figure 5-4 Single SV/NPB Audit Window, Audit Results Tab


    img/t_single_sv_npb_audit_and_optional_reconcile_from_lsms_gui_dbs-fig2.jpg
    Table 5-4 describes the meaning of the fields in this window.

    Table 5-4 Audit Results Fields

    Field Description Possible Values

    LSMS Total

    Number of data records that have been audited in the LSMS LNP database

    00000000—99999999

    NE Total

    Number of data records that have been audited in the NE LNP database

    00000000—99999999

    Same

    Number of LNP data records that are identical in both the LSMS and the NE LNP databases

    00000000—99999999

    Missing

    Number of LNP data records that are present in the LSMS LNP database, but not in the NE LNP database

    00000000—99999999

    Extra

    Number of LNP data records that are present in the NE LNP database, but not in the LSMS LNP database

    00000000—99999999

    Different

    Number of LNP data records that are present in both the LSMS LNP database and the NE LNP database, but with different checksums

    00000000—99999999

    Discrepancy Total

    Total number of LNP data record discrepancies (Missing, Extra, and Different)

    00000000—99999999

    Start Date/Time

    Time the audit phase was started

    MM/DD hh:mm:ss1

    End Date/Time

    Time the audit phase completed successfully or was abnormally terminated

    MM/DD hh:mm:ss1

    Elapsed Time

    Amount of time the audit took to complete or the amount of time the audit had run before the user aborted it or a failure occurred.

    hh:mm:ss1[A|F]2

    Full-Record Discrepancy Combobox

    List of LNP database objects whose full-record discrepancy file from the previous audit is available for viewing

    Number Pool Blocks or Subscription Versions

    1 MM indicates month, range 01—12

    DD indicates day, range 01—31

    hh indicates hour, range 00—23

    mm indicates minute, range 00—59

    ss indicates second, range 00—59

    2 A is appended at the end of the time is the operation is aborted.

    F is appended at the end of the time is the operation fails.
    To view the audit log file, click the View Log button. For more information about the log file, see Audit Error Messages.
  7. If a discrepancy is found, a discrepancy file is created, the Full-Record Discrepancy Log area becomes selectable, and the pull-down allows you to select which discrepancy file you would like to view.
    For more information about the discrepancy files, see Discrepancy Files.
  8. Examine the Audit Results tab to determine whether the object is listed as Missing, Extra, or Different and decide if you want to reconcile it.
    1. If you choose not to reconcile, click the Cancel button; you have now completed this procedure.
    2. If you choose to reconcile, click the Reconcile button.

      Note:

      The Reconcile button is selectable only if you have logged in as a member of the lsmsuser, lsmsuext, or lsmsall user group.
      The reconcile update is sent over the same connection as normal updates. When the reconcile completes, a window similar to the example shown in Figure 5-5 displays.

      Figure 5-5 Reconcile Complete


      img/t_single_sv_npb_audit_and_optional_reconcile_from_lsms_gui_dbs-fig3.jpg
      Click OK; you have now completed this procedure.

Range Audit and Optional Reconcile from LSMS GUI

Use the following procedure to manage from the LSMS user interface a Time Range audit or Object Range audit and optional reconcile of data at a network element.

  1. Ensure that none of the restricted situations described in Audit and Reconcile Function Summary is occurring.
  2. Log in as a member of the lsmsadm, lsmsuser, lsmsuext, lsmsview, or lsmsall user group.

    Note:

    If you plan to perform a reconcile if one is needed, log in as a member of thelsmsuser,lsmsuext, orlsmsall user group.
  3. If you plan to perform a reconcile, perform the following substeps to ensure that no NPA Split is scheduled to occur during the time required to perform the audit with reconcile.

    Note:

    Automatic split activation during a reconcile can cause the network element to be out of synchronization with the LSMS database. To avoid this problem, first perform the following substeps.
    1. Generate an NPA Split Report.
      Select Pending for Status and All NPAC Regions for NPAC Region. For information about creating and viewing NPA Split Data Reports, refer to the Database Administrator's Guide for LSMS, (Chapter 5, “LSMS Reports”).
    2. Determine whether NPA Splits are scheduled to be activated during the time the audit and reconcile are to be performed (to estimate time required to perform the audit and reconcile, see Synchronization Performance Estimates):

      • If no Pending NPA Splits were listed in the report in Step 3a, or if none of the Pending NPA Splits has a PDP Start Date that occurs within the time period required to complete the reconcile, go to 4.

      • If any Pending NPA Split has a PDP Start Date that occurs within the time period required to complete the audit and reconcile, continue with next substep.

    3. If any NPA Split is scheduled to be activated within the planned resynchronization period, delay the reconcile until after the NPA Split has been activated.
  4. Start the Audit window using either of the following:
    1. From the main menu on the LSMS Console window, select LSMS-> LNP Database Synchronization->Range Audit-><CLLI>, where <CLLI> is the Common Language Location Identifier for the network element to be audited.
    2. Right-click the LSMS Console window’s EMS status icon that corresponds to the network element to be audited, and select LNP Database Synchronization->Range Audit.
      The Audit Range tab of the Audit window displays. If a different tab displays, click the Audit Range tab. An example of this window is shown in Figure 5-6.

      Figure 5-6 Audit Window, Audit Range Tab


      img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig1.jpg
  5. Select the data you want to audit by doing one of the following:
    1. Click the All Database Objects radio button to audit all objects in the network element’s LNP database.
    2. To audit all subscription versions and number pool blocks within a specified time range, click the NPB and SV Database Objects in Specified Time Range radio button.
      The Start Date/Time and End Date/Time fields become active and display in the form MM/DD/YY hh:mm:ss <AM|PM>, where MM represents month, DD represents day, YY represents year, hh represents hour, mm represents minute, and ss represents second. To change any of these values, double click on the value so that it is highlighted and then click the up or down arrow to increment or decrement the value by one for each click on the arrow. For example to change 10/09/01 12:00:00 AM to 10/12/01 12:00:00 PM, double click the day field (09) and click the up arrow 3 times, then double-click the AM field and click the up arrow once. These fields have the following constraints:

      • The Start Date/Time must be seven days or less than the current date and time.

      • The End Date/Time must be equal to or greater than the Start Date/Time.

      • The End Date/Time must be equal to or less than the current date and time.

    3. To audit a subset of all objects in the network element’s LNP database, click the All Database Objects in Specified Data Range radio button, and then for each data type, click the pull-down arrow at the right of the box, and select the desired data range for that object.
      Table 5-5 shows the possible values available in the pull-down for each data type.

      Table 5-5 Audit Range Values

      Data Type Pull-down Values Constraints Results

      NPA Splits

      • None

      • All

      • Old NPA Range

      If OLD NPA Range is selected, two fields appear; specify a range by entering the starting OLD NPA value in the first field and enter the ending OLD NPA value in the second field. Each value must consist of 3 numeric digits in the range 200—999.

      Only those NPA Splits within the specified range will be audited. If no ending value is specified, the ending value defaults to the same value as the starting value.

      Number Pool Blocks*

      • None

      • All

      • NPA-NXX Range

      If NPA-NXX Range or NPA-NXX-X Range is selected, two fields appear; specify a range by entering the starting NPA-NXX or NPA-NXX-X value in the first field and enter the ending NPA-NXX or NPA-NXX-X value in the second field.

      For NPA-NXX Range, each value must consist of 6 numeric digits in the range 200000—999999 (do not use hyphens or periods).

      For NPA-NXX-X Range, the NPA-NXX must be the same for the starting and ending NPA-NXX-X values and each value must consist of 7 numeric digits in the range 2000000—9999999 (do not use hyphens or periods). An audit of this type is performed only over the normal update connection.

      Only those Number Pool Blocks that have an NPA-NXX or NPA-NXX-X within the specified range will be audited. If no ending value is specified, the ending value defaults to the same value as the starting value.

      Subscription Versions*

      • None

      • All

      • NPA-NXX Range

      If NPA-NXX Range or TN Range is selected, two fields appear; specify a range by entering the starting NPA-NXX or TN value in the first field and enter the ending NPA-NXX or TN value in the second field.

      For NPA-NXX Range, each value must consist of 6 numeric digits in the range 200000—999999 (do not use hyphens or periods).

      For TN Range, the NPA-NXX must be the same for the starting and ending TN values and each value must consist of 10 numeric digits in the range 2000000—9999999 (do not use hyphens or periods). An audit of this type is performed only over the normal update connection.

      Only those Subscription Versions that have an NPA-NXX or TN within the specified range will be audited. If no ending value is specified, the ending value defaults to the same value as the starting value.

      Default GTTs*

      • None

      • All

      • NPANXX Range

      If NPANXX Range is selected, two fields appear; specify a range by entering the starting NPA-NXX value in the first field and enter the ending NPA-NXX value in the second field.

      Each value must consist of 6 numeric digits in the range 200000—999999 (do not use hyphens or periods).

      Only those Default GTTs that have an NPA-NXX within the specified range will be audited. If no ending value is specified, the ending value defaults to the same value as the starting value.

      Override GTTs

      • None

      • All

      • LRN Range

      If LRN Range is selected, two fields appear; specify a range by entering the starting LRN value in the first field and enter the ending LRN value in the second field.

      Each value must consist of 10 numeric digits in the range 0000000000—9999999999 (do not use hyphens or periods).

      Only those Override GTTs that have an LRN within the specified range will be audited. If no ending value is specified, the ending value defaults to the same value as the starting value.

      * If any value other than None is selected for Subscription Versions, Number Pool Blocks, or Default GTTs, you must either select All for NPA Splits or select Old NPA and specify a range of 200—999.

  6. To initiate the audit, click the Start button.
    The display automatically changes to the Audit Results tab (shown in Figure 5-7), and the Start button is replaced by the Abort button.

    Note:

    It is generally not necessary to perform any action at the network element before starting an audit. However, it is possible for the NE operator to disable the ELAP’s ability to be audited. If the following error message is returned, contact the NE operator to request that the procedure described inEnabling RTDBLSMS Audit on ELAPbe performed:Connection already in use or operation not enabled at NE ‘<IP address>’
    The progress is indicated by start time, elapsed time, numbers appearing in the various columns for the selected data types, and status reported in the status field at the bottom of the window.

    Figure 5-7 Audit Window, Audit Results Tab


    img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig2.jpg
    Table 5-6 describes the meaning of the fields in this window.

    Table 5-6 Audit Results Fields

    Field Description Possible Values

    LSMS Total

    Number of data records that have been audited in the LSMS LNP database

    00000000—99999999

    NE Total

    Number of data records that have been audited in the NE LNP database

    00000000—99999999

    Same

    Number of LNP data records that are identical in both the LSMS and the NE LNP databases

    00000000—99999999

    Missing

    Number of LNP data records that are present in the LSMS LNP database, but not in the NE LNP database

    00000000—99999999

    Extra

    Number of LNP data records that are present in the NE LNP database, but not in the LSMS LNP database

    00000000—99999999

    Different

    Number of LNP data records that are present in both the LSMS LNP database and the NE LNP database, but with different checksums

    00000000—99999999

    Discrepancy Total

    Total number of LNP data record discrepancies (Missing, Extra, and Different)

    00000000—99999999

    Start Date/Time

    Time the audit phase was started

    MM/DD hh:mm:ss1

    End Date/Time

    Time the audit phase completed successfully or was abnormally terminated

    MM/DD hh:mm:ss1

    Elapsed Time

    Amount of time the audit took to complete or the amount of time the audit had run before the user aborted it or a failure occurred.

    hh:mm:ss1[A|F]2

    Full-Record Discrepancy Combobox

    List of LNP database objects whose full-record discrepancy file from the previous audit is available for viewing

    Number Pool Blocks or Subscription Versions

    1 MM indicates month, range 01—12

    DD indicates day, range 01—31

    hh indicates hour, range 00—23

    mm indicates minute, range 00—59

    ss indicates second, range 00—59

    2 A is appended at the end of the time is the operation is aborted.

    F is appended at the end of the time is the operation fails.

    To view the audit log file, click the View Log button. For more information about the log file, see Audit Error Messages.

    To abort while an audit is in progress, click the Abort button. A confirmation dialog displays, as shown in Figure 5-8.audit

    Figure 5-8 Abort Operation Dialog


    img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig3.jpg
    1. Click the Yes button to immediately terminate the operation in progress.
      If the LSMS has already started to create full-record discrepancy files, the operation does not stop until the full-record discrepancy files are fully created. If you want to reconcile any discrepancies found before the audit was aborted, perform the procedure described in Post-Audit Reconcile from the GUI
    2. Click the No button to close the Abort confirmation dialog and return back to the main Audit window with no other effect.
  7. When the audit completes, an information dialog similar to Figure 5-9 displays.

    Figure 5-9 Audit Complete Information Dialog


    img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig4.jpg
  8. When the audit completes or is terminated, the Audit window displays similar to the example shown in Figure 5-10.
    In this example, discrepancies in SVs and NPBs have been found, so a discrepancy file for each category has been created, the Full-Record Discrepancy Log area has become selectable, and the pull-down allows you to select which discrepancy file you would like to view. If you wish to view both files, first view one file, then view the other. For more information about the discrepancy files, see Discrepancy Files.

    Figure 5-10 Audit Complete


    img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig5.jpg
    Examine the Audit Results tab to determine whether any objects are listed as Missing, Extra, or Different and decide if you want to reconcile them.
    1. If you choose not to reconcile, click the Cancel button; you have now completed this procedure.
    2. If you choose to reconcile later, click the Save Reconcile button.
      When you are ready to perform the reconcile, follow the procedure described in Post-Audit Reconcile from the GUI.
    3. If you choose to reconcile immediately, ensure that you have considered any possible NPA Splits as described in 3; then click the Reconcile Now button.

      Note:

      The Reconcile Now button is selectable only if you have logged in as a member of the lsmsuser, lsmsuext, or lsmsall user group.
      Reconcile updates are sent over the same connection as normal updates. When the reconcile completes, a window similar to the example shown in Figure 5-11 displays.

      Figure 5-11 Reconcile Complete


      img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig6.jpg
      Click OK; a window similar to the example shown in Figure 5-12 displays.

      Figure 5-12 Reconcile Operation Complete


      img/t_range_audit_and_optional_reconcile_from_lsms_gui_dbs-fig7.jpg
      Click OK; you have now completed this procedure.

Post-Audit Reconcile from the GUI

Starting with LSMS release 8.X, a reconcile of an Object Range Audit can be performed at a time later than immediately after an audit completes. This function can be used in the following situations:

  • If a large number of discrepancies is found during an audit, you might want to postpone the reconcile until a later time to avoid impacting normal traffic.

  • If an Object Range Audit is aborted or interrupted, you can perform a Post-Audit Reconcile for all of the objects that were successfully audited before the interruption. You can also examine the Audit log to determine which objects were successfully audited, and perform another audit for objects that were not completely audited (for more information, see Continuing an Interrupted Object Range Audit).

The Post-Audit reconcile function is enabled by the creation of a Reconcile file that contains all the discrepant data found during the corresponding audit. Reconcile files are kept eight days and then deleted.

Note:

Any reconcile (whether immediate or postponed) can be performed only once. When a reconcile has been performed, the reconcile file is no longer available for selection from the Post-Audit Reconcile window.

To perform a Post-Audit reconcile, perform the following procedure to choose among the available reconcile files.

  1. Log in as a member of the lsmsuser, lsmsuext, or lsmsall user group.
  2. Perform the following substeps to ensure that no NPA Split is scheduled to occur during the time required to perform the reconcile.

    Note:

    Automatic split activation during a reconcile can cause the network element to be out of synchronization with the LSMS database.
    1. Generate an NPA Split Report.
      Select Pending for Status and All NPAC Regions for NPAC Region. For information about creating and viewing NPA Split Data Reports, refer to the Database Administrator's Guide for LSMS, (Chapter 5, “LSMS Reports”).
    2. Determine whether NPA Splits are scheduled to be activated during the time the reconcile is to be performed (to estimate time required to perform the reconcile, see Synchronization Performance Estimates:

      • If no Pending NPA Splits were listed in the report in Step 2a, or if none of the Pending NPA Splits has a PDP Start Date that occurs within the time period required to complete the reconcile, go to 4.

      • If any Pending NPA Split has a PDP Start Date that occurs within the time period required to complete the reconcile, continue with next substep.

    3. If any NPA Split is scheduled to be activated within the planned resynchronization period, delay the reconcile until after the NPA Split has been activated.
  3. Start the Post-Audit Reconcile window using either of the following:
    1. From the main menu on the LSMS Console window, select LSMS-> LNP Database Synchronization->Post-Audit Reconcile-><CLLI>, where <CLLI> is the Common Language Location Identifier for the network element to be audited.
    2. Right-click the LSMS Console window’s EMS status icon that corresponds to the network element to be audited, and select LNP Database Synchronization->Post-Audit Reconcile.
      The Input File table of the Post-Audit Reconcile window displays. If a different tab displays, click the Input File tab. An example of this window is shown in Figure 5-13.
  4. Click the Browse button and select the file that corresponds to the audit you wish to now reconcile.
    The example in Figure 5-13 shows a file has been selected.

    Figure 5-13 Post-Audit Reconcile Window, Input File Tab


    img/t_post_audit_reconcile_from_the_gui_dbs-fig1.jpg
  5. Click Start.
    After the LSMS finds the file to use for reconciling, the Post Audit Reconcile pop-up window shown in Figure 5-14 displays.

    Figure 5-14 Post Audit Reconcile Initialized


    img/t_post_audit_reconcile_from_the_gui_dbs-fig2.jpg
  6. Click OK.
    The Audit Results window displays, an example is shown in Figure 5-15.

    Figure 5-15 Audit Results Tab


    img/t_post_audit_reconcile_from_the_gui_dbs-fig3.jpg
  7. Ensure that you have considered any possible NPA Splits as described in 2; then click the Reconcile Now button.
    Reconcile updates are sent over the same connection as normal updates. When the reconcile completes, a window similar to the example shown in Figure 5-16 displays.

    Figure 5-16 Reconcile Complete


    img/t_post_audit_reconcile_from_the_gui_dbs-fig4.jpg
  8. Click OK; a window similar to the example shown in Figure 5-17 displays.

    Figure 5-17 Reconcile Operation Complete


    img/t_post_audit_reconcile_from_the_gui_dbs-fig5.jpg
    Click OK; you have now completed this procedure.

Performing an Audit Using the Command Line

Use the following procedure to perform a network element audit and optional reconcile of subscription versions (SVs) or Number Pool Blocks (NPBs) through the LSMS command line interface (lsmsclaa).

Note:

Starting with LSMS Release 8.X, the lsmsclaa AUDIT command can be used only to perform a Single SV or NPB Audit.

The lsmsclaa command does not display a progress bar or provide a way to cancel the audit while in progress. Results of the audit performed by this command are stored in the LsmsAudit.log file (see Audit Error Messages) and in discrepancy files (see Discrepancy Files).

For more information about using the lsmsclaa command, refer to the Alarms and Maintenance Guide.

Use this procedure to perform an audit of SVs or NPBs from the command line.

  1. Ensure that none of the restricted situations, as described in section Audit and Reconcile Function Summary, are occurring.
  2. To perform an audit only, log into the LSMS as a member of any user group.

    Note:

    If you need to perform a reconcile, log in as a member of thelsmsadm,lsmsuser,lsmsuext, orlsmsall user group.
  3. If you plan to perform a reconcile, perform the following substeps to ensure that no NPA Split is scheduled to occur during the time required to perform the audit with reconcile.

    Note:

    Automatic split activation during a reconcile can cause the network element to be out of synchronization with the LSMS database. To avoid this problem, first perform the following substeps.
    1. Generate an NPA Split Report.
      Select Pending for Status and All NPAC Regions for NPAC Region. For information about creating and viewing NPA Split Data Reports, refer to the Database Administrator's Guide for LSMS, (Chapter 5, “LSMS Reports”).
    2. Determine whether NPA Splits are scheduled to be activated during the time the audit and reconcile are to be performed (to estimate time required to perform the audit and reconcile, see Synchronization Performance Estimates):

      • If no Pending NPA Splits were listed in the report in this section, Step 3a, or if none of the Pending NPA Splits has a PDP Start Date that occurs within the time period required to complete the reconcile, go to 4.

      • If any Pending NPA Split has a PDP Start Date that occurs within the time period required to complete the audit and reconcile, continue with next substep.

    3. If any NPA Split is scheduled to be activated within the planned resynchronization period, delay the reconcile until after the NPA Split has been activated.
  4. Start the command-line interface by entering the following command with parameters as defined in Table 5-7: 
    $ $LSMS_DIR/start_cmdLine <SPID> <REGION> [<COMMANDFILE>]

    Table 5-7 Parameters Used by Command-Line Interface

    Parameter Description Required? Characters

    <SPID>

    Service Provider ID

    Yes

    4

    <REGION>

    Name of NPAC region

    Yes

    (Note)

    6 to 11

    <COMMANDFILE>

    Full name of a text file that contains a series of commands to be run by the command-line interface utility

    No

    1 to 256

    Note: To start the LSMS command line interface, you must specify one of the following values for <REGION>: Canada, Midwest, MidAtlantic, Southeast, Southwest, Northeast, Western, or WestCoast.
  5. The following prompt indicates that the command-line interface has started: 
    
Enter command ->
  6. Enter the following command at the command-line interface prompt (see Table 5-8 for a description of the command arguments): 
    audit <CLLI> <StartValue> [<ObjectType>] [reconcile] [details]

    Table 5-8 Audit Command Parameters

    Argument Name

    Description

    Required?

    Values

    <CLLI>

    Common Language Location Identifier of the network element whose LNP database is to be audited and optionally reconciled.

    Yes

    1–11 alphanumeric

    <StartValue>

    The argument represents the single SV or NPB value to be audited.

    Yes

    • For NPB, 7 numeric characters in range 2000000 to 9999999

    • For SV or ALL, 10 numeric characters in range 2000000000 to 9999999999

    <ObjectType>

    One of the following to indicate which data types in the specified range to audit:

    • NPB—audit only Number Pool Blocks.

    • SV—audit only subscription versions.

    • ALL—audit both Number Pool Blocks and subscription versions.

    Default is one of the following:

    • If<StartValue>has 7 digits, the default is NPB

    • If<StartValue>has 10 digits, the default is ALL

    No

    NPB or SV or ALL

    reconcile

    If this parameter is present, any discrepancies found by the audit are reconciled. (If the user is not a member of thelsmsuser,lsmsuext, orlsmsall groups, this parameter is ignored.)

    No

    N/A

    details

    If this parameter is present, status information is output every 5 seconds and includes audit discrepancy and reconcile download statistics.

    No

    N/A
  7. The command-line interface displays a message to indicate whether the audit or audit with reconcile was successful.
    For more information about the possible messages, refer to the Alarms and Maintenance Guide. You have now completed this procedure.

Audit Logs

Audit log files are generated for Range Audits that are initiated either from the GUI or from the command line. One log file is created for each day that a Range audit is performed. The log file is named LsmsAudit.log.<MMDD>, where <MMDD> is the timestamp that contains month and day. This log file is located in the directory /var/TKLC/lsms/logs/<CLLI>, where <CLLI> is the Common Language Location Identifier of the network element being audited. Log files are maintained for seven days after they are created; then they are automatically removed from the LSMS.

Note:

No log file is generated for a Single SV/NPB Audit.

Viewing Audit Log Files

You can view audit log files in either of the following ways

  • If you are performing a Range audit from the GUI, any time after a Range audit has begun, you can view the audit log file by clicking the View Log button. If the browser window used for displaying reports and logs is not already open, it is opened automatically and displays the log file.

  • You can also use one of the following methods to open the window shown in Figure 5-18 used to browse for this log:

    Figure 5-18 Browsing for Audit Log Files


    img/c_audit_log_file_dbs-fig1.jpg

    • Select Logs, and then Other... from the main menu of the LSMS Console window.

    • Click on the LSMS Console window’s EMS Status Icon that corresponds to the network element being audited so that the icon is highlighted. Right-click and select Logs, and then LNP Database Synchronization, and then Audit.

      Scroll down to find the folder that has the <CLLI> name for the NE that is being audited. Double-click the folder name, and then double click the file name LsmsAudit.log.<MMDD> that corresponds to the month and day you desire.

Audit Log File Contents

Whenever a Range audit is started, the audit log file for that day is appended (if this is the first audit of the day, the file is created). For each audit performed on that day, the audit log file contains information similar to the information displayed on the Audit Range, Audit Results, and Download Results tabs, such as start and end times for each stage, and numbers of missing, extra, and different objects in various LNP categories. The log and window also record whether database entries are present at the LSMS but missing at the NE, present at the NE but missing at the LSMS, or present at both the LSMS and NE but containing different values.

The audit log file contains the following sections:

  • Header Section

  • Audit Section

  • Reconcile Section

  • Summary Section

    Note:

    Starting with LSMS Release 8.X, summary sections for Object Range Audits indicate whether object types were completely audited, partially audited, or not audited, and shows results for both completely and partially audited object types.

Audit Log File Example for Two Completed Audits

Figure 5-19 shows an example of an audit log file that contains two separate audits and reconciles performed on the same day.

Figure 5-19 Example of an Audit Log File for Two Completed Audits


img/c_audit_log_file_dbs-fig2.jpg

img/c_audit_log_file_dbs-fig3.jpg

Audit Log File Example for a Partially Completed Audit

Figure 5-20 shows an example of an audit log file for an Object Range Audit that was interrupted.

Figure 5-20 Example of Audit Log File for Partially Completed Audit


img/c_audit_log_file_dbs-fig4.jpg

img/c_audit_log_file_dbs-fig5.jpg

Continuing an Interrupted Object Range Audit

Starting with LSMS Release 8.X, if an Object Range Audit is interrupted, you can interpret the contents of the audit log file to determine how many objects were completely audited. After the interruption has been resolved, you can complete your original audit goal by performing the following actions in any order (the file shown in Figure 5-20 is used as an example):

  • Perform a Post-Audit Reconcile (see Post-Audit Reconcile from the GUI), selecting the Partial Reconcile File listed in the Audit log (<CLLI>.reconcileFile. 0606144036.tar.gz in the example file). This Post-Audit Reconcile will reconcile the three discrepancies found in the Subscription Version range from 919550 to 919554 (there were no discrepancies found in the NPA Splits).

  • Perform another Range audit and reconcile of just SVs in the range 910555 to 910559.