Installing the CTM R9.0.0.620.5 Patch
-------------------------------------

This readme describes how to download and install the CTM R9.0.0.620.5 patch. 

Note: 

- Caveats are categorized as a server fix (S), client fix (C), or both (CS).
- This patch inherits all fixes from previous patches.

The following caveats are fixed in the CTM R9.0.0.620.5 patch:

CSCsl26108 (S): CTM performs slowly while connecting, discovering, and resynchronizing CTC-based 
		devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
CSCsu90217 (S): Continuous 15 min and 1 day PM lost bucket alarms occur and do not clear.
CSCsz83568 (S): A DB WriterWorker NPE appears in the pmservice.log file for MRC-12 cards.
CSCta29948 (S): Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.
CSCta33231 (S): The number of alarms displayed on the dashboard and NE Explorer is wrong. However, the 
		alarm count is shown correctly in the Alarm Browser.
CSCta39574 (S): When opening the Circuit table from an ONS 15454 node, circuits are not retrieved and a timeout 
		error is displayed.
		Note: If a timeout occurs again, increase the client database timeout period. Refer to section K.6.2,
		Database Timeout Occurs in Appendix K of the Cisco Transport Manager Release 9.0 User Guide.
CSCta69923 (S): Cleared alarms are not removed from the Alarm Browser.
CSCta73923 (S): ONS 15216 EDFA3 nodes lose connectivity with CTM.
CSCtb05738 (S): CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC 
		are assigned to a queue based on the value of the NE node ID. Because the node ID often has 
		an even value, only queues with an even ID are used to process events. Consequently, half of 
		the threads are instantiated but are never used to process events.
CSCtb13395 (S): The Alarm Browser does not display some cleared alarms. CTC shows the cleared alarms, but the 
		same alarms are missing from the CTM Alarm Browser.
CSCtb21147 (S): CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails 
		to report major DS1 alarms.
CSCtb30304 (C): An error message (EID-315) appears after selecting Edit > Find to search for a circuit.
CSCtb31787 (S): CTM R9.0 raises incomplete critical alarms.
CSCtb59547 (CS): CTM GateWay/CORBA reports incorrect physical location information.
CSCtb65065 (C): In the NE Explorer for the ONS 15310 MA or the ONS 15454 MSPP, the first time you select an 
		optical card, the Transceiver tab is blank.
CSCtb73160 (S): The Circuit table does not display port names for ONS 15454 ANSI DS1_E1_56 and OC192_XFP cards.
CSCtb78977 (S): The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
CSCtb83164 (S): After device provision configurations, the following APIs are not updated: getEquipment, 
		getAllEquipment, and getAllEquipmentName.
CSCtc19328 (C): The CTM Domain Explorer window freezes and you are unable to select other NEs.
CSCtc70085 (C): From the CTM client, you cannot launch CTC on release 9.0.x ENEs.
CSCtd03803 (S): ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain
		in Sync_Config state.
CSCtd31222 (S): Circuits without a destination are not displayed in the Circuit table.

The following caveats are fixed in the CTM R9.0.0.604.2 patch:

CSCsz63889 (S): Memory backups fail occasionally for CTC-based release 6.0.1 NEs.
CSCtb88190 (S): CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs 
		with an Unavailable status.
CSCtb85880 (S): After performing NE software upgrades, the SMService restarts NEServices. (Related caveat ID: CSCtc20552.)
CSCtb01411 (S): The network services and network service instances cannot be stopped or started from the Control Panel. 
		The SMService-0-<timestamp>.log file shows the following error message: 
		EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too many open files

The following caveats are fixed in the CTM R9.0.0.600.8 patch:

CSCsq26342 (CS): The getHistoryPMData API takes longer than 15 minutes to return data.
CSCsr48358 (S): The prune_ne_ipaddress script does not work with IPv6 addresses.
CSCsu68317 (S): The northbound CORBA interface returns incorrect cross-connect table information.
		The getAllCrossConnections API returns a CTP name retrieved by a VC-12 circuit in the format
		/sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.
CSCsv12810 (S): An MGX is added to a CTM server, but is not included in the Auto Backup process.
CSCsv33266 (S): If you perform a span switch from the Link Utilization table, the switch does not work for all
		circuits listed in the table.
CSCsw22308 (S): VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with 
		incorrect numbers, making it impossible to tell which VT the PM data is for.
CSCsw68952 (S): A database export fails with the following error: "ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier."
CSCsw72207 (S): The Protection panels shows the wrong name for an OTU2_XP card.
CSCsw91974 (S): In a large network of GNEs and ENEs, CTM fails to collect PM data.
CSCsx22431 (C): For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports
		the correct wavelength value.
CSCsx23360 (S): An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the 		
		Oracle Enterprise Manager or the Alert Log.
CSCsx26527 (S): The CTM link table shows valid and active phantom links, but the corresponding links in the NCP CTM
		layer do not exist.
CSCsx38325 (S): The first database export from the CTM GUI fails.
CSCsx44115 (S): The CTM server does not send SNMP traps or get IPv6 destinations. The following problems occur:
		- CTM does not retrieve Ethernet CoS PM data on ML cards from IPv6 NEs.
		- The SNMP gateway does not forward traps to IPv6 hosts.
CSCsx50126 (S): Due to security issues, CTM must support Apache web server version 2.2.11.
CSCsx50161 (S): The Apache Tomcat software should be disabled to avoid potential security issues.
CSCsx52433 (S): From the MGX Voice Gateway Configuration Center, the Circuit Identifier field is blank for DS1 and SONET
		lines on a VXSM card. Also, utilization counters are not enabled in the Diagnostics Center > Resource
		Control tab.
CSCsx55667 (CS): The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the
		message "no rows from db."
CSCsx56687 (S): The SPAN_BS_TABLE database table displays incorrect working and protected values.
CSCsx64513 (C): A warning message of a possible traffic impact appears when reconfiguring circuits. 
		This warning message should not appear since reconfiguring circuits does not affect traffic.
CSCsx81985 (S): During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05
		directory.
CSCsx93323 (S): CTM displays a "Media Gateway Link state, pendingIs" alarm with a severity set to Warning. 
		In other Element Managers, this type of alarm has a severity set to Major.
CSCsy14909 (CS): A VLAN range cannot be added on a 10GE_XP/GE_XP card.
CSCsy29600 (S): CTM does not receive PM data from managed MGX devices.
CSCsy30294 (S): CTM fails to automatically route and create a STS-24c circuit to the 15454-ADM-10G card when entering a 		
		value in the Time Slot Restriction field.
CSCsy56348 (C): Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
CSCsy83061 (C): From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for release 		
		8.0 NEs.
CSCsy95336 (S): CTM fails to reconfigure circuits on release 8.5 NEs.
CSCsz33838 (S): Cannot add drops on cards configured in Automatic mode.
CSCsz53477 (S): The Error Log contains multiple errors that are similar to the following:
		CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290  
CSCsz58653 (S): Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
CSCsz96763 (S): In the Service Up Time log, clicking the Stopped At column does not sort the table.
CSCta00978 (S): When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.
CSCta30577 (S): The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.
CSCta61660 (S): ENE/GNE role changes on the network causes unstable NE service and node connectivity issues.
CSCta69422 (S): Insufficient memory causes ONS 15305 NE (version 2.0) connectivity issues. Errors also appear after
		marking NEs as Out of Service and then In Service.
CSCta69424 (S): If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the 
		CTM client freezes.

For detailed caveat information, see the Release Notes for Cisco Transport Manager R9.0 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.0.0.620.5 is intended for customers who are currently using one of the following:
 - CTM R9.0.0.507
 - CTM R9.0.0.580
 - CTM R9.0.0.581
 - CTM R9.0.0.600
 - CTM R9.0.0.604

Note: Install the CTM R9.0.0.620.5 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 R9.0.0.620.5 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, make sure that the 
output results to one of the following:

- Cisco Transport Manager Server Version: 9.0 Build: 507
- Cisco Transport Manager Server Version: 9.0 Build: 580
- Cisco Transport Manager Server Version: 9.0 Build: 581
- Cisco Transport Manager Server Version: 9.0 Build: 600
- Cisco Transport Manager Server Version: 9.0 Build: 604


Backing Up the CTM Database Before Installing the CTM R9.0.0.620.5 Patch
------------------------------------------------------------------------

Before installing the CTM R9.0.0.620.5 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 9.0 User Guide:

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



Downloading the CTM R9.0.0.620.5 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 Product screen, expand Cisco Transport Manager.

Step 4: Click Cisco Transport Manager 9.0.

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

Step 6: In the right pane, click CTM9.0.0.620.5.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 CTM9.0.0.620.5.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 CTM9.0.0.620.5.patch.zip

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

cd /temp
unzip CTM9.0.0.620.5.patch.zip

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

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

cd 620

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

a. Open the CTM9.0.0.620.5.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 R9.0.0.620.5 Server Patch
--------------------------------------------

To apply the CTM R9.0.0.620.5 patch 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 620 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: 9.0 Build: 620 Patches: 5



Installing the CTM R9.0.0.620.5 Client Patch in 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 620 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 9.0 desktop icon or choose the CTM 9.0 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.0 Build: 620 (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.0 [9.0.0.620]



Installing the CTM R9.0.0.620.5 Client Patch in 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 620 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.0 Build: 620 (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.0 [9.0.0.620]
