Cisco Cisco Expressway
On the additional non-master Expressway being added to the cluster:
1. Log in as admin on an SSH or other CLI interface. At the Expressway command prompt, type:
xcommand DefaultValuesSet Level: 2
xcommand DefaultLinksAdd
Note: This command removes any LDAP authentication configuration – ensure that you have the web
admin password before executing this command.
admin password before executing this command.
2. Go to
Users > Administrator accounts
.
3. Delete all entries except the default admin account.
4. Go to
System > DNS
and ensure that System host name is the DNS hostname for this Expressway
(typically the same as the System name in
System > Administration
, but excluding spaces, and
unique for each Expressway in the cluster). If it is not configured correctly, set it up appropriately and
click Save.
Note: <System host name>.<DNS domain name> = FQDN of this Expressway
click Save.
Note: <System host name>.<DNS domain name> = FQDN of this Expressway
5. Go to
System > Clustering
and configure the fields as follows:
Cluster name
Identical to the Cluster name configured on the master
Expressway
Expressway
Cluster pre-shared key
Identical to that configured on the master Expressway
Configuration master
Identical to that configured on the master Expressway
Peer 1 IP address …Peer 6 IP address Identical to those configured on the master Expressway
6. Click Save.
Note that a cluster communication failure alarm will be raised on this Expressway peer advising that this
new Expressway is not communicating – this will clear after the restart.
new Expressway is not communicating – this will clear after the restart.
7. Restart the Expressway (go to
Maintenance > Restart options
, then click Restart and confirm OK).
If multiple peers need restarting: restart each peer in turn, waiting for the peer to be accessible through the
web interface before restarting the next peer.
web interface before restarting the next peer.
8. After the restart, wait approximately 2 minutes – this is the frequency with which configuration is copied
from the Master.
9. Go to
Status > Alarms
. If there is an alarm that the Expressway must be restarted, go to
Maintenance >
Restart options
and then click Restart.
If multiple peers need restarting: restart each peer in turn, waiting for the peer to be accessible through the
web interface before restarting the next peer.
web interface before restarting the next peer.
10. Check that configuration data exists as expected (
System
,
Configuration
and
Application
menus).
On other devices:
If you have any other Expressways neighbored (or connected via a traversal zone) to this cluster of
Expressway peers, ensure that their zone configuration for this cluster is updated to include the address of
this new peer.
Expressway peers, ensure that their zone configuration for this cluster is updated to include the address of
this new peer.
On each Expressway peer (including the master and this new Expressway peer):
Go to
Status > Alarms
. If there is an alarm that the Expressway must be restarted, go to
Maintenance >
Restart options
and then click Restart.
Cisco Expressway Cluster Creation and Maintenance Deployment Guide (X8.1)
Page 11 of 34
Adding an Expressway to an existing cluster