Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 6 – Troubleshooting
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.2)
Page 60 of 71
2. Remove the VCS from the cluster using: “Remove a live VCS from a VCS X7.2 cluster
3. Log in as root and run “clusterdb_destroy_and_purge_data.sh”.
4. Restore that VCS’s database by restoring a VCS backup taken on that VCS previously.
5. Add the VCS back to the cluster using “Add an X7.2 VCS to a VCS X7.2 cluster (Provisioning
Note: clusterdb_destroy_and_purge_data.sh is as dangerous as it sounds – only use this
command in conjunction with instructions from TAC.
command in conjunction with instructions from TAC.
Cisco TMS
No TMS Agent tabs
If there are no TMS Agent tabs, TMS Agent has to be enabled in TMS. See TMS Provisioning
deployment guide for details about how to do this.
deployment guide for details about how to do this.
Cisco TMS warnings
TMS Cluster Diagnostics
If TMS cluster diagnostics reports a difference in configuration on VCS peers, it is comparing the
output of https://<ip address>/alternatesconfiguration.xml for each VCS.
output of https://<ip address>/alternatesconfiguration.xml for each VCS.
To manually check the differences, on a Unix / Linux system, run:
wget --user=admin --password=<password> --no-check-certificate https://<IP
wget --user=admin --password=<password> --no-check-certificate https://<IP
or FQDN of VCS>/alternatesconfiguration.xml
for each of the VCS peers, then use diff to check for differences.
Conference Factory template does not replicate
This is by design; the Conference Factory %% value is NOT shared between cluster peers and the
Conference Factory application configuration is NOT replicated across a cluster.
Conference Factory application configuration is NOT replicated across a cluster.
See the section “Conference Factory (Multiway™)” above.
VCS’s External manager protocol keeps getting set to HTTPS
TMS can be configured to force specific management settings on connected systems. This includes
ensuring that a VCS uses HTTPS for feedback. If enabled, TMS will (on a time period defined by
TMS) re-configure the VCS’s System > External manager Protocol to HTTPS.
ensuring that a VCS uses HTTPS for feedback. If enabled, TMS will (on a time period defined by
TMS) re-configure the VCS’s System > External manager Protocol to HTTPS.
If HTTPS must be used for VCS to supply feedback to TMS, see details in “Appendix 2 – Adding a
VCS to TMS” to see how to set up certificates etc.
VCS to TMS” to see how to set up certificates etc.
TMS will force HTTPS on VCS if:
Administrative Tools > Configuration > Network Settings, TMS Services > Enforce
Management Settings on Systems = On
and
Management Settings on Systems = On
and
Administrative Tools > Configuration > Network Settings, Secure-Only Device
Communication > Secure-Only Device Communication = On
Communication > Secure-Only Device Communication = On
Set Enforce Management Settings on Systems to Off if TMS does not need to force the
management settings.
management settings.