Perform security preconfiguration

If the NFM-P TLS certificate requires an update to function in the IPv6 system, generate and distribute the required TLS files for the system, as described in NSP TLS configuration.

Clear failed deployments

Clear all outstanding failed deployments; see the NSP NFM-P User Guide for information about how to view and manage failed deployments.

Back up configuration files

Make a backup copy of the /opt/nsp/nfmp/server/nms/config/nms-server.xml file on each main server station.

Copy the file to a secure location that is unaffected by the conversion.

Gather required information

Obtain and record the following information for each main database:

• root user password

Obtain and record the following information for each main and auxiliary server:

• root user password

• nsp user password

Close unrequired clients

Close the open NFM-P GUI and XML API client sessions.

1. Open an NFM-P GUI client using an account with security management privileges, such as admin.

2. Choose Administration→Security→NFM-P User Security from the main menu. The NFM-P User Security - Security Management (Edit) form opens.

3. Click on the Sessions tab.

4. Click Search. The form lists the open GUI and XML API client sessions.

5. Identify the GUI session that you are using based on the value in the Client IP column.

6. Select all sessions except your current session and click Close Session.

7. Click Yes to confirm the action.

8. Click Search to refresh the list and verify that only the current session is open.

9. Close the NFM-P User Security - Security Management (Edit) form.

Close LogViewer

Close the LogViewer utility, if it is open.

Verify database archive log synchronization

If the NFM-P system is redundant, ensure that no database archive log gap exists between the primary and standby main databases.

Note: If you attempt a conversion to IPv6 when an archive log gap exists, the conversion fails.

1. In the open client GUI, view the Standby DB entry in the status bar.

2. If the entry reads “Database archive log gap”, you must reinstantiate the standby database. Otherwise, go to Step 10.

3. Choose Administration→System Information from the main menu. The System Information form opens.

4. Click Re-Instantiate Standby.

5. Click Yes to confirm the action. The reinstantiation begins, and the GUI status bar displays reinstantiation information.

   Note: Database reinstantiation takes considerable time if the database contains a large amount of statistics data.

   You can also use the System Information form to monitor the reinstantiation progress. The Last Attempted Standby Re-instantiation Time is the start time; the Standby Re-instantiation State changes from In Progress to Success when the reinstantiation is complete.

6. When the reinstantiation is complete, close the System Information form.

Verify database alignment

If the NFM-P system is redundant, ensure that the main database that you want as the primary database is the current primary database.

Note: This step may involve a main database switchover, which can take considerable time.

1. In the open client GUI, choose Administration→System Information from the main menu. The System Information form opens.

2. View the IP Address and Hostname values in the Primary Database Server panel and the Preferred DB setting in the Primary Server panel.

3. If the Preferred DB value does not match the IP Address value, perform a database switchover. See the database management chapter of the NSP System Administrator Guide for information about performing a database switchover.

Back up database

CAUTION Data Loss

The path of the main database backup directory must not include the main database installation directory, or data loss may occur.

Ensure that the backup directory path that you specify does not include /opt/nsp/nfmp/db.

Note: Before the NFM-P performs a database backup, it deletes the contents of the specified backup directory. Ensure that the backup directory that you specify does not contain files that you want to retain.

You must perform a database backup before you convert an NFM-P system to IPv6.

Back up the main database from the client GUI or a CLI; see the NSP System Administrator Guide for information.

Update hostname mappings

Update the /etc/hosts file on each main server, main database, and auxiliary server station, as required, to associate each component hostname with an IPv6 address instead of an IPv4 address.

End of steps