Converting an NFM-P system to redundancy
Introduction
|
CAUTION Service Disruption |
An NFM-P system conversion to redundancy requires a thorough understanding of NFM-P system administration and platform requirements, and is supported only under the conditions described in this guide, the NSP Planning Guide, and the NSP Release Notice.
Such an operation must be planned, documented, and tested in advance on a trial system that is representative of the target live network. Contact NSP professional services to assess the requirements of your NFM-P deployment, and for information about the upgrade service, which you are strongly recommended to engage for any type of deployment.
|
|
CAUTION Service Disruption |
An NFM-P system conversion to IPv6 involves a network management outage.
You must perform a conversion only during a maintenance period of sufficient duration.
This section describes the conversion of a standalone NFM-P system to a redundant NFM-P system.
You require an NFM-P license file for the new standby main server, or an updated license file that includes the standby main server information. Contact technical support for information about obtaining or updating an NFM-P license.
The NFM-P samconfig utility is used for component configuration and deployment. See NFM-P samconfig utility for information about the samconfig utility.
Note: It is strongly recommended that you verify the GPG signature of each RPM file that you download from Nokia to ensure that each file has a valid Nokia signature.
Note: It is strongly recommended that you verify the message digest of each NSP image file or software bundle that you download from the Nokia Support portal. The download page includes the MD5, SHA256, and SHA512 checksums for comparison with the output of the RHEL md5sum, sha256sum, or sha512sum command. See the associated RHEL man page for command usage information.
Note: The Bash shell is the supported command shell for RHEL CLI operations.
Redundancy conversion requirements
The following must be true before you attempt a system conversion to redundancy.
-
The NFM-P system is at the release described in this guide; you cannot combine an upgrade and a conversion to redundancy in one operation.
-
If the system to be converted is a newly upgraded system, the system is fully initialized and functional; an upgraded main server performs crucial upgrade-specific tasks during startup.
-
Each component in the standalone NFM-P system is operational.
Redundancy conversion restrictions
An NFM-P system conversion to redundancy is not supported during a system upgrade.
TLS considerations
The following options are available for implementing TLS on the new redundant system components:
-
Recommended—If you are using a TLS certificate generated by the PKI server, no action is required other than specifying the PKI server in the configuration of each new system element. Alternatively, if you provide a certificate, you must also import the certificate to the PKI server for distribution to each requestor.
System operation is unaffected in either case.
-
You can use a PKI server to implement a new TLS certificate throughout the system; however, each requestor requires configuration and a restart, which can affect system operation.
The Subject Alternative Name, or SAN, field of the certificate for the NFM-P main servers must include the following: