Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Recovery in Case of a Failing Node
No immediate action is required in the event of a server failure. If the passive node goes down, the active node con
tinues its operations as normal. If the active node goes down, the passive node will become active automatically, and
the NLB will detect the failure and direct all traffic to the new active node.
tinues its operations as normal. If the active node goes down, the passive node will become active automatically, and
the NLB will detect the failure and direct all traffic to the new active node.
Expect a delay of approximately one minute while the failover takes place. During this time the 'Unable to connect to
Cisco TMS' error will be shown on the web page.
Cisco TMS' error will be shown on the web page.
Troubleshoot the failing node’s software and hardware as you normally would, and bring it back online once it is oper
ational.
ational.
Troubleshooting with Managed Systems in a Redundant Deployment
Capturing a Wireshark trace on the active Cisco TMS server will show all incoming traffic as coming from the NLB.
You will therefore be unable to easily identify the communication between Cisco TMS and the managed systems you
are interested in.
You will therefore be unable to easily identify the communication between Cisco TMS and the managed systems you
are interested in.
Before you begin troubleshooting, do the following:
1.
For all the systems you are investigating, temporarily set the management address to the address of the active
Cisco TMS server.
Cisco TMS server.
2.
Take the Wireshark capture.
3.
Once you have finished taking the trace, set the management address of all the systems back to the address of
the NLB.
the NLB.
Logs
■
Log files must be gathered from both Cisco TMS servers.
■
If changing the log levels, ensure that this is done on both servers. The exception to this is if you are changing
the log level for a very short time, for example if you increase the log level, reproduce the problem and then
immediately decrease the log level again.
the log level for a very short time, for example if you increase the log level, reproduce the problem and then
immediately decrease the log level again.
Deploying a Hot Standby
Keeping an additional Cisco TMS server as a warm spare in case of failure is known as the "Hot Standby" redund
ancy model.This requires manual intervention if there is a failure on the primary Cisco TMS server, and is therefore a
switchover solution rather than a failover solution.
ancy model.This requires manual intervention if there is a failure on the primary Cisco TMS server, and is therefore a
switchover solution rather than a failover solution.
One Cisco TMS server is active at any given time with this redundancy model. The hot standby server must be kept up
to date with security patches and other upgrades so that it is ready for activation within a few minutes if the primary
server fails.
to date with security patches and other upgrades so that it is ready for activation within a few minutes if the primary
server fails.
Note that the hot standby redundancy model requires the tmsng database to be located on an external SQL server,
and that the two Cisco TMS servers must be in the same Windows domain.
and that the two Cisco TMS servers must be in the same Windows domain.
In this deployment, do not enable redundancy using
General Settings >
Enable TMS Redundancy.
In the instructions below the following examples are used:
Server
DNS Name
IP Address
Primary Cisco TMS Server (tms01)
tms01.example.com
10.0.0.10
Secondary Cisco TMS Server (tms02)
tms02.example.com
10.0.0.11
The examples assume that you use IPv4. If you also use IPv6, change the IPv6 addresses accordingly.
37
Cisco TelePresence Management Suite Installation and Upgrade Guide
Setting up a Redundant Deployment