1. EAGLE LNP Application Processor LNP Database Synchronization User's Guide
  2. Choosing a Database Maintenance Procedure

4 Choosing a Database Maintenance Procedure

After any network outage, the LSMS and network elements automatically attempt to resynchronize. This resynchronization occurs without operator intervention when the number of transactions that need to be retransmitted is less than or equal to the number that can be transmitted normally during a four-hour period under maximum provisioning load.

4.1 Choosing a Database Maintenance Procedure

This chapter describes the features required for resynchronization, and how to initiate and manage resynchronization from the LSMS. Resynchronization resends all transactions that were previously sent from the LSMS to the network element up to a maximum number of transactions or a maximum period of time.

4.2 Automatic Resynchronization Process

Automatic resynchronization is the process of automatically resending transactions that have occurred during an outage up to the number of transactions that could occur under the maximum provisioning load during an outage of up to four hours.

After any problem has been resolved that caused network outage between the LSMS and the network element, the LSMS and the network element’s Element Management System (EMS) perform the actions described in the following sections to begin automatic resynchronization (also called “short synchronization”). The process does not require operator intervention unless it is unsuccessful, in which case notifications are posted, as described in Notifications that Database Maintenance Is Required.

The following actions are part of the automatic resynchronization process:

  1. The Job Routing Server (JRS) of the active ELAP determines the database time stamp (DBTS) of both RTDBs (one on the active server and one on the standby server) and sends the DBTS that is the older of the two. An RTDB’s DBTS represents the last time the RTDB received an update from the LSMS.

  2. The LSMS determines how many transactions in the log file have a time stamp equal to or after the DBTS and does one of the following:

    • If the LSMS detects that the number of transactions requiring resynchronization exceeds the number that can be sent in four hours under maximum provisioning load, the LSMS posts at the LSMS notifications that database maintenance is required and sends a message to the network element indicating the automatic resynchronization cannot be performed. The active ELAP then sends the more recent DBTS of the two RTDBs (if the DBTS values were different), and this step is repeated. (If the more recent RTDB can be automatically resynchronized, you can copy the other RTDB from it after it has been automatically resynchronized, as described in Copying One RTDB from Another RTDB).

    • If the LSMS detects that the number of transactions requiring resynchronization is less than or equal to the number that can be sent in four hours under maximum provisioning load, the LSMS and EMS proceed with automatic resynchronization as described in steps #3 through #6.

  3. The LSMS displays the following notification at the LSMS user interface:

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

    Note:

    All notifications displayed during steps #3 through #6 are for information only; no user action is necessary.

  4. The LSMS stores all new updates arriving at the LSMS in the pending queue.

  5. In chronological order, the LSMS sends all transactions stored in the log file specific to the network element’s area of service. The chronological order starts at the first record that has a time stamp equal to or before the database time stamp (DBTS). For more information about DBTS, see Step 2. Although the resynchronization may result in duplicate messages, duplicate messages do not result in database errors. Also, if the LSMS is able to perform automatic resynchronization based on the older DBTS, any transactions sent to update the older RTDB but not needed by the newer RTDB are ignored by the newer RTDB.

  6. When resynchronization is complete, the LSMS displays the following notification at the LSMS user interface: 

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

    Automatic resynchronization is now complete; any updates stored in the LSMS pending queue are transmitted to the network element. Automatic resynchronization can occur for multiple network elements simultaneously.