Cisco Telepresence Management Suite Clustering With F5 BIG-IP Part 2


Access the tms1.collab.com 10.1.6.25 server Extract the Cisco TMS.zip archive to a folder ans run the Cisco TMS executable as administrator.

Click Yes to accept the license agreement. The installer now searches for an existing SQL Server and Cisco TMS database.

Connect the TMS1.collab.com server to the external SQL database.

Enter the IP address of the external SQL database 10.1.6.27 and the username SA and password. Click Next.

If you receive the following message “Could not connect to SQL Server: Provider cannot be found. It may not be properly installed. For more information, refer to Cisco TMS Installation guide”.

You need to install the SQL Native client before installing the TMS installation.

On the External SQL server 10.1.6.27, launch the SQL Configuration Manager, under SQL Server Network Configuration, click on Protocols for SQLEXPRESS, double click TCP/IP, click IP Address tab, scroll down to IPAII and set TCP/IP to 1433.  

Return to tms1.collab.com 10.1.6.25 and click Next, now the previous error disappears.

A new release key is required if performing a new installation. If no release key is selected, an evaluation version of Cisco TMS will be installed. Click Next. The Network Settings is displayed.

Configure network settings with IP address 10.1.6.25 to allow tms1.collab.com server to start connectivity with a basic network configuration.

Zones area are a concept used by Cisco TMS to route phone numbers and aliases when scheduling calls and using phone books.

Specify the Cisco TMS installation path, then click Next.

Click Generate to create a new key to encrypt system username and password in the Cisco TMS database, then click Next. Make a not of the encryption key, it will be used when installing tms2 later.

The Start Copying Files will be displayed. Verify all the settings in the displayed summary, then click Next to start the installation. Once finished, click Finish.

Once the Application is installed, you are asked to select a certificate, click Import, select the TMS’s certificate in .pfx format, the Common Name is tms.collab.com. At the end, click Finish.

Access the tms2.collab.com 10.1.6.26 server Extract the Cisco TMS.zip archive to a folder ans run the Cisco TMS executable as administrator. Repeat the same steps for tms2.collab.com.

Enter the encryption key generated during the installation on tms1.

Use the same certificate used on tms1 when enabling HTTPS.

If you forgot the Encryption Key of tms1, you can retrieve it from TMS Tools on tms1.collab.com.

Access tms1.collab.com using the url https://10.1.6.25/tms.

Navigate to Administrative Tools > General Settings > Enable TMS Redundancy and select Yes and click Save.

Testing manual failover

Navigate to Administrative tools  > TMS Server Maintenance > TMS Redundancy.

Notice the tms1 is the active node and tms2 is the passive node.

Access tms2.collab.com using the url https://10.1.6.26/tms. You should get an error telling that Cisco TMS is unavailable.

In TMS Redundancy click Force Manual Failover.

Refresh the tms1 web page.

You should get the ‘Cisco TMS is unavailable’ error.

Access tms2.collab.com using the url https://10.1.6.26/tms. Since tms2 is the active node, you can access the GUI.

Navigate to Administrative tools > TMS Server Maintenance >TMS Redundancy. You should see that the tms2 is now the active node while tms1 is the passive node.

Categories: Collaboration

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: