Check the Host Environment Compatibility Reference for NSP and CLM to ensure that the OS version of the host station supports the creation of VMs at the RHEL version that the NSP requires.

Log in to the VM host station as the root user.

If the host station OS version supports NSP VM creation, enter the following; otherwise, update the host OS version as required:

# osinfo-query os | grep rhel | grep -v - ↵

A list of supported RHEL variants is listed, for example:

rhel7.8 | Red Hat Enterprise Linux 7.8 | 7.8 | http://redhat.com/rhel/7.8

rhel7.9 | Red Hat Enterprise Linux 7.9 | 7.9 | http://redhat.com/rhel/7.9

rhel8.0 | Red Hat Enterprise Linux 8.0 | 8.0 | http://redhat.com/rhel/8.0

rhel8.1 | Red Hat Enterprise Linux 8.1 | 8.1 | http://redhat.com/rhel/8.1

rhel8.2 | Red Hat Enterprise Linux 8.2 | 8.2 | http://redhat.com/rhel/8.2

Record the appropriate RHEL version number in the left column, which is one of the following:

• the version that matches the NSP RHEL version, if supported

• the version that is less than but closest to the supported NSP RHEL version; in the output example, the version to record is 8.2, as the NSP supports a higher RHEL version that is not listed

Download the following files from the NSP downloads page on the Nokia Support portal to an empty local directory on the station:

• NSP_NFM-P_R_r_COLLOCATED_OS.qcow2

• each file named NSP_NFM-P_R_r_COLLOCATED_STANDALONE.qcow2.partn

• QCOW2_Images.cksum

where

n is the partial file ID

R_r is the NFM-P release identifier

Open a console window.

Navigate to the directory that contains the downloaded files.

An NFM-P product image is divided among a set of partial image files that you must concatenate to create one complete image file.

Enter the following to create the complete image file:

# cat NSP_NFM-P_R_r_COLLOCATED_STANDALONE.qcow2.part* >NSP_NFM-P_R_r_COLLOCATED_STANDALONE.qcow2 ↵

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 checksums for comparison with the output of the RHEL md5sum, sha256sum, or sha512sum command.

To verify a file checksum, perform the following steps.

1. Enter the following:

   # command file ↵

   where

   command is md5sum, sha256sum, or sha512sum

   file is the name of the file to check

   A file checksum is displayed.

2. Compare the checksum value and the value in the .cksum file.

3. If the values do not match, the file download has failed. Download a new copy of the file, and then repeat this step.

Convert the image files to raw format.

1. Enter the following:

   # qemu-img convert -f qcow2 NSP_NFM-P_R_r_COLLOCATED_OS.qcow2 -O raw -S 0 raw_OS.img ↵

2. Enter the following:

   # qemu-img convert -f qcow2 NSP_NFM-P_R_r_COLLOCATED_STANDALONE.qcow2 -O raw -S 0 raw_software.img ↵

where

R_r is the NFM-P release identifier

raw_OS is the name to assign to the raw OS image file

raw_software is the name to assign to the raw software image file

Resize the raw software image.

1. Navigate to the directory that contains the raw software image file created in Step 10.

2. Enter the following:

   # qemu-img resize raw_software.img sizeG ↵

   where

   raw_software.img is the file to resize

   size is the required size value in the response to your Platform Sizing Request

Convert the raw image from sparse format to non-sparse format; enter the following:

Note: The operation may take many minutes, depending on the file size.

# cp --sparse=never raw_software.img non-sparse_software.img ↵

where

raw_software.img is the raw software image file resized in Step 11

non-sparse_software.img is the name to assign to the non-sparse software image file

Enter the following to deploy the VM:

# virt-install --connect qemu:///system --ram RAM --vcpus=vCPUs -n instance --os-type=linux --os-variant=variant --disk path=raw_OS.img,device=disk,bus=virtio,format=raw,io=native,cache=directsync --disk path=non-sparse_software.img,device=disk,bus=virtio,format=raw,io=native,cache=directsync --network bridge=bridge_name --import ↵

where

bridge_name is the name assigned to the VM network bridge

vCPUs is the required number of vCPU threads in the response to your Platform Sizing Request

instance is the name to assign to the VM

non-sparse_software.img is the name of the non-sparse software image file created in Step 12

RAM is the required amount of VM RAM in the response to your Platform Sizing Request, in Mbytes; for example, 64 Gbytes is expressed as 65536, which is 64 x 1024 Mbytes

raw_OS.img is the name of the OS image file created in Step 10

variant is the OS version recorded in Step 4; for example, 8.2

When the NFM-P VM is instantiated, log in as the root user on the VM; the default password is available from technical support.

Set a secure password for the root user.

1. Enter the following:

   # passwd ↵

   The following prompt is displayed:

   New Password:

2. Enter a secure password.

   The following prompt is displayed:

   Confirm Password:

3. Re-enter the password.

4. Record the password and store it in a secure location.

Enter the following:

# pvresize /dev/vdb ↵

Enter the following:

# lsblk ↵

Basic disk partition information is displayed; the value in the SIZE column is the partition size in Gbytes.

As required, enter one or more of the following commands to extend the logical volumes for the partitions.

Note: You need to enter a command only if the SIZE value is lower than the required partition size in the response to your Platform Sizing Request.

Note: The lvextend command does nothing if a partition size is equal to or greater than the associated value in the response to your Platform Sizing Request. In such a case, the command returns a failure message that you can ignore.

# lvextend -L sizeG /dev/vg2/lv_nsp ↵

# lvextend -L sizeG /dev/vg2/lv_nspos ↵

# lvextend -L sizeG /dev/vg2/lv_log ↵

# lvextend -L sizeG /dev/vg2/lv_xmloutput ↵

# lvextend -L sizeG /dev/vg2/lv_db ↵

# lvextend -L sizeG /dev/vg2/lv_archivelog ↵

# lvextend -L sizeG /dev/vg2/lv_dbbackup ↵

# lvextend -L sizeG /dev/vg2/lv_nebackup ↵ (required only if size is greater than 1 Gbyte)

# lvextend -L sizeG /dev/vg2/lv_var_log ↵

# lvextend -L sizeG /dev/vg2/lv_var_log_audit ↵

# lvextend -L sizeG /dev/vg2/lv_extra ↵

where size is the required partition size in the response to your Platform Sizing Request, in Gbytes

For each partition modified in Step 18, enter the associated command in the following list:

# resize2fs /dev/mapper/vg2-lv_nsp ↵

# resize2fs /dev/mapper/vg2-lv_nspos ↵

# resize2fs /dev/mapper/vg2-lv_log ↵

# resize2fs /dev/mapper/vg2-lv_xmloutput ↵

# resize2fs /dev/mapper/vg2-lv_db ↵

# resize2fs /dev/mapper/vg2-lv_archivelog ↵

# resize2fs /dev/mapper/vg2-lv_dbbackup ↵

# resize2fs /dev/mapper/vg2-lv_nebackup ↵

# xfs_growfs /dev/mapper/vg2-lv_var_log ↵

# xfs_growfs /dev/mapper/vg2-lv_var_log_audit ↵

# resize2fs /dev/mapper/vg2-lv_extra ↵

Set a secure password for the VM nsp user.

1. Enter the following:

   # passwd nsp ↵

   The following prompt is displayed:

   New Password:

2. Enter a secure password.

   The following prompt is displayed:

   Confirm Password:

3. Re-enter the password.

4. Record the password and store it in a secure location.

Plumb each required network interface with an IPv4 address, network mask, and gateway address. See the OS documentation for configuration information.

Enter the following to set the station hostname:

# hostnamectl set-hostname hostname

where hostname is a short hostname or FQDN, depending on your requirement

Update the /etc/hosts file to map the station hostname to the IP address of an interface, as described in Using hostnames in the management network.

Enter the following to configure and create the main database:

# samconfig -m db ↵

The following is displayed:

Start processing command line inputs...

<db> 

Verify the database configuration.

1. Enter the following:

   <db> show-detail ↵

   The database configuration is displayed.

2. Review each parameter to ensure that the value is correct.

3. Configure one or more parameters, if required; see NFM-P samconfig utility for information about using the samconfig utility.

4. When you are certain that the configuration is correct, enter the following:

   <db configure> back ↵

   The prompt changes to <db>.

Enter the following to begin the database creation:

<db> apply ↵

The database creation begins, and progress messages are displayed.

The following is displayed when the database creation is complete:

DONE

db configurations updated.

When the database creation is complete, enter the following:

<db> exit ↵

The samconfig utility closes.

Enter the following to configure and enable the main server:

# samconfig -m main ↵

The following is displayed:

Start processing command line inputs...

<main> 

Verify the main server configuration.

1. Enter the following:

   <main> show-detail ↵

   The main server configuration is displayed.

2. Review each parameter to ensure that the value is correct.

3. Configure one or more parameters, if required.

   Note: The NFM-P uses the database backup settings to initialize the database during installation only. To change the backup settings after installation, you must use the Database Manager form in the NFM-P client GUI, as described in the NSP System Administrator Guide.

4. When you are certain that the configuration is correct, enter the following:

   <main configure> back ↵

   The prompt changes to <main>.

Enter the following:

<main> apply ↵

The configuration is applied.

Enter the following:

<main> exit ↵

The samconfig utility closes.

Optionally, for greater system security, you can remove the world permissions from RHEL compiler executable files; see Resetting GCC-compiler file permissions for information.

Enter the following to switch to the nsp user:

# su - nsp ↵

Enter the following:

bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

Enter the following to start the main server:

bash$ ./nmsserver.bash start ↵

Enter the following:

bash$ ./nmsserver.bash appserver_status ↵

The server status is displayed; the server is fully initialized if the status is the following:

Application Server process is running.  See nms_status for more detail.

When the server is fully initialized, close the console window.

End of steps