Cisco Cisco Expressway
■
"Cluster communication failure" alarm on the primary or any subordinate peers – this is expected.
■
"Cluster replication error: cannot find master or this slave’s peer configuration file, manual synchronization of
configuration is required"
configuration is required"
Theses alarms and warnings are expected and will clear when all cluster peers are upgraded and cluster data
synchronization has occurred (they should clear within 10 minutes of the complete upgrade).
synchronization has occurred (they should clear within 10 minutes of the complete upgrade).
On the Primary Expressway Peer:
1.
Check that configuration data exists as expected (System, Configuration and Application menus).
2.
Backup the Expressway (Maintenance > Backup and restore).
Note
: While Expressway peers are running different versions of code, do not make any changes except what you need
to do to upgrade. The cluster does not replicate changes to any peers that are on different versions to the primary
Expressway.
Expressway.
Upgrade Subordinate Peers
You can ignore any cluster-related alarms that occur during the upgrade process – these are expected.
1.
Log in to the subordinate peer as admin on the web interface.
2.
Backup the Expressway (Maintenance > Backup and restore).
You should backup your system before upgrading. If at a later date you need to downgrade to an earlier version,
to restore the configuration you will need to restore a backup made against that previous release.
to restore the configuration you will need to restore a backup made against that previous release.
3.
Enable maintenance mode:
a.
Go to Maintenance > Maintenance mode.
b.
Set Maintenance mode to
On.
c.
Click Save and click OK on the confirmation dialog.
4.
Wait for all calls to clear on this peer.
If necessary, manually remove any calls on this peer that do not clear automatically (using the web browser go to
Status > Calls, then select the check box next to the calls you want to terminate and click Disconnect).
Status > Calls, then select the check box next to the calls you want to terminate and click Disconnect).
5.
Upgrade and restart the Expressway (Maintenance > Upgrade).
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.
interface before restarting the next peer.
For any further details see the "Upgrading Software" section of
Expressway Administrator Guide.
Note that the web browser interface may timeout during the restart process, after the progress bar has reached
the end. This may occur if Expressway carries out a disk file system check – which it does approximately once
every 30 restarts, or if it has not checked its disks in the last 6 months.
the end. This may occur if Expressway carries out a disk file system check – which it does approximately once
every 30 restarts, or if it has not checked its disks in the last 6 months.
Upgrading the software on this subordinate Expressway peer is now complete.
Cluster-related alarms
You can ignore any cluster-related alarms that occur during the upgrade process, for example:
■
"Cluster communication failure" alarm on the primary or any subordinate peers – this is expected.
■
"Cluster replication error: cannot find master or this slave’s peer configuration file, manual synchronization of
configuration is required"
configuration is required"
Theses alarms and warnings are expected and will clear when all cluster peers are upgraded and cluster data
synchronization has occurred (they should clear within 10 minutes of the complete upgrade).
synchronization has occurred (they should clear within 10 minutes of the complete upgrade).
6
Cisco Expressway Cluster Creation and Maintenance Deployment Guide