Cisco Cisco TelePresence Video Communication Server Expressway
Upgrade an X7.1 cluster to an X7.2 cluster (Provisioning Extension mode)
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.2)
Page 15 of 71
On the Master VCS peer web interface:
1. Upgrade and restart the Master VCS (Maintenance > Upgrade).
For any further details see the "Upgrading Software" section of the VCS 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 VCS carries out a disk file system check – which it does
approximately once every 30 restarts
has reached the end. This may occur if VCS carries out a disk file system check – which it does
approximately once every 30 restarts
Upgrading of the software on the Master VCS is now complete.
Note: Do not worry about cluster-related alarms that occur during the upgrade process, for example
“Cluster communication failure” alarm on the Master or any non-master peers – this is expected.
“Cluster replication error: cannot find master or this slave’s peer configuration file, manual
synchronization of configuration is required”
synchronization of configuration is required”
Similarly do not worry about TMS warnings and emails about cluster problems created during this
upgrade.
upgrade.
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).
cluster data synchronization has occurred (they should clear within 10 minutes of the complete
upgrade).
On the Master VCS peer:
1. Check that the expected FindMe entries still exist on this master VCS (Status > Applications >
TMS Provisioning Extension Services > FindMe > Accounts).
2. Check that other configuration (including zone configuration, transforms and other configuration
for items from the System, VCS Configuration and Application menus) is as expected.
3. Backup the master VCS (See “Appendix 1 – Backing up a VCS” for details).
Note: It is recommended that while VCS peers are running different versions of code, configuration
changes to any VCS in the cluster are limited to the changes needed to complete the upgrade.
Configuration changes will not be replicated across VCS peers that are not running the same version
of software as the master VCS.
changes to any VCS in the cluster are limited to the changes needed to complete the upgrade.
Configuration changes will not be replicated across VCS peers that are not running the same version
of software as the master VCS.
Upgrade non-master peers
Note: Do not worry about cluster-related alarms that occur during the upgrade process – these are
expected.
expected.
For each non-master peer in the cluster:
1. Backup the VCS:
a. Details of how to perform a backup are described in “Appendix 1 – Backing up a VCS”.
Note: 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.
downgrade to an earlier version, to restore the configuration 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 VCS command line type:
xconfiguration SystemUnit Maintenance Mode: On
3. Log in to the non-master peer as admin on the web interface.