Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Deploying with a load balancer
Configuring two Cisco TMS servers (also referred to as "nodes" in this context) with a network load balancer
(NLB) provides a truly redundant Cisco TMS setup with fully automatic fail-over.
(NLB) provides a truly redundant Cisco TMS setup with fully automatic fail-over.
Requests from the systems managed by Cisco TMS pass transparently through the NLB so that the traffic
appears to come directly from the managed systems. (See
appears to come directly from the managed systems. (See
Recommended hardware
We recommend using the Cisco ACE 4710 Application Control Engine Appliance. The ACE is the only load
balancer that has been tested and verified to work with Cisco TMS.
balancer that has been tested and verified to work with Cisco TMS.
Fully documenting how to set up and manage an ACE appliance is outside the scope of this document, but a
sample Cisco TMS-compatible ACE configuration has been included in
sample Cisco TMS-compatible ACE configuration has been included in
for your reference.
documentation for further
information.)
Active directory and user authentication requirements
n
Both Cisco TMS servers must be members of the same Windows domain.
n
All Cisco TMS users must be imported from and authenticated using Active Directory.
n
Using local user accounts is not supported for this redundancy model.
Communication with managed systems
When deploying two Cisco TMS servers behind a load balancer such as the Cisco ACE 4710 Application
Control Engine Appliance, one virtual IP address must be assigned to the NLB and one IP address assigned
to each of the two Cisco TMS servers.
Control Engine Appliance, one virtual IP address must be assigned to the NLB and one IP address assigned
to each of the two Cisco TMS servers.
A DNS entry must be created pointing to the NLB's virtual IP address.
The NLB's hostname and IP address(es) must be entered in the fields on the
Network Settings
page in
.
for instructions on implementing this configuration.
Once the IP addresses and hostname values in
Network Settings
have been changed, the Database
Scanner service enforces the 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.
directing traffic to the NLB, which forwards the requests to the Cisco TMS servers.
All communication between Cisco TMS and the managed systems will now go through the NLB. This is
accomplished by keeping the Cisco TMS servers and the managed systems on different VLANs while the
servers use the NLB as their default gateway.
accomplished by keeping the Cisco TMS servers and the managed systems on different VLANs while the
servers use the NLB as their default gateway.
Cisco TMS's logic for determining whether a system is Reachable on LAN, Reachable on Public Internet or
Behind Firewall dictates how you set up the load balancer. As it is limiting to have systems in a Behind
Behind Firewall dictates how you set up the load balancer. As it is limiting to have systems in a Behind
Cisco TMS Administrator Guide (14.2)
Page 295 of 332
Redundant deployments
Deploying with a load balancer