Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Unmanaged bridges and unmanaged endpoints must also be manually added to Cisco TMS. Configurations for these
systems must be manually set for each unit, as automatic configuration is not possible for unsupported systems.
systems must be manually set for each unit, as automatic configuration is not possible for unsupported systems.
For instructions, see:
■
■
■
Through Unified CM
When a Unified CM is added to Cisco TMS, a list of telepresence endpoints registered to Unified CM is made available.
Administrators can use this list to add the endpoints to Cisco TMS for limited management.
.
Provisioning
Provisioning using Cisco TelePresence Management Suite Provisioning Extension (Cisco TMSPE) is recommended as
the most flexible and scalable way of registering and configuring large quantities of endpoints.
the most flexible and scalable way of registering and configuring large quantities of endpoints.
Note that this provisioning model does not actually add the endpoints themselves to Cisco TMS; the provisioning is user-
based, not device-based. This also means that the configuration received by the endpoint will depend on the user
signed in to the endpoint.
based, not device-based. This also means that the configuration received by the endpoint will depend on the user
signed in to the endpoint.
.
Pre-registration
Pre-registering endpoints in Cisco TMS is a legacy and smaller-scale alternative to provisioning. Up to 10 endpoints can
be pre-registered at a time to any folder.
be pre-registered at a time to any folder.
Pre-registration uses IP address, MAC address or, for legacy systems, serial number, to let the endpoint be recognized
instantly when it comes online, added as a Cisco TMS-controlled system, and configured as specified during pre-regis-
tration.
instantly when it comes online, added as a Cisco TMS-controlled system, and configured as specified during pre-regis-
tration.
Note that infrastructure systems may not be pre-registered.
How Cisco TMS Communicates with Managed Systems
Cisco TMS uses HTTP/HTTPS when communicating with managed endpoints and infrastructure products. In addition,
SNMP is used for communicating with some older endpoints, such as the Cisco TelePresence System MXP series.
SNMP is used for communicating with some older endpoints, such as the Cisco TelePresence System MXP series.
Managed systems also initiate connections to Cisco TMS. Examples of such connections include phonebook requests,
boot and registration events, and heartbeats from systems behind a firewall. Each Cisco TMS-managed system must
therefore be configured with an External Manager Address, which is used for contacting Cisco TMS.
boot and registration events, and heartbeats from systems behind a firewall. Each Cisco TMS-managed system must
therefore be configured with an External Manager Address, which is used for contacting Cisco TMS.
The Addresses that Systems Use to Contact Cisco TMS
You specify addresses that systems use for contacting Cisco TMS by going to
Administrative Tools > Configuration >
Network Settings
.
■
The IPv4, IPv6, and Fully Qualified Hostname addresses specified in the
Advanced Network Settings for Systems
on Internal LAN
are used by systems that have their System Connectivity status set to
Reachable on LAN.
39
Cisco TelePresence Management Suite Administrator Guide
System Management Overview