Table of Contents
Advertisement
Create a machinekey element using Microsoft's supplied methods or from the sample websites listed
above. Open the web.config file under the wwwCisco TMS directory and insert the new machinekey
element text under the existing <system.web> element in the document. You must update the
web.config file on each of the Cisco TMS servers. Be sure to use the same machinekey string on all
servers.
Setup Network Load Balancer.
Next, the Network Load Balancer should be installed and configured. Specific instructions will vary
based on the NLB type used, but the following requirements must be met for use with Cisco TMS.
Devices must be able to access a specific IP Address and DNS hostname that will be forwarded
by the NLB
The NLB must only forward a connection to a single server, not multiples
The NLB must be able forward HTTP and SNMP Trap traffic
The NLB should use sticky connections for web sessions for the best results
The NLB must maintain its own rules for determining which servers are available and which
to forward to:
The IP address and DNS hostname being forwarded by the NLB must be configured in Cisco
TMS as the as the Cisco TMS Server Addresses because Cisco TMS must know which
address to provide managed devices to reach Cisco TMS. . The appropriate address (local or
public) should be the entered in all managed devices and external integrations as the
management address or address to reach Cisco TMS. Please reference the Cisco TMS
Device Support Document available on the Cisco TMS installation media for configuration
details for each managed device type. Once the NLB is configured and operational, you may
continue to configure Cisco TMS as normal through its web interface and add devices and
other external integrations.
Maintenance
Users should regularly backup the SQL database. The interval between backups defines the
maximum time window over which data would be lost. Typical installations would perform full nightly
backups of the database. Please see the Section
document detailing backup and restore procedures for SQL server.
As multiple Cisco TMS servers are being used, administrators should periodically check that their file
synchronization process is still functioning to ensure seamless use of any Cisco TMS server.
Upgrading TMS
All Cisco TMS servers accessing the same database must be running the same Cisco TMS version.
When upgrading between Cisco TMS versions, there will be inconsistencies between different servers
as each is upgraded so extra steps are required when performing Cisco TMS upgrades or patches.
When performing a Cisco TMS upgrade, the following steps must be followed
Plan an upgrade during a time window when Cisco TMS can be made unavailable to users as
Cisco TMS will be unavailable during the duration of your upgrade
Log into the Windows console of each Cisco TMS server, and from the Services component of
Computer Management, manually stop all services whose name starts Cisco TMS and the
WWWPublishingSevice service. Repeat this step on all Cisco TMS servers that are part of the
pool. All Cisco TMS services and websites should be stopped on all servers before proceeding.
Start on a single Cisco TMS server. Start the installer for the Cisco TMS upgrade as normal.
During this process, any updates to the SQL database will be performed.
The installer will likely restart the Cisco TMS services and WWWPublishingService and may
require a reboot of the server. After the reboot, go into Services component of Computer
Management, manually stop all services whose name starts with Cisco TMS and the
WWWPublishingSevice
Proceed to the next server, and start the upgrade or patch installer the same as you did on the
first Cisco TMS server. Make sure to manually stop the Cisco TMS services and website after the
Cisco TMS redundancy configuration and overview
Cisco Redundancy Models for Cisco TMS
0 Backup and Recovery of the TMS database
of this
Page 22 of 32
Advertisement
Table of Contents
