Cisco Cisco TelePresence Video Communication Server Expressway
Disband a VCS X7.1 cluster
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.1)
Page 41 of 69
Disband a VCS X7.1 cluster
This process will remove all VCS peers from an existing cluster. FindMe and configuration replication
will be stopped, as will provisioning, and the cluster will be deleted from TMS.
will be stopped, as will provisioning, and the cluster will be deleted from TMS.
Each VCS will retain its configuration at the time the cluster was disbanded, and will function as a
stand-alone VCS.
stand-alone VCS.
Caution: If any of the VCSs are left in operation after being removed from the cluster, calls between
endpoints registered to different VCSs that were once part of the same cluster will not succeed. This
is because after the cluster has been disbanded, the Cluster Subzone will no longer exist and there
will not be any link between the two VCSs over which calls can be routed. To overcome this, you
must create neighbor relationships between the VCSs so that there are links between them.
endpoints registered to different VCSs that were once part of the same cluster will not succeed. This
is because after the cluster has been disbanded, the Cluster Subzone will no longer exist and there
will not be any link between the two VCSs over which calls can be routed. To overcome this, you
must create neighbor relationships between the VCSs so that there are links between them.
If any VCS is not accessible, firstly remove it using the procedure “Remove an out-of-service VCS
from a VCS X7.1 cluster (permanently)”.
from a VCS X7.1 cluster (permanently)”.
If TMS is used and TMS is in TMS Agent Legacy mode, on TMS:
1. Select Systems > Navigator (and any required sub folders) then select the Master VCS.
2. Select the Clustering tab.
3. Clear the Enable TMS Agent Data Replication on all Cluster Peers.
4. Click Save Cluster Settings.
5. Select the TMS Agent tab.
6. Ensure that Enable TMS Agent Data Replication is not selected; if this needs changing, change
it and click Save Settings.
If TMS is used and TMS is in TMS Agent Legacy mode, on TMS, for every non-master VCS peer:
1. Select Systems > Navigator (and any required sub folders) then click on the non-master VCS.
2. Select the TMS Agent tab.
3. Ensure that Enable TMS Agent Data Replication is not selected; if this needs changing, change
it and click Save Settings.
4. Repeat for all non-master VCS peers –TMS may require you to pause between disabling each
peer.
If TMS is used and TMS is in Provisioning Extension mode:
1. Select Systems > Navigator (and any required sub folders), then click on any VCS in the cluster.
2. Select the Provisioning tab.
3. Disable all 4 services (clear tick boxes).
4. Click Save.
On each non-master VCS peer:
1. Log into the web interface.
2. From the Clustering page ( VCS configuration > Clustering):
a. Change the Cluster name to a unique ID for this VCS (ideally to the routable Fully Qualified
Domain Name used in SRV records that address this individual VCS, for example
"vcs1.example.com", "vcs2.example.com". etc. (See Appendix 9 – Cluster name and DNS
SRV records.))
Note: Do NOT use the process “Appendix 8 – Changing the cluster name (and keeping
FindMe accounts)” because FindMe accounts are to be left with the master peer of the
cluster that this VCS is being removed from.
"vcs1.example.com", "vcs2.example.com". etc. (See Appendix 9 – Cluster name and DNS
SRV records.))
Note: Do NOT use the process “Appendix 8 – Changing the cluster name (and keeping
FindMe accounts)” because FindMe accounts are to be left with the master peer of the
cluster that this VCS is being removed from.
b. Delete the Cluster pre-shared key.