Cisco Cisco TelePresence Management Suite (TMS) Version 15
Understanding how Cisco TMS communicates with managed systems
Cisco TMS Redundancy Deployment Guide
Page 5 of 27
Understanding how Cisco TMS communicates
with managed systems
with managed systems
Cisco TMS uses HTTP/HTTPS when communicating with managed endpoints and infrastructure products.
In addition, SNMP and FTP are used for communicating with some older endpoints, such as the Cisco
TelePresence System MXP series.
In addition, SNMP and FTP are 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 SOHO systems. Each Cisco TMS-
managed system must therefore be configured with an External Manager Address, which is used for
contacting Cisco TMS.
phonebook requests, boot and registration events, and heartbeats from SOHO systems. 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
.
n
The IPv4, IPv6, and Fully Qualified Host Name 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.
for Systems on Internal LAN are used by systems that have their System Connectivity status set to
Reachable on LAN.
n
The Fully Qualified Host Name or IPv4 address specified in Advanced Network Settings for Systems
on Public Internet/Behind Firewall is used by systems that have their System Connectivity status set
to Reachable on Public Internet or Behind Firewall.
on Public Internet/Behind Firewall is used by systems that have their System Connectivity status set
to Reachable on Public Internet or Behind Firewall.
System Connectivity status
The System Connectivity status is configurable when an administrator adds a system to Cisco TMS or at a
later time by going to
later time by going to
Systems > Navigator >
select a system
> Connection
tab
>
System Connectivity in
Cisco TMS. By default systems are set to Reachable on LAN.
If the Enforce Management Settings on Systems setting is set to Yes in
Administrative Tools >
Network Settings > TMS Services
, Cisco TMS periodically pushes server information to systems:
n
The Fully Qualified Host Name (if set) or the IP address (if the Fully Qualified Host Name is not set) is
pushed to systems with System Connectivity status set to Reachable on LAN.
pushed to systems with System Connectivity status set to Reachable on LAN.
n
The TMS Server Address (Fully Qualified Host Name or IPv4 Address) setting is pushed to systems
with System Connectivity status set to Reachable on Public Internet.
with System Connectivity status set to Reachable on Public Internet.
The third System Connectivity option used by Cisco TMS is Behind Firewall. Cisco TMS assumes that
systems set to Behind Firewall are located behind a firewall or a router that uses network address translation
(NAT). Cisco TMS is then unable to connect to the system, for example to instruct it to launch a call. Having
a system set to Behind Firewall status will severely limit what you can do with the system in Cisco TMS.
systems set to Behind Firewall are located behind a firewall or a router that uses network address translation
(NAT). Cisco TMS is then unable to connect to the system, for example to instruct it to launch a call. Having
a system set to Behind Firewall status will severely limit what you can do with the system in Cisco TMS.
Why Cisco TMS changes the System Connectivity status
Cisco TMS will in some cases change the System Connectivity status based on boot and registration
events sent by a system.
events sent by a system.
Whenever a system sends a boot or registration event, Cisco TMS compares the reported IP address with
the HTTP header's source IP address.
the HTTP header's source IP address.