Installing the NFM-P

Description
CAUTION 

CAUTION

Service Disruption

An NFM-P system installation 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 

CAUTION

Support Liability

Failure to comply with the requirements and restrictions that apply to NFM-P system deployment may violate a support agreement.

NFM-P software installation is supported only under the conditions described in this guide.

Note: NFM-P installation is supported only for shared-mode NSP deployments. You cannot install an independent Release 22 NFM-P system. See Greenfield installations of independent NFM-P deployments for more information.

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.

Component configuration

Most NFM-P component configuration is performed using the samconfig utility. See NFM-P samconfig utility for information.

Note: The Bash shell is the supported command shell for RHEL CLI operations.

Greenfield installations of independent NFM-P deployments

Greenfield installations of independent Release 22 NFM-P systems are not supported under normal circumstances; only installations in shared mode with an NSP cluster are supported. However, such a system installation may be required, for example, to rebuild a Release 22 system after a catastrophic failure.

In such a scenario, contact technical support to obtain the required installation procedure.