This document addresses common problems that you encounter when you try to:
Establish link level connectivity from a PC that is directly attached to the active TCC.
Establish IP connectivity from a PC that is directly attached to the active TCC.
Install and configure the JavaTM software on the PC.
Use the TCC to download and launch the CTC software.
Note: This document is not an installation guide. For detailed installation and setup information, refer to the Using the Cisco Transport Controller chapter of the Cisco ONS 15454 user documentation. Use this document in conjunction with the user documentation as a troubleshooting and reference guide, or as a standalone troubleshooting guide.
There are no specific requirements for this document.
The information in this document is based on the Cisco ONS 15454.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to the Cisco Technical Tips Conventions for more information on document conventions.
This section explains how you can resolve the common connectivity problems in each scenario listed in the Introduction section.
For the initial setup of the Cisco ONS 15454, connect a straight-through RJ-45 Ethernet cable from the RJ-45 port of the network interface card (NIC) in the PC to the RJ-45 port on the TCC in the ONS 15454. Most 15454s have an active and a standby TCC. With software versions 2.0 and later, you can connect the cable to either the active or standby TCC.
Note: Slot 7 and slot 11 are reserved for the active and standby TCCs. These two slots are hubbed together with the backplane LAN, and the speed is fixed at 10 MB, half-duplex.
Note: The RJ-45 port on the TCC has no LED to indicate link level connectivity. You need to use the LEDs on the NIC in the PC to verify the link level connectivity for the Ethernet connection. When you successfully establish link level connectivity to the TCC, the red LED lights up. When traffic begins to pass, the green LED flashes.Figure 2 – LEDs on the NIC
The ONS 15454 is shipped with a default node name of TCCP. By default, all ONS 15454s are assigned a class C IP address of 18.104.22.168. For successful connection, you must configure the PC with a unique IP address within the class C subnet 192.1.0.x. You must also use a default gateway that points to the class C IP address 22.214.171.124 (or the existing IP address of the 15454 to which you want to directly connect).
Note: Shelves that are already in use most likely have an IP address that is different from the default IP address. Look directly at the shelf to find this address on the shelf LCD display. If your LCD display is defective, obtain the IP address from your network administrator. Configure a unique IP address on your PC. Ensure that the IP address is in the same IP class as the shelf IP address and network mask. The shelf IP is the same as your gateway IP address.
Open the TCP/IP Properties dialog box of the operating system on your PC. Change the last three digits of the IP address of the PC to a unique value between 1 and 254 (see Figure 3). Ensure that you exclude the default IP address of the 15454 (126.96.36.199).
Although the IP addresses of the PC and the ONS 15454 need to be unique, you must ensure that they are within the same class C subnet with the first three digits of 192.1.0.x. Ensure that the default gateway on the PC points to the default IP address on the ONS 15454. Figure 3 is an example of TCP properties in a Windows environment:Figure 3 – Microsoft TCP Properties
Ensure that you have IP connectivity from a DOS prompt. For this, you can use the ping command to send ICMP echo requests to the ONS 15454 default IP address, 188.8.131.52. A simple ping command, in which you specify the destination IP address is usually sufficient.
In the example shown in Figure 4, note that the -n operand specifies that you must send two ICMP echo requests. The -l operand specifies a packet size of 1500 bytes.
In this example, both echo requests are successful, and indicate IP connectivity to the Ethernet address 184.108.40.206 assigned to the Ethernet interface of the TCC.Figure 4 – Use the ping Command
If the ping command is unsuccessful, the ICMP echo requests time out, and indicate that the destination host is unreachable. The example in Figure 5 depicts the results of a ping command that failed.Figure 5 – When the ping Command Fails
Here, the PC is connected directly to the TCC, and there are only a few reasons for the ping to fail. Consider some of these suggestions to correct the problem:
Check whether the IP addresses are duplicates. The IP address 220.127.116.11 is not like a telephone number that matches at both ends. Instead, the IP address of the TCC and that of the PC must be unique and different.
Check whether the two IP addresses are in different subnets. The IP addresses of the TCC and PC must both be within the 192.1.0.x subnet. Otherwise, ping fails.
Check whether you use dual NICs or an enabled NIC and dial-up adapter at the same time, because this can cause problems like multiple IP addresses, which in turn can cause the ping to fail.
Before you download and launch the CTC software for the ONS 15454, you need to install and configure the JRE files or the JAR file.
Note: You need to download either the JRE files or the JAR file, and not both.
You can install the JRE files from the ONS 15454 software CD. You can also download the JRE files directly from the JavaTM web site. Complete these steps:
Insert the ONS 15454 software CD into the PC, and double-click the jre-1_2_2_005-win.exe file (see Figure 6).
Then, follow the on-screen instructions to complete the installation.
If you do not have the CD, you can download the JRE software from the Java TM web site.Figure 6 – Run the JRE Executable File
Next, you must install the Java policy file. Double-click the JavaPolicyInstall.exe file (see Figure 7).Figure 7 – Install the Java Policy File
The JavaPolicyInstall.exe file adds several lines of code to the bottom of the java.policy file. See Figure 8 for the specific lines of code.Figure 8 – Lines of Code in the java.policy File
You can use FTP to download the JAR file to your PC.
Open a DOS window.
Use the DOS command line to go to the directory on your PC where you want the JAR file to reside.
Use the ping command to ensure that the PC is directly connected to the Ethernet management interface on the TCC.
Type ftp ip address , and press Enter.
When you are prompted for a user name and password, press Enter twice to bypass these requests.
At the ftp:> prompt, type bin, and press Enter.
Type get CMS.JAR, and press Enter.
The JAR file is transferred to your hard drive, and a completion message is displayed.
At the next ftp:> prompt, type quit, and press Enter.
After you download the file, go to the directory where you saved the CMS.JAR file. Type java -jar CMS.JAR ip address to manually launch the CTC application.
java -jar CMS.JAR 18.104.22.168
After you install and configure the JRE software, you can download and launch the Cisco Transport Controller application. Complete these steps:
In the Address bar of the browser window, type the IP address of the Ethernet interface of the TCC (see Figure 9).
Press Enter to connect to the TCC.Figure 9 – Connect to the Ethernet Port on the TCC
Note: The "Applet cerent.launcher.CmsLauncherApplet notinited" error message indicates problems with the JRE software (see the bottom of the screen in Figure 9). See the Common Problems When You Install and Configure the JRE Software section for more information.
If the CTC application is successfully downloaded, the CTC login screen is displayed (see Figure 10). You are now ready to log in and use the CTC application.Figure 10 – The CTC Login Window
The "Applet cerent.launcher.CmsLauncherApplet notinited" error message indicates a problem with either the installation or configuration of the JRE software.
Complete these steps to troubleshoot this issue:
Select Start > Programs > Java Plug-in Control Panel.
The Java Plug-in Properties window displays (see Figure 11).
In the Basic tab, ensure that Enable Java Plug-in and Cache JARs in memory are checked.Figure 11 – The Java Plug-in Properties Dialog Box
Click the Advanced tab.
If the Path option is set to Use Java Plug-in Default, change it to point to the location where you have saved the JRE file, as shown here:Figure 12 – Type the Correct Path to the JRE File
Ensure that your browser is not configured to use a proxy server to access the Internet.
Complete these steps if you use Netscape:
Select Edit > Preferences > Advanced > Proxies.
Ensure that the Proxies configuration is set to Direct connection to the Internet.
Select Tools > Internet Options > Advanced > HTTP 1.1 Settings.
Ensure that the Use HTTP 1.1 through proxy connections check box is NOT checked.
Complete these steps if you use Internet Explorer:
Remove and reinstall the JRE software. Complete these steps:
Remove and reinstall the CTC software.
Note: The location of the program files differs across platforms and operating systems. Therefore, use the Search function on your computer to find all files that match CMS*.jar (see Figure 14). Manually delete each file that you find. The next time the PC connects to the TCC, a new CMS file is downloaded from the TCC.Figure 14 – Delete All CMS*.jar Files Manually
Instead of a web browser, use the DOS command line to launch the CTC application manually (see Figure 15). You need to specify the correct file path and the IP address of the Ethernet interface on the TCC.Figure 15 – Launch CTC Manually from the DOS Command Line
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.