Cisco Cisco TelePresence Video Communication Server Expressway
4.
Wait for all calls to clear and registrations to timeout 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).
to Status > Calls, then select the check box next to the calls you want to terminate and click Disconnect).
—
If necessary, manually remove any registrations from this peer that do not clear automatically (using the web
browser go to Status > Registrations > By device, then select the check box next to the devices you want to
remove and click Unregister).
browser go to 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).
deleted will not roll over to another peer, as other peers have their own Conference Factory registration (if
enabled).
5.
Upgrade and restart the primary VCS (Maintenance > Upgrade).
For any further details see the "Upgrading Software" section of
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, or if it has not checked its disks in the last 6 months.
the end. This may occur if VCS 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 of the software on the primary VCS 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"
Similarly you can ignore any Cisco TMS warnings and emails about cluster problems created during this 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).
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).
On the Primary VCS Peer:
1.
Check that configuration data exists as expected:
—
If FindMe is in use, check that the expected FindMe entries still exist (Status > Applications > TMS
Provisioning Extension Services > FindMe > Accounts).
Provisioning Extension Services > FindMe > Accounts).
—
Check configuration for items from the System, Configuration and Application menus.
2.
Backup the VCS (Maintenance > Backup and restore).
Note
: While VCS 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 VCS.
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 VCS (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.
7
Cisco TelePresence VCS Cluster Creation and Maintenance Deployment Guide