NPAC Key Exchange Rollback Procedure

Asset ID:	1-77-2382700.1
Update Date:	2018-04-05
Keywords:

Solution Type Sun Alert Sure

Solution 2382700.1 : NPAC Key Exchange Rollback Procedure

Applies to:

Oracle Communications EAGLE (Software) - Version LSMS 13.3 to LSMS 13.3 [Release LSMS 13.0]
Oracle Communications LSMS
Information in this document applies to any platform.

Description

If for some reason the rollback of the region from iconectiv to Neustar becomes necessary, this document will provide guidelines to perform the action.

The First section of this document should be executed BEFORE the loading of the iconectiv keys to facilitate a rollback to Neustar, should it become necessary.

Occurrence

The rollback of the regions to Neustar is a very remote possibility, but this document will provide guidance should this become necessary.

Symptoms

If the LSMS region should need to be rolled back to the Neustar NPAC, the iconectiv keys will need to be removed from the system to facilitate the connection to Neustar.

First Section - A)
A.1. Have only Neustar keys load.
If iconectiv keys are loaded, you "keyutil" to delete them

A.2. As user root, cd to the /var/TKLC/lsms/db/supDB directory

[root@lsmspri ~]# cd /var/TKLC/lsms/db/supDB/

A.3. As user root, stop the mysql process

[root@lsmspri supDB]# service mysql stop
Shutting down MySQL... SUCCESS!

A.4. As user root, take a backup of the database

[root@lsmspri supDB]# tar -czvf supDB.tar.gz *

AlarmFilter.frm
... OUTPUT FILTERED ...
WesternPublicKey.MYI

A.5. As user root, verify the hastatus reports ACTIVE

[root@lsmspri supDB]# hastatus
ACTIVE

A.6. As user root, start the mysql service

[root@lsmspri supDB]# service mysql start
Starting MySQL.. SUCCESS!

A.7. As user root, copy /var/TKLC/lsms/db/supDB/supDB.tar.gz to mate LSMS

[root@lsmspri supDB]# scp -p /var/TKLC/lsms/db/supDB/supDB.tar.gz mate:/var/TKLC/lsms/db/supDB/supDB.tar.gz
FIPS integrity verification test failed.
supDB.tar.gz 100% 1463KB 1.4MB/s 00:00

Second Section B) Connecting to iconectiv:

After performing the steps in Section A, perform the following steps to prepare for the connection to iconectiv:

B.1. ABORT ASSOCIATION

B.2. su to the lsmsadm user

[root@lsmspri supDB]# su - lsmsadm

B.3 As user lsmsadm, remove the private and public keys

[lsmsadm@lsmspri bin]$ keyutil -r Southwest -k private -x 1
There are keys to be deleted.
Ok to make changes? yes

[lsmsadm@lsmspri bin]$ keyutil -r Southwest -k public -x 1
There are keys to be deleted.
Ok to make changes? yes

B.4 Load the iconectiv keys

B.5. Use "keyutil" to set correct "InUse" key if necessary

Third Section C) Connecting Back to Neustar (Rollback)

To connect back to Neustar:

C.1 As user root, cd to /var/TKLC/lsms/db/supDB

[root@lsmspri ~]# cd /var/TKLC/lsms/db/supDB/

C.2. As user root, stop the mysql process

[root@lsmspri supDB]# service mysql stop
Shutting down MySQL... SUCCESS!

C.3. Extract the backup taken in Section A

[root@lsmspri supDB]# tar -xzvf supDB.tar.gz

C.4. Verify that the ownership of the file is still dbadm.dbadm

C.5 As user root, start the mysql service

[root@lsmspri supDB]# service mysql start
Starting MySQL.. SUCCESS!

C.6. Repeat steps on mate

C.7. As user lsmsadm, Use "keyutil" to set correct "InUse" key if necessary

History

04-04-2018 Initial Publication

Attachments

This solution has no attachment