Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco TelePresence Video Communication Server (VCS) clusters are designed to extend the resilience and capacity
of a VCS installation. VCS peers in a cluster share bandwidth usage as well as routing, zone, FindMe™ and other
configuration among 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.
of a VCS installation. VCS peers in a cluster share bandwidth usage as well as routing, zone, FindMe™ and other
configuration among 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.
Capacity licensing is carried out on a per-cluster basis. Any capacity 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 license capacity
installed on that peer remains available to the rest of the cluster for two weeks after it lost contact with the peer. This
will maintain the overall license capacity of the cluster. Note that each peer is always limited by its physical capacity;
the license capacity borrowing is only intended to give you time to repair your cluster.
peer are available for use by any peer within the cluster. If a cluster peer becomes unavailable, the license capacity
installed on that peer remains available to the rest of the cluster for two weeks after it lost contact with the peer. This
will maintain the overall license capacity of the cluster. Note that each peer is always limited by its physical capacity;
the license capacity borrowing is only intended to give you time to repair your cluster.
"Capacity" includes the following license types:
■
Traversal and non-traversal call licenses
■
TURN relay licenses
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.
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 guide describes how to create and maintain VCS clusters. It provides information on:
■
■
■
■
■
■
■
■
■
■
Cisco TMS is required if FindMe configuration is to be sourced from Cisco TMS and also if endpoints are to be
provisioned, but is not essential for clustering.
provisioned, but is not essential for clustering.
FindMe can be configured locally on the VCS cluster if required, but be aware that if FindMe data is stored on the
VCS cluster and not sourced by Cisco TMS, there is no way to later move that FindMe information to Cisco TMS.
VCS cluster and not sourced by Cisco TMS, there is no way to later move that FindMe information to Cisco TMS.
Enabling provisioning and creating a cluster are two separate processes. If you intend to enable provisioning on your
cluster, either:
cluster, either:
■
follow the instructions in this guide to create the cluster of VCSs (without provisioning enabled), and then
follow the instructions in Cisco TMS Provisioning Extension Deployment Guide to enable provisioning across
the cluster, or
follow the instructions in Cisco TMS Provisioning Extension Deployment Guide to enable provisioning across
the cluster, or
■
follow the instructions in Cisco TMS Provisioning Extension Deployment Guide to enable provisioning on what
will be the primary VCS, and then follow the instructions in this guide to create the cluster of VCSs
will be the primary VCS, and then follow the instructions in this guide to create the cluster of VCSs
Note that VCS X8 and later supports only Cisco TMS Provisioning Extension mode.
For more information about TMS Agent legacy mode provisioning, or for creating, modifying, and troubleshooting
clusters that will remain running on earlier software versions, see earlier versions of this deployment guide. Also, see
clusters that will remain running on earlier software versions, see earlier versions of this deployment guide. Also, see
for information about upgrading these clusters to X8.8.
6
Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide
Introduction