NFM-P deployment requirements

Platform requirements

Note: For optimal storage performance on a supported Nokia AirFrame server, set the default write cache policy for each created storage volume to Write Through. See the NokiaAirFrame server documentation for information about verifying, configuring, and setting the write cache policy for a volume.

The following are the NFM-P platform requirements.

Security requirements

Note: The use of sudo to gain root user privileges is supported for NFM-P installation, and for any other NFM-P operation that requires root user privileges.

The following are the NFM-P security requirements.

Network requirements
CAUTION 

CAUTION

Service Disruption

The use of hostname resolution for GUI and XML API client communication with an NFM-P main server in a NAT environment is strongly recommended.

When IP addresses are used in a NAT environment, the following conditions apply:

CAUTION 

CAUTION

Service Disruption

In a redundant system, a GUI client that opens a browser connection to the primary NFM-P main server may need to use the address of the peer main server after a main server communication failure.

To resolve the two addresses, a GUI client can use a common DNS name which maps each main server IP address provided by the DNS server to the primary main server.

Regardless of the network addressing scheme and configuration, for example, whether NAT, hostnames, or multiple interfaces are used, the /etc/hosts file of a component must contain valid address entries for reaching other components at the following times:

Using NAT

Network Address Translation adds an extra level of complexity to an NFM-P network. If NAT is to be used in the NFM-P management network, hostname resolution for GUI and XML API client communication is strongly recommended.

The following are the basic network configuration requirements; see Using hostnames in the management network for more information, including an example network configuration that uses hostnames.

Note: Hostnames are case-sensitive.

Firewalls

The following firewall types are supported in an NFM-P system:

Before you attempt to deploy an NFM-P system, or add a component to a system, you must ensure that any firewalls between the components allow the required traffic to pass between the components, or are disabled. The NSP Planning Guide lists the open ports required by each component.

Note: If you intend to use firewalld, you must configure firewalld according to the rules in the NSP Planning Guide, which describes using NFM-P templates to create firewalld rules.

Management network

The following requirements apply to the NFM-P management network.

Hostname usage in an NFM-P system has special configuration requirements. See Using hostnames in the management network for an example management network configuration, and Network requirements for specific configuration information.

Managed network and external systems
CAUTION 

CAUTION

Management Disruption

If an NFM-P system that is to be upgraded manages a device as a GNE, and the new NFM-P release supports native management of the device, you must unmanage the device and delete it from the main database before the upgrade.

After the upgrade, you can use the NFM-P to discover and manage the device natively, rather than as a GNE.

Note: Before you upgrade an NFM-P system that manages 7705 SAR, 7705 SAR-Hm, or VSR NEs using NGE, you must observe the following:

If you want to manage such devices after the NFM-P upgrade using NGE version 2, you must do the following:

  1. Upgrade each device to a release that supports NGE version 2.

  2. Use the NFM-P to specify NGE version 2 for each device.

The following requirements apply to the network of NFM-P-managed devices, and to the external systems with which the NFM-P is integrated.

Software deployment requirements

The following are the NFM-P software requirements.