Guest

Preview Tool

Cisco Bug: CSCvi18351 - TMS does not failover from alternate CMS to primary CMS

Last Modified

Sep 12, 2019

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

15.5 15.6 15.6.1

Description (partial)

Symptom:
If TMS using alternate CMS for meeting allocation, once alternate CMS got password expired or webadmin is not available, TMS does not failover back to available primary CMS. As result, TMS cannot allocate ports on CMS and meetings cannot be scheduled on CMS cluster.

Conditions:
The problem can be reproduced with following steps:
1. Disable webadmin only on CMS1. 
2. Schedule meeting. Meeting allocated. TMS switches to CMS2. Failover works!
3. Enable webadmin on CMS1. Disable webadmin on CMS2. Do a force refresh to be sure that TMS connected to CMS cluster. CMS status is OK in TMS.
4. Schedule meeting. Meeting allocation fails. TMS does not switch to CMS1. Failover failed!
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.