To perform the pre-conversion tasks
Description
The following steps describe the actions that you must perform in advance of a standalone or redundant NFM-P system conversion to IPv6.
Note: You require the following user privileges:
Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands:
Steps
Perform security preconfiguration | |||
1 |
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 procedures. | ||
Clear failed deployments | |||
2 |
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 | |||
3 |
Make a backup copy of the /opt/nsp/nfmp/server/nms/config/nms-server.xml file on each main server station. | ||
4 |
Copy the file to a secure location that is unaffected by the conversion. | ||
Gather required information | |||
5 |
Obtain and record the following information for each main database: | ||
6 |
Obtain and record the following information for each main and auxiliary server: | ||
Close unrequired clients | |||
7 |
Close the open NFM-P GUI and XML API client sessions.
| ||
Close LogViewer | |||
8 |
Close the LogViewer utility, if it is open. | ||
Verify database archive log synchronization | |||
9 |
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.
| ||
Verify database alignment | |||
10 |
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.
| ||
Back up database | |||
11 |
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 | |||
12 |
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 |