Cisco Cisco Expressway
Create a New Cluster of Expressway Peers
Note
: This procedure requires a period of downtime for the Expressway service. Ensure that these instructions are
followed in a scheduled maintenance window.
Process Summary
This process initiates a cluster of a single Expressway. Do not use this process if the cluster already exists.
To complete the cluster containing multiple Expressways, when this section is complete, follow the instructions in
to add the subordinate peers to the cluster.
Prerequisites
■
If a firewall exists between cluster peers, it must be configured to permit the traffic documented in
.
■
All Expressways to be included in the cluster must be running the same version (X8.7) of Expressway software.
Configure the Primary Peer
This process sets up the first (primary) peer of this new cluster – additional peers are added afterwards using the
process.
Before proceeding, the Expressway that will be the primary must be determined. The primary Expressway will be the
source of the configuration information for all Expressway peers in the cluster. Subordinate Expressway peers will have
their configuration deleted and replaced by that from the primary.
source of the configuration information for all Expressway peers in the cluster. Subordinate Expressway peers will have
their configuration deleted and replaced by that from the primary.
On other Expressways:
Check that no other Expressway (anywhere in the organization) has this Expressway’s IP address in its clustering peers
list.
list.
On this primary Expressway:
1.
Check that the Expressway is running X8.7 software.
2.
Backup the Expressway (Maintenance > Backup and restore).
3.
Using the web interface, review the configuration to ensure that the Expressway has:
—
A valid Ethernet speed (System > Network interfaces > Ethernet).
—
Valid IP address and IP gateway (System > Network interfaces > IP).
—
The same set of option keys installed as those that will be installed on all other peers of the cluster
(
(
Maintenance > Option keys
).
Note that the number of call license keys may be different on different peers; all other license keys must be
identical on each peer.
identical on each peer.
—
At least one valid DNS server configured, and that if unqualified DNS names are used elsewhere (e.g. for the
NTP server), that the correct Domain name is also configured (Domain name is added as a suffix to an
unqualified DNS name to make it into an FQDN) (System > DNS).
NTP server), that the correct Domain name is also configured (Domain name is added as a suffix to an
unqualified DNS name to make it into an FQDN) (System > DNS).
—
A valid and working NTP server configured (System > Time; in the Status section, the State should be
“
“
Synchronized
”).
—
No peers configured (System > Clustering – all Peer x IP address fields on this page should be blank. If not,
delete any entries and click Save).
delete any entries and click Save).
—
H.323 Mode set to
On (Configuration > Protocols > H.323)
8
Cisco Expressway Cluster Creation and Maintenance Deployment Guide