Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.1)
Page 6 of 69
Introduction
Cisco TelePresence Video Communication Server (Cisco VCS) clusters are designed to extend the
resilience and capacity of a Cisco VCS installation. VCS peers in a cluster share bandwidth usage as
well as routing, zone, FindMe™ and other configuration amongst themselves. Endpoints can register
to any of the peers 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. VCS peers in a cluster share bandwidth usage as
well as routing, zone, FindMe™ and other configuration amongst themselves. Endpoints can register
to any of the peers 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-cluster basis. Any traversal or non-traversal call licenses that
have been installed on a cluster peer are available for use by any peer within the cluster. If a cluster
peer becomes unavailable, the call licenses installed on that peer will remain available to the rest of
the cluster peers for two weeks from the time the cluster lost contact with the peer. This will maintain
the overall license capacity of the cluster — however, note that each peer is limited by its physical
capacity (500 non-traversal calls and 100 traversal calls).
have been installed on a cluster peer are available for use by any peer within the cluster. If a cluster
peer becomes unavailable, the call licenses installed on that peer will remain available to the rest of
the cluster peers for two weeks from the time the cluster lost contact with the peer. This will maintain
the overall license capacity of the cluster — however, note that each peer is limited by its physical
capacity (500 non-traversal calls and 100 traversal calls).
Every VCS peer in the cluster must have the same routing capabilities — if any VCS can route a call
to a destination it is assumed that all VCS peers in that cluster can route a call to that destination. If
the routing is different on different VCS peers, then separate VCSs / VCS clusters must be used.
to a destination it is assumed that all VCS peers in that cluster can route a call to that destination. If
the routing is different on different VCS peers, then separate VCSs / VCS clusters must be used.
This deployment guide describes how to create, modify and upgrade to X7.1 VCS clusters. It provides
information on how to:
information on how to:
Upgrade an X7.1 cluster to an X7.1 cluster (Provisioning Extension mode)
Upgrade X5.2 or earlier versions to X7.1
Note:
In X5.x, X6.x, X7.0.n and X7.1 in TMS Agent Legacy mode, TMS is involved in initiating the
environment for FindMe replication. Although not needed to replicate FindMe data throughout the
cluster in a running environment, TMS is required to perform the initial distribution of the FindMe data
throughout the cluster. TMS is also required if provisioning is to be supported on VCSs.
environment for FindMe replication. Although not needed to replicate FindMe data throughout the
cluster in a running environment, TMS is required to perform the initial distribution of the FindMe data
throughout the cluster. TMS is also required if provisioning is to be supported on VCSs.
X7.1 in Provisioning Extension mode: TMS is required if FindMe configuration is to be sourced from
TMS and also if endpoints are to be provisioned. TMS is not needed to set up cluster, and FindMe
can be configured locally on the VCS cluster if required. (If FindMe is stored locally on the VCS
cluster and not sourced by TMS, there is no way at a later date to move that FindMe information to
TMS.)
TMS and also if endpoints are to be provisioned. TMS is not needed to set up cluster, and FindMe
can be configured locally on the VCS cluster if required. (If FindMe is stored locally on the VCS
cluster and not sourced by TMS, there is no way at a later date to move that FindMe information to
TMS.)