Guest

Cisco Transport Manager

Release Notes for Cisco Transport Manager 9.2

  • Viewing Options

  • PDF (931.6 KB)
  • Feedback
Release Notes for Cisco Transport Manager Release 9.2

Table Of Contents

Release Notes for Cisco Transport Manager Release 9.2

Contents

Introduction

New Features and Functionality

Changes to the Release Notes

NE Software Releases Added

Sections and Caveats Added

CTM-Supported NE Software Releases

Third-Party Patches and Security Notices

Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234

Installing the CTM-Supported Critical Oracle Patch 12419249

CTM-Supported JDK and Apache Versions

Resolved Caveats—CTM R9.2 and CTM R9.2T

Resolved Caveats—CTM R9.2

Installing the Latest CTM R9.2 Patch or Service Pack

Using the Bug Toolkit to View Caveat Information

Search Bugs

Export to Spreadsheet

Open Caveats

Installation and Upgrade Caveats

CTM Client Caveats

Alarm Management

Circuit and Link Management

Data Services

Domain Explorer

NE Explorer

Network Map

Performance Monitoring

Miscellaneous

CTM Server and Database Caveats

Cisco Transport Controller Caveats

High Availability Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15305

Cisco ONS 15310

Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET

Cisco ONS 15454-M2 and Cisco ONS 15454-M6

Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Transport Manager Release 9.2


October 14, 2011

These release notes describe the caveats for Cisco Transport Manager (CTM) Release 9.2. These release notes accompany the Cisco Transport Manager Release 9.2 User Guide, the Cisco Transport Manager Release 9.2 Installation Guide, and the Cisco Transport Manager Release 9.2T 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 JDK and Apache Versions

Resolved Caveats—CTM R9.2 and CTM R9.2T

Resolved Caveats—CTM R9.2

Installing the Latest CTM R9.2 Patch or Service Pack

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) 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 9.2, CTM supports the Cisco Optical Networking System (ONS) family of optical NEs, the Cisco MGX 8880 Voice Gateway and MGX 8850/8830 Voice-Enabled Multiservice Switch, and the Cisco MDS 9000 Multilayer Director and Fabric Switch.

In Release 9.2T, CTM supports only the ONS family of optical NEs.

New Features and Functionality

The following tables describe the new features and functionality in CTM R9.2:

New Features in CTM R9.2

New Features in CTM R.9.2.460.8

Table 1 New Features in CTM R9.2 

New Feature
Description
Database Enhancements

Database migration from:

CTM R9.0 to R9.2

CTM R9.1 to R9.2

You can upgrade your CTM installation and migrate database information from CTM R9.0 or R9.1 to R9.2.

CTM Data Migrator wizard

You can use the CTM Data Migrator wizard to migrate select data from CTM R8.5 or later to CTM R9.2 or 9.2T. With the new wizard, you can migrate a subset of an existing CTM database to a newly installed CTM R9.2 or 9.2T server.

You cannot migrate your entire database. (If you want to migrate your entire database, see Chapter 4 in the Cisco Transport Manager Release 9.2 Installation Guide.)

The CTM Data Migrator wizard simplifies the migration because it imports data directly on a newly installed CTM R9.2 or 9.2T server, instead of upgrading the OS, upgrading and patching Oracle, and so on.

Note For CTM R9.2, this feature is available in CTM R9.2.0.400.4 or later. For CTM R9.2T, this feature is available in CTM R9.2.0.730.5 or later.

Support for embedded Oracle database

Note MGX support has been removed in CTM R9.2T.

Installing CTM R9.2T with an embedded Oracle database offers the following advantages:

The CTM installer checks all prerequisites and installs Oracle automatically. The installation includes any required Oracle patches.

Improved security: The oracle user account, SYSDBA Oracle credentials, and CTM database user credentials are hidden and can be changed and used only by Cisco for troubleshooting and configuration.

User-friendly tools let you browse the schema.

Redo logs and archive files are reorganized to save disk space.

You can restore the database to the most recent backup, or to a saved checkpoint.

The database has automatic resilience, including automatic checks of problems, health checks, and automatic management of tablespace fragmentation.

With an embedded Oracle database, you cannot:

Manage MGX devices.

Change the credentials of the oracle user, Oracle SYSDBA user, or CTM database user.

Use third-party tools to connect to the CTM Oracle database.

Modify the Oracle installation (for example, by patching it).

Use the Oracle Enterprise Manager to manage the database.

For information about installing CTM R9.2T, see the Cisco Transport Manager Release 9.2T Installation Guide. For information about using CTM R9.2T, see the Cisco Transport Manager Release 9.2 User Guide.

Server/Client Platform Enhancements

Ability to export the entire Equipment Inventory table

You have the option to export the entire Equipment Inventory table to a text file.

Ability to configure CTM server ports used for CTM GateWay/CORBA from the CTM client

A new Port Configuration tab is available from the CTM GateWay/CORBA Service pane. The Port Configuration tab allows you to configure the following CTM server port values:

Name service

Notification service

EMS session

Event notification port range

Server-to-client port range

Automatic software version check for NE activation

CTM automatically checks and lists any unsupported software versions when activating software or reverting software to an earlier version on an NE.

New NE Type column in the NE Software table

For ONS 15454 NEs, the NE type values are:

DWDM—For ONS 15454 MSTP R9.2 or later NEs.

TDM—For ONS 15454 MSPP R9.2 or later NEs.

Not Available—For all other NE versions.

Ability to configure a SOCKS v5 proxy server IPv4 address and port value to manage connectivity through network firewalls

In many networks, the CTM server is installed on a host behind a firewall, while the CTM client is installed on a host outside a firewall.

The firewall is the gateway for all TCP/IP connections to a private network. The firewall filters all connections using a set of configurable policies that determine whether a connection can be established with hosts behind the firewall, with the private network's hosts, and with hosts outside the firewall.

You can configure a SOCKS v5 proxy server. The SOCKS protocol tunnels the following connections to a firewall in a controlled manner:

All random GateWay/CORBA ports

The default JMOCO port (27613)

The JDBC connection port (1521)

In the Control Panel > Recovery Properties pane, you can associate each CTM server with a SOCKS host.

Ability to configure a three-character username

The minimum CTM username length is now three characters. In earlier CTM releases, the minimum username length was six characters.

Optical Enhancements

Support for CTC-based NE Release 9.2

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

ONS 15310 MA SDH R9.2

ONS 15310 MA SONET R9.2

ONS 15454 MSTP (ANSI/ETSI) R9.2

ONS 15454 MSPP (SONET/SDH) R9.2

ONS 15454-M6

ONS 15454-M2

Support for new optical cards

CTM manages the following new cards on optical devices:

40G-MXP-C

80-WXC-C

TNC—The Transport Node Controller (TNC) card combines the functions of multiple cards such as TCC2P, OSCM, ISC, and AIC-I. This is a controller card for ONS 15454-M2 and ONS 15454-M6.

TSC—The Transport Shelf Controller (TSC) card combines the functions of multiple cards such as TCC2P, ISC, and AIC-I. This is a controller card for ONS 15454-M2 and ONS 15454-M6.

TCC3—The Timing Communications Control Three (TCC3) card is an enhanced version of the TCC2P card. The primary enhancements include increased memory size and compact flash space. The TCC3 card boots up as a TCC2P card in older releases and as a TCC3 card from CTM R9.2 onward.

ONS 15454 multishelf NEs support up to 30 shelves and racks

In earlier CTM releases, a multishelf NE could support up to 12 shelves and racks. In CTM R9.2, a multishelf NE supports up to 30 shelves and racks.

Discovery of DWDM pluggable line insertion modules (PLIMs) on the Cisco Carrier Routing System 1 (CRS-1) R3.9.0 and R3.9.1

CTM R9.2 supports the discovery of DWDM PLIMs on the CRS-1 R3.9.0 and R3.9.1. CTM discovers the CRS-1 DWDM PLIMs through ONS 15454 NEs.

New Voltage/Temperature tab

A new Voltage/Temperature tab under the General subtab of the node properties pane is shown for the following NEs:

ONS 15454 SONET/SDH (M2/M6/Multishelf) R9.1 and R9.2

ONS 15310 CL R9.2

ONS 15310 MA R9.2

ONS 15310 MASDH R9.2

ONS 15600 SONET

ONS 15600 SDH

Ability to monitor performance parameters for ADM-10G cards

The LEX PM table provides monitoring of performance parameters related to HDLC particular framing (LEX) on optical interfaces.

Ability to manually discover NEs and add them to specific network partitions

In CTM R9.2, you can choose the mode of discovery for undiscovered NEs. In earlier CTM releases, the discovery mode was limited to Automatic. Using this feature, you can manually discover the NEs when needed, control the details retrieved during the discovery process, and add them to the desired network partitions.

Support for new payload types

CTM R9.2 supports the IB_5G payload for the following cards:

TXP_MR_10EX

OTU2_XP

CTM R9.2 supports the FE payload on RAD Small Form-Factor Pluggable (SFP) for the following cards:

CE-MR-6 (ONS 15310)

CE-MR-10 (ONS 15454 MSPP)

ML-MR-10 (ONS 15454 MSPP)

GE-XPE (ONS 15454 MSTP)

CTM R9.2 supports the CWDM XFP payload for the following cards:

GE-XP

GE-XPE

10GE-XP

10GE-XPE

OTU2-XP

40G-MXP

ADM-10G

CTM R9.2 supports the STM-16 L1 payload for the MXP_2.5G_10G card.

Ability to add a Data Communications Network (DCN)-connected network that can be split across several network partitions

When you add an NE whose source and destination belong to nodes in different network partitions, the Circuit table displays the circuit as a split network.

Layer 1 Enhancements

Ability to open the Link Utilization table for OTS links

For OTS links between NEs that belong to different network partitions, you can launch the Link Utilization table from:

The Link table > Configuration menu

OTS links in the Network Map

Circuit provisioning for optical channel network connection (OCHNC) circuits

You can select a local drop or a local source when you select the OCHNC circuit source or circuit destination.

Automatic link deletion in the purge phase of NE deletion

All links from NEs are deleted automatically during the purge phase of NE deletion. The purge process does not start if there are valid links on the NEs scheduled for permanent deletion. You must wait until all links on the NE become invalid; then, try again.

Reduction of time required to calculate route constraints during automatic routing

By means of a single click, you can exclude all nodes associated with a source and destination node. Later, you can selectively add back the desired nodes, which were previously excluded, to be considered for route constraints calculation. This is particularly helpful for large networks.

Improved topology behavior

The following behavior has been modified:

Links are no longer set as nonroutable when NEs are marked as Out Of Service.

Split topologies occur only when links are deleted.

Invalid links, resulting from NEs being marked as Out of Service, are now visible in the Create Circuit wizard. However, the links cannot be used for routing.

MGX Enhancements

Support for new MGX Voice Gateway releases. (This feature is not supported in CTM R9.2T.)

Expands CTM scope to include OAM&P for the following MGX releases:

Cisco MGX 8880 Media Gateway R5.6

Voice-Enabled Cisco MGX 8850 Multiservice Switch R5.6

Voice-Enabled Cisco MGX 8830 Multiservice Switch R5.6

VXSM R5.6

Note Basic MGX device synchronization is supported. Data and voice features are not supported.


The following table describes the new PER and MGX data and voice features and functionality supported in MGX 5.6, MGX 5.6.10, MGX 5.6.20, and PER for CTM R9.2.460.8.


Note For specific MGX limitations, see the release notes delivered with your MGX device.


Table 2 New Features in CTM R.9.2.460.8 

New Feature
Description
How to Access Feature
MGX Enhancements

Support for Text over IP

Text over IP (ToIP) is a means of providing a real-time text service that operates over IP-based networks. TTY text phones use ToIP for transmitting messages from one phone to another. VXSM supports Text Relay and TTY Upspeed for transmitting text characters using TTY phones. ToIP is supported in all VXSM cards and in all protocols with the FMC Codec template. CTM allows you to do the following:

Configure text relay profiles and parameters.

Add, modify, and delete text relay profiles.

Associate text relay profiles through event mapping.

To manage a text relay profile, from the Configuration Center, select VXSM Card > VBD tab > Text Relay Profile.

To manage event mapping, from the Configuration Center, select VXSM card > VBD tab > Event Mapping.

Enable/disable digital signal processor (DSP) redownload

When a DSP core fails, VXSM brings the core back in service by redownloading the DSP image on the entire DSP chip. For active and standalone VXSMs, the existing calls on the chip are moved to other available cores before the image redownload.

Enable or disable DSP redownload by selecting a VXSM card in the Configuration Center and setting true/false using Configuration > MGX Voice Gateway > Configuration Center > Media Gateway > Gateway Capabilities > DSP Redownload Enabled.

Enable/disable RTP Multiplexing

RTP Multiplexing enables VXSM to optimize the use of IP bandwidth between two gateways. VXSM achieves this by reducing the RTP header size and multiplexing different RTP session payloads into a single UDP payload. In RTP Multiplexing, the RTP sessions destined for a particular IP address are multiplexed into a single IP datagram.

Bandwidth optimization can also be achieved through Compressed RTP (CRTP). CRTP can be used to compress/decompress RTP traffic on Point-to-Point connection mode only. However, it causes the following:

Results in packet loss that causes poor service quality.

Due to long delay, more packets are discarded before the context is repaired.

Enable or disable RTP Multiplexing by selecting a VXSM card in the Configuration Center and setting true/false using Configuration > MGX Voice Gateway > Configuration Center > Media Gateway > Gateway Capabilities > RTP Multiplexing Enabled.

Management information base (MIB) support for V23 mode

CTM provides MIB support for V23 mode on VXSM OC3 cards in H248 protocols only.

Enable or disable V23 mode by selecting a VXSM card in the Configuration Center and setting true/false using Configuration > MGX Voice Gateway > Configuration Center > Media Gateway > Gateway Capabilities > V23 Mode Enabled.

MIB support for named signaling event (NSE) negotiation

Named signaling events are Cisco proprietary events that are used to notify peer gateway of upspeed and downspeed. CTM provides MIB support to enable or disable NSE negotiation.

Enable or disable NSE negotiation by selecting a VXSM card in the Configuration Center and setting true/false using Configuration > MGX Voice Gateway > Configuration Center > Media Gateway > Gateway Capabilities > Nse Negotiation Enabled.

SNMP Support for SVC between PXM and RPM-XF

CTM supports switched virtual circuit (SVC) connection between processor switching module (PXM) and router processing module (RPM). The connection details are updated in the database, which prevents faulty alarms from being generated at the node level. SVC connection can be viewed from the CTM GUI only. You cannot add, modify, delete, or perform diagnostic operations from the GUI.

While creating multiple SVC connections between PXM and RPM from the MGX CLI, you must use a different VPI.VCI. If you create multiple connections using the same VPI.VCI, the MGX2 platform identifies only one connection, and reports only the first connection from PXM. Subsequent connections are incomplete. The following message is displayed:

SVC already exist with same rvpi,rvci. 
Only one SVC connection with same 
rvpi,rvci will be written in PNNI config 
file and will be reported to NMS Server. 
Please confirm svcifconfig: Do you want 
to proceed (Yes/No)?

View a SVC connection by selecting a VXSM card in the Configuration Center using Connection tab > Connection List.

Support for Multiple codec string

CTM allows you to configure alternative strings for AAL5 codecs along with the existing strings on all VXSM cards with all protocols and in all templates.

Add alternate codec strings by selecting a VXSM card in the Configuration Center using Codec tab > Details column.

Support for Bearer IP Pool

The Multiple Bearer IP Pool feature allows interworking between two or more gateways residing on different private networks. VXSM acts as an interconnect gateway and provides a different set of IP addresses for each private network based on a predefined rule on the call agent (PGW).

To add a Bearer pool, select a VXSM card in the Configuration Center using Media Gateway > GatewayPool.

To add a Bearer IP pool, select a VXSM card in the Configuration Center using Media Gateway > GatewayIpPool.

To access the two new H.248 packages VPND and EVPND, select a VXSM card in the Configuration Center using H.248 > Termination Type > Create.

Preference for Codec Negotiation

CTM allows you to specify the codec negotiation preference as either remote or local. Only H.248 protocol in all VXSM cards supports codec negotiation.

Enable or disable codec negotiation by selecting a VXSM card in the Configuration Center and setting true/false using Configuration > MGX Voice Gateway > Configuration Center > Media Gateway > Gateway Capabilities > Codec Negotiation Local Preference.

PER Enhancement

Support for Virtual Media Gateway (VMG)

CTM supports VMG enhancement for PER by configuring VMG along with the VMG domain name. You can do the following:

Configure the MG-MGC association for H.248 protocol with the VMG domain name.

Modify the VMG domain name in H.248 configuration.

Mapping the VMG domain name to domain names.

Mapping the VMG domain name to H.248 association.

Mapping the VMG domain name to extended H.248 association.

Mapping the VMG domain name to Media Gateway Controller (MGC).

Mapping the VMG domain name to Voice Quality Monitoring (VQM).

Configure VMG in the Configuration center using H.248 > MG-MGC Association > Create.


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

NE Software Releases Added

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

Automatically added to CTM when the patch or service pack is installed:

ONS 15454 SONET R9.2.0.3

ONS 15454 SDH R9.2.0.3

Sections and Caveats Added

The following were added:

Table 2, "New Features in CTM R.9.2.460.8". Includes descriptions of PER and MGX data and voice features that were added in CTM R9.2.460.8.

Resolved Caveats—CTM R9.2 and CTM R9.2T. Includes all caveats that are resolved in CTM R9.2 and R9.2T.

The following caveats were added:

CSCth03477

CSCth97940

CSCti72307

CSCti90949

CSCtj06010

CSCtj70276

CSCtk00438

CSCtk48145

CSCtk60031

CSCtk62107

CSCtk95241

CSCtk95409

CSCtk96027

CSCtk98247

CSCtk99224

CSCtkl01324

CSCtl01263

CSCtl01522

CSCtl06299

CSCtl11227

CSCtl11270

CSCtl23021

CSCtl42434

CSCtl42638

CSCtl42648

CSCtl42812

CSCtl47122

CSCtl50071

CSCtl50355

CSCtl52951

CSCtl53108

CSCtl53250

CSCtl60411

CSCtl60447

CSCtl69065

CSCtl69996

CSCtl71105

CSCtl73675

CSCtl74392

CSCtl74413

CSCtl76288

CSCtl76340

CSCtl76891

CSCtl76905

CSCtl83153

CSCtl91069

CSCtl93740

CSCtn02279

CSCtn05685

CSCtn31705

CSCtn31738

CSCtn39199

CSCtt14314

CSCtq02022

CTM-Supported NE Software Releases

The following table lists the NE software releases supported in CTM R9.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 3 CTM-Supported NE Software Releases 

Product
Software Release
NE Version String

Cisco Carrier Routing System 1 (CRS-1)1

Release 3.9.0

03.90

Release 3.9.1

03.91

ONS 15216 100-GHz OADM1/2/4

Release 2.2.2

soadma.out-Ver2.2.2, soadmb.out-Ver2.2.2

Release 2.2.3

soadma.out-Ver2.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)

Passive

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 15305

Release 2.0.2

2.0.2

Release 2.0.3

2.0.3

Release 2.0.4

2.0.4

ONS 15305 CTC

Release 3.0.6

04.60-X08D-26.11

ONS 15310 CL

Release 7.2.3

07.23-007F-22.02

Release 8.5.1

08.51-008B-14.13

Release 8.6

08.60-009B-11.08

Release 8.6.1

08.61-010F-07.11

Release 9.0

09.00-008I-17.17

Release 9.1

09.10-009J-25.17

ONS 15310 MA SONET

Release 7.0.7

07.07-007L-03.20

Release 7.2.3

07.23-007F-22.02

Release 8.5.3

08.53-008J-17.07

Release 8.5.4

08.54-010D-30.09

Release 8.6

08.60-009B-11.08

Release 8.6.1

08.61-010F-07.11

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.1

09.10-009J-25.17

Release 9.2

09.20-010E-05.18

ONS 15310 MA SDH

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.1

09.10-009J-25.17

Release 9.2

09.20-010E-05.18

ONS 15327

Release 4.1.3

04.13-003L-19.01

Release 4.1.4

04.14-004C-09.23

Release 4.1.8.2

04.182-006-L2805

Release 7.0.5

07.05-007D-20.22

Release 7.2.3

07.23-007F-22.02

ONS 15454 SONET

Release 4.1.3

04.13-003L-19.01

Release 4.1.4

04.14-004C-09.23

Release 4.1.8.2

04.182-006-L2805

Release 7.0

07.00-005L-19.20

Release 7.0.1

07.01-006D-20.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.3

07.03-006I-29.09

Release 7.0.4

07.04-007A-08.16

Release 7.0.5

07.05-007D-20.22

Release 7.0.6

07.06-007H-08.13

Release 7.0.7

07.07-007L-03.20

Release 7.2.3

07.23-007F-22.02

Release 8.5

08.50-007I-19.18

Release 8.5.1

08.51-008B-14.13

Release 8.5.2

08.52-008E-25.04

Release 8.5.3

08.53-008J-17.07

Release 8.5.4

08.54-010C-12.19

Release 8.6

08.60-009B-11.08

Release 8.6.1

08.61-010F-07.11

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.0.2

09.02-009L-17.19

Release 9.1

09.10-009J-25.17

Release 9.2

09.20-010E-05.18

Release 9.2.0.32

09.203-010-H2606

Release 9.2.1

09.21-011A-11.15

Release 9.2.113

09.211-011-E2517

ONS 15454 SDH

Release 7.0.7

07.07-007L-03.20

Release 7.2.3

07.23-007F-22.02

Release 8.5

08.50-007I-19.18

08.50-P07I-19.18

Release 8.5.2

08.52-008E-25.04

08.52-P08E-25.04

Release 8.5.3

08.53-008J-17.07

Release 8.5.4

08.54-010C-12.19

Release 8.6

08.60-009B-11.08

Release 8.6.1

08.61-010F-07.11

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.0.2

09.02-009L-17.19

Release 9.1

09.10-009J-25.17

Release 9.2

09.20-010E-05.18

Release 9.2.0.34

09.203-010-H2606

Release 9.2.1

09.21-011A-11.15

Release 9.2.115

09.211-011-E2517

ONS 15454-M6

Release 9.2

09.20-010E-05.18-SPA

Release 9.2.1

09.21-011A-11.15-SPA

ONS 15454-M2

Release 9.2

09.20-010E-05.18-SPA

Release 9.2.1

09.21-011A-11.15-SPA

ONS 15530

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

ONS 15540 Extended Services Platform (ESP)

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

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

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

ONS 15600 SONET

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 9.0

09.00-008I-17.17

Release 9.1

09.10-009J-25.17

Release 9.2.1

09.21-011B-16.06

Release 9.2.116

09.211-011-E0905

ONS 15600 SDH

Release 8.0

08.00-007A-27.16

Release 9.0

09.00-008I-17.17

Release 9.1

09.10-009J-25.17

Release 9.2.1

09.21-011B-16.06

Release 9.2.117

09.211-011-E0905

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.4(30.200)

MGX VG 5.4(30.200)

Release 5.5(10.200)

MGX VG 5.5(10.200)

Release 5.6.(0.200)

MGX VG 5.6(0.200)

Release 5.6(10.200)8

MGX VG 5.6(10.200)

Release 5.6(20.200)8

MGX VG 5.6(20.200)

Voice-Enabled Cisco MGX 8830 Multiservice Switch

Release 5.4(30.200)

MGX VG 5.4(30.200)

Release 5.5(10.200)

MGX VG 5.5(10.200)

Release 5.6(0.200)

MGX VG 5.6(0.200)

Release 5.6(10.200)9

MGX VG 5.6(10.200)

Release 5.6(20.200)9

MGX VG 5.6(20.200)

Voice-Enabled Cisco MGX 8850 Multiservice Switch

Release 5.4(30.200)

MGX VG 5.4(30.200)

Release 5.5(10.200)

MGX VG 5.5(10.200)

Release 5.6(0.200)

MGX VG 5.6(0.200)

Release 5.6(10.200)10

MGX VG 5.6(10.200)

Release 5.6(20.200)10

MGX VG 5.6(20.200)

VISM-PR

Release 3.3.25

3.3.25

Release 3.3.30

3.3.30

Release 3.3.35

3.3.35

VXSM

Release 5.4.20

5.4.20

Release 5.4.21

5.4.21

Release 5.5.10

5.5.10

Release 5.6.00

5.6.00

Release 5.6.1011

5.6.10

Release 5.6.2011

5.6.20

1 You cannot manually add the CRS-1 to CTM via the Add New NE wizard. The only way to add a CRS-1 to CTM is as an autodiscovered NE. A Link Management Protocol (LMP) link must be configured between the ONS 15454 and the CRS-1; then, CTM autodiscovers the CRS-1.

2 For CTM R9.2T to support the ONS 15454 SONET R9.2.0.3, you must install the CTM R9.2.0.730.5 or later patch. For CTM R9.2 to support the ONS 15454 SONET R9.2.0.3 and ONS 15454 SDH R9.2.0.3, you must install the CTM R9.2.0.435.4 or later patch.

3 For CTM R9.2 to support the ONS 15454 SONET R9.2.11, you must install the CTM R9.2.0.4354 or later patch.

4 For CTM R9.2T to support the ONS 15454 SDH R9.2.0.3, you must install the CTM R9.2.0.730.5 or later patch. For CTM R9.2 to support the ONS 15454 SDH R9.2.0.3, you must install the CTM R9.2.0.435.4 or later patch.

5 For CTM R9.2 to support the ONS 15454 SDH R9.2.11, you must install the CTM R9.2.0.435.4 or later patch.

6 For CTM R9.2 to support the ONS 15600 SONET R9.2.0.3, you must install the CTM R9.2.0.435.4 or later patch.

7 For CTM R9.2 to support the ONS 15600 SDH R9.2.0.3, you must install the CTM R9.2.0.435.4 or later patch.

8 For CTM R9.2 to support the Cisco MGX 8880 Media Gateway R5.6.10 and R5.6.20, you must install the CTM R9.2.460.8 or later patch.

9 For CTM R9.2 to support the Cisco Voice-Enabled Cisco MGX 8830 Multiservice Switch R5.6.10 and R5.6.20, you must install the CTM R9.2.460.8 or later patch.

10 For CTM R9.2 to support the Voice-Enabled Cisco MGX 8850 Multiservice Switch R5.6.10 and R5.6.20, you must install the CTM R9.2.460.8 or later patch.

11 For CTM R9.2 to support VXSM R5.6.10 and R5.6.20, you must install the CTM R9.2.460.8 or later patch.


Third-Party Patches and Security Notices

Cisco periodically reviews the known Oracle patch alerts, 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.

Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234

Oracle released the Patch Set Update (PSU) patches 9352164 and 9952234. CTM R9.2.0.400.4 has been tested with these patches (see CSCtj72766). To install the Oracle patches 9352164 and 9952234, complete the following steps:


Step 1 Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink username and password.

Step 2 Select Patch from the menu and search for and download patches 9352164 and 9952234.

Step 3 Extract the README.html file from the Oracle PSU patch .zip file. As you read the README.html file, note that the CTM database has the following setup:

Oracle environment: Non-RAC.

Data Guard Physical Standby database: Not implemented.

Job Scheduling system: Used.

ASM instance: Not implemented.

Initial setup: Oracle 10.2.0.4.2; CTM R9.2.0.363 installed on the CTM server.

Step 4 Refer to the README.html file as you complete the following substeps:

a. Uninstall the PSU patch 10.2.0.4.2. (See the "Patch Deinstallation" paragraph in the README.html file. The PSU patch number is 8833280.)

b. Install the PSU patch 10.2.0.4.4. (See the "Patch Installation Instructions" paragraph in the README.html file. The PSU patch number is 9352164.)

c. As the root user, enter the following command:

sh psu_root.sh
 
   

Note If ORACLE_HOME is not set, the psu_root.sh script fails. By default, the $ORACLE_HOME directory is /oracle/product/10.2.0.


d. Check for any one-off patch conflicts with the PSU patch 10.2.0.4.6. (See the "One-Off Patch Conflict Detection and Resolution" paragraph in the README.html file.)

e. Install the PSU patch 10.2.0.4.6. (See the "Patch Installation Instructions" paragraph in the README.html file. The PSU patch number is 9952234.)

f. Enter the following command to load the modified SQL files into the database. (See the "Loading Modified SQL Files into the Database" paragraph in the README.html file.)

catbundle.sql psu apply
 
   

g. Enter the following commands to recompile views in the database. (See the "Recompiling Views in the Database Instructions" paragraph in the README.html file.)

recompile_precheck_jan2008cpu.sql
view_recompile_jan2008cpu.sql
utlrp.sql
 
   

h. Enter the following command to clean up the .patch_storage area:

$ORACLE_HOME/OPatch/opatch util cleanup
 
   

Installing the CTM-Supported Critical Oracle Patch 12419249

Oracle released the Critical Patch Set Update (CPU) patch 12419249. CTM R9.2.0.462.4 has been tested with these patches (see CSCtr99238). To install the Oracle patch 12419249, complete the following steps:


Step 1 Go to http://metalink.oracle.com and click Login to MetaLink. Enter your Oracle MetaLink username and password.

Step 2 Select Patch from the menu and search for and download patch 12419249.

Step 3 Extract the README.html file from the Oracle PSU patch .zip file. As you read the README.html file, note that the CTM database has the following setup:

Oracle environment: Non-RAC.

Data Guard Physical Standby database: Not implemented.

Job Scheduling system: Used.

ASM instance: Not implemented.

Initial setup: Oracle 10.2.0.4.2; CTM R9.2.0.462 installed on the CTM server.

Step 4 Refer to the README.html file as you complete the following substeps:

a. Install the CPU July 19, 2011 patch. (See the "Patch Installation Instructions" paragraph in the README.html file. The CPU patch number is 12419249.)


Note When you use the oracle command, opatch napply -skip_subset -skip_duplicate, some exceptions might occur. Use the command prompted by the installer or contact Oracle.


b. Enter the following command to load the modified SQL files into the database. (See the "Recompiling Views in the Database Instructions" paragraph in the README.html file.)

catbundle.sql psu apply
 
   

c. Enter the following commands to recompile views in the database. (See the "Recompiling Views in the Database Instructions" paragraph in the README.html file.)

recompile_precheck_jan2008cpu.sql
view_recompile_jan2008cpu.sql
utlrp.sql
 
   

d. Enter the following command to clean up the .patch_storage area:

$ORACLE_HOME/OPatch/opatch util cleanup
 
   

CTM-Supported JDK and Apache Versions

The following tables list the Java Development Kit (JDK) and Apache versions supported in CTM R9.2.

Table 4 CTM-Supported JDK Version 

JDK Version
Caveat ID
Caveat
Comment

1.6.0_20

This JDK version was used when CTM R9.2 was released.


Table 5 CTM-Supported Apache Version 

Apache Version
Caveat ID
Caveat
Comment

2.2.15

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


Resolved Caveats—CTM R9.2 and CTM R9.2T

The following table lists caveats that are resolved in CTM R9.2 and CTM R9.2T.


Note For more information on the latest caveats that have been resolved in the patches, see the corresponding Readme.


Table 6 Caveats Resolved in CTM R9.2 and CTM R9.2T 

Caveat ID
Caveat

CSCsq65717

The power monitor value (ELWBATVG or EHWBATVG) can only be changed once.

CSCsw69697

After a database migration, there are no modules available for debugging. The list under CTM Control Panel > Logging Properties > SNMP Trap Service Debug subtab is empty.

CSCsy87978

After clicking Cancel during an upgrade, the system does not revert to its previous state. This prevents the system from attempting another upgrade.

CSCsz63857

CTM reports the frequency of intermediate connection termination points (CTPs) for synchronous transport signal (STS) circuits instead of the STS specification.

CSCsz67234

After configuring many settings on an ADM-10G card, provisioning operations take a long time.

CSCsz70254

After upgrading from CTM R9.0, the ONS 1530x performance monitoring (PM) process is shown incorrectly as running.

CSCta08807

If you try to run the import_full_db.sh script while the CTM server is running, the script fails.

CSCta52764

The Active Channels column in the Optical Line tab does not update correctly.

CSCta98847

The CTM_CONFIG_TABLE is not migrated correctly and might affect PM services on MGX devices.

CSCtb41766

The time format in the Time Stamp field for real-time PM data does not match the server time format.

CSCtb55127

Exceptions are displayed and logged when NE services start up.

CSCtb97851

The CTM server fails to start. If a ctms-start command is issued, the command fails with the following error:

ctms-start: Command not found.

CSCtc11739

In the SVLAN Database Management wizard > Select a Resource pane, duplicate shelves are shown on multishelf NEs.

CSCtc12112

After setting the 24-hour time format, the 12-hour format still appears in some tables.

CSCtc22763

The getAllSupportedPTPs does not retrieve some CTP terminations.

CSCtc28066

CTM GateWay/CORBA displays invalid values for PMP_RXTOTALERRORS PM data.

CSCtc30664

Features are available to a user who is assigned to a custom profile with no CTM feature access.

CSCtc33113

An error message appears in the BLSR table when you try to edit a BLSR ring.

CSCtc33144

Occasionally, BLSR creation fails when the BLSR wizard is opened from the Domain Explorer. The following message error is displayed:

EID-1061: An error occurred while creating the ring provisioning

CSCtc40704

The getCTMHistoryPMData application program interface (API) reports the following unnecessary values: PMP_RXRUNTS, PMP_RXTOTALERRORS, and PMP_PORTDROPCOUNTS.

CSCtc58957

When you cut and paste an NE from one group to another in the Domain Explorer tree, the cut operation does not work.

CSCtc61863

When installing the CTM GateWay/CORBA option in either of the following high availability (HA) configurations, you must specify the virtual IP address on the Server IP Address screen:

Local redundancy configuration

Dual-node cluster geographical redundancy configuration

However, it is not clear in the Server IP Address screen that you should enter the virtual IP address, not the physical IP address.

CSCtc65216

CTM GateWay/CORBA does not start because the NameService process shuts down unexpectedly.

CSCtc79880

It takes a long time to launch CTC from an NE. The following message appears for several minutes: "Downloading ELE jars..."

CSCtc87376

The Force Channel Status and Force Channel fields are blank for SMR-C cards.

CSCtd00311

After upgrading, debug modules are missing from the Control Panel > Logging Properties pane > Basic Service Logging tab.

CSCtd18457

Alarm suppression cannot be set at the node level.

CSCtd21907

The Ack Time Stamp field in the Alarm Browser is blank.

CSCtd26062

After reconfiguring a circuit in Partial state, the circuit remains in Partial state and has incorrect circuit terminations.

CSCtd26217

The default CTM server installation path is incorrect.

CSCtd34174

Real-time PM data on ONS 15454 OSCM and OSC-CSM cards is incorrect.

CSCtd36677

When the network contains VCAT circuits, it takes a long time for the Circuit table to open.

CSCtd40324

CTM GateWay/CORBA incorrectly reports PTP trunk port data for cards with an OC-48 payload type.

CSCtd44168

The GetTopologicalLink API does not report the link count for server trail links.

CSCtd46787

The NE Explorer does not correctly show OPT-BST and OPT-PRE card ports.

CSCtd49122

The Domain Explorer tree is not updated after deleting or moving nodes.

CSCtd55103

You cannot use the PM Query by Category wizard to filter PM data by slot.

CSCtd60771

The ctmsetup.sh installation script overwrites the CTM GateWay/CORBA installation.

CSCtd60783

On the NE Explorer for the OTU_XP card > Line tab > VC4 Thresh subtab, the 15-minute and 1-day threshold values are inverted.

CSCtd61189

During CTM server maintenance, the Veritas Cluster Server (VCS) detects CTM_APACHE as offline, even if the Apache web server is running.

CSCtd63215

CTM client resynchronization is slow and an exception appears.

CSCtd75006

Filtering Audit Log data does not work correctly.

CSCtd75008

The SVLAN Profile wizard does not delete profiles on multiple NEs.

CSCtd78528

The Control Panel reports the wrong status of the CTM GateWay/CORBA service.

CSCtd81499

The getTPHistoryPMData API does not return any value when an MXP-MR-10DMEX card with an ISC3-PEER-1G or ISC-PEER-2G payload is provisioned.

CSCtd89038

An Oracle error message is displayed in the output of the import_full_db.sh script.

CSCtd94434

When the CTM server starts up, the ctms-start script displays the following error message:

ctms-start: /opt/CiscoTransportManagerServer/bin/store_procedure_in_cache.sh: not found

CSCtd99187

The CTM server installation quits with the error "Abort DB initialization due to sched_for_ctm_stats.sql." In the CTM GUI installer, an error message is displayed, although you can continue and terminate the installation.

CSCti13296

The PM service log file consumes all available space in the /tmp directory. When the /tmp directory is full, some operating system services are disrupted and Oracle sessions shut down, causing general application instability.

CSCti16526

TCA_EVENT_TABLE partitions are managed incorrectly. A new partition is created daily at 18:00 a.m. In the time frame between 00:00 a.m. and 18:00 p.m., PM alerts might not be shown.

Note This caveat is fixed with the latest CTM R9.2 patch and CTM R9.2T. See Installing the Latest CTM R9.2 Patch or Service Pack or the Cisco Transport Manager Release 9.2T Installation Guide.


Resolved Caveats—CTM R9.2

The following table lists caveats that are resolved only in CTM R9.2.


Note For more information on the latest caveats that have been resolved in the patches, see the corresponding Readme.


Table 7 Caveats Resolved Only in CTM R9.2 

Caveat ID
Caveat

CSCsf96351

After the CTM server restarts, SONET NEs do not come up.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtb98230

The CTM Alarm Browser does not display an alarm when the system uptime of service modules exceeds the threshold.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCth40538

The Alarm Browser Filter does not work.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCth71367

Navigating within the CTM client is slow, and the client freezes. If you launch a new CTM client, the following error is displayed:

EID-382: The CTM server is initializing. Please try again later.

(Related caveat ID: CSCti30435.)

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti33054

In the DS3_EC1_48 NE Explorer > DS3 tab > Line Config subtab, the Detected Line Type field does not show the M13 value.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti40572

After an ML card reboot, a CTM node resynchronization occurs.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti07957

In a dual-server configuration, the following functions stop working a few days after you run the import_full_db.sh script: PM collection, TCA event reporting, and the ability to disable logins.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti09988

The CTM GateWay/CORBA CreateTopologicalLink API returns an exception when creating SONET/SDH manual links. However, the manual link is created successfully.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti10164

Real-time PM data is not collected on a channel interface of an 80-WXC card installed in a multishelf environment with the shelf > 1.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti18733

Manual physical links are not created and do not appear in the Link table or the Network Map.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti70491

The CAP and BACKPLANE equipment state for the ONS 15600 NEs shows "Not present."

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti80797

The getCTMHistoryPMData API returns a PM data file with no data when layer rate 15 (LR_STS3c_and_AU4_VC4) or 14 (LR_STS1_and_AU3_High_Order_VC3) are used.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCti90949

The CTM server restarts intermittently after it receives an overwhelming number of events from network services. The server eventually crashes because it cannot manage the event load.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj01922

There is no CTM database table that reports the status (active or standby) of UPSR spans.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj06010

MGX GUI windows do not open because the UNIX permissions on the files in the /opt/CiscoTransportManagerServer/webServer/cgi-bin directory do not have read and execute permission for all users.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj67138

Historical optical PM data is not collected for 80_WXC_C cards on ONS 15454 SDH NEs.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj70276

The CTM server loses connectivity with NEs.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj72766

CTM must support the latest critical Oracle security patches.

Note You must install the Oracle security patches before installing the latest CTM R9.2 patch. See Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234.

CSCtj86600

The CIRCUIT_UPSR_BS_TBL database table is missing one of the rows for dual-ring interconnect (DRI) selectors.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj90800

A CTC-based network element never completes discovery.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtj92364

The Alarm Log displays the following error message: "EID-333: A database timeout occurred."

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk13119

The Section Trace tab shows no data for the OTU2_XP card.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk13137

The OTN Tab shows no data for a OTU2_XP card provisioned on a multishelf NE.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk13290

The service status is not automatically updated after activating or deactivating a service from the Control Panel.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk13351

Optical patchcords cannot be created if only OTU2_XP cards are provisioned inside the NE.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk13431

High CPU usage after bulk circuit creation.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk34613

LOS-P alarms are not reported by CTM on a fiber cut on an A/D SMR port.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk62107

The CTM server cannot start because the /db05 partition is full. The logarch function does not work.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk83953

The client_patch.bat installation script fails with the following message: "Unable to determine CTM client install location from registry. Please verify your installation and try again."

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtk98247

The Active status is not updated in the Protection tab for an ONS 15600 NE.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl05918

The Backup Upload feature does not work on CTM R9.2. The list of backup files is not shown.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl01777

When the PM data storage status is set to Optimized, Ethernet PM values are not stored in the database.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl46593

In the ASAP_4 card NE Explorer > VC tab, when there are multiple circuits created on the same port, CTM shows only one row with a VC ID of 1. Instead, CTM should show multiple rows, one row for each circuit (with a unique VC ID) on the port.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl46849

High-order SDH PM data is not collected for ONS 15600 SDH NEs.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl50080

The VC value is incorrect in the VC tab of an ONS 15600 NE STMxx card.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl50355

DCC termination points of an ONS 15600 NE ASAP card are not shown from the DCC tab.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl69065

After CTM9.2 363 MGX installation, an outdated svplus directory is found in the svplus directory.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl74392

An error does not appear when OTU2_XP card mode settings are not updated. Instead, the card mode change appears successful even when settings have not been changed.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl76288

When you configure multiple settings on an OTU2_XP card using NE explorer, CTM shows an error.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtl83275

The CTM R9.2 client periodically freezes.

CSCtn02782

The Line tab does not open on an ONS 15454 SDH NE STMxx card.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtn05639

Sometimes OTN FEC PM data is not collected on an OTU2_XP card.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtn30937

The MGX SRT tool reports GMT time zone instead of local time zone.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtn31705

The manage_cdump.sh script generates an output even when no core files exist.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack

CSCtn31738

When filtering CTM tables on MSNE, only shelf 1 results are displayed.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack

CSCtn39718

Cannot install the client patch if the installation directory name contains a blank space.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtn53940

NEs are not discovered completely and are stuck in Sync Config state.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtn76520

CTM is unable to retrieve 15454 NE default data.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCto06069

Excessive logging causes a blocked dispatcher thread in log4j. This problem applies to all CTC-based NEs.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCto87956

Sometimes you cannot launch CC, DC, or the Statistics report.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq52315

When you log into CTM in compress mode, loss of communication (LOC) and CTM server memory exhaustion can occur.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq61782

Gateway/CORBA APIs (setTCATPParameter and getTCATPParameter) return an exception on VC3 circuits of the DS3 cards.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq63737

Drag-and-drop functionality is not available for customized network admin users.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq75476

Unable to set Reach and Wavelength values on trunk ports for cards.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq75502

The getAllVCATSNCs API returns an exception when you use a filter.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq81999

The Error log contains many exceptions causing network service instability.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtq92100

The network admin user cannot delete NEs when the NEs are added directly to the CTM Domain for Superuser.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr11501

Port wavelengths are not available on OTU2XP when provisioned on MSPP nodes.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr17242

GateWay/CORBA APIs (getAllTopologicalLinks, getAllTopologicalLinksForME, and getAllTopLevelTopologicalLinks) used to retrieve topological links also incorrectly retrieve tunnel circuits (VTT/VCT).

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr21390

Unable to start CTM 9.2.0.435 client on Solaris machine when the user is not logged as a root user.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr25638

The CTM 9.2 client must support java 1.6.0_26 version.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr52100

The NE explorer does not display WSS cards after the software upgrade to 9.2. The Equipment inventory table is blank for WSS cards.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr72971

CTM Gateway/CORBA takes time to start and the status in control panel is not aligned properly.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCtr99238

CTM must support the latest critical Oracle security patches.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts00126

CTM backup fails.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts57158

CTM provides support for Apache web server 2.2.21.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts69708

CTM displays 1+1 protection group on MRC cards incorrectly.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts74778

cwmftpd process restarts when unexpected network latencies occur.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts85699

When you run the application on a remote display, the Data Migrator performance slows down.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

CSCts95528

CTM continously retries to add to the DB partial circuits using VAP or LAP circuits.

Note This caveat is fixed with the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


Installing the Latest CTM R9.2 Patch or Service Pack

Detailed instructions on how to download and install a CTM patch or service pack are provided in the readme file that accompanies the patch or service pack.

See the Cisco Transport Manager Readme Files section at http://www.cisco.com/en/US/products/sw/opticsw/ps2204/prod_release_notes_list.html.


Caution Do not install:
- A CTM R9.2 patch on systems running CTM R9.2T.
- A CTM R9.2T patch on systems running CTM R9.2.

Using the Bug Toolkit to View Caveat Information

This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release through the following subsections:

Search Bugs

Export to Spreadsheet

Search Bugs

This section explains how to use the Bug ToolKit to search for a specific bug or to search for all the bugs in a specified release.


Step 1 Go to http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.

You will be prompted to log into Cisco.com. After you login, the Bug Toolkit page opens.

Step 2 Click Launch Bug Toolkit.

Step 3 To search for a specific bug, enter the bug ID in the Search for Bug ID field and click Go in the Search Bugs tab.

To search for all the bugs in a specified release, enter the following search criteria in the Search Bugs tab:

Select Product Category—Network Management and Automation.

Select Products—Cisco Transport Manager.

Software Version—9.2.

Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, select Use custom settings for severity, status, and others and provide the following information:

Severity—Select the severity level.

Status—Select Open, Fixed, or Terminated.

Select Open to view all the open bugs. To filter the open bugs, clear the Open checkbox and select the appropriate sub-options that appear below the Open checkbox. The sub-options are New, Held, More, Open, Waiting, Assigned, Forwarded, Postponed, Submitted, and Information Required. For example, if you want to view only new bugs in Cisco Transport Manager 9.2, select New.

Select Fixed to view fixed bugs. To filter fixed bugs, clear the Fixed checkbox and select the appropriate sub-options that appear below the fixed checkbox. The sub-options are Resolved or Verified.

Select Terminated to view terminated bugs. To filter terminated bugs, clear the Terminated checkbox and select the appropriate sub-options that appear below the terminated checkbox. The sub-options are Closed, Junked, and Unreproducible. Select multiple options as required.

Advanced—Select the Show only bugs containing bug details checkbox to view only those bugs that contain detailed information, such as symptoms and workarounds.

Modified Date—Select this option if you want to filter bugs based on the date on which the bugs were last modified.

Results Displayed Per Page—Select the appropriate option from the list to restrict the number of results that appear per page.

Step 4 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.


Export to Spreadsheet

The Bug ToolKit provides the following options to export bugs to a spreadsheet:

Click Export All to Spreadsheet link in the Search Results page under the Search Bugs tab. Specify file name and folder name to save the spreadsheet. All the bugs retrieved by the search will be exported.

Click Export All to Spreadsheet link in the My Notifications tab. Specify file name and folder name to save the spreadsheet. All the saved bugs in all the groups will be exported.

If you are unable to export the spreadsheet, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information or call Cisco TAC (1-800-553-2447).

Open Caveats

The following section lists open caveats in Cisco Transport Manager 9.2 as of August 30, 2011. To view more details and possible workaround information for a particular bug, see Using the Bug Toolkit to View Caveat Information.

Installation and Upgrade Caveats

CTM Client Caveats

Alarm Management

Circuit and Link Management

Data Services

Domain Explorer

NE Explorer

Network Map

Performance Monitoring

Miscellaneous

CTM Server and Database Caveats

Cisco Transport Controller Caveats

High Availability Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15305

Cisco ONS 15310

Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET

Cisco ONS 15454-M2 and Cisco ONS 15454-M6

Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH


Note Some of the caveats are resolved in a CTM R9.2 patch. In such cases, the patch that contains the fix is indicated as a workaround.


Installation and Upgrade Caveats


CSCtf84240

Symptom    When the CTM client is installed on Solaris, the following file is created under the CTM client installation directory: @LongLink (dated Jan 1, 1970).

Conditions   The @LongLink file has no functional effect on the CTM application.

Workaround   You can safely remove the file from the file system.


CSCth75282

Symptom    There are no servers listed in the CTM Client Login window.

Conditions   This problem occurs on Microsoft Windows Vista and Windows 7 operating systems when the CTM client is installed in the root directory path (default is C:\Cisco).

Workaround   Change all read-only user file permissions to write. Do the following:


Step 1 Right-click the installation directory (default is TransportManagerClient9_2) and select Properties.

Step 2 Click the Security tab.

Step 3 Click Add.

Step 4 Select the Users group and click Edit.

Step 5 Check the Allow Modify check box under the Permissions for users area.

Step 6 Click OK to apply changes.



CSCti18475

Symptom    MGX migration errors are not shown in CTM.

Conditions   This problem occurs when migrating an MGX module from CTM R9.0 or R9.1 to CTM R9.2. Although an error on migration process appears under the /temp directory, the CTM GUI Installer reports that the CTM migration was successful.

Workaround   None.


CSCth97857

Symptom    The error "EID-130: Cannot authenticate user" appears after trying to log into a CTM server for the first time using the CTM client.

Conditions   This problem is seen after CTM server, CTM GateWay/CORBA, and client installation.

Workaround   Stop the CTM server and start it again.


CSCtj06010

Symptom    MGX GUI windows do not open because the UNIX permissions on the files in the /opt/CiscoTransportManagerServer/webServer/cgi-bin directory do not have read and execute permission for all users.

Conditions   This problem occurs when you install both optical and MGX modules, or when you install only MGX modules.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, enter the following commands to change the file permissions:

cd /opt/CiscoTransportManagerServer/webServer/cgi-bin
chmod a+x *
 
   

CSCtk83953

Symptom    The client_patch.bat installation script fails with the following message: "Unable to determine CTM client install location from registry. Please verify your installation and try again."

Conditions   This problem occurs when you install a CTM R9.2 client patch on a PC running Windows 7.

Workaround   Install the latest CTM R.2.0.420.4 or later patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl69065

Symptom    After CTM9.2 363 MGX installation, an outdated svplus directory is found in the svplus directory.

Conditions   This problem occurs when you install a CTM R9.2 server.

Workaround   None.


CSCtn03654

Symptom    An import of the entire database fails.

Conditions   This problem occurs during a new installation when you run the import_full_db.sh script. The script does not check if the export dump file exists on the file system. If you run import_full_db.sh and the dump file does not exist, data in the database is lost.

Workaround   Install the latest CTM R.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtn39718

Symptom    Cannot install the client patch if the installation directory name contains a blank space.

Workaround   This problem occurs if the name of the CTM client installation directory contains a blank space; for example, C:\Program Files\CiscoTransportManagerClient.

Workaround   Install the latest CTM R.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, change the name of the directory where the CTM client is installed; for example, C:\Cisco\CiscoTransportManagerClient.


CTM Client Caveats

This section contains the following information:

Alarm Management

Circuit and Link Management

Data Services

Domain Explorer

NE Explorer

Stop and restart the NE services. Then, change the IPv6 address again.

Network Map

Performance Monitoring

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 end NEs (ENEs) behind the firewall when SNMPv2 is enabled.

Conditions   This problem occurs when you enable SNMPv2 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 SNMPv1 for ENEs behind the firewall if the CTM server is the trap destination.


CSCin76849

Symptom    CTM and CTC do not show the actual equipment type for G1K-4 and TCC2 cards.

Conditions   See Symptom.

Workaround   None.


CSCsd18383

Symptom    Cannot filter alarms by affected object when the alarms have affected objects such as VFAC, FSTE, VCM, T1, and T3.

Conditions   Options such as VFAC, FSTE, VCM, T1, and T3 are missing from the list of affected objects in the Alarm Browser and the Alarm Log.

Workaround   Use the following options to filter the alarms.

Affected Object String
Filter Option to Select in the List of Affected Objects

VFAC

FAC

FSTE

FAC

VCM

STS, VC, or VT (depending on the type of circuit on which the alarm is raised)

T3

DS3

T1

DS1

SLOT

Equipment



CSCsd49219

Symptom    A mismatch alarm is raised incorrectly in 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 gateway NE (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.


CSCsv64186

Symptom    For NE version 7.0, the Alarm Suppressed For Maintenance alarm is not removed from the alarm table when the 32DMX card is deleted.

Conditions   This problem occurs when you:

1. Provision the 32DMX card on any slot.

2. Set any port to locked, maintenance. The Alarm Suppressed For Maintenance alarm is generated in the alarm table.

3. Delete the 32DMX card. The Alarm Suppressed For Maintenance alarm is still displayed in the alarm table.

Workaround   Refresh the CTM active alarm table. Then, mark the NE as Out of Service and then In Service.


CSCsv57617

Symptom    The port name (RPR, Ethernet, PoS) is incorrect or missing from the alarm table for all ML cards.

Conditions   This problem occurs for all ML interface alarms.

Workaround   None.


CSCtb72703

Symptom    Sometimes, when PM data is no longer valid, threshold crossing alerts (TCAs) are incorrectly raised in the Alarm Log.

Conditions   This problem occurs when a card changes card mode. Partial PM data become invalid, which generates TCAs.

Workaround   None.


CSCth40538

Symptom    The Alarm Browser Filter does not work.

Conditions   The problem occurs when you try to filter an ONS 15454 MSTP NE in a multishelf environment (not a single shelf environment). If a user applies a filter to any of the tabs, the Alarm Table becomes empty.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCth69815

Symptom    There is a high number of alarms in the Alarm Log.

Conditions   This problem occurs on a CTM server with MGX NE service running.

Workaround   None. This does not affect any CTM server functions.


CSCtk34613

Symptom    LOS-P alarms are not reported by CTM on a fiber cut on an A/D SMR port.

Conditions   This problem occurs if a fiber cut is generated on an A/D port of an SMR card and carrying a minimum of two circuits.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtj92364

Symptom    The Alarm Log displays the following error message: "EID-333: A database timeout occurred."

Conditions   This problem occurs when the network generates a large number of events such as threshold crossing alerts. The events accumulate in the CTM database tables and degrade the Alarm Log performance.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, do one of the following to reduce the Alarm Log scope:

Select a smaller set of NEs.

Apply a filter on a shorter time interval.

Circuit and Link Management


CSCeg06273

Symptom    Cannot change the administrative state to Out of Service-Out of Group (OOS_OOG) for 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.


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.


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


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.


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 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   This problem occurs when you 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 in a single operation; then, edit the tunnel alias to the desired value.


CSCsd12630

Symptom    The ONS 155xx Circuit table does not show circuit information for circuits whose names are modified using CTM.

Conditions   If you use CTM to modify an ONS 155xx circuit name, the circuit information for the renamed circuit does not appear.

Workaround   Refresh the circuit information.


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.


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. The same 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.


CSCse70271

Symptom    The number of TL1 circuits in the Circuit table increases after marking NEs as Out of Service and then In Service.

Conditions   This problem occurs because a circuit created through TL1 does not have a circuit ID compared to a circuit created in CTM.

Workaround   Enter the following Structured Query Language (SQL) commands to remove the invalid circuits:

su - oracle
sqlplus ctmanager/ctm123!
SQL> delete circuit_bs_tbl where cktstate=12;
SQL> commit;
 
   

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.


CSCsj80220

Symptom    Manual link creation fails.

Conditions   This problem occurs when a patchcord is already provisioned on the endpoint where you want to create the manual link.

Workaround   Create the manual link before creating a provisioned patchcord.


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.


CSCsq44778

Symptom    Connecting NE links shown in the Link table become invalid after removing NEs in a bidirectional line switch ring (BLSR).

Conditions   See Symptom.

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


CSCsr63160

Symptom    The Circuit table contains an invalid partial circuit with a name that ends in "_master".

Conditions   When you merge two open VCAT circuits, the Circuit table reports an invalid circuit with a circuit status of Partial. The name of the invalid circuit ends in "_master".

Workaround   Manually delete the invalid circuit from the Circuit table.


CSCsv39917

Symptom    Splitter-protected optical channel client connection (OCHCC) routing fails through OTU2_XP cards in Regeneration mode.

Conditions   This problem occurs under the following conditions:

Three OTU2_XP cards are present in three different NEs.

Two of the OTU2_XP cards are configured in splitter mode. The other OTU2_XP card is configured in EFEC mode.

The splitter working trunk ports pass through the EFEC regenerator.

The splitter protect trunk ports are directly connected, as follows:

A ------------B-----------C

Splitter EFEC splitter

Two trunk-to-trunk patchcords are created between working trunk ports and EFEC regenerator trunk ports.

One trunk-to-trunk patchcord is created between protect trunk ports.

At this point, a splitter-protected OCHCC circuit should be provisioned, but the circuit routing fails and the circuit is not created.

Workaround   None.


CSCsv69475

Symptom    Creation of an OCHCC circuit using PSM in MUX section or path protection is possible in only one direction. Creation of OCHCC should be available in both directions.

Conditions   This problem occurs when you create an OCHCC circuit with the source as a terminal node equipped with nXP and with PSM configured in MUX section or path protection. The following error message appears: "EID-3246. The wizard was not able to validate data."

Workaround   Create an OCHCC circuit in the opposite direction with a terminal node as the destination. The circuit is created successfully.


CSCsw30808

Symptom    Creating a circuit that contains 20 or more constraints causes a timeout error.

Conditions   This problem occurs when using the Create Circuit wizard to create a circuit with 20 or more nodes.

In the Routing Preferences pane, Enable Route Automatically and Using Required Nodes/Link are selected.

In the Route Constraints pane, each node is selected.

Workaround   None.


CSCsx26308

Symptom    The status of a VCAT circuit changes to Partial when adding new members to the circuit on SONET NEs.

Conditions   This problem occurs on VCAT circuits on SONET NEs where some ML_MR_10 card endpoints are configured in Automatic mode and other endpoints are configured in Manual mode.

Workaround   Create the initial circuit with all the required members and do not provision cards in mixed mode.


CSCsz38912

Symptom    Layer 2 multicast groups are not disabled correctly.

Conditions   This problem occurs under the following conditions:

1. Create a Resilient Packet Ring (RPR) L2 topology where two multicast groups (Group1 and Group2) are enabled.

2. Once the topology is updated, use the Modify L2 Topology wizard to disable multicast Group2. Leave multicast Group1 enabled.

3. Close the wizard and refresh the L2 Topology table. Multicast Group2 is shown as enabled (instead of disabled) and multicast Group1 is shown as disabled.

Workaround   None.


CSCta33329

Symptom    A "No Valid Route Found" error message appears.

Conditions   This problem occurs when adding members and manually routing to an existing VCAT DRI protected circuit.

Workaround   Use automatic routing when adding members to the circuit.


CSCta52790

Symptom    OCHCC circuit deletion causes missing parameters in the Optical Line panel.

Conditions   This problem occurs when you delete an OCHCC circuit that traverses an amplifier card.

Workaround   Refresh the NE.


CSCtc91052

Symptom    Data communications channel (DCC) links involved in a BLSR or multiplex section shared protection ring (MS-SPRing) are deleted from the CTM database.

Conditions   This problem occurs when you use the NE Explorer > BLSR or MS-SPRing tab to configure BLSR or MS-SPRing protection.

Workaround   Mark the NEs involved in the BLSR or MS-SPRing protection as Out Of Service, then In Service. This action updates the database with the missing DCC links.

To avoid this problem, create BLSR/MS-SPRing protection from the Domain Explorer, as follows:

For BLSR, select the NE in the Domain Explorer; then, choose Configuration > CTC-Based SONET NEs > Create BLSR.

For MS-SPRing, select the NE in the Domain Explorer; then, choose Configuration > CTC-Based SDH NEs > Create MS-SPRing.


CSCtc97693

Symptom    Circuit creation fails if a tunnel circuit is needed and the Time Slot Restriction option is checked in the Create Circuit wizard.

Conditions   This problem occurs if a tunnel circuit does not exist before the VC LO circuit is created. To recreate this problem, do the following:

1. Using the Create Circuit wizard, create a VC LO circuit that requires a tunnel circuit.

2. In the Routing Preferences pane, check the Time Slot Restriction option and click Next.

3. In the VT/VC LO Circuit Options pane, choose VT/VC LO Tunnel on Transit Nodes. An error message appears.

Workaround   Create the required tunnel circuit with time slot restriction enabled. Then, create a VC LO circuit that uses the tunnel circuit you created.


CSCtd00386

Symptom    The Layer 2 link between two ML-MR-10 cards remains invalid.

Conditions   This problem occurs under the following conditions:

1. Create a VCAT circuit between two ML-MR-10 cards. An L2 topology is automatically discovered. Since no Cisco IOS management is implemented in CTM for these cards, the L2 Resync state of the corresponding L2 topology remains in syncFail status.

2. Mark one of the NEs as Out of Service. Wait for the L2 link to become invalid.

3. Mark the NE as In Service. The link remains invalid.

Workaround   None.


CSCtd40139

Symptom    A timeout occurs when launching the Circuit table from the CTM domain for a SuperUser.

Conditions   This problem occurs when there are thousands of circuits in the database.

Workaround   Limit the query options.


CSCtd40814

Symptom    A timeout occurs when launching the Link table from the CTM domain for a SuperUser.

Conditions   This problem occurs when there are more than 2,000 links in the database.

Workaround   Limit the query options or increase the timeout.


CSCtd44336

Symptom    The number of spans for OCHCC circuits reported in CTC does not match the number of spans reported in CTM.

Conditions   This problem occurs in the Circuit table.

Workaround   Use CTC to view the correct number of spans for OCHCC circuits.


CSCtf30593

Symptom    Autodiscovered Layer 2 links are not recreated when an NE is deleted in another Layer 2 topology and then added back again.

Conditions   The problem occurs in a GNE/NE Layer 2 topology when an ENE/NE is deleted.

Workaround   Delete all NEs in the Layer 2 topology and add the NEs back.


CSCtg24877

Symptom    The deletion process of SONET/SDH manual links between trunk and client ports is different. When deleting links between trunk ports, they are automatically deleted. However, when deleting links between client ports, links that are removed are marked invalid and then must be manually deleted.

Conditions   This problem occurs when deleting SONET/SDH manual links created from CTM between trunk or client ports of two transponders.

Workaround   None.


CSCtg38296

Symptom    An OTU2_XP client port is shown as a trunk port in CTM.

Conditions   This can be seen in the OTU2_XP Alarm behavior tab or when creating Y-cable protection for a client port. CTM incorrectly shows client ports as DWDM trunk ports.

Workaround   None.


CSCtg40714

Symptom    From the Link table, the Detail column displays an incorrect value for autodiscovered links between two 40G-MXP-C cards. Instead, the Detail column shows OC-48 (SONET) and STM-16 (SDH).

Conditions   This problem occurs when there are two NEs connected via a Generic Communication Channel (GCC) through two 40G-MXP-C cards.

Workaround   None.


CSCtg96871

Symptom    The Circuit table is not updated when launched from the Domain Explorer.

Conditions   This problem occurs under the following conditions:

1. An NE is initially managed by an NE service and the Circuit table is launched from the Domain Explorer.

2. Add another NE to the same NE service.

3. Add another NE to a new NE service.

The Circuit table label is not updated to reflect multiple NEs, and the new circuit entries are not shown in the Circuit table.

Workaround   Close and reopen the Circuit table.


CSCth05212

Symptom    You cannot reconfigure HOP-V and LOP-v TL1 circuits.

Conditions   This problem occurs when upgrading a TL1 circuit to a regular circuit by selecting Configure > Reconfigure Circuit(s) from the Circuit table. The DISCOVERED_TL1 circuit status changes to PARTIAL_TL1 instead of DISCOVERED.

Workaround   None.


CSCth13333

Symptom    It takes a long time for links to become invalid after marking a number of NEs Out of Service.

Conditions   This problem occurs when a group of NEs are marked Out of Service. The problem is more apparent if alarms are present on the NEs.

Workaround   None.


CSCth35889

Symptom    The Circuit table displays "Unknown" circuits or unexpected circuits.

Conditions   This problem occurs if the circuit's source NEs are not yet discovered and if the NEs do not support cross-connection names.

Workaround   Enter the proper access credentials for the source NE and wait for the NE to be discovered.


CSCth85204

Symptom    A virtual link is not discovered by CTM after adding the NE back.

Conditions   This problem occurs under the following conditions:

1. A network partition is set to manual discovery mode and a virtual link exists.

2. Delete the NE associated to the virtual link.

3. Add the NE back to the same network partition.

The virtual link is not discovered. The NE no longer appears to be connected to another NE.

Workaround   Restart the NE service.


CSCti18733

Symptom    Manual physical links are not created and do not appear in the Link table or the Network Map.

Conditions   This problem occurs when you use the Create Link wizard to create a manual physical link. The link creation appears to succeed because no errors are reported. However, the link is not created.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk13431

Symptom    High CPU usage after bulk circuit creation.

Conditions   This problem occurs after doing a bulk circuit creation. There is a high CPU usage for a long period of time.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl06299

Symptom    On a circuit trace, notifications are not sent for new events.

Conditions   When changes are made to circuits, those changes are not reported on the circuit trace. Events that are not reported on the circuit trace include:

New alarms occurring on the NE or slot.

Setting the J1 path trace.

Also, if you suppress alarms at the NE level, the circuit trace does not update with the correct alarm color.

Workaround   Click the Refresh button.


CSCtl93740

Symptom    The Protection tab shows NO-STATUS instead of Active or Standby status.

Conditions   This problem occurs when there is a Y-cable protection created on a 40E-TXP-C card with OCC768/40GE payloads.

Workaround   Use CTC.

Data Services


CSCsg51351

Symptom    You cannot add or remove protection cards using the Add/Remove Cards wizard.

Conditions   This problem occurs because CTM does not fully support protection cards.

Workaround   None.


CSCsl54671

Symptom    In the NE Explorer for ML cards, the Ether tab > Gigabit Ethernet Provisioning or Fast Ethernet Provisioning subtabs are blank.

Conditions   This problem occurs when the ML card is not part of an L2 topology or is configured only with a Cisco IOS initialization file.

Workaround   Do one of the following:

Use the Cisco IOS CLI to configure the Gigabit Ethernet ports.

Configure the ML card before adding it to the L2 topology.

Send a Cisco IOS CLI write mem command to the card.


CSCsz16486

Symptom    ".1CTML2" is appended to the L2 topology name and not to the alias name entered in the Create Layer 2 Topology wizard.

Conditions   This problem occurs when creating an L2 topology and entering an alias name in the Create Layer 2 Topology wizard.

Workaround   From the Layer 2 Topology table, choose the Configuration > Modify L2 > General tab and edit the Alias field.


CSCta15410

Symptom    For cards that support split protection (for example, TXPP and MXPP), the service state for the GCC termination displays only one port state.

Conditions   This problem occurs on cards that support split protection. Choose NE Explorer > DCC/GCC/OSC > GCC. The working port state is the only port state displayed. Both port states should be displayed.

Workaround   Use CTC to view the service state of both ports used in the GCC termination.


CSCtd44161

Symptom    Duplex and Speed values are not updated in the Ether Ports subtab.

Conditions   This problem occurs after configuring the Duplex and Speed options from the FE Provisioning tab on an ONS 15310 MA SDH ML-100T card.

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


CSCtg92225

Symptom    The Selected Cards pane from the Add ML Card Wizard does not list all available ML cards when adding an ML card to an Layer 2 topology.

Conditions   This problem occurs when there are TL1 circuits involved in a L2 topology that have a POS1 port as the source.

Workaround   Delete the circuits that have the POS1 port as the source and recreate them with a POS0 port.


CSCth03477

Symptom    Some nodes are not discovered after restarting the CTM server.

Conditions   See Symptom.

Workaround   After the system reboots, restart the NE service.


CSCth71367 (Related caveat ID: CSCti30435)

Symptom    Navigating within the CTM client is slow, and the client freezes. If you launch a new CTM client, the following error is displayed:

EID-382: The CTM server is initializing. Please try again later.

Conditions   This problem occurs when all of the following conditions are met:

The CTM server is managing a complex network with many L2 topologies and VLAN services based on ML-card technology.

Multiple CTM client instances are open.

Different operators are performing various provisioning, discovery, and resynchronization operations on L2 topologies and services.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCto74015

Symptom    L2 topologies remain in Sync Failed state or are not discovered for several hours.

Conditions   This problem occurs when some of the NEs managed by CTM are in Initialization Failed state, and the circuits that use those NEs as the source or destination endpoints have a circuit status of Partial.

Workaround   Mark the NEs in Initialization Failed state as Out of Service. Within a few hours, the L2 topologies are discovered or synchronized automatically.

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   If the TCC card has to be swapped without synchronization, mark the NE as Out of Service in CTM. After swapping the TCC card, change the IP address of the NE in the Domain Explorer and then mark the NE as In Service.


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.


CSCse65683

Symptom    The NE time stamp for syslog messages is the same as the CTM time stamp because the actual NE time stamp when the syslog message was generated is not available. This duplicates the syslog messages in the event log, and each syslog message has a different time stamp.

Conditions   This problem occurs when an NE that contains ML cards is in service, then marked Out of Service and then In Service using CTM.

Workaround   None.


CSCsx37855

Symptom    When a GNE-ENE setup involves PSM cards with path protection, the Domain Name column in the APC Domain table shows sides as Unknown instead of as side (W) and side (P).

Conditions   This problem occurs when you have an NE with a PSM card in a path protection configuration and you do the following:

1. From the Domain Explorer, select the NE.

2. Choose Configuration > CTC-Based SONET NEs or SDH NEs > APC Domain Management.

3. From the APC Domain table, choose Edit > Discover APC Domain.

Workaround   None.


CSCta95826

Symptom    ONS 15501 NEs are discovered in CTM R9.1 with the wrong model type, because CTM R9.1 does not support ONS 15501 NEs.

Conditions   This problem occurs when either of the following conditions is met:

ONS 15501 NEs are connected to ONS 15540 NEs.

ONS 15530 NEs and the ONS 15501 are autodiscovered.

Workaround   None.


CSCtc09711

Symptom    In the SVLAN Database Management wizard > Select a Resource pane, shelves are not sorted on multishelf NEs.

Conditions   This problem occurs under the following conditions:

1. In the Domain Explorer, select a group of NEs that are provisioned with multiple GE_XP cards.

2. Choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > SVLAN DB Management. The SVLAN Database Management wizard opens.

3. In the Select a Resource pane, expand the Network tree. Shelves are not sorted.

Workaround   None.


CSCtd54733

Symptom    An NE is no longer discovered after the NE IP address is changed twice from the Domain Explorer.

Conditions   This problem occurs if you enable IPv6 on the NE from the Domain Explorer and then try to change the IP address.

Workaround   Stop and restart the NE services. Then, change the IPv6 address again.


CSCtf25218

Symptom    After undeleting many NEs in a group, the NEs are placed into the Domain Explorer instead of their original group.

Conditions   The problem occurs when you undelete many NEs in a group.

Workaround   Manually move the NEs back to the correct group.


CSCtg27295

Symptom    After starting the discovery process from the Undiscovered NEs folder, the Undiscovered NEs folder icon from the Domain Explorer tree disappears.

Conditions   This problem occurs when the CTM client is open for an extended amount of time and various discovery tasks have been performed.

Workaround   Close and reopen the CTM client.


CSCth53210

Symptom    The CTM client freezes when you open the Alarm Browser or the Equipment Inventory table from the root node of the Domain Explorer.

Conditions   See Symptom.

Workaround   Select a few NEs before you try to open the Alarm Browser or the Equipment Inventory table.


CSCtk48145

Symptom    When you open the Domain Explorer, select a CRS-1 or ONS 15454 NE, and then change the selection, the following message is displayed:

Property Sheet has been changed. Do you really want to discard changes?
 
   

The client hangs with the message "Retrieving data, please wait" shown in the bottom left corner of the Domain Explorer window.

Conditions   This problem occurs when the CRS-1 or ONS 15454 NE software version is not listed in the Supported NE table.

Workaround   Close and reopen the CTM client.


CSCtl83275

Symptom    The CTM R9.2 client periodically freezes.

Conditions   This problem occurs when the root of the Domain Explorer tree is selected and the entire tree is expanded.

Workaround   From the Domain Explorer tree, select a small subset of objects and only expand the tree when needed. Alternately, install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

NE Explorer


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.


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.


CSCsb52823

Symptom    Line configuration and threshold values are not shown in CTM when creating a new DS3 port through CTC.

Conditions   This problem can be seen in the NE Explorer > Property Sheet pane. The Broadband Ports tab does not reflect changes.

Workaround   None.


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.


CSCsd21653

Symptom    A card with a warning is not colored correctly in the rack view.

Conditions   See Symptom.

Workaround   None.


CSCsq67980

Symptom    Contact Status and Raised fields are not updated in the External Alarms subtab.

Conditions   This problem occurs when you:

1. Launch the NE Explorer on an ONS 15600 node.

2. Open the Alarm Extenders tab.

3. Create an external alarm from CTC.

When the alarm is created, the Contact Status and Raised fields are synchronized with CTC. However, once the alarm is raised in the Alarm Browser, the Contact Status and Raised check boxes change (the check boxes are selected). This update is not reflected in CTM. When the Alarm Browser is checked, the alarm is raised. The same conditions exist when the alarm is created from CTM.

Workaround   None.


CSCsq71167

Symptom    You cannot set the AINS Soak attribute on an ASAP card.

Conditions   This problem occurs when you:

1. Launch the NE Explorer on an ONS 15600 node.

2. Click the Ether Line tab.

3. Change the AINS Soak Count Down value.

4. Click Apply. The value reverts to the original AINS Soak value.

Workaround   In addition to setting the AINS Soak value, set other values in the Line tab. Setting other values sets the AINS Soak value.


CSCsq86608

Symptom    Intermediate port information shows incorrect data when upgrading an optical card to an MRC-12 card.

Conditions   This problem occurs when the NE Explorer > DCC tab is open during an MRC-12 card upgrade.

Workaround   Refresh the NE Explorer window.


CSCsw51242

Symptom    After you change an IP address on a managed NE, discovery problems occur if new networks containing the changed IP address are added to CTM.

Conditions   This problem occurs if you change the IP address on a managed NE; for example, from IP_address_A to IP_address_B. If you add to CTM a new network that contains an ENE with an IP address of IP_address_A, network discovery problems might occur.

Workaround   Restart the NE service.


CSCsx26152

Symptom    The SVLAN fields in the QinQ tab are not automatically updated when VLAN database changes are made.

Conditions   This problem occurs when both the QinQ tab on a GE_XP or 10GE_XP card and the NE Explorer are opened at the same time and you make changes to the VLAN database; for example, you add or delete rows.

Workaround   Change the card view on another GE_XP or 10GE_XP card on the same tab, or close and open the NE Explorer. This action forces the database information to refresh.


CSCtb10416

Symptom    When NEs are connected by links, the bulk purge of a set of NEs causes a flood of error messages (EID-693).

Conditions   This problem occurs under the following conditions:

1. Select a large number of NEs (for example, 250 NEs) and mark them as Out of Service.

2. Delete the selected NEs.

3. View the Deleted Network Elements group in the Domain Explorer tree. The following error message appears for each NE deletion:

EID-693: Cannot purge the requested NE because it is connected to another node with a 
link.

Workaround   None.


CSCtf00425

Symptom    When communication is interrupted between the CTM client and the CTM server, the automatic login feature is restarted, but does not work as expected. The default values in the Control Panel > Recovery tab are 60 seconds for wait time, and 6 retries. With this problem, the automatic login occurs every 10 seconds (instead of every 60 seconds), with 3 retries (instead of 6 retries).

Conditions   This problem occurs whenever communication is interrupted between the CTM client and the CTM server.

Workaround   Relaunch the CTM client manually.


CSCtf27721

Symptom    Cannot delete pluggable port modules (PPM) payload on a TNC card.

Conditions   This problem occurs when two PPMs are provisioned on a TNC card and you delete the first payload. The PPM Delete tab is unavailable.

Workaround   From the NE Explorer, click another tab and then open TNC PPM again. The Delete tab is now available.


CSCtf62377

Symptom    During an NE database restore, CTM shows the NE as Available, In Service. As the NE is restarting the process, CTM displays the NE status as "Available, In Service" to "Only reachable." The NE status should be reflected as unavailable until the NE has been rediscovered.

Conditions   This problem occurs during a CTC-based NE database restore. The time it takes for the NE state to change from INITIALIZING to UNDISCOVERED and then back to INITIALIZING in the audit log is equal to the NE polling time (default is 4 minutes). However, the NE remains in "Only reachable" state. The NE is finally discovered after another time interval equal to the NE polling time.

Workaround   None.


CSCtf96555

Symptom    Purged NEs are rediscovered and marked In Service.

Conditions   This problem occurs when links are being marked as invalid.

1. Select a group of NEs that are all LNEs.

2. Mark them all Out of Service.

3. Delete them. The NEs are moved to the Deleted NEs group. At this point, links are being marked as invalid.

4. Select all NEs to be purged. A message states that some NEs cannot be purged because valid links still exist.

5. Click Yes. Purged NEs are rediscovered and put In Service.

Workaround   Wait an appropriate amount of time until all links are inactive before purging NEs.


CSCti03057

Symptom    The NE Explorer > Card tab opens very slowly.

Conditions   This problem occurs when the card is provisioned with many pluggable port modules (PPMs).

Workaround   None.


CSCti05546

Symptom    OSCM optical line ports are missing on ONS 15454 ETSI NEs.

Conditions   This problem occurs when an OSCM card is preprovisioned on an ONS 15454ETSI NE. The Optical Line tab is empty.

Workaround   Refresh data from the NE.


CSCtl46593

Symptom    In the ASAP_4 card NE Explorer > VC tab, when there are multiple circuits created on the same port, CTM shows only one row with a VC ID of 1. Instead, CTM should show multiple rows, one row for each circuit (with a unique VC ID) on the port.

Conditions   This problem applies to ONS 15600 SONET or SDH ASAP_4 cards that are configured with STM pluggable port modules (PPMs). If you create multiple circuits—each with a unique VC ID---on the same port, the ASAP_4 card NE Explorer > VC tab displays only one row. Instead, the VC tab should show multiple rows, one row for each circuit on the port.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, use CTC to view the different circuits (and their VC IDs) that exist on the same port.

Network Map


CSCtc31637

Symptom    The zoom function does not work correctly in the Network Map.

Conditions   This problem occurs under the following conditions:

1. Zoom in or out of an area in the Network Map and click Save.

2. Click Refresh Data. The zoom area is incorrect or nodes are no longer visible.

Workaround   None.


CSCtc87460

Symptom    The Network Map does not reset to its default layout.

Conditions   This problem occurs under the following conditions:

1. Open the Network Map from a group of NEs.

2. Move an NE inside a grid of NEs.

3. Click Save.

4. Choose File > Revert to Default. The NEs are not reset to their original location. Instead, the NEs are smaller and are located in the top left corner of the map.

Workaround   None.


CSCth26545

Symptom    Sometimes, the Network Map freezes after you click Refresh. There may also be duplicate nodes in the Network Map.


Note The node duplication is only a graphic problem. There are no node duplications that occur in the CTM database.


Conditions   The problem occurs when an optical channel patchcord (for example, a transponder card such as a 10_DME or a WSS/DEMUX) or an OTS manual link is created between two amplifiers in two different nodes.

Workaround   None.


CSCtl23021

Symptom    CTM shows incorrect data in the NE Explorer > Timing > Reference List tab for 40G_MXP_CE_C and 40E_TXP_C cards.

Conditions   This problem applies to 40G_MXP_CE_C and 40E_TXP_C cards with OC192 PPM or OC768 data rates. At the shelf level, the Timing > Reference List tab shows the wrong card labels for NE References, BITS-1 Out References, and BITS-2 Out References. The values are shown correctly in CTC.

Workaround   Use CTC to view the correct values.


CSCtl91069

Symptom    After software is activated or reverted, ML cards are not initialized correctly. In the NE Explorer > ML Configuration tab, the Hostname and Microcode fields are dimmed.

Conditions   This problem occurs under the following conditions:

You activate or revert software on an NE that contains ML cards.

The ML Configuration tab is closed while the software is activated or reverted.

Workaround   In the NE Explorer window, perform a Refresh Data from Server operation.

Performance Monitoring


CSCin85192

Symptom    When you click OK in the Graph Parameters Selection dialog box, the selected parameters are not graphed correctly.

Conditions   This problem occurs occasionally under the following conditions:

1. Enable PM data collection for an ONS 15530 NE.

2. Launch the Line PM table for this NE and click the Graph Configure Parameter button.

3. In the Graph Parameters Selection dialog box, choose three parameters; then, click OK.

The graph shows only one parameter; two parameters are missing.

Workaround   Add the same parameters to the second graph, where they will be graphed correctly.


CSCin93966

Symptom    After a normalization operation on a PM graph, the maximum value of the Y axis is not displayed.

Conditions   This problem occurs when multiple graphs are displayed on the PM Plot tab. If a single graph is displayed, the maximum value of the Y axis is shown correctly after a normalization operation. This problem does not occur after a restore operation.

Workaround   To read the maximum value of the Y axis after a normalization operation, place your mouse pointer over the Y axis value. The tooltip shows the maximum value.


CSCsb31623

Symptom    When you launch the DS-1 PM table for an ONS 15310 NE, the FC-P (Tx) parameter is missing.

Conditions   See Symptom.

Workaround   None.


CSCsb45250

Symptom    Cannot collect valid real-time Storage Area Network (SAN) PM data for NEs earlier than release 5.0.

Conditions   When you launch the real-time SAN PM table for an NE release earlier than R5.0, incorrect PM values are displayed.

Workaround   None.


CSCsc46214

Symptom    The following problems are observed:

1. The generic framing procedure (GFP) PM parameters are displayed even if the ports are not provisioned for GFP. It should be displayed as N/A when the ports are not set.

2. The CTM GateWay/CORBA real-time PM data retrieval does not work. Ports 1 and 0 generate incorrect data, which does not match the data in CTM or CTC. The real-time PM data retrieval returns a -1 value instead of N/A when the ports are provisioned as high-level data link control (HDLC).

Conditions   This problem occurs when the PoS ports are set to HDLC for the ML cards. The bulk PM response should return an empty string instead of 0 for GFP parameters.

Workaround   None.


CSCsc89073

Symptom    Real-time PM tables display a Not Available message for PM queries with remote NEs when the selection context is large.

Conditions   For a remote NE, if you perform a real-time PM query with the slot and port selections set to All, the PM counter values display Not Available.

Workaround   Reduce the selection context and select the slot and port number required for the PM query.


CSCsd27300

Symptom    High bandwidth usage occurs between the CTM client and the CTM server.

Conditions   This problem occurs during a real-time PM session.

Workaround   None.


CSCse60425

Symptom    TCAs are not shown in the VC12 PM table for E1 and E1_42 cards.

Conditions   This problem applies to ONS 15454 SDH NEs.

Workaround   View the TCAs in the Alarm Log.


CSCsk28930

Symptom    PM data collection, audit trail collection, error logging, and audit logging stop abruptly.

Conditions   This problem occurs if the system time is set forward to a future date and then reset to a different date. This problem is due to a known Oracle issue.

Workaround   Enter the following SQL commands in TOAD or SQL*PLUS to restart the Oracle jobs and resume PM data collection:

Begin
DBMS_JOB.RUN (1,true);
DBMS_JOB.RUN (2,true);
DBMS_JOB.RUN (3,true);
DBMS_JOB.RUN (4,true); 
End;
 
   

CSCsu59134

Symptom    Unnecessary STS/VC HO path PM data is collected for an Ethernet PoS port on an ASAP_4 card.

Conditions   This problem occurs when you:

1. Create an STS-1 circuit on an Ethernet port on a provisioned or preprovisioned ASAP_4 card.

2. Create an STS-1 VC-HO circuit on an optical port on the same card.

3. Collect real-time PM data for the STS-1 VC-HO path. Information is also collected for the Ethernet PoS port.

This problem occurs when the two circuits mentioned in Steps 1 and 2 are created separately.

Workaround   None.


CSCsw69581

Symptom    1-day PM data shows values for the wrong day.

Conditions   This problem occurs when the CTM server and the managed NE use different time zones.

Workaround   Set the same time zone for the CTM server and the NE.


CSCsx52849

Symptom    Performance monitoring for OTN 1-day, far-end, real-time data does not work correctly for R7.0 NEs.

Conditions   This problem occurs when you have a TXP/MXP card supporting OTN and a R7.0 NE. Performance monitoring for G.709 section and G.709 path real-time, 1-day, far-end data does not work correctly. Only the UAS-SM and UAS-PM counters collect performance data; other counters are shown as N/A.

Workaround   Check OTN real-time, 1-day PM data on the far-end card.


CSCtb06160

Symptom    In the Optical Physical PM table (for 15-minute and 1-day data), the Maximum Received OSC Power field is blank.

Conditions   This problem occurs when the Maximum Received OSC Power field does not apply to a specific port; for example, a TX port. The field should display N/A.

Workaround   None.


CSCtl01777

Symptom    When the PM data storage status is set to Optimized, Ethernet PM values are not stored in the database.

Conditions   This problem occurs under the following conditions:

Your network contains at least one card that supports Ethernet PM data.

The Control Panel > PM Service pane > PM Data Storage field is set to Optimized.

Workaround   Set the Control Panel > PM Service pane > PM Data Storage field to Normal. Alternately, install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCuk55603

Symptom    For nodes equipped with PPM-provisioned transponder and muxponder cards, the reported Average Transmit Power value is incorrect.

Conditions   If you open the real-time Physical PM table for a particular slot with "All" selected as the port, the Average Transmit Power value is 0.0 dBm. The correct value is -40 dBm, as reported in CTC. This problem applies to R4.7 and R5.0 NEs equipped with PPM-provisioned MXP_2.5G_10E, DMP_2.5G, or TXP_MR_10E cards.

Workaround   Open the real-time Physical PM table for a particular slot and port. Do not select "All" as the port; rather, specify a particular port.


CSCth75323

Symptom    Bulk PM Collection settings do not work for preprovisioned NEs.

Conditions   This problem occurs under the following conditions:

Condition 1:

1. Create a group of preprovisioned NEs.

2. From the Domain Explorer, click the Performance menu.The PM Collection Settings option is unavailable for selection.

Condition 2:

1. Open the Network Element Properties sheet of an NE belonging to an NE group with In Service and preprovisioned NEs.

2. Verify that the PM Collection options are available in the NE properties sheet.

3. Click the Performance menu. The PM Collection settings is unavailable for selection for that NE.

4. Select the parent NE group.

5. Select Performance > PM Collection Settings. The menu item is available, but you cannot select preprovisioned NEs.

Workaround   Select each preprovisioned NE individually and enable PM using the Network Element Properties sheet. This is a potential problem with servers that have many nodes.


CSCti00208

Symptom    40G-MXP-C real-time PM counter values show N/A.

Conditions   The problem occurs when 40G-MXP-C 10GE ports are configured in WIS mode.

Workaround   None.


CSCti13083

Symptom    1-day historical Optical Physical PM data is not plotted in the Graph tab.

Conditions   This problem occurs when trying to plot 1-day Optical Physical PM data. Data is correctly collected by the CTM Server and available in the PM Table, but the graph is empty. This occurs for all cards where Optical Physical PM data is collected (amplifiers, OSC, multiplexers, demultiplexers, 40WXC, 80WX, and so on).

Workaround   None.


CSCti10164

Symptom    Real-time PM data is not collected on a channel interface of an 80-WXC card installed in a multishelf environment with the shelf > 1.

Conditions   This problem occurs when a real-time PM session is started on an 80-WXC card.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtj67138

Symptom    Historical optical PM data is not collected for 80_WXC_C cards on ONS 15454 SDH NEs.

Conditions   See Symptom.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl46849

Symptom    High-order SDH PM data is not collected for ONS 15600 SDH NEs.

Conditions   This problem occurs when VC3 and VC4 interfaces exist on the same interface.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtn05639

Symptom    Sometimes OTN FEC PM data is not collected on an OTU2_XP card.

Conditions   This problem occurs on NEs with 40G_MXP_C, 40G_MXP_CE and OTU2_XP cards.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

Miscellaneous


CSCeg57848

Symptom    The Equipment Inventory table shows TCC2P as TCC2.

Conditions   If you open the Equipment Inventory table for an ONS 15454 SDH NE that contains TCC2P modules, the Actual Equipment Type field displays TCC2. The field should distinguish between TCC2 and TCC2P modules.

Workaround   None.


CSCin94007

Symptom    CTM shows a blank password.

Conditions   An unset password is shown as an empty password field, which therefore reveals the actual password.

Workaround   Change the password of all NEs that have a blank password.


CSCsb29625

Symptom    When a new card is provisioned on a filler card on an ONS 15600 SDH NE, the actual equipment type is blank and a Mismatch of Equipment (MEA) alarm is raised.

Conditions   When a new card is provisioned on a filler card on an ONS 15600 SDH NE, the actual equipment type is blank in the Equipment Inventory table. The actual equipment type should report "Filler Card." Also, an MEA alarm is raised on the card. This problem applies only to ONS 15600 SDH NEs.

Workaround   None.


CSCsc61618

Symptom    The file CTM Client Home/gcoutput, where CTM Client Home is your client location, is unreadable.

Conditions   When multiple instances of the CTM client are launched on the same Solaris or Windows machine, all instances of the client write GC data to the same output file. The output file becomes unreadable.

Workaround   To avoid this problem, change the name of the file the clients write GC data to before launching a client instance.

To change the name of the GC data file on Windows systems:


Step 1 Go to the CTM-client-home/ directory, where CTM-client-home is your client location.

Step 2 Using an ASCII text editor, such as Notepad, open the file ctm-size.lax, where size is small, medium, large, highend, or default, according to your system size.

Step 3 Search for the string -Xloggc:. After you have located the string, locate the name gcoutput next to it. This is the filename used for GC output data.

Step 4 Change the filename gcoutput to a new name.

Step 5 Save and close the file.

Step 6 Start a new client session as usual.


To change the name of the GC data file on Solaris systems:


Step 1 Go to the CTM-client-home/ directory, where CTM-client-home is your client location.

Step 2 Using an ASCII text editor, such as Notepad, open the file ctmc-start.

Step 3 Search for the string -Xloggc:. After you have located the string, locate the name gcoutput next to it. This is the filename used for GC output data.

Step 4 Change the filename gcoutput to a new name.

Step 5 Save and close the file.

Step 6 Start a new client session as usual.



CSCsc67149

Symptom    The taskbar shows all grouped CTM client applications as javaw x instead of CTM.

Conditions   This problem occurs when the client is launched on Windows XP with multiple windows.

Workaround   None.


CSCsd17895

Symptom    The CTM client freezes when connected to a high-end CTM server.

Conditions   This problem occurs when many NEs are synchronizing and the bandwidth between the CTM client and the CTM server is 256 KB.

Workaround   Increase the bandwidth between the client and the server.


CSCse50587

Symptom    The number of alarms shown in the CTM Dashboard is not synchronized with the number of alarms shown in the Domain Explorer > Management Domain Properties pane.

Conditions   This problem occurs when a high number of alarms is raised continuously.

Workaround   Use the Alarm Browser to view the latest alarm information.


CSCsg46955

Symptom    There is a delay when performing a Revert to Default operation on the Network Map.

Conditions   This problem occurs when the Network Map contains more than 100 NEs.

Workaround   None.


CSCsg73328

Symptom    NEs do not come up in CTM after exchanging MAC addresses between managed NEs.

Conditions   If an NE is assigned a MAC address that already belongs to another NE managed by CTM, the NE does not come up. Note that a new MAC address that is not already in use can be assigned to an NE without any problems.

Workaround   Before swapping MAC addresses between NEs, remove the NEs from the network and delete them from the CTM server.


CSCsk74438

Symptom    When you change the NE default values of ONS 15600 SDH R8.0 NEs, the following error message appears: "Error in setting the values. Please choose a valid value from the range displayed."

Conditions   This problem occurs on version 08.00-007A-27.16 of ONS 15600 SDH NEs.

Workaround   Perform one of the following workarounds:

Use CTC to modify the NE default values.

Save the NE default values in a file using the Save to file option in the NE Defaults Management wizard. Use an editor to modify the file and use CTC to load the modified NE default values.


CSCsr52735

Symptom    The Refresh button does not flash when the port name is changed and automatic refresh is disabled. The window does not refresh automatically even after enabling automatic refresh.

Conditions   See Symptom.

Workaround   Click the Refresh button. Alternately, close and then reopen the window.


CSCsr71468

Symptom    When you add a new CTC-based NE to CTM that is part of a ring, the system takes a long time to discover the new NE and the other nodes of the ring.

Conditions   This problem occurs when you add a new CTC-based NE to CTM and the CTC-based NE service discovers a large network that contains several links and circuits. Discovery of the new NE occurs immediately after CTM discovers the links and circuits of the network.

Workaround   None.


CSCta47206

Symptom    Automatic backup fails with the following message in the Job Monitor table:

Error Index: MEM_BACKUP_FAIL_ERRDetailed Error String: Memory Backup
failed: java.lang.Exception: The node is busy saving recent modifications.

Conditions   This problem occurs because the NE is busy for a variety of reasons; for example, saving PM data. However, once the backup fails, CTM does not retry the backup.

Workaround   Schedule manual backups for the NEs that failed.


CSCtc58965

Symptom    An NE enabled with IP secure mode is discovered twice by CTM. CTM discovers the frontplane and backplane IP addresses as separate nodes.

Conditions   This problem occurs when you:

1. Enable a node with IP secure mode.

2. DCC-connect the node to another node already managed by CTM.

3. Add the node to CTM with the backplane IP address.

Workaround   Delete the backplane IP address node.


CSCtd92188

Symptom    When the CTM client starts up, the disclaimer window is difficult to read because the font size is too small.

Conditions   See Symptom.

Workaround   None.


CSCtf33048

Symptom    The Actual Status field in CTM and CTC do not match.

Conditions   The Actual Status in CTC is not updated after making CTM changes in the Protection tab of a GE_XP card in L2 mode.

Workaround   Do one of the following:

From the GE_XP card Property Sheet, click the Update button.

Force a Refresh from NE operation.


CSCtg24779

Symptom    Information from the OTU2 Ethernet tab does not match the information in CTC.

Conditions   See Symptom.

Workaround   None.


CSCtg47289

Symptom    Inaccurate port error message when deleting a pluggable port module (PPM).

Conditions   This problem occurs when you try deleting a PPM and the client port is Out of Service and the trunk port is In Service. The following error message appears: "Cannot perform the action because the port is in service." The error message should specify that the trunk port is the one In Service and must be Out of Service before deleting the PPM.

Workaround   None.


CSCtg92374

Symptom    The minimum character requirement is different for a username in the Control Panel and the Domain Explorer.

Conditions   From the Domain Explorer > Administration > CTC-Based NEs > NE Authorization window, the username minimum character requirement is one character. However, from the Control Panel > Security Properties > CTC-Based NEs window, the username minimum character requirement is 6 characters.

Workaround   None.


CSCth69689

Symptom    The HTML report and exported data file include all NEs of the same type instead of just the NEs currently displayed.

Conditions   This problem occurs under the following conditions:

1. Open the Undiscovered NEs table.

2. Select File > HTML Report or File > Export.

3. Select All Rows in Current Page.

4. Browse and select a target file.

5. Click OK. All NEs of the same type, instead of just the NEs displayed on the current page, are displayed.

Workaround   None.


CSCth82811

Symptom    The Export Add Undiscovered NE(s) Data window does not close.

Conditions   This problem occurs under the following conditions:

1. Open the Undiscovered NEs table.

2. Select File > Export.

3. Select All Rows in Current Page.

4. Browse and select a target file.

5. Click OK. The Export Add Undiscovered NE(s) Data window does not close.

Workaround   Click the Cancel button.


CSCth85433

Symptom    Cannot create or modify a CTM user.

Conditions   This problem occurs under the following conditions:

1. In the Control Panel > Security Properties pane > CTM Security tab, the lockout period is greater than the logout period, and the logout option is disabled.

2. In the Create New CTM User wizard (or Modify User Properties wizard), you click Use Global Settings for the lockout or logout period. When you click Next, the following error message is displayed:"EID-290: The logout period must be greater than the lockout period."

This message is true when the logout option is enabled, but false when logout is disabled.

Workaround   When creating or modifying a CTM user, do not click the Use Global Settings option.


CSCth85448

Symptom    Cannot set termination mode on TXP cards after provisioning PPM.

Conditions   If PPM or data rate is provisioned on a transponder card, you cannot edit the Termination Mode value.

Workaround   Delete PPM or data rate and set the TXP termination mode first.


CSCth85521

Symptom    A user with SuperUser or SysAdmin privileges can disable the login state of all users, preventing them from logging into CTM.

Conditions   In the Domain Explorer window, choose Administration > CTM Users. Select all users; then, set the Login State value to Disabled. No error message is displayed. You can also set your own login state to Disabled.

Workaround   Before disabling the login state for all users, verify that at least one user with SuperUser privileges has a login state of Enabled.


CSCth95386

Symptom    Cannot set the Max value for 40G-MXP CV-S Line/Section 15-min/1-day thresholds.

Conditions   After setting the Max value, the value remains unchanged.

Workaround   None.


CSCti20298

Symptom    New SNMP trap destination is not visible from the NE Explorer > Network > SNMP tab.

Conditions   This problem occurs when you create an SNMP trap destination using the SNMP tab, then close and reopen the NE Explorer.

Workaround   Click the Refresh button to synchronize the NE configuration from the server.


CSCti16437

Symptom    Cannot set optical TNC alarm thresholds. An error is displayed.

Conditions   The problem occurs when the TNC optical ports are configured as OC3.

Workaround   None.


CSCti18584

Symptom    After restoring to default optical threshold values, an error appears even if the operation was successful.

Conditions   This problem occurs when some optical thresholds values on MSTP TXP/MXP cards are changed and then are restored to default values.

Workaround   None.


CSCti40572

Symptom    After an ML card reboot, a CTM node resynchronization occurs.

Conditions   This problem occurs when the ML card is initialized with a new barebones file.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtj90800

Symptom    A CTC-based network element never completes discovery.

Conditions   This problem occurs when one of the cards equipped on the network element has a Product ID longer than 20 characters.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk13290

Symptom    The service status is not automatically updated after activating or deactivating a service from the Control Panel.

Conditions   See Symptom.

Workaround   Manually refresh the data using the Refresh Data button from the Control Panel. Alternately, install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl53108

Symptom    Changes made in the OTN > Trail Trace Identifier subtab are not reflected in other active CTM sessions.

Conditions   See Symptom.

Workaround   None.


CSCtn31738

Symptom    When filtering CTM tables on MSNE, only shelf 1 results are displayed.

Conditions   This problem occurs after completing the following steps:

1. On MSNE, open the Alarm Browser, PM table, or Alarm Log.

2. Choose any filter option.

3. Click Apply. Only shelf 1 results are displayed.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, do one of the following:

Select only the shelf ID that you want results for when filtering a table.

Close and reopen the table and do not use the filter feature.

CTM Server and Database Caveats


CSCsf96351

Symptom    After the CTM server restarts, SONET NEs do not come up.

Conditions   This problem occurs under the following conditions:

1. The CTM server is running normally, and all NEs are in the Discovered state.

2. Enter ctms-stop to stop the CTM server.

3. Enter ctms-start to start the CTM server.

4. After the CTM server restarts, all SONET NEs are stuck in read-only mode.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCsl69043

Symptom    After a new installation, circuit discovery on a meshed network is slow. It takes a long time to open the Circuit table.

Conditions   This problem occurs when the database is empty after a new installation and discovery is performed on a meshed network.

Workaround   As soon as the discovery process starts to slow down, compute the Oracle internal statistics. The slowness disappears after the computation of the automatic statistics. With CTM, Oracle statistics are computed automatically on a default schedule:

Every weekend from 10:00 p.m. to 6:00 a.m. the following day.

The start of the weekend at 10:00 a.m., for a duration of two days.


CSCsv83245

Symptom    When performing a database backup, the following error message appears: "EID-609: There isn't enough space in backup directory. Do you want to continue?" However, if you continue, the backup operation succeeds. The CTM disk space test is too conservative.

Conditions   See Symptom.

Workaround   Ignore the error message and continue the database backup procedure.


CSCtf53439

Symptom    Archiving log files in the /opt/CiscoTransportManagerServer/log directory does not work. Only the latest log files are saved; older files are not archived.

Conditions   This problem occurs when the settings in the Control Panel > Logging Properties pane > General tab > Archiving area are as follows:

Log File Archiving: Enabled

Archive Directory: /opt/CiscoTransportManagerServer/log

Max. No. Archived Log Files: 2

Workaround   None.


CSCtf75225

Symptom    Multiple CTM clients respond slowly, exhausting the CTM server memory.

Conditions   This problem occurs when you launch multiple CTM clients on the same workstation and exhaust the workstation's physical memory. The CTM clients become stuck but remain connected to the CTM server. The CTM clients consume just enough events to keep the connection to the CTM server alive. The CTM server continues accumulating events until the processes' memory is exhausted. In the worst-case scenario, the CTM server restarts.

Workaround   Immediately close as many stuck CTM clients as possible. After you close the CTM clients, the CTM server recovers memory.


CSCtf75380

Symptom    While the system is running, the Oracle alert log (/oracle/admin/CTM/bdump/alert_CTM.log) reports the following error:

"ORA-01555 caused by SQL statement below (SQL ID: 7yn18zp2fyj92, Query
Duration=5149 sec, SCN: 0x0000.10b5db2d):
Sun Mar 21 03:43:19 2010
SELECT ALARM_COUNT_TABLE.*,ALARM_COUNT_TABLE.ROWID FROM ALARM_COUNT_TABLE"

Conditions   This problem occurs in a high-end setup when CTM is running on an UltraSPARC T2 Plus server with the Oracle database (/db0x, x = 1...5) in stripe (RAID 0) on two 300-GB internal disks (SAS-2 10,000 rpm). This configuration causes latency of input and output of the internal disks.

Workaround   A configuration that uses database partitions in stripe on two internal disks of 10,000 rpm exhibits poor performance, especially I/O performance. In high-end setups, it is strongly recommended that you use a disk array.


CSCtg22680

Symptom    Sometimes, NEs managed by an NE service with credentials set from the Control Panel > Security tab cannot connect to the CTM server. The Alarm Browser and Audit Log display a "Failed Authentication" message.

Conditions   This problem occurs with a new CTM server installation where no NEs have been added to the CTM domain, as follows:

1. Add the first NE for a certain NE service (for example, ONS 15454 SONET) in Preprovisioned state.

2. From the Control Panel > Security tab, enter the username and password information to connect to the NE.

3. Change the NE state from Preprovisioned to In Service. The NE fails to connect, and a "Failed Authentication" message is recorded in the Alarm Browser and Audit Log.

Workaround   Do the following:


Step 1 Restart the NE service.

Step 2 Mark the NE as Out Of Service; then, change the credentials twice. The first time, set the wrong credentials. The second time, set the correct credentials.

Step 3 Mark the NE as In Service and then back to Out of Service.

Step 4 From the NE Authentication tab in the Domain Explorer, set the NE credentials.

Step 5 Mark the NE as In Service.



CSCtg37914

Conditions   The prune_audittrail script incorrectly reports deleted rows.

Conditions   This problem occurs on a CTM server that has a medium, large, or high-end CTM configuration with a partitioned database. During installation, the NE_AUDIT_TRAIL_TABLE is created with partitions based on time stamp, starting from the first day of installation. Adding an ONS 15454 NE and enabling audit trail data collection causes the CTM server database to store some NE records with a time stamp earlier than the one used for the first partition. This data is stored in the first partition created during installation. The prune_audittrail script can only delete them by dropping the partition where they are stored.

Workaround   Since the prune_audittrail script can only delete partitions with a time stamp at least two days older than the current date, it is necessary to wait for the script to drop the partition storing the data.


CSCtg54951

Symptom    A new network partition is set to automatic discovery mode instead of manual discovery mode.

Conditions   This problem occurs when you:

1. Select a node from the Domain Explorer.

2. Select Configuration > CTC-Based Sonet/SDH NEs > Equipment Inventory Table.

3. Select File > Export.

4. From the Field Separator area, click Other and enter | as the field separator.

5. From the Export area, select Entire Table.

6. From the Export Data area, click Server (dir). Leave all other values as the defaults.

7. Click OK.

One job is scheduled and one file is created for each node in the inventory table.

Workaround   None.


CSCth70417

Symptom    A new network partition is set to automatic discovery mode instead of manual discovery mode.

Conditions   This problem occurs under the following conditions:

1. From Control Panel > UI Properties, select Manual as the default discovery mode.

2. Configure NEs to be managed in a network partition.

3. Create a new network partition (with no NEs) from the Subnetwork Explorer:

Set an NE Out of Service and delete all its links.

Move the NE with its subnet to the new network partition.

The new network partition is set to automatic discovery instead of manual discovery mode.

Workaround   From Control Panel > NE Service, change the discovery mode to manual.


CSCth90095

Symptom    The showctm command shows two orchestration services running.

Conditions   The problem occurs after restarting an SMService. Once the SMService restarts, another instance of an orchestration service begins.

Workaround   Restart the CTM server.


CSCth90520

Symptom    The CTC-based PM services generate a large log file under the /tmp directory, which fills the directory completely.

Conditions   This problem occurs if CTM is running in ARCHIVELOG mode, and if /db05 is completely full.

Workaround   Open a shell on the CTM server and remove the CTC-based PM service logs from the /tmp directory.


CSCth97940

Symptom    In a medium-sized configuration, CTM stops collecting historical PM data, audit log data, and audit trail data if database pruning is not performed every three months.

Conditions   If the database pruning period is longer than three months, the historical PM data, audit log data, and audit trail information can fill the Oracle database tablespaces, preventing the storage of new data.

Workaround   Set the database pruning interval to 30 days and wait 1 day for the pruning process to complete.


CSCti07957

Symptom    In a dual-server configuration, the following functions stop working a few days after you run the import_full_db.sh script: PM collection, TCA event reporting, and the ability to disable logins.

Conditions   This problem occurs because the following SQL scripts are missing from the /bin directory on the database workstation:

db_job.sql

db_job_enterprise.sql

add_tca_part.sql

prune_tca.sql

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, do the following to copy the missing scripts from the CTM server workstation to the database workstation:


Step 1 On the CTM database workstation, log in as the root user.

Step 2 Enter the following commands:

scp server-workstation:/opt/CiscoTransportManagerServer/bin/db_job.sql 
/opt/CiscoTransportManagerServer/bin/db_job.sql
scp server-workstation:/opt/CiscoTransportManagerServer/bin/db_job_enterprise.sql 
/opt/CiscoTransportManagerServer/bin/db_job_enterprise.sql
scp server-workstation:/opt/CiscoTransportManagerServer/bin/add_tca_part.sql 
/opt/CiscoTransportManagerServer/bin/add_tca_part.sql
scp server-workstation:/opt/CiscoTransportManagerServer/bin/prune_tca.sql 
/opt/CiscoTransportManagerServer/bin/prune_tca.sql 

where server-workstation is the server name or IP address of the workstation where the CTM server is installed.

Step 3 Run the import_full_db.sh script.



CSCti16526

Symptom    TCA_EVENT_TABLE partitions are managed incorrectly. A new partition is created daily at 18:00 a.m. In the time frame between 00:00 a.m. and 18:00 p.m., PM alerts might not be shown.

Conditions   This problem occurs because the TCA_EVENT_TABLE is not partitioned correctly. It has only one partition instead of multiple partitions, which causes loss of data. This problem affects CTM R9.2 installed in a medium, large, or high-end configuration. This problem does not affect small configurations.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, enter the following commands:

su - oracle
sqlplus ctmanager/password
exec add_tca_partition()
exec add_tca_partition()
exec add_tca_partition()
exit 

where password is ctm123! by default.


CSCti72307

Symptom    The CTM server process does not release unused allocated memory.

Conditions   This problem was discovered during CTM soak testing. To simulate a customer network, the test bed environment consists of the CTM server, clients, and 4,000 nodes that provide a constant flat alarm rate. After 30 days of uninterrupted service, the memory consumption of the CTM server process increases slightly and linearly over time.

Note that if the CTM server process were to restart due to this memory leak, it would do so only once in several years.

Workaround   None.


CSCti90949

Symptom    The CTM server restarts intermittently after it receives an overwhelming number of events from network services. The server eventually crashes because it cannot manage the event load.

Conditions   This problem occurs with a CTM server that has a large or high-end CTM configuration and has more than 1000 NEs with the DSS feature enabled.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtj01922

Symptom    There is no CTM database table that reports the status (active or standby) of UPSR spans.

Conditions   See Symptom.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtj70276

Symptom    The CTM server loses connectivity with NEs.

Conditions   This problem occurs when the trace level log is enabled.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, disable logging and restart the affected NE service.


CSCtj72766

Symptom    CTM must support the latest critical Oracle security patches.

Conditions   Oracle released the Patch Set Update (PSU) patches 9352164 and 9952234. For security reasons, CTM must support these Oracle patches.

Workaround   See Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234.


CSCtj86600

Symptom    The CIRCUIT_UPSR_BS_TBL database table is missing one of the rows for DRI selectors.

Conditions   This problem occurs in a network with two interconnected rings. If you create a UPSR DRI circuit and view the CIRCUIT_UPSR_BS_TBL database table, the table lists seven rows instead of eight. One of the rows for DRI selectors is missing.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk00438

Symptom    The CTM Data Migrator wizard lets you import the database in a dual-server installation when the CTM server is running.

Conditions   When the CTM server is installed in a dual-server setup, you can use the CTM Data Migrator wizard to import data while the CTM server is running. The operation is not prevented. The correct behavior is that you should not be able to import data while the CTM server is running.

As an example of this problem, if you select the option to disable the NE services during the import, the Control Panel erroneously shows the NE services as active and running. However, the showctm command does not list any NE services in the command output.

Workaround   Stop the CTM server; then, repeat the import operation.


CSCtk60031

Symptom    The alert_CTM.log contains the following error message: "ORA-00942: table or view does not exist." This problem causes some CTM instability.

Conditions   Unknown.

Workaround   None.


CSCtk62107

Symptom    The CTM server cannot start because the /db05 partition is full. The logarch function does not work.

Conditions   This problem occurs when performing a CTM restore or import with the ORA_INST option enabled. When the ORA_INST option is enabled, the /oracle directory file ownership is changed to oracle:dba. Some of these files, including the logarch file, can only be executed with root ownership.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, do the following:

1. Shut down Oracle after the restore/import has completed.

2. Enter following command:

tar xvf /ctm_backup/oracle_dir.tar 

3. After the file has been extracted, restart Oracle.


CSCtl01263

Symptom    The current time option in the CTM R9.2T database restore utility behaves as the backup time option.

Conditions   The problem occurs in CTM R9.2T when running the restore_db.sh script. The current time option is supposed to restore the database to the time when the restore utility was launched. Instead, the database is restored to the date and time of the most recent database backup.

Workaround   None.


CSCtl05918

Symptom    The Backup Upload feature does not work on CTM R9.2. The list of backup files is not shown.

Conditions   This problem occurs when the backup file is created using the CTM server.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtn31705

Symptom    The manage_cdump.sh script generates an output even when no core files exist.

Conditions   A cron job runs the manage_cdump.sh script daily. If no core dump files are found under the /opt/CiscoTransportManagerServer/bin/ directory, the script returns the following output:

core.*: No such file or directory.
 
   

The cron job then sends mail to root. The correct behavior is that the script should produce output and send mail only if it finds core files on the file system.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack. Alternately, use the crontab -e command to modify the cron job and redirect the output and error to /dev/null.


CSCtn39199

Symptom    Network services continue to run after the ctms-abort command is used to stop the server.

Conditions   After you enter the ctms-abort command to stop the server, the showctm command shows that one or more network services are still running.

Workaround   Use the showctm command to determine the process identifier (PID) of each network service. Then, enter the following command for each network service:

kill -9 <PID>
 
   

CSCtq02022

Symptom    A new TCA partition is not added to the tca_event_table database table. Consequently, PM tables do not color rows when the TCA is out of range.

Conditions   This problem occurs after running the import_full_db script. The add_tca_partition script does not run on the first day, but works correctly thereafter.

Workaround   None.

Cisco Transport Controller Caveats


CSCeb39352

Symptom    A DRI circuit does not have DRI protection. Instead, it has only path/SNCP protection.

Conditions   This problem can occur under any of the following conditions:

There is no DRI segment in the network, but CTC still succeeds in creating a DRI circuit by creating only a path protection/SNCP circuit.

The primary and secondary nodes of a DRI circuit are set up such that the path from source to primary destination might end up the same as the path by way of the secondary destination.

The SNCP path is the shorter path, as compared to the DRI path.

Workaround   Use manual routing.


CSCth80187

Symptom    The regeneration group name does not match the name in CTC. Also, if a regeneration group already exists, a CTC exception appears if you try to change the name.

Conditions   This problem occurs after setting the regeneration group name in CTM for a provisioned ADM card on an ONS 15454 NE.

Workaround   None.


CSCth85024

Symptom    Cross-connections from CTC hang on Cisco Carrier Routing System 1 (CRS-1) NEs after deleting an optical channel trail (OCHTRAIL) circuit from CTM.

Conditions   This problem occurs after deleting an OCHTRAIL circuit connecting two CRS-1 PLIM cards and passing through a DWDM network cloud. A partial circuit is still visible from CTC. However, on CTM, the circuit is removed and the NEs are reported correctly.

Workaround   Do one of the following:

From CTC, delete the partial circuit that is visible.

Close and open CTC.

High Availability Caveats


Note The following caveats apply only to customers who have purchased the high availability (HA) option.



CSCsv21407

Symptom    A database restore fails because some of the archive log files are missing from the CTM_backup directory.

Conditions   This problem occurs in a CTM HA single-node or dual-node cluster geographic setup with archive log enabled.

Workaround   Manually copy the missing archive log files from the other side of the redundancy.


CSCsv42835

Symptom    During a local HA installation, the /etc/rc2.d/S99dbora and /etc/rc0.d/K10dbora files are not removed from the primary and secondary servers.

Conditions   This problem occurs in an HA setup.

Workaround   Manually remove the S99dbora and K10dbora files.

CTM GateWay/CORBA Caveats


Note The following caveats apply only to customers who have purchased the CTM GateWay/CORBA option.



CSCin75602

Symptom    CTM GateWay/CORBA returns XC loopback values for CTPs even when a loopback is present in the corresponding line.

Conditions   This problem occurs when a loopback is active on a corresponding line.

Workaround   Ignore the XC loopback value.


CSCsz36278

Symptom    The getAllPTPs and getAllSupportedPTPs APIs report unsupported layer rates on nXP cards; for example, TXP_MR_10E, MXP_2.5G_10E, and 10_DME cards.

Conditions   This problem occurs under the following conditions:

1. Verify that CTM GateWay/CORBA and the CTM server are running.

2. Define an OSS CORBA client user and connect to the CTM GateWay/CORBA northbound interface.

3. Provision or preprovision an ONS 15454 nXP card.

4. Start the getAllPTPs or getAllSupportedPTPs API on the card. PTP values are reported for the layer rates. These values include some unsupported layer rates.

Workaround   None.


CSCse82549

Symptom    The emsMgr::EMSMgr_I::createTopologicalLink API returns an exception with the message "Failed to get containing equipment for a PTP."

Conditions   This problem occurs when you use the CTM GateWay/CORBA interface.

Workaround   Create the link in the CTM client GUI. The link is displayed correctly by APIs such as getTopologicalLink.


CSCtb11887

Symptom    CTM GateWay/CORBA reports a successful NE deletion incorrectly.

Conditions   This problem occurs when you use the CTM GateWay/CORBA deleteManagedElement API to delete an NE that is Out of Service. The failure that occurs during the purging phase in the CTM database is not reported to CTM GateWay/CORBA.

Workaround   None.


CSCtb85060

Symptom    CTM GateWay/CORBA and the CTM GUI report different Alarm Reporting statuses.

Conditions   This problem occurs when you use the CTM GateWay/CORBA SetTPData API to set the AlarmReport attribute on a card. The CTM GUI does not reflect the same status.

Workaround   Configure alarm suppression from the CTM GUI.


CSCtc32866

Symptom    The getCTMHistoryPMData API reports unnecessary values.

Conditions   This problem occurs under the following conditions:

1. Verify that CTM GateWay/CORBA and the CTM server are running.

2. Define an OSS CORBA client user and connect to the CTM GateWay/CORBA northbound interface.

3. Provision an ONS 15454 SMR-C card and enable PM collection.

4. Start the getCTMHistoryPMData API on the card. Active channel PM values are displayed unnecessarily. This problem also occurs for the getTPHistoryPMData API.

Workaround   None.


CSCtc32969

Symptom    The getTPHistoryPMData API reports unnecessary layer rates.

Conditions   This problem occurs under the following conditions:

1. Verify that CTM GateWay/CORBA and the CTM server are running.

2. Define an OSS CORBA client user and connect to the CTM GateWay/CORBA northbound interface.

3. Provision an ONS 15454 SMR-C card and enable PM collection.

4. Start the getTPHistoryPMData API on the card. Active channel PM values are displayed unnecessarily. This problem also occurs for the getCTMHistoryPMData API.

Workaround   None.


CSCtc33038

Symptom    During the CTM GateWay/CORBA installation, the Select Network Configuration screen shows truncated information.

Conditions   This problem occurs during CTM GateWay/CORBA installation. The screen should display the following information:

Choose from the following options:
 
   
See the installation guide for the number of NEs supported.
 
   
Small
Medium
Large
Highend

Workaround   None.


CSCtd50240

Symptom    The getCTMHistoryPMData API reports the following unnecessary values: PMP_RXRUNTS and PMP_RXTOTALERRORS.

Conditions   This problem occurs when using CTM GateWay/CORBA for ONS 15454 TXP_MR_10E cards with PM collection enabled. After you start the getCTMHistoryPMData API on the card, the following values are displayed unnecessarily: PMP_RXRUNTS and PMP_RXTOTALERRORS.

Workaround   None.


CSCtf17175

Symptom    The alarm notifications retrieved by CTM GateWay/CORBA do not report the physical location of the alarm.

Conditions   This problem occurs on alarm notifications related to low-order SDH circuits on cards with pluggable units, such as MRC-12 cards.

Workaround   None.


CSCtf24786

Symptom    The CTM GateWay/CORBA GetAllEdgePoints API does not retrieve trunk port transponders.

Conditions   This problem affects any network with transponder cards.

Workaround   None.


CSCtg52429

Symptom    The CTM GateWay/CORBA definition of an edge point does not comply with the TeleManagement Forum (TMF) definition of an edge point.

Conditions   According to the TMF 513 version 3.1, edge points are defined as follows:

An Edge Termination Point (Edge TP) is a Termination Point (TP) that is at an entrance or exit point of a MultiLayer Subnetwork (MLSN), (i.e. add-drop or TPs that terminate topological links between two Subnetworks).

However, CTM GateWay/CORBA defines edge points as PTPs that are not part of topological links. This definition differs from the TMF definition of an edge point.

For example, in a termination point linked by a topological link to another managed element, the CTM GateWay/CORBA GetTP API returns the following parameter:

...
org.tmforum.mtnm.terminationPoint.TPProtectionAssociation_T 
tpProtectionAssociation=TPPA_NA,
boolean edgePoint=true,
org.tmforum.mtnm.globaldefs.NameAndStringValue_T[] additionalInfo={}
}
...

According to the TMF standard, the API should return:

boolean edgePoint=false 

The same problem affects the GetAllEdgePoints and GetAllEdgePointNames APIs.

Workaround   None.


CSCti03098

Symptom    The GateWay/CORBA getAllCtmMEInternalPatchord API shows NOT USED instead of AUTOPROVISIONED.

Conditions   The problem occurs when an internal connection between the 80-WXC-C card and another card (for example, a transponder or muxponder card) is AUTOPROVISIONED.

Workaround   None.


CSCti09988

Symptom    The CTM GateWay/CORBA CreateTopologicalLink API returns an exception when creating SONET/SDH manual links. However, the manual link is created successfully.

Conditions   This problem occurs in the CTM GateWay/CORBA API interface.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCti10764

Symptom    The GateWay/CORBA GetManagedElement API incorrectly reports the 40-Gb layer for unsupported NE software releases.

Conditions   This problem occurs after running the Gateway/CORBA GetManagedElement API on NE software releases prior to NE software release 9.2. The 40-Gb layer was not supported until CTM R9.2.

Workaround   None.


CSCti80797

Symptom    The getCTMHistoryPMData API returns a PM data file with no data when layer rate 15 (LR_STS3c_and_AU4_VC4) or 14 (LR_STS1_and_AU3_High_Order_VC3) are used.

Conditions   This problem occurs when using the CTM GateWay/CORBA getCTMHistoryPMData API.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl11227

Symptom    The CTM GateWay/CORBA getAllSubnetConnectionNameswithTP and getAllSubnetworkConnectionsWithTP APIs shows an exception on ONS 15600 NEs.

Conditions   See Symptom.

Workaround   Use the CTM GateWay/CORBA getAllSubnetConnectionName and getAllSubnetworkConnections APIs.


CSCtl11270

Symptom    The CTM GateWay/CORBA getSnc and getAllSNC APIs show a wrong FTP value on STS circuits created between two ASAP_4 cards with an Ethernet PPM port.

Conditions   See Symptom.

Workaround   None.


CSCtl50071

Symptom    The GateWay/CORBA SetTpData API on connection termination points (CTPs) seldom works on ONS 15600 NEs.

Conditions   See Symptom.

Workaround   None.


CSCtl53250

Symptom    Historical PM data is not retrieved on some layer rates for ONS 15600 NEs.

Conditions   The GateWay/CORBA getCTMHistoryPMData and getTPHistoryPMData APIs do not work for ONS 15600 SDH NEs on the following layer rates:

LR_Section_OC3_STS3_and_RS_STM1

LR_Section_OC12_STS12_and_RS_STM4

LR_Section_OC48_STS48_and_RS_STM16

LR_Section_OC192_STS192_and_RS_STM64

LR_Line_OC12_STS12_and_MS_STM

The GateWay/CORBA getCTMHistoryPMData API does not work for ONS 15600 SDH on the following layer rates:

LR_STS1_and_AU3_High_Order_VC3

LR_STS3c_and_AU4_VC4

For 15600 SONET NEs, the following layer rates do not work:

14. LR_STS1_and_AU3_High_Order_VC3

15. LR_STS3c_and_AU4_VC4

Workaround   None.


CSCtl69996

Symptom    On ONS 15600 SDH NEs, the following APIs return an invalid layer rate exception:

Create new SNC

Create and activate SNC

The following APIs return an empty CTP value:

GetAllSNC

GetSNC

The following API returns an "errorReason=Invalid input CTP Name....." exception:

getCTPsAndTopologicalLinks

Conditions   This problem occurs when VC3 circuits exist on ONS 15600 SDH NEs, and you then try to create VC3 high-order circuits on the same NEs.

Workaround   None.


CSCtl71105

Symptom    APIs that involve CTP do not work for ONS 15600 SDH NEs,

Conditions   The problem occurs on ONS 15600 SDH NEs when GateWay/CORBA APIs are launched and filtered at the CTP level. CTPs are not managed correctly for VC3 HO circuits. The following APIs do not work:

getContainedPotentialTPs

getContainedPotentialTPNames

getContainedInUseTPs

getContainedInUseTPNames

getAllPTPsForSNCProvisioning

getAllCTPsForSNCProvisioning

Workaround   Launch the API at the NE or PTP level.


CSCtl73675

Symptom    The getCTMHistoryPMData and getTPHistoryPMData APIs return an empty file or 0 PM.

Conditions   This problem occurs when the APIs execute with layer rates 15 (LR_STS3c_and_AU4_VC4) or 14 (LR_STS1_and_AU3_High_Order_VC3) and filter at the PTP level.

Workaround   Launch the APIs at the NE level.


CSCtn02279

Symptom    The API getAllSupportedPTPs fails on 40G_MXP_CE_C and 40E_TXP_C cards.

Conditions   This problem applies when 40G_MXP_CE_C and 40E_TXP_C cards are configured with internal patchcords.

Workaround   Delete the cards from the NE; then, readd them without internal patchcords.


CSCtt14314

Symptom    When you use a filter, the getAllVCATSNCs API shows all VCAT circuits.

Conditions   This problem occurs due to filtering by layer 14/layer 15 and VCAT member circuits.

Workaround   None.

NE-Specific Caveats

This section includes the following information:

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15305

Cisco ONS 15310

Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET

Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH

Cisco MGX Voice Gateway


CSCse39608

Symptom    The CTM Alarm Log continues to report card, line, path, and port modify alarms every eight hours.

Conditions   This problem occurs under normal conditions.

Workaround   Complete the following configuration before starting CTM or the MGX VG NE service:


Step 1 Enter the following command:

cd opt/svplus/config
 
   

Step 2 Open the NMServer.conf file using a text editor.

Step 3 Search for "PERIODIC_RESYNC_INTERVAL."

Step 4 Change the value from 8 to 0. It should show PERIODIC_RESYNC_INTERVAL 0.

Step 5 Start CTM or the MGX VG NE service.



CSCse96373

Symptom    CTM is not synchronized with the MGX NEs, or the SNMPs that CTM requests from the MGX NEs are not successful. Also, the Alarm Browser frequently reports a Process Restarted alarm.

Conditions   This problem occurs when MGX NEs that are supported in CTM R8.5 are installed on a Solaris 10 machine.

Workaround   By default, Solaris 10 machines run the Internet information server of port 9010, which is required in one of the CTM processes. To stop the process in a session, enter the following commands on the Solaris server with SuperUser privileges:

ps -aef | grep "htt"
kill -9 pid
ps -aef | grep "htt+server"
kill -9 pid
 
   

At this time, the MGX NE service can be stopped and then started for all CTM processes managing the MGX NEs. Enter the following commands on the Solaris server with SuperUser privileges to stop the Internet/Intranet Input Method (IIIM) server from restarting after the system reboots:

cd /etc
find ./ -type f | xargs grep "htt"
 
   

The entries in the resulting rc*.d files need to be removed or the files need to moved to a different location if they are meant for the IIIM process.

These steps should be performed by users with System Administrator privileges.


CSCsg27309

Symptom    MGX nodes encounter errors or do not synchronize after configuration.

Conditions   This problem occurs when you enter the command ps -aef | grep "htt". The following message is returned: "/usr/lib/im/htt -port 9010 -syslog -message_locale C >/dev/null 2 >&1 &."

Workaround   Make sure that the following ports are available:

9000

9003

9004

9006

9007

9008

9010

Udp 2500

If you need to use the IIIM server, the base ports of the MGX process must be remapped in the /opt/svplus/config/process.conf file to a port other than 9000. You must do this before starting CTM with MGX support on Solaris 10 machines.


CSCsg97551

Symptom    Cannot retrieve MGX NE information from the audit trail.

Conditions   This problem occurs when using CTM GateWay/CORBA with Orbix R6.0. This problem is resolved in Orbix R6.3.

Workaround   Close CTM, restart Orbix, and restart CTM.


CSCsh91128

Symptom    No error message is shown if more than 20 MGX nodes are added to a medium-sized CTM server.

Conditions   See Symptom.

Workaround   Install a large or high-end CTM server when you need to manage more than 20 MGX nodes.


CSCsu67520

Symptom    MGX NEs are not visible in the Subnetwork Explorer.

Conditions   This problem occurs when you:

1. Stop the MGX NE service.

2. Move the MGX node from the default MGX network to another subnetwork.

3. Restart the MGX NE service.

4. Open the Subnetwork Explorer. The MGX NE is shown under the default MGX network instead of under the subnetwork where the NE was moved.

This problem also occurs when you:

1. Stop the MGX NE service.

2. Move all MGX NEs from the default subnetwork to another subnetwork and then delete the default MGX network.

3. Restart the MGX NE service.

4. Open the Subnetwork Explorer. The MGX NEs are missing from the Subnetwork Explorer tree. To avoid this problem, do not delete the default MGX network from the Subnetwork Explorer tree.

Workaround   None.

Cisco ONS 15216 EDFA


CSCsg79599

Symptom    Cannot create an ONS 15216 EDFA2 SNMP community view using a wildcard mask.

Conditions   This problem occurs when you add an ONS 15216 EDFA2 R2.4 NE.

Workaround   None.


CSCsi32169

Symptom    The NE Explorer does not refresh and shows blank fields when you perform a Refresh from NE operation.

Conditions   This problem occurs when you perform a Refresh from NE operation from the NE Explorer after the ONS 15216 EDFA3 NE has been up and running for a long time, and there are no actions performed on the NE.

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


CSCsl06434

Symptom    The communication state of ONS 15216 EDFA3 NEs is Initialization Failed after rebooting the CTM server.

Conditions   This problem applies to ONS 15216 EDFA3 NEs on a dual CTM server installation and occurs after the CTM server reboots.

Workaround   Wait until the NE polling completes. Alternatively, mark the NE as Out of Service and then In Service.


CSCth53325

Symptom    ONS 15216 NEs disconnect from CTM and cannot be reconnected.

Conditions   This problem occurs when a single NE service manages more than 100 ONS 15216 NEs.

Workaround   Restart the ONS 15216 NE service.


CSCuk53021

Symptom    Users who are logged into an ONS 15216 EDFA3 NE cannot be logged out from CTM.

Conditions   The Log Out User feature in the NE Active User List table is not available for ONS 15216 EDFA3 NEs.

Workaround   Use the TL1 command DLT-USER-SECU::userid:123; to delete the user.


CSCuk53024

Symptom    The NE Active User List table for the ONS 15216 EDFA3 does not update when users log into or out of an NE.

Conditions   This problem occurs when you select an EDFA3 NE in the Domain Explorer and choose Administration > ONS 15216 > NE User Access Administration. In the NE User Access Administration table, choose Edit > NE Active Users. The table shows a list of users who are logged into the NE when the NE was marked as In Service in CTM. New updates are not reflected.

Workaround   Click the Refresh Data tool in the NE Active User List table.

Cisco ONS 15305


CSCeh40971 (Related caveat ID: CSCuk59381)

Symptom    The remote console echoes the password back to the user.

Conditions   This problem occurs when you start a remote console on the ONS 1530x from a CTM client running on Solaris. As you type the password, the Telnet session echoes back the password in plain text instead of asterisks (******).

Workaround   Before typing the password, change the Telnet client mode from Line to Character. Enter Ctrl + ] and then type mode character and press Enter. You are now in Character mode.


CSCsd28777

Symptom    When the timing standard is changed from SONET to SDH, the update appears only after a 1- to 2-minute delay.

Conditions   See Symptom.

Workaround   Wait until the tab updates correctly.


CSCsd57233

Symptom    When circuits are deleted, the DCC terminations of the ports involved in the circuit and ports related to endpoints are deleted from the CTM database. DCC terminations are not shown in the NE Explorer > DCC tab.

Conditions   This problem applies to DCC terminations and ports related to endpoints on STM cards on ONS 15305 NEs when circuits are deleted.

Workaround   Synchronize the NE.


CSCsd59855

Symptom    The alarm severity of discovered SDH links remains critical even if 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 In Service.


CSCsd90033

Symptom    Cannot delete DCC terminations on STM-1 ports when a 1+1 MSP protection group has been created.

Conditions   This problem applies to STM-1 ports on ONS 15305 R3.0 NEs with 1+1 MSP protection groups.

Workaround   None.


CSCse80101

Symptom    The ONS 15305 R3.0 NE Explorer > Alarm tab lists two profiles: Default and Node. No matter which profile you select, the Profile column is always set to Node.

Conditions   This problem applies to all cards, backplane, and noncard objects on ONS 15305 R3.0 NEs.

Workaround   None.


CSCsg79603

Symptom    When you perform a Force or Lockout switch on a 1+1 protection group between ports 1 and 2 of the STM-1S1.1-1-LC/E1-21 card, the switch automatically clears within 2 minutes.

Conditions   This problem applies to 1+1 protection groups between ports 1 and 2 of STM-1S1.1-1-LC/E1-21 cards.

Workaround   None.


CSCsg90604

Symptom    A caret (^) is added to the circuit name when the circuit is created between ONS 15305 and ONS 15454 NEs.

Conditions   This problem occurs when the circuit is created between ONS 15305 and ONS 15454 NEs.

Workaround   None.


CSCsh15353

Symptom    The VLAN tab in the NE Explorer of the E100-WAN-8 card is not refreshed when you perform a Tagged or Untagged operation.

Conditions   This problem applies to E100-WAN-8 cards on ONS 15305 NEs.

Workaround   Refresh data from the NE to update the status of the VLAN tab.


CSCsh48269

Symptom    The following problems are observed:

Some alarms show the wrong NE alarm time stamp and NE clear alarm time stamp. Both time stamps are different from those shown in CTC.

The CTM server is notified of some alarms twice.

Conditions   This problem occurs when a circuit is created and then fiber cuts are performed to generate loss of signal, loss of frames, and RDI alarms.

Workaround   None.


CSCsh53422

Symptom    Low-order circuits between ONS 15305 and ONS 15454 SDH NEs remain in Partial state in CTC when the circuit is deleted in CTM. After a rediscovery process, the circuits are also in Partial state in CTM.

Conditions   This problem applies to LOP or LOP-V circuits that are created in CTC and then deleted from CTM, or vice versa.

Workaround   Perform an NE discovery before completely deleting from CTM the circuit that is in Partial state.


CSCsh62476

Symptom    The old Cisco logo is shown in the Cisco Edge Craft splash screen, About Cisco Edge Craft dialog box, and program icon in the Cisco Edge Craft main window.

Conditions   When you view Cisco Edge Craft for ONS 15305 R2.x NEs, the old Cisco logo is shown.

Workaround   None.


CSCtd99755

Symptom    In Cisco Edge Craft, the Tools > Vt100 Terminal menu opens an unresponsive terminal window that displays the text "connected." You cannot interact with the terminal, because the keyboard input is ignored.

Conditions   This problem occurs when you use Cisco Edge Craft with either Solaris GUI environment:

Java Desktop System

Common Desktop Environment

Workaround   In the CTM client, choose Configuration > ONS 15305 > Launch CLI.

Cisco ONS 15310


CSCtc40528

Symptom    From the PM Query wizard for an ONS 15310 OPT ML-100T-8 card, PoS ports set up as GFP show HdlcRxAborts counter values in the PM 15 Minute and 1 Day fields. The fields should display N/A.

Conditions   This problem occurs on PoS ports set up as GFP.

Workaround   None.


CSCtg52258

Symptom    The Pluggable Rate Create button is available even if the PPM has been deleted.

Conditions   This problem occurs only occurs on ONS 15310 CL CTX cards.

Workaround   None.


CSCtl83153

Symptom    The Link Integrity Disable column is not available from the Ethernet tab for CE-MR-6 and CE-100T-8 cards.

Conditions   None.

Workaround   None.

Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET


CSCsc99611

Symptom    On a release 4.1.4 NE, the Local Orderwire and Express Orderwire tabs are missing.

Conditions   See Symptom.

Workaround   Launch CTC.


CSCsf13620

Symptom    The position of the nodes in CTC is not maintained when CTC is launched from CTM.

Conditions   This problem applies to all CTC-based NEs. Launch CTC on a node from CTM. Use CTC to change the node positions on the network view. Close CTC and relaunch it. The node positions that were changed earlier are not maintained.

Workaround   Use a web browser to launch CTC and view all saved changes to node positions.


CSCsg27470

Symptom    The Memory Restore operation on a tunnel NE (TNE) fails with an error message.

Conditions   This problem occurs when you perform a Memory Restore operation on a TNE, view the Job Monitor table, and check the status of the operation. The operation fails and shows an error message about a byte mismatch.

Workaround   None.


CSCsg73328

Symptom    NEs do not come up in CTM after exchanging the MAC address between managed NEs.

Conditions   The NE does not come up if you assign it a MAC address that belongs to another NE that is managed by CTM. A MAC address that is not used by other NEs can be assigned to any NE.

Workaround   Delete the NE from the network and from the CTM server before assigning its MAC address to another NE.


CSCsg78092

Symptom    Cannot change the New Expected String field in the Section Trace tab of MRC-12 cards.

Conditions   This problem applies to the Section Trace tab of MRC-12 cards in the NE Explorer. When you change the New Expected String field from ASCII to hexadecimal form, changes are not applied to CTM and CTC.

Workaround   None.


CSCsg78171

Symptom    Cannot change the New Expected String field in the Section Trace tab of the NE Explorer.

Conditions   This problem occurs when the new string contains invalid characters. The string is updated in CTC when it contains valid characters.

Workaround   None. This problem occurs only when using invalid characters.


CSCsh20563

Symptom    The Standby Software column in the NE Software table does not update after a software download operation on a TNE or ENE.

Conditions   This problem occurs when you perform a software download operation on a TNE or an ENE that is connected to the TNE. Open the NE Software table. There are no values listed in the Standby Software column.

Workaround   None.


CSCsh96438

Symptom    CTM and CTC report inconsistent port information for TCA events that are generated on DS3 cards.

Conditions   In the Alarm Log, the physical location information is wrong for TCA events generated on DS3 cards. This problem occurs because the port information in CTC is different from the port information in CTM.

Workaround   None.


CSCsj47309

Symptom    Cannot set the Send AIS-V for DS-1 AIS field on XTC cards.

Conditions   In the NE Explorer > slot properties pane for the XTC card, you cannot set the Send AIS-V for DS-1 AIS field in the DS-1 tab > Line Config subtab.

Workaround   Use CTC to set the Send AIS-V for DS-1 AIS field.


CSCsk19478

Symptom    The GetEquipment API does not return newly added equipment.

Conditions   This problem occurs when you execute the GetEquipment operation after a set operation. This is a timing problem. The set operation is not completely synchronous and finishes before all previously requested operations are complete.

Workaround   Wait for some time; then, perform the GetEquipment operation again.


CSCsk24889

Symptom    DS1 and DS3 port alarms are suppressed.

Conditions   This problem occurs if there are alarms on the DS1-n and DS3-n XTC ports of ONS 15327 NEs.

Workaround   Mark the NE as Out of Service and then In Service to resynchronize the alarms.


CSCtd36370

Symptom    In the Optical Channel > Parameter tab, the From field (which displays the EXP_RX port) for a 40WXC card is missing the port name after a refresh event.

Conditions   This problem occurs after creating a circuit on a 40WXC card. Initially, the port number and port name are set correctly. However, after a refresh event, the port name is missing.

Workaround   Close and open the NE Explorer.


CSCtd60751

Symptom    The STS Thresh subtab of an OTU2_XP card incorrectly reports an error.

Conditions   This problem occurs under the following conditions:

1. Configure LAN to WAN on an OTU2_XP card.

2. Click the STS Thresh subtab.

3. Click Reset to Defaults. The following error message appears: "Reset to Defaults partially failed." However, all threshold values are restored correctly to the default values.

Workaround   None.


CSCtf69133

Symptom    Cannot enable AIS-V insertion.

Conditions   This problem occurs on ONS 15454 NEs. After you try to insert AIS-V, a warning message appears. When you click OK, AIS-V is not enabled.

Workaround   Use CTC to enable AIS-V insertion.


CSCti00208

Symptom    For the ADM_10G card, the PJSTSMON# value is incorrectly mapped to 0.

Conditions   The problem occurs on ADM_10G cards when the PJSTSMon# value is set to Off. The value Off means pointer justification monitoring is disabled. Although the setting is correctly sent to the device, the system value is later changed to 0.

Workaround   None.


CSCti00281

Symptom    For the ADM_10G card, the PJSTSMON# Off value is incorrectly mapped to 0.

Conditions   The problem occurs on ADM_10G cards when the PJSTSMon# value is set to Off. The column PJSTSMon# under SONET/SDH Linehas the number of the STS circuits to be monitored. The value Off means pointer justification monitoring is disabled. Although the setting is correctly sent to the device, the system value is later changed to 0. In practice, this is a wrong mapping of the Off value.

Workaround   None.


CSCtk13119

Symptom    The Section Trace tab shows no data for the OTU2_XP card.

Conditions   This problem occurs on ONS 15454 NEs equipped with the OTU2_XP card.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk96027

Symptom    Termination mode cannot be set from the Line tab > SONET/SDH Line subtab for 10G or 40G MXP/TXP cards.

Conditions   This problem occurs when client ports are plugged with an OC192/STM64 payload.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk13137

Symptom    The OTN Tab shows no data for a OTU2_XP card provisioned on a multishelf NE.

Conditions   This problem occurs on multishelf ONS 15454 NEs equipped with the OTU2_XP card.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl74392

Symptom    An error does not appear when OTU2_XP card mode settings are not updated. Instead, the card mode change appears successful even when settings have not been changed.

Conditions   This problem occurs when the ports are in IS state or if a Y-cable protection exists.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl74413

Symptom    The Active/Standby status is not updated in the Protection tab for an OTU2_XP card.

Conditions   This problem can be seen when the Force or Lockout button is selected from the Protection tab. The status is not updated.

Workaround   Click on other tabs and return to the Protection tab to see the update.


CSCtl76288

Symptom    The Active/Standby status is not updated in the Protection tab for an OTU2_XP card.

Conditions   This problem occurs if you set multiple values and then click Apply.

Workaround   Click Apply after setting each value.


CSCtl76340

Symptom    After applying a setting on the Ports tab of an OTU2_XP card, CTM opens a different tab.

Conditions   This problem occurs after setting a value from Line tab > Ports subtab. After clicking the Apply button, another tab is opened.

Workaround   Click on the previous tab to view changed setting.


CSCtl76891

Symptom    For OTU2_XP cards, CTM does not show the following columns in the NE Explorer > Line tab > Ethernet subtab:

Client Distance

Enable Flow Control

Conditions   This problem applies to OTU2_XP cards that are configured in LAN-to-WAN mode.

Workaround   Use CTC to view the missing columns.


CSCtl76905

Symptom    An error appears after resetting thresholds to the default values for an OTU2_XP card.

Conditions   After the Reset to Defaults button is clicked, CTM shows the following error message: "Reset to defaults partially failed." However, the operation is successful and all thresholds are set to default values. This error appears for the following tabs:

Optical Thresh tab > TCA 15 min subtab

Optical Thresh tab > TCA 1 Day subtab

Optical Thresh tab > Alarm Thresh subtab

Line tab > VC4 Thresh 15 Min subtab

Line tab > VC4 Thresh 1 Day subtab

OTN tab > G.709 Thresh 15 Min subtab

OTN tab > G.709 Thresh 1 Day subtab

OTN tab > FEC Thresh 15 Min subtab

OTN tab > FEC Thresh 1 Day subtab

Workaround   None. Ignore the error.


CSCtn02782

Symptom    The Line tab does not open on an ONS 15454 SDH NE STMxx card.

Conditions   This problem occurs on STMxx cards on ONS 15454 SDH NEs with version 9.2.0 or 9.2.1.

Workaround   Install the latest CTM 9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

Cisco ONS 15454-M2 and Cisco ONS 15454-M6


CSCtf78353

Symptom    The current time displayed from an ONS 15454 M6 NE is one hour behind the actual time.

Conditions   This problem occurs on an ONS 15454 M6 NE with an SNTP server source when the time zone is configured as GMT + 01:00 CET.

Workaround   None.


CSCti05620

Symptom    Cannot change General Timing values.

Conditions   Navigate to NE Explorer > Timing tab > General subtab and try to change the values. An error appears and the values are not applied.

Workaround   None.


CSCti05740

Symptom    Cannot change Timing Reference List values.

Conditions   Navigate to NE Explorer > Timing tab > Reference List subtab and try to change the values. The values you changed are not applied. This problem occurs when the NE Timing mode is set to Line or Mixed.

Workaround   None.


CSCti11123

Symptom    The CTM Circuit table does not show the trunk port name on a 10GE_XP OCHCC card if it is on an ONS 15454-M6 shelf.

Conditions   This problem occurs when you change the trunk port name on a 10GE_XP card on an ONS 15454-M6 shelf. The OCHCC circuit endpoints are not updated on the CTM Circuit table.

Workaround   None.


CSCtk13351

Symptom    Optical patchcords cannot be created if only OTU2_XP cards are provisioned inside the NE.

Conditions   This problem occurs when CTM manages an ONS 15454-M6 node with only OTU2_XP cards provisioned.

Workaround   Add a different transponder to the same shelf. Alternately, install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.

Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP


CSCsg69277

Symptom    OSC links do not behave correctly in CTM after a fiber cut. Unidirectional links from the optical channel ROADM card to the line amplifier become invalid, while unidirectional links from the line amplifier to the optical channel ROADM card remain valid. The Network Map displays an alarm.

Conditions   This problem occurs after a fiber cut between two nodes on an MSTP ring. Open the Network Map and check the link status.

Workaround   None.


CSCsh54851 (Related caveat ID: CSCsq70978)

Symptom    Provisioning operations such as card and PPM provisioning take too long to complete on a heavily loaded multishelf NE.

Conditions   This problem occurs when you provision a heavily loaded multishelf ONS 15454 NE.

Workaround   None.


CSCsh71348

Symptom    CTM cannot automatically route an OCHCC circuit.

Conditions   The source or destination nodes are connected by either OTS or virtual links. There are two different paths with a different number of hops to terminate the circuit, but only one path is available because the other path, which has fewer hops, does not provide optical connectivity to the destination node. The interconnecting node is connected to the destination node with a provisioned patchcord link between the trunk port and the optical channels.

Workaround   Do the following:

Include or exclude nodes during manual routing.

(Applicable to WXC nodes) Select the outgoing optical side during manual routing.


CSCsh95163

Symptom    Links in the Network Map are shown as valid and no loss of signal (LOS) alarm is generated.

Conditions   This problem occurs after a fiber cut on a span between two nodes. This does not cause the OSC links to become invalid. This problem is related to the Network Layer Alarm Configuration (NLAC) feature, which does not work correctly when a fiber cut occurs between two NEs. The LOS alarms on both ends of the span are not cleared in CTM, and a Payload Missing Indication condition is generated in CTM.

Workaround   None.


CSCsi03803

Symptom    SONET or SDH manual links or phantom links cannot be created between MRC-12 cards with OC-xx PPMs if the optical channel patchcords or virtual links are already created on that PPM. The following error is shown: "EID-4025: Exception: Failed to create the Phantom Link cerent.cms.topo.PhantomLinkException:..."

If the manual link has been created and virtual links are present, the manual link cannot be deleted and the following error message is shown: "EID-705: An error occurred while deleting the selected link(s). Check the communication status of the source and destination nodes."

Conditions   This problem occurs when you create virtual links on PPMs and then a manual link between MRC-12 cards that contain the PPMs.

Workaround   Create the manual link before creating the optical channel patchcords or virtual links.


CSCsl22029

Symptom    The Enable APC command is enabled if the APC domain is in a Disabled for Internal Reasons state. Executing the command does not have any effect on the network.

Conditions   This problem occurs on an APC domain that belongs to a DWDM network with a ring or mesh topology. The APC domain is in a Disabled for Internal Reasons state, and a card involved in the ring is in Equipment Failure state.

Workaround   None.


CSCtd60408

Symptom    CTM does not check the .xml file provided by the CTP.

Conditions   This problem occurs when an ANSI node is provisioned using the ETSI .xml file provided by the CTP.

Workaround   None.


CSCtl01522

Symptom    When you create pluggable port modules (PPMs) on a 40G_MXP_C card, CTM does not return an error if the port is in use.

Conditions   This problem occurs during PPM provisioning. If you try to add the next PPM before CTM updates the data, and if you use the same index ID that belongs to a PPM that you already created, CTM does not report an error that the port is in use. The PPM creation succeeds, but the PPM tab shows incorrect data.

Workaround   Delete and readd the 40G_MXP_C card.


CSCtl60411

Symptom    When you create a Generic Communications Channel (GCC) termination on 40E-TXP-C and 40E-MXP-C cards, the Admin State setting is ignored.

Conditions   See Symptom.

Workaround   Set the Admin State value in the Line tab.


CSCtl60447

Symptom    The Admin State setting is ignored while creating Section Data Communications Channel (SDCC) or Line Data Communications Channel (LDCC) terminations on 40E-TXP-C cards.

Conditions   This problem occurs when the client port is configured for OC-768 or STM-256.

Workaround   Set the Admin State value in the Line tab > Port subtab.


CSCtn05685

Symptom    Product ID and Version ID columns are not available on the GBIC Inventory tab of a CE-MR-10 card.

Conditions   See Symptom.

Workaround   Use CTC to view the values.

Cisco ONS 15600 SONET and Cisco ONS 15600 SDH


CSCeh63852

Symptom    When proxy is enabled on an NE, any DCC-connected ONS 15600 SDH LNE does not change to an ENE unless it is explicitly configured as an ENE.

Conditions   This problem occurs when you enable proxy to an NE that is connected to an ONS 15600 SDH LNE by a DCC link. The ONS 15600 SDH does not change to an ENE.

Workaround   Configure the ONS 15600 SDH as an ENE.


CSCse52546

Symptom    The Audit Trail feature does not work for ONS 15600 SONET NEs. The table is always blank, even if the time filter is set to None.

Conditions   This problem applies to ONS 15600 SONET NEs.

Workaround   None.


CSCsu51567

Symptom    The wrong ONS 15600 SONET or SDH profile is saved.

Conditions   This problem occurs when there is more than one GNE. An ENE might be assigned to the wrong GNE.

Workaround   Design the network topology with only one GNE for each ENE group.


CSCtc33209

Symptom    In the Domain Explorer > Identification tab, the Software Version field reports a running version of an ONS 15600 node when it should report the software version as standby.

Conditions   This problem occurs on ONS 15600 NEs.

Workaround   None.


CSCti70491

Symptom    The CAP and BACKPLANE equipment state for the ONS 15600 NEs shows "Not present."

Conditions   This problem occurs when CTM is managing ONS 15600 NEs.

Workaround   Install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtk95241

Symptom    A TSC card cannot be added on slot 10 or 4 when preprovisioning an ONS 15600 NE. The TSC card is not listed as an optional card to add.

Conditions   See Symptom.

Workaround   None.


CSCtk95409

Symptom    You cannot enter the description field from the NE Explorer or Domain Explorer for ONS 15600 NEs.

Conditions   This problem occurs when you try to enter text in the description field from the NE Explorer or the Domain Explorer. After clicking Apply from the NE Explorer, the description you entered is removed. After entering the description from the Domain Explorer, the description is not shown in CTC.

Workaround   None.


CSCtk98247

Symptom    The Protection tab displays Standby status instead of Active status.

Conditions   This problem occurs on protected 1+1 paths between OCxx cards. One card or port must be in Active status.

Workaround   None.


CSCtk99224

Symptom    The Alarm Behavior tab does not show PIM 1, PPM information on ONS 15600 NEs.

Conditions   This problem occurs on ONS 15600 NEs with an ASAP_4 card provisioned with at least a PIM 1,PPM and the corresponding port.

Workaround   Set the alarm behavior in CTC.


CSCtkl01324

Symptom    The SNMP destination IP address disappears from the SNMP tab of an ONS 15600 NE.

Conditions   The problem occurs after doing the following:

1. Select the ONS 15600 NE from the NE Explorer.

2. Select Network > SNMP tab.

3. Add a new trap destination IP address.

4. Click on another tab or close the NE Explorer.

5. Open the SNMP tab again. The IP address you added is gone.

Workaround   Manually refresh from the server.


CSCtl42434

Symptom    The RS Thresh 15 Min subtab also shows MS Thresh 15 Min data on ONS 15600 NE STMxx cards.

Conditions   See Symptom.

Workaround   None. Ignore the MS Thresh 15 Min data.


CSCtl42638

Symptom    CTM cannot manage VC3 circuits (L1) using the J1 Path Trace tab for ONS 15600 SDH STMxx cards.

Conditions   All VC3 circuit information is missing from the J1 Path Trace tab on STMxx cards. Also, the J1 path trace option is not available from a circuit trace.

Workaround   None.


CSCtl42648

Symptom    CTM cannot manage VC3 circuits (CM) using the J1 Path Trace tab for ONS 15600 SDH STMxx cards.

Conditions   This problem occurs on VC3 circuits involving ONS 15600 NEs.

Workaround   Use CTC.


CSCtl42812

Symptom    Error EID-465 appears after checking the Request Laser Restart option from the Auto Laser Shutdown tab of an ONS 15600 NE.

Conditions   See Symptom.

Workaround   Use CTC.


CSCtl47122

Symptom    The Ether Loopback tab > SONET STS (Ether) subtab is not updated on an ONS 15600 ASAP_4 card.

Conditions   An ASAP_4 card is provisioned with Ethernet layer rate set on some ports. After creating VC4 or VC3 circuits, the SONET STS (Ether) subtab is not updated with the new information.

Workaround   None.


CSCtl50080

Symptom    The VC value is incorrect in the VC tab of an ONS 15600 NE STMxx card.

Conditions   This problem occurs on a circuit created with STMxx cards.

Workaround   Use CTC to view the VC value. Alternately, install the latest CTM R9.2 patch. See Installing the Latest CTM R9.2 Patch or Service Pack.


CSCtl50355

Symptom    DCC termination points of an ONS 15600 NE ASAP card are not shown from the DCC tab.

Conditions   This problem occurs when DCC termination points are created on port numbers different from 1-x-x.

Workaround   None.


CSCtl52951

Symptom    Real time PM Optical data for ONS 15600 NE ASAP cards show valid values for OSC Power. Values should not be displayed for OSC Power.

Conditions   See Symptom.

Workaround   None. Ignore values for OSC Power.

Related Documentation


Note You can access the most current CTM R9.2 documentation online at http://www.cisco.com/en/US/products/sw/opticsw/ps2204/tsd_products_support_series_home.html.


The CTM documentation set comprises the following guides:

Release Notes for Cisco Transport Manager Release 9.2—This document.

Cisco Transport Manager Release 9.2 Installation Guide—Explains how to install CTM R9.2 and how to upgrade from previous releases.

Cisco Transport Manager Release 9.2T Installation Guide—Explains how to install CTM R9.2T.

Cisco Transport Manager Release 9.2 User Guide—Describes how to use the CTM software, which consists of user applications and tools for network discovery, network configuration, connection management, fault management, system administration, and security management.

Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual—Describes the CTM GateWay/CORBA northbound interface product that is available for CTM. This document serves as a reference for developers of OSS applications that work with the CTM GateWay/CORBA interface.

Cisco Transport Manager Release 9.2 Database Schema—Describes the database schema that CTM uses to store information in an SQL database such as the Oracle database. The document is designed for users who need to create their own reports without using CTM.

Cisco Transport Manager Release 9.2 High Availability Installation Guide—Explains how to install CTM in an HA environment.


Note To obtain the Cisco Transport Manager Release 9.2 High Availability Installation Guide, contact your Cisco account representative.


Cisco Transport Manager Release 9.2 ML Provisioning Methodology—Describes the methodology that CTM uses to provision ML-series cards.

Cisco Transport Manager Release 9.2 Basic External Authentication—Describes how CTM supports basic external authentication.

Migration Matrix for Cisco Transport Manager Service Pack Releases—Describes the migration matrix for CTM service pack releases.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.