CTC Unable to Launch

Introduction

This document describes the steps to troubleshoot in order to resolve Cisco Transport Controller (CTC) launch related problems. CTC is an important part of Cisco Optical Transport Platforms and used for operation, administration and maintenance purposes. This document only addresses Windows related problems.

CTC software resides on the controller of Optical Networking Services (ONS) nodes. In order to obtain to a node on CTC, the IP address of the node has to be reachable from the user's machine and the IP address needs to be launched from an Internet browser.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Basic knowledge of Cisco Transport Controller and its use
• The IP address of the node on the user's machine
• Basic knowledge of the Microsoft Windows operating system

Components Used

The information in this document is based on the Cisco Transport Controller which is used for ONS series node management.

The steps to troubleshoot are only for users having problems with the launch of CTC from a Windows machine.

Related Products

This document can also be used with these hardware and software versions:

• Software version release 9.0 and above
• Hardware versions ONS 15454 M12, M6, M2 and ONS 15600

Troubleshoot CTC Launch Issues

When unable to launch CTC, troubleshoot with these methods.

Method 1: Delete the CTC Cache from the Machine

First, it is necessary to always delete the cache file from your PC.

In Windows-7 navigate to:

C:\Users\test\AppData\Roaming

In this example, "test" is the current user. For your PC, select the current user.
Open the folder named "Cisco" which contains a folder named "CTC", which must be deleted.

Within C:drive-users-username, delete all ctc.log file and ctc.ini files.

In Windows-XP navigate to:

C:\Documents and Settings\admin\Application Data\Cisco\CTC

Delete the CTC folder. Where admin = current user, select your username.

Method 2: Modify Internet Explorer Settings

1. In Internet Explorer 7, disable the Protected Mode for a zone:
   • Choose Tools > Internet Options.
   • Click the Security tab.
   • Select the appropriate zone and then uncheck the Enable Protected Mode check box.

   The Protected Mode status ("Protected Mode: On" or "Protected Mode: Off") is visible in the lower right corner of the IE status bar.

2. Set the security zone level to Medium.

Method 3: Modify Windows TCP Features and Disable Automatic TCP Tuning

1. In order to use this method, open a command prompt and enter this command:

   netsh interface tcp set global autotuninglevel=disabled

   Output of the command should be OK. This represents the successful execution of the command. If that does not produce an OK result, then run the command prompt as Administrator.
2. In order to run the command prompt as administrator navigate to All Programs > Accessories > Command Prompt, and right-click Run as Administrator.

   Receive Window Auto-Tuning feature for HTTP traffic on Windows Vista-based computers

3. Windows has the ability to automatically overwrite the above user settings, so you might also want to enforce them with this step:

   netsh int tcp set heuristics disabled

   Use the same method to disable autotuning:

   Hotfix improves TCP window scaling in Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

Method 4: Check Java Version Compatibility

Check for Java Version compatibility. Java version 6 with update 37 works for all CTC versions.

Download Java here.

Method 5: Install the CTC cache

The CTC cache can be useful and usually resolves most of the CTC launch related issues. Download the appropriate cache version (which depends on your node version). Install the cache on your machine and use this cache to launch CTC.

Download CTC cache here.

In addition, the cache can be downloaded from the node with the use of this link, where node-name is the IP address of the node.

http://node-name/fs/StartCTC.exe

Note: CTC cache 9.604 and 9.80 does not support software release version 9.40 and earlier. The Cisco Bug ID is CSCui16205 .