Cisco Cisco TelePresence Video Communication Server Expressway
Upgrade an X6.0, X6.1, X7.0 or X7.0.n cluster to an X7.0.n cluster
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.0.n)
Page 15 of 63
Upgrade non-master peers
Note: Do not worry about a “Cluster communication failure” alarm – this is expected.
For each non-master peer in the cluster:
1. Backup the Cisco VCS:
a. If the VCS being backed up is version X6.1: log in as root on an SSH or other CLI interface.
At the Cisco VCS command prompt, type:
mkdir /tandberg/persistent/oti
mkdir /tandberg/persistent/oti
mkdir /tandberg/persistent/management
b. Then perform backup as described in “Appendix 1 – Backing up a Cisco VCS”.
Note: You should backup your system before upgrading. If at a later date you need to
downgrade to an earlier version you will need to restore a backup made against that previous
release.
downgrade to an earlier version you will need to restore a backup made against that previous
release.
2. Log in to the non-master peer as admin on an SSH or other CLI interface. Enable maintenance
mode; from the Cisco VCS command line type:
xconfiguration SystemUnit Maintenance Mode: On
3. Log in to the non-master peer as admin on the web interface.
4. Wait for all calls to clear and registrations to timeout on this non-master peer.
If necessary, manually remove any calls on this peer that do not clear automatically (Status >
Calls, then select the check box next to the calls you want to terminate and click Disconnect).
Calls, then select the check box next to the calls you want to terminate and click Disconnect).
5. If necessary, manually remove any registrations from this peer that do not clear automatically
(Status > Registrations > By device, then select the check box next to the devices you want to
remove and click Unregister).
You can leave the registration for the conference factory – this will not be the source of calls, and
even if deleted will not roll over to another peer, as other peers have their own conference factory
registration (if enabled).
remove and click Unregister).
You can leave the registration for the conference factory – this will not be the source of calls, and
even if deleted will not roll over to another peer, as other peers have their own conference factory
registration (if enabled).
On the non-master peer:
6. Upgrade and restart the Cisco VCS (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.
For any further details see the "Upgrading Software" section of the Cisco VCS Administrator
Guide.
through the web interface before restarting the next.
For any further details see the "Upgrading Software" section of the Cisco VCS Administrator
Guide.
Note: The web browser interface may timeout during the restart process, after the progress bar has
reached the end; this may happen if:
reached the end; this may happen if:
Cisco VCS carries out a disk file system check – which it does approximately once every 30
restarts
restarts
Provisioning is enabled, and database re-indexing is in progress
Upgrading the software on this non-master Cisco VCS peer is now complete.
Note:
The upgrade process disables the Cisco VCS’s provisioning functionality — provisioning will be
restored later when Enable TMS Agent Data Replication is enabled.
restored later when Enable TMS Agent Data Replication is enabled.