Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Network topology and communication with managed systems
Incoming network traffic from users and managed systems is routed to the Cisco TMS servers through the
NLB. A Virtual IP address (VIP) must be assigned to the NLB, and a DNS record must be created pointing to
the NLB’s VIP. The VIP (or associated DNS record) is then used as the management and feedback address
for all managed systems.
NLB. A Virtual IP address (VIP) must be assigned to the NLB, and a DNS record must be created pointing to
the NLB’s VIP. The VIP (or associated DNS record) is then used as the management and feedback address
for all managed systems.
The NLB's hostname and IP address(es) must be entered in Cisco TMS
> Administrative Tools >
Configuration > Network Settings >
Advanced Network Settings for Systems on Internal LAN and
Advanced Network Settings for Systems on Public Internet/Behind Firewall.
Once the IP address and hostname values in
Network Settings
have been changed, the Database Scanner
service enforces these new network settings on the managed systems. The systems then start directing
traffic to the NLB, which forwards the requests to the Cisco TMS servers.
traffic to the NLB, which forwards the requests to the Cisco TMS servers.
Outgoing traffic from Cisco TMS’s own services does not go through the NLB; the active Cisco TMS node
will bypass the NLB when managing systems. For this reason, Cisco TMS’s logic for automatically updating
the system connectivity setting and parameters based on information in IP protocol headers is disabled when
Cisco TMS redundancy is enabled. For further information on how Cisco TMS communicates with managed
systems, refer to the chapter System management overview in the
will bypass the NLB when managing systems. For this reason, Cisco TMS’s logic for automatically updating
the system connectivity setting and parameters based on information in IP protocol headers is disabled when
Cisco TMS redundancy is enabled. For further information on how Cisco TMS communicates with managed
systems, refer to the chapter System management overview in the
Organizations that make significant changes to their network after deploying a redundant Cisco TMS solution
must manually verify that system connectivity between Cisco TMS and managed systems still works after
the network change. An example of a change that would require connectivity verification would be the
introduction of a new proxy between the managed systems and Cisco TMS.
must manually verify that system connectivity between Cisco TMS and managed systems still works after
the network change. An example of a change that would require connectivity verification would be the
introduction of a new proxy between the managed systems and Cisco TMS.
Architectural overview and network diagram
Example configuration
In the example below the following values are used:
Device
IP address
Hostname
F5 BIG-IP Virtual IP Address
10.0.200.40
tms.example.com
tms01
10.0.200.50
tms01.example.com
tms02
10.0.200.60
tms02.example.com
Table 2: VLAN200
Device
IP address
Hostname
Managed systems and users
10.0.100.0/24
Table 3: VLAN100
n
There are two Virtual LANs, VLAN200 and VLAN100.
n
The F5 BIG-IP is configured on VLAN200.
n
The two Cisco TMS servers (tms01 at 10.0.200.50 and tms02 at 10.0.200.60) are configured on VLAN200.
n
All clients (managed systems and users) are configured on VLAN100.
n
All traffic to the virtual IP address of the F5 BIG-IP is forwarded to one of the two Cisco TMS servers.
Cisco TelePresence Management Suite Installation and Upgrade Guide (14.5)
Page 32 of 56
Setting up a redundant deployment
Deploying with a load balancer