How do I stop an NSP cluster?

Purpose

CAUTION

Network Management Disruption or Outage

Performing the procedure in a standalone deployment completely stops the NSP and creates a network management outage that persists until you start the cluster. In a DR deployment, stopping an NSP cluster may initiate a server activity switch that may temporarily affect network management.

Perform the procedure only during a scheduled maintenance period and under the guidance of technical support.

The following steps describe how to stop the Kubernetes software in an NSP cluster, for example, when the NSP hosts in the cluster require maintenance, or for cluster decommissioning.

Note: If you are stopping the NSP clusters in a DR deployment, ensure that you perform the procedure at the appropriate stage of Workflow: stop and start DR NSP clusters.

Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command.

Note: release-ID in a file path has the following format:

R.r.p-rel.version

where

R.r.p is the NSP release, in the form MAJOR.minor.patch

version is a numeric value

Steps


1	Log in as the root user on the NSP deployer host.
2	Open a console window.
3	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
4	Edit the following line in the platform section, kubernetes subsection to read as shown below: `deleteOnUndeploy:false`
5	Save and close the file.
6	Enter the following: `#` `/opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl uninstall –-undeploy ↵` The NSP cluster stops.
7	Log in as the root user on the NSP cluster host.
8	Open a console window.
9	Enter the following periodically to display the Kubernetes cluster status: `#` `kubectl get pods -A ↵` The NSP cluster is stopped when only the following output is displayed: `NAME READY STATUS RESTARTS AGE` `nsp-backup-storage-0 1/1 Running 0 age`
10	When the NSP cluster is stopped, close the console window. End of steps