Prepare required resources

Submit an NSP Platform Sizing Request for the new deployment type.

Back up NSP databases, configuration

If you are expanding a standalone NSP cluster, or the primary cluster in a DR deployment, you must back up the following NSP databases; perform “How do I back up the NSP cluster databases?” in the NSP System Administrator Guide.

Note: Ensure that you copy each backup file to a secure location on a station outside the NSP deployment that is reachable from the NSP cluster.

• file-server-app

• nspos-postgresql

• nspos-neo4j

• nspos-solr

• nsp-tomcat

• nrcx-tomcat

• opensearch

Enlarge cluster, standalone deployment

If the NSP is a standalone deployment, go to Step 7.

Enlarge clusters, DR deployment

Perform Step 7 to Step 29 on the standby NSP cluster.

Perform Step 7 to Step 41 on the primary NSP cluster.

Perform Step 36 to Step 41 on the standby NSP cluster.

Uninstall NSP

Log in as the root or NSP admin user on the NSP deployer host.

Open a console window.

Transfer the following file to a secure location on a station outside the NSP cluster that is unaffected by the conversion activity.

/opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/appliedConfigs/nspConfiguratorConfigs.zip

Configure the NSP to completely remove the existing deployment.

1. Open the following file using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the following line in the platform section, kubernetes subsection to read as shown below:

     deleteOnUndeploy:true

3. Save and close the nsp-config.yml file.

Enter the following to stop the NSP cluster:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass uninstall --undeploy --clean

# /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl uninstall --undeploy --clean ↵

Create new NSP cluster

Using the resource specifications in the response to your Platform Sizing Request, create the required new NSP cluster VMs and resize the existing VMs, as required.

Resize cluster as required

Log in as the root or NSP admin user on the NSP deployer host.

Open a console window.

Open the following file using a plain-text editor such as vi:

/opt/nsp/nsp-k8s-deployer-release-ID/config/k8s-deployer.yml

You must add each new node to the hosts section, as shown below.

Configure the following parameters for each new node; see the descriptive text at the head of the file for parameter information, and Hostname configuration requirements for general configuration information.

- nodeName: node_name

  nodeIp: private_IP_address

  nodeIpv6: private_IPv6_address

  accessIp: public_IP_address

  isIngress: value

where

node_name is the VM name

private_IP_address is the VM IP address on the internal network

private_IPv6_address is the optional VM IPv6 address on the internal network; in a NAT environment, this is the private IPv6 address.

public_IP_address is the public VM address; required only in a NAT environment

value is true or false, and indicates whether the node acts as a load-balancer endpoint

Note: The nodeName value:

• can include only ASCII alphanumeric and hyphen characters

• cannot include an upper-case character

• cannot begin or end with a hyphen

• cannot begin with a number

• cannot include an underscore

• must end with a number

Save and close the k8s-deployer.yml file.

Create a backup copy of the updated k8s-deployer.yml file, and transfer the backup copy to a station that is separate from the NSP system and preferably in a remote facility.

Note: The backup file is crucial in the event of an NSP deployer host failure, so must be available from a separate station.

Enter the following:

# cd /opt/nsp/nsp-k8s-deployer-release-ID/bin ↵

Enter the following to create the cluster configuration:

# ./nspk8sctl config -c ↵

The following is displayed when the creation is complete:

✔ Cluster hosts configuration is created at: /opt/nsp/nsp-k8s-deployer-release-ID/config/hosts.yml

For each NSP cluster VM that you are adding, enter the following to distribute the local SSH key to the VM:

# ssh-copy-id -i ~/.ssh/id_rsa.pub user@address ↵

where

address is the NSP cluster VM IP address

user is the designated NSP ansible user, if root-user access is restricted; otherwise, user@ is not required

Enter the following:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspk8sctl --ask-pass install

# ./nspk8sctl install ↵

The NSP Kubernetes environment is deployed.

On the NSP cluster host, enter the following to verify that the new node is added to the cluster:

# kubectl get nodes ↵

On the NSP deployer host, enter the following:

# cd /opt/nsp/NSP-CN-DEP-release-ID/bin ↵

Open the following file using a plain-text editor such as vi:

/opt/nsp/NSP-CN-DEP-release-ID/config/nsp-deployer.yml

Configure the following parameters:

hosts: "hosts_file"

where hosts_file is the absolute path of the hosts.yml file; the default is /opt/nsp/nsp-k8s-deployer-new-release-ID/config/hosts.yml

Save and close the nsp-deployer.yml file.

Configure deployment

Perform the following steps on the NSP deployer host to update the NSP configuration.

1. Open the nsp-config.yml file backed up in Step 9 using a plain-text editor such as vi:

2. In the deployment subsection of the nsp section, configure the type parameter to the new deployment type configured in Step 25.

3. Verify the file content to ensure that the configuration is correct.

4. Save and close the file.

Configure the NSP to preserve the deployment.

1. Open the following file on the NSP deployer host using a plain-text editor such as vi:

   /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

2. Edit the following line in the platform section, kubernetes subsection to read as shown below:

     deleteOnUndeploy:false

3. Save and close the nsp-config.yml file.

Deploy NSP in restore mode

On the NSP deployer host, enter the following:

# cd /opt/nsp/NSP-CN-DEP-release-ID/bin ↵

Enter the following:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config --restore

# ./nspdeployerctl install --config --restore ↵

The NSP cluster is deployed in restore mode.

Restore databases

On the NSP cluster host, enter the following:

# kubectl get pods -A ↵

The database pods are listed.

Verify that the database pods are running; the number of replica pods running depends on the deployment type:

• standard, medium, or basic—one replica each of nspos-neo4j-core, nsp-tomcat, and one of nrcx-tomcat, if included in the deployment

• enhanced—three replicas each of nspos-neo4j-core and nsp-tomcat

Perform “How do I restore the NSP cluster databases?” in the NSP System Administrator Guide.

Start NSP

On the NSP deployer host, enter the following:

# cd /opt/nsp/NSP-CN-DEP-release-ID/bin ↵

Enter the following:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config --deploy

# ./nspdeployerctl install --config --deploy ↵

The NSP cluster is deployed, and the NSP starts.

On the NSP cluster host, enter the following every few minutes to display the cluster status:

Note: You must not proceed to the next step until the cluster is fully operational.

# kubectl get pods -A ↵

The status of each NSP cluster pod is displayed; the NSP cluster is operational when the status of each pod is Running or Completed, with the following exception.

• If you are including any MDM VMs in addition to a standard or enhanced NSP cluster deployment, the status of each mdm-server pod is shown as Pending, rather than Running or Completed.

Use a browser to open the NSP cluster URL.

Verify the following.

• The NSP sign-in page opens.

• The NSP UI opens after you sign in.

• In a DR deployment, if the standby cluster is operational and you specify the standby cluster address, the browser is redirected to the primary cluster address.

Note: If the UI fails to open, perform “How do I remove the stale NSP allowlist entries?” in the NSP System Administrator Guide to ensure that unresolvable host entries from the previous deployment do not prevent NSP access.

Use the NSP to monitor device discovery and to check network management functions.

Close the open console windows.

End of steps