Installing the CTM R8.5.0.410.3 Service Pack
--------------------------------------------

This readme describes how to download and install the CTM R8.5.0.410.3 service pack.

Caution: Due to CSCtc55148, if the following conditions exist, you must truncate all non-empty PM tables in the database before installing the CTM R8.5.0.410.3 patch:

- You are using a small CTM server configuration
- You installed the CTM R8.5.0.387.6 patch
- PM collection is enabled

Note that by truncating PM tables, you will lose all historical PM data. Contact the Cisco TAC for assistance.

Note: 

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

The following caveats are fixed in the CTM R8.5.0.410.3 service pack:


Fixed in CTM R8.5.0.410.3:
--------------------------

CSCsr95859 (S): A CTM server core dump file (ilogCleanup) is created when the CTM server shuts down.
CSCta31966 (S): Memory usage for the ooemc process increases over a period of time.
CSCta42487 (S): The SM service disconnects during a JMOCO hello message, and the CTM server restarts. (See also CSCtf17428.) 
CSCtc28944 (S): From CTM, you cannot launch CTC on a CTC-based R8.5.1 NE.
CSCtc49689 (S): The Oracle Alert log displays deadlock error messages. 
CSCte41792 (C): The code fix for CSCsh98117 changed the Admin State behavior for CTC-based circuits. The correct circuit Admin State behavior must be restored.
CSCte65495 (S): Memory usage for the ooemc process increases when cache Roguewave lists are cleared.
CSCte77971 (S): From CTM, you cannot launch CTC or add new R8.5.1 or R8.6 NEs.
CSCtf06220 (S): Database migration to CTM R9.1 hangs when ARCHIVELOG mode is enabled. The /db05 filesystem fills up, and the migration hangs. 
CSCtf06511 (S): If you upgrade from to CTM R9.1 on a week day (not on a weekend), the following error occurs:
 		ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running
CSCtf08344 (S): The CTP EMS native name is incorrect for a low-order (LO) VC circuit alarm.
CSCtf27628 (S): The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does not update. This issue causes problems with Oracle 
		statistics management and node connectivity.
CSCtf45430 (S): After migrating to CTM R9.0 or R9.1, the processes parameter value is not set correctly in the initCTM.ora file.

The following NE Software Releases are supported in the CTM R8.5.0.410.3 service pack:
- Cisco ONS 15310 MA Release 8.5.4
- Cisco ONS 15454 SDH Release 8.5.4
- Cisco ONS 15454 SONET Release 8.5.4

The CTM R8.5.0.410.3 service pack also provides support for the Carrier Ethernet Multirate 6 (CE-MR-6) card.


Fixed in CTM R8.5.0.392.2:
--------------------------

CSCsu26072 (S): CTM deletes valid, discovered OCH patchcords that are created by CTC.
CSCsu26107 (CS): CTM users cannot create an OCH patchcord trunk or client from the CTC interface on a card 
		 configured with a wavelength higher than 32.
CSCsu49494 (S): The Circuit table does not show the port name for circuits with a source or destination on ML-MR-10 or CE-MR-10 cards.
CSCsv00207 (S): When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though 
		automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.
CSCsv97842 (S): A memory leak occurs on the CTM server because of uncontrolled thread creation.
CSCsw37526 (CS): When you zoom in on the Network Map and save the view as the default, the following error message is generated:
		 EID-700: An error occurred while saving nodes coordinates to the database. Refresh the view and retry.
CSCsw68952 (S): A database export fails with the following error: 
		ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
CSCsw98325 (C): Cannot export tables in HTML format from the CTM client.
CSCsx17951 (C): The Find dialog box > Metro DWDM Circuits option does not find ONS 15454 OCH circuits.
		Note: This caveat is resolved with a change to the Cisco Transport Manager Release 8.5 User Guide. Section 1.5.5.1, "Finding Data,"
		now includes this note: "The Metro DWDM Circuits option applies only to ONS 155xx NEs. For other NE types, such as the ONS 15454,
		the Metro DWDM Circuits option returns no results. To filter circuits on ONS 15454 NEs, use the Circuit table filter."
CSCsx47556 (S): After backing up the CTM R8.5 database from the Control Panel or with the backupdb.sh command, the log file backup_db.log 
		is not generated. The backup_db.log file is not written to the /oracle/admin/CTM/udump directory because there is a space 
		character added when assigning the PATH to the file.
CSCsx52287 (C): Event notification is not audible.
CSCsx55667 (S): The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
CSCsx93323 (CS): CTM displays a "Media Gateway Link state, pendingIs" alarm with a "Warning" severity. In other Element Managers, this 
		 type of alarm is set with a "Major" severity.
CSCsy29600 (S): CTM does not receive PM data from managed MGX devices.
CSCsy56348 (C): Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
CSCsy93198 (S): On the CTM client, the following MGX windows take approximately 15 minutes to load:
		- MGX Chassis View
		- Configuration Center
		- Diagnostics Center
		- Performance screens
CSCsz79773 (S): Occasionally, NE backup files are canceled when automatic daily backups are scheduled. The Job Monitor table shows two backups 
		running at the same time for the same NE, yet only one backup executes successfully. The second backup fails with the following 
		exception: "Cannot execute Backup Database; A similar task is already running."
CSCta30985 (S): A memory leak occurs on the CTM server because of zombie LWP creation when a user is in locked state.
CSCta69019 (S): The ctms-stop and ctms-abort scripts do not work when Oracle is down.
CSCta73380 (C): Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.
CSCta95729 (C): NEs cannot be moved to the bottom right corner of the Create Circuit wizard map view.
CSCtb73160 (S): The Circuit table does not display port names for ONS 15454 SONET DS1_E1_56 and OC192_XFP cards.
CSCtb78977 (S): The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
CSCtb98230 (CS:) After a card restarts, the MGX device log correctly reports a card uptime problem. However, CTM never shows the same alarm.
CSCtc12055 (S): Cannot use automatic or manual backup to prune MGX data.
CSCtc49087 (S): CTM displays the MGX 88xx chassis serial number as N/A in the Equipment Inventory table.
CSCtc55148 (S): Automatic and manual PM data pruning does not work on small CTM servers.
CSCtd50557 (C): Cannot install the client patch if the installation directory name contains a blank space.


Fixed in CTM R8.5.0.390.3:
--------------------------

CSCsu90217 (S): Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
CSCsz63889 (S): Sometimes memory backups fail for CTC-based NEs with release 6.0.1. 
CSCsz75781 (S): The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM
		cards in the network. (Related caveat ID: CSCtb15132.)
CSCsz83568 (S): The following null pointer exception appears in the pmservice.log file for MRC-12 cards: 
		"[com.cisco.stardm.service.pm.ons15454.ONS15454DBWriter,DB WriterWorker#18] 
		NE UMSWMIR030 : VT1-5-10-1-4-7-4-10 - module Type: 219 at shelf 1 and slot 5 raised NullPointerException 
		in parse() method. java.lang.NullPointerException"
CSCta69923 (S): Cleared alarms are not removed from the Alarm Browser.
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"
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.
CSCtb21147 (S): CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report
		major DS1 alarms.
CSCtb34284 (S): The core_pmon.sh script that checks the status of critical CTM processes runs every 30 seconds instead
		of every 5 minutes.
		Note: If a previous workaround has been applied, edit the core-pmon.sh file and remove the row that contains "sleep 270." 
		Installing later patches will not overwrite the file.


Fixed in CTM R8.5.0.387.6:
--------------------------

CSCso44836 (S): On a dual-server setup, the automatic pruning of the /db05 directory does not work. 
	        CTM*.arc files accumulate in /db05 and do not move automatically to /ctm_backup.
CSCso62224 (S): Upgrading the CTM server workstation from CTM R8.0 to R8.5 fails on a dual-server setup. When the Upgrade from 
	        Existing CTM Release check box is checked, the following error message appears: 
		"Can't find database name and version information, abort."
CSCsq67942 (CS): The NE User Access Administration table and Modify NE User wizard show different values for the same fields.
CSCsr60497 (C): When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
CSCsr62641 (C): When you delete NEs from the Deleted NEs group, a warning message should report that the NEs are scheduled for 
		permanent deletion. As a confirmation that NEs have been deleted, check the Audit Log for the message 
		"AUD-5015: <NE ID> has been successfully purged."
CSCsr65306 (S): When upgrading from one CTM release to the next (as detailed in the Cisco Transport Manager Installation Guide), 
		the migration scripts fail with Java exceptions.
CSCsr91285 (C): CTC cross-launch fails when multiple software versions are present.
CSCsu10502 (S): The export_full_db.sh script creates large hidden tar files under the /ctm_backup directory. With multiple
		database exports, the /ctm_backup file system becomes full, and CTM crashes.
CSCsu37369 (S): The Audit Log records a flood of events that are similar to the following:
		AUD-147: NE (xxx) Property Changed - New Subnet Id (nn)
		AUD-5018: NE (xxx) has changed its Subnetwork ID from ...
		AUD-169: Topology Changed - Subnet (Subnetwork-nn) Added
CSCsu66316 (C): Cannot launch CTC from CTM for an ONS 15454 MSTP R8.5.2 node.
CSCsu67460 (S): Even though automatic alarm acknowledgement is enabled, cleared alarms do not move from the 
		Alarm Browser to the Alarm Log.
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.
CSCsu90020 (S): Manual circuit routing through a server trail fails.
CSCsu90286 (S): Circuit routing through a server trail fails.
CSCsv04954 (S): When logging into the CTM client, the login fails.
CSCsv07267 (S): After marking an NE as Out of Service > In Service > Out of Service > In Service, cross-connections are no longer 
		discovered for that NE.
CSCsv07682 (S): You cannot save a VLAN database. The job does not appear in the Job Monitor table, or the operation fails with 
		the error "ORA-01461."
CSCsv12810 (S): An MGX node is added to the 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.
CSCsv40528 (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. (Related caveat ID: CSCsw22308.)
CSCsv47526 (S): The setTPData and getTP APIs might fail for a CTP whose native name involves an MRC-12 card, which generates 
		a null pointer exception.
CSCsv52311 (S): The getSNC and getAllSubnetworkConnections APIs return CTPs in the format /sts1_au3-j=1-k=[1..192] instead 
		of /sts1_au3-j=[1..64]-k=[1..3]. Also, the setTPData API might fail for CTPs created on OC-192 XFP cards, 
		which generates a null pointer exception.
CSCsv70799 (S): CTM and CTC show different values for LBC and OPT parameters on MRC-25G-4 cards.
CSCsv70863 (C): In the card-level NE Explorer > Line tab > Line Config subtab > Admin State field, if you change the administrative 
		state of the port from In Service to Out of Service, a warning dialog box prompts you for confirmation. If you 
		click Yes, the port changes to Out of Service. If you click No, the port remains In Service. If you click the 
		X in the upper corner of the warning dialog box to cancel the operation, the port changes to Out of Service.
CSCsw43520 (S): A memory leak occurs on the CTM server because of zombie LWP creation during startup.
CSCsw73743 (S): The getAllCrossConnections API returns an error if the node does not contain circuits.
CSCsw88114 (C): In a filter dialog box, the User Specified radio button allows only 2009 to 2018 as the year.
CSCsw91974 (S): In a large network of GNEs and ENEs, CTM fails to collect PM data.
CSCsw91994 (S): The CTM database contains unusable indexes, which means that PM tables and audit logs contain no data.
CSCsx09374 (S): In an HA setup, if you install CTM R8.5.0.350.1 or later, the Apache web server is no longer controlled by the 
		Veritas Apache agent. Even if the web server is running, the Veritas Apache agent does not acknowledge it.
CSCsx22431 (C): CTM and CTC show different wavelength calculations for OCHNC circuits.
CSCsx50111 (S): ENE nodes configured in Secure IP mode do not reconnect to CTM after the node is marked as Out of Service and then In Service.
CSCsx50126 (S): Due to security issues, CTM must support Apache web server version 2.2.11.
CSCsx50161 (S): Due to security issues, Apache Tomcat must be disabled.
CSCsx56687 (S): The SPAN_BS_TABLE database table displays incorrect working and protected values.
CSCsx81985 (S): Archive log pruning degrades as database usage increases, and the /db05 directory fills up.
CSCsy10635 (S): When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0 on a single-server setup installed with optical modules only,
		a warning message says problems occurred during the upgrade. The CTM server starts correctly despite the warning message.
CSCsy23134 (S): CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6 NEs.


Fixed in previous CTM R8.5 patches:
-----------------------------------

CSCse91332 (S): CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.
CSCsh67863 (S): NEs do not change to In Service state.
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.
CSCsl26218 (S): The NE services freezes after adding 3000 NEs, deleting 30 NEs, adding a new topology with GNEs, 
		and marking several NEs as Out of Service and then In Service.
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.
CSCsl34530 (S): The network topology is not updated in CTM.
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 not 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.
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.
CSCsu22851 (S): A memory leak occurs on the CTM server because of zombie LWP creation.
CSCsu50742 (S): The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.
CSCsu56857 (S): The Circuit table loses values for the following fields: Customer ID, Service ID, and Description.
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.
CSCsu86435 (C): Occasionally, Cisco Edge Craft does not launch from CTM.
CSCsu88344 (S): CTM performance degrades severely when the managed domain contains duplicate IP addresses. Furthermore, 
		CTM does not display a warning message about the duplicate IP addresses.
CSCsu88903 (S): The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
CSCsv07073 (S): The Circuit table loses values for the following fields: Circuit Alias Name, Note, Customer ID, 
		Service ID, and Description.
CSCsv07090 (S): The Circuit table loses additional values after marking a node as Out of Service/In Service and 
		restarting the NE service.
CSCsv81066 (S): The NE service freezes after discovering a large NE network.

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.410.3 is intended for customers who are currently using one of the following:

- CTM R8.5.0.231
- CTM R8.5.0.350.1
- CTM R8.5.0.359.1
- CTM R8.5.0.361.2 
- CTM R8.5.0.368.3 
- CTM R8.5.0.375.2
- CTM R8.5.0.378.3
- CTM R8.5.0.381.3
- CTM R8.5.0.384.3
- CTM R8.5.0.387.6
- CTM R8.5.0.390.3
- CTM R8.5.0.392.2

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

Note: In a dual-server setup, comment the stty values in the .cshrc file of the database host machine 
to allow the database host machine to copy and execute the patch scripts remotely. Also, 
make sure that there is a .rhosts file in the / directory of the server machine before installing the patch.

Complete the following procedures to upgrade to the CTM R8.5.0.410.3 service pack.


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: 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
- Cisco Transport Manager Server Version: 8.5 Build: 381
- Cisco Transport Manager Server Version: 8.5 Build: 384
- Cisco Transport Manager Server Version: 8.5 Build: 387
- Cisco Transport Manager Server Version: 8.5 Build: 390
- Cisco Transport Manager Server Version: 8.5 Build: 392


Backing Up the CTM Database Before Installing the CTM R8.5.0.410.3 Service Pack
-------------------------------------------------------------------------------

Before installing this patch, it is strongly recommended that you back up the existing database. 
To back up CTM, 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.410.3 Service Pack
---------------------------------------------

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 8.5.

Step 4: 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 5: At the Select a Release screen, click Expand all and click 8.5.0.410.3.

Step 6: In the right pane, click Download Now to download CTM8.5.0.410.3.patch.zip.

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: Download the CTM8.5.0.410.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 .zip file to the temporary directory:

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

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

cd /temp
unzip CTM8.5.0.410.3.patch.zip

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

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

cd 410

Step 12: In Windows, download the CTM8.5.0.410.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.410.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.410.3 Server Service Pack on the Same or Separate Workstation(s)
------------------------------------------------------------------------------------------

Step 1: If you are installing the server patch on separate workstations, you must enable the 
remote shell (rsh) on the server in order to install the server service pack successfully. Complete the following substeps:

a. Enter the following command to verify that the rsh is enabled:

rsh <IP_address_of_CTM_server> ls

b. If an error is returned, open a shell on the CTM server workstation and edit the /.rhosts file. 
As the root user, enter the following commands to modify the /.rhosts file:

# cat >> /.rhosts << EOF
<database_workstation_name> root
EOF

where <database_workstation_name> is the hostname of the CTM database workstation.

Step 2: 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 3: 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 make sure that all user sessions are terminated. 

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

ctms-stop

Step 5: To patch the server, enter the following command in the 410 directory where the service pack 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 6: 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 7: As the root user, enter the following command at the UNIX prompt on the CTM server workstation to verify the 
service pack 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: 410 Patches: 3

Step 8: After installing the service pack, 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.410.3 Client Service Pack in Windows
--------------------------------------------------------------

Note: This procedure also applies to a dual-server setup.

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 410 service pack directory that was extracted with the WinZip utility.

Step 2: Using the command prompt, go to the directory where the service pack 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 service pack
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 service pack 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: 410 (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.410]

Step 5: After installing the service pack, 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.410.3 Client Service Pack in Solaris
--------------------------------------------------------------

Note: This procedure also applies to a dual-server setup.

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 410 directory where the service pack 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 service pack 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: 410 (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.410]

step 5: After installing the service pack, 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.
