Guest

Cisco Transport Manager

Release Notes for Cisco Transport Manager 9.1

  • Viewing Options

  • PDF (827.1 KB)
  • Feedback
Release Notes for Cisco Transport Manager Release 9.1

Table Of Contents

Release Notes for Cisco Transport Manager Release 9.1

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 Oracle 10.2.0.4 Patch

Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234

CTM-Supported JDK and Apache Versions

Resolved Caveats

Installing the Latest CTM R9.1 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

User 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 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.1


November 22, 2011

These release notes describe the caveats for Cisco Transport Manager (CTM) Release 9.1. These release notes accompany the Cisco Transport Manager Release 9.1 User Guide and the Cisco Transport Manager Release 9.1 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

Installing the Latest CTM R9.1 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.1, 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.

New Features and Functionality

The following table describes the new features and functionality in CTM R9.1.

Table 1-1 New Features in CTM R9.1 

New Feature
Description
Database Enhancements

Database migration from:

CTM R8.5 to R9.1

CTM R9.0 to R9.1

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

Server/Client Platform Enhancements

Confirmation of successful user password change

There is an enforced password change request when the default user logs in for the first time. After you change your password, you receive the following confirmation:

Your CTM password was successfully changed.

New Domain Explorer icons to track the progress of an NE purge

New Domain Explorer object icons let you track the progress of an NE purge. The following icon indicates that the NE purge is in progress:

If the NE purge fails, the following icon appears:

When the NE purge completes successfully, the NE is removed from the Deleted Network Elements group.

If the purge fails, you can repeat the purge and view the progress status.

Ability to export all data in the Alarm Browser or Alarm Log

You can export the entire contents of the Alarm Browser or Alarm Log to a text file. In previous CTM releases, you could export only the visible or selected rows. In CTM R9.1, you can export all data in the Alarm Browser or Alarm Log, as long as the window is not in automatic refresh mode. A progress bar tracks the export progress.

The entire-table export writes the data to a user-specified text file and retains the user-selected table customizations. For example, if you customized the table to make a column invisible, that column does not appear in the exported file.

In the User Preferences dialog box, you can enable or disable the ability to export the entire contents of the Alarm Browser or the Alarm Log. It might take longer to open the Alarm Browser or Alarm Log with the export entire table feature enabled.

Ability to display time information in 12-hour or 24-hour format

In the User Preferences dialog box, you can select 12-hour format (for example, 01:30 PM) or 24-hour format (for example, 13:30) for the display of time information.

Ability to create Layer 2 patchcords (virtual links)

You can use the Create Link wizard to create Layer 2 patchcords between network-to-network interface (NNI) ports on GE-XP or 10GE-XP cards when the card modes are set to L2 over DWDM. Layer 2 patchcords allow for the management of service provider virtual LAN (SVLAN) circuits between different Layer 2 domains.

Support for a calendar tool to specify the date setting

Many CTM windows incorporate a date/time setting. In previous CTM releases, you specified the date with separate drop-down lists for day, month, and year. In CTM R9.1, you can specify the date in a single calendar tool.

Use the calendar tool to choose the year, month, and day:

Year—Click the year combo box or the double arrow (<<, >>) at the bottom of the calendar.

Month—Click the month combo box or the single arrow (<, >) at the bottom of the calendar.

Day—Click the day of the month on the calendar. The current date is shown in blue.

Ability to save filters in the Alarm Log and Audit Log windows

You can save (and delete) filters in the following windows:

Alarm Log—Perceived severity (PS) filters

Audit Log—Category and Service filters

When you save a filter, the Filter tool changes to red in the Alarm Log and Audit Log windows. When you delete a saved filter, the Filter tool reverts to blue.

Ability to configure the CTM GateWay/CORBA client ports

In earlier CTM releases, CTM GateWay/CORBA was configured to use random ports and did not support a firewall between the OSS client and the CTM server. In CTM R9.1, you can configure CTM GateWay/CORBA to use static ports, enabling the use of a firewall between the OSS client and the CTM server.

Optical Enhancements

Support for CTC-based NE Release 9.1

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

ONS 15310 CL R9.1

ONS 15310 MA SDH R9.1

ONS 15310 MA SONET R9.1

ONS 15454 MSTP (ANSI/ETSI) R9.1

ONS 15454 MSPP (SONET/SDH) R9.1

ONS 15600 SONET R9.1

ONS 15600 SDH R9.1

Support for new optical cards

CTM manages the following new cards on optical devices:

OPT-RAMP-CE: Enhanced optical RAMAN pump, C-band.

SMR1_40_C: Single-module reconfigurable optical add/drop multiplexer (ROADM); 40 channels; C-band; with preamplifier, 100-GHz technology, and a WSSx2 module. This unit is optimized for degree-2 reconfigurable nodes.

SMR2_40_C: Single-module ROADM; 40 channels; C-band; with preamplifier and booster amplifier, 100-GHz technology, and a WSSx4 module. This unit provides an effective way to support multi-degree nodes up to degree-4.

T-DCU: Tunable dispersion-compensating unit cards that compensate for chromatic dispersion (CD) of the transmission fibre. There are two line cards:

TDC-CC (Coarse T-DCU)

TDC-FC (Fine T-DCU)

Support for the maintenance loop signaling entity (MLSE) transponder module

The following cards support the MLSE transponder module:

TXP_MR_10E transponder, C-band

MXP_2.5G_10E muxponder, C-band

MXP_MR_10DME data muxponder, C-band

When the MLSE transponder module is installed, CTM displays the cards as follows:

TXP_MR_10EX

MXP_2.5G_10EX

MXP_MR_10DMEX

Support for link integrity timers

CTM supports configurable link integrity timers for the following mapper cards on NE R8.5 and later:

ONS 15454 SDH and ONS 15454 SONET:

CE-100T-8

CE-1000-4

CE-MR-10

G1000-4

ONS 15310 CL, ONS 15310 MA SDH, and ONS 15310 MA SONET:

CE-100T-8

CE-MR-6

Support for new payload types on TXP_MR_2.5G and TXPP_MR_2.5G cards

CTM supports the following new payloads for TXP_MR_2.5G and TXPP_MR_2.5G cards:

DVB-ASI

ISC1

Support for single-card configuration on ADM-10G cards

In an ADM-10G single-card configuration, port 17 can be configured as a trunk port supporting an OC-192 payload. After it is configured as a trunk port, you can use port 17 in circuit, link, and server trail configurations.

Support for dual-server SNTP configurations

CTM supports dual-server SNTP configurations on CTC-based R9.1 NEs. You can use the NE Explorer or the SNTP Configuration dialog box to provision primary and secondary NTP and SNTP server addresses. The secondary NTP/SNTP address can have IPv4 or IPv6 format.

Ability to retrieve internal and learned MAC addresses on GE_XP and 10GE_XP cards

You can retrieve a list of internal and learned MAC addresses on a GE_XP or 10GE_XP card. You can retrieve the list of MAC addresses based on a single SVLAN value or a range of values from 1 to 4093. There is one MAC address per port, plus one MAC address that identifies the CPU. You can also clear all learned MAC addresses on the card. This feature applies to ONS 15454 SONET and ONS 15454 SDH R9.1 NEs.

Improved functionality when configuring SVLAN profiles and managing the SVLAN database

You can add, modify, and delete SVLAN profiles on ONS 15454 SONET and ONS 15454 SDH NEs.

You can also provision the SVLAN database for the network of ONS 15454 SONET and ONS 15454 SDH NEs. On R9.0 and earlier NEs, the SVLAN database is stored on the NE itself. On R9.1 NEs, the SVLAN database is stored on the 10GE_XP and GE_XP cards.

Support for editing the Trail Trace Identifier (TTI) from the Circuit Trace window

You can edit the TTI from the Circuit Trace window. The Edit TTI option is available for all the trunk ports that support the optical transport network (OTN). The Edit TTI option is not available if you disabled OTN on the trunk port, or if the trunk port is the protected actor of the protection group.

Ability to add user notes in the Equipment Inventory table

The User Note dialog box allows you to view and add user notes to equipment that has a valid serial number in the Equipment Inventory table. If a piece of equipment has a note, a User Note tool appears under the Note column.

Support for Optical Service Channel (OSC) power values on ONS 15454 SONET and ONS 15454 SDH NEs

Six new OSC power parameters are supported on all cards supported on ONS 15454 SONET and ONS 15454 SDH NEs.

For OPT-BST-E cards, in addition to the existing parameters, OSC power values are displayed in the Optical Line tab.

Support for Protection Switching Module (PSM) standalone management on ONS 15454 SONET and ONS 15454 SDH NEs

The PSM cards can be set to standalone mode on ONS 15454 SONET and ONS 15454 SDH NEs.

Support of Ethernet drop-and-continue circuit functionality for GT3 cards

You can create an additional drop point in order to bifurcate the volume of traffic moving from source to destination.

Support for 10GE LAN-to-WAN conversion on OTU2_XP cards on ONS 15454 SONET and ONS 15454 SDH NEs

CTM supports conversion of 10GE LAN traffic to 10GE WAN traffic on ports 1 to 3.

For OTU2_XP cards, 1-day and 15-minute thresholds for STS and VC4 are added to SONET and SDH, respectively.

Enhanced look and feel of the CTM server

The new windows manager that is installed with the Solaris 10 Java Development System renders a new look and feel to CTM.

Layer 1 Enhancements

Support for NNI endpoints during SVLAN creation and discovery

CTM supports SVLAN provisioning among NNI endpoints. The Create SVLAN wizard > Source and Destination panes display the NNI label in the Port field and in the Summary table.

Ability to open the Circuit table from the Link table > Configuration menu for SONET and Synchronous Digital Hierarchy (SDH) links

For SONET and SDH links between NEs that belong to different network partitions, you can launch the Circuit table from:

The Link table > Configuration menu

SONET and SDH links in the Network Map

Ability to open the Link Utilization table for SONET and SDH links

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

The Link table > Configuration menu

SONET and SDH links in the Network Map

Ability to create a provisional patchcord (PPC) Layer 1 virtual link between ONS 15600 and ONS 15454 NEs

You can create a PPC L1 virtual link between ONS 15600 and ONS 15454 destination points.

New GUI features to simplify tasks and enhance user experience

New buttons and added functionality simplify user tasks, as follows:

Minimizing the left pane with the use of a one-touch button.

Moving NEs in maps by dragging and dropping with the mouse, without pressing the Control key.

Adding links by right-clicking graphical maps for manual routing in circuit-related wizards.

Including and excluding links by right-clicking graphical maps in constrained routing.

Identifying protection channel access (PCA) links on graphical maps with a PCA label added above the link in the map.

Navigating to other subnetworks that contain values different from the values in the current network.

MGX Enhancements

Support for new MGX Voice Gateway releases

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

Cisco MGX 8880 Media Gateway R5.5.10

Voice-Enabled Cisco MGX 8850 Multiservice Switch R5.5.10

Voice-Enabled Cisco MGX 8830 Multiservice Switch R5.5.10

VXSM R5.4.21, R5.5.10

MGX SNMPv3 northbound interface support

CTM forwards traps from MGX devices to the external OSS. The northbound interface for CTM MGX now enables SNMPv3 to receive OSS registration requests and send traps to the OSS.

SNMPv3 offers authentication and privacy mechanisms to keep SNMP packet traffic on the wire confidential. Enhanced security prevents packets on the wire from being sniffed, SNMP community strings from being compromised, and configurations from being modified. SNMPv3 provides a user security model that uses encryption algorithms to authenticate and encrypt SNMP packets on the wire.

MGX automatic backup performance

When multiple MGX backups are scheduled, the backups are done in sequence instead of in parallel to avoid network congestion.

SNMP support to reset and switch cards on MGX devices

In previous CTM releases, the following operations were available only via the command-line interface (CLI). There was no SNMP support for these operations:

Reset a card: resetcd

Switch the PXM: switchcc

Switch the service module: switchredcd

In CTM R9.1, you can use the Card Reset operation to reset cards (resetcd) on MGX devices.

You can use the Switch Card operation to switch controller cards (switchcc) and service modules (switchredcd) on MGX devices.

Note Only SuperUsers and custom users with the appropriate privileges can reset and switch cards.

SFTP support for narrow band service module (NBSM) cards

CTM R9.1 provides SFTP support for uploading and downloading of configuration and statistics files.


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

NE Software Releases Added

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

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

ONS 15327 R4.1.8.2

ONS 15454 SONET R4.1.8.2

ONS 15454 SONET R8.5.1

ONS 15454 SONET R9.0.2

ONS 15454 SDH R8.5.1

ONS 15454 SDH R9.0.2

Sections and Caveats Added

The following section was added:

Installing the Latest CTM R9.1 Patch or Service Pack

The following caveats were added:

CSCte50207

CSCte63901

CSCtf00243

CSCtf04028

CSCtf08332

CSCtg33017

CSCtg30554

CSCtg62909

CSCtg80725

CSCth29044

CSCth85433

CSCth85521

CSCth97940

CSCti90949

CTM-Supported NE Software Releases

The following table lists the NE software releases supported in CTM R9.1.


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

Table 2 CTM-Supported NE Software Releases 

Product
Software Release
NE Version String

ONS 15216 100-GHz OADM1/2/4

Release 2.2.2

soadma.out-Ver2.2.2, 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 9.0

09.00-008I-17.17

Release 9.1

09.10-009J-25.17

ONS 15310 MA SONET

Release 7.2.3

07.23-007F-22.02

Release 8.5.3

08.53-008J-17.07

Release 8.6

08.60-009B-11.08

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

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

ONS 15327

Release 4.1.8.21

04.182-006-L2805

Release 7.2.3

07.23-007F-22.02

ONS 15454 SONET

Release 4.1.4

04.14-004C-09.23

Release 4.1.8.22

04.182-006-L2805

Release 7.2.3

07.23-007F-22.02

Release 8.5.13

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

08.60-009B-11.08

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.0.24

09.02-009L-17.19

Release 9.1

09.10-009J-25.17

ONS 15454 SDH

Release 7.2.3

07.23-007F-22.02

Release 8.5.15

08.51-008B-14.13

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

08.60-009B-11.08

Release 9.0

09.00-008I-17.17

Release 9.0.1

09.01-009F-20.11

Release 9.0.26

09.02-009L-17.19

Release 9.1

09.10-009J-25.17

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

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

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.0)

5.4.30

Release 5.5(0.0)

5.5.00

Release 5.5(10.0)

5.5.10

Voice-Enabled Cisco MGX 8830 Multiservice Switch

Release 5.4(30.0)

5.4.30

Release 5.5(0.0)

5.5.00

Release 5.5(10.0)

5.5.10

Voice-Enabled Cisco MGX 8850 Multiservice Switch

Release 5.4(30.0)

5.4.30

Release 5.5(0.0)

5.5.00

Release 5.5(10.0)

5.5.10

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

5.5.00

Release 5.5.10

5.5.10

1 In order for CTM to support the ONS 15327 R4.1.8.2, you must install CTM R9.1.0.350.3 or later.

2 In order for CTM to support the ONS 15454 SONET R4.1.8.2, you must install CTM R9.1.0.350.3 or later.

3 In order for CTM to support the ONS 15454 SONET R8.5.1, you must install CTM R9.1.0.350.3 or later.

4 In order for CTM to support the ONS 15454 SONET R9.0.2, you must install CTM R9.1.0.366.1 or later.

5 In order for CTM to support the ONS 15454 SDH R8.5.1, you must install CTM R9.1.0.366.1 or later.

6 In order for CTM to support the ONS 15454 SDH R9.0.2, you must install CTM R9.1.0.366.1 or later.


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 Oracle 10.2.0.4 Patch

Starting from CTM R9.0.1.400.1, the Oracle 10.2.0.4 patch (see CSCtj72796) is supported. To install the Oracle 10.2.0.4 patch, complete the following steps.


Note In a dual-server setup, install the patch on the database workstation.



Step 1 Verify that your server has enough RAM available for your CTM network size. See the Cisco Transport Manager Release 9.1 Installation Guide, section "Server Specifications" for details.

Step 2 Enter the following command to verify that the CTM R9.1 server is running:

showctm
 
   

Step 3 If the CTM server is running, enter the following command to stop it:

ctms-stop
 
   

Step 4 Log into the CTM database workstation.

Step 5 As the oracle user, enter the following commands to shut down Oracle:

su - oracle
sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown immediate
SQL> quit
lsnrctl stop
 
   

Step 6 Complete the following substeps to download and install the Oracle 10g 10.2.0.4 patch for Solaris (patch number 6810189):

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

b. Extract the 316900.1 document.

c. Click Advanced at the top of the Oracle MetaLink page.

d. Enter 316900.1 in the Document ID field; then, click Submit. The 316900.1 document provides the following information:

System requirements

Lists of resolved bugs

List of known issues

e. Click Patches.

f. Click Simple Searches.

g. Enter 6810189 in the Search by Patch Number(s) field.

h. Choose Solaris Operating System (SPARC 64-bit) from the Platform or Language list box.

i. Click Go.

j. Click Download to download the p6810189_10204_Solaris-64.zip file.

k. Enter the following command to log into the Oracle workstation as the oracle user:

su - oracle
 
   

l. Save the patch to the /oracle directory.

m. As the oracle user, copy the response file in the /oracle directory.

If you are installing the patch with 64-bit Oracle Enterprise Edition or 64-bit Oracle Standard Edition, enter:

cp /<mount_point>/400/config/400/patchset_64bit_10204.rsp /oracle
 
   

n. Enter the following command to extract the patch files:

Unzip p6810189_10204_Solaris-64.zip
 
   

A directory named Disk1 is created automatically.

o. Remove the p6810189_10204_Solaris-64.zip file from the /oracle directory.

p. Enter the following commands to install the patch:

cd Disk1
./runInstaller -silent -responseFile /oracle/patchset_64bit_10204.rsp
 
   

q. At the prompt to run the root.sh script, log into another terminal window as the root user and enter the following command:

/oracle/product/10.2.0/root.sh
 
   

r. At the prompt for the local bin directory, enter the following path in the root.sh script:

/oracle/product/10.2.0/local/bin
 
   

Note You are prompted to overwrite some files. Reply yes to all of the prompts.


s. Enter the following commands to remove the patch installation files:

cd /oracle
rm -rf /oracle/Disk1
 
   

Step 7 Complete the following postinstallation steps for the Oracle 10g 10.2.0.4 patch for Solaris (patch number 6810189):

a. Enter the following command to log into the database workstation as the oracle user:

su - oracle
 
   

b. Enter the following command to start the Oracle listener:

lsnrctl start
 
   

c. For single-instance installations, enter the following commands to use SQL*Plus to log into the database as the SYS user with SYSDBA privileges:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
 
   

d. Enter the following commands:

SQL> STARTUP UPGRADE
SQL> SPOOL /temp/patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF
 
   

This step might take several minutes to complete.

e. Using another terminal window, check whether the /temp/patch.log report contains any errors. If errors exist, correct them; then, rerun the catupgrd.sql script.

f. Enter the following commands to restart the database:

SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
 
   

g. Enter the following command to run the utlrp.sql script and recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql
 
   

h. Enter the following command to check the status of all components after the upgrade:

SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
 
   

In the command output, all components should have a status of VALID for a successful upgrade.

Step 8 Complete the following substeps to recompile database views after installing the Oracle 10g 10.2.0.4 patch for Solaris (patch number 6810189):

a. Enter the following commands to verify that the view recompilation has been performed:

su - oracle
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SELECT * FROM registry$history WHERE ID='6452863';
SQL> QUIT
 
   

If the view recompilation has been performed, the preceding commands return one or more rows. If the view recompilation has not been performed, the commands return no rows.

b. If it is necessary to recompile the views in the database, enter the following commands to run the precheck script, which reports the maximum number of views and objects that can be recompiled:

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @recompile_precheck_jan2008cpu.sql
SQL> QUIT
 
   

c. As the oracle user, enter the following commands to run the view recompilation script, if necessary. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA:

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP UPGRADE
SQL> @view_recompile_jan2008cpu.sql
SQL> SHUTDOWN;
SQL> STARTUP;
SQL> QUIT
 
   

d. Check for any errors in the vcomp_SID_timestamp.log file in the current directory.

e. If any invalid objects were reported, enter the following commands to run the utlrp.sql script:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
SQL> QUIT
 
   

f. Manually recompile any invalid objects. For example:

SQL> alter package schemaname.packagename compile;
 
   

Step 9 Complete the following substeps to download and install the OPatch (patch number 6880880):

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

b. Select Patch from the menu and search for the 6880880 patch.

c. Choose Solaris Operating System (SPARC 64-bit) from the Platform or Language list box.

d. Click Go.

e. Click Download to download the p6880880_112000_SOLARIS64.zip file to your local workstation.

f. Enter the following command to log into the Oracle workstation as the oracle user:

su - oracle
 
   

g. Save the patch to the $ORACLE_HOME directory.

h. Enter the following commands to unzip p6880880_112000_SOLARIS64.zip to your Oracle home directory:

cd $ORACLE_HOME
unzip p6880880_112000_SOLARIS64.zip
 
   

i. At the prompt asking if you want to replace all files, choose Replace All.

Patch 6880880 is now installed.

j. To verify that you have the Opatch utility installed, enter the following command as the oracle user:

$ORACLE_HOME/OPatch/opatch version
 
   

The following messages appear:

Invoking OPatch 11.2.0.1.0
OPatch version: 11.2.0.1.0
OPatch succeeded.
 
   

Note The OPatch version (11.2.0.1.0 or later) is different from the Oracle software version (10.2.0.4), because they are separate products.


k. Enter the following command to remove the temporary .zip file:

rm $ORACLE_HOME/p6880880_112000_SOLARIS64.zip
 
   

Step 10 Enter the following commands to shut down Oracle and the listener:

su - oracle
lsnrctl stop
sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown immediate
SQL> quit
 
   

Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234

Starting from CTM R9.0.1.400.1, the latest critical Oracle patches (see CSCtj72766) are supported. 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.0 and CTM R9.1 installed.

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

a. 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.)

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


c. 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.)

d. 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.)

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

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

g. 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.1.

Table 3 CTM-Supported JDK Version 

JDK Version
Caveat ID
Caveat
Comment

1.5.0_20

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


Table 4 CTM-Supported Apache Version 

Apache Version
Caveat ID
Caveat
Comment

2.2.13

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


Resolved Caveats

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


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


Table 5 Caveats Resolved in CTM R9.1 

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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

CSCsi01139

There is missing SONET performance monitoring (PM) data for a 15-minute robust PM data collection interval on ONS 15310 CL NEs.

CSCsj97000

It takes too long to preprovision cards that have too many ports and there is no indication that the operation is in progress.

CSCsk34470

The DS3 tab of the ONS 15310 CL NE Explorer is empty after configuring a broadband port that carries DS3 or EC1 payload.

CSCsq76213

The graphic map displayed for a high-level circuit trace or detailed circuit trace does not update after you switch circuit views.

CSCsq84105

The ETHERSTATSTXFIFOOVERFLOWEVENTS value for the CE-MR card shows N/A when retrieving historical PM data.

CSCsq99180

The getAllSupportedPTPs application program interface (API) fails for an OSCM card and returns an error message.

CSCsr11587

For a 10GE_XP card, if you launch a pseudo-IOS connection from the Tools menu, the Telnet window launches but does not respond to keyboard entries.

CSCsr22988

The Bulk FTP Configuration wizard does not display an error message when you enter invalid parameters. The job is scheduled and fails.

CSCsr25541

The IPv6 address format is not reported correctly.

CSCsr43528

EC1 ports are listed in the Optical tab and PPM ports are listed in the EC1 tab of a CTX card.

CSCsr65845

The CTM server cannot connect to and manage MGX NEs.

CSCsr71236

The port status does not update when you select the Force or Clear option from the Protection tab > Protection Groups subtab > Operations subtab > Protection Group Details area.

CSCsr86376

The MTU size value is not updated on a protected port.

CSCsu37386

Creation of a protected SVLAN circuit (Layer 2 1+1 plus FAPS protection) between 10GE_XP cards fails.

CSCsu41715

The wrong physical PM trunk port values are displayed for a 2.5G_DM card. The Physical PM table should show N/A trunk port values for Min TX Power, Avg TX Power, and Max TX Power.

CSCsu52555

When saving an SVLAN database or profile to a file, CTM should check whether the filename that you enter exists. If the file exists, CTM should prompt you to confirm whether or not you want to replace the existing database or profile file.

CSCsu62916

Cannot create dual-ring interconnect (DRI)-protected STS-v circuits in CTM. DRI protection is not available in the Create Circuit wizard.

CSCsu69633

QinQ-Transparent mode settings cannot be deleted or changed from an SVLAN circuit even after the SVLAN settings are deleted.

CSCsu74133

Sometimes, the Active IP Address field in the Domain Explorer does not update automatically.

CSCsu81327

Modifications to default settings from a saved file cannot be set on ONS 15454 NE versions 4.16, 4.62, and 5.08.

CSCsu94566

Line Data Communications Channel (LDCC) and Section Data Communications Channel (SDCC) links on an OTU2_XP card should not be discovered as routable links.

CSCsv21284

When using the Create SVLAN wizard to create a QinQ setting, an incorrect class of service (CoS) value is displayed.

CSCsv21500

An incorrect Inner SVLAN value is displayed in the QinQ tab of the GE_XP or 10GE_XP card when using CTC to change the Operation value from Double Add to Add or Translate Add to Translate.

CSCsv23067

In the CTM GUI, NEs are constantly being moved and taking a long time to be grouped into subnetworks. Also there is a large amount of database query activity.

CSCsv27126

CTM does not return an error if you select 1+1 protection for splitter-protected, optical channel patchcord links on an OTU2_XP card, even though 1+1 protection is invalid for splitter-protected links.

CSCsv34441

A card can be set in EFEC mode even when Y-cable protection is configured.

CSCsv36952

Circuit creation does not set the correct OTU2_XP card attributes when the card is in Regeneration mode.

CSCsv38910

Line tab values for Line Thresh 15 Min and 1 Day subtabs do not reset to the correct default values.

CSCsv44984

The Bulk FTP Configuration wizard does not display an error when an IPv6 address is entered as the FTP host address for an NE that does not have IPv6 enabled.

CSCsv45598

Sometimes, when launching the L2 Topology table, the following error message appears: "EID-333: A database timeout occurred."

CSCsv57817

Moving subnetworks across network partitions in the Subnetwork Explorer leads to inconsistent behavior.

CSCsv58015

The connectivity state of an unmanaged NE displayed in the Domain Explorer and Control Panel is inconsistent.

CSCsv59259

Active Channels and Power values from the Slot Properties pane > Optical Band tab are incorrect for a 4MD_xx.x card.

CSCsv65237

You cannot use CTM GateWay/CORBA to set the low power threshold (Power Low) on an OPT_RAMP_C card.

CSCsv76358

Sometimes, using CTC to change the port mode of an E1_21_DS3_E3_3 card on an E3 interface does not automatically update the information in the Broadband Ports tab.

CSCsv86239

A database export does not update the database tables correctly.

CSCsv88769

Values that are entered in the Network Element Properties pane > NE Authentication tab > CTM Server - SNMP Connection area are not validated when the SNMP protocol is set to SNMPv3.

CSCsv97145

The NE Explorer > VC tab of a CTX card shows the wrong high-order (HO) and low-order (LO) virtual channel (VC) values.

CSCsw17803

Open virtual concatenation (VCAT) circuit creation fails, and the physical termination point (PTP) information is shown incorrectly as VC4=0.

CSCsw25338

The port name is not displayed in the Physical Location column of the Alarm Browser for DS1 or DS3 cards.

CSCsw37547

Circuits remain in the CTM database with a CktState value equal to 12.

CSCsw39894

Setting the regeneration line name for specific ports on an OTU2_XP card (in Standard Regeneration mode) also sets the same regeneration line name for all remaining ports on the card.

CSCsw40134

After powering down and powering up the CTM server workstation, some duplicate groups appear in the CTM domain. These duplicate groups persist even after the CTM server is restarted.

CSCsw40388

A section trace cannot be configured on client ports.

CSCsw44603

The VC4 Threshold tab is not available for an E1_63_DS3_E3_3 card.

CSCsw49153

Provisioned SVLAN circuits are not displayed if the SVLAN table is started from the card view.

CSCsw50865

The Circuit Trace window shows a low-order Virtual Tributary (VT) circuit span incorrectly as LAP/VAP.

CSCsw63014

The Protection tab > Operation subtab > Protection Group Details area displays "No Status."

CSCsw63068

The High-Level Circuit Trace graphic map displays a gray link, instead of a green link, for an open-ended VCAT circuit.

CSCsw68470

You cannot modify an existing LDCC from OSI and IP (PPP) to IP (PPP) or from IP (PPP) to OSI and IP (PPP).

CSCsw69115

An incorrect value (-0.1) is reported on the OTN real-time PM panel even if OTN counters are disabled.

CSCsw69548

You cannot save an SVLAN name that contains commas.

CSCsw72382

The getTCATPParams API shows SONET thresholds for unsupported parameters.

CSCsw79060

The SNMPv3 wizard reappears with values after the client is locked and unlocked.

CSCsw79346

The SDH LO VC3 PM table displays PM values for a VC12 circuit.

CSCsw79969

You cannot perform a hard reset on an ONS 15310 MA CTX 2500 card.

CSCsw93005

The ODU Transparency value cannot be changed for an OTU2_XP card in Standard Regen mode.

CSCsw98943

A card can be set in EFEC mode even when the port is not in OOS, DSBLD state.

CSCsw99989

A patchcord link cannot be created between SONET/SDH card ports and SONET/SDH OTU2_XP client ports.

CSCsx03216

Connection with the NE is lost when saving or deleting an SVLAN database that contains several SVLANs on multiple cards.

CSCsx15019

The Card tab should not be available from the NE Explorer for the OPT_BST_L card.

CSCsx15063

The Card tab values are not updated after PPM or payload provisioning.

CSCsx28572

Sometimes you cannot enable a LAN subnet from the OSI tab.

CSCsx32065

You cannot filter the Network Map to show OCH transport unit links.

CSCsx34727

When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0, if the network configuration size upgrade option is selected, an error appears stating that you must increase disk space to continue with the migration. CTM incorrectly checks the partition free space instead of the partition size. Also, the error message should be a warning message.

CSCsx38249

Deletion of SVLAN profiles is not saved when saving to a file.

CSCsx44183

In a protected SVLAN circuit, deletion of endpoints does not work correctly from the SVLAN table (Configuration > Delete Drop).

CSCsx49646

From the SVLAN wizard, the Add Drop operation fails (SVLAN Table > Add Drop).

CSCsx69981

When creating MGC IP address entries using the CTM GUI, only an MGC Index from 1 to 4 can be entered. You should be able to create an MGC Index from 1 to 24.

CSCsy74450

In a small network configuration, the CTM server installation fails when the optional db01_rd and db02_rd partitions are configured.

CSCsy84624

The switch selector for UPSR/SNCP circuits is missing from the Circuit Trace window.

CSCsx93323

CTM displays a "Media Gateway Link state, pendingIs" alarm with a severity set to Warning. In other element managers, this type of alarm has a severity set to Major.

CSCsz63857

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

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

CSCtd18515

Cannot create L2 topologies or add cards when the Graphical Enhanced option is selected.

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

CSCtd50557

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

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

CSCtd77921

Adding an SVLAN drop fails and may cause traffic loss.

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

CSCte85662

The CTM R9.1 client does not start in Windows. The load bar reaches 100% and the application hangs.

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

CSCtf13479

While upgrading to CTM R9.1, the sched_for_ctm_stats.sql command fails.

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

CSCtf52162

An incorrect time is displayed in the Time Stamp field of the real-time PM table. When the Time Stamp field should display Central European Summer Time (CEST), it incorrectly displays Greenwich Mean Time (GMT). The correct server time is displayed at the bottom right of the real-time PM table.

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

CSCtf78021

After upgrading from CTM R8.5 to CTM R9.1, the CTM Config database table shows discrepancies.

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

CSCtf78039

After upgrading from CTM R8.5 to CTM R9.1, the initCTM.ora file is not updated correctly.

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

CSCtg19956

Discovery time tracing is enabled by default. Instead, NE services should start up with discovery time tracing disabled.

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

CSCtg38402

ROADM power monitoring does not work correctly in the CTM R9.1.0.350.3 patch.

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

CSCtg62909

Real-time PM graphs do not work correctly if the Time Display option is set to 24 Hour.

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

CSCtg73332

The Alarm Log shows duplicate clears for the same alarm.

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

CSCtg78740

The CTM GateWay/CORBA client does not update when equipment is provisioned or deleted.

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

CSCtg89916

Errors and stack traces are included erroneously in the log file in the /tmp directory.

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

CSCtg92011

The minimum length of the CTM username should change from six to three characters.

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

CSCth05616

The NE Explorer does not display 32WSS optical channel parameters. The Optical Channel tab is blank for 32WSS cards.

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

CSCth21611

Loss of communication alarm storms occur periodically on CTC-based network services.

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

CSCth29044

Archived redo logs are generated incorrectly in the /oracle partition instead of in the /db05 partition. If the /oracle partition fills up, Oracle hangs and CTM crashes.

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

CSCth31822

Autodiscovered links change incorrectly to invalid.

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

CSCth43371

The CTM R9.1.0.365.2 patch installation fails on a dual-server setup.

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

CSCth53325

ONS 15216 NEs disconnect from CTM and cannot be reconnected.

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

CSCth69497

The NE service does not respond promptly to commands sent from CTM clients.

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.

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

CSCth87771

Sudo software version 1.6.6 (bundled with CTM) has a potential security vulnerability or exposure (CVE-2010-1646).

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

CSCth92179

CTM loses NE connectivity and the garbage collector usage is high.

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

CSCti59552

CTM reloads the same .gif, which causes high memory usage in the CTM client and slow performance.

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

CSCti83745

The ONS 15454 DWDM tab > ROADM Power Monitoring subtab shows an hourglass icon continuously.

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the CTM-Supported Critical Oracle Patches 9352164 and 9952234.

CSCtj72796

CTM must support the Oracle 10.2.0.4 patch. See Installing the CTM-Supported Oracle 10.2.0.4 Patch.

CSCtj90800

A CTC-based NE never completes discovery.

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

CSCtl19084

CTM does not prune PM tables automatically.

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

CSCtn76520

The PM Data Collection stops working for all Optical Networking System (ONS) Network Elements (NEs).

Note This caveat is fixed with the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

CSCtq04889

Sometimes you cannot launch audit trail from the CTM domain explorer.

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

CSCtq26433

NE service is stuck and several operation may be affected.

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

CSCtr28626

Unable to launch service uptime, service uptime log, Gateway/SNMP Users and TNE Devices.

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

CSCts00126

CTM backup fails.

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


Installing the Latest CTM R9.1 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.

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

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.1, 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.1 as of May 24, 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 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.1 patch or service pack. In such cases, the patch or service pack that contains the fix is indicated as a workaround.


Installation and Upgrade Caveats


CSCsw69697

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

Conditions   This problem occurs if the CTM release you are upgrading from (for example, CTM R8.0 or CTM R8.5) has debug active on modules associated with NEs that are not supported in CTM R9.0.

Workaround   Before upgrading, clear debug on modules that are associated with NEs that are not supported in CTM R9.0.


CSCsy87978

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

Conditions   See Symptom.

Workaround   Do the following:

1. Reinstall the older CTM version.

2. Restore the database.

3. Proceed with a new upgrade.


CSCsz70254

Symptom    After upgrading from CTM R9.0 to CTM R9.1, the ONS 1530x PM process is shown incorrectly as running.

Conditions   This problem occurs when an ONS 1530x NE is connected before the migration. In the Domain Explorer > Administration > Service Uptime table, the ONS 1530x PM process is reported as running when there are no ONS 1530x NEs connected to the server.

Workaround   None.


CSCta15409

Symptom    A CTM dual-server installation forces the user to cancel installation if the wrong options are selected in the Main Options screen.

Conditions   This problem occurs if you select both options to install the CTM server and the database in the Main Options screen. After you click Next, an error message appears, but does not allow you to go back to the Main Options screen. You must click Cancel and exit the installation.

Workaround   None.


CSCta46657

Symptom    A warning message is displayed after migrating the database from CTM R8.5 when only MGX modules are installed on the server.

Conditions   This problem occurs when you migrate the database from:

CTM R8.5 to CTM R9.0 with MGX modules only

CTM R8.5 to CTM R9.1 with MGX modules only

Workaround   None.


CSCta98847

Symptom    The CTM_CONFIG_TABLE is not migrated correctly from CTM R9.0 to CTM R9.1 and might affect PM service on MGX devices.

Conditions   This problem occurs after upgrading from CTM R9.0 to CTM R9.1. The CTM_CONFIG_TABLE is missing the following data values:

SECTION: mgx88xx-pm

PROPERTY: pm-jvm-heap-init and jvm-heap-max

Workaround   None.


CSCtb55127

Symptom    Exceptions are displayed and logged when NE services start up.

Conditions   This problem occurs after upgrading from CTM R8.5.

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


CSCtb97851

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

Conditions   This problem occurs when you upgrade CTM from an earlier release and cancel the installation at the final Installation Summary screen. When you cancel the installation, the existing CTM installation is not removed; instead, it is renamed. When you try to start the CTM server, the ctms-start command fails.

Workaround   To restore the existing CTM installation, enter the following UNIX commands as the root user:

cd /opt
rm -r CiscoTransportManagerServer
rm CiscoTransportManagerServer9.1
ln -s CiscoTransportManagerServer-old-<time_stamp> CiscoTransportManagerServer
rm CiscoTransportManagerServer.oldCTM
 
   

CSCtc61863

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

Conditions   This problem occurs when installing CTM GateWay/CORBA in a local redundancy, HA configuration or in a dual-node cluster, geographical redundancy, HA configuration.

Workaround   At the Server IP Address screen, specify the virtual IP address for the server setup.


CSCtd00311

Symptom    After you upgrade to CTM R9.1 from an earlier release, debug modules are missing from the Control Panel > Logging Properties pane > Basic Service Logging tab.

Conditions   This problem occurs under the following conditions:

1. In the earlier release, open the Control Panel > Logging Properties pane.

2. In the Basic Service Logging tab, enable SM service logging.

3. Select some debug modules for NEs that are no longer supported in CTM R9.1; for example, ONS 1580x NEs.

4. After you upgrade to CTM R9.1, the list of available modules is empty in the Control Panel > Logging Properties Pane > Basic Service Logging tab. The list of selected modules still shows modules related to unsupported NEs.

Workaround   None.


CSCtd26217

Symptom    The default CTM server installation path is incorrect.

Conditions   The installation path should be /cisco/CiscoTransportManagerServer.

Workaround   Manually change the CTM installation path.


CSCtd50557

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

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

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, change the name of the directory where the CTM client is installed.


CSCtd60771

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

Conditions   This problem occurs when you run the ctmsetup.sh script and reinstall CTM GateWay/CORBA.

Workaround   None.


CSCtd94434

Symptom    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

Conditions   This problem occurs when the CTM server and database are installed on separate workstations. The store_procedure_in_cache.sh file is present on the CTM database workstation instead of on the CTM server workstation.

Workaround   Log into the CTM server workstation as the root user and enter the following commands:

cd /opt/CiscoTransportManager/bin
1- rcp 
<CTM_database_IP_address>:/opt/CiscoTransportManagerServer/bin/store_procedure_in_cache.sh 
./store_procedure_in_cache.sh
 
   
2- rcp 
<CTM_database_IP_address>:/opt/CiscoTransportManagerServer/bin/install_storeprocedure_inca
che.sh ./install_storeprocedure_incache.sh
 
   

where <CTM_database_IP_address> is the IP address of the CTM database workstation.


CSCtd99187

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

Conditions   This problem occurs when you add MGX modules to a CTM server that previously had only optical modules installed.

Workaround   Reinstall CTM. At the Select Modules to Install screen, choose All of the Above Modules to install optical and MGX modules.


CSCtd99333

Symptom    Cannot install CTM GateWay/CORBA. During the installation, the "Cisco Transport Manager CORBA GateWay" check box is missing from the Select Products to Install screen.

Conditions   This problem occurs during the initial installation of the CTM server, if you do not click the Done button in the last installer screen.

Workaround   Enter the following shell command:

/cdrom/ctm_91_sol_s1/Disk1/InstData/Solaris/VM/update_db_history_table.sh <network-size> 
<optical-modules-installed> <MGX-modules-installed>
 
   

where:

<network-size> is small, medium, large, or highend.

<optical-modules-installed> is true or false

<MGX-modules-installed> is true or false

For example, if you are installing CTM in a small network with optical and MGX modules installed, enter:

/cdrom/ctm_91_sol_s1/Disk1/InstData/Solaris/VM/update_db_history_table.sh small true true
 
   

After running the preceding shell command, relaunch the CTM GateWay/CORBA installation.


CSCte50207

Symptom    Cannot launch the CTM client if the installation directory name contains a blank space.

Conditions   This problem occurs if the directory where the CTM client is installed has a blank space in the name. For example, if the installation directory is C:\Program Files\CTM (with a space between Program and Files), you cannot launch the CTM client.

Workaround   Install the CTM client in a directory whose name does not contain blank spaces. If the CTM client has already been installed, edit one of the following .lax files in the CTM client directory, depending on the size of your server:

For a small server, edit ctm-small.lax

For a medium server, edit ctm-medium.lax

For a large server, edit ctm-large.lax

For a high-end server, edit ctm-highend.lax

In the .lax file, search for the -Dctm.xml.fileLocation= setting and add " at the beginning and end of the CTM client directory (for example, "C:\Documents and Settings\username\Desktop\CTM Client 91").


CSCtf13479

Symptom    While upgrading to CTM R9.1, the sched_for_ctm_stats.sql command fails with the following error:

SQL>     @./sched_for_ctm_stats.sql
DECLARE
*
ERROR at line 1:
ORA-27478: job "SYS.GATHER_STATS_CTM_JOB" is running 
ORA-06512: at "SYS.DBMS_ISCHED", line 2805 
ORA-06512: at "SYS.DBMS_SCHEDULER", line 1753 
ORA-06512: at line 36

Conditions   This problem occurs while upgrading from CTM R8.5 or CTM R9.0 to CTM R9.1.

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


CSCtf27279

Symptom    The CTM R9.1.0.350.3 patch remains stuck while installing the CTM client on Microsoft Windows.

Conditions   The CTM R9.1.0.350.3 patch installation fails when the patch folder is located on a network drive and not on the local hard disk drive.

Workaround   If you have not yet tried to install the patch, copy the patch folder to the local hard disk before running the client_patch.bat command. If you already tried to install the patch, you must uninstall the CTM client, reinstall it, and then apply the patch from the local hard disk.


CSCtf78039

Symptom    After upgrading from CTM R8.5 to CTM R9.1, the initCTM.ora file is not updated correctly.

Conditions   This problem occurs with all CTM server sizes.

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


CSCth87771

Symptom    Sudo software version 1.6.6 (bundled with CTM) has a potential security vulnerability or exposure (CVE-2010-1646).

Conditions   This problem occurs when Sudo is installed with CTM. For more information on CVE-2010-1646, see the CVE website at http://cve.mitre.org/.

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

CTM Client Caveats

This section contains the following information:

Alarm Management

Circuit and Link Management

Data Services

Domain Explorer

NE Explorer

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.


CSCtd21907

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

Conditions   This problem occurs under the following conditions:

1. Auto-acknowledge is enabled in the Control Panel.

2. An alarm is raised, cleared (automatically acknowledged by CTM), and raised again with the same NE time stamp.

Workaround   Manually acknowledge the alarm.


CSCtd75006

Symptom    Filtering Audit Log data does not work correctly.

Conditions   This problem occurs under the following conditions:

1. From the Domain Explorer window, choose Administration > Audit Log. View the data displayed in the table.

2. Choose File > Filter and specify the filter parameters.

3. Click OK. The table should be filtered with the parameters you specified.

4. Choose File > Filter and remove the filter parameters you specified in Step 2. View the data in the table. It does not match the data that was originally displayed in Step 1.

Workaround   None.

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.


CSCsz63857

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

Conditions   This problem occurs when STS circuits are created with multiple intermediate spans.

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


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.


CSCtc33113

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

Conditions   This problem rarely occurs, but has been seen on networks that contain NEs running different software versions.

Workaround   Do one of the following:

From the BLSR tab, create the BLSR ring on each NE that defines the BLSR termination.

Use CTC to create the BLSR ring.


CSCtc33144

Symptom    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

Conditions   This error occurs when the NE Explorer hangs after a BLSR ring is created. Although the BLSR ring is created successfully and appears in the BLSR table, it cannot be edited. If you try to edit the BLSR ring, an error message appears.

Workaround   Use CTC to edit the BLSR ring.


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


CSCtd18515

Symptom    Cannot create L2 topologies or add cards when the Graphical Enhanced option is selected.

Conditions   This problem occurs after the Graphical Enhanced option is selected from the Routing Preferences pane (from auto or manual provisioning) when creating L2 topologies or adding cards.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, choose the Graphical or Textual option from the Routing Preferences pane.


CSCtd26062

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

Conditions   This problem occurs under the following conditions:

1. You have one simple circuit with the following NEs: A, B, C, and D.

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

2. The link between B and C goes down, causing the circuit state to become Partial or Out of Service.

3. Reconfigure the circuit so that it becomes two separate circuits that are the identical size and direction as the original circuit.

A ------------B

C ------------D

4. After successful reconfiguration, the resulting circuits remain in Partial state, and the circuit terminations are incorrect. The correct behavior is for the circuit state to be In Service and have correct circuit terminations.

Workaround   Restart the NE services.


CSCtd36677

Symptom    It takes a long time for the Circuit table to open.

Conditions   This problem occurs when the network contains VCAT circuits.

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


CSCtd40139

Symptom    A timeout occurs when launching the Circuit table from the CTM Domain for 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 Superuser.

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

Workaround   Limit the query options or increase 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.


CSCtd77921

Symptom    Adding an SVLAN drop fails and may cause traffic loss.

Conditions   This problem occurs when adding a drop on SVLAN domains connected by Layer 2 patchcords on NNI client ports.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, you can manually add the SVLAN drop settings.


CSCtg19956

Symptom    Discovery time tracing is enabled by default. Instead, NE services should start up with discovery time tracing disabled.

Conditions   See Symptom.

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

User Management

CSCtg92011

Symptom    The minimum length of the CTM username should change from six to three characters.

Conditions   You can change the CTM username from the Domain Explorer:

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

2. In the CTM Users table, choose Edit > Create and follow the steps in the Create New User wizard.

The minimum length of the CTM username is six characters. CTM should accept a three-character username.

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

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


CSCth69497

Symptom    The NE service does not respond promptly to commands sent from CTM clients.

Conditions   This problem occurs when an NE is equipped with IOS cards and the SNMP destination is not configured correctly with the CTM server.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, restart the NE service and configure the SNMP destination correctly on the NE with the CTM server IP address.


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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.

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.


CSCtc11739

Symptom    In the SVLAN Database Management wizard > Select a Resource pane, duplicate shelves are shown 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. Duplicate shelves appear for some multishelf NEs.

Workaround   None.


CSCtc58957

Symptom    The Cut command does not work.

Conditions   This problem occurs when you cut and paste an NE from one group to another in the Domain Explorer tree.

Workaround   Manually delete the NE from its original group.


CSCtd49122

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

Conditions   See Symptom.

Workaround   Do one of the following:

Close and reopen the CTM client.

Refresh data from the database.


CSCtd75008

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

Conditions   This problem occurs if you select a group of NEs with the same profile in the Domain Explorer and use the SVLAN Profile Management wizard to delete one or more profiles. The only SVLAN profile deleted is from the first NE that was selected in the Select a Resource pane.

Workaround   Delete SVLAN profiles, one at a time, from each NE.


CSCtj90800

Symptom    A CTC-based NE never completes discovery.

Conditions   This problem occurs when one of the cards on the NE has a product ID longer than 20 characters.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.


CSCsq65717

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

Conditions   This problem occurs when you change either the ELWBATVG or EHWBATVG value once on the Power Monitor tab. The value is set successfully and is reflected in CTC. Any subsequent changes to these values are not reflected in CTM.

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.


CSCsw61380

Symptom    It is possible to create a Routing Information Protocol (RIP) address without first activating RIP.

Conditions   This problem occurs under the following conditions:

1. Launch the NE Explorer for any CTC-based NE.

2. In the Network tab > RIP subtab, check the RIP Active check box.

3. Click Create and create a default entry.

4. Click Apply. The RIP Active check box becomes disabled, and the RIP entry is created.

5. Select a row in the RIP Address Summary table. The Create and Delete buttons are enabled.

6. Create another RIP address. The new address is created successfully and appears in CTC. However, the RIP Active check box remains disabled.

Workaround   None.


CSCta52764

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

Conditions   This problem occurs under the following conditions:

1. Create several circuits passing through a dense wavelength division multiplexing (DWDM) ring.

2. From the NE Explorer, select a corresponding amplifier card and click the Optical Line tab.

3. Delete the corresponding circuit or edit it and put it in Out of Service state.

4. Reopen the Optical Line tab. The Active Channels column is not updated.

Workaround   Use CTC to view the correct number of active channels, or close the client and reopen it.


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.


CSCtc87376

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

Conditions   This problem occurs when creating a bidirectional optical channel network connection (OCHNC) on an SMR1 or SMR2 card, as follows:

1. From the NE Explorer, select an ONS15454 SONET/SDH SMR1 or SMR2 card.

2. Click the Optical Channel > Parameters tab.

3. Select an existing circuit wavelength and click Retrieve. A table displays a row where the Force Channel Status and Force Channel fields are blank instead of displaying N/A.

Workaround   None.


CSCtd46787

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

Conditions   See Symptom.

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


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.


CSCte63901

Symptom    Sometimes the card name is displayed as "null" from the DWDM > All Facilities tab.

Conditions   Unknown.

Workaround   Close and reopen the CTM client.


CSCtg38402

Symptom    ROADM power monitoring does not work correctly in the CTM R9.1.0.350.3 patch.

Conditions   This problem occurs when an ONS 15454 SDH R9.1 NE is configured as follows:

Side A: Shelf 1, slot 3, 40-WSS-C

Side B: Shelf 1, slot 14, 40-WSS-C

Side C: Shelf 3, slot 14, 32-WSS

CTM does not show side C. Furthermore, CTM shows side A as shelf 3, slot 14, 32-WSS.

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


CSCth05616

Symptom    The NE Explorer does not display 32WSS optical channel parameters. The Optical Channel tab is blank for 32WSS cards.

Conditions   This problem occurs when you create or delete an OCH circuit that is routed through the selected 32WSS card, and then open the Optical Channel tab for that card. When the tab opens, it is blank.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, refresh data from the server.


CSCti33054

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

Conditions   See Symptom.

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


CSCti83745

Symptom    The ONS 15454 DWDM tab > ROADM Power Monitoring subtab shows an hourglass icon continuously.

Conditions   This problem occurs when you launch the node-level NE Explorer, click the DWDM tab > ROADM Power Monitoring subtab, and click the Update button. An hourglass icon is displayed continuously, even though the update operation succeeds. This problem applies to an ONS 15454 ROADM NE that is configured with an OCHCC circuit.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, click the Cancel button in the NE Explorer window.

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.


CSCtd31432

Symptom    After a zoom, NE locations are not saved in the Network Map.

Conditions   This problem occurs under the following conditions:

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

2. In the preview map pane, zoom in on the network and move some NEs.

3. Click Save.

4. Click Refresh. All nodes disappear from the Network Map.

Workaround   Resize the square in the preview map pane (located in the top left corner) and refresh the Network Map.

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.


CSCtd34174

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

Conditions   This problem occurs if you query PM data for all ports on the card.

Workaround   Query real-time PM data for single ports that have valid power values.


CSCtd55103

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

Conditions   This problem occurs on ONS 15600 SDH NEs when the PM category is set to Multiplex Section and the PM interval is set to Real Time.

Workaround   Use the PM Query by NE Model wizard instead of the PM Query by Category wizard.


CSCtf52162 (Related caveat ID: CSCtb41766)

Symptom    An incorrect time is displayed in the Time Stamp field of the real-time PM table. When the Time Stamp field should display CEST, it incorrectly displays GMT. The correct server time is displayed at the bottom right of the real-time PM table.

Conditions   This problem occurs when real-time PM data is collected.

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


CSCtg62909

Symptom    Real-time PM graphs do not work correctly if the Time Display option is set to 24 Hour.

Conditions   This problem occurs when in the Domain Explorer window you choose Edit > User Preferences, click the Time Preferences tab, and set the Time Display option to 24 Hour. If you then open a real-time PM table on any node or card and plot the results, the graph does not work.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 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.

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:

1. Go to the <CTM_client_home>/ directory, where <CTM_client_home> is your client location.

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.

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.

4. Change the filename gcoutput to a new name.

5. Save and close the file.

6. Start a new client session as usual.

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

1. Go to the <CTM_client_home>/ directory, where <CTM_client_home> is your client location.

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

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.

4. Change the filename gcoutput to a new name.

5. Save and close the file.

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.


CSCtb49760

Symptom    The Find function for circuits does not work.

Conditions   This problem occurs with NEs running software version 9.1.

Workaround   None.


CSCtc12112

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

Conditions   This problem occurs when you specify 24-hour time format in the User Preferences dialog box. The Service Monitor and Service Uptime tables still display time in 12-hour format.

Workaround   Place your cursor over the time to see the tooltip. The tooltip displays the time in 24-hour format.


CSCtc30664

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

Conditions   This problem occurs when a custom profile is created and is not given access to any CTM features. When a user is assigned this profile, some CTM features are still enabled.

Workaround   None.


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.


CSCtd33920

Symptom    The ROADM Power Monitoring graph shows only one power type when there should be more.

Conditions   This problem occurs if the Add Power value is less than the values for the other power types.

Workaround   Use CTC to view the graph.


CSCtd63215

Symptom    CTM client resynchronization is slow and an exception appears.

Conditions   This problem occurs when you enable debugging on the CTM client and then choose File > Refresh Data. After resynchronization is complete, the following exception is displayed:

java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Unknown Source)
at com.cisco.stardm.framework.nesp.NEServiceProvider.eventOccured 
(NEServiceProvider.java:5367)
at com.cisco.stardm.event.VWEventNotifier.notifyListeners(VWEventNotifier.java:457)
at com.cisco.stardm.event.VWEventDispatcher.run(VWEventDispatcher.java:80)

Workaround   None.


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.


CSCte85662

Symptom    The CTM R9.1 client does not start in Windows. The load bar reaches 100% and the application hangs.

Conditions   On a localized version of a Windows OS, when you run the CTM client in Debug mode, the output displays the following error:

Exception in thread "Thread-4" java.lang.IllegalArgumentException: Illegal patt
 rn character 'j'
         at java.text.SimpleDateFormat.compile(Unknown Source)
         at java.text.SimpleDateFormat.initialize(Unknown Source)
         at java.text.SimpleDateFormat.<init>(Unknown Source)
         at java.text.SimpleDateFormat.<init>(Unknown Source)
         at com.cisco.stardm.framework.uicomponents.ImStatusBar.showServerTime(I
 StatusBar.java:741)
         at com.cisco.stardm.framework.uicomponents.ImStatusBar.update(ImStatusB
 r.java:718)
         at java.util.Observable.notifyObservers(Unknown Source)
         at java.util.Observable.notifyObservers(Unknown Source)
         at com.cisco.stardm.framework.uicomponents.ServerTimeReader.updateTime(
 mStatusBar.java:895)

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


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.

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:

1. Restart the NE service.

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

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

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

5. Mark the NE as In Service.


CSCtg30554

Symptom    The CTM client does not start when the Windows Control Panel > Regional and Language Options are set to Japanese.

Conditions   See Symptom.

Workaround   Do the following:

1. In the CTM client installation directory, locate the file named ctm-<network-size>.lax, where <network-size> is small, medium, large, or highend.

2. Open the file with any text editor.

3. Find the line that begins with lax.nl.java.option.additional.

4. At the end of this line, add one blank space and then the following text:

-Dfile.encoding=UTF-8
 
   

5. Save the file; then, launch the CTM client.


CSCtg56522

Symptom    When you use the Add NE wizard to add a new ONS 15454 NE, the CTM server does not manage that NE, and the NE is not shown in the Domain Explorer.

Conditions   This problem occurs when the total number of NEs in the network partition reaches or exceeds the network partition limit. The NEs in the network partition can be of different types, such as a mix of ONS 15454 and ONS 15305 NEs.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, create a new network partition and move all NEs of the same type into the same network partition.


CSCtg80725

Symptom    After a successful login, the CTM client remains stuck at the Welcome screen. The shell where the CTM client was started with the ctmcdebug-start command reports the following exception:

Exception in thread "main" java.lang.NoSuchMethodError: 
org.apache.log.output.io.rotate.RotatingFileTarget.<init>(ZLorg/apache/log/format/Formatter;Lorg/apach
e/log/output/io/rotate/RotateStrategy;Lorg/apache/log/output/io/rotate/FileStrategy;)V
        at org.jacorb.util.LogKitLoggerFactory.setDefaultLogFile(LogKitLoggerFactory.java:207)
        at org.jacorb.util.Environment.initLogging(Environment.java:597)
        at org.jacorb.util.Environment.addProperties(Environment.java:397)
        at org.jacorb.orb.ORB.set_parameters(ORB.java:1602)
        at org.omg.CORBA.ORB.init(Unknown Source)
        at com.cisco.stardm.framework.utils.GlobalUtils.initORB(GlobalUtils.java:194)
        at com.cisco.stardm.framework.CTMClient.initConfigManager(CTMClient.java:1395)
        at com.cisco.stardm.framework.CTMClient.<init>(CTMClient.java:676)
        at com.cisco.stardm.framework.CTMClient.main(CTMClient.java:154)

Conditions   See Symptom.

Workaround   As the user running the CTM client, go to the home directory (which is / for the root user). In the home directory, locate the jacorb.properties file and rename it to jacorb.properties.old.


CSCth85433

Symptom    Cannot create or modify a CTM user.

Conditions   This problem occurs when:

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.


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.


CSCti59552

Symptom    CTM reloads the same .gif, which causes high memory usage in the CTM client and slow performance.

Conditions   See Symptom.

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


CSCti70491

Symptom    The CAP and backplane equipment states are always reported as "Not present" for ONS 15600 NEs.

Conditions   In the Equipment Inventory table for ONS 15600 NEs, the Equipment State field for the CAP and backplane shows "Not present."

Workaround   None.

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.1 patch. See Installing the Latest CTM R9.1 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.


CSCta08807

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

Conditions   This problem occurs if you run the import_full_db.sh script while the CTM server is running. The import_full_db.sh script does not perform a check on the CTM application, so you must run the script while the CTM server is stopped. This limitation is described in the CTM user guide.

Workaround   None.


CSCtd61189

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

Conditions   This problem occurs when the CTM server is stopped and restarted manually with the ctms-stop and ctms-start commands. Following this procedure, the VCS Apache agent incorrectly detects the Apache web server status as offline.

Workaround   Do the following:

1. Enter the following command to manually start the CTM server with the noapache option:

ctms-start -noapache
 
   

2. Enter the following command to start the CTM_APACHE web server:

hares -online CTM_APACHE -sys <sysname>
 
   

CSCtd89038

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

Conditions   This problem occurs when you run the /opt/CiscoTransportManagerServer/bin/import_full_db.sh script. In the output, the following error message is displayed:

SQL> BEGIN DBMS_JOB.SUBMIT(:jobno,'Login_Disable;',TRUNC(SYSDATE)+1+6/24, 
'TRUNC(SYSDATE+1)+6/24'); END;
 
   
*
ERROR at line 1:
ORA-06550: line 1, column 93:
PLS-00201: identifier 'LOGIN_DISABLE' must be declared
ORA-06550: line 1, column 93:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_JOB", line 79
ORA-06512: at "SYS.DBMS_JOB", line 136
ORA-06512: at line 1
 
   

This problem occurs because an SQL procedure in the import_full_db.sh script is executed multiple times, which generates errors when the script runs.

Despite the errors, the import procedure completes successfully. You can restart the CTM server after the script completes.

Workaround   None.


CSCtf00243

Symptom    CTM does not validate GateWay/CORBA port configuration changes and the GateWay/CORBA Service is shown incorrectly as running when it has stopped.

Conditions   This problem occurs when an incorrect port range is configured for GateWay/CORBA ports. For example, if the minimum port range value is set at 4000 and the maximum port range value is set at 3000, CTM does not display an error message. CTM GateWay/CORBA restarts, but in some cases, it stops and the GUI does not refresh.

Workaround   Restart the CTM server.


CSCtf04028

Symptom    In the CTM client Control Panel, the GateWay/CORBA Service is shown incorrectly as running when it has stopped.

Conditions   This problem occurs under the following conditions:

1. Enable the IMR service.

2. While CTM GateWay/CORBA is running, change some of the gateway port values (such as the notification port range, ping port range, or notification port).

3. Stop and restart the GateWay/CORBA Service. CTM GateWay/CORBA restarts, but in some cases, it stops and the GUI does not refresh.

Workaround   Disable the IMR service.


CSCtg33017

Symptom    After a reboot of the Solaris server on which the CTM server is installed, the CTM server does not start up automatically.

Conditions   This problem occurs when you reboot the Solaris server on which the CTM server is installed.

Workaround   Use the ctms-start command to start the CTM service manually.


CSCtg89916

Symptom    Errors and stack traces are included erroneously in the log file in the /tmp directory.

Conditions   The NE services log file in the /tmp directory should not contain any errors; instead, errors should be logged in the log file under ./log. Log files in the /tmp directory do not wrap, and therefore must not contain any errors.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, clear the contents of the log file manually. Do not delete the file itself.


CSCth29044

Symptom    Archived redo logs are generated incorrectly in the /oracle partition instead of in the /db05 partition. If the /oracle partition fills up, Oracle hangs and CTM crashes.

Conditions   This problem applies to the CTM R9.1 server when the CTM R9.1.0.365.2 patch is installed and ARCHIVELOG mode is enabled. If ARCHIVELOG mode is disabled, this problem does not occur.

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

Alternately, you can do the following:

1. Enter the following command to stop the CTM server:

ctms-stop
 
   

2. Edit the /oracle/admin/CTM/pfile/initCTM.ora file to remove the comments (#) from the following lines:

log_archive_dest               = /db05/CTM/CTM
log_archive_format             = %t_%s_%r.arc
 
   

In this example, the Oracle SID is CTM. Your db05 folder might have a different name if you are using a customized SID.

3. Enter the following commands to shut down and restart Oracle:

su - oracle
sqlplus /nolog
conn /as sysdba
shutdown immediate
startup
exit
 

4. Move any *.dbf files from /oracle/product/10.2.0/dbs to /ctm_backup.

5. Enter the following command to restart CTM:

ctms-start
 
   

If you cannot stop CTM immediately (in other words, if you cannot complete Step 1), you can temporarily set the archive_log_dest to /db05 without restarting Oracle and CTM. To do this, enter the following commands:

su - oracle
sqlplus /nolog
conn /as sysdba
alter system set log_archive_dest='/db05/CTM/CTM';
exit
 

It is recommended that you complete Step 1 to Step 5 at the earliest maintenance window. If you temporarily set the archive_log_dest to /db05, archived redo logs are not moved automatically from /db05 to /ctm_backup.


CSCth21611

Symptom    Loss of communication alarm storms occur periodically on CTC-based network services.

Conditions   This problem occurs when the CTM server manages more than 100 fully equipped NEs.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, enable the Parallel Garbage Collection strategy by adding the -XX:+UseParallelOldGC property to the jnet.sh file; then, restart the CTC-based network services.


CSCth92179

Symptom    CTM loses NE connectivity and the garbage collector usage is high.

Conditions   This problem occurs when the CTM server manages more than 100 fully equipped NEs on a small network configuration.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, enable the Parallel Garbage Collection strategy by adding the -XX:+UseParallelOldGC property to the jnet.sh file; then, restart the CTC-based network services.


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.


CSCti13296

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

Conditions   This problem occurs when the logging subsystem experiences a problem while the PM service is running.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, remove the PM service log file from the /tmp directory and reboot the workstation.


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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack.


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.


CSCtk17643

Symptom    If you try to add an NE that was previously deleted from CTM, an error message indicates that the IP address already exists.

Conditions   This problem occurs when a CTM user deletes an NE from CTM. Although the NE is no longer visible in the Domain Explorer, it can still be found in the Subnetwork Explorer.

Workaround   Run the prune_ne.sh script in the /opt/CiscoTransportManagerServer/bin/ directory. If the script fails to prune the NE, contact the Cisco Technical Assistance Center (TAC).


CSCtk62107 (Related caveat ID: CSCtn86703)

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.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, do the following:

1. Shut down Oracle after the restore or import has completed.

2. Enter following command:

tar xvf /ctm_backup/oracle_dir.tar 

3. After the file has been extracted, restart Oracle.


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.


CSCtc79880

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

Conditions   This problem occurs when CTC is launched from an NE that belongs to a network partition containing a large number of NEs.

Workaround   None.

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.


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.


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.


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   Use the CTM GUI to configure alarm suppression.


CSCtc22763

Symptom    The getAllSupportedPTPs does not retrieve some CTP terminations.

Conditions   This problem occurs when the OSS retrieves CTP terminations subtended by a PTP.

Workaround   None.


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.


CSCtc28066

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

Conditions   This problem occurs on OTU2_XP cards with a layer rate of 106.

Workaround   Use the CTM GUI to retrieve PM data.


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.


CSCtc40704

Symptom    The getCTMHistoryPMData API reports the following unnecessary values: PMP_RXRUNTS, PMP_RXTOTALERRORS, and PMP_PORTDROPCOUNTS.

Conditions   This problem occurs when using CTM GateWay/CORBA for ONS 15454 CE-100T-8 cards with PM collection enabled. After starting the getCTMHistoryPMData API on the card, the following values are displayed unnecessarily: PMP_RXRUNTS, PMP_RXTOTALERRORS, and PMP_PORTDROPCOUNTS.

Workaround   Use the CTM GUI to retrieve PM data.


CSCtc65216

Symptom    CTM GateWay/CORBA does not start.

Conditions   This problem occurs when the NameService process shuts down unexpectedly.

Workaround   Restart the NameService process; then, start CTM GateWay/CORBA.


CSCtd18457

Symptom    Alarm suppression cannot be set at the node level.

Conditions   This problem occurs when using the CTM GateWay/CORBA client to set alarm suppression at the node level.

Workaround   From the CTM GUI, choose NE Explorer > Alarm > Alarm Behavior and check Suppress Alarms.


CSCtd40324

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

Conditions   This problem occurs when the getAllPTPs API is started on an MXP card whose client ports can be set only with an OC-48 payload type. Trunk ports work at a rate of 10 Gb/s, but the API reports the trunk port when layer rate OC-48 is selected.

Workaround   None.


CSCtd44168

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

Conditions   This problem occurs under the following conditions:

1. Use the CreateServerTrail API to create a server trail link between two NEs. Specify a link count number.

2. After the server trail link is created, use GetTopologicalLink or GetAllTopologicalLinks to retrieve the link. The layer rate is reported, but the link count is missing.

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 starting the getCTMHistoryPMData API on the card, the following values are displayed unnecessarily: PMP_RXRUNTS and PMP_RXTOTALERRORS.

Workaround   None.


CSCtd78528

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

Conditions   This problem occurs when you double-click Start Service to start CTM GateWay/CORBA.

Workaround   From the CLI, enter the gwcorba-stop.sh command to stop the service. Then, restart the service in the Control Panel.


CSCtd81499

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

Conditions   See Symptom.

Workaround   None.


CSCtg78740

Symptom    The CTM GateWay/CORBA client does not update when equipment is provisioned or deleted.

Conditions   See Symptom.

Workaround   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, use the getAllEquipment API, which reports the correct data when equipment is provisioned or deleted.


CSCtf08332

Symptom    The CTM GateWay/CORBA GetRollsToPTPs API does not return a list of available PTPs.

Conditions   This problem occurs when using the CTM GateWay/CORBA GetRollsToPTPs API, which requests available PTPs moving from one circuit to another.

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   Do the following before starting CTM or the MGX VG NE service:

1. Enter the following command:

cd opt/svplus/config
 
   

2. Open the NMServer.conf file using a text editor.

3. Search for "PERIODIC_RESYNC_INTERVAL."

4. Change the value from 8 to 0. It should show PERIODIC_RESYNC_INTERVAL 0.

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. Alternately, 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   Install the latest CTM R9.1 patch. See Installing the Latest CTM R9.1 Patch or Service Pack. Alternately, 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.


CSCtd99728

Symptom    The Cisco Edge Craft GUI does not appear correctly in the Solaris Java Desktop System. For example, the left panel (Management Tree) occupies the entire main window. The right panel (Attributes > Viewing ONS 15305) is not visible. The information in the Help > About panel is not visible because it is displayed in white font on a white background.

Conditions   This problem occurs when you use the CTM client and Cisco Edge Craft with the Solaris Java Desktop System.

Workaround   Use the CTM client and Cisco Edge Craft with Windows, or with the Solaris Common Desktop Environment.


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.

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   Perform the GetEquipment operation again after some time has passed.


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.


CSCsz67234

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

Conditions   This problem occurs on ADM-10G cards. The provisioning operations bounce from being very slow to normal.

Workaround   None.


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


CSCtd60783

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

Conditions   This problem occurs on OTU_XP cards configured as LAN to WAN on ONS 15454 SDH NEs.

Workaround   None.

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   Include or exclude nodes during manual routing. For WXC nodes only, 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.

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.

Related Documentation


Note You can access the most current CTM R9.1 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.1—This document.

Cisco Transport Manager Release 9.1 Installation Guide—Explains how to install CTM and how to upgrade from previous releases.

Cisco Transport Manager Release 9.1 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.1 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.1 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.1 High Availability Installation Guide—Explains how to install CTM in an HA environment.


Note To obtain the Cisco Transport Manager Release 9.1 High Availability Installation Guide, contact your Cisco account representative.


Cisco Transport Manager Release 9.1 ML Provisioning Methodology—Describes the methodology that CTM uses to provision ML-series cards.

Cisco Transport Manager Release 9.1 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.