300-415 · Question #215
An engineer builds a three-node vManage cluster and then realizes that multiple nodes are unnecessary for the size of the company. How should the engineer revert the setup to a single vManage?
The correct answer is C. Leave the cluster as is and point to one vManage. If a vManage cluster is built but redundancy is no longer desired, the most practical approach is to leave the cluster running and simply configure WAN Edge devices and other controllers to connect to only one of the vManage nodes.
Question
Options
- AUse the cluster conversion utility to convert to standalone vManage.
- BRestore vManage from the backup VM snapshot.
- CLeave the cluster as is and point to one vManage.
- DRemove two nodes from the three-node vManage cluster.
How the community answered
(22 responses)- A5% (1)
- C86% (19)
- D9% (2)
Why each option
If a vManage cluster is built but redundancy is no longer desired, the most practical approach is to leave the cluster running and simply configure WAN Edge devices and other controllers to connect to only one of the vManage nodes.
There is no supported 'cluster conversion utility' in Cisco SD-WAN to revert a vManage cluster to a standalone instance.
Restoring from a VM snapshot would only be viable if a snapshot of a standalone vManage existed before clustering, which is not implied by the question.
Cisco SD-WAN does not provide a direct or supported utility to 'downgrade' a multi-node vManage cluster to a standalone instance. The recommended approach is to continue operating the cluster with all nodes, even if two are considered unnecessary, and ensure that all devices are pointed to a single active vManage node for management.
Simply removing nodes from a vManage cluster without proper uninstallation and re-configuration can lead to an unstable or corrupted cluster state, as the cluster state requires all members to be properly managed.
Concept tested: vManage cluster management limitations
Topics
Community Discussion
No community discussion yet for this question.