Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 6 – Troubleshooting
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X7.0.n)
Page 52 of 63
5. Add the Cisco VCS back to the cluster using “Add an X7.0.n VCS to a VCS X7.0.n cluster (n is
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 the “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 Cisco VCS peers, it is comparing
the output of https://<ip address>/alternatesconfiguration.xml for each Cisco VCS.
the output of https://<ip address>/alternatesconfiguration.xml for each Cisco 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 Cisco 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
Cisco TMS can be configured to force specific management settings on connected systems. This
includes ensuring that a Cisco VCS uses HTTPS for feedback. If enabled, Cisco TMS will (on a time
period defined by Cisco TMS) re-configure the Cisco VCS’s System > External manager Protocol to
HTTPS.
includes ensuring that a Cisco VCS uses HTTPS for feedback. If enabled, Cisco TMS will (on a time
period defined by Cisco TMS) re-configure the Cisco VCS’s System > External manager Protocol to
HTTPS.
If HTTPS must be used for Cisco VCS to supply feedback to Cisco TMS, see details in “Appendix 2 –
Adding a Cisco VCS to Cisco TMS” to see how to set up certificates etc.
Adding a Cisco VCS to Cisco TMS” to see how to set up certificates etc.
Cisco TMS will force HTTPS on Cisco 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 Cisco TMS does not need to force the
management settings.
management settings.
Set Secure-Only Device Communication to Off if it is unnecessary for Cisco VCS to provide
feedback to Cisco TMS using HTTPS (if HTTP is sufficient).
feedback to Cisco TMS using HTTPS (if HTTP is sufficient).