Cisco Cisco TelePresence Video Communication Server Expressway
Create a new cluster of VCS X7.0.n peers
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.0.n)
Page 18 of 63
Create a new cluster of VCS X7.0.n peers
Note: This procedure will require a period of downtime for the VCS service. Ensure that these
instructions are followed in a scheduled maintenance window.
instructions are followed in a scheduled maintenance window.
This section documents enabling clustering on a single Cisco VCS. This will be the Master peer of the
cluster.
cluster.
To complete the cluster by adding multiple Cisco VCSs, once this section is complete, follow the
instructions in “Add an X7.0.n VCS to a VCS X7.0.n cluster (n is the same value on all peers)” to add
the non-master peers to the cluster.
instructions in “Add an X7.0.n VCS to a VCS X7.0.n cluster (n is the same value on all peers)” to add
the non-master peers to the cluster.
Do not use this section if the cluster already exists; instead, follow the instructions in “Add an X7.0.n
VCS to a VCS X7.0.n cluster (n is the same value on all peers)”.
VCS to a VCS X7.0.n cluster (n is the same value on all peers)”.
Note: If Device Provisioning or FindMe is to be used with an X7.0.n VCS cluster, then use of Cisco
TMS is essential. If neither Device Provisioning nor FindMe is to be used, then use of Cisco TMS is
optional but recommended.
TMS is essential. If neither Device Provisioning nor FindMe is to be used, then use of Cisco TMS is
optional but recommended.
If Cisco TMS is to be used with this Cisco VCS cluster, ensure that it is running version 12.6 or later.
Prerequisites
All Cisco VCSs to be included in the cluster must be running the same version of Cisco VCS
software, and that version of software must be X7.0.n (n is the same value on all peers).
software, and that version of software must be X7.0.n (n is the same value on all peers).
If Device Provisioning and FindMe are configured, they must have already been proven to be
operational on the master Cisco VCS after its upgrade to X7.0.n.
operational on the master Cisco VCS after its upgrade to X7.0.n.
If a firewall exists between cluster peers, it must be configured to permit the traffic documented in
Appendix 3.
Appendix 3.
Set up the master peer of the cluster
This process sets up the first (Master) peer of this new cluster – additional peers are added afterwards
using the “Add an X7.0.n VCS to a VCS X7.0.n cluster (n is the same value on all peers)” process.
using the “Add an X7.0.n VCS to a VCS X7.0.n cluster (n is the same value on all peers)” process.
Before proceeding, the Cisco VCS that will be the Master must be chosen.
Note:
The Master Cisco VCS will be the source of the configuration information for all Cisco VCS peers
in the cluster. Non-master Cisco VCS peers will have their configuration deleted and replaced by
that from the Master.
in the cluster. Non-master Cisco VCS peers will have their configuration deleted and replaced by
that from the Master.
FindMe information can only be kept if the relevant Cisco VCS is already configured to operate
with Cisco TMS and is configured with Enable TMS Agent Data Replication. (FindMe information
for clusters is stored on Cisco TMS; it is deleted on VCS and overwritten by the information from
Cisco TMS when Enable TMS Agent Data Replication is enabled.)
with Cisco TMS and is configured with Enable TMS Agent Data Replication. (FindMe information
for clusters is stored on Cisco TMS; it is deleted on VCS and overwritten by the information from
Cisco TMS when Enable TMS Agent Data Replication is enabled.)
On neighbor Gatekeepers (GKs) and Border Controllers (BCs):
1. If the Master Cisco VCS has a traversal zone configured to connect with any GK or BC, upgrade
these systems to N6.1 or Q6.1 or later code.
On other Cisco VCSs:
1. Check that no other Cisco VCS (anywhere) has this Cisco VCS’s IP address in their Alternates or
Clustering Peers list.