Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Preface
Change History
Date
Change
Reason
May
2016
2016
Cisco TMS Support for Two-Node Conductor Clusters feature is no longer in preview
status.
status.
Cisco
TMS15.2.1
TMS15.2.1
April
2016
2016
Addition of new features.
Cisco TMS
15.2.1
15.2.1
Table 1
Software Release Notes Change History
Product Documentation
The following documents provide guidance on installation, initial configuration, and operation of the product:
■
■
■
New Features in 15.2.1
ESXi 6.0 Support
Cisco TMS now supports ESXi 6.0. It also works with the previous version 5.5.
Cisco TMS Support for Two-Node Conductor Clusters
TelePresence Conductor cluster support has been added to Cisco TMS.
You can configure Cisco TMS to automatically transfer to the subordinate Conductor if the primary Conductor node fails.
Cisco TMS monitors the status of the primary node through a mix of polling and feedback requests. Failover happens
only while the primary node is down, and Cisco TMS reroutes to the primary Conductor when it is available again.
Cisco TMS monitors the status of the primary node through a mix of polling and feedback requests. Failover happens
only while the primary node is down, and Cisco TMS reroutes to the primary Conductor when it is available again.
Cisco TMS support for two-node Conductor clusters allows TMS to continue to manage scheduled meetings after a
Conductor node failure, without requiring manual intervention on the TMS.
Conductor node failure, without requiring manual intervention on the TMS.
The following elements have been added to Cisco TMS user interface:
■
In Systems > Navigator, the Clustering tab has been added for each clustered TelePresence Conductor to view
the status of primary and peer TelePresence Conductors.
the status of primary and peer TelePresence Conductors.
■
A new Conductorfailover-liveservice log is introduced and enabled by default. It records all occurrences of
failover transfers between TelePresence Conductor nodes.
failover transfers between TelePresence Conductor nodes.
You can still add a primary TelePresence Conductor that is down for maintenance and marked in red.
For future compatibility we recommend that TelePresence Conductor clusters are configured with no more than two
nodes. If you currently deploy three-node clusters, you should consider removing a node. Cisco may discontinue the
ability to add a third node to a cluster in a future software release.
nodes. If you currently deploy three-node clusters, you should consider removing a node. Cisco may discontinue the
ability to add a third node to a cluster in a future software release.
While the primary node is down you can continue to schedule meetings as normal, without any manual intervention on
the TMS. Some Conference Control Center functions are also available. If the primary node is still down at the scheduled
start time, TMS switches the meeting to the subordinate node. Note that TMS does not display the subordinate node as
the TMS. Some Conference Control Center functions are also available. If the primary node is still down at the scheduled
start time, TMS switches the meeting to the subordinate node. Note that TMS does not display the subordinate node as
3
Cisco TelePresence Management Suite Software Release Notes