Cisco Cisco TelePresence Video Communication Server Expressway
Upgrade an X5.1, X5.1.1 or X5.2 cluster to an X6.0 cluster
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X6)
Page 16 of 76
chown nobody:nobody /tandberg/persistent/oti/server/x5 -R
15. Repeat these steps, choosing option 5 again, to make sure that this has cured the problem.
If Cisco TMS is used, on Cisco TMS:
Ensure that Cisco TMS has all the correct settings for this upgraded Cisco VCS by forcing a refresh of
Cisco TMS.
Cisco TMS.
1. Go to Systems > Navigator (and any required sub folders) and select the Master Cisco VCS.
2. Select the Settings tab.
3. Click Force Refresh.
4. Select the TMS Agent tab
a. ensure that Enable TMS Agent Data Replication is selected.
b. ensure that Authentication Scheme is set to Digest.
If any changes need to be made, click Save Settings.
Note: If TMS Agent Data Replication reports Disabled then there is a problem. On Cisco TMS select
Administrative Tools > Activity Status and look for the Description ‘Enable TMS Agent Data
Replication for system(s): <VCS name(s)>’. Click on the description for a full listing of the Activity log
associated with this action. Identify and fix any reported problems.
Administrative Tools > Activity Status and look for the Description ‘Enable TMS Agent Data
Replication for system(s): <VCS name(s)>’. Click on the description for a full listing of the Activity log
associated with this action. Identify and fix any reported problems.
On this Master Cisco VCS:
5. Log in to the web browser of this Cisco VCS.
6. Check the Warnings page (Status > Warnings):
a. If required, restart the Cisco VCS.
b. If “Security Alert: the TMS agent database has the default LDAP password set” or “Security
Alert: the TMS agent database has the default replication password set” appear, see the
relevant section in ‘Appendix 7 – Troubleshooting’.
relevant section in ‘Appendix 7 – Troubleshooting’.
7. Disable maintenance mode. From the Cisco VCS command line type:
xconfiguration SystemUnit Maintenance Mode: Off
Upgrade non-master peers
If several non-master peers need upgrading, the upgrades may be carried out one at a time, or in
parallel. The downloading of software and rebooting can be carried out on all non-master peers at the
same time.
parallel. The downloading of software and rebooting can be carried out on all non-master peers at the
same time.
The process below handles the ‘all at the same’ case, if upgrades are to be done one at a time, carry
out the process “Upgrade non-master peers” and ”Add an X6.0 VCS to the VCS X6.0 cluster” for the
first non-master Cisco VCS, then repeat for each and every subsequent non-master Cisco VCS.
out the process “Upgrade non-master peers” and ”Add an X6.0 VCS to the VCS X6.0 cluster” for the
first non-master Cisco VCS, then repeat for each and every subsequent non-master Cisco VCS.
For each non-master peer in the cluster:
1. Enable maintenance mode.
From the Cisco VCS command line type:
xconfiguration SystemUnit Maintenance Mode: On
2. Wait for all calls to clear and registrations to timeout. If necessary, manually remove any calls that
do not clear automatically (Status > Calls, then select the check box next to the calls you want to
terminate and click Disconnect).
terminate and click Disconnect).
3. If necessary, manually remove any registrations 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).
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).