The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco DNA Center's implementation of high availability (HA) is described in the Cisco DNA Center High Availability Guide. We recommend that you first review this information and then determine whether you want to deploy HA in your production environment. If you choose to do so, complete the following tasks:
Complete the deployment procedure that is appropriate for your network:
Activate high availability (HA) on your Cisco DNA Center cluster.
See Additional HA Deployment Considerations and make any additional configurations that are necessary.
To install a brand new HA cluster, complete the following steps:
|
Step 1 |
Configure the first installed appliance as the primary node. |
|
Step 2 |
Configure the second and third appliances in the cluster. |
To deploy an existing HA cluster, where the primary node uses the required interface cable configurations, complete the following steps.
|
Step 1 |
Upgrade the primary node to the latest Cisco DNA Center version. For information about upgrading your current release of Cisco DNA Center, see the Cisco DNA Center Upgrade Guide. |
|
Step 2 |
Confirm that you are using the required interface cable configurations on the primary node. |
|
Step 3 |
Update the virtual IP address (if the virtual IP address is not yet added). See Reconfigure the Appliance Using the Configuration Wizard. |
|
Step 4 |
Configure the second and third appliances in the cluster. |
|
Step 5 |
Enter the following command to check the GlusterFS size: sudo du -h /data/maglev/srv/maglev-system/glusterfs/mnt/bricks/default_brick/ | tail -1 | awk '{print $1}' If the GlusterFS file system size is larger than 150 GB, complete the steps described in Existing HA Deployment of the Primary Node with Nonstandard Interface Configurations. |
To deploy an existing HA cluster where the primary node uses nonstandard interface configurations, complete the following steps.
|
Step 1 |
Upgrade the primary node to the latest Cisco DNA Center version. For information about upgrading your current release of Cisco DNA Center, see the Cisco DNA Center Upgrade Guide. |
|
Step 2 |
Create a backup of the remote repository. See the "Backup and Restore" chapter in the Cisco DNA Center Administrator Guide. |
|
Step 3 |
Reimage the primary node with the required interface cable configuration. See Interface Cable Connections and Install the Cisco DNA Center ISO Image. Make sure that the VIP has been configured correctly on the primary node. |
|
Step 4 |
On the primary node, install the same set of packages that you selected during the backup. |
|
Step 5 |
Using the backup file that you created in Step 2, restore the remote repository's data. |
|
Step 6 |
Configure the second and third appliances in the cluster. |
Cisco DNA Center's implementation of HA is described in the Cisco DNA Center High Availability Guide. We recommend that you first review this information and then determine whether you want to deploy HA in your production environment. If you choose to do so, complete the following steps:
Click the menu icon (
) and choose .
Click Activate High Availability.
After you click Activate High Availability, Cisco DNA Center enters into maintenance mode. In this mode, Cisco DNA Center is unavailable until the redistribution of services is completed. You should take this into account when scheduling an HA deployment.
 Note |
Cisco DNA Center goes into maintenance mode every time you restore the database, perform a system upgrade (not a package upgrade), and activate HA (as described above). |
For an existing HA deployment, the following additional configurations must be made.
Note |
For information about known HA bugs and workarounds, see “Open Bugs—HA" in the Release Notes for Cisco Digital Network Architecture Center. |
If you enabled telemetry for a device (without enabling the VIP), complete the following steps:
|
Step 1 |
Use the sudo maglev-config update command to update the cluster VIP. |
|
Step 2 |
Disable telemetry on the device:
|
|
Step 3 |
Reenable telemetry using the profile associated with the device previously. |
You must update the wireless controllers in your network with the new VIP of Cisco DNA Center.
Feedback