Cisco Cisco TelePresence Video Communication Server Expressway
Prerequisites
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.1)
Page 8 of 69
Prerequisites
VCS clusters peers must all run the same version of code, for example all X7.1, all X7.0.2 or all X6.1.
The only occasion where different peers should be allowed to run different versions of code is for the
short period of time while a cluster is being upgraded from one version of code to another.
The only occasion where different peers should be allowed to run different versions of code is for the
short period of time while a cluster is being upgraded from one version of code to another.
Before setting up a cluster of X7.1 VCS peers or adding an X7.1 VCS to a cluster, ensure that:
a DNS SRV record is available for the cluster which contains A or AAA records for each peer of
the cluster
the cluster
each and every VCS peer in a cluster is within a 15ms hop (30ms round trip delay) of each and
every other VCS in or to be added to the cluster
every other VCS in or to be added to the cluster
each and every VCS peer in a cluster must be directly routable to each and every other VCS in or
to be added to the cluster. (There must be no NAT between cluster peers – if there is a firewall
ensure that the required ports are opened.)
to be added to the cluster. (There must be no NAT between cluster peers – if there is a firewall
ensure that the required ports are opened.)
all VCS peers have the same set of option keys installed
•
•
the number of call license keys may be different on different peers; all other license keys
must be identical on each peer
must be identical on each peer
•
the VCS must be restarted after installing some option keys in order to fully activate them
the Cisco TMS version being run is TMS 12.6 or later (TMS 13.2 or later is required if using
Provision Extension mode)
Provision Extension mode)
each VCS has a different system name
H.323 mode is enabled on each VCS (
VCS configuration > Protocols > H.323
, and for H.323
mode select On) – H.323 communications are used between cluster peers
the VCS cluster has a DNS SRV record that defines all cluster peers
the DNS servers used by the VCS peers must support both forward and reverse DNS lookups of
TMS and all VCS peer addresses; the DNS servers must also provide address lookup for any
other DNS functionality required (for example: system servers like NTP and the external manager
that are configured using DNS names, Microsoft OCS/Lync Server FQDN lookup, LDAP server
forward and reverse lookup); note that reverse lookups are frequently provided through PTR
records
TMS and all VCS peer addresses; the DNS servers must also provide address lookup for any
other DNS functionality required (for example: system servers like NTP and the external manager
that are configured using DNS names, Microsoft OCS/Lync Server FQDN lookup, LDAP server
forward and reverse lookup); note that reverse lookups are frequently provided through PTR
records
If TMS is to be used for replicating FindMe and/or Provisioning data, ensure that TMS Agent
Legacy mode or Provisioning Extension mode functionality has been enabled on TMS (see TMS
provisioning deployment guide for details).
Legacy mode or Provisioning Extension mode functionality has been enabled on TMS (see TMS
provisioning deployment guide for details).