Installing CTM R9.2.0.435.4
---------------------------

This readme describes how to download and install CTM R9.2.0.435.4.


Caution: CTM R9.2.0.435.4 is a CTM R9.2 (CTM R9.2.0.363) standard edition patch. 
Do not install CTM R9.2.0.435.4 on systems running CTM R9.2T (CTM R9.2.0.715).


CTM R9.2.0.435.4 provides the following:

- Support for ONS 15454 SONET/SDH NEs version 9.2.0.3.
- Support for ONS 15454 SONET/SDH and ONS 15600 NEs SONET/SDH version 9.2.1.1.
- Support for the AIS/squelch feature on OTU2_XP cards on NEs version 9.2.1.1.
- Support for Java plug-in version 1.6.0_26 or later.
- Support for Apache web server 2.2.19 or later.
- Support for a runtime logging utility for Jacorb.
- Ability to change the number of threads serving a queue dynamically.
- Enhanced SVLAN discovery.


The following caveats are fixed in CTM R9.2.0.435.4:

- CSCtj54321:  The "Migration check failed" error is displayed after the ctms-start command is issued.
- CSCtj86799:  The NE service log contains continuous NCP exceptions.
- CSCtk13453:  ONS 15454 PM data in not displayed when using GateWay/CORBA APIs on some layer rates.
- CSCtk62107:  The CTM server cannot start because the /db05 partition is full.
- CSCtk81770:  CTM does not start because the inode limit has been reached in the /opt directory.
- CSCtl06435:  The network admin user cannot modify or delete OCHNC circuits.
- CSCtl19084:  PM tables are not automatically pruned.
- CSCtl71781:  CTM reports that RAM usage is 95% and generates an alarm.
- CSCtl74392:  A card mode error does not appear when an incorrect configuration on an OTU2_XP card is set.
- CSCtl90870:  The NE service log contains many exceptions.
- CSCtl91087:  The Alarm Browser is empty when "Enable Export of Entire Table" is enabled.
- CSCtl91219:  The getPMdata APIs return no PM data for optical physical layer on OC-192.
- CSCtn03654:  An import of the entire database fails.
- CSCtn08131:  Alarms such as LOS-P remain stuck in CTM after they are cleared in CTC.
- CSCtn26728:  On OTU2_XP cards on multishelf NEs, the Trail Trace Identifier subtab is empty.
- CSCtn31705:  The manage_cdump.sh script generates an output even when no core files exist.
- CSCtn31738:  When filtering CTM tables on MSNE, only shelf 1 results are displayed.
- CSCtn38812:  The getAllVCATSNCs API returns a server error.
- CSCtn39799:  CTM must restrict the number of classes in the InitialPoll module.
- CSCtn70886:  There are NE Service log exceptions on Entity Model for DS cards.
- CSCtn89636:  Support for Java plug-in version 1.6.0_24 or later.
- CSCto42478:  PM data is not displayed for a DS3 card on an ONS 15454 SDH.
- CSCto49685:  JBOSS JMS automatically restarts after CTM is stopped.
- CSCto70795:  On rare occasions, too many initial poll threads can cause LOCs on a GNE/ENE network.
               Note: The CTM R9.2.0.435.4 patch, adds a new check box called "Network Discovery Threads - Use reduced number of threads" in the Control 	
               Panel. Under TAC guidance, check this option to reduce the number of parallel threads used during the network discovery phase. Depending 
               on your network topology, DCN/DCC bandwidth, and GNE-to-ENE ratio, reducing the number of parallel threads will optimize network discovery 
	       performance and prevent timeouts.  Do not use this option unless you are affected by this bug. 
- CSCto71624:  SNMP-based NEs, like the ONS 15216 and ONS 15305, do not receive SNMP traps.
- CSCto71664:  The maximum number of allowed Oracle sessions must be increased on a medium CTM network configuration.
- CSCto77558:  The NE service memory is exhausted due to a memory leak on NE transient events.
- CSCto93667:  The SMR2 Optical Channel tab does not display From and To port information.
- CSCto94039:  You are prompted to save changes in Control Panel even if settings have not changed.
- CSCto96625:  An inappropriate property sheet message is displayed during Control Panel navigation.
- CSCtq38340:  A double deadlock occurs on an NE Service.

CTM R9.2.0.420.6 provides the following:



- Support for ONS 15600 NEs version 9.2.1.
- Support for ONS 15454 SONET/SDH NEs version 8.5 and 9.2.1.
- Y-cable support for the OTU2 card. 



The following caveats are fixed in CTM R9.2.0.420.6:

- CSCtg17028: The CTC-based network service runs out of memory after several days.
- CSCth40538: The Alarm Browser Filter does not work.
- CSCti40572: After an ML card reboot, a CTM node resynchronization occurs.
- CSCti70491: The CAP and BACKPLANE equipment state for the ONS 15600 NEs shows "Not present."
- CSCti80797: The getCTMHistoryPMData API returns a PM data file with no data when layer rate 15 (LR_STS3c_and_AU4_VC4) 
	      or 14 (LR_STS1_and_AU3_High_Order_VC3) are used.
- CSCtj90800: A CTC-based NE never completes discovery.
- CSCtj92364: The Alarm Log displays the following error message: "EID-333: A database timeout occurred."
- CSCtk13119: The Section Trace tab shows no data for the OTU2_XP card.
- CSCtk13137: The OTN Tab shows no data for a OTU2_XP card provisioned on a multishelf NE.
- CSCtk13290: The service status is not automatically updated after activating or deactivating a service from the Control Panel.
- CSCtk13351: Optical patchcords cannot be created if only OTU2_XP cards are provisioned inside the NE.
- CSCtk13431: High CPU usage after bulk circuit creation.
- CSCtk34613: LOS-P alarms are not reported by CTM on a fiber cut on an A/D SMR port.
- CSCtk83953: The client_patch.bat installation script fails with the following message: "Unable to determine CTM client install 
	      location from registry. Please verify your installation and try again."
- CSCtl01777: When the PM data storage status is set to Optimized, Ethernet PM values are not stored in the database.
- CSCtl05918: The Backup Upload feature does not work on CTM R9.2. The list of backup files is not shown.
- CSCtl46593: In the ASAP_4 card NE Explorer > VC tab, when there are multiple circuits created on the same port, CTM shows only one 
	      row with a VC ID of 1. Instead, CTM should show multiple rows, one row for each circuit (with a unique VC ID) on the port.
- CSCtl46849: High-order SDH PM data is not collected for ONS 15600 SDH NEs.
- CSCtl50080: The VC value is incorrect in the VC tab of an ONS 15600 NE STMxx card.
- CSCtl83275: The CTM R9.2 client periodically freezes.
- CSCtn02782: The Line tab does not open on an ONS 15454 SDH NE STMxx card.
- CSCtn05639: Sometimes OTN FEC PM data is not collected on an OTU2_XP card.
- CSCtn39718: Cannot install the client patch if the installation directory name contains a blank space. 

The following caveats are fixed in CTM R9.2.0.400.4:

- CSCsf96351: After the CTM server restarts, SONET NEs do not come up.
- CSCth71367: Navigating within the CTM client is slow, and the client freezes. (Related caveat ID: CSCti30435.)
- CSCti07957: In a dual-server configuration, the following functions stop working a few days after you run the 
	      import_full_db.sh script: PM collection, TCA event reporting, and the ability to disable logins.
- CSCti09988: The CTM GateWay/CORBA CreateTopologicalLink API returns an exception when creating SONET/SDH manual links. 
	      However, the manual link is created successfully.
- CSCti10164: Real-time PM data is not collected on a channel interface of an 80-WXC card installed in a multishelf 
	      environment with the shelf > 1. 
- CSCti16526: TCA_EVENT_TABLE partitions are managed incorrectly. A new partition is created daily at 18:00 a.m. 
	      In the time frame between 00:00 a.m. and 18:00 p.m., PM alerts might not be shown.
- CSCti18733: Manual physical links are not created and do not appear in the Link table or the Network Map.
- CSCti90949: The CTM server restarts intermittently after it receives an overwhelming number of events from network 
	      services. The server eventually crashes because it cannot manage the event load.
- CSCtj01922: There is no CTM database table that reports the status (active or standby) of UPSR spans.
- CSCtj06010: MGX GUI windows do not open because the UNIX permissions on the files in the 
	      /opt/CiscoTransportManagerServer/webServer/cgi-bin directory do not have read and execute permission for all users.
- CSCtj67138: Historical optical PM data is not collected for 80_WXC_C cards on ONS 15454 SDH NEs.
- CSCtj70276: The CTM server loses connectivity with NEs.
- CSCtj72766: CTM must support the latest critical Oracle security patches.
	      Note: You must install the Oracle security patches before installing the latest CTM R9.2 patch. 
	      See "Installing the Oracle Patch Set Update Patches 9352164 and 9952234."
- CSCtj86600: The CIRCUIT_UPSR_BS_TBL database table is missing one of the rows for dual-ring interconnect (DRI) selectors.



Using the CTM Data Migrator Wizard
----------------------------------
 
CTM R9.2.0.x.x patches provide support for the CTM Data Migrator wizard, which allows you to migrate select data from CTM R8.5 or later to CTM R9.2. With the new wizard, 
you can migrate a subset of an existing CTM database to a newly installed CTM R9.2 server.
 
- The CTM Data Migrator wizard reduces the migration time and provides a safer, easier migration. 
 
- The CTM Data Migrator wizard lets you migrate the following data:  
  - CTM core tables and database pruning policy information. 
  - CTM users, including user profile information. 
  - Managed NEs, NE logical grouping information, network partition information, security information to authenticate to nodes, 
    and Domain Explorer and Subnetwork Explorer map coordinates (optional). 
  - Manual links and L1 circuits with user data (optional). 
  - VLAN customer-related information, L2 topologies, and QoS templates (optional). 
 
- The CTM Data Migrator wizard does not migrate alarms and PM data. If you want to migrate the entire database, you must 
  perform a standard upgrade.
 
For installation instructions, see the Cisco Transport Manager Release 9.2 Installation Guide, Chapter 3, "Using the CTM Data Migrator Wizard." The guide is available at 
http://www.cisco.com/en/US/products/sw/opticsw/ps2204/prod_installation_guides_list.html.

For detailed caveat information, see the Release Notes for Cisco Transport Manager R9.2 at
http://cisco.com/en/US/products/sw/opticsw/ps2204/prod_release_notes_list.html.

Alternately, if you have a Cisco.com account and a Cisco service contract, you can use the Bug Toolkit to reference and monitor all 
caveats recorded against this product, including those recorded subsequent to the publication of this document. To access the 
Bug Toolkit, visit http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

CTM R9.2.0.435.4 is intended for customers who are currently using one of the following:

- CTM R9.2.0.420.6
- CTM R9.2.0.400.4
- CTM R9.2.0.363

Note: Install the patch only in a non-high availability setup. If you are using a high availability
setup, contact your Cisco account representative before installing CTM this patch.


Complete the following procedures to upgrade to CTM R9.2.0.435.4.


Determining What CTM Patch Is Currently Installed in the CTM System
-------------------------------------------------------------------

To check your current CTM release and patch level, log into the CTM server as the root user
and enter the following command:

showctm

The first line of the output gives you the release and patch level. Before proceeding, make sure that the 
output results to one of the following:

- Cisco Transport Manager Server Version: 9.2 Build: 420

- Cisco Transport Manager Server Version: 9.2 Build: 400

- Cisco Transport Manager Server Version: 9.2 Build: 363


Backing Up the CTM Database Before Installing CTM R9.2.0.435.4
--------------------------------------------------------------

Before installing CTM R9.2.0.435.4, it is strongly recommended that you back up the existing database.
To back up the CTM database, refer to the following sections in Chapter 4 of the Cisco Transport Manager
Release 9.2 User Guide:

- Backing Up the CTM Database from the CTM GUI
- Backing Up the CTM Database from the CLI


Downloading CTM R9.2.0.435.4
----------------------------

Step 1: Go to http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875317.

Step 2: At the Select a Product screen, expand Cisco Transport Manager.

Step 3: Click Cisco Transport Manager 9.2.

Step 4: At the Select a Release screen, click Expand all and click 9.2.0.435.4.

Step 5: In the right pane, click Download Now.

Step 6: At the Log In screen, enter your registered Cisco.com username and password; then, click Log In.

Note: If you do not have a Cisco.com username and password, you can register for them at 
http://tools.cisco.com/RPF/register/register.do.

Step 7: At the Download Software screen, click Proceed With Download.

Step 8: At the License Agreement screen, read the terms of the license agreement and click Agree.

Step 9: At the Select a download option screen, select one of the following options:

- Download Manager Option: If you have Java version 1.4.2.xx installed on your computer.
- Non Java Download Option: If you do not have Java installed on your computer.

Step 10: Download the CTM9.2.0.435.4.patch.zip file to a temporary directory (such as /temp) on the CTM server.

Step 11: In Solaris, enter the following commands to extract the file to the temporary directory:

cd /<directory-name>
unzip CTM9.2.0.435.4.patch.zip

For example, to extract the file to the /temp directory, enter:

cd /temp
unzip CTM9.2.0.435.4.patch.zip

This creates a directory called 435, which contains all patch-related files.

Step 12: Enter the following command to enter the directory:

cd 435

Step 13: In Windows, download the file to the client workstation. Extract the file using a tool such as WinZip, as follows:

a. Open the CTM9.2.0.435.4.patch.zip file in WinZip.

b. Click the Extract button.

c. Verify that the Use folder names check box is checked.

d. In the Extract to drop-down list, select the location where you want to extract the files.

e. Click Extract.


Installing CTM R9.2.0.435.4 on the Server
-----------------------------------------

To apply CTM R9.2.0.435.4 to the server, complete the following steps:

Step 1: Notify all CTM users before shutting down the CTM server:

a. In the Domain Explorer window, choose File > Notify Users. The Notify Users dialog box opens.

b. In the Message Targets area, click the All CTM Users radio button.

c. Type the message in the Message area. Customize the message as appropriate for your organization. A sample
message might read:

The CTM server will be shut down in 5 minutes. Please log out of the CTM client before then.

d. Click Send.

e. Wait an appropriate amount of time for the CTM users to log out.

Step 2: At the end of the grace period, log out all of the CTM clients:

a. Log into the CTM server using an account with SuperUser privileges.

b. In the Domain Explorer window, choose Administration > CTM Users.

c. In the CTM Users table, choose Administration > Logged In CTM Users.

d. In the Logged In CTM Users table, select a user and choose Administration > Log Out User (or click the
Log Out User tool).

Note: This menu option is disabled if you selected your own session.

e. Click Yes at the following prompt:

This operation will log out the selected CTM user. The process will take approximately 1 minute and this
CTM client will be unusable until then. Do you wish to continue?

Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the
request is complete. Log out all of the users listed in the Logged In CTM Users table to make sure that all user
sessions are terminated.

Step 3: As the root user, enter the following command at the UNIX prompt to stop the CTM server:

ctms-stop

Step 4: To patch the server, enter the following command in the 435 directory where the patch was extracted:

./server_patch.sh

Note: Depending on the size of the database, the script might take a while to complete. Do not interrupt 
the script before it finishes.

Step 5: As the root user, enter the following command at the UNIX prompt on the CTM server workstation to start
the CTM server:

ctms-start

Step 6: As the root user, enter the following command at the UNIX prompt on the CTM server workstation to verify
the patch installation:

showctm

You should see the following version string in the first line of output for the preceding command:

Cisco Transport Manager Server Version: 9.2 Build: 435 Patches: 4


Installing the CTM R9.2.0.435.4 Client on Windows
-------------------------------------------------

The following steps describe how to patch a CTM client installation in Windows. Before proceeding,
make sure that there are no instances of the client running in the system. To shut down a running client,
choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.

Step 1: Locate the 435 directory that was extracted with the WinZip utility.

Step 2: Using the command prompt, go to the directory where the patch files were extracted,
locate the client_patch.bat file, and enter the following command:

client_patch

You can also use the Windows Explorer folder view to access the directory where the patch files were extracted
and double-click the client_patch.bat file.

Step 3: Double-click the CTM 9.2 desktop icon or choose the CTM 9.2 Start menu shortcut to start the client.

Step 4: To verify the patch installation on the CTM client, do one of the following:

- Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version
string in the About Cisco Transport Manager dialog box; then, click OK:

Client: 9.2 Build: 435 (client configuration size)

- (Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer.
In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab.
The Version field indicates the CTM client version number, which should read:

9.2 [9.2.0.435]


Installing the CTM R9.2.0.435.4 Client on Solaris
-------------------------------------------------

The following steps describe how to patch a CTM client installation in Solaris. Before proceeding,
make sure that there are no instances of the client running in the system. To shut down a running client,
choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.

Step 1: Go to the 435 directory where the patch files were extracted with the unzip command.

Step 2: Enter the following command:

./client_patch.sh

Step 3: Enter the following command to start the CTM client:

ctmc-start

Step 4: To verify the patch installation on the CTM client, do one of the following:

- Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version
string in the About Cisco Transport Manager dialog box; then, click OK:

Client: 9.2 Build: 435 (client configuration size)

- (Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer.
In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab.
The Version field indicates the CTM client version number, which should read:

9.2 [9.2.0.435]