Returning Operation from Shadow LSMS to Main LSMS

Use the procedures described in this section to return operations from the shadow LSMS to the main LSMS after the main LSMS has been restored. Do not take the shadow LSMS out of service until you have completed this procedure, including the resynchronization of LNP data with the NPAC and network elements. If any problem occurs during the restoration of operations to the main LSMS, you can return to using the shadow LSMS.

In addition to the assumptions listed in “Preparing for a Disaster Situation”, the following conditions are assumed:

The main LSMS is restored at the same physical site. If another site is used, you must perform site survey and preparation as you do for any initial LSMS installation. For more information about installing LSMS, refer to Application B Card Hardware and Installation Guide.
A network connection exists between the restored main LSMS and each NPAC and network element.
Encryption keys have been exchanged between the NPAC and the restored main LSMS.
License keys are valid for the main LSMS.
At the main LSMS, valid backups exist for all data.
At a previously inactive shadow LSMS, valid backups exist for all data. A complete backup should be scheduled immediately before the scheduled return to the main LSMS, so that no locally provisioned data is entered after the switch back to the main LSMS.

Perform the procedures shown in Table 1 to restore the main LSMS.

Procedures to Return Operations from Shadow LSMS to Main LSMS
Restoring Operations to the Main LSMS After Running on Active Shadow Main LSMS	Restoring Operations to the Main LSMS After Running on Previously Inactive Shadow	In the order shown in the appropriate column, perform the following recovery procedures:
1	1	Contact the My Oracle Support (MOS) to arrange repair or replacement of the LSMS. Oracle will dispatch technicians who will perform repairs and return the LSMS to operational status.
2	2	Recovery acceptance test or manufacturing acceptance test, depending on the severity of original failure (performed by technicians).
3	3	After the My Oracle Support (MOS) personnel have performed an acceptance test, if desired, customers may wish to perform the following tests to verify that the restored main LSMS is fully functional: Verifying the State of the Servers Verifying the Processes Running on the Active Server (with primary server as active server) Verifying the GUI Operability on the Active Server (with primary server as active server) Manually Switching Over from the Active Server to the Standby Server Verifying the Processes Running on the Active Server (with secondary server as active server) Verifying the GUI Operability on the Active Server (with secondary server as active server) Manually Switching Over from the Active Server to the Standby Server
3	4	If any NPAC data may be updated during the period of time between when you plan to disconnect the shadow LSMS and connect with the main LSMS, contact each NPAC from which the LSMS needs data and request download files for that time period.
	5	If returning from a shadow LSMS that was previously inactive, contact each NPAC from which the LSMS needs data to provide them with the IP address with which to establish association to the main LSMS.
4	6	If any download files were requested from any NPAC above, FTP the files and import them into the LSMS (see Downloading Files from an NPAC to the LSMS).
5	7	Start the LSMS GUI.
6	8	Perform the procedures in “Reconnecting Network Elements”, where the source LSMS is the shadow LSMS, and the destination LSMS is the main LSMS.
7	9	For each network element, perform a time-range audit (specify the start time to be one hour before the outage occurred) and a full-range audit of DGTT, OGTT, and NPA Splits. For information about performing audits, refer to “Audit and Optional Reconcile from the LSMS GUI” in the LNP Database Synchronization User's Guide.
8, 9, 10	10, 11, 12	If any query servers are installed: Stop the directly connected query servers. Configure each directly connected query server to use the main LSMS as its master host (refer to the procedure described in “MySQL Replication Configuration for Query Servers” in the Configuration Guide. For each directly connected query server, perform the procedure in “Reload a Query Server Database from the LSMS”.