Guest

Cisco Transport Manager

Release Notes for Cisco Transport Manager 5.0

Table Of Contents

Release Notes for Cisco Transport Manager Release 5.0

Contents

Introduction

Changes to the Release Notes

Caveats and Sections Added

Caveats Removed

CTM-Supported NE Software Releases

Adding the ONS 15454 SDH R5.0.1 to the Supported NE Table

Adding the ONS 15454 SONET R5.0.3 to the Supported NE Table

Support for the ML-100T-8, CE-100T-8, and ASAP_4 Cards

Installing the CTM R5.0.0.867.2 Patch

How to Differentiate Between a CTM System with the CTM R5.0.0.867.2 Patch and a CTM System Without the Patch

Installing the CTM R5.0.0.866.1 Patch

Installing the CTM R5.0.0.866.1 Patch on the CTM Server

How to Differentiate Between a CTM System with the CTM R5.0.0.866.1 Patch and a CTM System Without the Patch

Installing the CTM R5.0.0.866.1 Patch for the CTM Client on Sun Solaris

Installing the CTM R5.0.0.866.1 Patch for the CTM Client on Microsoft Windows

Resolved Caveats

Open Caveats

CTM Client Caveats

Installation and Migration

Alarm Management

Circuit and Link Management

User Management

Data Services

Domain Explorer

NE Explorer

Performance Monitoring

Control Panel

Miscellaneous

Cisco Transport Controller Caveats

Cisco Edge Craft Caveats

CTM Server Caveats

High Availability Caveats

CTM GateWay/TL1 Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco ONS 15216 EDFA3

Cisco ONS 15310

Cisco ONS 15327 and ONS 15454 SONET

Cisco ONS 15454 MSTP

Cisco ONS 15501

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH

Cisco CRS-1

Cisco Catalyst 6509

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco Transport Manager Release 5.0


February 22, 2008

These release notes describe the caveats for Cisco Transport Manager (CTM) Release 5.0. These release notes accompany the Cisco Transport Manager Release 5.0 User Guide and the Cisco Transport Manager Release 5.0 Installation Guide.


Note You can access the most current Cisco documentation, including these release notes, online at http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/optnet/ctm/index.htm


Contents

These release notes contain the following sections:

Introduction

Changes to the Release Notes

CTM-Supported NE Software Releases

Installing the CTM R5.0.0.867.2 Patch

Installing the CTM R5.0.0.866.1 Patch

Resolved Caveats

Open Caveats

CTM Client Caveats

Cisco Transport Controller Caveats

Cisco Edge Craft Caveats

CTM Server Caveats

High Availability Caveats

CTM GateWay/TL1 Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

Cisco Transport Manager is an advanced management system that provides functionality at the element and network management levels for Cisco optical network elements (NEs). CTM supports fault, configuration, performance, and security management functional areas. CTM also serves as a foundation for integration into a larger overall Operations Support System (OSS) environment by providing northbound gateway interfaces to higher layer management systems.

Beginning with Release 5.0, CTM's expanded charter includes not only management of the Cisco Optical Networking System (ONS) family of optical NEs, but also Cisco routers and switches. As the first example of this expanded charter, CTM R5.0 introduces support for the Cisco Carrier Routing System 1 (CRS-1) and the Cisco Catalyst 6509. Subsequent releases will extend support to additional Cisco routers and switches and continue support for the Cisco ONS family.


Note The CTM R5.0 online help works on Internet Explorer 6.0 and Netscape 7.0. All other browsers are not supported.


Changes to the Release Notes

This section documents supplemental changes that have been made since the initial release of the Release Notes for Cisco Transport Manager Release 5.0.

Caveats and Sections Added

The following caveats and sections have been added to the release notes:

The following sections were added to describe how to install supported patches:

Installing the CTM R5.0.0.867.2 Patch

Installing the CTM R5.0.0.866.1 Patch

The following sections were added to describe how to add support for new NE releases:

Adding the ONS 15454 SDH R5.0.1 to the Supported NE Table

Adding the ONS 15454 SONET R5.0.3 to the Supported NE Table

The following caveats were added:

CSCuk56291 was added as an open caveat for customers who do not install the CTM R5.0.0.866.1 patch, and as a resolved caveat for customers who install the patch.

CSCeh42192 was added as an open caveat for customers who do not install the CTM R5.0.0.867.2 patch, and as a resolved caveat for customers who install the patch.

CSCef69396 (Related DDTS number: CSCeh49691)

CSCeg17587

CSCeh10098

CSCeh32965

CSCeh46416

CSCeh60275

CSCeh61602

CSCeh83555

CSCeh84563

CSCei02136

CSCei50739

CSCei50739

CSCei74892

CSCei76514

CSCei86578

CSCin86183

CSCin93648

CSCsc71161

CSCsf19864

CSCuk56409

Caveats Removed

The following caveats were moved from the Open Caveats section to the Resolved Caveats section, because they were mistakenly classified as open defects:

CSCee15082

CSCef09861

CTM-Supported NE Software Releases

The following table lists the NE software releases supported in CTM R5.0.


Caution Before updating the software image on an NE, check the following table to verify whether the NE software version is supported in this CTM release. If you add an unsupported NE software version, the CTM server might not communicate with one or more NEs in the domain, causing erroneous behavior.

Table 1 CTM-Supported NE Software Releases 

Product
Software Release

ONS 15201/ONS 15252

Release 1.1(2)

Release 1.1(3)

ONS 15216 100-GHz OADM1/2/4

Release 2.2.2

ONS 15216 EDFA2

Release 2.2.1

Release 2.3

Release 2.4

ONS 15216 EDFA3

Release 1.1

ONS 15216 100-GHz Red/Blue Filters

Passive

ONS 15216 200-GHz Red/Blue Filters

Passive

ONS 15216 200-GHz OADM1/2

Passive

ONS 15216 EDFA1

Passive

ONS 15216 OSC

Passive

ONS 15216 DCU

Passive

ONS 15216 FlexLayer

Passive

ONS 15302

Release 1.0.1

Release 2.0

Release 2.0.11

ONS 15305

Release 1.1.1

Release 2.0

Release 2.0.12

ONS 15310 CL

Release 5.0

ONS 15327

Release 3.4.1

Release 4.1.3

Release 4.1.4

Release 4.1.5

Release 4.1.6

Release 4.6.2

Release 5.0

ONS 15454 SONET3

Release 3.2.1

Release 3.3

Release 3.4.1

Release 4.0.1

Release 4.0.3

Release 4.1.1

Release 4.1.3

Release 4.1.4

Release 4.1.5

Release 4.1.6

Release 4.6.2

Release 4.7

Release 5.0

Release 5.0.34

ONS 15454 SDH5

Release 4.1.3

Release 4.1.4

Release 4.6.2

Release 4.6.3

Release 4.7

Release 5.0

Release 5.0.16

ONS 15501

Release 4.1 DC

Release 4.1 AC

ONS 15530

Cisco IOS Release 12.2(22)S2

Cisco IOS Release 12.2(25)SV

ONS 15540 Extended Services Platform (ESP)

Cisco IOS Release 12.2(22)S2

Cisco IOS Release 12.2(25)SV

ONS 15540 Extended Services Platform with external cross-connect capability (ESPx)

Cisco IOS Release 12.2(22)S2

Cisco IOS Release 12.2(25)SV

ONS 15600 SONET

Release 1.1.2

Release 1.1.3

Release 1.3.17

Release 5.0

ONS 15600 SDH

Release 1.4

ONS 15800

Release 2.0 (TL1 Agent Release 2.0)

Release 2.1 (TL1 Agent Release 2.1)

ONS 15801

Release 2.0 (TL1 Agent Release 2.0)

Release 2.1 (TL1 Agent Release 2.1)

ONS 15808

Release 2.1 (TL1 Agent Release 2.3)

Release 2.2 (TL1 Agent Release 2.4)

Cisco CRS-1

Release 2.0

Release 3.0

Cisco Catalyst 65098

CatOS 6.3(7) or later

1 In order for CTM to support the ONS 15302 R2.0.1, you must install the CTM R5.0.0.866.1 patch. See Installing the CTM R5.0.0.866.1 Patch.

2 In order for CTM to support the ONS 15305 R2.0.1, you must install the CTM R5.0.0.866.1 patch. See Installing the CTM R5.0.0.866.1 Patch.

3 The ONS 15454 SONET is the ANSI version of the product, which includes support for the Multiservice Transport Platform (MSTP) and Multiservice Provisioning Platform (MSPP) configurations.

4 In order for CTM to support the ONS 15454 SONET R5.0.3, you must add the software version to the Supported NE Table. See Adding the ONS 15454 SONET R5.0.3 to the Supported NE Table.

5 The ONS 15454 SDH is the ETSI version of the product, which includes support for the MSTP and MSPP configurations.

6 In order for CTM to support the ONS 15454 SDH R5.0.1, you must add the software version to the Supported NE Table. See Adding the ONS 15454 SDH R5.0.1 to the Supported NE Table.

7 In the CTM software, the Supported NE table shows "15600 1.30" in the Version Name field for the ONS 15600 SONET. This corresponds to the ONS 15600 SONET R1.3.1, which is the supported version.

8 The Cisco Catalyst 6509 is supported as part of the CRS-1.


Adding the ONS 15454 SDH R5.0.1 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R5.0.1, you must add the latest software version to the Supported NE Table. Complete the following steps:


Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.

Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "05.00-004L-23.23" as the software version, and "15454 SDH 5.00" as the version name.

Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.

Step 4 Enter 05.01-005B-27.22 in the Software Version field. Change the Version Name field to 15454 SDH 5.01.

Step 5 Click OK.

Step 6 CTM asks for confirmation to manage the new version. Click OK.


Adding the ONS 15454 SONET R5.0.3 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R5.0.3, you must add the latest software version to the Supported NE Table. Complete the following steps:


Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.

Step 2 Select a row that lists "Cisco ONS 15454 SONET" as the NE model, "05.00-004L-23.23" as the software version, and "15454 5.00" as the version name.

Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.

Step 4 Enter 05.03-005C-09.07 in the Software Version field. Change the Version Name field to 15454 5.03.

Step 5 Click OK.

Step 6 CTM asks for confirmation to manage the new version. Click OK.


Support for the ML-100T-8, CE-100T-8, and ASAP_4 Cards

Although mentioned in the CTM documentation and online help, the ML-100T-8, CE-100T-8, and ASAP_4 cards are not officially supported in CTM R5.0. These cards will be supported in a future CTM release.

Installing the CTM R5.0.0.867.2 Patch

This section describes how to install the CTM R5.0.0.867.2 patch, which fixes CSCeh42192.


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

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

Step 3 Click Cisco Transport Manager 5.0.

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 Software Type screen, click Transport Manager (CTM) Patches.

Step 6 Click Expand all; then, click 5.0.0.867.2.

Step 7 In the right pane, click CTMR5.0.0.867.2.patch.tar.

Step 8 At the Download Image screen, click Download.

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

Step 10 Download the CTMR5.0.0.867.2.patch.tar file to a temporary directory (for example, /tmp).

Step 11 Enter the following commands to extract the files to the temporary directory:

cd /<directory_name>
tar xvf CTMR5.0.0.867.2.patch.tar

For example, to extract the files to the /tmp directory, enter:

cd /tmp
tar xvf CTMR5.0.0.867.2.patch.tar

Step 12 Log into the CTM R5.0 server workstation as the root user.

Step 13 Complete the following substeps to shut down all of the CTM clients:

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

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

c. In the Logged In CTM Users table, select the user whose session will be ended and choose Administration > Log Out User (or click the Log Out User tool).

d. 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 while the CTM server logs out the selected CTM client. The CTM GUI is frozen for approximately 1 minute until the request is complete.

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

ctms-stop 

Step 15 On the CTM R5.0 server workstation, enter the following commands to copy the openfusion file from the /opt/CiscoTransportManagerServer directory to a backup file:

mv /opt/CiscoTransportManagerServer/openfusion 
/opt/CiscoTransportManagerServer/openfusion.bak

Step 16 Enter the following command to install the patch:

./installOF.sh all <CTM_server_IP_address>


Note After the patch installs successfully, a new openfusion directory is created.


Step 17 The install script updates the jacorb.properties file with new parameters. Verify that the opt/CiscoTransportManagerServer/openfusion/classes/jacorb.properties contain the following new parameters:

jacorb.connection.client.max_idle_receptor_Threads=5

jacorb.connection.client.max_receptor_threads=1000

jacorb.connection.server.max_idle_receptor_threads=5

jacorb.connection.server.max_receptor_threads=1000

jacorb.connection.server.keepalive=on

jacorb.connection.client.keepalive=off

Step 18 Enter the following command to run the server_patch.sh file:

./server_patch.sh

Step 19 Assuming that the mll_inv_view.sql file is in the /tmp directory, enter the following commands to update the mll inventory view in the Oracle database:

su - oracle
sqlplus ctmanager/ctm123!
SQL> @/tmp/mll_inv_view.sql
SQL> exit

Step 20 Complete one of the following options, depending on your configuration:

For Solaris clients, copy the CTMClient.jar and Platform.jar to the /opt/CiscoTransportManagerClient/bin directory.

For Windows clients, copy the CTMClient.jar and Platform.jar to the C:\Cisco\TransportManagerClient5_0\bin directory.

Step 21 Complete one of the following options, depending on your configuration:

For Solaris clients, download the ems-client.def file to a temporary directory. Then, copy the ems-client.def file from the temporary directory to the /opt/CiscoTransportManagerClient/config directory (default).

For Windows clients, download the ems-client.def file to a temporary directory. Then, copy the ems-client.def file from the temporary directory to the C:\Cisco\TransportManagerClient5_0\config directory (default).

Step 22 As the root user, enter the following command at the UNIX prompt on the CTM R5.0 server workstation to start the CTM server:

ctms-start

Step 23 Complete one of the following options to start the CTM client, depending on your configuration:

For Solaris clients, enter the following command:

./ctmc-start

For Windows clients, double-click the CTM desktop icon or choose the CTM Start menu shortcut.



Note After installing the CTM R5.0.0.867.2 patch, the CTM client version is shown as 5.0.1[5.0.0.867.2] in the Domain Explorer and Control Panel windows. This is a known issues that is tracked as CSCin91080.


How to Differentiate Between a CTM System with the CTM R5.0.0.867.2 Patch and a CTM System Without the Patch

Log into the CTM R5.0 server workstation as the root user and enter the following command:

showctm

In the output, you will see "5.0.0.867.2" as the version string if the patch has been applied. If the patch has not been applied, you will see "5.0.0.866."

Installing the CTM R5.0.0.866.1 Patch

This section describes how to install the CTM R5.0.0.866.1 patch, which fixes CSCuk56291. Contact the Cisco Technical Assistance Center (TAC) to obtain the patch.

Installing the CTM R5.0.0.866.1 Patch on the CTM Server


Note The default directory where the CTM server is installed is /opt/CiscoTransportManagerServer. If you are using a different installation directory, change the directory name in the .sh script.



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

ctms-stop 

Step 2 Copy the server_patch.tar file to a temporary location on the CTM R5.0 server workstation.

Step 3 Enter the following command to untar the server_patch.tar file from the temporary location:

tar -xvf server_patch.tar

Step 4 Enter the following commands to run the bryggen_patch.sh file, which replaces the server_version.def and the CTMServer files:

cd server_patch 
./bryggen_patch.sh 

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

ctms-start


Note After installing the CTM R5.0.0.866.1 patch, the CTM server discovers the ONS 15302 R2.0.1 and ONS 15305 R2.0.1 as R2.0.0 and reports "2.0.0" as the software version. This is a known issue that is tracked as CSCuk56409.



How to Differentiate Between a CTM System with the CTM R5.0.0.866.1 Patch and a CTM System Without the Patch

Log into the CTM R5.0 server workstation as the root user and enter the following command:

showctm

In the output, you will see "5.0.0.866.1" as the version string if the patch has been applied. If the patch has not been applied, you will see "5.0.0.866."

Installing the CTM R5.0.0.866.1 Patch for the CTM Client on Sun Solaris


Note The default directory where the CTM client is installed is /opt/CiscoTransportManagerClient. If you are using a different installation directory, change the directory name in the .sh script.



Step 1 Complete the following substeps to shut down all of the CTM clients:

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

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

c. In the Logged In CTM Users table, select the user whose session will be ended and choose Administration > Log Out User (or click the Log Out User tool).

d. 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 while the CTM server logs out the selected CTM client. The CTM GUI is frozen for approximately 1 minute until the request is complete.

Step 2 Copy the solaris_client.tar file to a temporary location on the CTM R5.0 client workstation.

Step 3 Enter the following command to untar the solaris_client.tar file from the temporary location:

tar -xvf solaris_client.tar

Step 4 Enter the following commands to run the bryggen_client_patch.sh file:

cd solaris_client
./bryggen_client_patch.sh

Step 5 Enter the following commands to restart the CTM R5.0 client:

cd /opt/CiscoTransportManagerClient
./ctmc.sh 


Note After installing the CTM R5.0.0.866.1 patch, if you choose Help > About Cisco Transport Manager, the dialog box shows the client version as 5.0.0.866.1 Build: 866 Patch: 1.



Installing the CTM R5.0.0.866.1 Patch for the CTM Client on Microsoft Windows


Note The default directory where the CTM client is installed is C:\Cisco\TransportManagerClient5_0. If you are using a different installation directory, change the directory name in the .bat script.



Step 1 Complete the following substeps to shut down all of the CTM clients:

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

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

c. In the Logged In CTM Users table, select the user whose session will be ended and choose Administration > Log Out User (or click the Log Out User tool).

d. 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 while the CTM server logs out the selected CTM client. The CTM GUI is frozen for approximately 1 minute until the request is complete.

Step 2 Double-click the /client_patch folder where the windows_client.zip file is located.

Step 3 Copy the windows_client.zip file to a temporary location on the CTM R5.0 client workstation.

Step 4 Double-click windows_client.zip and extract the contents from the temporary location.

Step 5 Double-click the bryggen_client_patch.bat file.

Step 6 Double-click the CTM desktop icon or choose the CTM Start menu shortcut to start the CTM R5.0 client.


Note After installing the CTM R5.0.0.866.1 patch, if you choose Help > About Cisco Transport Manager, the dialog box shows the client version as 5.0.0.866.1 Build: 866 Patch: 1.



Resolved Caveats

The following table lists caveats that are resolved in CTM R5.0.

Table 2 Caveats Resolved in CTM R5.0 

DDTS Number
Caveat

CSCdz31204

Cisco Transport Controller (CTC), when launched from CTM, does not provide user interface options for Disable Network Discovery or Disable Circuit Management.

CSCdz79862

Alarms are not visible for DS3i-N-12 cards in ONS 15454 SONET or ONS 15454 SDH NEs.

CSCea00262

ONS 15454 SDH performance monitoring (PM) tables do not contain far-end path-level PM data for E1-14 and E1-42 electrical cards.

CSCea01880

PM tables display the near-end errored second ratio (ESR) value for VC12 cards as -1 or N/A (not available).

CSCea03766

CTC shows duplicate threshold crossing alerts (TCAs) for OC-3 failure count line (FC-L).

CSCea12620

The High-Order PM table does not show TCAs for STM4-4 cards.

CSCea36759

If the CTM GateWay/CORBA getTCATPParams method is performed on a card shortly after circuit creation on that card, the method might not return any data.

CSCea90737

CTM misses several audit records after a software activate and revert from certain NE software versions.

CSCeb20421

If CTM loses connectivity to a gateway network element (GNE), CTM GateWay TL1 cannot communicate to end network elements (ENEs) even if CTM has direct LAN connectivity to ENEs and the GNE is not configured to run proxy for ENEs.

CSCeb22752

Virtual Tributary (VT) circuit creation over a VT aggregation point (VAP) fails.

CSCeb29829

CTM reports multiple spurious wavelength collision discrepancies.

CSCeb30141

The PJ STS Mon number might have a value out of range of the number of STSs for an OC-N card.

CSCeb30943

The wrong card state is shown after changing a protect card.

Related Distributed Defect Tracking System (DDTS) number: CSCin58008.

CSCeb38711

Under certain circumstances you cannot route a VT circuit.

CSCeb46316

The port names are not updated in circuit tables for XTC-DS3 interfaces.

CSCeb49440

The Service Monitor (SM) service does not restart the NE Service after a failure.

CSCeb55503

When you upgrade or downgrade a card (for example, from DS3 to DS3NE) and this card is part of a protection group, the protection group details in the NE Explorer are not updated with the new card type.

CSCeb65980

Protection channel access (PCA) drops cannot be added to unidirectional circuits.

Related DDTS numbers: CSCea93569 and CSCin74711.

CSCeb69868

In the NE Defaults tab of the ONS 15327 NE Explorer, you can see entries for cards that are not supported by the ONS 15327 but only by the ONS 15454.

Related DDTS number: CSCeb71437.

CSCeb76147

In the Alarm Browser, when filtering on "Equipment" as the affected object and when the selection is the CTM domain, EMS alarms with "CTM" as the source ID are also shown in the result set.

CSCec47971

A Ring ID Mismatch alarm might not be raised on an ONS 15600 node if the ring ID is changed.

CSCec48260

In rare cases, CTM does not collect PM data on an ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE for a period of time and then begins collecting this data again.

CSCec55540

A discard confirmation popup is not always shown when you change values in a window and then exit the window without applying the changes.

Related DDTS number: CSCec71705.

CSCec68790

For STM1, STM4, and STM16 payload types, the RS Thresh 15 Min, RS Thresh 1 Day, MS Thresh 15 Min, and MS Thresh 1 Day tabs under the corresponding STM-N tab show data that is inconsistent with the data shown by CTC.

CSCec69051

If you try to invoke a CTC session from CTM immediately after exiting CTC, CTM displays the error message "Error in launching CTC node view." The error message should prompt you to wait several minutes before restarting CTC.

CSCec73776

PM statistics for Gigabit Ethernet/FICON/ESCON payload on multirate 2.5G transponder cards are not shown in the correct table.

CSCec74833

The Circuit table launch times out while performing a database query to retrieve data.

CSCec75025

When an STS circuit is created on an EC1 card for an ONS 15454, the NE Defaults tab shows the following columns for STS Threshold 15 Min and STS Threshold 1 Day:

PSC (protection switching count)

PSD (protection switching duration)

These columns are not supported from the NE Defaults tab.

CSCec75048

When an STS circuit is created on an EC1 card for an ONS 15454, the NE Defaults tab does not show the following columns for STS Threshold 15 Min and STS Threshold 1 Day:

PJCS-PDET (pointer justification count seconds-path detected)

PJCS-PGEN (pointer justification count seconds-path generated)

PJC-DIFF (pointer justification count-difference)

Related DDTS number: CSCin64299.

CSCec75057

When an STS circuit is created on an OC-N card for an ONS 15454, the following columns are missing from the STS Threshold 15 Min and STS Threshold 1 Day tabs:

PJCS-PDET

PJCS-PGEN

PJC-DIFF

Related DDTS number: CSCin64300.

CSCec77803

In CTM, the Line Config tab for TXP_MR_2.5G or TXPP_MR_2.5G cards has the payload type GE/FC/2FC. The value OOS_AINS is available as an option in the State field. When this value is chosen, it is displayed in the related State check box. This state value is not supported by CTC on TXP_MR_2.5G or TXPP_MR_2.5G cards with GE/FC/2FC payload type. The OOS_AINS value should not be available in CTM.

CSCec77964

Cannot provision the Protection Group Revertive feature.

CSCec87081

In the CTM high availability (HA) environment, once the active server is switched over to standby mode, several web server processes continue running.

Related DDTS number: CSCin63704.

CSCec87371

Extra slots are shown as possible regeneration peer slots for the TXP_MR_2.5G card.

CSCec88320

CTM does not display the protection status of the splitter-protected trunk ports (ports 2 and 3) of TXPP_MR_2.5G cards.

CSCec89948

CTM GateWay/TL1 reports inconsistent "Gateway not ready" error messages.

CSCed01103

CTM GateWay/CORBA does not report physical termination points (PTPs) for ONS 15501 AC or DC NEs.

CSCed01988

The way that CTM GateWay/TL1 applies NE authentication changes is inconsistent with CTM.

CSCed02193

If you modify the data communications channel (DCC) area ID from CTM, all existing rows are deleted except for the one that changed. Additionally, one DCC area ID is allowed to change for DCC area IDs that have a bidirectional line switch ring (BLSR) on them.

CSCed02444

A PM graph is not displayed for class of service (CoS) PM tables.

CSCed09857

The IfRtrPriority value for the ONS 15600 is shown as negative for the router priority range 127 to 255.

CSCed12277

The NE Explorer displays a shelf view with no cards in it.

CSCed12641

Searching for an existing SONET circuit by name from the domain root node in the Domain Explorer window returns the error "The requested search criteria did not return any data."

CSCed13198

CTM GateWay/TL1 loses connection with the GNE when the ENE stops responding.

CSCed14657

It is possible to provision Power High and Power Low thresholds in the Optical Threshold tab.

CSCed15572

In the ONS 15454 NE Explorer node-level DCC/GCC tab > LDCC/SDCC subtabs, the tables for the transponder have the Delete button enabled. This is inconsistent with the SONET/SDH tab. If you click the Delete button, an error is shown on the console.

Related DDTS number: CSCin62714.

CSCed15942

When you launch the ONS 15454 NE Explorer and create an Open Shortest Path First (OSPF) virtual link, the creation succeeds and CTM allows you to edit the neighbor address. The neighbor address cannot be changed in CTC. If you change the address on the ONS 15454, the change goes through. If you change the address on the ONS 15600, the change does not go through.

CSCed16221

When the XC loopback parameter is changed from CTC, CTM does not show the updated value.

CSCed16784

In CTM, the Loopback tab for TXP_MR_2.5G and TXPP_MR_2.5G cards has the payload type GE/FC/2FC. The value OOS_AINS (Out of Service Auto-In Service Soak) is available as an option in the State field. When this value is chosen, it is displayed in the related State check box. This state value is not supported by CTC on TXP_MR_2.5G or TXPP_MR_2.5G cards with GE/FC/2FC payload type. The OOS_AINS value should not be available in CTM.

CSCed17653

The PM graph cannot be plotted for the following parameters on ONS 15454 SONET and ONS 15454 SDH NEs: Minimum Transmitted Power, Average Transmitted Power, Maximum Transmitted Power, Minimum Received Power, Average Received Power, and Maximum Received Power.

CSCed19034

An extra row, with all fields set to N/A, is displayed in the table on the WDM ANS/Port Status tab.

CSCed20629

Network maps are refreshed automatically.

CSCed20635

Layer 2 links are shown as gray instead of green or an alarm color on the Network Map.

CSCed21311

CTM GateWay/CORBA expects an inconsistent connection termination point (CTP) name for creating a subnetwork connection (SNC).

CSCed22174

Cannot create a threshold on a Fiber Channel 4-port (FC_MR-4) card.

CSCed23084

NEs show loss of connectivity although there are no connectivity problems.

CSCed23142

The Subnetwork Explorer might not display all the NEs in its tree and throws exceptions on the console.

CSCed23288

In the Laser tab of the ONS 15216 EDFA2 NE Explorer, the Measured Gain parameter displays the wrong tooltip.

CSCed24134

Link selection during manual circuit creation takes a long time.

CSCed24268

When an MXP_2.5G_10G card is configured for Ethernet, the Rx Utilization, Tx Utilization, and Last Clear Time are shown as blank in the PM table.

Related DDTS number: CSCed23166.

CSCed26954

CTM GateWay/CORBA reports ONS 158xx-related PTPs with the following format:

/rack=[1..8]/shelf=[1..3]/slot=[1..17]/port=[0:2]


The format should be:

/rack=[1..8]/shelf=[1..3]/slot=[1..17]

CSCed29161

Changing the regen-peer slot on a TXPP-MR-2.5G card is not reflected in the card selected as the regeneration peer.

CSCed29431

For links with a layer rate of Layer 2, the protection type shows PARTIALLY-PROTECTED when the underlying circuit is FULLY-PROTECTED.

CSCed30552

Some of the attributes in the WDM ANS tab > Provisioning-OADM subtab show default values in CTM. CTC shows the same attributes as empty fields.

CSCed30564

Two groups of attributes are displayed in the Provisioning-OADM tab while CTC displays a single group of attributes called Term East Side/West Side.

CSCed31079

CTM does not allow clearing of normalization of an auto ring switch. A CLEAR command on the standby span cannot be issued from the NE Explorer.

CSCed31402

The hourglass cursor is continuously displayed when the create Y-cable operation fails.

CSCed31430

When a PM query is filtered on a physical location down to the subslot and/or port level, the results of the query are incorrect. There is no problem if the query filters at the slot level.

CSCed31786

It is possible to create a dense wavelength division multiplexing (DWDM) ring with an empty ring ID, but it is not possible to delete or modify the ring from the DWDM Ring table.

CSCed32534

TXP-MR-2.5G and TXPP-MR-2.5G cards are not displayed in the Circuit Trace window.

CSCed35005

If another filter is applied after 1-day PM data is launched, the resulting PM table switches to 15 minutes instead of 1 day.

CSCed35048

The installer hangs when migrating CTM GateWay/CORBA for a high-end configuration.

Related DDTS number: CSCee37164.

CSCed35285

PM graphs are printed even though Cancel is clicked on the Page Setup dialog box.

CSCed39660

Cannot create manual links between an ONS 15454 NE and an ONS 15327 NE when terminating on an 8-port OC-3 card or a 4-port OC-12 card.

CSCed40793

Message dialog boxes flash and cannot be read properly.

CSCed42822

If all the relay IP addresses or community names in the Network Explorer > Network tab > SNMP subtab are deleted, the updates for Relay B and Relay C are not propagated to CTM.

CSCed44483

Deletion of a SONET/SDH layer link between NEs in different network partitions fails and returns an error message.

CSCed45464

Cannot create Layer 2 (L2) services on a point-to-point topology.

CSCed48452

The physical PM counts for laser bias current (LBC), optical power transmitted (OPT), and optical power received (OPR) on ONS 15600 cards are shown as a percentage (%) and do not match the counts displayed in CTC.

CSCed49451

The Disable AIS/RDI on TIM-S check box is grayed out.

CSCed49477

From CTM it is possible to provision a loopback on TXP-2.5G-MR or TXPP-2.5G-MR card trunk ports 2 and 3 when those ports are not in the Out of Service-Maintenance (OOS_MT) state. CTM does not display an error and shows misaligned data to CTC.

CSCed49800

When NEs are moved from one network partition to another, subsequent CORBA calls fail.

CSCed52322

PM tables for ML cards are not initialized for a proxy/firewall setup.

CSCed52436

Simple Network Management Protocol (SNMP) v1 traps for ML cards are not supported in a proxy/firewall setup.

CSCed53126

The NE shelf view is shown as empty, even if data is present in the database.

CSCed55516

CTM does not support command-line interface (CLI) Telnet through firewall/proxy.

CSCed55558

NEs might not get discovered after changing the password from the Control Panel.

CSCed56799

Incorrect alarms are shown in CTM after the NE software is upgraded or downgraded to a different version.

CSCed57663

The loopback tab shows ports in a random order. When this occurs, some provisioning might not be reflected correctly on the CTM client.

CSCed59044

The Additional Info field of the TopologicalLink_T method displays an invalid provisioning type for some links.

CSCed85080

The CTM GateWay/TL1 command line start and stop scripts are not included in the base CTM R4.6 installation.

CSCee10238

Discrepancy in port states.

CSCee15082

Cannot launch the Border Gateway Protocol (BGP) Configuration Neighbor Group Address Family (AF) window.

CSCee35815

The ONS 15216 EDFA2 R2.2.1 does not support the Software Download option under the Administration menu, which is correct in CTM. However, if you perform a software download for multiple NEs, the ONS 15216 EDFA2 NE type and version number are included in the list of available NEs. The ONS 15216 EDFA2 should not be included in the list.

CSCee47477

CTM does not warn you when a port is already used by another termination.

CSCee51192

The Storage Area Network (SAN) PM table does not distinguish between FC- and GE-configured equipment.

CSCee56949

The autolaser shutdown (ALS) feature is not available for OSC_CSM and OSCM cards.

CSCee56952

The ALS feature is not available for OPT-PRE and OPT-BST cards.

CSCee56956

CTM allows provisioning of the SendDoNotUse, PJVC4Mon#, PJSTSMon#, and AINS Soak parameters in the Line tab > Line Config subtab for OSC_CSM and OSCM cards.

CSCee60367

ONS 15216 EDFA2 NEs become unavailable when the SNMP community name is public.

CSCee65483

No newdbinfo file is created on secondary (standby) nodes when migrating data from older releases to CTM R4.7 in an HA environment. This causes database link creation errors during basic migration.

CSCee77842

If you click the Help button while creating an alarm profile in the NE Explorer, the help file does not open.

CSCee86185

WDM ANS data is displayed for both east and west sides even though only one side is provisioned.

CSCee87332

An error message appears while creating a circuit that is set to route automatically. The circuit is created if it is set to route manually through an alternate route.

CSCee92128

After changing the ONS 15600 SONET user code, the Equipment Inventory table is not updated.

CSCee95202

CTM GateWay/CORBA does not display the PTP names correctly in the returned topological links after getAllTopologicalLinks is invoked. According to the CTM GateWay/CORBA implementation agreement, the PTP names for the ONS 158xx NEs have the format /rack=1/shelf=1/slot=x:y, where y can be 2, 3, 4, or 5 depending on the direction of the PTP. However, when getAllTopologicalLinks is invoked, the last integer, which denotes the direction, is missing.

CSCee96564

The Alarm Browser does not report alarms for the ONS 15216 EDFA2.

CSCef09861

Cannot set the password in the Intermediate System-to-Intermediate System (ISIS) Configuration application > Process tab. The error message "Illegal value: Error unpacking password" is generated.

CSCef11489

Under certain conditions, a software download job fails on the ONS 15216 EDFA2.

CSCef97988

After creating a BLSR, the Reversion Time field in the BLSR table shows "Inconsistent."

Related DDTS number: CSCin58398.

CSCef97991

The CTM timing status for building integrated timing supply (BITS) facilities does not change when the source changes.

CSCeg03526

The ONS 15600 NE Explorer shows insufficient STS information for OC cards.

CSCeh42192

When the thread count exceeds the 1000-thread limit, a loss of connectivity may occur.

CSCin18581

PSC-R and PSC-S counts are interchanged in CTM.

CSCin33531

TCAs are not generated when a PM threshold is crossed for a protect STM16 card.

CSCin34621

Unavailable seconds-VT layer (UAS-V) fields in the SONET VT Path PM table are not colored purple when TCAs are raised.

CSCin51761

When an unmanaged NE is viewed in the Domain NE table, some of the columns display incorrect information.

CSCin57164

Cannot provision a 2-fiber BLSR using CTM.

CSCin58690

The NE name is not updated in CTM.

CSCin59283

Pointer justification counts are not available.

CSCin59436

A VT or VC aggregation point circuit is added without a customer ID or service ID.

CSCin59967

CTM does not show the new software version for ONS 1530x NEs.

CSCin60303

Path pointer justification PM values are returned for electrical cards. Pointer justification parameters are valid only for optical cards, not electrical cards; therefore, they should be marked as undefined for all electrical cards.

CSCin60327

A unidirectional link cannot be added to an unmanaged NE even though the PTPs are available.

CSCin60599

A loss of signal (LOS) alarm from an E3/T3 card is displayed on the E3 card.

CSCin60601

ONS 15302 or ONS 15305 NE alarms related to power ports and external alarm ports are reported in CTM and Cisco Edge Craft (CEC) with a physical location, for example Chassis, port xx, while similar alarms on other NE families (ONS 15454) are displayed with Chassis as the physical location.

CSCin60976

After migrating the database from CTM R4.0 to R4.6, the values for the TxPackets, RxGiants, and TxCollisions parameters on E-series cards for ONS 15327, ONS 15454 SONET, and ONS 15454 SDH NEs in the Ethernet PM table do not match the previous values.

CSCin61076

An error message is displayed while attempting circuit creation.

CSCin61166

When an STS circuit is created on a DS3I card for an ONS 15454, the NE Defaults tab shows SAS-P in the Line tab for the DS3I card.

CSCin61333

No J0, J1, or J2 byte indication is present in the Trace Identifier Mismatch (TIM) alarm probable cause.

CSCin62239

During circuit provisioning, the port name is shown incorrectly for the ONS 15327 XTC-14 and XTC-28-3 cards. The port name of the first port is associated with the remaining ports during circuit creation.

CSCin62271

The STS details that are part of the displayed affected object are shown incorrectly in the Alarm Browser for unidirectional path switched ring (UPSR) switching alarms for the R3.0.3 NE.

CSCin62468

Irrelevant information is shown in the source and destination PTP IDs for a Layer 2 link that is selected on the Network Map.

CSCin62499

Cannot change the area ID for the DCC used by the BLSR setup.

CSCin62525

CTM allows you to provision cards when an XC card is not present.

CSCin62568

Modification of OSPF advertisement and Admin State is not reflected correctly for SDCC and LDCC terminations in CTM.

CSCin62842

PM data is not collected on ENEs in a GNE/ENE setup.

CSCin62873

A Provisioner user with read-only permissions for the Firewall/Proxy tab can see the tab as read/write, although the Apply button is disabled.

CSCin63190

On ONS 15302 NEs, filtering for Affected Object on OC-N/STM-N shows alarms raised for Regenerator Section (RS) Affected Object.

Related DDTS number: CSCin72569.

CSCin63291

In the Create Protection Group dialog box, the Reversion Time field does not have 0.5 minutes as an allowable value when the node has an E3 card provisioned on it.

CSCin63315

An error message is displayed during circuit creation.

CSCin63387

Circuit creation generates an error that a named circuit already exists. However, the Circuit table does not show any such circuit.

CSCin63395

When the Security Advisory message is entered, it is shown as &apos when updated.

CSCin63492

A user with a custom user profile with no access to the Circuit table can launch the Link Utilization table from a network map, but not from the Link table.

CSCin63543

CTM GateWay/CORBA throws a ProcessingFailureException while running the setTPData application program interface (API).

CSCin63592

CTM GateWay/CORBA throws an org.omg.CORBA.UNKNOWN error while running the getCTPsAndTopologicalLinks API.

CSCin63704

On the CTM server, the showctm command displays more than one Apache web server process.

CSCin63841

When you try to create multiple single-source, multidestination circuits by specifying the number of circuits as greater than 1, the Create Circuit wizard fails for all circuits after the first one.

CSCin63863

CTM shows an extra threshold parameter (SAS-P) for DS3I/DS3IN cards on ONS 15454 SONET or ONS 15454 SDH R4.6 NEs. This parameter is not supported by the hardware or CTC.

CSCin63877

The Time Zone, Date, and Daylight Saving Time fields in the NE Explorer > Identification tab are not updated.

CSCin63981

PM data validity is not shown correctly for the SONET path PM parameters for ONS 15327 NEs.

CSCin64103

Invalid data is shown as valid for the RS-UAS PM parameter on optical cards.

CSCin64123

Automatic login does not work in domain manager mode if there are many NEs present.

CSCin64491

The map in the Create Circuit wizard shows the wrong direction for VAP and low-order aggregation point (LAP) links.

CSCin64543

If you select Simple Password as the authentication type for OSPF virtual links, the Confirm Password value is not populated upon edit. The save does not occur until you retype the Confirm Password each time upon edit.

CSCin64591

In the NE Explorer > Line Config tab for the ONS 15454 SONET or ONS 15454 SDH NE, the possible line type values are not shown correctly for the DS3I card.

CSCin64596

Cannot launch TL1 from the ONS 15454 SDH NE Explorer.

CSCin64602

The Service State value is not updated when the service is stopped from the Control Panel.

CSCin64727

The VT affected object option is missing from the Alarm Browser filter for ONS 15327 NEs. This means that these alarms cannot be filtered out.

CSCin65011

The "Alarm suppressed: Alarms/Events suppress for this object" alarm in CTC is shown as a Section Trace Identifier Mismatch alarm in CTM.

CSCin65040

CTM displays unsupported path threshold parameters (PSC-W, PSD-W, PSC-R, PSD-R, PSC-S, PSD-S) for an OC-3 card on the ONS 15454 SONET R3.21.

CSCin65047

Information for certain BLSRs is missing from the BLSR table.

CSCin65103

The OC-12 card shows far-end STS path thresholds for the ONS 15454 SONET R3.03. These far-end parameters are not supported by the hardware or CTC.

CSCin65156

In the Modify User Profile wizard, the ONS 1580x Domain NE Table option has no privilege selected for the default users (Network Admin, Operator, and Provisioner). The allowed permissions are Read Only and No Access.