Stop and undeploy NSP cluster

In a standalone NSP deployment, perform Step 3 to Step 8.

In a DR NSP deployment, perform Step 3 to Step 8 on the standby NSP cluster.

Then repeat Step 3 to Step 8 on the primary NSP cluster.

Log in to deployer host of the NSP cluster as a root user.

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

Edit the following line in the platform section, kubernetes subsection to read:

  deleteOnUndeploy:false

Save and close the file.

Stop and undeploy the NSP cluster.

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 uninstall --undeploy --clean

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

Check pods status in the NSP cluster host.

Log in to the standby cluster host as a root user.

# kubectl get pods -A ↵

The status of each NSP cluster pod is displayed; only kube-system and nsp-backup-storag-0 pods is Running.

Redeploy NSP cluster

In a standalone NSP deployment, perform Step 11 to Step 17.

In a DR NSP deployment, perform Step 11 to Step 17 on the primary NSP cluster.

Then repeat Step 11 to Step 17 on the standby NSP cluster.

Log in to deployer host of the appropriate NSP cluster as a root user.

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

For a standalone NFM-P system, remove the IP address configured as the primaryIp value in the nfmp section.

For a redundant NFM-P system, remove the IP address configured as the standyIp value in the nfmp section.

Save and close the file.

Enter the following to redeploy 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 install --config --deploy

# /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl install --config --deploy ↵

Do not proceed to the next step until NSP redeploys successfully and all nodes are managed through MDM.

Enter the following periodically to display the status of the Kubernetes system pods:

Note: You must not proceed to the next step until each pod STATUS reads Running or Completed.

# kubectl get pods -A ↵

The pods are listed.

In the NSP UI, check the NFM-P configuration status.

Open Settings, User Preferences.

When NFM-P is removed from the NSP configuration, the NFM-P Client option is removed from the User Preferences page.

Check NFM-P connection status.

Open Data Collection and Analysis Management, Analytics Server Management, Server Status.

When NFM-P is removed from NSP configuration, in the NFM-P section, the Enabled is set to No, Ready is set to No, and Active database host field is empty.

The Auxiliary Database section displays the auxiliary database server details.

Check the auxiliary database clusters status in the Auxiliary Database Clusters section on System Health dashboard.

In the NSP UI, check analytics report generation.

Open Data Collection and Analysis Management, Analytics Reports, Reports and Dashboards, NSP, utilization, and then Temperature, CPU, Memory Utilization Details (NSP).

Back up the auxiliary database as described in the NSP System Administrator Guide as a scheduled or manual backup.

Transfer the backup files to a separate facility for safekeeping.

If auxiliary databases are geo-redundant, issue the cluster status API call:

Note: In order to issue a RESTCONF API call, you require a token; see the My First NSP API Client tutorial on the Network Developer Portal for information.

https://server/restconf/data/auxdb:auxdb-agent

where

server is the NSP advertised address

In the output, the copy-cluster status should be “SUCCESS”. 

Remove NFM-P

Uninstall and remove all NFM-P auxiliary server software.

On each auxiliary server station, perform the following.

1. As the root user, enter the following:

   # dnf remove nsp-nfmp-aux-server nsp-nfmp-config nsp-nfmp-jre nsp-nfmp-nodeexporter ↵

   # systemctl reboot ↵

2. As the root user, enter the following to remove the contents of the /opt/nsp/ directory:

   # rm -rf /opt/nsp/* ↵

3. Remove the following installation files:

   • nsp-nfmp-jre-R.r.p-rel.version.rpm

   • nsp-nfmp-config-R.r.p-rel.version.rpm

   • nsp-nfmp-aux-server-R.r.p-rel.version.rpm

   • nsp-nfmp-nodeexporter-R.r.p-rel.version.rpm

Uninstall and remove all NFM-P main server software.

On each main server station, perform the following.

1. As the root user, enter the following:

   # /opt/nsp/Uninstaller/uninstall.sh ↵

   # systemctl reboot ↵

2. As the root user, remove the contents of the /opt/nsp/ directory.

   # rm -rf /opt/nsp/* ↵

3. Remove the following installation files:

   • nsp-nfmp-jre-R.r.p-rel.version.rpm

   • nsp-nfmp-config-R.r.p-rel.version.rpm

   • nsp-nfmp-nspos-R.r.p-rel.version.rpm

   • nsp-nfmp-main-server-R.r.p-rel.version.rpm

   • nsp-nfmp-nodeexporter-R.r.p-rel.version.rpm

Uninstall and remove all NFM-P database software.

On each database station, perform the following.

1. As the root user, enter the following:

   # dnf remove nsp-nfmp-main-db nsp-nfmp-oracle nsp-nfmp-config nsp-nfmp-jre nsp-nfmp-nodeexporter ↵

   # systemctl reboot ↵

2. As the root user, remove the contents of the /opt/nsp/ directory.

   # rm -rf /opt/nsp/* ↵

3. Remove the following installation files:

   • OracleSw_PreInstall.sh

   • nsp-nfmp-jre-R.r.p-rel.version.rpm

   • nsp-nfmp-config-R.r.p-rel.version.rpm

   • nsp-nfmp-main-db-R.r.p-rel.version.rpm

   • nsp-nfmp-oracle-R.r.p-rel.version.rpm

   • nsp-nfmp-nodeexporter-R.r.p-rel.version.rpm

Uninstall all NFM-P GUI clients in the network.

Decommission the NFM-P main, database, and auxiliary server stations.

End of steps