Cisco Cisco TelePresence Video Communication Server Expressway
Prerequisites
Before setting up a cluster of X8.7 VCS peers or adding an X8.7 VCS to a cluster, ensure that:
Platform and Software Versions Match
■
All clusters peers are running the same version of code. The only occasion where different peers are 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, during which time the cluster will operate in a partitioned fashion.
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, during which time the cluster will operate in a partitioned fashion.
■
Each peer is using a hardware platform (appliance or virtual machine) with equivalent capabilities; for example,
you can cluster peers that are running on standard appliances with peers running on 2 core Medium VMs, but
you cannot cluster a peer running on a standard appliance with peers running on 8 core Large VMs.
you can cluster peers that are running on standard appliances with peers running on 2 core Medium VMs, but
you cannot cluster a peer running on a standard appliance with peers running on 8 core Large VMs.
Network Conditions Are Met
■
Each peer has a different LAN configuration (a different IPv4 address and a different IPv6 address, where
enabled).
enabled).
■
Each 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.
added to the cluster.
■
Each peer in a cluster is 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.)
must be no NAT between cluster peers – if there is a firewall ensure that the required ports are opened.)
Basic Configuration Is Done
■
Each peer has a different system name.
■
All 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.
each peer.
—
The VCS must be restarted after installing some option keys in order to fully activate them.
■
H.323 mode is enabled on each peer (Configuration > Protocols > H.323, and for H.323 mode select
On).
The cluster uses H.323 signaling between peers to determine the best route for calls, even if all endpoints are
SIP endpoints.
SIP endpoints.
DNS Configuration is Done
■
The DNS servers used by the VCS peers must support both forward and reverse DNS lookups of Cisco TMS and
all VCS peer addresses; the DNS servers must also provide address lookup for any other DNS functionality
required, such as:
all VCS peer addresses; the DNS servers must also provide address lookup for any other DNS functionality
required, such as:
—
NTP servers or the external manager if they configured using DNS names
—
Microsoft Lync Server FQDN lookup
—
LDAP server forward and reverse lookup (reverse lookups are frequently provided through PTR records)
Note:
DNS server configuration does not replicate and you must configure the DNS server address on each peer.
■
A DNS SRV record is available for the cluster which contains A or AAAA records for each peer of the cluster.
This configuration is advised for video interoperability and business to business (B2B) video calling, but is not
required for Mobile and Remote Access.
required for Mobile and Remote Access.
■
(For MRA) Create a
collab-edge
SRV record for each peer in the VCS Expressway cluster
■
(For B2B only) The VCS Expressway cluster has a DNS SRV record that defines all cluster peers
TMS Has Been Configured (if necessary)
■
Cisco TMS, if used, is running version 13.2 or later (12.6 or later is permitted if you are not using Cisco TMS for
provisioning or FindMe).
provisioning or FindMe).
4
Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide