Cisco Cisco Expressway
Prerequisites
Before setting up a cluster of X8.8 Expressway peers or adding an X8.8 Expressway 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.
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.
■
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.
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.
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 Expressway in or to
be added to the cluster.
be added to the cluster.
■
Each peer in a cluster is directly routable to each and every other Expressway 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.)
(There 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 to all other peers.
■
Each peer has a certificate that identifies it to other peers, for creating permissive TLS connections between
peers (default). If you want to enforce TLS, the certificate must also be valid and must be issued by an
authority that is trusted by all peers.
peers (default). If you want to enforce TLS, the certificate must also be valid and must be issued by an
authority that is trusted by all peers.
■
All peers have the same set of option keys installed, with the following exceptions:
—
Rich Media Sessions
—
Room system and desktop system registration licenses
—
TURN relay licenses
All other license keys must be identical on each peer.
Note:
Installing some types of option keys requires you to restart the Expressway.
■
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 Expressway peers must support both forward and reverse DNS lookups of Cisco
TMS and all Expressway peer addresses; the DNS servers must also provide address lookup for any other DNS
functionality required, such as:
TMS and all Expressway 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 FE 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.
6
Cisco Expressway Cluster Creation and Maintenance Deployment Guide
Prerequisites