LNP Database Synchronization Files

C LNP Database Synchronization Files

This appendix describes the files that are recorded when the various types of LNP database synchronization are performed.

C.1 Introduction

This appendix describes the contents of the following files that are created for LNP Database Synchronization operations.

A log file is created to record the results of each audit or electronic bulk load (see Log Files).
After an audit, the LSMS user has the option to view a discrepancy file that shows the full records at both the LSMS and at the network element for any discrepancies found in subscription versions or number pool blocks (see Discrepancy Files).

C.2 Log Files

When the LSMS user starts an audit, or electronic bulk load operation, the LSMS creates a log file to record the results of the operation.

Location of LNP Database Synchronization Log Files

Table C-1 shows the names of various LNP database synchronization log files and the directories where they are stored. In this table, <CLLI> indicates the Common Language Location Identifier of the network element for which the LNP database synchronization operation is performed, and <MMDD> indicates the month and day the operation was performed. Log files are maintained only for a period of seven days; after a log file has been stored seven days, it is automatically deleted.

Table C-1 LNP Database Synchronization Log File Directories

LNP Database Synchronization Operation	Log File Directory and Name
Audit	/var/TKLC/lsms/logs/<CLLI>/LsmsAudit.log.<MMDD>
Electronic bulk load	/var/TKLC/lsms/logs/<CLLI>/LsmsBulkload.log.<MMDD>

Viewing an LNP Database Synchronization Log File

An LNP database synchronization log file can be viewed in any of the following ways:

By clicking the View Log button on the window used to start the operation any time after the operation has started
By selecting Logs>Other... from the main LSMS menu; in the file chooser dialog that displays, scroll to find the directory named <CLLI>, where <CLLI> is the Common Language Location Identifier (CLLI) of the network element the operation is performed for, double-click the directory to open it, and double-click the file name that corresponds to the month and day the operation was performed
By highlighting the EMS status icon for the network element the operation is performed for, right-clicking and selecting Logs>LNP Database Synchronization><operation>, where <operation> is the operation being performed; in the file chooser dialog that displays, double-click the file name that corresponds to the month and day the operation was performed

C.2.1 LNP Database Synchronization Log File Contents

An LNP database synchronization log file consists of a number of sections. Table C-2 shows which sections are present for each type of log file. The sections are described in Header Section .

Table C-2 LNP Database Synchronization Log File Contents

Log File Section	LNP Database Synchronization Operation Type A=Audit/Reconcile, B=Bulk Load, R=Resync
Header	A, B, R
Audit	A
Reconcile	A
Bulk Load	B
Re-sync	A, B, R
Summary	A, B, R
Download Commit/Discard	B, R

Header Section

The log file for every type of LNP database synchronization has a header section, which includes:

Name of the user that started the operation
Common Language Location Identifier (CLLI) of the network element for which the operation is performed
Date and time a connection was established with the network element
IP address and port number of the network element for which the operation is being performed

Figure C-1 shows an example of a header section.

Figure C-1 Header Section Example

img/c_lnp_database_synchronization_log_file_contents_dbs_fig1.jpg

Audit Section

The log file for every type of audit has an audit section, which includes:

Type of LNP data currently being audited
Date and time the audit started and completed

List of duplicates and discrepancies found in the network element’s LNP database for the type of data being audited. The list contains:

LNP data type’s key field, as shown in Table C-3

Table C-3 LNP Data Type Key Fields

LNP Data Type	Key Field
Subscription version (SV)	TN
Number pool block (NPB)	NPA-NXX-X
NPA Split	Old NPA
Default GTT	NPA-NXX
Override GTT	LRN

Type of discrepancy, as described in Table C-4

Table C-4 LNP Data Type Key Fields

Discrepancy Type	Meaning
DUPLICATE	Receiving a checksum more than once for the same LNP object from the LSMS or the NE indicates that a duplicate LNP object exist.
MISSING	Not receiving a checksum for a LNP object that resides in the LSMS database indicates that the NE is missing that LNP object.
EXTRA	Receiving a checksum for a LNP object from the NE that does not reside in the LSMS database indicates that the NE has an extra LNP object which needs to be deleted.
DIFFERENT	Mismatching checksums indicate that the NE has the LNP data object in its database; however, one or more attributes of that LNP data object (for example. LRN) are different from the one on the LSMS.

For duplicate NPBs or SVs found in the LSMS LNP database, the NPAC regions in whose databases the duplicates reside

Figure C-2 shows an example of an audit section.

Figure C-2 Audit Section Example

img/c_lnp_database_synchronization_log_file_contents_dbs_fig2.jpg

Reconcile Section

When the user chooses to reconcile at the end of any type of audit, the log file for the audit has a reconcile section, which includes:

Date and time the reconcile started and completed
The following information for all commands that failed or were rejected by the network element (the maximum number of command rejections logged per operation is 100,000):
- Date
- Time
- Failure reason
- Command name
- Attributes

Figure C-3 shows an example of a reconcile section.

Figure C-3 Reconcile Section Example

img/c_lnp_database_synchronization_log_file_contents_dbs_fig3.jpg

Bulk Load Section

The log file has a bulk load section, which includes:

Date and time the bulk load started and completed
The following information for all commands that failed or were rejected by the network element (the maximum number of command rejections logged per operation is 100,000):
- Date
- Time
- Failure reason
- Command name
- Attributes

Figure C-4 shows an example of a bulk load section.

Figure C-4 Bulk Load Section Example

img/c_lnp_database_synchronization_log_file_contents_dbs_fig4a.jpg

img/c_lnp_database_synchronization_log_file_contents_dbs_fig4b.jpg

Resynchronization Section

The log files contain a resynchronization section. In addition, the LNP database synchronization operations contain a resynchronization section; these operations use the automatic resynchronization function of the LSMS to transmit all data updates that may have been received at the LSMS during the time the LNP database operation was occurring.

The resynchronization section includes:

Date and time the resynchronization started and completed
Network element’s LNP database timestamp (DBTS)
The following information for all commands that failed or were rejected by the network element (the maximum number of command rejections logged per operation is 100,000):
- Date
- Time
- Failure reason
- Command name
- Attributes
Network element’s LNP DBTS after the resynchronization operation completed

Figure C-5 shows an example of a resynchronization section.

Figure C-5 Resynchronization Section Example

img/c_lnp_database_synchronization_log_file_contents_dbs_fig5a.jpg

img/c_lnp_database_synchronization_log_file_contents_dbs_fig5b.jpg

C.2.1.1 Summary Section

Every LNP database synchronization log file contains a summary section. The contents of the summary section depends on the type of LNP database synchronization operation, as described in the following sections:

Summary Section for Audit Operation

The log file for an audit includes an audit summary section, which includes:

Range (data or time) of the LNP data type audited
Total number of LNP data objects audited on both the LSMS and the network element
Total number of LNP data objects that are identical on both the LSMS and the network element
Total number of LNP data objects found for each type of discrepancy and total number of discrepancies
The following items, which are included only when duplicates are detected:
- Total number of LNP data objects found to be duplicate on the LSMS
- Total number of LNP data objects found to be duplicate on the NE
- A note explaining that duplicate data cannot be corrected by performing a reconcile

Figure C-6 shows an example of a audit summary section for an audit performed for an NPA-NXX range.

Figure C-6 Audit Summary Section Example for NPA-NXX Range

Figure C-7 shows an example of a audit summary section for an audit performed for a time range.

Figure C-7 Audit Summary Section Example for Time Range

Summary Section for Download Operations

Electronic bulk load synchronization operations have a period during which LNP data is downloaded to the network element without being interspersed with normal data updates.

The log files for these types of operations includes a download summary section, which includes:

Total number of objects that were successfully downloaded and applied to the network element’s LNP database
Total number of objects that were successfully downloaded to, but rejected by, the network element

Figure C-8 shows an example of a download summary section.

Figure C-8 Download Summary Section Example

C.2.1.2 Download Commit/Discard Section

The log files for the following types of LNP database synchronization operations include a download commit/discard section:

Electronic bulk load
User-initiated resynchronization

The download commit/discard section includes:

Date and time the download started and completed
Status of the commit or discard request

Figure C-9 shows an example of a reconcile section.

Figure C-9 Download Commit/Discard Section Example

C.3 Discrepancy Files

After an audit has completed, the LSMS user has the option of viewing full records information about any subscription version (SV) or number pool block (NPB) data objects that were found to be missing, extra, or different.

Location of Discrepancy Files

Table C-5 shows the names of the two types of discrepancy files and the directories where they are stored. In this table, <CLLI> indicates the Common Language Location Identifier of the network element for which the audit was performed, and <MMDD> indicates the month and day the audit was performed. Log files are maintained only for a period of seven days; after a log file has been stored seven days, it is automatically deleted.

Table C-5 LNP Database Synchronization Log File Directories

LNP Data Object Type	Full-Record Discrepancy File Directory and Name
Subscription version	/var/TKLC/lsms/logs/<CLLI>/LsmsAudit.sv.discrepancy.log.<MMDD>
Number pool block	/var/TKLC/lsms/logs/<CLLI>/LsmsAudit.npb.discrepancy.log.<MMDD>

Viewing a Discrepancy File

An LNP database synchronization log file can be viewed in any of the following ways:

By clicking the View Discrepancies button on the Audit Results tab of the Audit window used to start an audit of SVs or NPBs any time after the audit has completed
By selecting Logs>Other... from the main LSMS menu; in the file chooser dialog that displays, scroll to find the directory named <CLLI>, where <CLLI> is the Common Language Location Identifier (CLLI) of the network element the operation is performed for, double-click the directory to open it, and double-click the file name that corresponds to the month and day the operation was performed
By highlighting the EMS status icon for the network element the operation is performed for, right-clicking and selecting Logs>LNP Database Synchronization-><operation>, where <operation> is the operation being performed; in the file chooser dialog that displays, double-click the file name that corresponds to the month and day the operation was performed

C.3.1 Discrepancy File Contents

A discrepancy file consists of a the following sections:

Header section (see Header Section)
Discrepancy section (see Discrepancy Section)
Summary section (see Discrepancy Summary Section)

Header Section

Each type of discrepancy file contains a header section, which includes:

Date and time the discrepancy file was generated
Name of the user that started the operation
Common Language Location Identifier (CLLI) of the network element for which the operation is performed

Figure C-10 shows an example of a header section.

Figure C-10 Example of a Discrepancy File Header Section

img/c_discrepancy_file_contents_dbs_fig1.jpg

Discrepancy Section

Each type of discrepancy file contains a discrepancy section, which includes:

Date and time the discrepancy file was generated
Type of LNP data discrepancy
Side-by-side comparison of LSMS and network element LNP data records (including attributes names and values)

A full-record discrepancy file contains up to a maximum of 1000 discrepancies.

Figure C-11 shows an example of a discrepancy section for an audit of Number Pool Blocks (NPBs).

Figure C-11 Discrepancy Section Example, Audit of NPBs

img/c_discrepancy_file_contents_dbs_fig2.jpg

Figure C-12 shows an example of a discrepancy section for an audit of subscription versions (TNs).

Figure C-12 Discrepancy Section Example, Audit of TNs

img/c_discrepancy_file_contents_dbs_fig3.jpg

Discrepancy Summary Section

Each type of discrepancy file contains a summary section, which includes:

Total number of each type of discrepancy included in the report
Date and time the discrepancy file was completed

Figure C-13 shows an example of a discrepancy summary section.

Figure C-13 Discrepancy Summary Section Example

img/c_discrepancy_file_contents_dbs_fig4.jpg