Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 7 – Troubleshooting
Cisco VCS Deployment Guide: Cluster creation and maintenance (Cisco VCS X6)
Page 63 of 76
Cluster script, option 5
“WARNING: There are more Public Keys than there are cluster peers.”
If, when running Cluster script option 5 you receive a status: “WARNING: There are more Public Keys
than there are cluster peers.” this means that the Cisco VCS has been a member of a cluster in the
past and that cluster was not disbanded properly, or the Cisco VCS was not removed from the cluster
properly.
than there are cluster peers.” this means that the Cisco VCS has been a member of a cluster in the
past and that cluster was not disbanded properly, or the Cisco VCS was not removed from the cluster
properly.
Cluster keys are kept in the directory /tandberg/.ssh
Cluster key looks like rsynch-aaa.bbb.ccc.ddd.pub
- where aaa.bbb.ccc.ddd is the IP address of the Cisco VCS peer to which they belong.
- where aaa.bbb.ccc.ddd is the IP address of the Cisco VCS peer to which they belong.
Delete any keys (whose name starts rsynch and end .pub) whose IP address does not match a Cisco
VCS in the cluster.
VCS in the cluster.
Do not delete any other files in this directory.
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 3 –
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).