Installing the CTM R8.5.0.381.3 Patch
-------------------------------------

Note: The CTM R8.5.0.381.3 patch inherits all bug fixes and obsoletes all earlier CTM R8.5 patches.

This readme describes how to download and install the CTM R8.5.0.381.3 patch, which fixes the following caveats:

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

CSCse91332 (S): CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.
CSCsj01676 (S): The Maximum Login Attempts alarm for an unknown user is not cleared if you set the Max Retries field 
	        in the Control Panel to one.
CSCsj19520 (S): The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service or CTM server is restarted.
CSCsk44773 (S): Due to security issues, CTM must support Apache web server version 2.0.61.
CSCsk84707 (S): CTM PM pruning fails due to a buffer overflow error.
CSCsl09775 (S): NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the 
	        /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
CSCsl20872 (CS): Creating an L1 circuit fails and the following message appears: 
	        "EID-932: Failed to route the circuit. Details: client timeout reached."
CSCsl26108 (S): CTM does not perform quickly when connecting, discovering, and resynchronizing CTC-based devices such as 
	        the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
CSCsl28305 (S): Unable to determine the status of the database when the migration or export operation fails.
CSCsl31836 (C): In the CTM Login dialog box, the text area with the legal disclaimer displays only 69 characters for each 
	        row; it should display 80 characters.
CSCsl37264 (C): The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
CSCsl43107 (C): A background Java/Javaw process is opened and does not close when you close the CTM client. Every time the 
	        CTM client is opened, a new Java process is created. Therefore, if the CTM client is opened several times, 
	        several dangling Java processes are created.
CSCsl48499 (C): The backup files are not listed in the Backup File dialog box after choosing Administration > Memory Backup 
	        Upload in the Domain Explorer.
CSCsl95721 (S): The Circuit table does now show port names for circuits on MRC-12 cards (on ONS 15454 R6.0.1 NEs) or 
	        MRC-4 cards (on ONS 15454 R8.0 NEs). The Circuit table shows incorrect port names for circuits on DS3 cards 
	        (on ONS 15454 R6.0.1 NEs).
CSCsm17261 (S): When a node is marked as Out of Service and then In Service, the alarm ID and time stamp are assigned new 
	        values in the Alarm Browser. The alarm notes are also missing.
CSCsm21463 (S): The Circuit table does not display the port name for E1-42 cards for source and destination NEs. 
	        Also, the Circuit table does not display the port name for STM-1 cards for destination NEs.
CSCsm37071 (S): IMR is an OpenFusion service that is required for the correct behavior of the CTM server. In certain 
	        environments, IMR shuts down unexpectedly, causing the SM service and any connected services to shut down 
	        and restart.
CSCsm41384 (S): The /tmp directory on the application server for log4j contains error messages and cleared CTM alarms that 
                are unacknowledged. log4j is the library that manages log messages in the database and in the log files.
CSCsm84722 (S): Patches cannot be installed in dual-server setup.
CSCsm85018 (S): There are compatibility issues between CTM R8.5 and the CTM GateWay/CORBA R8.0 client after changing the 
	        CTM R8.5 notifications.idl file located in the /opt/CiscoTransportManager/idl directory.
CSCsm99421 (S): CTP values of alarms are printed when you run the getAllActiveAlarms API. But for certain alarms where 
	    the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.
CSCso00123 (S): The CTM client cannot connect to the CTM server. The following error message appears: "EID-382: The CTM server 
                is initializing. Please try again after some time."
CSCso00769 (S): Unable to delete or modify drops or VLANs that are associated with custom QoS profiles.
CSCso01840 (CS): It takes a long time to discover NEs after the NE service restarts.
CSCso01900 (S): The CTC-based NE service takes a long time to reconnect and discover NEs.
CSCso01942 (CS): CTM takes a long time to discover a large network of GNEs and ENEs.
CSCso35202 (S): The Oracle shutdown script does not work while the server workstation is shutting down. 
CSCso44701 (S): CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job Monitor table displays the 
	        following message:
	        (Too many open files)
	        (No such file or directory)
CSCso51993 (S): Manual links do not work correctly. In the Link table, circuits related to a specific link are 
	        not shown, and manual links are shown as not being used for routing.
CSCso62224 (S): Upgrading the CTM server workstation from CTM R8.0 to R8.5 or from CTM R8.5 to R9.0 fails on a dual-server setup.
CSCso76700 (S): The CTM GateWay/CORBA NBI creates additional proxy consumers if you do not stop CTM GateWay/CORBA 
	        before executing the ctms-stop or ctms-start commands.
CSCsq11152 (CS): Due to security issues, CTM must support a new JRE version.
CSCsq24237 (S): CTM retrieves old and new alarms that are identical when a node is marked as Out of Service and then 
	        In Service. The same problem occurs when the NE service is restarted.
CSCsq26342 (S): The getHistoryPMData API takes longer than 15 minutes to return data.
CSCsq26362 (S): The output file generated from getHistoryPMData returns duplicate rows.
CSCsq31631 (S): Memory backup and memory restore fail on MGX nodes when Telnet is disabled.
CSCsq32073 (S): Due to security issues, CTM must support Apache web server version 2.0.63.
CSCsq65111 (C): In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.
CSCsq80551 (S): CTM must add support for ONS 15305 R3.0.6 NEs.
CSCsq87850 (CS): SVLAN ports are not displayed correctly.
CSCsq89269 (CS): In the NE Explorer for a GE_XP card, if you click the SVLAN tab, the same tab appears when you 
	         select another GE_XP card.
CSCsq92344 (S): After upgrading to CTM R8.5, all MGX NEs monitored by the CTM server report voltage sensor alarms against 
	        the VXSM card in slot 1. However, if you log into the chassis of the unit, there are no corresponding 
	        alarms on the gateway.
CSCsq94272 (C): You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.
CSCsq96596 (CS): In the NE Explorer for a GE_XP card, the SVLAN tab does not work correctly.
CSCsr06975 (S): In the NE Explorer for a GE_XP card, if you click the SVLAN tab, deselect all SVLANs, and click 
	        Apply, an error occurs.
CSCsr13995 (C): In the NE Explorer for a GE_XP card, when you switch from the QoS tab of one GE_XP card to the 
	        QoS tab of a different GE_XP card, the information from the QoS tab of the first GE_XP card is added 
	        to the information in the QoS tab of the second GE_XP card.
CSCsr16489 (CS): CTM must add support for release 4.1.3 NEs.
CSCsr30785 (S): The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
CSCsr44800 (S): CTM must add support for release 4.1.6 NEs.
CSCsr53609 (S): A CTM server core dump file is created when the CTM server shuts down.
CSCsr61773 (S): CTM must add support for release 4.6.2 NEs.
CSCsr70191 (S): When the system date is changed while the CTM server is running, the CTM server shuts down the NE, PM, and NBI services within five minutes.
CSCsr71540 (S): When you apply a CTM patch on a migrated CTM system, the following SQL error is returned:
	        sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing object
CSCsr94216 (S): Some of the fields that are present in the CTM Alarm Browser are missing from the CTM GateWay/CORBA output. For example, the Object and 
                Module Name fields are missing from the events retrieved by CTM GateWay/CORBA. 
CSCsu18321 (CS): The Circuit Repair window does not automatically close when the repair operation is finished.   
CSCsu50742 (S): The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.
CSCsu62835 (S): The following SQL errors are generated during patch installation:
                Executing pre requisite sql fixes for 361 patch
                5589 rows deleted. Commit complete. Table altered. ALTER TABLE ACTIVE_ALARM_TABLE ADD CONSTRAINT ... 
                ERROR at line 1: ORA-00955: name is already used by an existing object Commit complete.
                done. 
CSCsu88903 (S): The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.

For detailed caveat information, see the Release Notes for Cisco Transport Manager R8.5 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 R8.5.0.381.3 is intended for customers who are currently using CTM R8.5.0.231, R8.5.0.350.1, R8.5.0.359.1, 
R8.5.0.361.2, R8.5.0.368.3, R8.5.0.375.2, or R8.5.0.378.3.

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

Complete the following procedures to upgrade to the CTM R8.5.0.381.3 patch.



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, 
verify that the output results to one of the following:

- Cisco Transport Manager Server Version: 8.5 Build: 231
- Cisco Transport Manager Server Version: 8.5 Build: 350 
- Cisco Transport Manager Server Version: 8.5 Build: 359
- Cisco Transport Manager Server Version: 8.5 Build: 361
- Cisco Transport Manager Server Version: 8.5 Build: 368
- Cisco Transport Manager Server Version: 8.5 Build: 375
- Cisco Transport Manager Server Version: 8.5 Build: 378



Backing Up the CTM Database Before Installing the CTM R8.5.0.381.3 Patch 
------------------------------------------------------------------------

Before installing the CTM R8.5.0.381.3 patch, 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 8.5 User Guide:

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



Downloading the CTM R8.5.0.381.3 Patch
--------------------------------------

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

Step 2: 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 3: At the Select a Device screen, expand Cisco Transport Manager.

Step 4: Click Cisco Transport Manager 8.5.

Step 5: At the Select a Release screen, click Expand all and click 8.5.0.381.3.

Step 6: In the right pane, click CTM8.5.0.381.3.patch.zip.

Step 7: At the Download Image screen, click Download.

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

Step 9: Download the CTM8.5.0.381.3.patch.zip file to a temporary directory (such as /temp) on the CTM server.

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

cd /<directory_name>
unzip CTM8.5.0.381.3.patch.zip

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

cd /temp
unzip CTM8.5.0.381.3.patch.zip

This creates a directory called 381, which contains all of the patch-related files. 

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

cd 381

Step 12: In Windows, download the CTM8.5.0.381.3.patch.zip file to the client workstation. 
Extract the file using a tool such as WinZip, as follows:

a. Open the CTM8.5.0.381.3.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 the CTM R8.5.0.381.3 Server Patch
--------------------------------------------

To apply the CTM R8.5.0.381.3 patch to the server, complete the following steps:

Step 1: Complete the following substeps to 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, complete the following substeps to 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 verify 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 381 directory where the patch was extracted:

./server_patch.sh

Note: The script might take awhile to complete, depending on the database size. 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: 8.5 Build: 381 Patches: 3

Step 7: After installing the CTM R8.5.0.381.3 patch, you have the option of upgrading your JRE version. 
See "Upgrading the CTM R8.5 Server to JRE Version 1.5.0_16" in the Release Notes for Cisco Transport
Manager Release 8.5. 



Installing the CTM R8.5.0.381.3 Client Patch in Windows
-------------------------------------------------------

The following steps describe how to patch a CTM client installation in Windows. Before proceeding, 
verify 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 381 patch 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 8.5 desktop icon or choose the CTM 8.5 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: 8.5 Build: 381 (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:

8.5 [8.5.0.381]

Step 5: After installing the CTM R8.5.0.381.3 patch, you have the option of upgrading your JRE version. 
See "Upgrading the CTM R8.5 Windows Client to JRE Version 1.5.0_16" in the Release Notes for Cisco Transport
Manager Release 8.5.



Installing the CTM R8.5.0.381.3 Client Patch in Solaris
-------------------------------------------------------

The following steps describe how to patch a CTM client installation in Solaris. Before proceeding, 
verify 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 381 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: 8.5 Build: 381 (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:

8.5 [8.5.0.381]

Step 5: After installing the CTM R8.5.0.381.3 patch, you have the option of upgrading your JRE version. 
See "Upgrading the CTM R8.5 Solaris Client to JRE Version 1.5.0_16" in the Release Notes for Cisco Transport Manager Release 8.5.