Installing CTM R9.2.0.400.4
---------------------------

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

Note: Caveats are categorized as a server fix (S), client fix (C), or both (CS).

The following caveats are fixed in CTM R9.2.0.400.4:

CSCsf96351 (S): After the CTM server restarts, SONET NEs do not come up.
CSCth71367 (S): Navigating within the CTM client is slow, and the client freezes. (Related caveat ID: CSCti30435.)
CSCti07957 (S): 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 (S): The CTM GateWay/CORBA CreateTopologicalLink API returns an exception when creating SONET/SDH manual links. 
		However, the manual link is created successfully.
CSCti10164 (S): 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 (S): 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 (S): Manual physical links are not created and do not appear in the Link table or the Network Map.
CSCti90949 (S): 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 (S): There is no CTM database table that reports the status (active or standby) of UPSR spans.
CSCtj06010 (S): 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 (S): Historical optical PM data is not collected for 80_WXC_C cards on ONS 15454 SDH NEs.
CSCtj70276 (S): The CTM server loses connectivity with NEs.
CSCtj72766 (S): 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 (S): The CIRCUIT_UPSR_BS_TBL database table is missing one of the rows for dual-ring interconnect (DRI) selectors.

CTM R9.2.0.400.4 also adds support for the CTM Data Migrator wizard, which allows you to 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.

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.400.4 is intended for customers who are currently using CTM R9.2.0.363.

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

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


Installing the Oracle Patch Set Update Patches 9352164 and 9952234
------------------------------------------------------------------

Oracle released the Patch Set Update (PSU) patches 9352164 and 9952234. For security reasons, CTM must support these Oracle patches.
Complete the following steps before installing the CTM R9.2.0.400.4 patch:

Step 1: Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink username and password.

Step 2: Select Patch from the menu and search for and download patches 9352164 and 9952234.

Step 3: Extract the README.html file from the Oracle PSU patch .zip file. As you read the README.html file, note that the 
CTM database has the following setup:

- Oracle environment: Non-RAC.
- Data Guard Physical Standby database: Not implemented.
- Job Scheduling system: Used.
- ASM instance: Not implemented.
- Initial setup: Oracle 10.2.0.4.2; CTM R9.2.0.363 installed on the CTM server.

Step 4: Refer to the README.html file as you complete the following substeps:

a. Uninstall the PSU patch 10.2.0.4.2. (See the "Patch Deinstallation" paragraph in the README.html file. 
The PSU patch number is 8833280.)

b. Install the PSU patch 10.2.0.4.4. (See the "Patch Installation Instructions" paragraph in the README.html 
file. The PSU patch number is 9352164.) 

c. As the root user, enter the following command:

sh psu_root.sh

Note: If ORACLE_HOME is not set, the psu_root.sh script fails. By default, the $ORACLE_HOME directory is /oracle/product/10.2.0.

d. Check for any one-off patch conflicts with the PSU patch 10.2.0.4.6. (See the "One-Off Patch Conflict Detection and 
Resolution" paragraph in the README.html file.)

e. Install the PSU patch 10.2.0.4.6. (See the "Patch Installation Instructions" paragraph in the README.html 
file. The PSU patch number is 9952234.)

f. Enter the following command to load the modified SQL files into the database. (See the "Loading Modified SQL 
Files into the Database" paragraph in the README.html file.) 

catbundle.sql psu apply

g. Enter the following commands to recompile views in the database. (See the "Recompiling Views in the 
Database Instructions" paragraph in the README.html file.)

recompile_precheck_jan2008cpu.sql
view_recompile_jan2008cpu.sql
utlrp.sql

h. Enter the following command to clean up the .patch_storage area:

$ORACLE_HOME/OPatch/opatch util cleanup


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 the following:

- Cisco Transport Manager Server Version: 9.2 Build: 363


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

Before installing CTM R9.2.0.400.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.400.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.400.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.400.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.400.4.patch.zip

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

cd /temp
unzip CTM9.2.0.400.4.patch.zip

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

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

cd 400

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.400.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.400.4 on the Server
-----------------------------------------

To apply CTM R9.2.0.400.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 400 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: 400 Patches: 4


Installing the CTM R9.2.0.400.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 400 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: 400 (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.400]


Installing the CTM R9.2.0.400.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 400 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: 400 (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.400]