Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Introduction
Cisco TelePresence Video Communication Server (Cisco VCS) clusters are designed to extend the
resilience and capacity of a Cisco VCS installation. Cisco VCSs in the cluster share bandwidth usage,
routing, zone, FindMe™ and other configuration among themselves. Endpoints can register to any of
the Cisco VCSs in the cluster; if they lose connection to their initial peer, they can re-register to
another peer in the cluster.
resilience and capacity of a Cisco VCS installation. Cisco VCSs in the cluster share bandwidth usage,
routing, zone, FindMe™ and other configuration among themselves. Endpoints can register to any of
the Cisco VCSs in the cluster; if they lose connection to their initial peer, they can re-register to
another peer in the cluster.
Call licensing is carried out on a per-VCS peer basis, and so enough call licenses must be applied to
each peer to support the number of calls that are needed on that peer, plus any additional calls that
may be required when one or more other peers become inaccessible. The same number of licenses
must be applied to each peer in the cluster.
each peer to support the number of calls that are needed on that peer, plus any additional calls that
may be required when one or more other peers become inaccessible. The same number of licenses
must be applied to each peer in the cluster.
Every Cisco VCS peer in the cluster must have the same routing capabilities — if any Cisco VCS can
route a call to a destination it is assumed that all peers in that cluster can route the call to that
destination. If the routing is different on different Cisco VCSs, then separate Cisco VCSs / Cisco VCS
clusters must be used.
route a call to a destination it is assumed that all peers in that cluster can route the call to that
destination. If the routing is different on different Cisco VCSs, then separate Cisco VCSs / Cisco VCS
clusters must be used.
This deployment guide describes how to create, modify and upgrade to X5 Cisco VCS clusters. It
provides information on how to:
provides information on how to:
upgrade an X1 Cisco VCS or X2 Cisco VCS set of Alternates to a Cisco VCS X5 cluster
upgrade a Cisco VCS X3 / X4 cluster to a Cisco VCS X5 cluster
upgrade a Cisco VCS X5 cluster to a Cisco VCS X5.2 cluster
create a new cluster of Cisco VCS X5 peers
add an X5 Cisco VCS as a new peer to an existing X5 cluster
remove a peer from an X5 cluster
disband an X5 cluster
change the master peer of an X5 Cisco VCS cluster
change the IP address of an X5 cluster peer
Note: In X3.x the use of Cisco TelePresence Management Suite (Cisco TMS) was essential to the
correct operation of a Cisco VCS cluster because Cisco TMS was in control of copying configuration
from the Master Cisco VCS to the non-master peers.
correct operation of a Cisco VCS cluster because Cisco TMS was in control of copying configuration
from the Master Cisco VCS to the non-master peers.
In X4.1 the Cisco VCS performs the replication of configuration from Master Cisco VCS to non-master
peers and so use of Cisco TMS was optional for clustering. If provisioning was supported, Cisco TMS
was needed.
peers and so use of Cisco TMS was optional for clustering. If provisioning was supported, Cisco TMS
was needed.
In X5.x Cisco TMS is involved in initiating the environment for FindMe replication. Although not
needed to replicate FindMe data throughout the cluster in a running environment, Cisco TMS is
required to perform the initial distribution of the FindMe data throughout the cluster. Cisco TMS is also
required if provisioning is to be supported on Cisco VCSs.
needed to replicate FindMe data throughout the cluster in a running environment, Cisco TMS is
required to perform the initial distribution of the FindMe data throughout the cluster. Cisco TMS is also
required if provisioning is to be supported on Cisco VCSs.
Note: Enabling provisioning and creating a cluster are two separate processes. If you intend to
enable provisioning on your cluster, either:
enable provisioning on your cluster, either:
follow the instructions in this guide to create the cluster of Cisco VCSs (without provisioning
enabled), and then follow the instructions in the Cisco TMS Provisioning Deployment Guide to
enable provisioning across the cluster, or
enabled), and then follow the instructions in the Cisco TMS Provisioning Deployment Guide to
enable provisioning across the cluster, or
follow the instructions in the Cisco TMS Provisioning Deployment Guide to enable provisioning
on what will be the Master Cisco VCS, and then follow the instructions in this guide to create the
cluster of Cisco VCSs.
on what will be the Master Cisco VCS, and then follow the instructions in this guide to create the
cluster of Cisco VCSs.
For creating and modifying clusters that will remain X4 and X3 clusters, see:
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X5)
Page 6 of 72