Configuring an NFM-P system deployment

Deployment conditions

Before you attempt to install the NFM-P, you must comply with the conditions in this section and ensure that the NFM-P platform is correctly configured, as described in Part I: Getting started.

Chapter 3, RHEL OS deployment for the NSP contains OS-specific information about single-user GUI client and client delegate server deployment.

Platform support

You can deploy NFM-P components in virtual machines, or VMs. See the NSP Planning Guide for VM host requirements, and Deployment in a VM for VM deployment requirements and restrictions.

An NFM-P system consists of the following:

• one standalone main server, or two in a redundant deployment

• one standalone main database, or two in a redundant deployment

• one or more single-user GUI clients or client delegate servers

• optionally, one or more auxiliary servers

Note: CPAM functions in an NFM-P system are enabled only when the system includes one or more operational 7701 CPAA devices. See the 7701 CPAA and vCPAA Setup and Installation Guide for 7701 CPAA deployment information.

The following table lists the supported platforms for each NFM-P component type.

Table 13-2: NFM-P platform support by component

NFM-P component	Mac OS X	Microsoft Windows	RHEL
Main server			✓
Main database			✓
Auxiliary server			✓
Client delegate server		✓	✓
Single-user client	✓	✓	✓

nsp user account

NFM-P system operation and management require a RHEL user account called nsp in the nsp user group.

• The initial installation of any of the following components on a station creates the group and account:

  • main server

  • auxiliary server

• The nsp user owns all NFM-P server processes; only the nsp user can start or stop a server, or run a server script.

• The nsp home directory is /opt/nsp.

• The initial nsp password is randomly generated, and must be changed during the initial login attempt.

• The root user owns some files in the /opt/nsp/nfmp/server directory for low-level installation and support functions.

• Server uninstallation does not remove the nsp user account, user group, or home directory.

• Root user privileges are required only for component installation or upgrade, and for low-level support functions.