Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Introduction
Introduction
Software version 13.1 is a maintenance release. This document lists and describes the caveats solved
for this release.
for this release.
CAUTION: You must back up your configuration before upgrading to 13.1. You must also
remember the administrator user name and password for the backup configuration. You will
need these if you ever need to make use of this backup file.
remember the administrator user name and password for the backup configuration. You will
need these if you ever need to make use of this backup file.
Software dependencies and upgrades
There is a software dependency between Cisco TMS 13.1 and VCS X5 or greater. If your installation
uses the TMS Provisioning directory functionality for Movi deployments and you are upgrading TMS
from either software version 12.1 or 12.2, you must follow the upgrade procedures the document
uses the TMS Provisioning directory functionality for Movi deployments and you are upgrading TMS
from either software version 12.1 or 12.2, you must follow the upgrade procedures the document
When installing and upgrading to Cisco TMS 13.1, and if the TMS Agent is being utilized or intended
to be utilized, Cisco recommends that you upgrade the Cisco VCS to X5.2 or later.
to be utilized, Cisco recommends that you upgrade the Cisco VCS to X5.2 or later.
During initial Cisco TMS 13.1 installs, the Enable TMS Agents found under Administrative Tools >
General Settings is now set to No by default. To enable the TMS Agent in the Cisco TMS, the
administrator must set this to Yes. Cisco recommends that after setting the Enable TMS Agents to
Yes in the Cisco TMS, that the administrator confirm that the Local TMS Agent in the TMS Agent
Diagnostics shows no errors and that all diagnostic tests are OK. The TMS Agent Diagnostics can be
found under Administrator Tools > TMS Agent Diagnostics. If any errors are found on the Local
TMS Agent, then these errors need to be fixed before proceeding with replication to the Cisco VCS(s).
Refer to the Diagnostic section within the latest available Provisioning Deployment Guide and X5.1.1
for troubleshooting any errors found on the Local TMS Agent or contact your local Cisco partner or
customer support for assistance.
General Settings is now set to No by default. To enable the TMS Agent in the Cisco TMS, the
administrator must set this to Yes. Cisco recommends that after setting the Enable TMS Agents to
Yes in the Cisco TMS, that the administrator confirm that the Local TMS Agent in the TMS Agent
Diagnostics shows no errors and that all diagnostic tests are OK. The TMS Agent Diagnostics can be
found under Administrator Tools > TMS Agent Diagnostics. If any errors are found on the Local
TMS Agent, then these errors need to be fixed before proceeding with replication to the Cisco VCS(s).
Refer to the Diagnostic section within the latest available Provisioning Deployment Guide and X5.1.1
for troubleshooting any errors found on the Local TMS Agent or contact your local Cisco partner or
customer support for assistance.
Note: Upgrades will be blocked if the procedures found in this document are not followed
appropriately. The error message will state that Provisioning on all clusters must be disabled before
upgrading to 13.1.
appropriately. The error message will state that Provisioning on all clusters must be disabled before
upgrading to 13.1.
For the proper installation of the OpenDS and Provisioning components, MS DOS or access to
execute *.cmd and *.bat files (not necessarily the command prompt) must be available on the server
during installation and upgrades.
execute *.cmd and *.bat files (not necessarily the command prompt) must be available on the server
during installation and upgrades.
DNS records and Provisioning Directory functionality (TMS Agent)
For installations using the TMS Provisioning Directory functionality for Movi and E20 deployments, the
local hostname of the Cisco TMS server must match the DNS A record for the TMS Agent to operate
correctly. Before starting any upgrade, ensure that the DNS servers used by Cisco TMS contain
forward lookups for the Cisco TMS server. DNS reverse lookups (PTR records) that were required in
TMS 12.5, are no longer required for Cisco TMS 13.1.
local hostname of the Cisco TMS server must match the DNS A record for the TMS Agent to operate
correctly. Before starting any upgrade, ensure that the DNS servers used by Cisco TMS contain
forward lookups for the Cisco TMS server. DNS reverse lookups (PTR records) that were required in
TMS 12.5, are no longer required for Cisco TMS 13.1.
Note: The same DNS requirement applies to the Cisco VCS. See