Cisco Cisco Expressway
Introduction
Cisco Expressway (Expressway) clusters are designed to extend the resilience and capacity of an Expressway
installation. Expressway 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.
installation. Expressway 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:
■
Rich Media Session licenses
■
Room system and desktop system registration licenses
■
TURN relay licenses
Every Expressway peer in the cluster must have the same routing capabilities — if any Expressway can route a call to a
destination it is assumed that all Expressway peers in that cluster can route a call to that destination. If the routing is
different on different Expressway peers, then separate Expressways / Expressway clusters must be used.
destination it is assumed that all Expressway peers in that cluster can route a call to that destination. If the routing is
different on different Expressway peers, then separate Expressways / Expressway clusters must be used.
This guide describes how to create and maintain Expressway 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.
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 Expressways (without provisioning enabled), and
then follow the instructions in Cisco TMS Provisioning Extension Deployment Guide to enable provisioning
across the cluster, or
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 on what
will be the primary Expressway, and then follow the instructions in this guide to create the cluster of
Expressways
will be the primary Expressway, and then follow the instructions in this guide to create the cluster of
Expressways
5
Cisco Expressway Cluster Creation and Maintenance Deployment Guide
Introduction