How do I perform an NSP DR switchover?
Purpose
|
CAUTION Service disruption |
Performing this procedure causes a temporary loss of network visibility, which may be service-affecting.
You must perform the procedure only with the assistance of technical support during a scheduled maintenance period.
Perform this procedure to manually switch the primary and standby NSP cluster roles.
Note: You require root user privileges on the NSP cluster host in each data center.
Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command.
Steps
1 |
Perform How do I identify the NSP cluster DR roles? to identify each NSP cluster role. |
2 |
Log in as the root or NSP admin user on a VM in the standby NSP cluster. |
3 |
Open a console window. |
4 |
Enter the following: # kubectl exec -n $(kubectl get pods -A | awk '/nsp-role-manager/ {print $1;exit}') -it $(kubectl get pods -A | awk '/nsp-role-manager/ {print $2;exit}') -c role-manager -- /opt/nsp/os/rolemgr/bin/rmgrctl toActive ↵ The standby cluster assumes the primary role. |
5 |
Enter the following periodically to display the status of the clusters as the roles change: # kubectl exec -n $(kubectl get pods -A | awk '/nsp-role-manager/ {print $1;exit}') -it $(kubectl get pods -A | awk '/nsp-role-manager/ {print $2;exit}') -c role-manager -- /opt/nsp/os/rolemgr/bin/rmgrctl statusAll ↵ Output like the following is displayed when the role changes are complete: Site: primary_cluster_name Status: active Since: timestamp
Site: standby_cluster_name Status: standby Since: timestamp |
6 |
When the role changes are complete, close the open console windows. End of steps |