Release Notes for Cisco Transport Manager 7.2 [Cisco Transport Manager]

Table Of Contents

Release Notes Cisco Transport Manager Release 7.2

Contents

Introduction

New Features and Functionality

Changes to the Release Notes

NE Software Releases Added

Caveats and Sections Added

Caveats and Sections Removed

CTM-Supported NE Software Releases

Adding the ONS 15310 CL R7.0.5 to the Supported NE Table

Adding the ONS 15310 CL R7.2.2 to the Supported NE Table

Adding the ONS 15310 CL R7.2.3 to the Supported NE Table

Adding the ONS 15310 MA R7.0.5 to the Supported NE Table

Adding the ONS 15310 MA R7.2.2 to the Supported NE Table

Adding the ONS 15310 MA R7.2.3 to the Supported NE Table

Adding the ONS 15327 R4.1.82 to the Supported NE Table

Adding the ONS 15327 R5.0.4 to the Supported NE Table

Adding the ONS 15327 R7.0.5 to the Supported NE Table

Adding the ONS 15327 R7.2.2 to the Supported NE Table

Adding the ONS 15327 R7.2.3 to the Supported NE Table

Adding the ONS 15454 SONET R4.1.82 to the Supported NE Table

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

Adding the ONS 15454 SONET R7.0.4 to the Supported NE Table

Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table

Adding the ONS 15454 SONET R7.2.2 to the Supported NE Table

Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.3 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.4 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table

Adding the ONS 15454 SDH R7.2.2 to the Supported NE Table

Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table

Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table

Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table

Adding the MGX Voice Gateway R5.3.00 to the Supported NE Table

Third-Party Patches and Security Notices

CTM-Supported JRE and Apache Versions

Resolved Caveats

Installing the CTM R7.2.0.230.1 Patch

Determining What CTM Patch Is Currently Installed in the CTM System

Backing Up the CTM Database Before Installing the CTM R7.2.0.230.1 Patch

Downloading the CTM R7.2.0.230.1 Patch

Installing the CTM R7.2.0.230.1 Server Patch on the Same or Separate Workstation(s)

Installing the CTM R7.2.0.230.1 Client Patch in Windows

Installing the CTM R7.2.0.230.1 Client Patch in Solaris

Open Caveats

Installation and Upgrade Caveats

CTM Client Caveats

Alarm Management

Circuit and Link Management

User Management

Data Services

Domain Explorer

NE Explorer

Network Map

Performance Monitoring

Control Panel

Miscellaneous

CTM Server Caveats

Cisco Transport Controller Caveats

High Availability Caveats

CTM GateWay/TL1 Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco 7600

Cisco Catalyst 6509

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15302 and Cisco ONS 15305

Cisco ONS 15310

Cisco ONS 15327 and Cisco ONS 15454 SONET

Cisco ONS 15454 MSTP

Cisco ONS 15501, Cisco ONS 15530, and Cisco ONS 15540

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH

Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808

Cisco CRS-1 and Cisco XR 12000

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes Cisco Transport Manager Release 7.2

September 18, 2009

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

Note You can access the most current Cisco documentation, including these release notes, online at http://www.cisco.com/en/US/products/sw/opticsw/ps2204/tsd_products_support_series_home.html.

Contents

These release notes contain the following sections:

•Introduction

•New Features and Functionality

•Changes to the Release Notes

•CTM-Supported NE Software Releases

•Third-Party Patches and Security Notices

•CTM-Supported JRE and Apache Versions

•Resolved Caveats

•Installing the CTM R7.2.0.230.1 Patch

•Open Caveats

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

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), routers, and switches. 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.

In Release 7.2, CTM supports the Cisco 7600 Series Edge Router (Cisco 7600); the Cisco Optical Networking System (ONS) family of optical NEs; the Cisco Carrier Routing System 1 (CRS-1), which includes the Cisco Catalyst 6509; the Cisco XR 12000; the Cisco MGX 8880 Voice Gateway and MGX 8850/8830 Voice-Enabled Multiservice Switch; and the Cisco MDS 9000 Multilayer Director and Fabric Switch.

Note The Cisco 7600 module is not supported in a high availability installation setup in CTM R7.2.

New Features and Functionality

The following table describes the new features and functionality in CTM R7.2.

Table 1 New Features and Functionality in CTM R7.2

New Feature

Description

Support for the RAN-SVC card

Adds support for the RAN-SVC card on the ONS 15454 SONET and ONS 15454 SDH.

The RAN-SVC card decompresses wireless voice data that was compressed by a peer module residing in a Cisco MWR-1941-DC. The RAN-SVC card receives the compressed data on VT1.5 or VC12 circuits from the ONS 15454 cross-connect. The data is then reconstituted onto VT1.5 or VC12 circuits and driven back over the ONS 15454 cross-connect. The ONS 15454 receives compressed information over a variety of higher rate interfaces, such as OC-3 or DS-3. The decompressed voice data is delivered externally over DS-1 or E1 interfaces.

Support for the XFP OC-192 SR1

Adds support for the XFP OC-192 SRI module, a new type of pluggable I/O module (PIM) with one pluggable port module (PPM) on the existing ONS 15600 SONET Any Service Any Port (ASAP_4) card.

Support for CTC-based NE Release 7.2

Expands CTM's scope to include operations, administration, management, and provisioning (OAM&P) for the following CTC-based NE releases:

•ONS 15310 CL R7.2

•ONS 15310 MA R7.2

•ONS 15327 R7.2

•ONS 15454 SONET R7.2

•ONS 15454 SDH R7.2

•ONS 15600 SONET R7.2

Support for CRS-1 Release 3.3.1

Expands CTM's scope to include OAM&P for the CRS-1 R3.3.1.

Support for XR 12000 Release 3.3.1

Expands CTM's scope to include OAM&P for the XR 12000 R3.3.1.

Support for CRS-1 DWDM physical layer interface modules (PLIMs)

DWDM is an optical technology that is used to increase bandwidth over existing fiber-optic backbones. DWDM can be configured on supported 10 Gigabit Ethernet (GE) or packet-over-SONET PLIMs. DWDM support in Cisco IOS XR software is based on the Optical Transport Network (OTN) protocol as specified in ITU-T G.709. This standard combines the benefits of SONET/SDH technology with the multiwavelength networks of DWDM. It also provides for forward error correction (FEC), which reduces network costs by reducing the number of regenerators used.

The CRS-1 supports OC-768c/STM-256 DWDM PLIM and 10 GE DWDM PLIM controllers. Support includes:

•Inventory collection

•Card-level operational status in the Equipment Inventory table

•Interface-level operational status shown in the rack view

•Alarm and LED status shown in the rack view and tree view

Note These DWDM PLIMs are supported only on the CRS-1, not on the XR 12000.

DWDM optical channel client connection (OCHCC) circuit provisioning for CRS-1

Allows you to provision DWDM OCHCC circuits on CRS-1 NEs.

Manual link creation between DWDM cards on CRS-1 NEs

Allows you to create manual links between DWDM cards on CRS-1 NEs. Adds support for two new link layer rates: 10G ITU and 40G ITU.

DWDM Controller Configuration application

The CRS-1 and XR 12000 NE Explorer now includes the DWDM Controller Configuration application, which allows you to configure DWDM controllers.

SONET/SDH APS Configuration application

The CRS-1 and XR 12000 NE Explorer now includes the SONET/SDH APS Configuration application, which enables recovery from fiber (external) or equipment (interface and internal) failures at the SONET or SDH line layer. You can configure SONET/SDH automatic protection switching (APS) for CRS-1 and XR 12000 NEs.

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

NE Software Releases Added

The following NE releases were added to Table 2, "CTM Supported NE Software Releases":

•Manually added to CTM:

Note You can manually add new NE software releases to CTM R7.2.0.191.1 or later.

–ONS 15310 CL R7.0.5

–ONS 15310 CL R7.2.2

–ONS 15310 CL R7.2.3

–ONS 15310 MA R7.0.5

–ONS 15310 MA R7.2.2

–ONS 15310 MA R7.2.3

–ONS 15327 R4.1.82

–ONS 15327 R5.0.4

–ONS 15327 R7.0.5

–ONS 15327 R7.2.2

–ONS 15327 R7.2.3

–ONS 15454 SONET R4.1.82

–ONS 15454 SONET R7.0.3

–ONS 15454 SONET R7.0.4

–ONS 15454 SONET R7.0.5

–ONS 15454 SONET R7.2.2

–ONS 15454 SONET R7.2.3

–ONS 15454 SDH R7.0.3

–ONS 15454 SDH R7.0.4

–ONS 15454 SDH R7.0.5

–ONS 15454 SDH R7.2.2

–ONS 15454 SDH R7.2.3

–ONS 15600 SONET R7.2.2

–ONS 15600 SONET R7.2.3

–MGX Voice Gateway R5.3.00

Caveats and Sections Added

The following caveats and sections were added to the release notes:

•The section CTM-Supported JRE and Apache Versions was added to list the JRE and Apache versions supported in CTM R7.2.

•The section Third-Party Patches and Security Notices was added.

•The section Installing the CTM R7.2.0.230.1 Patch was added.

•The section New Features and Functionality was added.

•The following footnote was added to Table 2: "The MGX Voice Gateway R5.3.10 is supported in compatible mode when it is added as an R5.3.00 NE and when only R5.3.00 features are managed."

•The ONS 15305 CTC R3.0.2 was added to Table 2. The ONS 15305 CTC R3.0.2 uses the same NE version string as the ONS 15305 CTC R3.0 and is supported automatically by CTM R7.2. You do not need to manually add support for the ONS 15305 CTC R3.0.2, because it is simply a firmware upgrade from the ONS 15305 CTC R3.0.

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

–Adding the ONS 15310 CL R7.0.5 to the Supported NE Table

–Adding the ONS 15310 CL R7.2.2 to the Supported NE Table

–Adding the ONS 15310 CL R7.2.3 to the Supported NE Table

–Adding the ONS 15310 MA R7.0.5 to the Supported NE Table

–Adding the ONS 15310 MA R7.2.2 to the Supported NE Table

–Adding the ONS 15310 MA R7.2.3 to the Supported NE Table

–Adding the ONS 15327 R4.1.82 to the Supported NE Table

–Adding the ONS 15327 R5.0.4 to the Supported NE Table

–Adding the ONS 15327 R7.0.5 to the Supported NE Table

–Adding the ONS 15327 R7.2.2 to the Supported NE Table

–Adding the ONS 15327 R7.2.3 to the Supported NE Table

–Adding the ONS 15454 SONET R4.1.82 to the Supported NE Table

–Adding the ONS 15454 SONET R7.0.3 to the Supported NE Table

–Adding the ONS 15454 SONET R7.0.4 to the Supported NE Table

–Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table

–Adding the ONS 15454 SONET R7.2.2 to the Supported NE Table

–Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table

–Adding the ONS 15454 SDH R7.0.3 to the Supported NE Table

–Adding the ONS 15454 SDH R7.0.4 to the Supported NE Table

–Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table

–Adding the ONS 15454 SDH R7.2.2 to the Supported NE Table

–Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table

–Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table

–Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table

–Adding the MGX Voice Gateway R5.3.00 to the Supported NE Table

•The following caveats were added:

–CSCsd13369, page 176

–CSCse91995, page 168

–CSCsf05571, page 118

–CSCsg22838, page 158

–CSCsg79219, page 45

–CSCsg90763, page 115

–CSCsh20561, page 78

–CSCsh69456, page 121

–CSCsh85790, page 170

–CSCsh86942, page 96

–CSCsi06634, page 172

–CSCsi07958, page 179

–CSCsi13810, page 180

–CSCsi17070, page 131

–CSCsi29161, page 180

–CSCsi39771, page 115

–CSCsi39881, page 160

–CSCsi40250, page 172

–CSCsi40265, page 173

–CSCsi49818, page 96

–CSCsi55020, page 97

–CSCsi55227, page 97

–CSCsi55280, page 97

–CSCsi56588, page 107

–CSCsj01676, page 122

–CSCsj01791, page 64

–CSCsj07403, page 174

–CSCsj17755, page 174

–CSCsk27644, page 80

–CSCsk27692, page 98

–CSCsk53826, page 65

–CSCsk74382, page 65

–CSCsl03411, page 66

–CSCsl31698, page 124

–CSCsl34425, page 125

–CSCsm91004, page 126

–CSCsq96399, page 66

–CSCsq96429, page 66

–CSCsv14849, page 66

–CSCsy18486, page 67

Caveats and Sections Removed

The following sections were removed, because the CTM R7.2.0.230.1 patch inherits all bug fixes and obsoletes these earlier patches and service packs:

•Installing the CTM R7.2.0.199.1 Patch

•Installing the CTM R7.2.0.205.2 Patch

•Installing the CTM R7.2.0.207.1 Patch

•Installing the CTM R7.2.0.208.1 Patch

•Installing the CTM R7.2.0.215.2 Patch

•Installing the CTM R7.2.0.221.2 Service Pack

•Installing the CTM R7.2.0.224.2 Patch

CTM-Supported NE Software Releases

The following table lists the NE software releases supported in CTM R7.2.

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 2 CTM-Supported NE Software Releases

Product

Software Release

NE Version String

ONS 15216 100-GHz OADM1/2/4

Release 2.2.2

soadma.out-Ver2.2.2

Release 2.2.2

soadmb.out-Ver2.2.2

Release 2.2.3

soadma.out-Ver2.2.3

Release 2.2.3

soadmb.out-Ver2.2.3

ONS 15216 200-GHz OADM1/2

Passive

1.0

ONS 15216 DCU

Passive

2.0

ONS 15216 DWDM Filter (including ONS 15216 100-GHz Red/Blue Filters and ONS 15216 200-GHz Red/Blue Filters)

Release 2.1

2.1

ONS 15216 EDFA1

Passive

1.0

ONS 15216 EDFA2

Release 2.3

v2.3.0

Release 2.4

v2.4.0

ONS 15216 EDFA3

Release 1.1

01.01.00

ONS 15216 FlexLayer

Passive

1.0

ONS 15216 OSC

Passive

2.0

ONS 15302

Release 2.0.1

2.0.1

Release 2.0.2

2.0.2

ONS 15305

Release 2.0.2

2.0.2

Release 2.0.3

2.0.3

ONS 15305 CTC

Release 3.0

04.60-X06B-22.16

Release 3.0.2

04.60-X06B-22.16

ONS 15310 CL

Release 5.0.2

05.02-005C-26.23

Release 5.0.4

05.04-005G-13.18

Release 5.0.6

05.06-005H-23.18

Release 5.0.7

05.07-005J-05.17

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006H-07.19

Release 7.0.5¹

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

Release 7.2.2²

07.22-007B-08.19

Release 7.2.3³

07.23-007F-22.02

ONS 15310 MA

Release 7.0

07.00-005L-19.20

Release 7.0.2⁴

07.02-006H-07.19

Release 7.0.5⁵

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

Release 7.2.2⁶

07.22-007B-08.19

Release 7.2.3⁷

07.23-007F-22.02

ONS 15327

Release 4.1.3

04.13-003L-19.01

Release 4.1.4

04.14-004C-09.23

Release 4.1.8

04.180-005-E1322

Release 4.1.81

04.181-006-A2920

Release 4.1.82⁸

04.182-006-L2805

Release 4.6.6

04.66-005K-09.00

Release 5.0.2

05.02-005C-26.23

Release 5.0.4⁹

05.04-005G-13.18

Release 5.0.6

05.06-005H-23.18

Release 5.0.7

05.07-005J-05.17

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006H-07.19

Release 7.0.5¹⁰

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

Release 7.2.2¹¹

07.22-007B-08.19

Release 7.2.3¹²

07.23-007F-22.02

ONS 15454 SONET

Release 4.0.3

04.03-004F-23.23

Release 4.1.3

04.13-003L-19.01

Release 4.1.4

04.14-004C-09.23

Release 4.1.6

04.16-004I-10.23

Release 4.1.8

04.180-005-E1322

Release 4.1.81

04.181-006-A2920

Release 4.1.82¹³

04.182-006-L2805

Release 4.6.1

04.61-004B-03.02

Release 4.6.4

04.64-004L-21.00

Release 4.6.5

04.65-005C-23.19

Release 4.6.6

04.66-005K-09.00

Release 4.7 (MSTP only)

04.70-004I-14.01

Release 5.0.2

05.02-005C-26.23

Release 5.0.4

05.04-005G-13.18

Release 5.0.6

05.06-005H-23.18

Release 5.0.7

05.07-005J-05.17

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.1 (MSTP only)

07.01-006D-20.20

Release 7.0.2

07.02-006H-07.19

Release 7.0.3 (MSTP only)¹⁴

07.03-006I-29.09

Release 7.0.4 (MSTP only)¹⁵

07.04-007A-08.16

Release 7.0.5¹⁶

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

07.20-M06H-22.00

Release 7.2.2¹⁷

07.22-007B-15.13

Release 7.2.3¹⁸

07.23-007F-22.02

ONS 15454 SDH

Release 4.1.8

04.180-005-E1322

Release 4.6.3

04.63-004I-30.23

Release 5.0

05.00-004L-23.23

Release 5.0.1

05.01-005B-27.22

Release 5.0.4

05.04-005G-13.18

Release 5.0.6

05.06-005H-23.18

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.1 (MSTP only)

07.01-006D-20.20

Release 7.0.2

07.02-006H-07.19

Release 7.0.3 (MSTP only)¹⁹

07.03-006I-29.09

Release 7.0.4 (MSTP only)²⁰

07.04-007A-08.16

Release 7.0.5²¹

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

07.20-M06H-22.00

Release 7.2.2²²

07.22-007B-15.13

Release 7.2.3²³

07.23-007F-22.02

ONS 15501

Release 4.1 AC

4.1

Release 4.1 DC

4.1

ONS 15530

Cisco IOS Release 12.2(26)SV1

12.2(26)SV1

Cisco IOS Release 12.2(29)SV

12.2(29)SV

ONS 15540 Extended Services Platform (ESP)

Cisco IOS Release 12.2(26)SV1

12.2(26)SV1

Cisco IOS Release 12.2(29)SV

12.2(29)SV

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

Cisco IOS Release 12.2(26)SV1

12.2(26)SV1

Cisco IOS Release 12.2(29)SV

12.2(29)SV

ONS 15600 SONET

Release 1.3.1

Note Release 1.3.1 is the same as 1.3.0.

01.30-004D-01.20

Release 5.0.2

05.02-005C-26.23

Release 5.0.4

05.04-005G-13.18

Release 5.0.6

05.06-005H-23.18

Release 5.0.7

05.07-005J-05.17

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006H-07.19

Release 7.2

07.20-006E-04.17

Release 7.2.2²⁴

07.22-007B-08.19

Release 7.2.3²⁵

07.23-007F-22.02

ONS 15600 SDH

Release 1.4

01.40-004A-15.18

ONS 15800

Release 2.1 (TL1 Agent Release 2.1)

2.1

ONS 15801

Release 2.1 (TL1 Agent Release 2.1)

2.1

ONS 15808

Release 2.2 (TL1 Agent Release 2.4)

2.4

CRS-1

Release 3.2

3.2.0

Release 3.2.1

3.2.1

Release 3.2.2

3.2.2

Release 3.3

3.3.0

Release 3.3.1

3.3.1

XR 12000

Release 3.2

3.2.0

Release 3.2.1

3.2.1

Release 3.2.2

3.2.2

Release 3.3

3.3.0

Release 3.3.1

3.3.1

Cisco 7609

12.2(18)SXF

—

Cisco Catalyst 6509

CatOS 7.1(1) or later

Most recent CatOS release

Cisco MDS 9000

MDS 9000 family, including MDS 9100, MDS 9200, MDS 9500, Port Analyzer Adapter, and Storage Networking Module

—

Cisco MGX 8880 Media Gateway

Release 5.0.20

5.0(20.0)

Release 5.2.00

5.2(0.0)

Release 5.3.00²⁶, ²⁷

5.3(0.0)

Voice-Enabled Cisco MGX 8850 Multiservice Switch

Release 5.0.20

5.0(20.0)

Release 5.2.00

5.2(0.0)

Release 5.3.00

Note See footnote about adding support for this software release.

5.3(0.0)

Voice-Enabled Cisco MGX 8830 Multiservice Switch

Release 5.0.20

5.0(20.0)

Release 5.2.00

5.2(0.0)

Release 5.3.00

Note See footnote about adding support for this software release.

5.3(0.0)

VISM-PR

Release 3.3.10

—

Release 3.3.20

—

Release 3.3.25

—

VXSM

Release 5.0.70 (VXSM 1.5 MR)

—

Release 5.2.00 (VXSM 2.0)

—

Release 5.3.00 (VXSM 2.5)

—

¹In order for CTM to support the ONS 15310 CL R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.0.5 to the Supported NE Table.

²In order for CTM to support the ONS 15310 CL R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.2.2 to the Supported NE Table.

³In order for CTM to support the ONS 15310 CL R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.2.3 to the Supported NE Table.

⁴In order for CTM to support the ONS 15310 MA R7.0.2, you must run a script in the database. See CSCsf29570.

⁵In order for CTM to support the ONS 15310 MA R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.0.5 to the Supported NE Table.

⁶In order for CTM to support the ONS 15310 MA R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.2.2 to the Supported NE Table.

⁷In order for CTM to support the ONS 15310 MA R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.2.3 to the Supported NE Table.

⁸In order for CTM to support the ONS 15327 R4.1.82, you must add the software version to the Supported NE table. See Adding the ONS 15327 R4.1.82 to the Supported NE Table.

⁹In order for CTM to support the ONS 15327 R5.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15327 R5.0.4 to the Supported NE Table.

¹⁰In order for CTM to support the ONS 15327 R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.0.5 to the Supported NE Table.

¹¹In order for CTM to support the ONS 15327 R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.2.2 to the Supported NE Table.

¹²In order for CTM to support the ONS 15327 R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.2.3 to the Supported NE Table.

¹³In order for CTM to support the ONS 15454 SONET R4.1.82, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R4.1.82 to the Supported NE Table.

¹⁴In order for CTM to support the ONS 15454 SONET R7.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.0.3 to the Supported NE Table.

¹⁵In order for CTM to support the ONS 15454 SONET R7.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.0.4 to the Supported NE Table.

¹⁶In order for CTM to support the ONS 15454 SONET R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table.

¹⁷In order for CTM to support the ONS 15454 SONET R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.2.2 to the Supported NE Table.

¹⁸In order for CTM to support the ONS 15454 SONET R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table.

¹⁹In order for CTM to support the ONS 15454 SDH R7.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.0.3 to the Supported NE Table.

²⁰In order for CTM to support the ONS 15454 SDH R7.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.0.4 to the Supported NE Table.

²¹In order for CTM to support the ONS 15454 SDH R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table.

²²In order for CTM to support the ONS 15454 SDH R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.2.2 to the Supported NE Table.

²³In order for CTM to support the ONS 15454 SDH R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table.

²⁴In order for CTM to support the ONS 15600 SONET R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table.

²⁵In order for CTM to support the ONS 15600 SONET R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table.

²⁶In order for CTM to support the MGX Voice Gateway R5.3.00, you must add the software version to the Supported NE table. See Adding the MGX Voice Gateway R5.3.00 to the Supported NE Table.

²⁷The MGX Voice Gateway R5.3.10 is supported in compatible mode when it is added as an R5.3.00 NE and when only R5.3.00 features are managed.

Adding the ONS 15310 CL R7.0.5 to the Supported NE Table

In order for CTM to support the ONS 15310 CL R7.0.5, you must add the 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 15310 CL" as the NE model, "07.00-005L-19.20" as the software version, and "15310 CL 7.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 07.05-007D-20.22 in the Software Version field. Change the Version Name field to 15310 CL 7.05.

Step 5 Click OK.

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

Adding the ONS 15310 CL R7.2.2 to the Supported NE Table

In order for CTM to support the ONS 15310 CL R7.2.2, you must add the 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 15310 CL" as the NE model, "07.20-006E-04.17" as the software version, and "15310 CL 7.20" 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 07.22-007B-08.19 in the Software Version field. Change the Version Name field to 15310 CL 7.22.

Step 5 Click OK.

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

Adding the ONS 15310 CL R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15310 CL R7.2.3, you must add the 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 15310 CL" as the NE model, "07.20-006E-04.17" as the software version, and "15310 CL 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15310 CL 7.23.

Step 5 Click OK.

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

Adding the ONS 15310 MA R7.0.5 to the Supported NE Table

In order for CTM to support the ONS 15310 MA R7.0.5, you must add the 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 15310 MA" as the NE model, "07.00-005L-19.20" as the software version, and "15310 MA 7.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 07.05-007D-20.22 in the Software Version field. Change the Version Name field to 15310 MA 7.05.

Step 5 Click OK.

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

Adding the ONS 15310 MA R7.2.2 to the Supported NE Table

In order for CTM to support the ONS 15310 MA R7.2.2, you must add the 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 15310 MA" as the NE model, "07.20-006E-04.17" as the software version, and "15310 MA 7.20" 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 07.22-007B-08.19 in the Software Version field. Change the Version Name field to 15310 MA 7.22.

Step 5 Click OK.

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

Adding the ONS 15310 MA R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15310 MA R7.2.3, you must add the 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 15310 MA" as the NE model, "07.20-006E-04.17" as the software version, and "15310 MA 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15310 MA 7.23.

Step 5 Click OK.

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

Adding the ONS 15327 R4.1.82 to the Supported NE Table

In order for CTM to support the ONS 15327 R4.1.82, you must add the 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 15327" as the NE model, "04.181-006-A2920" as the software version, and "15327 4.181" 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 04.182-006-L2805 in the Software Version field. Change the Version Name field to 15327 4.182.

Step 5 Click OK.

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

Adding the ONS 15327 R5.0.4 to the Supported NE Table

In order for CTM to support the ONS 15327 R5.0.4, you must add the 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 15327" as the NE model, "05.02-005C-26.23" as the software version, and "15327 5.02" 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.04-005G-13.18 in the Software Version field. Change the Version Name field to 15327 5.04.

Step 5 Click OK.

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

Adding the ONS 15327 R7.0.5 to the Supported NE Table

In order for CTM to support the ONS 15327 R7.0.5, you must add the 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 15327" as the NE model, "07.00-005L-19.20" as the software version, and "15327 7.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 07.05-007D-20.22 in the Software Version field. Change the Version Name field to 15327 7.05.

Step 5 Click OK.

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

Adding the ONS 15327 R7.2.2 to the Supported NE Table

In order for CTM to support the ONS 15327 R7.2.2, you must add the 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 15327" as the NE model, "07.20-006E-04.17" as the software version, and "15327 7.20" 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 07.22-007B-08.19 in the Software Version field. Change the Version Name field to 15327 7.22.

Step 5 Click OK.

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

Adding the ONS 15327 R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15327 R7.2.3, you must add the 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 15327" as the NE model, "07.20-006E-04.17" as the software version, and "15327 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15327 7.23.

Step 5 Click OK.

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

Adding the ONS 15454 SONET R4.1.82 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R4.1.82, you must add the 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" as the NE model, "04.181-006-A2920" as the software version, and "15454 4.181" 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 04.182-006-L2805 in the Software Version field. Change the Version Name field to 15454 4.182.

Step 5 Click OK.

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

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

In order for CTM to support the ONS 15454 SONET R7.0.3, you must add the 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" as the NE model, "07.00-005L-19.20" as the software version, and "15454 7.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 07.03-006I-29.09 in the Software Version field. Change the Version Name field to 15454 7.03.

Step 5 Click OK.

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

Adding the ONS 15454 SONET R7.0.4 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R7.0.4, you must add the 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" as the NE model, "07.00-005L-19.20" as the software version, and "15454 7.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 07.04-007A-08.16 in the Software Version field. Change the Version Name field to 15454 7.04.

Step 5 Click OK.

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

Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R7.0.5, you must add the 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" as the NE model, "07.00-005L-19.20" as the software version, and "15454 7.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 07.05-007D-20.22 in the Software Version field. Change the Version Name field to 15454 7.05.

Step 5 Click OK.

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

Adding the ONS 15454 SONET R7.2.2 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R7.2.2, you must add the 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" as the NE model, "07.20-006E-04.17" as the software version, and "15454 7.20" 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 07.22-007B-15.13 in the Software Version field. Change the Version Name field to 15454 7.22.

Step 5 Click OK.

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

Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15454 SONET R7.2.3, you must add the 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" as the NE model, "07.20-006E-04.17" as the software version, and "15454 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15454 7.23.

Step 5 Click OK.

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

Adding the ONS 15454 SDH R7.0.3 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R7.0.3, you must add the 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, "07.00-005L-19.20" as the software version, and "15454 SDH 7.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 07.03-006I-29.09 in the Software Version field. Change the Version Name field to 15454 SDH 7.03.

Step 5 Click OK.

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

Adding the ONS 15454 SDH R7.0.4 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R7.0.4, you must add the 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, "07.00-005L-19.20" as the software version, and "15454 SDH 7.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 07.04-007A-08.16 in the Software Version field. Change the Version Name field to 15454 SDH 7.04.

Step 5 Click OK.

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

Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R7.0.5, you must add the 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, "07.00-005L-19.20" as the software version, and "15454 SDH 7.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 07.05-007D-20.22 in the Software Version field. Change the Version Name field to 15454 SDH 7.05.

Step 5 Click OK.

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

Adding the ONS 15454 SDH R7.2.2 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R7.2.2, you must add the 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, "07.20-006E-04.17" as the software version, and "15454 SDH 7.20" 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 07.22-007B-15.13 in the Software Version field. Change the Version Name field to 15454 SDH 7.22.

Step 5 Click OK.

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

Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15454 SDH R7.2.3, you must add the 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, "07.20-006E-04.17" as the software version, and "15454 SDH 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15454 SDH 7.23.

Step 5 Click OK.

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

Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table

In order for CTM to support the ONS SONET 15600 R7.2.2, you must add the 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 15600" as the NE model, "07.20-006E-04.17" as the software version, and "15600 7.20" 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 07.22-007B-08.19 in the Software Version field. Change the Version Name field to 15600 7.22.

Step 5 Click OK.

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

Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table

In order for CTM to support the ONS 15600 SONET R7.2.3, you must add the 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 15600" as the NE model, "07.20-006E-04.17" as the software version, and "15600 7.20" 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 07.23-007F-22.02 in the Software Version field. Change the Version Name field to 15600 7.23.

Step 5 Click OK.

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

Adding the MGX Voice Gateway R5.3.00 to the Supported NE Table

In order for CTM to support the MGX Voice Gateway R5.3.00, you must add the 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 MGX Voice Gateway" as the NE model, "5.0(20.0)" or "5.2(0.0)" as the software version, and "MGX VG 5.0(20.0)" or "MGX VG 5.2(0.0)" 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 5.3(0.0) in the Software Version field. Change the Version Name field to MGX VG 5.3(0.0).

Step 5 Click OK.

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

Third-Party Patches and Security Notices

Cisco reviews the known Oracle patch alerts every quarter, including patches for security breaches. If any Oracle patch applies to CTM or its components, Cisco tests the Oracle patch and includes it as a requirement for the next CTM patch. Cisco also conducts quarterly reviews of other third-party software products that CTM uses, such as Solaris, Apache, and Java.

CTM-Supported JRE and Apache Versions

The following tables list the JRE and Apache versions supported in CTM R7.2.

Table 3 CTM-Supported JRE Version

JRE Version

Caveat ID

Caveat

Comment

1.4.2.11

—

—

This JRE version was used when CTM R7.2 was released.

Table 4 CTM-Supported Apache Version

Apache Version

Caveat ID

Caveat

Comment

2.0.43

—

—

This Apache version was used when CTM R7.2 was released.

Resolved Caveats

The following table lists caveats that are resolved in CTM R7.2.
Table 5 Caveats Resolved in CTM R7.2
Caveat ID

Caveat

CSCsb46479

When data communications channel (DCC) links are deleted, CTM does not display patchcord links between the same nodes.

CSCsc72571

Cannot sort columns displaying an orange triangle icon in the L2 Service Drops table.

CSCsc85014

All types of circuits sourced from, terminating on, or traversing an ONS 15600 SONET R5.0.x or R6.x NE enter the CONVERSION_PENDING state.

Related caveat ID: CSCsc02877.

CSCsc88798

Historical performance monitoring (PM) parameters show N/A for the far-end E1 interface on all cards.

CSCsd06568

Cannot activate an existing image on a device in the Cisco 7600 Flash File table.

CSCsd16911

The UAS-V PM counter value does not increment for ports 50 to 56 in a DS1_E1_56 card.

CSCsd19127

Units are not handled correctly in the Quality of Service (QoS) application for Cisco IOS XR-based NE types when configuration is performed outside of the CTM GUI; for example, with the command-line interface (CLI).

CSCsd19469

Under some conditions, the NE Explorer GUI becomes unresponsive for more than 10 seconds. This problem occurs on applications that involve collection and display of data from the NE. An example is the Configuration > Policy > Packet Filter application. When the buttons adjacent to the inbound/outbound fields are clicked, processing delays occur when access control list (ACL) information is collected from the router.

CSCsd22467

The Server Monitor table sometimes shows incorrect values for the NE sync time.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsd26526

The CTM user interface does not distinguish between preconfigured and configured interfaces when managing Cisco IOS XR-based NE types. Both are displayed as if they were actually present and operational on the managed NE.

CSCsd33485

In Australian time zones, the CTM application clock returns one hour less than the system time from 3:00 a.m. on March 26, 2006 to 3:00 a.m. on April 2, 2006.

CSCsd37232

The CTM GateWay/CORBA process crashes due to Java Virtual Machine (JVM) error ID 434F444523414348450E43505000CF 01.

CSCsd37522

When you try to launch the NE Explorer by double-clicking a gateway network element (GNE) node, an error message is returned.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsd52570

In the QoS application, clearing the inbound or outbound service policy for an interface removes that interface from the application and prevents additional operations. This problem occurs in the Configuration > Policy > QoS application > Service Policies tab. If you clear either the inbound or outbound service policy and then click OK or Apply, the interface is removed after a refresh operation. The correct behavior is for the interface to remain in the user interface to permit additional operations.

CSCsd53793

The CTM GateWay/CORBA getTCATPParams command does not show PMP_OFS values for STM-1 cards on ONS 15454 SDH NEs.

CSCsd54564

The CTM GateWay/CORBA getAllL2Topologies interface returns invalid values of numberOfVcatMembers.

CSCsd54959

The getTCATPParameter command fails for DS1 cards on ONS 15454 SONET NEs.

CSCsd55147

The getTCATPParams command on STM-1E_12 for multiplex section (MS) does not show PMP_EB at the far end on ONS 15454 SDH NEs.

CSCsd55421

The 1+1 protection status is not reported correctly on STM-1-1-8-LC and STM-1-S1-1-LCE1-21 cards.

CSCsd56092

Marking the NEs as Out of Service and then In Service shuts down the ML card PoS ports. This affects traffic passing through the ML card. Traffic still goes through in wrap state, but does not pass through the newly added ML card.

CSCsd57049

The 15-minute Low Order PM table hangs while trying to retrieve data.

CSCsd60766

Latitude and longitude values are shown as null in the NE Explorer. If you try to change a null value, a warning message is returned and the new value is not set.

CSCsd84295

Frequently opening and closing the NE Explorer for Cisco IOS XR NEs slows down the CTM client.

CSCsd89188

If you select a rack, slot, card, or interface on a Cisco 7609 and then launch the Alarm Log or the Alarm Browser, all active alarms on the NE are visible.

CSCsd89800

CTM GateWay/CORBA reports the wrong circuit direction for OCHNC circuits on release 7.x and 8.x NEs. The circuit direction should be CD_UNI or CD_BIDI, but CTM GateWay/CORBA reports east-to-west or west-to-east.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsd93772

Cisco 7600 NEs remain in sync-configuration state for a long time.

CSCsd93868

Cannot display 24-hour PM data for ONS 155xx NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.
CSCsd94868
While installing the CTM R7.1 server, if you check the Install CiscoView Server check box, you receive the following prompt:

CiscoView installation has been moved to CTM Server Disk 3. After CTM server has been installed, insert the CTM Server Disk 3 and run the './installCiscoView.sh' script.
This prompt is incorrect because the CiscoView installation is located on disk 4, not disk 3.
CSCse08931

When the user is forced by the system administrator to change the password at login, the complexity checking of the password does not include the comparison against the previous n passwords, where n is a number defined in the Control Panel.

CSCse18924

After migrating data from CTM R5.0.2 to CTM R7.0, you cannot enable the Control Panel > Logging Properties pane > Enable Initialization Log feature.

CSCse19117

Automatic refresh does not work after deleting a Layer 2 (L2) topology or L2 service. Entries in the L2 Topology and L2 Service tables remain unchanged even after enabling automatic refresh.

CSCse22933

After migrating data from CTM R5.0.2 to CTM R7.0, some new CTM R7.0 parameters are missing from the ctm_config_table.

CSCse25745

The creation of a 1:1 protection group fails with a server-side exception.

Related caveat ID: CSCse57789.

CSCse29655

When you change the IP address of a node in CTC, CTM receives the update and displays the new IP address. Afterwards, the IP address changes back to the old IP address.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCse47060

When creating patchcords on an MXPP_MR_2.5G card, CTM shows the inventory as 2.5G_DMP but the drop ports are not displayed.

CSCse52685

Cannot create VT circuits via CTM on DS1 ports of a CTX card on the ONS 15310 CL R6.0.

Related caveat IDs: CSCse75211, CSCse72642.

CSCse55887

DWDM optical link creation fails if the bidirectional option is selected.

CSCse61127

For the ONS 15216 EDFA2, the NE alarm time is incorrect in the Alarm Browser and Alarm Log.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCse72619

It takes approximately 2.5 minutes to open the Control Panel window.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCse75838

Statistics data is not collected for MGX MPSE 16 T1E1 PhysLine E1/T1.

CSCse77091

CTM R7.0 does not allow the creation of a VT1 from an ONS 15327 to an ONS 15454 through an ONS 15600 using VT tunnels.

CSCse79009

"Audit Log 100 Percent Full" alarms are not cleared for NE releases earlier than 6.0.

CSCse87371

If you try to enable CoS accounting on ONS 15454 SONET R4.1 NEs, you receive a warning message that CoS accounting is not supported on the NE, which is the correct behavior. However, you can enable CoS accounting on ONS 15454 SDH R4.1 NEs, even though ML cards do not support CoS accounting for the ONS 15454 SDH R4.1.

CSCse94192

While adding NE defaults from one NE to another, an IDL/config exception is generated.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCse98144

You cannot connect to the CTM GateWay/CORBA service because it does not pick up the specified notification port. Instead, the CTM GateWay/CORBA service randomly picks up another port to connect.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCse99051

After rearranging the default network view and saving the configuration, you must rearrange nodes in the network view every time you create a manual circuit.

Related caveat ID: CSCse72649.

CSCsf09055

The Alarm Browser lists incorrect Connection Admission Control (CAC) alarms for VXSM cards.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf10637

The maximum size of the CTM client debug file is 1 MB and it does not change even after modifying its value in the Debug Options dialog box.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf12019

While creating manual circuits using textual routing and fully protected paths, the current NE does not change when you click the Alternate Route button. A stack trace shows a null pointer exception.

CSCsf12195

Connection termination point (CTP) naming differs from what is reported in the Cisco Transport Manager Release 7.2 GateWay/CORBA User Guide and Programmer Manual. For STS-1 CTPs, values for k > 3 are shown in all application program interfaces (APIs) that contain CTPs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf19350

During L2 topology creation, when you select manual provisioning for the first circuit in the RPR Circuit Segment Details screen, the Textual and Graphical Routing Preferences screen appears. If you select the textual option, the manual provisioning screen with textual options appears. However, even if you select graphical routing for the second circuit, the textual selection screen appears.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf19399

During an Add/Remove Card operation, when the circuit name contains 30 characters, an EID-927 error occurs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf22050

When one of the L2 topologies is in Sync Failed state, getAllL2Topologies returns nothing. It should return all remaining L2 topologies.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsf27109

The getAllSubnetworkConnections method takes a lot of time to respond. Once the subnetwork size increases to a significant level and the Circuit table and Circuit CTP table contain more than 200,000 records, getAllSubnetworkConnections runs a couple of SQL queries on the tables to get the required data. Database queries take time to execute because there is a huge amount of data, resulting in the performance degradation of the API.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg04592

The CTM client exits if you enter the wrong login password in the CTM Locked dialog box.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg11372

Cannot apply saved defaults to other NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg13534

Some 15-minute and 1-day historical PM tables are empty for ONS 15454 SDH and ONS 15454 MSTP NEs.

Related caveat ID: CSCsk19435.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg13574

Cannot schedule an automatic backup for all NE models.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg35907

Cannot clear the Max Login Attempts Exceeded alarm for an unknown user.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg50040

For NE R7.0 and R7.2, the "Audit log 100 percent full" alarm does not get cleared from the Alarm Browser.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg72820

Cannot set the Admin SSM value for MRC_12 cards.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg74859

Cannot change the alarm profile severity for SNTP-HOST.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg84278

There is a long delay in publishing the NT_OBJECT_CREATION event from the CTM GateWay/CORBA interface in CTM R7.0 and CTM R7.2. In earlier CTM releases, the same event took only 4 seconds to publish.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsg86303

When an advanced QoS profile is applied to a drop, the QoS profile name becomes Custom_QoS after the resync period.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh06817

The "Maximum login attempts exceeded" alarm is not cleared after unchecking the Infinite check box in the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh18844

One of the following occurs if an advanced QoS profile is applied to a drop that does not have a QoS profile or a drop that has an existing profile that the QoS does not recognize:

•A Java error.

•The QoS policy is applied to the drop in incorrect order.

•The QoS policy is applied to the drop twice.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh20547

Create a VLAN on a topology and then add QoS profiles to a drop. The QoS profiles are added but displayed in incorrect order. They are sorted based on the Match Any field values.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh22076

A traffic loss of 15 seconds occurs through a VLAN created on a Resilient Packet Ring (RPR) Layer 2 topology.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh26353

CTM does not show the PLM - Payload Mismatch alarm on ONS 15305 CTC NEs. The same alarm is visible in CTC and Cisco Edge Craft.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh30264

The Circuit table shows the incorrect service state (OOS or OOS Partial) for OCHNC circuits. It also occasionally shows the incorrect service state for SONET and SDH circuits.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh42924

Create a topology. While modifying the topology, change the CoS value and then the corresponding bandwidth. The CoS value is reset to the default value.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh45398

The TCA_EVENT_TABLE is not pruned and grows to millions of rows. The huge number of rows causes high CPU usage and performance degradation.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh46229

PM data collection takes longer than 15 minutes, resulting in high CPU usage.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh46264

The Probable Cause field in the CORBA NT_ALARM contains trailing white spaces.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh49737

The PPM holder information is missing from the EquipmentHolder field for alarms raised on PPM holders in MRC cards.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh55478

Acknowledging alarms takes a long time or even freezes the GUI.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh57128

The Affected Object field of the "Maximum login attempts exceeded" alarm does not show the IP address of the client workstation where the login was attempted.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh66027

The port information for threshold crossing alert (TCA) events that are generated on DS3 cards is wrong.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh66116

CTM GateWay/TL1 stops responding and exhibits loss of connectivity when more than 1000 nodes are added. No commands can be entered and no alarms or events are reported.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh66120

CTM GateWay/TL1 crashes with a core dump when the CTM domain contains 1200 or more nodes.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh72631

In a scalability setup with approximately 3000 nodes, CTM GateWay/TL1 does not respond to commands with the CTM domain as the target ID (TID). The commands with the node as the TID work correctly. For example, CTM GateWay/TL1 does not respond to the rtrv-ne-ems:CTM::23 command.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh74488

The CTM GateWay/CORBA service does not start when you launch it using the CTM client or CLI.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh77677

Custom QoS profile information is lost after some time.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh79249

The oraclesw9i/admin/udump directory contains a prune_pm.err error log file that reports the following error message: "ORA-14083: Cannot drop the only partition of a partitioned table."

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh86966

The Circuit table does not refresh automatically after enabling the auto refresh feature.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh92123

When you perform a lot of manual alarm acknowledgement, the size of the ACK_TABLE increases. When this happens, it takes too long to show alarms in the Alarm Browser and to manually acknowledge selected alarms.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh92692

CTM GateWay/TL1 core dumps occur on the network.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh94186

The confirmation dialog box is not displayed after uploading a configuration file to a TCC card.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh98865

The following alarms are shown incorrectly in the Alarm Browser:

•LAN Connection Polarity Reversed

•Loss of Channel

•FEC Mismatch

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsh99664

CTM GateWay/TL1 does not manage ONS 15454 R4.0.3 NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi03340

All NEs in a GNE/end network element (ENE) ring are shown as ENEs. The GNEs are also shows as ENEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi05508

When you use the RTRV-ALM-ALL command to retrieve ONS 1580x NE alarms, the alarms do not contain the rack, subrack, slot, and card information.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi05518

CTM GateWay/TL1 temporarily stops forwarding events to the OSS.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi06828

The pruning operation on an ONS 15454 SDH audit trail parameter does not work correctly.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi08236

CTM GateWay/TL1 logs wrap quickly, meaning important information is lost and debugging becomes difficult.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.
CSCsi12991
CTM GateWay/TL1 returns a DENY to any command, indicating that the NEs are not connected and the login failed:
M  c04 DENY
  PIUI
  "Privilege, Illegal User Identity"
  /*Gateway Login To NE Failed */
Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.
CSCsi20156

CTM GateWay/TL1 crashes randomly when it is stopped from the Control Panel while it is processing a command or sending responses to the OSS client.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi25592

The Alarm Browser does not display any alarms raised on an ONS 15216 EDFA3 NE due to changes in threshold or alarm behavior severities. Only old alarms are visible in the Alarm Browser.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi25978

An unsupported NE version is seen in the Supported NE table.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi26713

NEs are added successfully but do not appear in the Domain Explorer and cannot be located with the Find feature.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi29165

After creating a QoS profile, the class order changes.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi29816

The SNMP and Alarm Behavior tables are empty for ONS 15216 EDFA3 NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi34127

When a POS port is disabled in one of the member cards of a topology, an alarm is generated on the NE that contains the card. But the object is shown as Bad Physical Location.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi55194

Cannot perform read/write operations for reach and wavelength parameters on MRC_12 cards on ONS 15454 SONET NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi56733

Cannot download the NE defaults file if it was saved previously on the CTM server.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi59605

The Equipment Inventory table shows a single row marked as Chassis after removing and reinserting a fan tray. It does not show the fan tray or fan slot.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi75389

The get/setTCA API fails for near- and far-end STM-1 path thresholds on MRC_12 cards.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi75723

The Circuit table does not display the port name for DS3E, DS3XM, and DS3XM_12 cards.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsi97803

When you log into CTM as an Operator, Provisioner, Network Admin, or SysAdmin user, the number of alarms shown on the Dashboard is inconsistent with the number of alarms reported by the Alarm Browser.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj05733

Domain Manager Mode (DMM) commands like rtrv-alm-all, rtrv-alm-ems, rtrv-ne-ems, and rtrv-subntwrk-ems are truncated to 20 rows, which results to missing information. The output is incomplete and an error message is displayed.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj07316

Cannot set the Admin SSM value for the MRC_12 cards on R6.x NEs.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj17920

Cannot set the Protection Switching Count (PSC) and Protection Switching Duration (PSD) threshold values on ONS 15454 SONET NEs.

CSCsj19520

The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service or CTM server is restarted.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj51055

After applying customized settings on an ML card, you cannot change the QoS profile on a VLAN drop port.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj52259

After a CTM server restart, the Alarm Browser reports a loss of communication between CTM and ONS 15305 NEs. The NEs are stuck in Initialization Failed state with an incorrect username/password error.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj57699

The Alarm Browser shows no alarms for NEs, even though the NE icons in the Domain Explorer tree indicate alarms, and CTC shows alarms.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj62479

The Error Log reports the following invalid error message for the MS-ISC card: "EID-6059: ML Card resync failure for NE: <NE_ID> - slot: 6 - Reason: IOS Config is empty and/or not found."

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj70432

The CTM server overwrites the most recent log files in the archive log directory.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj80112

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.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsj83214

The Circuit table displays TL1 circuits incorrectly.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk20958

CTM GateWay/CORBA APIs return an exception with the following error reason: "The srcNodeId is null for the circuit with nodeId <node_ID>."

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk21490

CTM GateWay/CORBA APIs return an exception with the following error reason: "Failed to get containing equipment for a PTP."

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk26507

When installing a patch earlier than CTM R7.2.0.221.2, many messages appear on screen, including messages that seem like errors.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk28871

The /db05 partition is 100 percent full and the CTM server shuts down automatically.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk30176

PM data is not collected in a GNE-ENE setup.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk52028

If you launch the NE Explorer for an ONS 15454 SONET or ONS 15454 SDH with AIC or AICI cards, click the card, click Alarm Extenders, and try to set the alarm type, the operation fails with an error message.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk84130

Upgrading to CTM R8.0 fails after installing the CTM R7.2.0.199.1 patch or later.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk84731

The getCTMHistoryPMData API does not return any CTP data when used on a managed element.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsk90404

The following messages—which do not indicate an error condition—are shown incorrectly in the Error Log with a severity level of Major instead of Debug:

•Socket blocked for writing: <number>, user <user>

•Zero events in the queue, removing the queue

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsl09775

NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsl34139

The MGX NE service does not start automatically even if some MGX NEs are present in the network. The MGX NEs are connected but cannot be managed.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsm37071

Implementation Repository (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.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsl47537

PM pruning fails.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsm46882

Cannot view server trails in CTM.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsm84722

Cannot install CTM patches in a dual-server setup.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsm99421

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.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCso06978

The following error message appears after clicking the Upload Log Files button in the Control Panel > Logging Properties > General tab: "Error reading Configuration Properties from Server..."

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCso51648

The NE Explorer does not display all protection groups. The same protection groups that are missing from CTM are visible in CTC.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsq94272

You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsr60497

When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

CSCsw88229

When you start the CTM client in Debug mode and then choose Administration > Memory Backup, the client hangs and an error message appears in the console window where you entered the ./ctmcdebug-start command.

Note This caveat is fixed with the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.
Installing the CTM R7.2.0.230.1 Patch

Note The CTM R7.2.0.230.1 patch inherits all bug fixes and obsoletes all earlier CTM R7.2 patches and service packs.

This section describes how to download and install the CTM R7.2.0.230.1 patch. This patch contains new fixes for the following caveats:

•CSCsq94272: You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.

•CSCsw88229: When you start the CTM client in Debug mode and then choose Administration > Memory Backup, the client hangs and an error message appears in the console window where you entered the ./ctmcdebug-start command.

This patch also inherits fixes of all earlier CTM R7.2 patches and service packs for the following caveats:

•CSCsd22467: The Server Monitor table sometimes shows incorrect values for the NE sync time.

•CSCsd37522: When you try to launch the NE Explorer by double-clicking a GNE node, an error message is returned.

•CSCsd89800: CTM GateWay/CORBA reports the wrong circuit direction for OCHNC circuits on release 7.x and 8.x NEs. The circuit direction should be CD_UNI or CD_BIDI, but CTM GateWay/CORBA reports east-to-west or west-to-east.

•CSCsd93868: Cannot display 24-hour PM data for ONS 155xx NEs.

•CSCse29655: When you change the IP address of a node in CTC, CTM receives the update and displays the new IP address. Afterwards, the IP address changes back to the old IP address.

•CSCse61127: For the ONS 15216 EDFA2, the NE alarm time is incorrect in the Alarm Browser and Alarm Log.

•CSCse72619: It takes approximately 2.5 minutes to open the Control Panel window.

•CSCse94192: While adding NE defaults from one NE to another, an IDL/config exception is generated.

•CSCse98144: You cannot connect to the CTM GateWay/CORBA service because it does not pick up the specified notification port. Instead, the CTM GateWay/CORBA service randomly picks up another port to connect.

•CSCsf09055: The Alarm Browser lists incorrect CAC alarms for VXSM cards.

•CSCsf10637: The maximum size of the CTM client debug file is 1 MB and it does not change even after modifying its value in the Debug Options dialog box.

•CSCsf12195: CTP naming differs from what is reported in the Cisco Transport Manager Release 7.2 GateWay/CORBA User Guide and Programmer Manual. For STS-1 CTPs, values for k > 3 are shown in all APIs that contain CTPs.

•CSCsf19350: During L2 topology creation, when you select manual provisioning for the first circuit in the RPR Circuit Segment Details screen, the Textual and Graphical Routing Preferences screen appears. If you select the textual option, the manual provisioning screen with textual options appears. However, even if you select graphical routing for the second circuit, the textual selection screen appears.

•CSCsf19399: During an Add/Remove Card operation, when the circuit name contains 30 characters, an EID-927 error occurs.

•CSCsf22050: When one of the L2 topologies is in Sync Failed state, getAllL2Topologies returns nothing. It should return all remaining L2 topologies.

•CSCsf27109: The getAllSubnetworkConnections method takes a lot of time to respond. Once the subnetwork size increases to a significant level and the Circuit table and Circuit CTP table contain more than 200,000 records, getAllSubnetworkConnections runs a couple of SQL queries on the tables to get the required data. Database queries take time to execute because there is a huge amount of data, resulting in the performance degradation of the API.

•CSCsg04592: The CTM client exits if you enter the wrong login password in the CTM Locked dialog box.

•CSCsg11372: Cannot apply saved defaults to other NEs.

•CSCsg13534: Some 15-minute and 1-day historical PM tables are empty for ONS 15454 SDH and ONS 15454 MSTP NEs. (Related caveat ID: CSCsk19435)

•CSCsg13574: Cannot schedule an automatic backup for all NE models.

•CSCsg35907: Cannot clear the Max Login Attempts Exceeded alarm for an unknown user.

•CSCsg50040: For NE R7.0 and R7.2, the "Audit log 100 percent full" alarm does not get cleared from the Alarm Browser.

•CSCsg72820: Cannot set the Admin SSM value for MRC_12 cards.

•CSCsg74859: Cannot change the alarm profile severity for SNTP-HOST.

•CSCsg84278: There is a long delay in publishing the NT_OBJECT_CREATION event from the CTM GateWay/CORBA interface in CTM R7.0 and CTM R7.2. In earlier CTM releases, the same event took only 4 seconds to publish.

•CSCsg86303: When an advanced QoS profile is applied to a drop, the QoS profile name becomes Custom_QoS after the resync period.

•CSCsh06817: The "Maximum login attempts exceeded" alarm is not cleared after unchecking the Infinite check box in the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area.

•CSCsh18844: One of the following occurs if an advanced QoS profile is applied to a drop that does not have a QoS profile or a drop that has an existing profile that the QoS does not recognize:

–A Java error.

–The QoS policy is applied to the drop in incorrect order.

–The QoS policy is applied to the drop twice.

•CSCsh20547: Create a VLAN on a topology and then add QoS profiles to a drop. The QoS profiles are added but displayed in incorrect order. They are sorted based on the Match Any field values.

•CSCsh22076: A traffic loss of 15 seconds occurs through a VLAN created on an RPR Layer 2 topology.

•CSCsh26353: CTM does not show the PLM - Payload Mismatch alarm on ONS 15305 CTC NEs. The same alarm is visible in CTC and Cisco Edge Craft.

•CSCsh30264: The Circuit table shows the incorrect service state (OOS or OOS Partial) for OCHNC circuits. It also occasionally shows the incorrect service state for SONET and SDH circuits.

•CSCsh42924: Create a topology. While modifying the topology, change the CoS value and then the corresponding bandwidth. The CoS value is reset to the default value.

•CSCsh45398: The TCA_EVENT_TABLE is not pruned and grows to millions of rows. The huge number of rows causes high CPU usage and performance degradation.

•CSCsh46229: PM data collection takes longer than 15 minutes, resulting in high CPU usage.

•CSCsh46264: The Probable Cause field in the CORBA NT_ALARM contains trailing white spaces.

•CSCsh49737: The PPM holder information is missing from the EquipmentHolder field for alarms raised on PPM holders in MRC cards.

•CSCsh55478: Acknowledging alarms takes a long time or even freezes the GUI.

•CSCsh57128: The Affected Object field of the "Maximum login attempts exceeded" alarm does not show the IP address of the client workstation where the login was attempted.

•CSCsh66027: The port information for TCA events that are generated on DS3 cards is wrong.

•CSCsh66116: CTM GateWay/TL1 stops responding and exhibits loss of connectivity when more than 1000 nodes are added. No commands can be entered and no alarms or events are reported.

•CSCsh66120: CTM GateWay/TL1 crashes with a core dump when the CTM domain contains 1200 or more nodes.

•CSCsh72631: In a scalability setup with approximately 3000 nodes, CTM GateWay/TL1 does not respond to commands with the CTM domain as the TID. The commands with the node as the TID work correctly. For example, CTM GateWay/TL1 does not respond to the rtrv-ne-ems:CTM::23 command.

•CSCsh74488: The CTM GateWay/CORBA service does not start when you launch it using the CTM client or CLI.

•CSCsh77677: Custom QoS profile information is lost after some time.

•CSCsh79249: The oraclesw9i/admin/udump directory contains a prune_pm.err error log file that reports the following error message: "ORA-14083: Cannot drop the only partition of a partitioned table."

•CSCsh86966: The Circuit table does not refresh automatically after enabling the auto refresh feature.

•CSCsh92123: When you perform a lot of manual alarm acknowledgement, the size of the ACK_TABLE increases. When this happens, it takes too long to show alarms in the Alarm Browser and to manually acknowledge selected alarms.

•CSCsh92692: CTM GateWay/TL1 core dumps occur on the network.

•CSCsh94186: The confirmation dialog box is not displayed after uploading a configuration file to a TCC card.

•CSCsh98865: The following alarms are shown incorrectly in the Alarm Browser:

–LAN Connection Polarity Reversed

–Loss of Channel

–FEC Mismatch

•CSCsh99664: CTM GateWay/TL1 does not manage ONS 15454 R4.0.3 NEs.

•CSCsi03340: All NEs in a GNE/ENE ring are shown as ENEs. The GNEs are also shown as ENEs.

•CSCsi05508: When you use the RTRV-ALM-ALL command to retrieve ONS 1580x NE alarms, the alarms do not contain the rack, subrack, slot, and card information.

•CSCsi05518: CTM GateWay/TL1 temporarily stops forwarding events to the OSS.

•CSCsi06828: The pruning operation on an ONS 15454 SDH audit trail parameter does not work correctly.

•CSCsi08236: CTM GateWay/TL1 logs wrap quickly, meaning important information is lost and debugging becomes difficult.

•CSCsi12991: CTM GateWay/TL1 returns a DENY to any command, indicating that the NEs are not connected and the login failed:
M  c04 DENY
  PIUI
  "Privilege, Illegal User Identity"
  /*Gateway Login To NE Failed */
•CSCsi20156: CTM GateWay/TL1 crashes randomly when it is stopped from the Control Panel while it is processing a command or sending responses to the OSS client.

•CSCsi25592: The Alarm Browser does not display any alarms raised on an ONS 15216 EDFA3 NE due to changes in threshold or alarm behavior severities. Only old alarms are visible in the Alarm Browser.

•CSCsi25978: An unsupported NE version is seen in the Supported NE table.

•CSCsi26713: NEs are added successfully but do not appear in the Domain Explorer and cannot be located with the Find feature.

•CSCsi29165: After creating a QoS profile, the class order changes.

•CSCsi29816: The SNMP and Alarm Behavior tables are empty for ONS 15216 EDFA3 NEs.

•CSCsi34127: When a POS port is disabled in one of the member cards of a topology, an alarm is generated on the NE that contains the card. But the object is shown as Bad Physical Location.

•CSCsi55194: Cannot perform read/write operations for reach and wavelength parameters on MRC_12 cards on ONS 15454 SONET NEs.

•CSCsi56733: Cannot download the NE defaults file if it was saved previously on the CTM server.

•CSCsi59605: The Equipment Inventory table shows a single row marked as Chassis after removing and reinserting a fan tray. It does not show the fan tray or fan slot.

•CSCsi75389: The get/setTCA API fails for near- and far-end STM-1 path thresholds on MRC_12 cards.

•CSCsi75723: The Circuit table does not display the port name for DS3E, DS3XM, and DS3XM_12 cards.

•CSCsi97803: When you log into CTM as an Operator, Provisioner, Network Admin, or SysAdmin user, the number of alarms shown on the Dashboard is inconsistent with the number of alarms reported by the Alarm Browser.

•CSCsj05733: DMM commands like rtrv-alm-all, rtrv-alm-ems, rtrv-ne-ems, and rtrv-subntwrk-ems are truncated to 20 rows, which results to missing information. The output is incomplete and an error message is displayed.

•CSCsj07316: Cannot set the Admin SSM value for the MRC_12 cards on R6.x NEs.

•CSCsj19520: The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service or CTM server is restarted.

•CSCsj51055: After applying customized settings on an ML card, you cannot change the QoS profile on a VLAN drop port.

•CSCsj52259: After a CTM server restart, the Alarm Browser reports a loss of communication between CTM and ONS 15305 NEs. The NEs are stuck in Initialization Failed state with an incorrect username/password error.

•CSCsj57699: The Alarm Browser shows no alarms for NEs, even though the NE icons in the Domain Explorer tree indicate alarms, and CTC shows alarms.

•CSCsj62479: The Error Log reports the following invalid error message for the MS-ISC card: "EID-6059: ML Card resync failure for NE: <NE_ID> - slot: 6 - Reason: IOS Config is empty and/or not found."

•CSCsj70432: The CTM server overwrites the most recent log files in the archive log directory.

•CSCsj80112: 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.

•CSCsj83214: The Circuit table displays TL1 circuits incorrectly.

•CSCsk20958: CTM GateWay/CORBA APIs return an exception with the following error reason: "The srcNodeId is null for the circuit with nodeId <node_ID>."

•CSCsk21490: CTM GateWay/CORBA APIs return an exception with the following error reason: "Failed to get containing equipment for a PTP."

•CSCsk26507: When installing a patch earlier than CTM R7.2.0.221.2, many messages appear on screen, including messages that seem like errors.

•CSCsk28871: The /db05 partition is 100 percent full and the CTM server shuts down automatically.

•CSCsk30176: PM data is not collected in a GNE-ENE setup.

•CSCsk52028: If you launch the NE Explorer for an ONS 15454 SONET or ONS 15454 SDH with AIC or AICI cards, click the card, click Alarm Extenders, and try to set the alarm type, the operation fails with an error message.

•CSCsk84130: Upgrading to CTM R8.0 fails after installing the CTM R7.2.0.199.1 patch or later.

•CSCsk84731: The getCTMHistoryPMData API does not return any CTP data when used on a managed element.

•CSCsk90404: The following messages—which do not indicate an error condition—are shown incorrectly in the Error Log with a severity level of Major instead of Debug:

–Socket blocked for writing: <number>, user <user>

–Zero events in the queue, removing the queue

•CSCsl09775: NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.

•CSCsl34139: The MGX NE service does not start automatically even if some MGX NEs are present in the network. The MGX NEs are connected but cannot be managed.

•CSCsl47537: PM pruning fails.

•CSCsm37071: 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.

•CSCsm46882: Cannot view server trails in CTM.

•CSCsm84722: Cannot install CTM patches in a dual-server setup.

•CSCsm99421: 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.

•CSCso06978: The following error message appears after clicking the Upload Log Files button in the Control Panel > Logging Properties > General tab: "Error reading Configuration Properties from Server..."

•CSCso51648: The NE Explorer does not display all protection groups. The same protection groups that are missing from CTM are visible in CTC.

•CSCsr60497: When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.

CTM R7.2.0.230.1 is intended for customers who are currently using CTM R7.2.0.191.1, R7.2.0.195.1, R7.2.0.199.1, R7.2.0.205.2, R7.2.0.207.1, R7.2.0.208.1, 7.2.0.215.2, R7.2.0.221.2, or R7.2.0.224.2.

Note Install the CTM R7.2.0.230.1 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 R7.2.0.230.1 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: 7.2 Build: 191

•Cisco Transport Manager Server Version: 7.2 Build: 195 Patches: 1

•Cisco Transport Manager Server Version: 7.2 Build: 199 Patches: 1

•Cisco Transport Manager Server Version: 7.2 Build: 205 Patches: 2

•Cisco Transport Manager Server Version: 7.2 Build: 207 Patches: 1

•Cisco Transport Manager Server Version: 7.2 Build: 208 Patches: 1

•Cisco Transport Manager Server Version: 7.2 Build: 215 Patches: 2

•Cisco Transport Manager Server Version: 7.2 Build: 221 Patches: 2

•Cisco Transport Manager Server Version: 7.2 Build: 224 Patches: 2

Backing Up the CTM Database Before Installing the CTM R7.2.0.230.1 Patch

Before installing the CTM R7.2.0.230.1 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 7.2 User Guide:

•Backing Up the CTM Database from the CTM GUI

•Backing Up the CTM Database from the CLI

Downloading the CTM R7.2.0.230.1 Patch

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

Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In.

Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.

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

Step 4 Click Cisco Transport Manager 7.2.

Step 5 At the Select a Software Type screen, click Transport Manager (CTM) Patches.

Step 6 At the Select a Release screen, click Expand all; then, click 7.2.0.230.1.

Step 7 In the right pane, click CTM7.2.0.230.1.patch.zip.

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 CTM7.2.0.230.1.patch.zip file to a temporary directory (such as /temp) on the CTM server.

Step 11 In Solaris, enter the following commands to extract the .zip file to the temporary directory:
cd /<directory_name>
unzip CTM7.2.0.230.1.patch.zip
For example, to extract the .zip file to the /temp directory, enter:
cd /temp
unzip CTM7.2.0.230.1.patch.zip
Step 12 This creates a directory called 230, which contains all of the patch-related files. Enter the following command to enter the directory:
cd 230
Step 13 In Windows, download the CTM7.2.0.230.1.patch.zip file to the client workstation. Extract the file using a tool such as WinZip, as follows:

a. Open the CTM7.2.0.230.1.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 R7.2.0.230.1 Server Patch on the Same or Separate Workstation(s)

Step 1 (For a dual-server setup only; if yours is a single-server setup, skip to the next step.) If you are installing the CTM R7.2.0.230.1 server patch in a configuration where the CTM server and database are on separate workstations, you must enable the remote shell (rsh) on the server in order to install the CTM R7.2.0.230.1 patch 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 230 directory where the patch was extracted:
./server_patch.sh
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 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: 7.2 Build: 230 Patches: 1
Installing the CTM R7.2.0.230.1 Client Patch 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 230 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 R7.2 desktop icon or choose the CTM R7.2 Start menu shortcut to start the client.

Step 4 To verify the patch installation on the CTM client, do one of the following:

•Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version string in the About Cisco Transport Manager dialog box; then, click OK:
Client: 7.2 Build: 230 (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:
7.2 [7.2.0.230]
Installing the CTM R7.2.0.230.1 Client Patch 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 230 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: 7.2 Build: 230 (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:
7.2 [7.2.0.230]
Open Caveats

The following sections describe the caveats that are not resolved in the CTM R7.2 software:

•Installation and Upgrade Caveats

•CTM Client Caveats

–Alarm Management

–Circuit and Link Management

–User Management

–Data Services

–Domain Explorer

–NE Explorer

–Network Map

–Performance Monitoring

–Control Panel

–Miscellaneous

•CTM Server Caveats

•Cisco Transport Controller Caveats

•High Availability Caveats

•CTM GateWay/TL1 Caveats

•CTM GateWay/CORBA Caveats

•NE-Specific Caveats

–Cisco 7600

–Cisco Catalyst 6509

–Cisco MGX Voice Gateway

–Cisco ONS 15216 EDFA

–Cisco ONS 15302 and Cisco ONS 15305

–Cisco ONS 15310

–Cisco ONS 15327 and Cisco ONS 15454 SONET

–Cisco ONS 15454 MSTP

–Cisco ONS 15501, Cisco ONS 15530, and Cisco ONS 15540

–Cisco ONS 15600 SONET and Cisco ONS 15600 SDH

–Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808

–Cisco CRS-1 and Cisco XR 12000

Installation and Upgrade Caveats

•CSCsd32439

Symptom    If you choose to upgrade from the existing release, the Previous button is dimmed.
Conditions   This problem occurs during upgrade.

Workaround   None.

•CSCsd52436

Symptom    After migrating from CTM R6.0 to CTM R7.0, R7.1, or R7.2, the valid links on ONS 15216 NEs become invalid.
Conditions   This problem occurs when the database is migrated and the CTM server is restarted. When you upgrade to a new CTM version, the CTM server is restarted. After migration, even after the NEs come up and the links become visible in the Link table, the links are marked as invalid.

Workaround   Delete and recreate the links on ONS 15216 NEs.

•CSCsd56923

Symptom    If you cancel the CTM upgrade after finishing all GUI selections and then retry the upgrade, a "Version not supported" error is returned.
Conditions   This problem applies only if you cancel the CTM upgrade after all GUI selections are complete.

Workaround   Before running the upgrade again, copy /opt/olddbinfo to /opt/newdbinfo.

•CSCse67644

Symptom    When the server is migrated from CTM R6.0 to CTM R7.2 and robust PM data collection is enabled on the NEs, data is lost for the migrated interval.
Conditions   This problem occurs when you enable robust PM data collection on any NE and then migrate the server from CTM R6.0 to CTM R7.2. Robust PM data is not collected for the migrated interval. The PM data buckets lost during the database migration cannot be retrieved.

Workaround   None.

•CSCsg79219

Symptom    When the CTM server is started with the ctms-start command, the add_log_partition.sh script returns an error that the CTM database cannot be found.
Conditions   This problem occurs when the CTM server and the CTM database are installed on separate workstations. This problem occurs because the installation scripts do not update the configuration files on the CTM server with the correct database system ID (SID) and IP address.

Workaround   After successfully installing the CTM server, edit the following files manually on the workstation where the CTM server is installed before starting the CTM server:

•/var/opt/oracle/oratab

This file does not contain the CTM database entry. Copy this entry from the /var/opt/oracle/oratab file on the workstation where the CTM database is installed.

•$ORACLE_HOME/network/admin/tnsnames.ora

This file does not contain the CTM database entry. As the oracle UNIX user, copy this entry from the tnsnames.ora file on the workstation where the CTM database is installed.

•/opt/CiscoTransportManagerServer/bin/add_log_partitions.sh

After the commands setting the ORACLE_HOME and TWO_TASK variables, insert the following commands:

–export ORACLE_HOME

–export TWO_TASK

•/opt/CiscoTransportManagerServer/cfg/CTMServer.cfg

Edit the following settings:

–db-link: Must contain a reference to the CTM database SID; for example, CTM.

–db-host: Must contain the IP address of the workstation where the CTM database is installed.

–db-location: Must contain the CTM database SID and the IP address of the workstation where the CTM database is installed.

•CSCsi88931

Symptom    After installing the CTM R7.0.0.370.1 patch or any later CTM R7.0 patch, an upgrade to CTM R7.2 or R8.0 fails.
Conditions   If you install the CTM R7.0.0.370.1 patch and then try to upgrade to CTM R7.2 or R8.0, the upgrade fails. This problem also applies to all later CTM R7.0 patches (R7.0.0.372.1, R7.0.0.375.1, R7.0.0.377.1, R7.0.0.382.1, R7.0.0.385.1, R7.0.0.389.1, R7.0.0.395.1, and R7.0.0.400.1). The root cause of this problem is that the CTM R7.0.0.370.1 patch adds data to the CTM database that is processed incorrectly by the CTM R7.2 or R8.0 upgrade procedure.

Workaround   For CTM R7.2, a patch is available to fix this problem. Contact your Cisco account representative to obtain the patch. For CTM R8.0, see the Release Notes for Cisco Transport Manager Release 8.0.

•CSCsk26507

Symptom    When installing a patch earlier than CTM R7.2.0.221.2, many messages appear on screen, including messages that seem like errors. For example:
Function created. No errors. Function created. No errors. Function created. No errors. 
Function created. No errors. Function created. No errors. Function created. No errors. 
Function created. 
No errors. Function created. No errors. create or replace TYPE link_id_tabtype is Table of 
number; 
<CTM_patch_number>.Readme.txt client client_patch.bat client_patch.sh config reg.exe 
server server_patch.sh sqlplus.out 
ERROR at line 1: ORA-02303: cannot drop or replace a type with type or table dependents 
create 
TYPE AlarmInfoType as OBJECT ( <CTM_patch_number>.Readme.txt client client_patch.bat 
client_patch.sh config reg.exe server 
server_patch.sh sqlplus.out ERROR at line 1: ORA-00955: name is already used by an 
existing object No errors. create TYPE 
AlarmInfoListType as table of AlarmInfoType; <CTM_patch_number>.Readme.txt client 
client_patch.bat client_patch.sh config 
reg.exe server server_patch.sh sqlplus.out ERROR at line 1: ORA-00955: name is already 
used by an existing object No errors. 
Package created. No errors. Package body created. No errors. Function created. No errors. 
Procedure created. No errors.
Conditions   This problem occurs when installing a patch earlier than CTM R7.2.0.221.2 on the CTM server.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsk84130

Symptom    Upgrading to CTM R8.0 fails after installing the CTM R7.2.0.199.1 patch or later.
Conditions   See Symptom.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsm46882

Symptom    Cannot view server trails in CTM.
Conditions   When you create a server trail in CTM or CTC after migrating from CTM R6.0 to CTM R7.0 or later, you cannot view the server trail in the CTM Link table.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch. Alternately, enter the following SQL commands:
ALTER TABLE LINK_TABLE MODIFY STNODEID NUMBER(10); 
ALTER TABLE LINK_TABLE MODIFY STUNIQUEID NUMBER(10);
•CSCsm84722

Symptom    Cannot install CTM patches in a dual-server setup.
Conditions   CTM patches do not support dual-server scenarios. Therefore, fixes cannot be applied to servers in a dual-server setup.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCso06978

Symptom    The following error message appears after clicking the Upload Log Files button in the Control Panel > Logging Properties > General tab: "Error reading Configuration Properties from Server..."
Conditions   This problem occurs when the CTM server is upgraded from CTM R7.0 to a later release.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch. Alternately, manually upload the log files from the CTM server to the CTM client using a file transfer protocol; for example, FTP or SFTP.

CTM Client Caveats

This section contains the following information:

•Alarm Management

•Circuit and Link Management

•User Management

•Data Services

•Domain Explorer

•NE Explorer

•Network Map

•Performance Monitoring

•Control Panel

•Miscellaneous

Alarm Management

•CSCec49029

Symptom    In the Alarm Browser, the module name "TCC" (Timing Communications and Control) is displayed regardless of the actual equipment type. For example, alarms reported on TCC, TCC1, and TCC2 cards all display "TCC" as the module name.
Conditions   TCC2 and TCC1 alarms display the module name as "TCC" in the Alarm Browser and Alarm Log.

Workaround   None.

•CSCeg14267 (Related caveat IDs: CSCef94105, CSCef89143)

Symptom    Link down alarms, syslog events, and configuration messages are not received for ML cards on ENEs behind the firewall when SNMP v2 is enabled.
Conditions   This problem occurs when you enable SNMP v2 for the CTM server trap destination on an ONS 15310 or ONS 15454 ENE behind the firewall. If the ENE contains ML cards and you generate a link down trap on one of the ports on the ML card, the Alarm Browser does not report the link down trap as an alarm. This problem applies to NE releases earlier than R5.0.

Workaround   Use SNMP v1 for ENEs behind the firewall if the CTM server is the trap destination.

•CSCin76849

Symptom    CTM and Cisco Transport Controller (CTC) do not show the actual equipment type for G1K-4 and TCC2 cards.
Conditions   See Symptom.

Workaround   None.

•CSCsb62632

Symptom    The Domain Explorer does not show the correct alarm status for MGX NEs. The Alarm Browser does not show connection-related alarms.
Conditions   This problem occurs when hundreds of MGX NEs are added in bulk, and each NE contains 1000 or more alarms. This problem also occurs when the CTM server is cold started and the server is managing hundreds of MGX NEs, each containing 1000 or more alarms.

Workaround   Launch the Configuration Center GUI and click the Connection tab to view connection-related alarms for MGX nodes.

•CSCsd49219

Symptom    A mismatch alarm is raised incorrectly from CTC and CTM.
Conditions   This problem occurs when you use CTM or CTC to preprovision an ONS 15305 card in an empty slot.

Workaround   To clear the alarm, physically insert the card in the slot.

•CSCsd67111

Symptom    The Alarm Log does not report syslog and configuration trap messages from ENEs in a GNE-ENE setup for SNMPv2. The Alarm Log shows trap messages only for GNEs.
Conditions   This problem is not observed with SNMPv1 if the ENEs use port 391 to send traps to GNEs. If ENEs use SNMPv1 with relay settings (port 162), traps are not shown in the Alarm Log.

Workaround   None.

•CSCse72287

Symptom    The Alarm Browser and Alarm Log do not display DBOSYNC alarms from ONS 15600 SONET R1.3.1 NEs.
Conditions   This problem occurs when an ONS 15600 SONET R1.3.1 sends a DBOSYNC alarm.

Workaround   To prevent CTM from discarding DBOSYNC alarms, use an SQL tool (such as SQL*Plus) to run the following SQL commands against the CTM database:
INSERT INTO ALARM_EVENT_TYPE_ENUM_TABLE VALUES (17214, 'Standby Database Out of Sync', 
'DBOSYNC', 'UNIDENTIFIED', 1);
commit;
•CSCse75608 (Related caveat ID: CSCsf17110)

Symptom    The Locate Alarm feature does not work for environmental alarms; it returns a "String not found" error.
Conditions   This problem applies to ONS 15310 MA NEs.

Workaround   None.

•CSCse75609

Symptom    The layer rate is shown as zero for alarms on the optical ports of ONS 15305 NEs.
Conditions   If you generate an alarm indication signal (AIS) alarm on an S4.1-2-LC module with multiplex section (MS) as the affected object, the getAllActiveAlarms API shows the layer rate as zero (0). Instead, it should show the layer rate for the S4.1-2-LC module. This problem applies to ONS 15305 NEs.

Workaround   None.

•CSCse75765

Symptom    The Alarm Browser does not display the port name for any alarms.
Conditions   If you mark card ports as In Service, and then a loss of signal (LOS) alarm is generated on the ports, in CTC the Alarm Location field shows the physical location as well as the port name. However, the CTM Alarm Browser does not show the port name information. The port name should be shown in the Physical Location field of the Alarm Browser, along with the actual physical location (such as slot and port).

Workaround   Refresh data from the NE. Alternately, mark the NE as Out of Service (in the Network Element Properties pane > Status tab > Operational State field) and click Save. Then, mark the NE as In Service and click Save.

•CSCse98401

Symptom    CTM does not show the "LP-UNEQ - SLMF-Unequipped Low Order - Path Unequipped" alarms on ONS 15305 CTC NEs. The same alarm is visible in CTC and Cisco Edge Craft.
Conditions   You can generate an LP-UNEQ alarm on the ONS 15305 using Cisco Edge Craft:

1. Connect to an ONS 15305 with 8*FE + SMAP installed.

2. Select one of the LAN x ports and set the layer to Layer 1. A VC group object is created under the LAN x port.

3. Select the VC group object and select the bandwidth.

4. Set AdminCapacity* to a value other than 0. An LP-UNEQ alarm is generated but is not visible in CTM.

Workaround   Use CTC or Cisco Edge Craft to view LP-UNEQ alarms.

•CSCsh57128

Symptom    The Affected Object field of the "Maximum login attempts exceeded" alarm does not show the IP address of the client workstation where the login was attempted.
Conditions   When an unknown user tries to log into the CTM server, the login is denied with an error message. When the maximum number of retries is exceeded, an alarm is generated. The Affected Object field of the alarm should report the IP address of the workstation where the login was attempted.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsi59605

Symptom    The Equipment Inventory table shows a single row marked as Chassis after removing and reinserting a fan tray. It does not show the fan tray or fan slot.
Conditions   This problem occurs when you change a chassis component; for example, removing and reinserting a fan tray.

Workaround   Complete one of the following workarounds:

•Refresh data from the NE.

•Mark the NE as Out of Service and then In Service.

•Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsi97803

Symptom    When you log into CTM as an Operator, Provisioner, Network Admin, or SysAdmin user, the number of alarms shown on the Dashboard is inconsistent with the number of alarms reported by the Alarm Browser.
Conditions   This discrepancy occurs when you log in as an Operator, Provisioner, Network Admin, or SysAdmin user.

Workaround   Log into CTM as a SuperUser. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsj62479

Symptom    The Error Log reports the following invalid error message for the MS-ISC card: "EID-6059: ML Card resync failure for NE: <NE_ID> - slot: 6 - Reason: IOS Config is empty and/or not found."
Conditions   When an MS-ISC card boots up in an ONS 15454 SONET MSTP multishelf NE, the Error Log reports the invalid error message that is shown in the Symptom. Despite the misleading error, the MS-ISC card boots correctly and functions normally.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsj80112

Symptom    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.
Conditions   With automatic alarm acknowledgement, the server should automatically acknowledge alarms when they are cleared and move them from the Alarm Browser to the Alarm Log. When this problem occurs, the cleared alarm disappears from the Alarm Browser and is not shown in the Alarm Log.

This problem occurs when automatic alarm acknowledgement and automatic pruning of fault management (FM) data are enabled. To check whether your system is affected by this problem, enter the following SQL command on the CTM database:
SQL> select * from ACK_TABLE where ACKINDEX=-1;
If the query returns zero records, your system is affected by this problem.

Workaround Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

Alternately, enter the following SQL commands to temporarily restore Alarm Log functionality:
SQL> insert into ACK_TABLE values (-1, 'CTM', '', 1);
SQL> commit;
This problem might reappear when the next FM pruning occurs. Repeat this workaround to restore Alarm Log functionality.

•CSCsk52028

Symptom    If you launch the NE Explorer for an ONS 15454 SONET or ONS 15454 SDH with AIC or AICI cards, click the card, click Alarm Extenders, and try to set the alarm type, the operation fails with an error message.
Conditions   If you try to set the alarm type, the operation fails for the following alarm types:

•Standby engine transfer

•Explosive gas toxic gas ventilation

•CEV hatch fail

•Level converter

•Second ADSL low volt disconnect

•Low volt disconnect bypass

•-139 V power converter

•-190 V power converter

•Power supply major

•Power supply minor

•Ringing generator major

•Ringing generator minor

•AC or AC rectifier power fail ADSL equipment

•AC or AC rectifier power fail DCL equipment critical state

•AC or AC rectifier power fail DCL equipment

•Commercial AC fail site equipped with standby engine

•AC power loss distributed power RT bay

•Retrieved standby engine commercial AC restored

•High low temp

Workaround   To fix this problem on NE release 6.0 and later, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch. For NE release 5.0.2 and earlier, there is no workaround.

•CSCuk58912

Symptom    It is possible to set alarm threshold values on ONS 1580x measurement points that are outside the range of possible values. For example, you can set a negative power threshold (in milliwatts).
Conditions   See Symptom.

Workaround   Refer to the appropriate hardware documentation before attempting to set thresholds on ONS 1580x cards. The hardware documentation lists the range of possible values.

Circuit and Link Management

•CSCeb26255

Symptom    You cannot create a circuit with a secondary destination and dual-ring interconnect (DRI) protection.
Conditions   This problem occurs when creating circuits on the ONS 15454 SONET R4.0.3.

Workaround   Use manual routing to create the circuit, or retry the same circuit creation using automatic routing and reverse the primary and secondary destination nodes.

•CSCeg06273

Symptom    Cannot change the administrative state to Out of Service-Out of Group (OOS_OOG) for virtual concatenation (VCAT) circuits or VCAT member circuits.
Conditions   The OOS_OOG administrative state is supported for VCAT circuits on certain card configurations only. The following constraints apply:

•ONS 15454 ML-series cards do not support OOS_OOG, regardless of link capacity adjustment scheme (LCAS) mode.

•The FC_MR-4 card does not support OOS_OOG when the LCAS mode is None.

Workaround   Apply the OOS_OOG state to VCAT member circuits only when this administrative state is supported.

•CSCeg49544

Symptom    A manual link is not removed automatically when a patchcord link with the same layer type is created between the same endpoints.
Conditions   This problem occurs when links involve client ports on the following cards: TXP_MR_2.5G, TXPP_MR_2.5G, DM_2.5G, DMP_2.5G, MXP_MR_10G, MXP_MR_10E, and TXP_MR_10E. This problem applies to ONS 15454 SONET and ONS 15454 SDH R5.0 NEs.

Workaround   Manually remove the manual link.

•CSCei84860

Symptom    The J1 path trace displays expected and received bytes at the source end for unidirectional circuits.
Conditions   This display problem occurs on all electrical cards. CTM displays the expected bytes, but you cannot set them. This problem does not apply to SONET or SDH optical cards.

Workaround   None.

•CSCin65850

Symptom    The protection type for physical layer links is not automatically modified when the underlying protection in the NE is deleted.
Conditions   If you configure the protection type on two NEs, you can create a manual link with that particular protection. If the protection is deleted from the two terminating NEs, the protection type for the manual link is changed to Unprotected only if the link is in the SONET/SDH layer, but not when the link is in the physical layer.

Workaround   Delete the manual links; then, recreate them without protection.

•CSCsb36751

Symptom    When you open the Link table from the domain level, the table takes a long time to open and you receive the error message "An error occurred while retrieving data from the database."
Conditions   This problem occurs when you open the Link table from the domain node and the table contains thousands of rows.

Workaround   Limit the scope of query by opening the Link table for a group or NE node.

•CSCsb59118

Symptom    When launching the Circuit table at the domain level, the table contains zero entries and the following error message is displayed: "An error occurred while retrieving data from the database."
Conditions   This problem occurs when the network contains a high number of NEs with many circuits.

Workaround   Try to launch the Circuit table on a domain with fewer NEs.

•CSCsb95230

Symptom    Creation of an STS-n circuit between E100 cards using CTM fails with the following error:
EID-931: Failed to provision the circuit.
Unable to provision circuit. Circuit provision error.
Unable to create the VLANs for the circuit at <node name>
Conditions   This error occurs on ONS 15454 R4.1.4 NEs when EPOS circuits, which were created using CTC R4.1.4, already exist on the NEs.

Workaround   Do one of the following:

•Launch CTC R4.1.4 from the NE and use it to create the circuit.

Note Circuit creation will fail if you use the CTC R5.x that is launched from CTM.

•Delete all existing EPOS circuits that were created using CTC R4.1.4 and then use CTM or CTC R5.x to recreate the circuits.

•Upgrade the ONS 15454 NEs to R5.x.

•CSCsc78150

Symptom    The Link Utilization table shows the VC3 as 0 for all VC3 members of the VC tunnel circuit with VC3 port grouping. It also shows an unused entry for the VC4. This happens only in circuits with multiple hops.
Conditions   Unknown.

Workaround   Use the following guidelines, depending on the symptom:

•VC3 - Appearing as 0: The database is updated in two cycles. In the first cycle, the VC4 values are updated, and in the second cycle the VC3 values are correctly stored in the database. If you notice this problem, wait briefly before launching the Link Utilization table. The inconsistency will be removed automatically.

•Unused Entry: Once the used entries show the correct values, the unused entries will be corrected automatically.

•CSCsc87791

Symptom    International characters can be entered in fields that do not support them.
Conditions   If you enter an international character in a nonalias field, the entry is permitted.

Workaround   Do not enter non-English characters in nonalias fields.

•CSCsc93614

Symptom    Server trails cannot be created for any port other than port 1 of an E1 card. An "Invalid Preferences" error appears.
Conditions   This error appears if you select a different VT/VC3/VC12/VC11 number for the source and destination while creating the server trail.

Workaround   None.

•CSCsd02541

Symptom    An error appears when attempting to route a circuit after an upgrade from OC-192 XFP to OC-192. The Link table shows the link as valid, and the physical termination point (PTP) ID is not updated.
Conditions   Unknown.

Workaround   None.

•CSCsd06614

Symptom    When a low-order circuit is created and the option to have the corresponding tunnel created automatically is selected, the alias name of the tunnel and the low-order circuit is the same. When multiple low-order circuits are created through the same operation (the number of circuits is more than 1 in the Create Circuit wizard), the alias of the tunnel is the same as that of the first low-order circuit in the group.
Conditions   Create a low-order circuit and check the Automatically create tunnel check box.

Workaround   Do one of the following:

•Create the tunnel(s) with the desired alias, then create the low-order circuits routed through them.

•Create the low-order circuit(s) and the tunnel through a single operation, then edit the tunnel alias to the desired value.

•CSCsd12630

Symptom    ONS 155xx Circuit table does not show circuit information for circuits whose names are modified using CTM.
Conditions   Modify an ONS 155xx circuit name using CTM. Circuit information for the renamed circuit does not appear.

Workaround   Refresh the circuit information.

•CSCsd30268

Symptom    The DCC link between the TXP client port and the line card is discovered at the physical layer instead of the SDCC layer.
Conditions   See Symptom.

Workaround   None.

•CSCsd30368

Symptom    Composite net links created in the network are not discovered in CTM if the NEs are already discovered or added in CTM. If the NEs are added to CTM after the link is created, the discovery works as expected.
Conditions   This problem applies only to composite net links.

Workaround   Mark the NEs terminating the composite net links as Out of Service and back In Service. The links will be discovered correctly.

•CSCsd30391

Symptom    Composite net links are displayed in the CTM Network Map when they should not be.
Conditions   See Symptom.

Workaround   None.

•CSCsd42206

Symptom    Cannot remove a high-order VCAT circuit between two GE-2-WAN cards on ONS 15305 NEs. CTM returns a message that the circuit has been successfully removed, but the circuit is not removed from the Circuit table.
Conditions   This problem applies to high-order VCAT circuits between two GE-2-WAN cards when the circuit is deleted.

Workaround   None.

•CSCsd45581

Symptom    For server trails created on ONS 15310 MA NEs, the wrong physical location is shown for all path alarms such as Encapsulation Mismatch and TIM-P. CTM shows the physical location with port 0. For example, if an alarm is raised on slot 1, port-29-56, the physical location is shown as slot 1, port 0.
Conditions   This problem occurs when you create a server trail link between two ONS 15310 MA NEs of STS-1 type using DS1 port-29-56 of DS1_84_DS3_EC1_3. Then create an L2 PTP from ML/HDLC frame format to CE port/GFP-F frame format. When the Encapsulation Mismatch alarm is raised, the physical location for the alarm is incorrect.

Workaround   None.

•CSCsd46307

Symptom    An invalid link becomes valid when NEs are marked as Out of Service and then In Service. This problem applies to links that are invalid because one or both ports of the link are marked as Out of Service, or because a fiber cut occurs on the link.
Conditions   When an NE is marked as In Service, CTM takes into account only the validity of the end PTPs of the link in the inventory information before marking the link as valid or invalid. CTM does not consider the actual status of the link in the network.

Workaround   None.

•CSCsd48430

Symptom    Cannot create more than one VT server trail on DS1 cards on ONS 15454, ONS 15310 MA, and ONS 15310 CL NEs when a server trail already exists on the first VT of the selected STS. Although other VTs are available, they are not listed in the server trail creation wizard as possible endpoints. This operation succeeds in CTC.
Conditions   This problem occurs only when a VT server trail exists on the first VT.

Workaround   Use other VTs only for VT server trail creation.

•CSCsd50813

Symptom    The following null pointer exception is generated during STS creation in the Source/Destination pane:
EID-915: Failed to retrieve STSs.
java.land.NullPointerException.
Also, you cannot route a circuit manually through available STSs. The manual routing wizard returns the error message "STSs are not available."

Conditions   See Symptom.

Workaround   For the null pointer exception during STS creation, check whether the STS exists on the same port. If it does, change the port. There is no workaround for the problem of being unable to manually route a circuit through available STSs.

•CSCsd52297

Symptom    After upgrading from CTM R6.0, the Link Validity value changes from Valid to Invalid for some links between ONS 1580x NEs or between an ONS 15454 and an ONS 1580x NE.
Conditions   This problem occurs when you create a link in CTM R6.0 and then upgrade your CTM release.

Workaround   Mark one of the NEs in the link as Out of Service and then back In Service.

•CSCsd55013

Symptom    An hourglass is shown on the Circuit Trace window when the WDM Topology check box is checked. It takes 15 seconds or longer for the circuit trace to refresh.
Conditions   This problem applies only to the CTM client on Windows. The same behavior occurs for any type of circuit when you click the Refresh Data tool.

Workaround   Resize the window. The Circuit Trace window updates immediately.

•CSCsd55060

Symptom    A patchcord link between a trunk port and a channel port is shown in the Link table at the Physical layer.
Conditions   This problem occurs when you use the Create Link wizard to create a patchcord link between a trunk port and a channel port on two R6.0 NEs.

Workaround   None.

•CSCsd56066

Symptom    The getAllPTPsForSNCProvisioning method returns all DS3 ports on DS3_EC1_48 cards for layer rate 14. The method should return only EC1 ports for layer rate 14. DS3 ports should be returned only for layer rate 4; instead, the method returns DS3 ports for layer rates 4 and 14.
Conditions   See Symptom.

Workaround   None.

•CSCse54602

Symptom    Alarms are not summarized on autodiscovered links between DWDM transponder client ports when configured with SONET or SDH payload.
Conditions   This problem occurs if you provision two DWDM transponder cards between client ports on two different NEs. If you configure the client ports to have SONET or SDH payload and then create the DCC termination on both ports, CTM discovers a link with link provisioning set to auto. Alarms are not summarized in the Network Map or Link table. The alarm severity in the Link table is reported as "No Alarms," even if alarms exist on the source or destination PTP.

Workaround   None.

•CSCse63492

Symptom    The alarm severity of discovered SDH links remains critical even if the alarms are cleared.
Conditions   This problem applies to a DCC link between two ONS 15305 NEs or between an ONS 15305 and an ONS 15454 NE.

Workaround   Mark one or both nodes as Out of Service, remove the invalid link, and mark the node(s) back to In Service.

•CSCse69351

Symptom    Name changes of parent VCAT circuits made from CTC do not reflect in CTM.
Conditions   This problem applies only to a name change of the parent VCAT circuit.

Workaround   Rediscover the circuit.

•CSCse73260

Symptom    If you create a manual link between a 2.5G_DM trunk (on the source node) and an STM-16 TXP client (on the destination node), the STM-16 layer detail is not available. The STM-16 layer is available only if the link is created in the other direction (on the 2.5G_DM on the destination node).
Conditions   This particular configuration is used to combine the data aggregation of the 2.5G_DM trunk with the higher DWDM transmission performance of the TXP_MR_10E card.

Workaround   Create the manual link using the TXP client port as the source termination point.

•CSCse76870

Symptom    Manual link validity between a CSR-1 and ONS 15454 is not handled correctly when there is a loss of connectivity to the ONS 15454.
Conditions   This problem occurs when you create a manual link with endpoints on a CRS-1 and ONS 15454. If you cycle the ONS 15454 from In Service to Out of Service and back to In Service to simulate a loss of connectivity, the link status does not update correctly.

Workaround   None.

•CSCse79378

Symptom    The cross-connect (XC) utilization for STS and VT circuits is not populated on ONS 15310 NEs.
Conditions   This problem occurs when mapping an intra-NE STS-1 or VT circuit from any DS3 or DS1 card to another card.

Workaround   None.

•CSCse84755

Symptom    When creating VT-VCAT circuits on CE-100T-8 cards on ONS 15310 CL NEs, invalid VT thresholds are created on DS1 interfaces on CTX cards.
Conditions   This problem applies to ONS 15310 CL NEs.

Workaround   None.

•CSCse93968

Symptom    The getAllCrossConnections API returns cross-connects for CTX cards with incorrect PTP details on ONS 15310 MA NEs.
Conditions   This problem occurs with VT-VCAT circuits on CE-100T-8 cards going through CTX cards. For these types of circuits, the floating termination point (FTP) on the CTX card is shown as /rack=1/shelf=1/slot=3/sub_slot=255/ppm_holder=2/port=1.

However, there is no subslot for CTX cards; subslots apply to ASAP cards. This problem applies to ONS 15310 MA NEs. The problem is not observed for PPM-based MRC_12 cards on ONS 15454 NEs.

Workaround   None.

•CSCse95481

Symptom    If a card is changed or upgraded on an NE, all circuits that existed on that slot before the operation still show the module that existed before the change.
Conditions   This problem occurs when circuits exist on a card that is replaced or upgraded.

Workaround   After upgrading or replacing a card, mark the NE as Out of Service and then In Service. This refreshes the display strings associated with the circuits on the replaced module.

•CSCse96654

Symptom    The subnetwork automatic grouping feature does not work after a TCC reset.
Conditions   After rebooting a node that is part of a subnetwork, when the node comes up, CTM puts it in a different subnetwork automatically. Because of this, nodes in the same network go into different subnetworks. This problem applies to ONS 15454 SONET NEs.

Workaround   None.

•CSCsf15991

Symptom    For links terminating on ONS 15600 SONET or ONS 15600 SDH NEs, the Link Utilization table shows the wrong VC4/STS number when a low-order circuit traverses the link over a tunnel. The Circuit Trace report for the low-order circuit shows the VT/VC3 number as 255. The Circuit Span table for the low-order circuit shows 255 for endpoints on the ONS 15600 SONET or ONS 15600 SDH NEs.
Conditions   This problem occurs when you route a low-order circuit on a tunnel through an ONS 15600 SONET or ONS 15600 SDH NE. These NE types do not support low-order cross-connects.

Workaround   Ignore the incorrect low-order information shown in the CTM client.

•CSCsh30264

Symptom    The Circuit table shows the incorrect service state (OOS or OOS Partial) for OCHNC circuits. It also occasionally shows the incorrect service state for SONET and SDH circuits.
Conditions   This problem occurs after creating a unidirectional or bidirectional OCHNC circuit in CTM. CTC shows the circuit as in service (IS), while the CTM Circuit table shows the same circuit as out of service (OOS or OOS Partial). This problem occurs occasionally for SONET and SDH circuits as well.

Workaround   Force circuit rediscovery by marking the NEs as Out of Service, and then as In Service. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsi75723

Symptom    The Circuit table does not display the port name for DS3E, DS3XM, and DS3XM_12 cards.
Conditions   If you apply a text name to a port on a DS3E, DS3XM, or DS3XM_12 card, the text name is not shown in the source or destination fields in the Circuit table.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsj01791

Symptom    The following error message is returned when you try to create a unidirectional manual link from an ONS 15454 SONET NE to an ONS 15216 EDFA NE:
EID-733: The node <node_name> is not available or there are no available physical 
termination points for the given link size 10G-ITU in the specified layer and direction. 
Conditions   This problem occurs when you try to create a link with these details:

•Layer: Physical

•Layer detail: 10G-ITU

•Protection: Unprotected

•Direction: Unidirectional

•Provisioning type: Manual

Workaround   None.

•CSCsj83214

Symptom    The Circuit table displays TL1 circuits incorrectly.
Conditions   The Circuit table does not discover correctly TL1 circuits that are created through the TL1 interface or from CTC. The Circuit table displays split TL1 circuits with the string "Duplicate" appended to the circuit name. This problem is resolved when the NE service restarts, but if the NE is marked as Out of Service and then In Service, the problem reoccurs.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsk53826

Symptom    CTM and CTC do not discover server trail links that are created in opposite directions.
Conditions   This problem occurs when you create a server trail between node 1/port A and node 2/port B. If you then create another server trail in the opposite direction between the same ports, CTM and CTC do not discover that server trail.

Workaround   Create all server trail links in the same direction.

•CSCsk74382

Symptom    CTM does not discover more than two server trail links created between the same ports on the same VC-4 between two ONS 15454 SDH NEs. The Link table displays the first two server trail links with the wrong names, including an incorrect VC-12/VC-11/VC-3 number. CTC correctly discovers these server trail links.
Conditions   This problem occurs when you create three VC-12/VC-11/VC-3 server trail links between the same ports.

Workaround   The default name for the new server trail links is calculated incorrectly and conflicts with the names of the existing links. Therefore, change the names of the newly created server trail links.

•CSCsl03411

Symptom    The Circuit table does not contain the expected circuits.
Conditions   This problem occurs when you open the Circuit table from the NE Explorer on a card that is involved in a port- or card-level protection group. Circuit information is shown only for circuits that have working cards or ports.

Workaround   There is no workaround in CTM. You can view the circuit information in CTC.

•CSCsq96399

Symptom    Server trails are discovered as not routable, and the nodes that the server trails connect are located in different subnetworks.
Conditions   This problem occurs after marking a node as Out of Service and then In Service.

Workaround   Restart the NE service.

•CSCsq96429

Symptom    After deleting server trails from the Link table, all server trails are no longer discovered.
Conditions   See Symptom.

Workaround   Restart the NE service.

•CSCsr60497

Symptom    When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
Conditions   This problem is seen only in the map view when creating a circuit manually using the Create Circuit wizard. The node names are shown correctly in the Network Map from the Domain Explorer.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsv14849

Symptom    When a Provisioner user tries to modify, reconfigure, or delete a low-order path (LOP) VCAT circuit, the following error messages are generated:
EID-989: Access violation. Verify that you have user privileges to perform this operation 
on this circuit.
EID-943: Circuit deletion failed. Failed to delete the following circuit(s): 
<circuit_name>.
Conditions   The error messages described in the Symptom are generated when a user with Provisioner privileges opens the Circuit table and tries to modify, reconfigure, or delete an LOP VCAT circuit of size VC12 or VC3 on an SDH NE. As a result of this problem, L2 topologies based on LOP-v circuits cannot be removed.

Workaround   Log into the CTM client with SuperUser privileges to modify, reconfigure, or delete LOP VCAT circuits.

•CSCsy18486

Symptom    In the Create Circuit wizard, tunnel links are not available for VT circuit routing.
Conditions   The problem occurs when you launch the Create Circuit wizard and use previously created tunnel circuits to create new VT circuits.

Workaround   Restart the NE service.

User Management

•CSCin81532

Symptom    When using a Retrieve, Maintenance, or Provisioning user account for CTM server-to-NE connectivity, CTM allows NE user administration operations to be performed on R4.1.4 NEs. User administration should be allowed only for Superuser accounts.
Conditions   This problem applies only to R4.1.4 NEs and is fixed in later NE releases.

Workaround   Use a Superuser account for CTM server-to-NE connectivity.

•CSCsd47150

Symptom    The IOS Users table is blank for ENEs in a GNE-ENE setup after changing ENEs to GNEs and GNEs to ENEs, and changing the community strings for the ENEs.
Conditions   This problem occurs when you add GNE/ENEs in a DCC-connected ring to CTM. After the NEs come up, if you change the ENEs to GNEs and the GNEs to ENEs and then change the community string for the ENEs, the IOS Users table is not populated for ML cards on the ENEs.

Workaround   None.

•CSCsd47274

Symptom    The IOS Users table is blank for a GNE-ENE setup with ONS 15600 NEs as GNEs. The SNMP community string is blank for all ENEs in the Domain Explorer. The community string was configured as public for all NEs in CTC. Because of this problem, L2 does not work in a GNE-ENE setup where ONS 15600 NEs are configured as GNEs.
Conditions   Unknown.

Workaround   None.

•CSCse94210

Symptom    When trying to create users on multiple NEs from the Domain Explorer > Administration > NE User Access Administration menu option, the Job Monitor table shows the task status as Failed for some nodes, even though the user is created.
Conditions   This problem applies to ONS 15310 MA and ONS 15454 SONET NEs.

Workaround   None.

Data Services

•CSCeh50962

Symptom    After the CTM server is rebooted, Layer 2 RPR services take about 20 minutes to get to "Complete" L2 Sync State.
Conditions   After the server reboots, Layer 2 RPR services with VLANs remain in L2ServiceNotReady L2 Sync State in the Layer 2 Topology table for about 20 minutes.

Workaround   None.

•CSCeh51003

Symptom    Cannot delete VLANs in an RPR configuration.
Conditions   This problem was observed while trying to create an RPR topology with ONS 15310 and ONS 15454 ML-100T cards with five VLANs.

Workaround   Complete one of the following workarounds, depending on the situation:

•If the startup configuration is accessed while CTM tries to apply the barebone configuration, a wr mem failure occurs. Wait for some time; then, apply the command again.

•If there is a difference between the startup configuration and the running configuration on the ML card, enter the wr mem command on the card.

•CSCeh97834

Symptom    CTM fails to create an L2 service on an RPR ring when there are approximately 110 services created on the ML card.
Conditions   This problem occurs when ML cards take a long time to store the running configuration on the startup configuration. CTM times out in the request response condition and propagates an error message, even though the VLAN is created eventually.

Workaround   If the VLAN is not discovered, mark the NEs as Out of Service and back In Service. This restarts the topology and VLAN discovery process. Entering the wr mem command on the cards where the VLAN is configured helps rediscover the missing VLANs.

•CSCei37993

Symptom    An RPR is shown as up even though the station IDs are not unique.
Conditions   If an RPR has duplicate stations IDs, it should not be shown as up. However, CTM displays an RPR with duplicate station IDs as up.

Workaround   None.

•CSCei58026

Symptom   After creating an L2 service in an RPR in a large network, the L2 topology goes into L2ServiceNotReady or Sync Failed state and does not recover.

Conditions   In large RPRs involving many ML cards, it takes CTM a long time to create L2 service drops. During this time, the L2 topology might go into L2ServiceNotReady or Sync Failed state without recovery.

Workaround   Wait for 30 to 45 minutes for CTM to recover the resynchronization state. If the L2 topology has not recovered after 45 minutes, mark the NEs as Out of Service (in the Network Element Properties pane > Status tab > Operational State field) and click Save. Then, mark the NEs as In Service and click Save. This restarts the VLAN discovery process, which discovers the VLANs and their associated drops.

•CSCei76154 (Related caveat ID: CSCse64642)

Symptom    The multilayersubnetwork.idl file returns errors when it is compiled with a third-party Interface Definition Language (IDL) compiler.
Conditions   See Symptom.

Workaround   If you are using Java for OSS client development, use JacORB's IDL compiler to compile the file. OSS clients must use JacORB and cannot use any other object request brokers (ORBs). There is no known workaround for OSS clients written in C++.

•CSCsb38681

Symptom   The L2 Topology table launched for an NE shows all topologies in that subnetwork.

Conditions   See Symptom.

Workaround   None.

•CSCsb57054

Symptom    An L2 topology goes into L2ServiceNotReady state during RPR creation and cannot recover. The Alarm Browser contains the warning alarm "Need to save running config."
Conditions   This problem applies to ML cards used in RPR creation.

Workaround   Try any of the following:

•Reboot the ML cards on which the warning alarm occurs. Then, use the Enable L2 Service option to reapply the base card configuration.

•Telnet into the cards and enter the wr mem command so that both the startup and running configurations are the same. Then, use the Enable L2 Service option to reapply the base card configuration.

•Restart the topology creation by reloading the barebone configuration and rebooting the cards in the L2 topology.

•CSCsb66827

Symptom    Two RPRs are discovered when NEs are added to the CTM server for the first time.
Conditions   This problem occurs when NEs are added to the CTM server for the first time and there is a delay in the NE synchronization.

Workaround   Restart the NE service.

•CSCsb66965

Symptom    L2 topology PTPs and RPRs are not discovered and displayed in the L2 Topology table.
Conditions   This problem was observed during regression testing of L2 topologies. When the problem occurs, L2 topologies are not visible in the L2 Topology table. The problem persists even after marking the NEs as Out of Service and In Service, or after reloading or resetting the configuration.

Workaround   Restart the NE service.

•CSCsc82864

Symptom    A topology with 24 cards takes longer than 90 minutes to come up.
Conditions   See Symptom.

Workaround   Complete the following steps:

Step 1 Verify that the SNMP trap settings have been configured correctly on all NEs.

Step 2 Before creating the L2 topology, verify that the card has synchronized with CTM. To do this, launch the IOS Users table on the group and verify that the table contains entries pertaining to the card.

Step 3 Allow 15 minutes to recreate a topology on a card after deleting the old topology on the card.

•CSCsc91219

Symptom    A four-card RPR with 50 VLANs does not synchronize.
Conditions   See Symptom.

Workaround   None.

•CSCsd25352

Symptom    Topology discovery does not occur on the monitoring server.
Conditions   Unknown.

Workaround   Mark the NEs as Out of Service (in the Network Element Properties pane > Status tab > Operational State field) and click Save. Then, mark the NEs as In Service and click Save. Alternately, restart the NE service for the NEs.

•CSCsd31676

Symptom    For an L2 topology with segments of varying sizes, the sizes and number of VCAT members are displayed incorrectly.
Conditions   Unknown.

Workaround   None.

•CSCsd39577

Symptom    An L2 topology is shown as Incomplete when the status should be Complete. All circuits are shown as discovered in the Circuit table.
Conditions   Unknown.

Workaround   Restart the NE service.

•CSCsd44356

Symptom    The circuit alias and topology alias do not work in a mixed-size L2 topology.
Conditions   This problem applies to mixed topology creation.

Workaround   Manually add the alias to the circuits after the creation is complete.

•CSCsd45491

Symptom    When the topology name is longer than 26 characters, after a card is added the new circuit is not discovered correctly and the RPR wraps. CTM appends the time stamp to the newly created circuit name on the added card. This sometimes causes naming problems.
Conditions   This problem occurs only when the topology name contains 26 characters or more.

Workaround   Always create a topology name that contains fewer than 26 characters.

•CSCsd53003

Symptom    The Add Drop wizard shows RSTP is disabled on the existing drops when STP is actually enabled on the existing drops.
Conditions   This problem occurs during the add drop operation.

Workaround   None.

•CSCsd53108

Symptom    When RADIUS relay is enabled on the card, IOS user creation is shown as successful, but the users are not visible in the IOS Users table. Instead, CTM should return an error that IOS users could not be created.
Conditions   This problem occurs when RADIUS relay is enabled on the card.

Workaround   None.

•CSCsd53332

Symptom    After performing a remove card operation, PoS ports are not enabled.
Conditions   Unknown.

Workaround   Use the NE Explorer or Modify Ports dialog box to make PoS state changes.

•CSCsd54231

Symptom    Not all PoS ports are enabled after an add/remove card operation.
Conditions   This problem occurs because CTM cannot enable all of the PoS ports that were shut down during an add/remove card operation.

Workaround   Wait for the L2 topology to go into Sync Complete state. Then, use the Modify Ports dialog box or the NE Explorer to enable the PoS ports that were shut down during the add/remove card operation.

•CSCsd55143

Symptom    The Multicast Bandwidth class of service (CoS) value is set to 0 (zero) on a newly added card.
Conditions   When a card is added and bandwidth values are set, the Multicast Bandwidth CoS value is reported incorrectly as 0.

Workaround   Use the CLI to change multicast CoS values.

•CSCsd57810

Symptom    While trying to modify L2 topology bandwidth, the following error is returned:
EID-368: Error occurred while modifying L2 topology bandwidth. Could not modify bandwidth 
values.
Conditions This problem occurs on ML cards if there are two match cos commands under class-map. CTM can only support one match cos command. The second match cos command is shown as "null" in the CTM GUI. When you try to modify L2 topology bandwidth, the error message is generated.

A sample problem configuration is shown as follows:
class-map match-any AVVID_VOICE_VIDEO
 match cos  1  2
 match cos  5
Workaround   From the CTM GUI, delete the last null value, make the necessary topology bandwidth modifications, and click Apply. The multiple match cos command problem should be corrected and you should not receive any error messages.

•CSCse64026 (Related caveat ID: CSCsd44356)

Symptom    In a 24-card RPR, the Alias field is not set to the user-specified value.
Conditions   This problem applies to ONS 15454 NEs.

Workaround   None.

•CSCse71108

Symptom    When an ML card reset is in progress, you can modify the Ethernet ports. CTM confirms that the port modification succeeded, even though no changes were actually applied to the card.
Conditions   This problem applies to ONS 15454 SONET R5.0.6 NEs with G-series cards.

Workaround   None.

•CSCse71564

Symptom    After an ML card reset, the L2 topology goes into L2 Service Not Ready state and never transitions to Complete state.
Conditions   This problem applies to ONS 15454 R7.0 NEs.

Workaround   None.

•CSCse73576

Symptom    An error message is returned when trying to launch the L2 Topology table. Also, the Circuit table launches but freezes the CTM client.
Conditions   This problem occurs only on certain large-scale setups and is due to CTM database-related issues.

Workaround   None.

•CSCse76654

Symptom    It is possible to create two PTP L2 topologies with different class maps using the same ML cards.
Conditions   This problem occurs only when you begin creating the second PTP topology on the ML card before CTM discovers the first PTP topology. This problem does not occur if you wait for CTM to discover the first PTP topology on the ML card before you begin creating the second PTP topology.

Workaround   Ensure that all PTP topologies related to the selected ML card are discovered before trying to create a second PTP topology on the same ML card. The CTM client provides a warning message if you try to create a second PTP topology before the first one is discovered.

•CSCse82387

Symptom    A VLAN created in CTC is not visible in the VLAN tab of the CTM NE Explorer for Ethernet cards.
Conditions   This problem applies to Ethernet cards on ONS 15305 R3.0 and ONS 15454 NEs.

Workaround   To display VLAN data correctly, refresh data from the server.

•CSCse83853

Symptom    An RPR topology is shown as complete when it contains only one circuit.
Conditions   This problem occurs under the following conditions:

1. Create a TL1 circuit from ML PoS 0 to ML PoS 1.

2. CTM discovers the topology as an incomplete RPR.

3. Using the CTC Upgrade Circuit option, upgrade the circuit to a normal CTC circuit.

4. The circuit state changes from Discovered_TL1 to Discovered and the L2 topology shows the status as complete. However, the RPR ring is not complete, because it contains only one circuit.

Workaround   Mark the NEs involved in the RPR as Out of Service and then In Service.

•CSCse88621

Symptom    The NE takes a long time to synchronize if ML cards are not loaded with a barebone configuration.
Conditions   This problem occurs when there is no configuration on ML cards.

Workaround   Load a barebone configuration on all ML cards.

•CSCse91457

Symptom    After creating a UNI/QinQ-type Layer 2 service with CoS accounting enabled, the service comes up. If you then delete the Layer 2 service, CTM deletes everything but does not delete the CoS accounting command from the Cisco IOS CLI.
Conditions   This problem applies to all NEs on which Layer 2 services can be created.

Workaround   Select the card in the NE Explorer, click the Ether Provisioning tab, and disable CoS accounting.

•CSCse94115

Symptom    The Exercise Ring operation fails on an ENE not directly connected to the GNE.
Conditions   This problem applies to NE R6.0.1.

Workaround   Use CTC to complete the Exercise Ring operation.

•CSCsf19350

Symptom    During L2 topology creation, when you select manual provisioning for the first circuit in the RPR Circuit Segment Details screen, the Textual and Graphical Routing Preferences screen appears. If you select the textual option, the manual provisioning screen with textual options appears. However, even if you select graphical routing for the second circuit, the textual selection screen appears.
Conditions   This problem occurs during L2 topology creation when you select textual routing for the first circuit and graphical routing for the second circuit.

Workaround   Select the textual routing preference option for the first circuit. For the second circuit, first select the textual routing option; then, select the graphical routing option. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsf19399

Symptom    During an Add/Remove Card operation, when the circuit name contains 30 characters, an EID-927 error occurs.
Conditions   This problem occurs when the circuit name has exactly 30 characters. Circuit names with more than 30 characters are not accepted and a corresponding error message is displayed. If the circuit name has exactly 30 characters, the EID-927 error is displayed.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsf20093

Symptom    RPR topology creation fails, creating incomplete topologies.
Conditions   This problem occurs when the server is overloaded and invalid entries are present in the Circuit Drop Selection pane, causing wizard parameters to initialize incorrectly. Consequently, an incorrect wizard navigation is set.

Workaround   Click the Back button instead of the Next button in the wizard. This ensures a reinitialization of the incorrect parameters and sets the correct wizard navigation.

•CSCsf22050

Symptom    When one of the L2 topologies is in Sync Failed state, getAllL2Topologies returns nothing. It should return all remaining L2 topologies.
Conditions   See Symptom.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsg86303

Symptom    When an advanced QoS profile is applied to a drop, the QoS profile name becomes Custom_QoS after the resync period.
Conditions   This problem occurs whenever an advanced QoS profile is applied to a drop.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh18844

Symptom    One of the following occurs if an advanced QoS profile is applied to a drop that does not have a QoS profile or a drop that has an existing profile that the QoS does not recognize:
•A Java error.

•The QoS policy is applied to the drop in incorrect order.

•The QoS policy is applied to the drop twice.

Conditions   See Symptom.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh20547

Symptom    Create a VLAN on a topology and then add QoS profiles to a drop. The QoS profiles are added but displayed in incorrect order. They are sorted based on the Match Any field values.
Conditions   The default value of the Match Any field is set to True. When you disable the Match Any field, all the newly-created QoS profiles are sorted based on the Match Any field values.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh20561

Symptom    QoS statements remain on the card after deleting drops from a VLAN.
Conditions   This problem occurs on any drop that contains a QoS class map on a topology with VLANs. After deleting the drops from the VLAN, the QoS statements should also be deleted from the configuration. Instead, the QoS statements remain on the card.

Workaround   None.

•CSCsh22076

Symptom    A traffic loss of 15 seconds occurs through a VLAN created on an RPR Layer 2 topology.
Conditions   This problem occurs under the following conditions:

1. Create an RPR Layer 2 topology and wait until its state changes to Complete.

2. Create VLAN Layer 2 services on the RPR topology and then connect a traffic generator to the topology.

3. Open the Add/Remove Cards wizard and add a new ML card to the RPR topology. When creating the new circuits, choose the Manual Routing option.

4. Remove the recently added ML card; then, repeat this process at least four or five times.

Workaround   From the Add/Remove Cards wizard, choose the Automatic Routing option when provisioning the L1 circuits. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh42924

Symptom    Create a topology. While modifying the topology, change the CoS value and then the corresponding bandwidth. The CoS value is reset to the default value.
Conditions   This problem occurs when you first change the CoS value and then the bandwidth value. If you change the bandwidth value before the CoS value, the correct values are set.

Workaround   Change the bandwidth first before changing the CoS value. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh77677

Symptom    Custom QoS profile information is lost after some time.
Conditions   This problem applies to QoS profiles created with the VLAN creation wizard.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsh94186

Symptom    The confirmation dialog box is not displayed after uploading a configuration file to a TCC card.
Conditions   In the Configuration tab of the NE Explorer, click File >> TCC. There is no confirmation dialog box to notify you that the file has been uploaded to the TCC card.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsi29165

Symptom    After creating a QoS profile, the class order changes.
Conditions   Occasionally, after creating and then editing the QoS profile, the class order changes.

Workaround   Edit the QoS profile twice. The problem is not seen on the second time you edit the QoS profile. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsi34127

Symptom    When a POS port is disabled in one of the member cards of a topology, an alarm is generated on the NE that contains the card. But the object is shown as Bad Physical Location.
Conditions   This problem occurs when you disable a POS port in one of the member cards of a topology.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsj51055

Symptom    After applying customized settings on an ML card, you cannot change the QoS profile on a VLAN drop port.
Conditions   This problem occurs under the following conditions:

1. In the NE Explorer slot properties pane for an ML card, download a customized barebone configuration file in the Card Configuration tab.

2. Create an RPR Layer 2 topology on the same ML card.

3. Create a VLAN with a QoS with multiple classes.

4. Change the QoS profile on one of the VLAN drop ports. CTM displays an error message and does not change the QoS profile.

Workaround   Use the CLI interface to apply the configuration change. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsk27644

Symptom    Cannot enable an 802.1q drop from the Modify L2 Service Drops dialog box. The modification completes successfully, but the related IOS subinterface remains down.
Conditions   This problem occurs when you disable an 802.1q drop in the Modify L2 Service Drops dialog box, and then re-enable that same drop.

Workaround   Use Cisco IOS commands to force the subinterface to come up.

Domain Explorer

•CSCei60546

Symptom    An NE with one TCC card goes into loss of communication (LOC) state if the TCC card is swapped without a synchronization.
Conditions   If a TCC card on the NE is swapped with a card that has a different IP address, the NE fails to come up in CTM.

Workaround   None.

•CSCei76087

Symptom    After the CTM server is restarted, unmanaged NEs have a red check mark next to them in the Domain Explorer, indicating that their configuration synchronization failed.
Conditions   This problem occurs when a CTM server with unmanaged NEs is restarted. When the server comes back up, the Domain Explorer displays red check marks to indicate that the configuration synchronization failed for the unmanaged NEs.

Because these NEs are unmanaged, no actual configuration synchronization would ever occur. However, the config synchronization status for these NEs should always show success (a green check mark).

Workaround   None.

•CSCsc48173

Symptom    The NE service name for one event does not match the name used in the Audit Log filter. The following message might not appear in the Audit Log:
AUD-7000: Subnetwork Mode Automatic - MGX88xxSubnetManager Started > > >regrouping of managed NEs in subnetworks mgx88xx-ne

Conditions   See Symptom.

Workaround   Turn off the Audit Log filter to see the message.

•CSCsc61181

Symptom    MGX Voice Gateway applications cannot be launched from the CTM Domain Explorer.
Conditions   If you install the CTM client in a location that has spaces in the directory path, the MGX Voice Gateway applications cannot be launched from the CTM Domain Explorer.

For example, D:\Program Files\ctm has a space between Program and Files. Installing in this location causes the Symptom described.

Workaround   Install the CTM client in the default directory location, or choose a target directory path without spaces.

•CSCsc90221

Symptom    For a multishelf NE, the state change from Out of Service to In Service is inconsistent and occurs without a configuration synchronization.
Conditions   This problem occurs when you add a multishelf NE, mark it as Out of Service, make a configuration change, and mark it as In Service.

Workaround   None.

•CSCsc92667

Symptom    When you add an unmanaged NE to CTM and mark it as In Service, the unmanaged NE shows a red check mark (unreachable) instead of a green check mark (reachable).
Conditions   See Symptom.

Workaround   None.

•CSCsd40326

Symptom    After a switch activity is performed with a Cisco IOS command on an ONS 155xx with a redundant CPU (active/standby), the node is shown as available in the CTM Domain Explorer but unavailable in the tree view.
Conditions   This problem applies to an ONS 155xx NE with an active/standby CPU configuration. When a switch activity command is performed through a Cisco IOS session on the NE, the node is shown as available in the CTM Domain Explorer but unavailable in the tree view.

Workaround   Mark the NE as Out of Service and then In Service.

•CSCsd46616

Symptom    An LOC occurs and a DCC NE keeps changing to any of the following: GNE, LAN-connected network element (LNE), and ENE.
Conditions   This problem occurs when many NEs are synchronizing per partition.

Workaround   After restarting the NE service or server, mark a few rings as In Service, in sequence.

•CSCse65683

Symptom    In a 24-card RPR, if you mark the NEs as Out of Service, wait for an hour, and then mark the NEs back to In Service, it causes the PoS port state to change from Up to Down, which could affect traffic.
Conditions   This problem applies to ONS 15454 NEs.

Workaround   None.

•CSCsf16285

Symptom    An ENE is not reachable in a GNE/ENE setup because its name is the same as one of the NEs in CTM.
Conditions   This problem occurs when all of the ENEs and the GNE in a GNE/ENE setup are marked as Out of Service. The initial poll of one of the ENEs returns an Oracle exception because the unique constraint on the NE system ID is not met.

Workaround   Delete the ENE from CTM and then add it again.

•CSCsf26013

Symptom    When a subnet containing an ENE is moved to a different network partition, the ENE goes into LOC state.
Conditions   This problem applies to CTC-based NEs and occurs when a subnet containing an ENE is moved from one network partition to another.

Workaround   Launch another CTM client and then move the subnet to a different network partition.

•CSCsi26713

Symptom    NEs are added successfully but do not appear in the Domain Explorer and cannot be located with the Find feature.
Conditions   This problem occurs when the Domain Explorer contains several thousand NEs.

Workaround   Install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

NE Explorer

•CSCed15994

Symptom    Setting the Routing Information Protocol (RIP) metric to zero does not generate an error message.
Conditions   In the ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE Explorer > Network tab > RIP subtab, if you change the default RIP metric to 0 (zero), the value is not accepted. There is no error message to inform you that the change is not accepted.

Workaround   Zero is not a valid value for the RIP metric. Specify a different value.

•CSCef65097

Symptom    The NE Explorer does not refresh the Secure Config Mode value after a mode change.
Conditions   This problem occurs under the following conditions:

1. Select an NE with a TCC2 card and insert a TCC2P card in the standby slot. Wait for the TCC2P card to synchronize with the active TCC2 card and become standby.

2. Remove the TCC2 card.

3. Select the NE and launch the NE Explorer. Click the Network tab > Secure Config Mode subtab.

4. Change to secure config mode. Provide the IP address and netmask. The TCC2P card reboots. After several minutes, CTM re-establishes connectivity to the NE and synchronizes the NE data.

5. Return to the NE Explorer window and verify the NE connectivity. The cursor in the NE Explorer window remains an hourglass icon, and the data does not refresh.

Workaround   Close and reopen the NE Explorer.

•CSCeh45510

Symptom    Clicking the Apply button after modifying the SNMP User Datagram Protocol (UDP) port does not save the modified value.
Conditions   If you modify the SNMP UDP port value and then click Apply, the change is not saved.

Workaround   Click any other cell in the table; then, click the Apply button.

•CSCei18858 (Related caveat ID: CSCei18705)

Symptom    After entering an invalid value or changing a value in the NE Explorer > NE Defaults tab, the CTM client hangs for approximately 3 minutes.
Conditions   If you change a value or enter a value in the NE Explorer > NE Defaults tab that is outside the valid range, the CTM client hangs for approximately 3 minutes. CTM does not perform fixed field validation on NE defaults values, so there is nothing to prevent you from entering an invalid value. There is no error message displayed before the client recovers.

Workaround   None.

•CSCei60347

Symptom    The DS3XM-12 NE Explorer > Customer Info tab does not show values for the transmux conversion ports, which are DS3XM-12 card ports used for VT-DS3 mapping.
Conditions   During circuit creation, if you check the VT-DS3 Mapping Conversion check box in the Routing Preferences pane, customer information data is not shown for the transmux conversion ports in the DS3XM-12 card slot NE Explorer.

Workaround   None. These ports are used internally for mapping only; customer and service IDs are not attached to these ports.

•CSCei79415

Symptom    When you choose NE Explorer > Configuration > Export NE Configuration, no data is exported for the NE or the cards. The file where the configuration is exported lists only tab names.
Conditions   See Symptom.

Workaround   None.

•CSCin62527

Symptom    The default RIP summary address is not created when activating RIP from CTM.
Conditions   If you launch the NE Explorer, click the Network tab > RIP subtab, check the RIP Active check box, and click Apply, no summary address is created.

Workaround   Manually create a default RIP address after activating RIP from CTM. Alternately, use CTC to activate RIP so that the default RIP address is created automatically.

•CSCin62975

Symptom    No range address is created when enabling Open Shortest Path First (OSPF) on a LAN from CTM.
Conditions   See Symptom.

Workaround   In CTM, manually provision the OSPF area range address for the respective range area IDs. In the NE Explorer, choose Network > OSPF Area Range; then, click the Create button. Alternately, enable OSPF from CTC so that the range address is created when OSPF is enabled.

•CSCin81696

Symptom    When a 1:1 protection group is created for a DS3XM card on an ONS 15454 NE, the protection group is not visible immediately.
Conditions   This problem occurs when you launch the ONS 15454 NE Explorer and click the Protection tab > Protection Groups subtab. If you create a 1:1 protection group that involves a DS3XM card, there is a delay of several minutes before the new protection group is visible.

Workaround   Wait several minutes for the protection group to appear.

•CSCin92735

Symptom    In the ONS 15600 SDH NE Explorer > Security tab, the Users, Active Logins, and Policy subtabs are missing.
Conditions   See Symptom.

Workaround   Use CTC to access the Users, Active Logins, and Policy subtabs.

•CSCsc76963

Symptom    If a line card is removed from a Cisco IOS XR-based NE during the time that CTM is collecting inventory data from that NE, the correct inventory data for that NE might not be collected. The line card data shown in the rack view of the NE Explorer or in the Equipment Inventory table might not match the inventory of the device.
Conditions   This problem occurs when a card is removed immediately after adding a Cisco IOS XR-based NE to CTM.

Workaround   Perform a manual resynchronization of the NE after the initial synchronization is complete. In the Domain Explorer, select the NE and choose Configuration > Cisco XR 12000 > Resync with NE. Avoid changing the physical configuration of the box until after the initial synchronization is complete. The Equipment Inventory table data is shown for XR 12000 NE types in the Domain Explorer > Configuration > Cisco XR 12000 > Equipment Inventory Table.

•CSCsc78688

Symptom    In the NE Explorer tree view, the card status for shared-port adapter (SPA) cards is not shown.
Conditions   This problem is seen when expanding the tree view for a Cisco IOS XR-based NE containing SPA cards.

Workaround   Determine the status using the show platform command in the CLI to the NE.

•CSCsc81404

Symptom    Power supplies are not shown in the tree view on the NE Explorer.
Conditions   This problem occurs for all Cisco IOS XR-based NE types when the tree view tree is expanded on the NE Explorer.

Workaround   View the power supply information from the Equipment Inventory table. From the Domain Explorer, select an NE, choose Configuration > Cisco XR12000 > Equipment Inventory Table, and look for power supply in the description column.

•CSCsc87190

Symptom    Applying configuration changes to a Cisco IOS XR-based NE from CTM fails with an error if the device was booted from memory.
Conditions   When you boot an NE from memory, the NE goes into an unsupported state and configuration changes cannot be applied. To detect whether the error occurred, select the NE from the Domain Explorer and look at the Software Version field on the Identification tab. It shows the version as 0.0.0.0. The show version CLI command returns 0.0.0.0.

Workaround   Diskboot the NE and resynchronize CTM with the NE.

•CSCsc97135

Symptom    The NE ID for the ONS 15600 cannot be modified and the description field is missing in the NE Explorer.
Conditions   See Symptom.

Workaround   None.

•CSCsc98405

Symptom    Cannot perform a forced soft reset on CTX cards in the ONS 15310 MA.
Conditions   See Symptom.

Workaround   None.

•CSCsc99394

Symptom    A Cisco IOS XR-based NE remains in the initializing or initializing-synch configuration for longer than five minutes.
Conditions   This behavior occurs when Secure Shell Protocol (SSH) communications are used between CTM and a Cisco IOS XR-based NE, and the SSH configuration is incorrect on the NE. No updates are seen in the Domain Explorer or NE Explorer for some XR 12000 or CRS-1 devices. The green check mark icon is not displayed to indicate completion of data collection and discovery.

Workaround   Delete the NE from CTM, then perform complete SSH configuration on the NE as outlined in the CTM user guide. Restart the NE service to clear the internal state. Add the NE back into CTM.

•CSCsc99849

Symptom    The MPLS interface option is not shown for PM statistics collection. PM threshold/statistics applications do not show the MPLS Interface Template window.
Conditions   See Symptom.

Workaround   None.

•CSCsd15380

Symptom    Operational status for interfaces on SPA cards is not shown correctly in the CTM inventory screens for Cisco IOS XR-based NE types.
Conditions   This problem applies to NEs that contain SPA cards.

Workaround   Use the CLI on the router to determine operational status.

•CSCsd17128

Symptom    SNMP traps are not received from an ENE if configuration is done from the CTM client.
Conditions   See Symptom.

Workaround   Use CTC to configure the SNMP settings.

•CSCsd21128

Symptom    Alarm profile management operations fail.
Conditions   When you apply an alarm profile from one type of NE to another, the following additional information is added to the Job Monitor table:

EID-1024: Exception:com.cisco.stardm.csm.api.CommfailureException:java.lang.NULlPointer Exception from Model Layer

Workaround   None.

•CSCsd21653

Symptom    A card with a warning is not colored correctly in the rack view.
Conditions   See Symptom.

Workaround   None.

•CSCsd31850

Symptom    On NE version 6.2, coding, framing, and AIS thresholds are editable in BITS-OUT on the ONS 15454 SONET and SDH. The issue is fixed in SDH but not in SONET.
Conditions   See Symptom.

Workaround   None.

•CSCsd37522

Symptom    When you try to launch the NE Explorer by double-clicking a GNE node, an error message is returned.
Conditions   This problem applies to a GNE/ENE setup of ONS 15454 nodes connected with patchcords. When you double-click one of the GNEs after it becomes reachable, an error message is returned.

Workaround   Launch the NE Explorer from the menu or toolbar. Alternately, install the CTM R7.2.0.230.1 patch. See Installing the CTM R7.2.0.230.1 Patch.

•CSCsd43544

Symptom    After changing the protection group name, the default name is still shown.
Conditions   When you use the NE Explorer > Protection tab to create a protection group between transponders and then change the name of the protection group you just created, the name is set correctly on the node and displayed correctly by CTC, but CTM continues to show the default protection group name. This problem also occurs if the default protection group name is changed when the protection group is created.

Workaround   None.

•CSCsd46817

Symptom    Cannot use the CTM NE Explorer to create a 2-fiber BLSR on the ONS 15327.
Conditions   CTC changed the related interface, but the corresponding change was not made in CTM.

Workaround   None.

•CSCsd46844

Symptom    The Squelch table is blank for ONS 15327 NEs but correct for ONS 15454 SONET NEs.
Conditions   This problem is due to a CTC interface change. The Squelch table is correct for ONS 15454 SONET NEs but blank for ONS 15327 NEs.

Workaround   None.

•CSCsd46879

Symptom    The FC-P counter for 15-minute or 1-day far-end STS thresholds shows near-end values instead of far-end values. Even if you change the values of FC-P to far end, the changes occur at the near end for the OC-192 XFP card.
Conditions   This problem is due to the incorrect usage of metadata.

Workaround   None.

•CSCsd47319

Symptom    The wrong reversion time option is shown in the Timing tab for ONS 15310 MA NEs.
Conditions   See Symptom.

Workaround   None.

•CSCsd48566

Symptom    In the CTM client, you cannot view or edit the SNMP community strings for an ONS 15600 that supports SNMP traps.
Conditions   This problem applies to an ONS 15600 NE that is reachable in CTM.

Workaround   None.

•CSCsd54727

Symptom    For 15-minute and 1-day near-end line thresholds, six thresholds are missing for OC-192 cards.
Conditions   If you open the NE Explorer for an ONS 15454 node that contains an OC-192 card and click the Line tab > Line Thresh 15-Min/Line Thresh 1-Day subtabs, the following parameters are missing at the near end: PSC-W, PSD-W, PSC-S, PSD-S, PSC-R, and PSD-R.

Workaround   None.

•CSCsd54772

Symptom    The Raise AIS for LOF option for DS1 cards on ONS 15454 NEs should be removed, because it is not applicable.
Conditions   See Symptom.

Workaround   None.

•CSCsd54810

Symptom    Cannot restart the laser for CTX cards in ONS 15310 CL nodes. The option to restart the laser is dimmed.
Conditions   The laser cannot be restarted when it is shut down and a manual restart is selected.

Workaround   None.

•CSCse57499

Symptom    Cannot provision reach and wavelength parameters for MRC_12 and OC-192 XFP cards on the ONS 15454 SONET and ONS 15454 SDH R7.2.
Conditions   If you launch the NE Explorer for an MRC_12 or OC-192 XFP card and try to change the Reach or Wavelength fields in the Line Config tab, the change is not applied in CTM and the value remains as N/A.

Workaround   None.

•CSCse63352

Symptom    Cannot set autodetect credits on an FC_MR card through CTM when the enable distance extension is not set.
Conditions   This problem occurs when the extension is set through CTC, but not through CTM.

Workaround   None.

•CSCse71474

Symptom    CTM supports two invalid admin states—OOS and OOS AINS—for ONS 15310 MA R7.2 NEs.
Conditions   In the NE Explorer, CTM shows OOS and OOS AINS as possible admin state values, even though the cards on the ONS 15310 MA R7.2 do not support these states and the operation fails.

Workaround   None.

•CSCse73643

Symptom    The detected line type is shown as E1_MF for DS3IN cards on ONS 15454 SONET NEs.
Conditions   This problem applies to ONS 15454 SONET NEs.

Workaround   None.

•CSCse74210

Symptom    The Squelch table is incorrect for ONS 15600 SDH NEs. For STM-64 two-fiber BLSRs, the Squelch table shows 96 entries. For STM-16 MS-SPRings, the Squelch table shows 25 entries. The table should show 32 entries for STM-64 and 8 entries for STM-16.
Conditions   This problem applies to ONS 15600 SDH NEs.

Workaround   None.

•CSCse79186

Symptom    Cannot perform read/write operations for reach and wavelength parameters on CTX cards on the ONS 15310 CL and ONS 15310 MA.
Conditions   See Symptom.

Workaround   None.

•CSCse80635

Symptom    An invalid admin state is supported for the RAN_SVC card on ONS 15454 SDH NEs.
Conditions   See Symptom.

Workaround   None.

•CSCse81636

Symptom    You can edit the DCC on a port where regenerator section DCC (RS-DCC) and MS-DCC are enabled.
Conditions   This problem applies to ONS 1545

Hierarchical Navigation

Cisco Transport Manager

Release Notes for Cisco Transport Manager 7.2

Downloads

Table Of Contents

Release Notes Cisco Transport Manager Release 7.2

Contents

Introduction

New Features and Functionality

Changes to the Release Notes

NE Software Releases Added

Caveats and Sections Added

Caveats and Sections Removed

CTM-Supported NE Software Releases

Adding the ONS 15310 CL R7.0.5 to the Supported NE Table

Adding the ONS 15310 CL R7.2.2 to the Supported NE Table

Adding the ONS 15310 CL R7.2.3 to the Supported NE Table

Adding the ONS 15310 MA R7.0.5 to the Supported NE Table

Adding the ONS 15310 MA R7.2.2 to the Supported NE Table

Adding the ONS 15310 MA R7.2.3 to the Supported NE Table

Adding the ONS 15327 R4.1.82 to the Supported NE Table

Adding the ONS 15327 R5.0.4 to the Supported NE Table

Adding the ONS 15327 R7.0.5 to the Supported NE Table

Adding the ONS 15327 R7.2.2 to the Supported NE Table

Adding the ONS 15327 R7.2.3 to the Supported NE Table

Adding the ONS 15454 SONET R4.1.82 to the Supported NE Table

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

Adding the ONS 15454 SONET R7.0.4 to the Supported NE Table

Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table

Adding the ONS 15454 SONET R7.2.2 to the Supported NE Table

Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.3 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.4 to the Supported NE Table

Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table

Adding the ONS 15454 SDH R7.2.2 to the Supported NE Table

Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table

Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table

Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table

Adding the MGX Voice Gateway R5.3.00 to the Supported NE Table

Third-Party Patches and Security Notices

CTM-Supported JRE and Apache Versions

Resolved Caveats

Installing the CTM R7.2.0.230.1 Patch

Determining What CTM Patch Is Currently Installed in the CTM System

Backing Up the CTM Database Before Installing the CTM R7.2.0.230.1 Patch

Downloading the CTM R7.2.0.230.1 Patch

Installing the CTM R7.2.0.230.1 Server Patch on the Same or Separate Workstation(s)

Installing the CTM R7.2.0.230.1 Client Patch in Windows

Installing the CTM R7.2.0.230.1 Client Patch in Solaris

Open Caveats

Installation and Upgrade Caveats

CTM Client Caveats

Alarm Management

Circuit and Link Management

User Management

Data Services

Domain Explorer

NE Explorer