Guest

Cisco Transport Manager

Release Notes for Cisco Transport Manager 9.0

  • Viewing Options

  • PDF (1.2 MB)
  • Feedback
Release Notes for Cisco Transport Manager Release 9.0

Table Of Contents

Release Notes for Cisco Transport Manager Release 9.0

Contents

Introduction

New Features and Functionality

Changes to the Release Notes

NE Software Releases Added

Sections and Caveats Added

Sections Removed

CTM-Supported NE Software Releases

Adding the ONS 15305 R2.0.2 to the Supported NE Table

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

Installing the CTM-Supported Oracle Patch 7291739

CTM-Supported JRE and Apache Versions

Resolved Caveats

Installing the Latest CTM R9.0 Patch or Service Pack

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/TL1 Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15302 and 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 ONS 15800, Cisco ONS 15801, and Cisco ONS 15808

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Transport Manager Release 9.0


September 19, 2011

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


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


Contents

These release notes contain the following sections:

Introduction

New Features and Functionality

Changes to the Release Notes

CTM-Supported NE Software Releases

Third-Party Patches and Security Notices

CTM-Supported JRE and Apache Versions

Resolved Caveats

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

Table 1-1 New Features in CTM R9.0 

New Feature
Description
Database Enhancements

Database migration from:

CTM R8.0.x to R9.0

CTM R8.5.x to R9.0

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

Server/Client Platform Enhancements

Support for up to 4000 NEs in a high-end configuration

In CTM R8.5, the CTM server could support up to 3000 optical NEs in a high-end configuration. In CTM R9.0, the server supports up to 4000 optical NEs.

External authentication with RADIUS support

Enables the CTM server to use the Pluggable Authentication Module (PAM) Solaris library for authentication against RADIUS access servers. In the Security Properties pane of the Control Panel, you can enable external authentication and choose PAM RADIUS as the authentication tool.

IPv6 support between the CTM server and ONS 15000 devices

CTM provides IPv6 support for the following NE releases:

ONS 15310 CL R9.0

ONS 15310 MA SDH R9.0

ONS 15310 MA SONET R9.0

ONS 15454 SDH R9.0

ONS 15454 SONET R9.0

ONS 15600 SDH R9.0

ONS 15600 SONET R9.0

Note CTM R9.0 maintains support for IPv4 addresses.

Configuring SNMPv3 on CTC-based NEs

CTM discovers, updates, and provisions SNMPv3 NE tables on CTC-based NEs. SNMPv3 offers the following benefits:

Provides a standards-based approach to secure monitoring.

Ensures secure transactions through authentication, transport layer encryption, and hashed message payloads.

Ensures that the content of each received message is protected from disclosure and is sent from a valid origin.

Protects message payloads from modification of information, masquerade security threats, and "man-in-the-middle" attacks.

Simplifies management by allowing the application of complex, granular access control parameters to each request.

Requires no changes to the standard SNMP configuration.

Enables organizations to remain compliant with federal security standards for cryptography-related applications.

You can configure SNMPv3 on the following CTC-based tables:

SNMPv3 NE Users table

SNMPv3 NE MIB Views table

SNMPv3 NE Groups table

SNMPv3 NE Trap Destinations table

SNMPv3 NE Notification Filters table

If the CTC-based NE is configured as a proxy, you can configure SNMPv3 on these additional tables:

SNMPv3 NE Proxy Forwarder table

SNMPv3 NE Proxy Trap Forwarder table

SNMPv3 NE Remote Users table

Qualification of new T5120 and T5220 Sun servers

The CTM server runs on Sun T5120 and T5220 servers.

Report CTM server availability

You can view current and historical information about NE and performance monitoring (PM) services.

The Service Availability table allows you to monitor the status of currently active services.

The Service Uptime Log allows you to view historical uptime data for services that were previously activated, but are currently deactivated.

Enable or disable CTM server logging

In the Logging Properties pane of the Control Panel, you can enable or disable CTM server logging without affecting the logging operation on other services.

Memory restore displayed in chronological order

In the Memory Restore dialog box > Source area, you can choose Local to retrieve the backup file from the CTM client workstation, or Server to retrieve the backup file from the CTM server workstation.

If you choose the Server radio button, the backup files are listed in chronological order, with the most recent backup file displayed at the top of the list.

The backup file uses the following naming convention:

<NE_model>-<date><time>-backup.cfg

where:

<date> has the format YYYYMMDD (that is, 20090306 is March 6, 2009)

<time> has the format hhmmss (that is, 144911 is 2:49:11 p.m.)

For example, a valid backup filename is Cisco_ONS_15454-20090201144911-backup.cfg.

Designated SOCKS servers

You can enable or disable designated SOCKS servers on CTC-based NEs.

Cleared alarms in debug log

When a database exception occurs, cleared alarms are dumped into the debug log.

Note This feature is available only after installing the CTM R9.0.0.620.5 or later patch.

Optical Enhancements

Support for CTC-based NE Release 9.0

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

ONS 15310 CL Release 9.0

ONS 15310 MA SDH Release 9.0

ONS 15310 MA SONET Release 9.0

ONS 15454 MSTP (ANSI/ETSI) Release 9.0

ONS 15454 MSPP (SONET/SDH) Release 9.0

ONS 15600 SONET Release 9.0

ONS 15600 SDH Release 9.0

ONS 15454 multishelf NEs support up to 12 shelves and racks

In previous CTM releases, a multishelf NE could support up to 8 shelves and racks. In CTM R9.0, a multishelf NE supports up to 12 shelves and racks.

Support for new optical cards

CTM manages the following new cards on optical devices:

4-port, XFP-based, 10-G transponder (10GR)—ONS 15454 MSTP

4x10-GE Xponder Enhanced—ONS 15454 MSTP

20-GE Xponder Enhanced—ONS 15454 MSTP

CE-MR-6—ONS 15310 MA SONET, ONS 15310 MA SDH

E1_21_E3_DS3_3 and E1_63_E3_DS3_3—ONS 15310 MA SDH

Optical Raman Pump Unit C-Band (OPT-RAMP-C)—ONS 15454 MSTP

OTU2-XP—ONS 15454 MSTP

Protection Switch Module (PSM)—ONS 15454 MSTP

Ability to apply protection to ports in a splitter protection group

In the Circuit Trace window, a new right-click menu option allows you to apply protection to the ports in a splitter protection group.

This feature applies to OCHCC, OCHTRAIL, and OCHNC circuits that use optical protection.

Ability to download software and back up or restore the database to an ENE with firewall enabled

You can configure database backup and restore, and software download to an ENE when proxy/firewall is enabled. CTM lets you provision up to 12 legal FTP hosts that will expire after a configurable amount of time. You can use the Bulk FTP Hosts Configuration feature to create an FTP host in a GNE/ENE firewall environment for multiple NEs simultaneously.

Support for new DS1 line length values on DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards on ONS 15310 MA SONET R9.0.1 and later NEs

CTM supports the new DS1 line length values on DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards:

0 db LBO

-7.5 db LBO

-15 db LBO

-22.5 db LBO

Note These values can be seen on ONS 15310 MA SONET R9.0 NEs, but cannot be set. These new DS1 line length values can be set only on ONS 15310 MA SONET R9.0.1 and later NEs.

Note Support for new DS1 length values is available only after installing the CTM R9.0.0.620.5 or later patch.

Layer 1 Enhancements

Tracing of incomplete circuits

CTM allows you to trace circuits in Partial state. A circuit trace report is generated for partial circuits that have the source and destination node information.

Zoom levels are available in the Circuit Trace window

CTM allows you to zoom in or zoom out on the Circuit Trace window.

High-level circuit trace

In the High-Level Circuit Trace window, a graphic map uses high-level span information such as NEs and links to display the circuit trace.

Support for grouping during circuit provisioning

The new Graphical Enhanced radio button in the Routing Preferences pane of the Circuit wizard provides top-level and detailed views of the circuit map.

The top-level view displays the subnetworks or groups involved in the CTM system. You can expand the top-level views by right-clicking a subnetwork or group icon and choosing View from the shortcut menu. A detailed view of the circuit map appears and displays the nodes and links that belong to the specific subnetwork or group. From the detailed view, you can select the nodes and links that you need for provisioning the circuit. You can also collapse a detailed view by clicking the Top View button. The circuit map reverts to the top-level view.

Ability to expand or collapse link objects during manual circuit provisioning

While provisioning manual circuit routing in the Create Circuit wizard, you can right-click a link or link bundle in the map view and choose Expand or Collapse from the shortcut menu. If you choose Collapse, the links are hidden and the link bundle is displayed. If you choose Expand, the link bundle is hidden and the links are displayed.

The color of the link bundle represents the link selection status, which has the following order of priority (from highest to lowest):

Magenta—The link bundle contains at least one excluded link.

Blue—The link bundle contains at least one selected link.

White—The link bundle contains at least one selecting link.

Green—All links in the link bundle are selectable.

Red—The link bundle contains at least one unselectable link.

The link bundle tooltip reports the number of links in the bundle and the name of each link. The background color of each link name in the tooltip represents the link selection status.

Support for open-ended VCAT circuits

CTM R9.0 supports open-ended virtual concatenation (VCAT) circuits that originate on Ethernet or ML-series cards. The destination can be OC-n or STM-n cards. You can route open-ended VCAT circuits to or from any of the cards or ports where VCAT circuits originate or terminate. Compared to a standard VCAT circuit, an open-ended VCAT circuit has only one virtual concatenation group (VCG).

Support for service provider VLANs (SVLANs)

A new Create SVLAN wizard allows you to configure SVLANs on GE_XP or 10GE_XP cards on ONS 15454 SONET and ONS 15454 SDH R9.0 NEs.

Data Enhancements

ML card bulk configuration download

Downloads the base card configuration (BCC) barebone file to multiple ML-series cards on the following NEs:

ONS 15310 CL SONET

ONS 15310 MA SDH

ONS 15310 MA SONET

ONS 15454 SDH

ONS 15454 SONET

IEEE 802.3ad link aggregation

CTM R9.0 supports IEEE 802.3ad link aggregation, which allows one or more links to be aggregated into a single link aggregation group. Link aggregation provides link protection, increased bandwidth, increased availability, and load balancing across multiple links. The standard also defines the Link Aggregation Control Protocol (LACP), which is used to configure and control the link aggregation sublayer. LACP provides the ability to continuously monitor the configuration and take appropriate reconfiguration actions.

CTM allows users with the appropriate permissions to select the link aggregation methods. You can see all of the interfaces that belong to a link aggregation group, plus the aggregation method provisioned.

To support link aggregation, CTM supports Ethernet channel configuration on a per-card basis.

VLAN mirroring on standby cards

VLAN services that are provisioned on the working/active ML cards are automatically provisioned on the protect/standby ML cards.

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 Release 5.3.10, 5.3.20, 5.4.10, 5.4.30, 5.5.00

Voice-Enabled Cisco MGX 8850 Multiservice Switch Release 5.3.10, 5.3.20, 5.4.10, 5.4.30, 5.5.00

Voice-Enabled Cisco MGX 8830 Multiservice Switch Release 5.3.10, 5.3.20, 5.4.10, 5.4.30, 5.5.00

VXSM Release 5.3.30, 5.4.20, 5.5.00

Support for media gateway overload notification on VXSM cards

CTM reports how many calls per second are running in the system. At the VXSM card level, the Resource Control tab contains a Gateway Resource Utilization category. When you select this category, all of the supported resources are selected in the configuration table. The Real-Time Statistics table displays the following statistics:

Maximum utilization

Minimum utilization

Average utilization

Select a specific resource and the real-time statistics to retrieve the current values for that resource.

Reporting of card uptime

In the VXSM Card tab > Front Card Configuration category of the Configuration Center, CTM reports uptime for the following MGX cards:

AXSMXG

MPSM-T3E3-155

MPSM-16-T1E1

PXM1E

PXM45

RPM-XF

VXSM

VXSM circuit description

In the Configuration Center, you can configure the circuit identifier on the following VXSM cards:

VXSM T1E1, DS1 line circuit identifier

VXSM T3E3, DS3 line circuit identifier

VXSM OC3, SONET line circuit identifier

VXSM OC3, SONET path circuit identifier

Support for super G3 fax spoofing on VSXM cards

Enables or disables fax negotiation spoofs that automatically force Super Group 3 (SG3) fax machines to send faxes over T.38 Group 3 (G3) modulations. You can enable or disable this feature on VXSM cards in the Configuration Center (VXSM Card tab > VBD tab > Fax Relay Profile).

Number of active and emergency calls in progress

In the Diagnostic Center, the Resource Control tab > Call Statistics subtab lists the number of active and emergency calls in an H.248 setup. When the VXSM card is configured for Media Gateway Control Protocol (MGCP) or Trunking Gateway Control Protocol (TGCP), only active calls are listed in the Real Time Statistics table.

Out-of-service and in-service trunks at the E1 level

You can configure the service state of a path or line to down, even if a time-division multiplexing (TDM) configuration exists for that particular path or line. In this way you can prevent the VXSM card from detecting and generating statistical alarms on the TDM configuration.

Diagnostic Center display for DSPCODECPOOLS

In the Diagnostic Center, the Resource Control tab > Codec Pool Stats subtab lists the available coder-decoder (codec) pools with real-time statistics on available and utilized DSP channels.

MGX SFTP support

CTM supports Secure File Transfer Protocol (SFTP) to upload and download configuration and statistics files from MGX devices. With SFTP, all data is encrypted and is safe from interception. The encryption is unique to the SFTP session, making data decryption extremely unlikely. User credentials determine SFTP access.

Support for Daylight Saving Time on MGX devices

You can use the CTM GUI to enable or disable Daylight Saving Time (DST) and configure DST settings on MGX devices. You can enable or disable this feature by selecting a node in the Domain Explorer tree and choosing Configuration > MGX Voice Gateway > Configuration Center > Daylight Savings tab.

Support for SSHv1, FTP, and Telnet access

You can use the CTM GUI to enable or disable SSHv1, FTP, or Telnet access to a switch. You can enable or disable this feature by selecting a node in the Domain Explorer tree and choosing Configuration > MGX Voice Gateway > Configuration Center. In the Node tab, choose the applicable options in the SSHv1, FTP, or Telnet field.

Proactive detection of data path failure for RPM-XF cards

The RPM-XF card runs a data path check (DPC) on the active and standby cards to detect the health of the data path. The results of the RPM-XF data path check are communicated to CTM through traps, and the alarms are displayed in the Alarm Browser.

Support for AnnexAB

You can enable AnnexAB features by choosing Configuration > MGX Voice Gateway > Configuration Center > H.248 tab and selecting the appropriate option under the Profile Undotted Notation or Profile Annexab Enabled field.

Support for SMS detection

You can create event mapping with the event type SMS. You can enable this feature by choosing Configuration > MGX Voice Gateway > Configuration Center > VBD tab and selecting SMS under the Event Index field.


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

NE Software Releases Added

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

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

ONS 15305 R2.0.4 and R2.0.5

ONS 15305 R2.2.2

ONS 15310 CL R9.0.1

ONS 15310 MA SONET R9.0.1

ONS 15310 MA SDH R9.0.1

ONS 15454 SDH R9.0.1

ONS 15454 SDH R9.0.2

ONS 15454 SONET R9.0.1

ONS 15454 SONET R9.0.2

ONS 15600 SDH R9.0.1

ONS 15600 SONET R9.0.1

Manually added to CTM:

ONS 15305 R2.0.2

Sections and Caveats Added

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

The section Installing the Latest CTM R9.0 Patch or Service Pack was added.

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

The following caveats were added:

CSCsy01229

CSCsy74450

CSCsz26474

CSCsz43543

CSCta58331

CSCta62163

CSCta73380

CSCta95729

CSCtb14476

CSCtb28839

CSCtb62164

CSCtb67646

CSCtb70847

CSCtb75511

CSCtb83268

CSCtb97851

CSCtc10079

CSCtc45424

CSCtc54674

CSCtd01497

CSCtd26328

CSCtd36677

CSCtd40139

CSCtd50613

CSCtf08332

CSCtf45430

CSCtg80725

CSCth85433

CSCth85521

CSCth87771

CSCth97940

CSCti13296

CSCti23042

CSCti90949

CSCtn93251

CSCtn95802

CSCts44079

CSCts60545

Sections Removed

The following sections were removed, because the CTM R9.0.0.680.3 patch inherits all bug fixes and obsoletes these earlier patches:

Installing the CTM R9.0.600.8 Patch

Installing the CTM R9.0.604.2 Patch

Installing the CTM R9.0.0.620.5 Patch

Installing the CTM R9.0.0.645.3 Patch

Installing the CTM R9.0.0.650.4 Patch

Installing the CTM R9.0.0.670.5 Patch

CTM-Supported NE Software Releases

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


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

Table 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)

Release 2.1

2.1

ONS 15216 EDFA1

Passive

1.0

ONS 15216 EDFA2

Release 2.3

v2.3.0

Release 2.4

v2.4.0

ONS 15216 EDFA3

Release 1.1

01.01.00

ONS 15216 FlexLayer

Passive

1.0

ONS 15216 OSC

Passive

2.0

ONS 15302

Release 2.0.2

2.0.2

ONS 15305

Release 2.0.21

2.0.2

Release 2.0.3

2.0.3

Release 2.0.42

2.0.4

Release 2.0.53

2.0.5

Release 2.2.24

2.2.2

ONS 15305 CTC

Release 3.0.5

04.60-X06F-28.14

Release 3.0.6

04.60-X08D-26.11

ONS 15310 CL

Release 5.0.8

05.08-006J-16.07

Release 6.0.1

06.01-005L-10.05

Release 6.0.3

06.03-007D-06.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.4

07.04-007A-08.16

Release 7.0.5

07.05-007D-20.22

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-08.19

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 8.5

08.50-007I-19.18

Release 8.5.1

08.51-008B-14.13

Release 9.0

09.00-008I-17.17

Release 9.0.15

09.01-009F-20.11

ONS 15310 MA SONET

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.4

07.04-007A-08.16

Release 7.0.5

07.05-007D-20.22

Release 7.0.7

07.07-007L-03.20

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-08.19

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 8.5

08.50-007I-19.18

Release 8.5.1

08.51-008B-14.13

Release 8.5.3

08.53-008J-17.07

Release 9.0

09.00-008I-17.17

Release 9.0.16

09.01-009F-20.11

ONS 15310 MA SDH

Release 9.0

09.00-008I-17.17

Release 9.0.17

09.01-009F-20.11

ONS 15327

Release 4.1.4

04.14-004C-09.23

Release 4.1.82

04.182-006-L2805

Release 4.6.6

04.66-005K-09.00

Release 5.0.4

05.04-005G-13.18

Release 5.0.8

05.08-006J-16.07

Release 6.0.1

06.01-005L-10.05

Release 6.0.3

06.03-007D-06.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.4

07.04-007A-08.16

Release 7.0.7

07.07-007L-03.20

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-08.19

Release 7.2.3

07.23-007F-22.02

ONS 15454 SONET

Release 4.1.4

04.14-004C-09.23

Release 4.1.6

04.16-004I-10.23

Release 4.1.82

04.182-006-L2805

Release 4.6.2

04.62-004E-23.20

Release 5.0.2

05.02-005C-26.23

Release 5.0.6

05.06-005H-29.19

Release 5.0.8

05.08-006J-16.07

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.0.3

06.03-007D-06.05

Release 6.2

06.20-006C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.1 (MSTP only)

07.01-006D-20.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.3 (MSTP only)

07.03-006I-29.09

Release 7.0.4

07.04-007A-08.16

Release 7.0.5

07.05-007D-20.22

Release 7.0.6 (MSTP only)

07.06-007H-08.13

Release 7.0.7

07.07-007L-03.20

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-15.13

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 8.5

08.50-007I-19.18

Release 8.5.1

08.51-008B-14.13

Release 8.5.2

08.52-008E-25.04

Release 8.5.3

08.53-008J-17.07

Release 9.0

09.00-008I-17.17

Release 9.0.18

09.01-009F-20.11

Release 9.0.29

09.02-009L-17.19

ONS 15454 SDH

Release 4.6.2

04.62-004E-23.20

Release 5.0.2

05.02-005C-26.23

Release 5.0.6

05.06-005H-29.19

Release 6.0

06.00-005H-18.21

Release 6.0.1

06.01-005L-10.05

Release 6.0.3

06.03-007D-06.05

Release 6.2

06.20-006C-17.10

06.20-P06C-17.10

Release 6.2.2

06.22-006F-23.21

Release 7.0

07.00-005L-19.20

Release 7.0.1 (MSTP only)

07.01-006D-20.20

Release 7.0.2

07.02-006I-06.16

Release 7.0.4

07.04-007A-08.16

Release 7.0.5

07.05-007D-20.22

Release 7.0.7

07.07-007L-03.20

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-15.13

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 8.0.2

08.02-008G-17.16

Release 8.5

08.50-007I-19.18

08.50-P07I-19.18

Release 8.5.1

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 9.0

09.00-008I-17.17

Release 9.0.110

09.01-009F-20.11

Release 9.0.211

09.02-009L-17.19

ONS 15501

Release 4.1 AC

4.1

Release 4.1 DC

4.1

ONS 15530

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

Cisco IOS Release 12.2(30)S

12.2(30)S

ONS 15540 Extended Services Platform (ESP)

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

Cisco IOS Release 12.2(30)S

12.2(30)S

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

Cisco IOS Release 12.2(29)SV3

12.2(29)SV3

Cisco IOS Release 12.2(30)S

12.2(30)S

ONS 15600 SONET

Release 5.0.8

05.08-006J-16.07

Release 6.0.1

06.01-005L-10.05

Release 6.2.4

06.24-006L-15.00

Release 7.0

07.00-005L-19.20

Release 7.0.4

07.04-007A-08.16

Release 7.2

07.20-006E-04.17

Release 7.2.2

07.22-007B-08.19

Release 7.2.3

07.23-007F-22.02

Release 8.0

08.00-007A-27.16

Release 9.0

09.00-008I-17.17

Release 9.0.112

09.01-009F-20.11

ONS 15600 SDH

Release 1.4

01.40-004A-15.18

Release 8.0

08.00-007A-27.16

Release 9.0

09.00-008I-17.17

Release 9.0.113

09.01-009F-20.11

ONS 15800

Release 2.1 (TL1 Agent Release 2.1)

2.1

ONS 15801

Release 2.1 (TL1 Agent Release 2.1)

2.1

ONS 15808

Release 2.2 (TL1 Agent Release 2.4)

2.4

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

5.3.10

Release 5.3.20

5.3.20

Release 5.4.10

5.4.10

Release 5.4.30

5.4.30

Release 5.5.00

5.5.00

Voice-Enabled Cisco MGX 8830 Multiservice Switch

Release 5.3.10

5.3.10

Release 5.3.20

5.3.20

Release 5.4.10

5.4.10

Release 5.4.30

5.4.30

Release 5.5.00

5.5.00

Voice-Enabled Cisco MGX 8850 Multiservice Switch

Release 5.3.10

5.3.10

Release 5.3.20

5.3.20

Release 5.4.10

5.4.10

Release 5.4.30

5.4.30

Release 5.5.00

5.5.00

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

5.3.30

Release 5.4.2014

5.4.20

Release 5.5.00

5.5.00

1 In order for CTM to support the ONS 15305 R2.0.2, you must add the software version to the Supported NE table. See Adding the ONS 15305 R2.0.2 to the Supported NE Table.

2 In order for CTM to support the ONS 15305 R2.0.4, you must install the CTM R9.0.0.645.3 or later patch.

3 In order for CTM to support the ONS 15305 R2.0.5, you must install the CTM R9.0.0.715.3 or later patch.

4 In order for CTM to support the ONS 15305 R2.2.2, you must install the CTM R9.0.0.680.3 or later patch.

5 In order for CTM to support the ONS 15310 CL R9.0.1, you must install the CTM R9.0.600.8 or later patch.

6 In order for CTM to support the ONS 15310 MA SONET R9.0.1, you must install the CTM R9.0.600.8 or later patch.

7 In order for CTM to support the ONS 15310 MA SDH R9.0.1, you must install the CTM R9.0.600.8 or later patch.

8 In order for CTM to support the ONS 15454 SONET R9.0.1, you must install the CTM R9.0.600.8 or later patch.

9 In order for CTM to support the ONS 15454 SONET R9.0.2, you must install the CTM R9.0.0.645.3 or later patch.

10 In order for CTM to support the ONS 15454 SDH R9.0.1, you must install the CTM R9.0.600.8 or later patch.

11 In order for CTM to support the ONS 15454 SDH R9.0.2, you must install the CTM R9.0.0.645.3 or later patch.

12 In order for CTM to support the ONS 15600 SONET R9.0.1, you must install the CTM R9.0.600.8 or later patch.

13 In order for CTM to support the ONS 15600 SDH R9.0.1, you must install the CTM R9.0.600.8 or later patch.

14 VQM is supported in VXSM R5.4.20.


Adding the ONS 15305 R2.0.2 to the Supported NE Table

In order for CTM to support the ONS 15305 R2.0.2, you must add the software version to the Supported NE table. Complete the following steps:


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

Step 2 Select a row that lists "Cisco ONS 15305" as the NE model, "2.0.2" as the software version, and "15305 2.0" as the version name.

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

Step 4 Enter 2.0.2 in the Software Version field. Change the Version Name field to 15305 2.0.

Step 5 Click OK.

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


Third-Party Patches and Security Notices

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

Installing the CTM-Supported Oracle 10.2.0.4 Patch

Starting from CTM R9.0.0.690.2, 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.0 Installation Guide, section "Server Specifications" for details.

Step 2 Enter the following command to verify that the CTM R9.0 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

CTM R9.0.0.690.2 has been tested with the latest critical Oracle patches (see CSCtj72766). To install the Oracle patches 9352164 and 9952234, complete the following steps:


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

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

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

Oracle environment: Non-RAC.

Data Guard Physical Standby database: Not implemented.

Job Scheduling system: Used.

ASM instance: Not implemented.

Initial setup: Oracle 10.2.0.4.0 and CTM R9.0 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
 
   

Installing the CTM-Supported Oracle Patch 7291739

The following steps describe how to install the Oracle patch 7291739.


Note The Oracle patch must be installed before installing the CTM R9.0.0.680.3 or later server patch.



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

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

Step 3 Download the p7291739_10203_SOLARIS64.zip file.

Step 4 From the p7291739_10203_SOLARIS64.zip file, extract the README.txt file that accompanies the Oracle patch 7291739. As you read the README.txt file, note that the CTM database has the following setup:

Oracle environment: Non-RAC.

Step 5 Refer to the README.txt file as you install the Oracle Interim Patch for Base Bug: 7291739. You must install the patch as the Oracle user.

Step 6 After the Oracle patch is installed, install the CTM R9.0.0.680.3 or later server patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CTM-Supported JRE and Apache Versions

The following tables list the Java Runtime Environment (JRE) and Apache versions supported in CTM R9.0.

Table 3 CTM-Supported JRE Version 

JRE Version
Caveat ID
Caveat
Comment

1.5.0_17

This JRE version was used when CTM R9.0 was released.


Table 4 CTM-Supported Apache Versions 

Apache Version
Caveat ID
Caveat
Comment

2.2.8

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

2.2.11

CSCsx50126

Due to security issues, CTM must support Apache web server version 2.2.11.

This Apache version was supported starting in CTM R9.0.0.600.8.


Resolved Caveats

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

Table 5 Caveats Resolved in CTM R9.0 

Caveat ID
Caveat

CSCse91332

CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.

CSCse91435

CTM GateWay/CORBA does not send a notification event when an existing network partition is deleted from CTM.

CSCsf96351

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

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

CSCsg30824

CTM allows you to edit the PPM port rate from OC48 to OC3 when a server trail exists and contains an STS-6c port rate.

CSCsg86081

Unable to retrieve a J1 path trace on ONS 15600 SDH ASAP cards.

CSCsh32836

Cannot view the ML card's VLAN port IP address and corresponding NE and slot number after creating an L2 service.

CSCsh46506

The following problems are observed:

1. The default MGX management module of CTM log files is set to have high verbosity. To resolve this issue, the debug levels in the config files have been reduced for this release. However, if this problem occurs, the debug levels have to be increased and the problem is reproduced.

2. The MGX management module log files are not cleared when CTM or the MGX NE service is restarted.

CSCsh69305

Active and standby ML cards are not shown when creating VLANs on 802.17 Resilient Packet Ring (RPR) topologies using the corresponding wizard.

CSCsi25561

When you change the CTM database password from the Database Properties pane of the Control Panel and the preliminary checks fail, the CTM server is not restarted, the database password is not changed, and you are notified of the proper EMS alarms. However, the following error message appears: "Caution: The database password has been changed by a user. The CTM server will restart in 15 seconds."

CSCsj01676

The Maximum Login Attempts alarm for an unknown user is not cleared if you set the Max Retries field in the Control Panel to one.

CSCsj19520

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

CSCsj54751

The CTM client user interfaces are dimmed for several minutes.

CSCsk00034

Unable to perform real-time statistics polling on connections that do not have statistics support on one end. The RPM endpoint has no real-time statistics support.

CSCsk19647

Each network partition has a limit of 500 NEs. If NEs are manually added and autodiscovered, and exceed the network partition limit, the NEs are added to the Domain Explorer but not to the network service. As a consequence, CTM cannot manage or connect to the NEs.

CSCsk27692

The Network Map occasionally displays a newly added L2 link in orange (indicating a major alarm), even though no alarms are reported in the Alarm Browser window.

CSCsk28808

Unable to select an alarm profile for interlink ports on SDH ADM_10G cards.

CSCsk44773

Due to security issues, CTM must support Apache web server version 2.0.61.

CSCsk48068

When you delete a VLAN from an L2 topology, the following error message appears: "Could not delete VLAN completely."

CSCsk50113

The CTM client disconnects from the CTM server.

CSCsk52250

The CTM client shows the wrong installation status of CTM GateWay/CORBA.

CSCsk53838

The Audit Trail table does not contain any entries for one or more nodes, or it stops collecting updates on the same nodes. The audit trail data is available in CTC.

CSCsk63579

NE alarms are not saved in the database and not displayed in the Alarm Browser and Alarm Log.

CSCsk68874

It takes too long for a newly created L2 topology to appear in the L2 Topology table.

CSCsk71257

The Change Card function does not change the card in the shelf, module, and tree views.

CSCsk78622

The VC3 value is zero in the Link Utilization table for VC3 port group circuits.

CSCsk80234

Some NEs are not visible in the Network Map.

CSCsk86875

Some 1-day PM buckets are missing.

CSCsk90677

In the Alarm Browser, an "Alarm Suppressed for Maintenance" alarm is displayed for an OPT-BST card and it cannot be cleared.

CSCsk96257

The CTM client freezes.

CSCsl03900

The APC Domain table is empty if you select a node that does not terminate an APC domain.

CSCsl06339

The notification service process restarts. When you use the showctm -v command, the start time of the notification service process is more recent than the start time of other processes. All other processes work correctly, including CTM GateWay/CORBA, which is based on the notification service.

CSCsl08269

A timeout operation occurs when you remove an ML card from an RPR topology. However, the ML card has been provisioned correctly.

CSCsl09775

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

CSCsl11930

Oracle startup fails due to lack of memory after a dual-server installation. The following message appears:

SQL> ORA-27102: out of memory

SVR4 Error: 22: Invalid argument

(Related caveat ID: CSCsq58179.)

CSCsl15115

There is a high CPU usage by the CTC-based network service. High CPU usage is normal during provisioning operations or when a large number of alarms is generated on NEs managed by the network service.

CSCsl17182

Unable to open or modify a TL1 tunnel.

CSCsl17291

Unable to create a manual link using CTM GateWay/CORBA.

CSCsl20872

Creating an L1 circuit fails and the following message appears: "EID-932: Failed to route the circuit. Details: client timeout reached."

CSCsl21987

Random CTM GateWay/TL1 CPU usage is higher than normal. It shows approximately 10% with peaks of up to 15%.

CSCsl22134

The following error message appears when creating an OCHNC circuit between NE R5.x and R6.x:

The selected NEs do not support bidirectional circuit creation.

CSCsl22172

The Ethernet PM table shows rxPackets and txPackets counters instead of the rxTotalPkts and txTotalPkts counters. The rxTotalPkts and txTotalPkts counter are shown as N/A.

CSCsl22236

Unable to add manually the following NEs to the CTM client:

ONS 15327 R4.1.x

ONS 15327 R6.0.x

ONS 15327 R6.2.x

ONS 15454 SONET R4.1.x

ONS 15600 SONET R6.0.x

ONS 15600 SONET R6.2.x

If any of the preceding NE versions is previously added to the CTM client, you cannot connect to the NE and mark it as In Service.

CSCsl22254

Some L2 topologies are not displayed or they appear as split topologies in the Layer 2 Topology table.

CSCsl23871

Cannot monitor and provision the auto laser shutdown parameters on the OPT_PRE card. The Auto Laser Shutdown tab is not present in the NE Explorer.

CSCsl26070

Updated link cost and shared risk link group (SRLG) values are not available after migration.

CSCsl26108

CTM performs slowly while connecting, discovering, and resynchronizing CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.

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

CSCsl26218

The NE services freeze after adding 3000 NEs, deleting 30 NEs, adding a new topology with GNEs, and marking several NEs as Out of Service and then In Service.

CSCsl28305

Unable to determine the status of the database when the migration or export operation fails.

CSCsl31836

In the CTM Login dialog box, the text area with the legal disclaimer displays only 69 characters for each row; it should display 80 characters.

CSCsl34203

CTM GateWay/CORBA can retrieve Ethernet circuits using the CTP naming convention.

CSCsl34542

The upgrade from one CTM release to another CTM release fails due to an error in creating a primary key constraint on the ACTIVE_ALARM_TABLE.

CSCsl37025

The PM service restarts after several days. The error log contains a large number of errors associated with writing PM data to the database.

CSCsl37264

The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.

CSCsl39284

Unable to create circuits on optical nodes that belong to the default Network Partition 1.

CSCsl43107

A background Java/Javaw process is opened and does not close when you close the CTM client. Every time the CTM client is opened, a new Java process is created. Therefore, if the CTM client is opened several times, several dangling Java processes are created.

CSCsl45830

CTM GateWay/TL1 restarts.

CSCsl48499

The backup files are not listed in the Backup File dialog box after choosing Administration > Memory Backup Upload in the Domain Explorer.

CSCsl95721

The Circuit table does now show port names for circuits on MRC-12 cards (on ONS 15454 R6.0.1 NEs) or MRC-4 cards (on ONS 15454 R8.0 NEs). The Circuit table shows incorrect port names for circuits on DS3 cards (on ONS 15454 R6.0.1 NEs).

CSCsm17261

When a node is marked as Out of Service and then In Service, the alarm ID and time stamp are assigned new values in the Alarm Browser. The alarm notes are also missing.

(Related caveat ID: CSCsq24237.)

CSCsm21463

The Circuit table does not display the port name for E1-42 cards for source and destination NEs. Also, the Circuit table does not display the port name for STM-1 cards for destination NEs.

CSCsm64677

The restoreME application program interface (API) does not work correctly, so you cannot use CTM GateWay/CORBA to restore the managed element (ME) configuration file.

CSCsm99421

Connection termination point (CTP) values of alarms are printed when you run the getAllActiveAlarms API. But for certain alarms for which the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.

CSCso01840

It takes a long time to discover NEs after the NE service restarts.

CSCso01900

The CTC-based NE service takes a long time to reconnect and discover NEs.

CSCso01942

CTM takes a long time to discover a large network of GNEs and ENEs.

CSCso07731

If you use textual routing to provision protected contiguous concatenation (CCAT) circuits, the operation might fail.

CSCso35202

On CTM R8.5, the Oracle shutdown script does not work while the server workstation is shutting down. On CTM R8.0 and R8.5, Oracle occasionally fails to start automatically while the CTM server workstation is starting, and then the CTM server does not start correctly.

CSCso44701

CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job Monitor displays the following message:

(Too many open files)

(No such file or directory)

CSCso51993

Manual links do not work correctly. In the Link table, circuits related to a specific link are not shown, and manual links are shown as not being used for routing.

CSCso76700

The CTM GateWay/CORBA NBI creates additional proxy consumers if you do not stop CTM GateWay/CORBA before executing the ctms-stop or ctms-start commands.

CSCso92358

Disabled tabs are enabled when performing operations in the navigation tree.

(Related caveat ID: CSCsk31966.)

CSCsq24237

CTM retrieves old and new alarms that are identical when a node is marked as Out of Service and then In Service. The same problem occurs when the NE service is restarted.

CSCsq26342

The getHistoryPMData API takes longer than 15 minutes to return data.

CSCsq26362

The output file generated from getHistoryPMData returns duplicate rows.

CSCsq31631

Memory backup and memory restore fail on MGX nodes when Telnet is disabled.

CSCsq32073

Due to security issues, CTM must support Apache web server version 2.0.63.

CSCsq50589

In the Domain Explorer, you can set any password for CTM server-to-NE connections, because the password syntax is not verified correctly.

CSCsq65111

In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.

CSCsq78385

The SMService_port property generates a random value even if it is set to a fixed value.

CSCsq87850

SVLAN ports are not displayed correctly.

CSCsq89269

In the NE Explorer for a GE_XP card, if you click the SVLAN tab, the same tab appears when you select another GE_XP card.

CSCsq92344

After upgrading to CTM R8.5, all MGX NEs monitored by the CTM server report voltage sensor alarms against the VXSM card in slot 1. However, if you log into the chassis of the unit, there are no corresponding alarms on the gateway.

CSCsq94272

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

CSCsr06975

In the NE Explorer for a GE_XP card, if you click the SVLAN tab, deselect all SVLANs, and click Apply, an error occurs.

CSCsr30785

The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.

CSCsr48358

The prune_ne_ipaddress script does not work with IPv6 addresses.

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

CSCsr53609

A CTM server core dump file is created when the CTM server shuts down.

CSCsr55311

When you filter alarms that have CTM as the affected object, the alarm does not appear in the Alarm Browser or Alarm Log.

CSCsr55335

Duplicate circuit names appear in CTM when a circuit name is updated in CTC.

CSCsr65306

The migration scripts fail with a Java exception.

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

CSCsr70191

When the system date is changed while the CTM server is running, the CTM server shuts down the NE, PM, and NBI services within five minutes.

CSCsu26103

The Supported NE table > Add Supported NE dialog box shows incongruous data.

CSCsu30979

If you try to modify a QoS profile on a VLAN drop, the operation fails with the following error message:

EID-874: Failed to modify some drops on the L2 service.

CSCsu50742

The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.

CSCsu54724

In the NE Explorer for a GE_XP card, the list of configured SVLANs is not available.

CSCsu68317

The northbound CORBA interface returns incorrect cross-connect table information. The getAllCrossConnections API returns a CTP name retrieved by a VC-12 circuit in the format /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.

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

CSCsu82028

The APIs getTCATPPParams and setTCATPParams do not work for trunk ports on GE_XP and 10GE_XP cards.

CSCsu88218

When creating multiple STS circuits, an error is returned.

CSCsv12810

An MGX is added to a CTM server, but is not included in the automatic backup process.

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

CSCsu90217

Continuous 15-minute and 1-day PM lost bucket alarms occur and do not clear.

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

CSCsv00207

A cleared alarm disappears from the Alarm Browser.

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

CSCsv33266

If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.

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

CSCsv45598

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

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

CSCsw22308

VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with incorrect numbers, making it impossible to tell which VT the PM data is for.

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

CSCsw68952

A database export fails with the following error:

ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.

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

CSCsw72207

The Protection panel shows the wrong name for an OTU2_XP card.

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

CSCsw91974

In a large network of GNEs and ENEs, CTM fails to collect PM data.

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

CSCsx23360

An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle Enterprise Manager or the Alert Log.

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

CSCsx22431

For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports the correct wavelength value.

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

CSCsx26527

The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer do not exist.

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

CSCsx38325

The first database export from the CTM GUI fails.

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

CSCsx44115

The CTM server does not send SNMP traps or get IPv6 destinations. The following problems occur:

Ethernet CoS PM data on ML cards is not retrieved from IPv6 NEs.

The SNMP gateway does not forward traps to IPv6 hosts.

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

CSCsx50126

Due to security issues, CTM must support Apache web server version 2.2.11.

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

CSCsx50161

The Apache Tomcat software should be disabled to avoid potential security issues.

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

CSCsx52287

Event notification is not audible.

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

CSCsx52433

From the MGX Voice Gateway Configuration Center, the Circuit Identifier field is blank for DS1 and SONET lines on a VXSM card. Also, utilization counters are not enabled in the Diagnostics Center > Resource Control tab.

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

CSCsx55667

The getCTPsAndTopologicaLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."

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

CSCsx56687

The SPAN_BS_TABLE database table displays incorrect working and protected values.

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

CSCsx64513

A warning message of a possible traffic impact appears when reconfiguring circuits. This warning message should not appear, because reconfiguring circuits does not affect traffic.

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

CSCsx81985

During intensive database usage, archive log pruning does not efficiently remove files from the /db05 directory.

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

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.

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

CSCsy14909

A VLAN range cannot be added on a 10GE_XP/GE_XP card.

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

CSCsy29600

CTM does not receive PM data from managed MGX devices.

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

CSCsy30294

CTM fails to automatically route and create a STS-24c circuit to the 15454-ADM-10G card when entering a value in the Time Slot Restriction field.

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

CSCsy56348

Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.

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

CSCsy83061

From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for release 8.0 NEs.

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

CSCsy84624

UPSR/SNCP switch selectors are missing from the Circuit trace.

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

CSCsy95336

CTM fails to reconfigure circuits on release 8.5 NEs.

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

CSCsz33838

Cannot add drops on cards configured in Automatic mode.

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

CSCsz53477

The Error Log contains multiple errors that are similar to the following:

CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290 

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

CSCsz58653

Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.

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

CSCsz63889

Sometimes memory backups fail for CTC-based release 6.0.1 NEs.

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

CSCsz71168

A database import causes incorrect index error messages.

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

CSCsz75781

The Error Log contains meaningless DWDM error messages.

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

CSCsz79773

Daily backups automatically scheduled from CTM are canceled.

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

CSCsz96763

In the Service Up Time log, clicking the Stopped At column does not sort the table.

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

CSCsz83568

A DB WriterWorker NPE appears in the pmservice.log file for MRC-12 cards.

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

CSCta00978

When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.

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

CSCta23414

Installing CTM R9.0.0.600.7 shows security_config.sql script errors.

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

CSCta29948

Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.

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

CSCta30560

Circuit Wizard fails when the back button is used after changing destinations.

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

CSCta30577

The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.

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

CSCta30985

In locked state, there is a C server memory leak due to zombie lightweight processes (LWPs).

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

CSCta31966

Memory usage for the ooemc process increases over a period of time.

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

CSCta33231

The number of alarms displayed on the dashboard and NE Explorer is wrong. However, the alarm count is shown correctly in the Alarm Browser.

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

CSCta35142

CTM restarts and the core_pmon.log file reports an Oracle error.

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

CSCta39574

When opening the Circuit table from an ONS 15454 node, circuits are not retrieved and a timeout error is displayed.

Note This caveat is fixed with the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. If a timeout occurs again, increase the client database timeout period. Refer to section K.6.2, "Database Timeout Occurs" in Appendix K of the Cisco Transport Manager Release 9.0 User Guide.

CSCta42487

The SM service disconnects during a JMOCO hello message, and the CTM server restarts. (Related caveat ID: CSCtf17428.)

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

CSCta61660

ENE/GNE role changes on the network cause unstable NE service and node connectivity issues.

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

CSCta69019

The ctms-stop and ctms-abort scripts do not work when Oracle is down.

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

CSCta69422

The ONS 15305 NE Service hangs, and if you try to mark NEs as In Service or Out of Service, CTM returns the following error message:

EID-542: Database error: Cannot modify the NE state.

(Related caveat ID: CSCta27875.)

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

CSCta69424

If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the CTM client freezes.

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

CSCta69923

Cleared alarms are not removed from the Alarm Browser.

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

CSCta73923

ONS 15216 EDFA3 nodes lose connectivity with CTM.

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

CSCtb01411

The network services and network service instances cannot be stopped or started from the Control Panel. The SMService-0-<timestamp>.log file shows the following error message:

EID-5016: Exception: %01 occurred while launching service process.java.io.IO

Exception: Too many open files

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

CSCtb05738

CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC are assigned to a queue based on the value of the NE node ID. Because the node ID often has an even value, only queues with an even ID are used to process events. Consequently, half of the threads are instantiated but are never used to process events.

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

CSCtb13395

The Alarm Browser does not display some cleared alarms. CTC shows the cleared alarms, but the same alarms are missing from the CTM Alarm Browser.

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

CSCtb21147

CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.

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

CSCtb25595

Alarm icons display incorrect information in the Domain Explorer tree.

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

CSCtb33156

Oracle undo and temp tablespaces consume all of the free space in the /db01 partition.

Note You must install the Oracle security patches before installing the latest CTM R9.0 patch. See Installing the CTM-Supported Oracle Patch 7291739.

CSCtb25595

Alarm icons display incorrect information in the Domain Explorer tree.

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

CSCtb55127

Exceptions are displayed and logged when NE services start up.

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

CSCtb83002

The CTM client freezes and does not respond to user commands.

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

CSCtb85880

After performing NE software upgrades, the SM service restarts NE services.

(Related caveat ID: CSCtc20552.)

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

CSCtb30304

An error message (EID-315) appears after selecting Edit > Find to search for a circuit.

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

CSCtb31787

CTM R9.0 raises incomplete critical alarms.

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

CSCtd56250

CTC cannot be launched from CTM.

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

CSCtb55280

EQPT_INFO_TABLE is filled incorrectly by the MGX NE service.

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

CSCtb59547

CTM GateWay/CORBA reports incorrect physical location information.

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

CSCtb59923

Several exceptions appear in the CTM network service log.

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

CSCtb65065

In the NE Explorer for the ONS 15310 MA or the ONS 15454 MSPP, the first time you select an optical card, the Transceiver tab is blank.

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

CSCtb72630

Network discovery hangs when the LINK_TABLE database table is empty.

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

CSCtb73160

The Circuit table does not display port names for ONS 15454 ANSI DS1_E1_56 and OC192_XFP cards.

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

CSCtb78977

The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.

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

CSCtb83164

After device provision configurations, the following APIs are not updated: getEquipment, getAllEquipment, and getAllEquipmentName.

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

CSCtb88190

CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs with an Unavailable status.

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

CSCtc10514

CTM does not receive alarms from ONS 15305 R2.0 NEs.

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

CSCtc19328

The CTM Domain Explorer window freezes and you are unable to select other NEs.

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

CSCtc20162

When a single ONS 15305 NE service manages than one hundred ONS 15305 NEs, the ONS 15305 NE service restarts.

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

CSCtc35552

The discovery state of an NE is incorrect.

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

CSCtc49087

CTM shows MGX 88xx chassis serial no. as N/A in Inventory table.

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

CSCtc67375

OCHCC circuits are not shown when the Circuit table is launched from a link.

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

CSCtc70085

From the CTM client, you cannot launch CTC on release 9.0.x ENEs.

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

CSCtc73082

Adding a preprovisioned MGX node to a CTM server results in high CPU usage.

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

CSCtd03803

ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain in Sync_Config state.

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

CSCtd31222

Circuits without a destination are not displayed in the Circuit table.

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

CSCtd49099

Occasionally, Ethernet PM data is not collected for historical 15-minute and 1-day intervals.

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

CSCtd50557

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

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

CSCtd52681

CTM R9.0 must add support for the ONS 15305 R2.0.4.

Note This caveat is fixed with the CTM R9.0.0.645.3 or later patch.

CSCte35831

CTM R9.0 must add support for the ONS 15454 SONET and ONS 15454 SDH R9.0.2.

Note This caveat is fixed with the CTM R9.0.0.645.3 or later patch.

CSCte39776

The CTM NE Description field does not match the NE description in CTC.

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

CSCte65495

Server memory usage for the ooemc process increases over a period of time with every MGX NE resync.

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

CSCte98243

Cannot clear PM counters for Ethernet real-time PM data on CE-MR-10 cards.

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

CSCtf06220

In a high availability, single-node, geographical redundancy setup, the database migration from CTM R9.0 to R9.1 hangs when ARCHIVELOG mode is enabled. The /db05 filesystem fills up, and the migration hangs.

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

CSCtf06511

If you upgrade from to CTM R9.1 on a week day (not on a weekend), the following error occurs:

ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running

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

CSCtf27628

The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does not update. This issue causes problems with Oracle statistics management and node connectivity.

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

CSCtf78021

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

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

CSCtf78039

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

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

CSCtg56522

Cannot add CTC-based NEs to a CTC-based network service. When you use the Add NE wizard, the CTM server does not manage the new NE and the NE is not shown in the Domain Explorer.

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

CSCtg92011

Customer request to change minimum length of CTM username to 3 characters.

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

CSCth33907

Add support for the Solaris patch cluster released on July 06, 2010 (Recommended OS Cluster Solaris 10 SPARC July 06 2010).

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

CSCth33919

Add support for the Veritas Storage Foundation 5.0 Maintenance Pack 3 Rolling Patch 2 (RP2).

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

CSCth40549

A confirmation message appears for no reason in the Domain Explorer.

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

CSCth48038

CTX Transceiver tab is blank for Cisco ONS 15310 MA SDH nodes.

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

CSCti10246

The CTC-based network services can restart when short of stack memory.

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

CSCti30435

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

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

(Related caveat ID: CSCth71367.)

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

CSCti13296

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

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

CSCti61844

The Create Layer 2 Topology wizard or the Add/Remove Card wizard freezes for several minutes, and then proceeds correctly.

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

CSCti72327

L2 topology resynchronization takes too long when there are many VLANs.

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

CSCti90949

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

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

CSCtj21034

The remote debug console (RDC) has no commands for Layer 2 cache management.

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

CSCtj72796

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

CSCtj88343

CTM must support Cisco Edge Craft Release 2.2.2.

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

CSCtj88384

The getAllSubnetworkConnections API does not work.

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

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.0 Patch or Service Pack.

CSCtj92364

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

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

CSCtk13431

High CPU usage after bulk circuit creation.

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

CSCtk81770

CTM does not start because the inode limit has been reached in the /opt directory.

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

CSCtk13453

PM data is not retrieved when using GateWay/CORBA APIs on some layer rates.

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

CSCtk99910

Sometimes, a CTC library deadlock occurs when CTM manages a large number of nodes. NE connectivity is lost and no longer visible in CTM.

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

CSCtl06435

The network admin user cannot modify or delete OCHNC circuits. An access violation error is shown.

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

CSCtl71781

CTM reports that RAM usage is at 95 percent and generates an alarm.

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

CSCtl83275

The CTM client freezes after some time.

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

CSCtn30937

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

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

CSCto71624

SNMP-based NEs like ONS 15216 and ONS 15305 do not receive SNMP traps.

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

CSCtq43320

CTM and Cisco Edge Craft Release 2.2.2 alarm browsers are not synchronized.

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

CSCts64323

CTM must support Cisco Edge Craft Release 2.2.3.

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


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

Open Caveats

The following sections describe the caveats that are not resolved in the CTM R9.0 software:

Installation and Upgrade Caveats

CTM Client Caveats

Alarm Management

Circuit and Link Management

User Management

Data Services

Domain Explorer

NE Explorer

Network Map

Performance Monitoring

Miscellaneous

CTM Server and Database Caveats

Cisco Transport Controller Caveats

High Availability Caveats

CTM GateWay/TL1 Caveats

CTM GateWay/CORBA Caveats

NE-Specific Caveats

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15302 and 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 ONS 15800, Cisco ONS 15801, and Cisco ONS 15808

Installation and Upgrade Caveats


CSCsr65306

Symptom    When upgrading from one CTM release to the next (as detailed in the Cisco Transport Manager Installation Guide), the migration scripts fail due to the following Java exception:

...
Executing the SQL pre-upgrade script...
Exception in thread "main" java.lang.NoClassDefFoundError: 
org/bouncycastle/openssl/PasswordFinder
        at com.cisco.stardm.platform.Decrypt.main(Decrypt.java:65)

Conditions   This problem occurs when upgrading from:

CTM R7.2 to CTM R8.0

CTM R8.0 to CTM R8.5

CTM R8.x to CTM R9.0

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


CSCsr65845

Symptom    The CTM server cannot connect to and manage MGX NEs.

Conditions   This problem occurs when the CTM server and the CTM database are installed on separate UNIX workstations, and the Oracle system ID (SID) is different from the default SID (CTM).

Workaround   Edit the following files:

/opt/CiscoTransportManagerServer/cwm/svplus/.cshrc

/opt/CiscoTransportManagerServer/cwm/svplus/.profile

In these files, replace the default Oracle SID (CTM) with the SID that will be specified in the CTM database installation.


CSCsw69697

Symptom    After a database migration, there are no modules available for debugging. The list under the 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 debugging active on modules associated with NEs that are not supported in CTM R9.0.

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


CSCsx34727

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

Conditions   This problem occurs when performing one of the following upgrades:

From CTM R8.0 or R8.5 with a medium network size to CTM R9.0 with a large network size

From CTM R8.0 or R8.5 with a medium network size to CTM R9.0 with a high-end network size

From CTM R8.0 or R8.5 with a large network size to CTM R9.0 with a high-end network size

Workaround   Close the error message window and continue the migration.


CSCsx50126

Symptom    Due to security issues, CTM must support Apache web server version 2.2.11.

Conditions   See Symptom.

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


CSCsx50161

Symptom    The Apache Tomcat software should be disabled to avoid potential security issues.

Conditions   The Apache Tomcat software is installed as part of JBOSS during installation.

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


CSCsy01229

Symptom    When installing CTM R9.0 on a T2-based server in a small network configuration, the installation fails at the end of disk 3.

Conditions   This problem occurs when you install CTM on a T2 processor-based Sun workstation. The installation succeeds on SPARC-based servers, but fails on T2-based servers.

Workaround   Complete the following steps to install CTM R9.0 on a T2 server in a small network configuration. This procedure, which must be performed in a root shell, fixes the Oracle memory and system project settings. The system must be equipped with at least 8 GB of RAM.

This procedure applies only to small CTM configurations that:

Are not part of a high availability (HA) configuration.

Are equipped with a T2-based processor.

Have at least 8 GB of RAM.

Use a single server setup (where you install the CTM server and Oracle database on the same workstation).


Step 1 Enter the following command to verify that the workstation has at least 8 GB of RAM, which is the minimum RAM required for a small installation on a T2 server:

#prtdiag -v | grep -i memory
 
   

Step 2 Complete the following procedures to download the CTM R9.0.0.550 patch and then install CTM.


Downloading the CTM R9.0.0.550 Patch


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

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


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


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

Step 4 Click Cisco Transport Manager 9.0.

Step 5 At the Select a Release screen, click Expand all and click 9.0.0.550.1.

Step 6 In the right pane, click CTM9.0.0.550.patch.zip.

Step 7 At the Download Image screen, click Download.

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

Step 9 Download the patch zip file to a temporary directory (such as /temp) on the CTM server.

Step 10 In Solaris, enter the following commands to extract the file to the temporary directory:

cd /<directory_name>
unzip CTM9.0.0.550.patch.zip
 
   

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

cd /temp
unzip CTM9.0.0.550.patch.zip
 
   

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

Step 11 Enter the following command to enter the directory:

cd 550
 
   

Applying the Patch and Installing CTM R9.0


Step 1 If the CTM server has never been installed on the current workstation (in other words, a fresh installation), skip to Step 3 after completing all of the steps in section 2.1.2, "Updating the System Parameters" in the Cisco Transport Manager Release 9.0 Installation Guide.

Step 2 Complete the following substeps to remove the previous CTM installation (if any):

a. Delete all of the files and subdirectories in the /db0* directories.

b. Remove the CTM server installation directory (the default is /opt/CiscoTransportManagerServer).

c. Remove the Oracle pfile of the previous installation.

Generic pfile path: /oracle/admin/<SID>/pfile/init<SID>.ora

Default pfile path: /oracle/admin/CTM/pfile/initCTM.ora

d. Reboot the system.

Step 3 In the patch folder, go to the T2_small_install directory and enter the following commands to check the permissions:

#cd ./T2_small_install
#ls -l *.sh
#chmod +x *.sh
 
   

Step 4 Insert the first installation disk, start the CTM installer, and select all of the required installation settings as per the Cisco Transport Manager Release 9.0 Installation Guide.


Caution Stop at the Pre-Installation Summary screen. Do not click the Install button.

Step 5 In a separate root shell, enter the following commands to launch the fix_installation.sh script:

#cd /T2_small_install
#./fix_installation.sh
 
   

After you launch the fix_installation script, usage instructions appear on screen. See the usage example below.

When you launch the script, specify the <CTM_version> and <SID>. Be very careful to specify the correct values.

Usage Example

# ./fix_installation.sh
 
   

Usage: ./fix_installation.sh <CTM_version(9.0)> <SID>

Example:

./fix_installation.sh 9.0 CTM
 
   

Step 6 After the fix_installation script runs and preliminary checks succeed, the following message appears onscreen:

Please PRESS INSTALL NOW on Pre-Installation Summary screen
 
   

Step 7 Return to the Pre-Installation Summary screen. Click the Install button and continue the installation as per the installation guide to complete the CTM server installation.

The script runs during the CTM installation and continuously prints the following output until the fix is complete:

Script ./fix_installation.sh is running ...
 
   

Once complete, the script exits with the following messages:

___ PFILE has been created
___ Modifying pfile ...
___ <SID> pfile has been modified. 
Script ./fix_installation.sh has completed successfully
 
   


CSCsy74450

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

Conditions   This problem occurs only in a small installation when the optional db01_rd and db02_rd partitions are present but do not meet the minimum partition size requirement.

Workaround   Use either of the following workarounds:

Delete the optional db01_rd and db02_rd partitions; then, restart the installation.

Add more space to the db01_rd and db02_rd partitions. Both partitions should have at least 1 GB of available space. Then, restart the installation.


CSCtb55127

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

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

Workaround   None.


CSCtb97851

Symptom    The CTM server fails to start. If you run the ctms-start command, the command fails with the following error:

ctms-start: Command not found.

Conditions   This problem occurs when you upgrade CTM from an earlier release, but you cancel the installation at the final Installation Summary screen. By cancelling the installation, the existing CTM installation is not removed, but it is renamed. When you then 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.0
ln -s CiscoTransportManagerServer-old-<timestamp> CiscoTransportManagerServer
rm CiscoTransportManagerServer.oldCTM
 
   

CSCtd50557

Symptom    Cannot install the CTM 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.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternatively, change the name of the directory where the CTM client is installed.


CSCtf06220

Symptom    In a high availability, single-node, geographical redundancy setup, the database migration from CTM R9.0 to R9.1 hangs when ARCHIVELOG mode is enabled. The /db05 filesystem fills up, and the migration hangs.

Conditions   This problem occurs when many archive log files are created under the /db05 filesystem. When the /db05 filesystem fills, it blocks the database migration.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, remove the archive log files manually from the /db05 filesystem, or use the logarch.sh script to remove the files.


CSCtf06511

Symptom    If you upgrade from to CTM R9.1 on a week day (not on a weekend), the following error occurs:

ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running

Conditions   See Symptom.

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


CSCtf27628

Symptom    The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does not update. This issue causes problems with Oracle statistics management and node connectivity.

Conditions   This problem occurs after migrating the CTM server to CTM R9.1.

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


CSCtf45430

Symptom    After migrating to CTM R9.0 or R9.1, the processes parameter value is not set correctly in the initCTM.ora file.

Conditions   This problem occurs in a high-end setup after upgrading from CTM R8.5.0.387.6 to CTM R9.0 or R9.1.

Workaround   Shut down the CTM server and Oracle database; then, in the /oracle/admin/<CTM_SID>/pfile/init<CTM_SID>.ora file, change the processes parameter value to 5000.


CSCtf78021

Symptom    After upgrading from CTM R8.5 to CTM R9.0 or 9.1, the CTM Config database table shows discrepancies.

Conditions   If you compare the R9.0 or R9.1 CTM Config database table to the R8.5 version, discrepancies exist. The CTM Config database table is not migrated correctly.

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


CSCtf78039

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

Conditions   This problem occurs with all CTM server sizes.

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

CTM Client Caveats

This section contains the following information:

Alarm Management

Circuit and Link Management

User Management

Data Services

Domain Explorer

NE Explorer

Network Map

Performance Monitoring

Miscellaneous

Alarm Management


CSCec49029

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

Conditions   TCC2 and TCC1 alarms display the module name as "TCC" in the Alarm Browser and Alarm Log.

Workaround   None.


CSCeg14267 (Related caveat IDs: CSCef94105, CSCef89143)

Symptom    Link down alarms, syslog events, and configuration messages are not received for ML cards on ENEs behind the firewall when SNMP v2 is enabled.

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

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


CSCin76849

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


CSCsv00207

Symptom    When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.

Conditions   With automatic alarm acknowledgement, the server should automatically acknowledge alarms when they are cleared and move them from the Alarm Browser to the Alarm Log. When this problem occurs, the cleared alarm disappears from the Alarm Browser and is not shown in the Alarm Log.

This problem occurs when automatic alarm acknowledgement and automatic pruning of fault management data are enabled. To check whether your system is affected by this problem, enter the following SQL command on the CTM database:

SQL> select * from ACK_TABLE where ACKINDEX=-1;
 
   

If the query returns zero records, your system is affected by this problem.

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


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.


CSCsz79773

Symptom    Occasionally, NE backup files are canceled when automatic daily backups are scheduled. The Job Monitor table shows two backups running at the same time for the same NE, yet only one backup executes successfully. The second backup fails with the following exception: "Cannot execute Backup Database; A similar task is already running."

Conditions   This problem occurs when you use the Control Panel to schedule automatic backups for ONS 15454 NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternatively, disable and re-enable automatic backup in the Control Panel.

After the patch is applied, the backup file is created in the correct folder. However, the Job Monitor table still shows two backups running at the same time for the same NE, and only one backup executes successfully. The second backup fails with the following exception: "Unknown exception."


CSCta29948

Symptom    Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.

Conditions   This problem affects GNEs and ENEs under normal conditions.

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


CSCta33231

Symptom    The number of alarms displayed on the dashboard and NE Explorer is wrong. However, the alarm count is shown correctly in the Alarm Browser.

Conditions   This problem occurs with MGX devices in a network managed by CTM R9.0. This problem was not seen for ONS devices managed by CTM.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, mark the NE Out-of-Service. Wait an appropriate time for the node to sync and then mark the NE In-Service.


CSCta69923

Symptom    Cleared alarms are not being removed from the Alarm Browser.

Conditions   To confirm whether this problem affects your network, turn on the service logs and monitor whether or not alarm clear messages in the logs are shown correctly in the Alarm Browser.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, mark the NE In-Service, then Out-of-Service.


CSCtb05738

Symptom    CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC are assigned to a queue based on the value of the NE node ID. Because the node ID often has an even value, only queues with an even ID are used to process events. Consequently, half of the threads are instantiated but are never used to process events.

Conditions   This problem occurs when there are many uncleared alarms, and CTM performance degrades.

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


CSCtb13395

Symptom    The Alarm Browser does not display some cleared alarms. CTC shows the cleared alarms, but the same alarms are missing from the CTM Alarm Browser.

Conditions   This problem occurs when CTM receives alarms in the wrong sequence, especially when multiple events occur simultaneously.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, resynchronize the alarm information by marking the NEs as Out of Service and then In Service.


CSCtb21147

Symptom    CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.

Conditions   This problem applies to NEs that are equipped with DS3XM_12 cards and provisioned with VT circuits. When CTM receives a DS1 alarm from a VT circuit on a DS3XM_12 card, the "ds1Num" field is always set incorrectly to -1.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, apply an NE alarm profile that suppresses the reporting of VT termination alarms on DS3XM_12 cards. Refer to the NE hardware documentation for the procedure to modify an NE alarm profile.


CSCtb25595

Symptom    Alarm icons display incorrect information in the Domain Explorer tree.

Conditions   This problem occurs only rarely in scalability testing with a simulated network of 4,000 NEs.

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


CSCtb31787

Symptom    CTM R9.0 raises incomplete critical alarms.

Conditions   This problem occurs when a PVC is created between an RPM and PXM.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. After installing the patch, do the following to reduce the severity of incomplete connection alarms:


Step 1 A new flag (REDUCE_INCOMPLETE_CONNECTION_SEVERITY) has been added into /opt/svplus/config/NMServer.conf file. Do one of the following:

Set this flag to enable, to reduce the severity of incomplete connection alarm from Critical to Warning.

Disable this flag. By default, this flag is set to disable.

Step 2 Edit the /opt/svplus/xml/ruledata.xml file and change NewAlarmSev to 2 for NewAlarmCondID 62303.



CSCtb78977

Symptom    The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.

Conditions   This problem occurs when there is a high voltage in an MGX node.

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


CSCtb98230

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

Conditions   When the service modules (PXM45, PXM1E, AXSM, MPSM) run for longer than 440 or 460 days, the trap 60067 is generated for PXM, AXSM, and MPSM cards. When CTM receives the trap, it should display the following alarm in the Alarm Browser:

A major alarm if the card exceeds the low threshold (by default, 440 days)

A critical alarm if the card exceeds the high threshold (by default, 460 days)


Note The trap 60067 should be generated when the low threshold exceeds 430 days; however, due to CSCtd62409, the trap is generated only when the low threshold exceeds 440 days.


Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternatively, reset the service module manually and clear the alarms in the Alarm Browser.


CSCuk58912

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

Conditions   See Symptom.

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


CSCtj92364

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

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

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

Select a smaller set of NEs.

Apply a filter on a shorter time interval.

Circuit and Link Management


CSCeg06273

Symptom    Cannot change the administrative state to Out of Service-Out of Group (OOS_OOG) for VCAT circuits or VCAT member circuits.

Conditions   The OOS_OOG administrative state is supported for VCAT circuits on certain card configurations only. The following constraints apply:

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

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

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


CSCei84860

Symptom    The J1 path trace displays expected and received bytes at the source end for unidirectional circuits.

Conditions   This display problem occurs on all electrical cards. CTM displays the expected bytes, but you cannot set them. This problem does not apply to SONET or SDH optical cards.

Workaround   None.


CSCsb59118

Symptom    When launching the Circuit table at the domain level, the table contains zero entries and the following error message is displayed: "An error occurred while retrieving data from the database."

Conditions   This problem occurs when the network contains a high number of NEs with many circuits.

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


CSCsb95230

Symptom    Creation of an STS-n circuit between E100 cards using CTM fails with the following error:

EID-931: Failed to provision the circuit.
Unable to provision circuit. Circuit provision error.
Unable to create the VLANs for the circuit at <node_name>.

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

Upgrade the ONS 15454 NEs to R5.x.


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

Conditions   See Symptom.

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


CSCsq76213

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

Conditions   Both the high-level circuit trace and circuit trace features have the capability to draw circuit information using different detailed views. For example, the OCHCC circuit type has a related OCH trail circuit type. Both circuits can be displayed in the high-level circuit trace map and the circuit trace map. If you select an OCHCC circuit to be displayed, the graphic map is updated for any events or operations that affect the OCHCC circuit. However, if you change the view from the OCHCC circuit to the related OCH trail circuit, the map does not update. This problem occurs because the graphic window is still registered to receive events that affect the OCHCC circuit, not the OCH trail circuit.

Workaround   None.


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.


CSCsr86376

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

Conditions   This problem occurs when you configure an OTU2_XP card in splitter protection mode and provision 10 GE payload type. The MTU value is updated on the working trunk port, but not on the protected trunk port.

This problem also occurs when an OTU2_XP card is configured in TXP mode and in a Y-cable protection group. The MTU value change on the working client port does not change on the protect client port.

Workaround   Refresh the NE.


CSCsu37386

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

Conditions   This problem occurs when more than one card in the SVLAN circuit is specified as the master card.

Workaround   Set only one card as he master card. For protected SVLAN circuits only, one card should be set as the master card, and protection should be enabled.


CSCsu62916

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

Conditions   This problem occurs when you:

1. Provision two CE-MR-10 cards on two NEs that belong to a network that allows DRI protection (two interconnected rings).

2. From the NE Explorer, configure the CE-MR-10 cards for Automatic mode.

3. Launch the Create Circuit wizard and choose STS-v as the circuit type.

4. In the Create Circuit wizard > Routing Preferences pane, choose Split Routing. The DRI protection type is not listed in the Set Protection for All drop-down list.

Workaround   Use CTC to create the circuit.


CSCsu69633

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

Conditions   An SVLAN circuit with QinQ-Transparent mode is created. If it is deleted, the SVLAN settings are removed, but the QinQ-Transparent settings remain. Also, if you try to change the QinQ setting from Transparent mode to Selective mode, the Transparent SVLAN field is dimmed, but the Transparent SVLAN ID remains instead of having an N/A value.

Workaround   Manually refresh data from the NE.


CSCsu94566

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

Conditions   This problem occurs when LDCC or SDCC links are created between OC192 and OTU2_XP client ports, and between OTU2_XP trunk ports. If you mark the NE as Out of Service and then back In Service, the LDCC or SDCC links are rediscovered as routable links instead of as nonroutable links.

Workaround   None.


CSCsv21284

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

Conditions   In the Ether Ports tab, when the Ingress CoS value is set to 0,..7,Trust and not set to a carrier VLAN, an incorrect CoS value is displayed in the Create SVLAN wizard.

Workaround   None.


CSCsv21500

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

Conditions   This problem occurs only when using CTC to change the Operation value. The Inner SVLAN value in the QinQ tab of GE_XP or 10GE_XP cards is dimmed correctly, but shows an incorrect value.

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


CSCsv23067

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

Conditions   This problem occurs when you add NEs, that are not physically connected, from the CTM Gateway/CORBA into the same subnetwork.

Workaround   From the Control Panel, disable Automatic Grouping.


CSCsv27126

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

Conditions   You can create splitter-protected, optical channel patchcord links between working and protect TXP pairs, and CTM allows you to select 1+1 as the protection type. After the patchcords are created, the Link table shows them with 1+1 protection. However, 1+1 protection is invalid for splitter-protected links; CTM should disallow 1+1 protection.

Workaround   Create separate optical channel patchcords for working and protect trunks that use splitter protection.


CSCsv33266

Symptom    If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.

Conditions   In the Link Utilization table, if you switch spans from CLEAR to FORCE, some of the circuits listed in the table remain in CLEAR status.

Workaround   Use CTC to perform the span switch.


CSCsv36952

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

Conditions   An OCHCC circuit is created between three OTU2_XP cards with the following configuration:

Node A ---- node B ---- node C, where:

Node A—OTU2_XP card is configured in TXP mode.

Node B—OTU2_XP card is configured in Regeneration mode.

Node C—OTU2_XP card is configured in TXP mode.

The OCHCC circuit endpoints are on node A and node C.

The Create Circuit wizard does not set the correct parameters on the OTU2_XP card in Regeneration mode. A G.709/FEC mismatch error occurs. Also, if the port state of the endpoints is IS, the port states of node A and C are also set to IS, while the port state of node B remains OOS. DSBLD breaks the circuit path.

Workaround   Manually set the OTN parameters and port state setting on the card in Regeneration mode (node B).


CSCsv39917

Symptom    Splitter-protected 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 the destination being a terminal node. The circuit is created successfully.


CSCsw17803

Symptom    Open VCAT circuit creation fails, and the PTP information is shown incorrectly as VC4=0.

Conditions   On an SDH node, the open VCAT circuit creation fails and PTP information does not update correctly for the primary destination selection on ONS 15454 SDH nodes and for the secondary destination selection on ONS 15600 SDH nodes.

Workaround   Close and reopen the Create Circuit wizard.


CSCsw25338

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

Conditions   This problem occurs when there is an alarm on ONS 15310 MA DS1 or DS3 cards.

Workaround   None.


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.


CSCsw37547

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

Conditions   This problem occurs when circuits are deleted from CTM or CTC. After 10 hours, the circuits are removed from the database, except under the following conditions:

The NE service is restarted before the 10-hour timeout elapses.

The NE service is not restarted, but the nodes are marked as In Service after 1 hour.

Workaround   None.


CSCsw50865

Symptom    The Circuit Trace window shows a low-order VT circuit span incorrectly as LAP/VAP.

Conditions   This problem occurs when you create a low-order VT LAP/VAP circuit with at least one intermediate ONS 15454 node between the source and destination. In the Create Circuit wizard, select VC LO Aggregation Point as the VC LO Circuit option; select VC LO Grooming Node as the intermediate node; then, click Finish. When you open the Circuit Trace window, the entire span from source to destination is shown incorrectly as LAP/VAP.

Workaround   None.


CSCsw63068

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

Conditions   This problem occurs when you:

1. Create an open-ended VCAT circuit.

2. Open a member circuit.

3. From the Member table, open the High-Level Circuit Trace window.

Workaround   None.


CSCsw99989

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

Conditions   This problem occurs when you:

1. Configure an OTU2_XP card in TXP mode.

2. Provision a SONET/SDH payload type.

A physical SONET/SDH patchcord link cannot be created between the SONET/SDH OTU2_XP client port and a SONET/SDH card port.

Workaround   Use CTC to create the patchcord link.


CSCsw72207

Symptom    The Protection panel shows the wrong name for an OTU2_XP card.

Conditions   This problem occurs when you have an OTU2_XP card with payload configured, and you create a splitter-protection group or a Y-cable protection group. After the protection group is created, the OTU2_XP card is reported in the Protection panel with the wrong name; for example, "XP_4_10G_LINE_CARD" instead of "OTU2_XP" card. This problem also occurs if a GCC or DCC is present.

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


CSCsx22431

Symptom    For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports the correct wavelength value.

Conditions   This problem occurs when there is a circuit on the 58.98 wavelength.

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


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.


CSCsx26527

Symptom    The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer do not exist.

Conditions   This problem occurs when the NE service process is stopped and restarted, and the NEs remain in the In Service state.

Workaround   After the NE service restarts and the NEs have been discovered, mark the NEs associated with the phantom links as Out of Service and then In Service. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsx32065

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

Conditions   This problem occurs only when filtering OCH transport unit links.

Workaround   To view OCH transport unit links, select Layer 3 on the Network Map.


CSCsx44183

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

Conditions   This problem occurs when you try to delete endpoints from the SVLAN table and then manually recreate them using the QinQ/SVLAN settings from NE Explorer. The VLAN circuit is discovered in partial state instead of complete.

Workaround   When creating, editing, or deleting SVLAN endpoints, do only one of the following:

Use the SVLAN wizard available from the SVLAN table.

Manually create, edit, or delete endpoints using the QinQ/SVLAN settings from the NE Explorer.


Note Use only one of these methods. The problem occurs when you make some modifications in the wizard and also manually from the NE Explorer.


If the problem has already occurred and the circuit is discovered in partial state instead of complete state, restart the NE service.


CSCsx47596

Symptom    The CVLAN value does not reset to 0 in the QinQ tab of a GE_XP or 10GE_XP card when changing the Operation value from Add, Translate, or Translate Add to Double Add.

Conditions   This problem occurs only when changing the Operation value to Double Add from the QinQ tab.

Workaround   Set the CVLAN field to 0 before changing the Operation value to Double Add.


CSCsx49646

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

Conditions   This problem occurs in an L2 trunk to trunk circuit. When adding a new drop to a SVLAN on a different NE, the sanity check might fail based on the current circuit source. This occurs if the NE involved in the SVLAN circuit contains 1+1 protected card.

Workaround   Manually provision and create endpoints using the QinQ/SVLAN settings from NE Explorer.


CSCsx56687

Symptom    The SPAN_BS_TABLE database table displays incorrect working and protected values.

Conditions   This problem occurs when circuits are routed over VT tunnels.

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


CSCsx64513

Symptom    A warning message of a possible traffic impact appears when reconfiguring circuits. This warning message should not appear, because reconfiguring circuits does not affect traffic.

Conditions   This message appears after selecting Configuration > Reconfigure Circuit(s) from the Circuit table.

Workaround   Ignore the message. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsy14909

Symptom    A VLAN range cannot be added on a 10GE_XP/GE_XP card.

Conditions   This problem occurs when you try to add a VLAN range from the Create SVLAN wizard or from the NE Explorer > QinQ tab of a 10GE_XP/GE_XP card.

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


CSCsy30294

Symptom    CTM fails to automatically route and create a STS-24c circuit to the 15454-ADM-10G card when entering a value in the Time Slot Restriction field.

Conditions   This problem occurs when provisioning a STS-24c circuit on the 15454-ADM-10G card using the Circuit Creation wizard and entering a value in the Time Slot Restriction field.

Workaround   Manually route the circuit and select the desired time slot for each span. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsy56348

Symptom    Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.

Conditions   This problem occurs under normal conditions.

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


CSCsy84624

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

Conditions   When you perform a circuit trace for a UPSR/SNCP circuit, the UPSR/SNCP selector is missing.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, use the switch commands in the Modify Circuit dialog box.


CSCsy95336

Symptom    CTM fails to reconfigure circuits on release 8.5 NEs.

Conditions   In the Circuit table, when you choose Reconfigure Circuit(s) for a release 8.5 NE, an exception is generated and the circuit is not reconfigured. The same problem applies to CTC release 9.0 when release 8.5 NEs are added. On CTC, the following error message is returned:

EID-2328: An error occurred during the circuit reconfiguration.

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


CSCsz33838

Symptom    Cannot add drops on cards configured in Automatic mode.

Conditions   For CTM R9.0, this problem occurs when creating a drop (for example, on an ONS 15454 SONET CE-MR card) using the Create Drop wizard from the Configuration > Modify Circuit > Drop tab of the Circuit table. The following error appears: "EID-904: Failed to set the circuit end points for circuit creation."

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


CSCsz58653

Symptom    Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.

Conditions   This problem occurs when you use manual routing or constrained routing to create a VT circuit.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, mark the NEs that are involved in the circuit as Out of Service and then In Service.


CSCta00978

Symptom    When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.

Conditions   This problem occurs after entering a value in the CVLAN field of the QinQ Settings pane.

Workaround   From the NE Explorer, delete and recreate the QinQ settings. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCta30560

Symptom    Circuit Wizard fails when the back button is used after changing primary/secondary destinations.

Conditions   This problem occurs when creating an open VCAT circuit using the Circuit Wizard under the following conditions:

1. In the Members Destination pane, specify primary and secondary destinations.

2. Click the Add Destination button.

3. Click Next

4. In the Routing Preferences pane, click Back to return to the Members Destination pane.

5. Change the primary or secondary destination.

6. Click the Add Destination button.

7. Click Next. A CORBA error occurs.

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


CSCta39574

Symptom    When opening the Circuit table from an ONS 15454 node, circuits are not retrieved and a timeout error is displayed.

Conditions   This problem occurs after provisioning 48 STS-1 circuits on a system with a large number of circuits. For example, the problem occurs on a system with around 96,000 circuits present on the CIRCUIT_BS_TBL.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. If a timeout occurs again, increase the client database timeout period. Refer to section K.6.2, "Database Timeout Occurs" in Appendix K of the Cisco Transport Manager Release 9.0 User Guide.


CSCta73380

Symptom    Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.

Conditions   This problem occurs after adjusting the zoom level in the map view within the Create Circuit wizard.

Workaround   None.


CSCta95729

Symptom    NEs cannot be moved to the bottom right corner of the Create Circuit wizard map view.

Conditions   This problem occurs after adjusting the zoom level in the map view within the Create Circuit wizard.

Workaround   None.


CSCtb30304

Symptom    An error message (EID-315) appears after selecting Edit > Find to search for a circuit:

EID-315 Unable to Retrieve Circuit after Provisioning

Conditions   This problem occurs when searching for a provisioned circuit through the Edit > Find.

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


CSCtb73160

Symptom    The Circuit table does not display port names for ONS 15454 ANSI DS1_E1_56 and OC192_XFP cards.

Conditions   This problem occurs with circuits created between DS1_E1_56 or OC192_XPF cards.

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


CSCtb75511

Symptom    Adding a new member to a VCAT circuit fails. After clicking Next from the Route Constraints pane of the Add Member wizard, the Routing Preferences pane appears instead of the Review Route pane.

Conditions   This problem occurs if the following options in the Routing Preferences pane are checked:

Route Automatically

Using Required Nodes/Links

Review Route Before Creation

View Route Textual

Workaround   Select the View Route Graphical or View Route Graphical Enhanced options (instead of View Route Textual) in the Routing Preference pane.


CSCtd31222

Symptom    Circuits without a destination are not displayed in the Circuit table.

Conditions   This problem occurs when open-ended VCAT circuits and partial circuits with out-of-service destination nodes are present on the network.

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


CSCtd36677

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

Conditions   This problem occurs when there are VCAT circuits in the network.

Workaround   None.


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.


CSCtc67375

Symptom    OCHCC circuits are not shown when the Circuit table is launched from a link.

Conditions   This problem occurs under the following conditions:

1. Open the network map.

2. Right-click an OTS link and select the Circuit table. Only OHC-NC and OCH-Trail Tunnels are shown.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, you can find the OCHCC circuit by checking the OCH trail tunnel source and destination.


CSCtl06435

Symptom    The network admin user cannot modify or delete OCHNC circuits. An access violation error is shown.

Conditions   The problem occurs when a network admin tries to modify OCHNC circuits in CTM.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, you can log in as SuperUser.

User Management


CSCin81532

Symptom    When using a Retrieve, Maintenance, or Provisioning user account for CTM server-to-NE connectivity, CTM allows NE user administration operations to be performed on R4.1.4 NEs. User administration should be allowed only for Superuser accounts.

Conditions   This problem applies only to R4.1.4 NEs and is fixed in later NE releases.

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


CSCtg92011

Symptom    Customer request to change the minimum length of CTM username from 6 to 3 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.

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


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.

Data Services


CSCsg21079

Symptom    Cannot preprovision the port name of the RAN-SVC card in CTM. CTM does not allow you to change or view the port name.

Conditions   This problem occurs all the time.

Workaround   Use CTC to provision the cards.


CSCsg50514

Symptom    It takes a long time to create an 802.17 RPR Layer 2 topology.

Conditions   This problem occurs in a GNE/ENE setup when the RPR contains multiple protected ML cards. It might take CTM as long as 30 minutes to create the 802.17 RPR.

Workaround   None.


CSCsg51351

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

Conditions   This problem occurs all the time 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:

Configure the Gigabit Ethernet ports using the Cisco IOS CLI.

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

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


CSCsw49153

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

Conditions   This problem occurs when the circuits do not have trunk ports belonging to the selected card.

Workaround   Start the SVLAN table from the node view.


CSCta61660

Symptom    ENE/GNE role changes on the network cause unstable NE service and node connectivity issues.

Conditions   This problem occurs when there are incorrect SNMP community strings that increase in length with each role change between an ENE and GNE node. The following error might appear:

EID-2017: Exception: %01 for NE: %02 while %03.ORA-12899: value too large for column 
"CTMANAGER"."NE_INFO_TABLE"."NESNMPCOMMSTRING" (actual: 277, maximum: 256)

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


CSCta69424

Symptom    If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the CTM client freezes.

Conditions   This problem occurs when SVLAN discovery begins while the NE service contains at least one NE release earlier than 9.0. For example, if the NE service contains an NE release 8.0 and an NE release 9.0 and SVLAN discovery begins, the CTM client freezes.

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


CSCte39776

Symptom    The CTM NE Description field does not match the NE description in CTC.

Conditions   This problem occurs on NEs with software versions 8.0 or later.

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


CSCtg56522

Symptom    Cannot add CTC-based NEs to a CTC-based network service. When you use the Add NE wizard, the CTM server does not manage the new NE, and the NE is not shown in the Domain Explorer.

Conditions   This problem occurs when the network partition contains 500 or more NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, create a new network partition and move all NEs of the same type into the same network partition. For example, if there is a mix of ONS 15454 and ONS 15305 NEs, move all ONS 15454 NEs to the new partition.


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.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, restart the NE service and configure the SNMP destination correctly on the NE with the CTM server IP address.


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


CSCti61844

Symptom    The Create Layer 2 Topology wizard or the Add/Remove Card wizard freezes for several minutes, and then proceeds correctly.

Conditions   This problem occurs in a high-end meshed network with MSPP NEs when you:

1. Launch the Create Layer 2 Topology wizard or the Add/Remove Card wizard from the Domain Explorer or from the L2 Topology table.

2. Click the first Next button in the wizard.

The wizard freezes for several minutes.

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


CSCti72327

Symptom    L2 topology resynchronization takes too long when there are many VLANs.

Conditions   This problem occurs when you configure many VLANs on an L2 topology, and then you do one of the following:

Mark the NEs involved in the L2 topology as Out of Service and then In Service.

Configure a new VLAN in the same L2 topology.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, wait until the Layer 2 Service Resync Status changes from "In Progress" to "Complete."


CSCtj21034

Symptom    The remote debug console (RDC) has no commands for Layer 2 cache management.

Conditions   This problem occurs when you open the RDC with the command telnet localhost <9600 + NE-service-number>. If you use the help command to show all RDC commands, there are no commands for Layer 2 cache management.

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


CSCtk13431

Symptom    High CPU usage after bulk circuit creation.

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

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


CSCsc61181

Symptom    MGX Voice Gateway applications cannot be launched from the CTM Domain Explorer.

Conditions   If you install the CTM client in a location that has spaces in the directory path, the MGX Voice Gateway applications cannot be launched from the CTM Domain Explorer.

For example, D:\Program Files\ctm has a space between Program and Files. Installing in this location causes the Symptom described.

Workaround   Install the CTM client in the default directory location, or choose a target directory path without spaces.


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.


CSCsu74133

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

Conditions   This problem might occur under one of the following conditions:

The IPv6 address of a GNE is changed on the network.

A LAN connection fails for an IPv6 GNE.

Workaround   Refresh the data on the Domain Explorer or close and reopen CTM.


CSCsv45598

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

Conditions   See Symptom.

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


CSCsv88769

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

Conditions   This problem occurs when you:

1. Select an NE in the Domain Explorer. 

2. From the Network Element Properties pane, select the NE Authentication tab.

3. In the CTM Server - SNMP Connection area, select SNMPv3 as the SNMP protocol.

4. Enter invalid values and click Save. CTM accepts the invalid entries.

Workaround   Refresh the Domain Explorer window to restore the saved values.


CSCsw40134

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

Conditions   This problem was observed in a network that uses simulated NEs. This problem was not observed with real NEs.

Workaround   From the CTM client, remove the duplicated groups.


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.


CSCsx50111

Symptom    ENE nodes configured in Secure IP mode do not reconnect to CTM after the node is marked as Out of Service and then In Service.

Conditions   This problem occurs in a GNE/ENE network with ENEs configured in Secure IP mode.

Workaround   Do the following:

1. Mark the ENE as Out of Service.

2. From the Domain Explorer > Address tab, modify the IP address.

3. Mark the ENE as In Service.

Repeat these steps each time the NE goes through an Out of Service/In Service cycle.


CSCtb14476

Symptom    In the Domain Explorer > Management Domain Properties pane > Status tab > NE Count by Operational State field, the "NEs in Initialization" counter is always 0 (zero).

Conditions   When NEs transition to the Initialization discovery state, the "NEs in Initialization" counter does not update.

Workaround   None.


CSCtc35552

Symptom    The discovery state of an NE is incorrect.

Conditions   This problem may occur in large networks when an NE is discovered.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, mark the NE Out of Service and then In Service. You may need to do this multiple times before the NE discovery state is correct.


CSCtc45424

Symptom    The ONS 15305 NE Service restarts due to lack of memory.

Conditions   This problem occurs when more than 500 NEs are connected to the same ONS 15305 NE service.

Workaround   None.


CSCth40549

Symptom    A confirmation message appears for no apparent reason when selecting a node from the Domain Explorer.

Conditions   The problem occurs when the NE Description field has been entered within CTC and contains carriage return characters.

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


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.0 Patch or Service Pack.


CSCtl83275

Symptom    The CTM client freezes after some time.

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

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

NE Explorer


CSCed15994

Symptom    Setting the Routing Information Protocol (RIP) metric to zero does not generate an error message.

Conditions   In the ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE Explorer > Network tab > RIP subtab, if you change the default RIP metric to 0 (zero), the value is not accepted. There is no error message to inform you that the change is not accepted.

Workaround   Zero is not a valid value for the RIP metric. Specify a different value.


CSCef65097

Symptom    The NE Explorer does not refresh the Secure Config Mode value after a mode change.

Conditions   This problem occurs under the following conditions:

1. Select an NE with a TCC2 card and insert a TCC2P card in the standby slot. Wait for the TCC2P card to synchronize with the active TCC2 card and become standby.

2. Remove the TCC2 card.

3. Select the NE and launch the NE Explorer. Click the Network tab > Secure Config Mode subtab.

4. Change to secure config mode. Provide the IP address and netmask. The TCC2P card reboots. After several minutes, CTM re-establishes connectivity to the NE and synchronizes the NE data.

5. Return to the NE Explorer window and verify the NE connectivity. The cursor in the NE Explorer window remains an hourglass icon, and the data does not refresh.

Workaround   Close and reopen the NE Explorer.


CSCeh45510

Symptom    Clicking the Apply button after modifying the SNMP User Datagram Protocol (UDP) port does not save the modified value.

Conditions   If you modify the SNMP UDP port value and then click Apply, the change is not saved.

Workaround   Click any other cell in the table; then, click the Apply button.


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.


CSCin62527

Symptom    The default RIP summary address is not created when activating RIP from CTM.

Conditions   If you launch the NE Explorer, click the Network tab > RIP subtab, check the RIP Active check box, and click Apply, no summary address is created.

Workaround   Manually create a default RIP address after activating RIP from CTM. Alternately, use CTC to activate RIP so that the default RIP address is created automatically.


CSCin62975

Symptom    No range address is created when enabling Open Shortest Path First (OSPF) on a LAN from CTM.

Conditions   See Symptom.

Workaround   In CTM, manually provision the OSPF area range address for the respective range area IDs. In the NE Explorer, choose Network > OSPF Area Range; then, click the Create button. Alternately, enable OSPF from CTC so that the range address is created when OSPF is enabled.


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.


CSCse87505

Symptom    In the NE Explorer, the SSXC card is shown as CXC for ONS 15600 SONET R7.2 NEs.

Conditions   This problem applies to ONS 15600 SONET R7.2 NEs.

Workaround   None.


CSCse88833

Symptom    The Customer Info table is blank for XTC cards on ONS 15327 R4.1.4 and R4.1.8 NEs.

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 the 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. Select an ONS 15600 NE from the NE Explorer.

2. Open the Ether Line tab.

3. Change the AINS Soak Count Down value.

4. Click Apply. The values revert back 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.


CSCsr25541

Symptom    The IPv6 address format is not reported correctly.

Conditions   This problem occurs when you:

1. Open the NE Explorer and select an NE.

2. Click the Network tab > FTP Host subtab.

3. Click Create.

4. In the wizard, enter an IPv6 address in the following format: "value::" (for example, 10:25:65:ee:aefb::).

5. Click OK.

On the FTP host subtab, the IPv6 address is reported incorrectly as "0.0.0.0." CTC reports the IPv6 address correctly.

Workaround   None.


CSCsr43528

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

Conditions   This problem occurs when you do one of the following:

Open the Broadband Ports tab of a CTX card and create an EC1 port. The new EC1 port is listed in the EC1 and Optical tabs.

Create a PPM port from the Pluggable Provisioning tab. The new PPM port is listed in the EC1 and Optical tabs.

Workaround   Click Cancel.


CSCsr71236

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

Conditions   This problem occurs when you:

1. Open the NE Explorer.

2. Select a PSM card.

3. Click the Protection tab > Protection Groups subtab > Operations subtab.

4. In the Protection Group Details area, click Force or Clear. The command executes, but the port status does not update.

Workaround   Close and open the NE Explorer.


CSCsv38910

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

Conditions   This problem occurs on preprovisioned DS3XM_12 cards. After clicking Reset to Defaults from the Line Thresh 15 Min or 1 Day subtabs, incorrect default values are displayed.

Workaround   Use CTC to reset the default values.


CSCsv76358

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

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

Workaround   Refresh the NE or mark the NE as Out of Service and then In Service.


CSCsv97145

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

Conditions   This problem occurs after creating HO or LO VC circuits on a CTX card. CTC shows the correct VC values.

Workaround   None.


CSCsw40388

Symptom    A section trace cannot be configured on client ports.

Conditions   This problem occurs under the following conditions:

1. Configure the OTU2_XP card for TXP mode.

2. Configure the OC192 payload type on all ports.

3. From the Line tab > Section Trace subtab, only trunk ports 3 and 4 are available for a section trace. You cannot enable a section trace on client ports 1 and 2.

Workaround   None.


CSCsw44603

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

Conditions   This problem occurs when you:

1. Create a high-order circuit on an E1 port on an E1_63_E3_DS3_3 card.

2. Open the E1 tab. The VC4 Threshold tab missing. You cannot retrieve PM data at that port for the VC4 circuit.

Workaround   Use CTC.


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.


CSCsw63014

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

Conditions   This problem occurs after creating 1+1 port protection on an ONS 15310 MA card.

Workaround   Refresh the NE.


CSCsw68470

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

Conditions   This problem occurs when modifying an existing LDCC:

1. From the Domain Explorer, select a CTC-based NE with an existing LDCC termination.

2. Select the LDCC and click Edit.

3. From the Layer3 (Layer2) Config tab, change the current configuration to one of the following:

IP (PPP)

OSI and IP (PPP)

4. Click OK to apply the changes.

5. From the NE Explorer, select the DCC/LDCC tab. The modifications are not reflected in the DCC/LDCC tab.

Workaround   Use CTC to modify the LDCC.


CSCsw69548

Symptom    You cannot save an SVLAN name that contains commas.

Conditions   See Symptom.

Workaround   Do not include commas in VLAN names.


CSCsx17951

Symptom    ONS 15454 OCHxx circuits are not available from the Edit > Find > Object Type > Metro DWDM Circuits > Circuit Type drop-down list. Instead, the OCHxx circuits are listed under the SONET Circuits > Circuit Type drop-down list.

Conditions   This problem occurs if you use the Find feature in the NE Explorer to search for OCHxx circuits from the Metro DWDM Circuits > Circuit Type drop-down list.

Workaround   Select Edit > Find > Object Type > SONET Circuits. From the Circuit Type drop-down list, select the appropriate OCHxx circuit.


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 some changes to the VLAN database; for example, adding or deleting some 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.


CSCta44804

Symptom    You cannot change the LAN configuration on a multishelf R9.0 NE from the CTM GUI.

Conditions   This problem occurs when you try to change the LAN Config field from the NE Explorer (General tab > Multishelf Config subtab). Although no error message is displayed, the parameter does not change on the node.

Workaround   Use CTC to change the LAN configuration.


CSCsz43543

Symptom    Clicking the Help tool from the NE Explorer does not work. Also, the Help menu lists "Pseudo CLI" instead of "Current Window."

Conditions   For 8.0 and 8.5 NEs, the online help does not appear after clicking the Help tool from the NE Explorer.

For 9.0 NEs, the Pseudo CLI window, instead of the online help, appears after clicking the Help tool from the NE Explorer.

Workaround   You can launch the online help by doing one of the following:

Click the Help button within the dialog box.

Access the online help from another window; for example, the Domain Explorer.


CSCtb65065

Symptom    In the NE Explorer for the ONS 15310 MA or the ONS 15454 MSPP, the first time you select an optical card, the Transceiver tab is blank.

Conditions   This problem applies to OC192_XFP, MRC_12, MRC_25G_4, and CTX2500 cards that contain at least one small form factor pluggable (SFP).

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, toggle between the Auto Laser Shutdown tab and the Transceiver tab. When you toggle back to the Transceiver tab, the correct card SFP data is displayed.


CSCtb88190

Symptom    CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs with an Unavailable status.

Conditions   This problem occurs with a GNE-ENE network containing GNEs with version 9.0.x. This problem is likely to occur with networks with more than 50 NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, revert GNE 9.0.x versions shown as ENEs to version 8.5.x.


CSCtc19328

Symptom    The CTM Domain Explorer window freezes and you are unable to select other NEs.

Conditions   This problem usually occurs when there is a large number of NEs in different groups.

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


CSCtc70085

Symptom    From the CTM client, you cannot launch CTC on release 9.0.x ENEs.

Conditions   This problem is likely to occur when ENEs are part of a network with more than 30 NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 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.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, refresh data from the server.

Network Map


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.

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.


CSCsb43019

Symptom    CTM does not report PM values at time 00:00 for an ONS 1580x card.

Conditions   This problem occurs when the connection to the NE is lost, the offline time period includes 00:00, and PM retrieval is enabled for more than one card.

Workaround   Retrieve PM values for one card only.


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 (Related caveat ID: CSCsc61537)

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;
 
   

CSCsq84105

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

Conditions   This problem occurs when you retrieve historical PM data for an ONS 15310 MA SDH CE-MR card. The Ethernet category shows N/A for ETHERSTATSTXFIFOOVERFLOWEVENTS.

Workaround   None.


CSCsu41715

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

Conditions   This problem occurs on 2.5G_DM cards configured as FG_GE. If you use the 15-minute or 1-day filter to run a physical PM query, the Physical PM table shows incorrect values for Min TX Power, Avg TX Power, and Max TX Power.

Workaround   None.


CSCsu59134

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

Conditions   This problem occurs when you:

1. Create an STS-1 circuit on an Ethernet port of 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.


CSCsu90217

Symptom    Continuous 15-minute and 1-day PM lost bucket alarms occur and do not clear.

Conditions   This problem occurs under normal CTM operation.

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


CSCsw69115

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

Conditions   This problem occurs when you disable or collect invalid OTN counters.

Workaround   None.


CSCsw69581

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

Conditions   This problem occurs when the CTM server and managed NE are set to different time zones.

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


CSCsw72382

Symptom    The getTCATPParams API shows SONET thresholds for unsupported parameters.

Conditions   This problem occurs when you:

1. Configure an OTU2_XP card in TXP mode.

2. Configure the SONET payload type on ports 1 to 3. The getTCATPParams API shows thresholds for unsupported parameters; for example, PSC and PSD.

Workaround   None.


CSCsw79346

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

Conditions   This problem occurs when you:

1. Create a VC3 circuit between an E3 interface on electrical cards of two ONS 15310 MA SDH nodes.

2. Create a VC12 circuit between the same ONS 15310 MA SDH nodes and cards as in Step 1.

3. Launch the real-time PM table on SDH LO VC3.

Workaround   None.


CSCsw91974

Symptom    In a large network of GNEs and ENEs, CTM fails to collect PM data.

Conditions   This problem occurs when each PM service instance manages a large network of GNEs and ENEs, and each GNE manages more than 10 ENEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. After installing the patch, you must complete the following steps to enable a designated SOCKS server (DSS) on the CTC-based PM services:


Step 1 Complete the following substeps to enable a DSS on the NE service:

a. From the Domain Explorer, open the Control Panel.

b. Select the NE service where you want to enable a DSS.

c. In the Status tab, check the Enable Designated Socks Server check box; then, click Save.

Step 2 In the CTM Control Panel, stop all CTC-based PM services.

Step 3 Log into the CTM server workstation as the root user.

Step 4 Go to the /opt/CiscoTransportManagerServer/bin directory and make a backup copy of the jpm.sh file.

Step 5 Use vi to edit the jpm.sh file and add the following property:

-Dctm.pm.dssPMPollerEnabled=true \
 
   

Step 6 (Optional) Add the following property to the jpm.sh file:

-Dctm.pm.refresh.interval=X \
 
   

where X is the number of seconds after which the PM services reload the DSS list. The default value is 600 seconds. Do not add any blank lines or spaces after the slash (\).

Step 7 Save the changes and exit.

Step 8 In the CTM Control Panel, restart the CTC-based PM services.



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. In fact, only the counter UAS-SM and UAS-PM collect performance data while all other counters are shown as N/A.

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


CSCsz83568

Symptom    The following null pointer exception appears in the pmservice.log file for MRC-12 cards:

[com.cisco.stardm.service.pm.ons15454.ONS15454DBWriter,DB WriterWorker#18] NE UMSWMIR030 : 
VT1-5-10-1-4-7-4-10 - module Type: 219 at shelf 1 and slot 5 raised NullPointerException 
in parse() method. 
java.lang.NullPointerException

Conditions   This problem occurs on MRC-12 cards where VT circuits are provisioned.

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


CSCtc10079

Symptom    A lost PM bucket alarm cannot be cleared manually.

Conditions   This problem occurs when you select an NE that has an outstanding lost PM bucket alarm, and acknowledge that alarm. If you try to clear the alarm manually, the alarm does not clear.

Workaround   None.


CSCtd49099

Symptom    Occasionally, Ethernet PM data is not collected for historical 15-minute and 1-day intervals.

Conditions   This problem applies to NEs with ML or MSTP cards; for example, GE_XP, 10GE_XP, and so on.

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


CSCte98243

Symptom    Cannot clear PM counters for Ethernet real-time PM data on CE-MR-10 cards.

Conditions   See Symptom.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, use CTC to clear the PM counters.


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.


CSCtn93251

Symptom    PM table shows a wrong interface identification for 15454-ETSI NEs.

Conditions   This problem occurs when PM data is retrieved on an HO virtual container type with VC4-xC#n circuits.

Workaround   None.

Miscellaneous


CSCeg57848

Symptom    The Equipment Inventory table shows TCC2P as TCC2.

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

Workaround   None.


CSCin94007

Symptom    CTM shows a blank password.

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

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


CSCsb29625

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

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

Workaround   None.


CSCsc61618

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

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

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

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


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

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

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

Step 4 Change the filename gcoutput to a new name.

Step 5 Save and close the file.

Step 6 Start a new client session as usual.


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


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

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

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

Step 4 Change the filename gcoutput to a new name.

Step 5 Save and close the file.

Step 6 Start a new client session as usual.



CSCsc67149

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

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

Workaround   None.


CSCsc99811

Symptom    A node name change is not reflected in the CTM client.

Conditions   This problem occurs when the name change is performed from CTM GateWay/TL1.

Workaround   Wait for the next synchronization, or force a synchronization from the NE.


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.


CSCsi25547

Symptom    NEs are added successfully, but they do not appear in the Domain Explorer and cannot be located using the Find feature. Moreover, if an NE is moved from one group to another, the NE disappears from the Domain Explorer.

Conditions   This problem occurs when the Domain Explorer contains thousands of NEs and the NEs are frequently dragged and dropped from one group to another over a very long period of time.

Workaround   None. The fix for the CSCsi26713 does not fix CSCsi25547, but it extends the time during which CTM works correctly.


CSCsj97000

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

Conditions   This problem occurs when you preprovision cards that have too many ports; for example, DS1_84_DS3_EC1_2 and DS1_E1_56 cards that contain too many ports.

Workaround   None.


CSCsk34470

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

Conditions   This problem occurs when you:

1. Open the ONS 15310 CL NE Explorer and select a CTX card.

2. Select the Broadband Ports tab and create a new DS3 or EC1 broadband port.

3. Select the DS3 tab for the DS3 port or EC1 tab for the EC1 port and then select the subtabs. The line parameters are empty.

Workaround   Refresh data from the CTM server to refresh the line parameter information.


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.


CSCsl26108

Symptom    CTM performs slowly while connecting, discovering, and resynchronizing CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.

Conditions   This problem rarely occurs and is caused by XML messages that are formatted incorrectly. It does not affect any CTM functionality, but impacts CTM performance.

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


CSCsr11587

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

Conditions   This problem occurs when a 10GE_XP card is preprovisioned on an SDH NE running release 9.0 software.

Workaround   None.


CSCsr22988

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

Conditions   This problem occurs when you:

1. Open the Bulk FTP Configuration wizard and click Add Row.

2. Enter invalid parameters; for example, the wrong IP address or an incorrect mask value.

3. Click Next. No errors are displayed. The wizard continues to schedule the job.

Workaround   None.


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.


CSCsu52555

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

Conditions   This problem occurs when you open the VLAN Database Profile Management wizard, select the To File option, and enter the filename of an existing file in the Save VLAN pane. No errors or warning messages appear and you are allowed to finish the remaining steps in the wizard.

Workaround   None.


CSCsv44984

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

Conditions   If an IPv6 address is entered for an IPv6 NE in the Bulk FTP Configuration wizard, the wizard continues to schedule the job.

Workaround   None.


CSCsv57817

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

Conditions   This problem occurs when you:

1. Disable automatic subnetwork grouping in the Control Panel.

2. In the Subnetwork Explorer, create two network partitions: one for SONET NEs, and one for SDH NEs.

3. Create an empty subnetwork in the SDH network partition.

4. Select the empty subnetwork and in the properties pane, try to change the network partition to the SONET network partition. The operation fails with an error message.

5. In the Subnetwork Explorer tree, drag and drop the same subnetwork from the SDH network partition to the SONET network partition. The operation succeeds.

The operation should succeed under both scenarios.

Workaround   None.


CSCsw22308

Symptom    VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with incorrect numbers, making it impossible to tell which VT the PM data is for.

Conditions   For VT1.5 PM data for DS3XM-12 cards, the numbers in the Physical Location and Interface columns are jumbled, making it impossible to tell which VT PM you are looking at on a given line. This problem occurs with CTC releases 6.0.1, 7.0.0, 7.2.2, and 8.0.

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


CSCsw79060

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

Conditions   This problem appears when you:

1. Launch the SNMPv3 wizard.

2. Follow instructions and complete the steps in the wizard.

3. Close the wizard.

4. Lock and unlock the client. The SNMPv3 wizard reopens.

Workaround   None.


CSCsx03216

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

Conditions   This problem occurs when you save or delete an SVLAN database that contains 4093 SVLANs on at least two GE_XP/10GE_XP cards.

Workaround   Save the SVLAN databases one at a time on a single GE_XP/10GE_XP card.


CSCsx38249

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

Conditions   This problem occurs when you do the following:

1. In the Domain Explorer, Subnetwork Explorer, or Network Map window, choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > VLAN DB Profile Management. The VLAN Database Profile Management wizard opens.

1. Select From NE or From File to load an SVLAN profile.

2. Click Next.

3. Select Delete Selected Row to delete an existing SVLAN profile.

4. Click Next.

5. In the Save VLAN pane, select To File to save the SVLAN profile.

6. Load the SVLAN profile from the file you saved in Step 5. The SVLAN profile you deleted still exists.

Workaround   Do one of the following:

Manually delete the row from the file.

Save the modified profile on the NE first, load it, and then in the Save VLAN pane, select To File to save the SVLAN profile.


CSCsx44115

Symptom    The CTM server does not send SNMP traps or gets to IPv6 destinations. The following problems occur:

CTM does not retrieve Ethernet CoS PM data on ML cards from IPv6 NEs.

The SNMP gateway does not forward traps to IPv6 hosts.

Conditions   This problem occurs with a dual-stack CTM server managing IPv6 networks.

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


CSCsx52287

Symptom    Event notification is not audible.

Conditions   After multiple reconfigurations of "Play Audible Notification For" in the User Preferences dialog box, the sound notification might stop working, although the CTM client generates a notification dialog box when new events arrive. This problem is not always reproducible.

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


CSCsz75781

Symptom    The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM cards in the network.

Conditions   This problem occurs while provisioning a line card; for example, an OC-3 line card.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, disable the Error level for the Error Log. Note, however, that disabling errors logged with the Error level will prevent other valid errors—including warning and debug errors—from appearing in the Error Log.


CSCsz96763

Symptom    In the Service Up Time log, clicking the Stopped At column does not sort the table.

Conditions   This problem occurs when you select Administration > Service Up Time Log, and try to sort the table by clicking the top of the Stopped At column.

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


CSCtb59923

Symptom    Several exceptions appear in the CTM network service log.

Conditions   This occurs when SNMP is configured on LNE Nodes with Layer 2 cards.

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


CSCtb67646

Symptom    The CTM client freezes and does not respond to user commands.

Conditions   This problem was observed on a high-end setup with 4,000 optical NEs. After the entire managed network was disconnected (that is, all 4,000 NEs were disconnected), the CTM client froze. This problem cannot be reproduced consistently.

Workaround   If the CTM client is running on Windows, use the Task Manager to stop the CTM client Java process manually. If the CTM client is running on Solaris, enter the kill -9 command to stop the CTM client Java process.


CSCtb83002

Symptom    The CTM client freezes and does not respond to user commands.

Conditions   This problem was observed on a high-end setup with 4,000 optical NEs. After the entire managed network was added using CORBA (that is, all 4,000 NEs were added in bulk using CORBA), the CTM client froze. This problem cannot be reproduced consistently.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, if the CTM client is running on Windows, use the Task Manager to stop the CTM client Java process manually. If the CTM client is running on Solaris, enter the kill -9 command to stop the CTM client Java process.


CSCtb85880 (Related caveat ID: CSCtc20552)

Symptom    After performing NE software upgrades, the SM service restarts NE services.

Conditions   This problem occurs if the Java Virtual Machine (JVM) PermGen memory space is full. The NE service logs contain a PermGen OutOfMemoryException.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, increase PermGen memory by modifying the /opt/CiscoTransportManagerServer/bin/ jnet.sh file, as follows:

Replace -XX:MaxPermSize=128m with -XX:MaxPermSize=256m

Replace -XX:PermSize=128m with -XX:PermSize=256m

Add -XX:+CMSPermGenSweepingEnabled

Add -XX:+CMSClassUnloadingEnabled


CSCtd26328

Symptom    SNMP rows are not displayed in the SNMP tab when more than one relay is present.

Conditions   This problem occurs when creating an SNMP trap destination with more than one relay {A|B|C} IP address on NE releases earlier than 9.0.

Workaround   None.


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.


CSCti23042

Symptom    Changes to the SNMP trap destination fields are not applied and CTM does not display an error message.

Conditions   This problem occurs when editing SNMP trap destination fields from the SNMP subtab as follows:

1. From the Domain Explorer, select an NE with an existing SNMP trap destination.

2. Choose Configuration > NE Explorer.

3. In the node properties pane, click the Network tab; then click the SNMP subtab.

4. Edit some fields.

5. Click Apply. CTM displays a confirmation message.

6. Check CTC. The new SNMP trap destination values are not updated.

Workaround   Do one of the following:

From CTM, delete the SNMP trap destination row and create it again.

Use CTC to edit the SNMP trap destination values.

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.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, restart the NE service from the Control Panel.


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.


CSCsr48358

Symptom    The prune_ne_ipaddress script does not work with IPv6 addresses.

Conditions   This problem applies to NEs that are added to CTM with an IPv6 address.

Workaround   Provide an IPv4 address when running the prune_ne_ipaddress script. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsv58015

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

Conditions   This problem occurs when restarting the NE service process of an unmanaged NE. In the Domain Explorer, the NE is shown as unreachable, while the Control Panel shows the NE as reachable.

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


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 with the database backup procedure.


CSCsv86239

Symptom    A database export does not update the database tables correctly.

Conditions   This problem occurs when using the CLI to perform a CTM database export.

Workaround   None. This problem has no impact on the CTM system.


CSCsw68952

Symptom    A database export fails with the following error:

ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.

Conditions   This problem might occur due to certain content in some tables. For example, literal IDs associated with circuits or NEs, or special characters in descriptions might cause the database export to fail.

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

If Java is enabled, confirm that DBMS_JAVA synonyms and packages are created and valid. As SYSDBA, run the $ORACLE_HOME/javavm/install/initdbj.sql script to create the required packages.

If Java is disabled, run the $ORACLE_HOME/javavm/install/rmjvm.sql script to remove Java-related objects.


CSCsx23360

Symptom    An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle Enterprise Manager or the Alert Log.

Conditions   This problem occurs during the first database export.

Workaround   Manually change the privilege to PUBLIC. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsx81985

Symptom    During intensive database usage, archive log pruning does not efficiently remove files from the /db05 directory.

Conditions   This problem occurs when there is a high volume of database activity. For example, this problem might occur when removing 200+ NEs that contain a large amount of historical performance monitoring data.

Workaround   Manually move the arc files from /db05/CTM to /ctm_backup. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsz26474

Symptom    The Service Manager (SMService) starts a higher number of ONS 15454 network services than is expected. If the number of network services is too high, the services start and shut down continuously, which degrades the overall performance of the CTM server.

Conditions   This problem occurs when a single network partition contains more than 500 NEs of the same type; for example, more than 500 ONS 15454 SONET NEs. The CTM GUI prevents you from adding more than 500 NEs to a single network partition. However, certain scenarios—such as the automatic discovery of NEs or a database upgrade from an earlier release—could cause the CTM server to exhibit this condition.

Workaround   Delete NEs from the network partition until the partition contains 500 or fewer NEs.


CSCsz63889

Symptom    Sometimes memory backups fail for CTC-based release 6.0.1 NEs.

Conditions   This problem occurs when the NE security ticket is negative.

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


CSCsz71168

Symptom    A database import causes incorrect index error messages.

Conditions   This problem occurs if you perform a database export from one server and a database import in another server (or the same server) after a new CTM installation.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, you can manually rebuild indexes after the database import completes with errors. Enter the following command:

# alter index <INDEX_NAME> rebuild;
 
   

CSCta23414

Symptom    When installing a CTM patch, the following error message is displayed in the log:

The database has been imported, executing security_config.sql
ERROR: ORA-01031: insufficient privileges SP2-0640: Not connected

Consequently, the security_config.sql script does not run and some permissions in the CTM database are incorrect. (The permissions are available to public instead of ctmanager.)

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

The configuration is dual server; that is, the CTM server and database are installed on separate workstations.

The CTM database is exported using the CTM R9.0.0.507 (FCS) build, and is imported later.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, log into the CTM database workstation and run the /opt/CiscoTransportManagerServer/bin/security_config.sql script as sysdba. You do not have to shut down the CTM server while running this script.


CSCta30985

Symptom    A memory leak occurs on the CTM server because of zombie LWP creation when a user is in locked state.

Conditions   See Symptom.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, disable user lockout in the Control Panel > Security Properties pane > CTM Security tab > Client Inactivity Timer Settings area.


CSCta35142

Symptom    CTM restarts and the core_pmon.log file reports an Oracle error.

Conditions   This problem occurs in a high-end CTM configuration on a T2 server. CTM shuts down and restarts. The core_pmon.log file reports the following error: "Oracle not running, Shutting Down CTM Server." This problem rarely occurs.

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


CSCta42487 (Related caveat ID: CSCtf17428)

Symptom    The SM service disconnects during a JMOCO hello message, and the CTM server restarts.

Conditions   This problem occurs infrequently during stress and soak testing on a T2 server in a high-end setup.

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


CSCta69019

Symptom    The ctms-stop and ctms-abort scripts do not work when Oracle is down.

Conditions   This problem occurs when Oracle is down. The ctms-stop and ctms-abort scripts contain an incorrect check. The scripts assume that Oracle is always up. Note that this problem rarely occurs, because the CTM server does not work correctly if Oracle is down.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, complete the following steps:


Step 1 Enter the showctm command to display the CTM processes.

Step 2 Kill the CTM server process with the lowest process ID.

Step 3 Kill the CTM server process with the highest process ID.

Step 4 Kill the SM service.

Step 5 Start Oracle.

Step 6 Enter the ctms-start command to restart CTM.



CSCtb01411

Symptom    The network services and network service instances cannot be stopped or started from the Control Panel. The SMService-0-<timestamp>.log file shows the following error message:

EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too 
many open files

Conditions   Although the issue is not systematic, it might occur when the CTM server has been running for a long time.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, enter the commands ctms-stop and ctms-start to restart the CTM server. Note, however, that the problem can occur again after a long time.


CSCtb28839

Symptom    CTM does not discover the entire network, and NEs remain in loss of communication (LOC) state with the following error:

OutOfMemoryError: PermGen space:

Conditions   This problem might occur when you upgrade from CTM R8.5 to CTM R9.0.

Workaround   Modify the MaxPerSize and PermSize parameters in the jnet.sh script as follows:

Original value:

-XX:MaxPermSize=128m
-XX:PermSize=128m
 
   

Fixed value:

-XX:MaxPermSize=256m
-XX:PermSize=256m

CSCtb33156

Symptom    Oracle undo and temp tablespaces consume all of the free space in the /db01 partition.

Conditions   This problem occurs when there is heavy database activity. This problem is related to a known Oracle caveat (7291739: CONTENTION UNDER AUTO-TUNED UNDO RETENTION).

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


CSCtb62164

Symptom    After running the getinfo.sh script, the following error message appears:

Permission denied while running "rsh". Check the environment and make sure the root is 
permitted to run "rsh" on host.

Conditions   This problem occurs on a single server installation where rsh is not configured. The /.rhosts file is missing.

Workaround   Create the .rhosts file.


CSCtb70847

Symptom    From the Service Monitor table, the Service Name field incorrectly displays the network service instance value as 0.

Conditions   This problem occurs when the service instance value is higher than 99.

Workaround   To determine the correct network service instance value, do one of the following:

From the CLI, run the showctm command.

From the Domain Explorer, choose Administration > Service UpTime to open the Service Availability table.


CSCtb72630

Symptom    Network discovery hangs when the LINK_TABLE database table is empty.

Conditions   This problem occurs under either of the following conditions:

CTM is installed for the first time, and the LINK_TABLE is empty.

Internal statistics are not calculated on an Oracle system.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, calculate the Oracle internal statistics with a database administration command on the LINK_TABLE database table.


CSCtb81830

Symptom    Multiple initial poll jobs are created for the same NE.

Conditions   Due to an overload of the CTM server, the network service process cannot complete the initial poll for NEs within the polling interval (240 seconds by default). The network service schedules a new initial poll for the same NE every 240 seconds, without first checking whether the initial poll is already in the queue.

The network service log reports the following errors:

2010-08-12 10:47:53,369] [WARN Initial Poll DispatcherWorker#4 on CERENT167] EID-2089: 
InitialPoll to NE is failed
2010-08-12 11:00:48,642] [WARN Initial Poll DispatcherWorker#7 on CERENT167] EID-2089: 
InitialPoll to NE is failed
2010-08-12 11:13:40,081] [WARN Initial Poll DispatcherWorker#4 on CERENT167] EID-2089: 
InitialPoll to NE is failed
2010-08-12 11:26:35,081] [WARN Initial Poll DispatcherWorker#3 on CERENT167] EID-2089: 
InitialPoll to NE is failed

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, restart the network service to clear all initial poll jobs from the queue.


CSCtb83268

Symptom    Some optical NEs (such as the ONS 15454) are shown with a red check mark in the Domain Explorer tree. If these NEs are marked as Out of Service and then In Service, the red check mark persists, and the NEs are not discovered. Restarting the NE service does not resolve the problem.

Conditions   This problem occurs when the CTM database contains inconsistent data. The inconsistency might have been caused by an earlier CTM upgrade.

Workaround   None.


CSCtd01497

Symptom    Automatic database pruning does not work.

Conditions   This problem occurs in a dual-server CTM configuration.

Workaround   Create the /oracle/admin/CTM/udump directory.


CSCtd03803

Symptom    ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain in Sync_Config state.

Conditions   This problem occurs when the SNMP community strings continue to increase in length until the value is too large for the CTM database NE_INFO_TABLE_NESNMPCOMMSTRING column.

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


CSCtd50613

Symptom    When you import large database dump files, the /db05 filesystem fills up.

Conditions   This problem occurs if ARCHIVELOG mode is enabled when you import a large database dump file. If the database contains a large amount of data, the import produces many archived redo logs, and the /db05 filesystem partition fills up.

Workaround   Disable ARCHIVELOG mode before importing the database. Re-enable ARCHIVELOG mode after the import procedure completes.


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


CSCti10246

Symptom    The CTC-based network services can restart when short of stack memory.

Conditions   This problem occurs in medium, large, and high-end installations of a CTM server with more than 200 NEs in the same NE service.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, replace $jrepath -server $4 $5 \ with $jrepath -server $4 -Xmx2650m \ in the /opt/CiscoTransportManagerServer/bin/jnet.sh file; then restart the CTC-based network services.


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   Remove the PM service log file from the /tmp directory. To recover fully from this problem, reboot the workstation.


CSCti30435 (Related caveat ID: CSCth71367)

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


CSCti90949

Symptom    The CTM server intermittently restarts after an overwhelming number of events are received 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.0 patch. See Installing the Latest CTM R9.0 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.


CSCtk81770

Symptom    CTM does not start because the inode limit has been reached in the /opt directory.

Conditions   This problem occurs when there is a large number of empty log files (OpenFusion.*.log) present under the /opt/CiscoTransportManagerServer/openfusion/etc/jacorb/ directory. To view inode usage, enter the following command:

df -F ufs -o i  

An error message appears, stating that there are no inodes left.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, delete all OpenFusion.* files from the /opt/CiscoTransportManagerServer/openfusion/etc/jacorb/ directory.

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.


CSCsu94684

Symptom    When the OSPF Area ID value is set to 1, CTC sends "0:0:0:0:0:0:0:1" instead of "0.0.0.1."

Conditions   This problem occurs with an incorrect OSPF Area ID and only to OSPF with Area ID 0.0.0.1.

Workaround   None.


CSCsx38325

Symptom    The first database export from the CTM GUI fails.

Conditions   This problem occurs only when exporting the CTM database from the GUI before performing the same operation from the CLI.

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


CSCtd56250

Symptom    CTC cannot be launched from CTM.

Conditions   This problem occurs when the database jar version and CTM client jar version in the configuration file does not match.

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


CSCtk99910

Symptom    A CTC library deadlock occurs when CTM manages a large number of nodes. NE connectivity is lost and no longer visible in CTM.

Conditions   This problem occurs when two threads in an application run in a particular sequence and there is a large number of overhead circuits in a large network.

Workaround   Restart the NE service. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.

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 ARCHIVELOG mode enabled.

Workaround   Manually copy the missing archive log files from the other side of the redundancy.


CSCsv42835

Symptom    During HA local 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.


CSCsw63232

Symptom    The optional HA feature for managing replication traffic and NE traffic in separate networks does not manage a failover condition that simulates a network crash on the replication network or NE network.

Conditions   This problem occurs when there are at least two network interface cards (NICs) for every MultiNicA resource.

Workaround   Contact your account representative for the latest version of the Cisco Transport Manager Release 9.0 High Availability Installation Guide, section 2.12, "(Optional) Advanced Network Monitoring."


CSCtc54674

Symptom    In a high availability setup, users cannot execute sudo commands on the secondary CTM server.

Conditions   This problem occurs in an HA setup with local redundancy.

Workaround   Copy the /etc/sudoers file from the primary server to the secondary server.

CTM GateWay/TL1 Caveats


CSCin76320

Symptom    For the ONS 15216 EDFA2 R2.4, the ED-NE-GEN command fails in the CTM GateWay/TL1 session.

Conditions   In a CTM GateWay/TL1 session, the ED-NE-GEN command is denied with the message "GateWay not ready for Network Element." The command does not work because the CTM server is not informed of the change.

Workaround   None.


CSCsd13126

Symptom    The CTM GateWay/TL1 session times out on ONS 15530 and ONS 15540 nodes if kept idle for longer than 60 minutes.

Conditions   This problem applies to TL1 sessions left idle for longer than 60 minutes on ONS 15530 or ONS 15540 NEs.

Workaround   None.


CSCsx32037

Symptom    When launching the TL1 interface on an ENE, the following error message is shown: "EID-501: Cannot launch a remote console to selected NE." Also, the Managed NEs list from the Control Panel displays the IPv6 address of the ENEs instead of their IPv4 address.

Conditions   This problem occurs after changing NE connectivity from IPv4 to IPv6 on a GNE/ENE network.

Workaround   Click the Refresh Data tool from the CTM client or restart the CTM client.

CTM GateWay/CORBA Caveats


Note The following caveats apply only to customers who have purchased the CTM GateWay/CORBA option.



CSCeb43036

Symptom    Cannot set J1 path trace parameters immediately after circuit creation.

Conditions   This problem occurs if you create a subnetwork connection (SNC) between any two NEs, and then immediately try to set J1 trace parameters by using the ManagedElementManager_I::setTPData method.

Workaround   First, either set the IPPM parameter by using the ManagedElementManager_I::setTPData method, or set threshold parameters by using the PerformanceManagementManager_I::setTCATPParameter method. Then, set J1 trace parameters by using the ManagedElementManager_I::setTPData method.


CSCed42655

Symptom    CTM GateWay/CORBA is not installed when the server and the database are installed on separate machines.

Conditions   This problem occurs if the CTM database is installed alone on one machine, and the CTM server and CTM GateWay/CORBA are installed on a second machine.

Workaround   Install CTM GateWay/CORBA on both the server and database machines. Select the Install GateWay/CORBA option for both the CTM server installation and the CTM database installation. On the CTM server machine, CTM GateWay/CORBA error messages might be displayed; you can ignore these.


CSCin75602

Symptom    CTM GateWay/CORBA returns XC loopback values for CTPs even when the 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.


CSCin94462

Symptom    A CTM GateWay/CORBA user is able to perform operations even after being logged out from the CTM client.

Conditions   A CTM GateWay/CORBA user is not logged out immediately when a forced logout is performed from the CTM client. This problem occurs because the user session that is used to connect to the CORBA gateway service is cleared in CTM GateWay/CORBA. The OSS user will notice the loss of session during the next ping cycle to the EMS or when trying to perform an operation on a different manager object.

Workaround   After a forced user logout, the OSS connection must wait until the next ping cycle to the emsSession or until another operation is performed on a different manager object.


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 a CTM GateWay/CORBA interface.

Workaround   Create the link in the CTM client GUI. The link is displayed correctly by APIs such as getTopologicalLink.


CSCse86815

Symptom    The getAllEquipment API returns the value "Unequipped" in the Equipment field when an ONS 15302 R2.0 card is preprovisioned. Instead, the equipment name should be returned.

Conditions   This problem applies to a preprovisioned card on an ONS 15305 R2.0 NE.

Workaround   None.


CSCse86815

Symptom    The getAllEquipment API returns the value "Unequipped" in the Equipment field when an ONS 15302 R2.0 card is preprovisioned. Instead, the equipment name should be returned.

Conditions   This problem applies to a preprovisioned card on an ONS 15305 R2.0 NE.

Workaround   None.


CSCsq26342

Symptom    The getHistoryPMData API takes longer than 15 minutes to return data.

Conditions   When you use the getHistoryPMData API to retrieve data for an ME, the request might take longer than 15 minutes, depending on the node configuration and the server activities.

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


CSCsq99180

Symptom    The getAllSupportedPTPs API fails for an OSCM card and returns an error message.

Conditions   This problem occurs on SONET platforms.

Workaround   Use the getAllSupportedPTPNames API, which correctly returns the available ports for an OSCM card.


CSCsu68317

Symptom    Cross-connect table information provided by the northbound CORBA interface is wrong. The CTP name retrieved by a VC12 circuit (when using getAllCrossConnections) is /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.

Conditions   This problem might occur in the presence of LO circuits routed through tunnel circuits.

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


CSCsv65237

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

Conditions   This problem occurs on OPT_RAMP_C cards.

Workaround   Use CTC or the CTM GUI to set the power threshold.


CSCsw80498

Symptom    An exception appears and PM values are not displayed when you use the CTM GateWay/CORBA interface to collect ONS 15310 MA SDH DS3 PM data.

Conditions   This problem occurs when you use CTM GateWay/CORBA to collect DS3 PM data.

Workaround   None.


CSCsx55667

Symptom    The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."

Conditions   This problem occurs when the connection between the CTM system and a remote NE is lost momentarily. For example, DCN instability or a network delay might cause the connection to drop for a short time.

Workaround   Mark the NE as Out of Service and then In Service. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCsz53477

Symptom    The Error Log contains multiple errors that are similar to the following:

CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290

Conditions   This problem occurs when an OCHNC circuit is created and passes through a node that contains a WXC card.

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


CSCta30577

Symptom    The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.

Conditions   IMR is an OpenFusion service required by the CTM server. IMR is considered a critical process and is monitored by core_pmon.sh. The CTM server shuts down automatically if the IMR service stops running.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, complete one of the following workarounds, depending on whether your CTM R9.0 setup uses a non-HA or an HA configuration:

Non-HA Configuration

For CTM R9.0 in a non-HA configuration, complete the following steps:


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

#ctms-stop
 
   

Step 2 Go to the /opt/CiscoTransportManagerServer/openfusion/bin/ directory and enter the following commands:

# ./run com.prismt.openfusion.tools.ChangeJacORBProperties -r jacorb.use_imr=on 
jacorb.use_imr=off
# ./run com.prismt.openfusion.tools.ChangeJacORBProperties -r jacorb.use_imr_endpoint=on 
jacorb.use_imr_endpoint=off
 
   

Step 3 Enter the following command to start the CTM server:

#ctms-start
 
   

HA Configuration

For CTM R9.0 in an HA configuration, work with a Symantec Veritas expert to complete the preceding steps. Any changes on the primary server must also be made on the secondary server. After the changes are complete, verify that the /opt/CiscoTransportManagerServer/openfusion/classes/jacorb.properties file has been modified correctly on the secondary server.


CSCta62163

Symptom    The setTPData API returns an exception or does not set parameters on ONS 15310 MA SDH NEs.

Conditions   See Symptom.

Workaround   Use the CTM client.


CSCtb59547

Symptom    CTM GateWay/CORBA reports incorrect physical location information.

Conditions   This problem occurs when a pluggable insertion module (PIM) is removed from an ONS 15600 ASAP card. However, the Alarm Browser correctly displays the Improper Removal alarm.

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


CSCtb83164

Symptom    After device provision configurations, the following APIs are not updated: getEquipment, getAllEquipment, and getAllEquipmentName.

Conditions   See Symptom.

Workaround   Stop and restart the CTM GateWay/CORBA service.


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.


CSCti80797

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

Conditions   This problem occurs when using the CTM GateWay/CORBA getCTMHistoryPMData API.

Workaround   Use the getTPHistoryPMData API. Alternately, install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack.


CSCtj88384

Symptom    The getAllSubnetworkConnections API does not work.

Conditions   This problem occurs when the CTM GateWay/CORBA service is running.

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


CSCtk13453

Symptom    PM data is not retrieved when using GateWay/CORBA APIs on some layer rates.

Conditions   This problem occurs with the following layer rates:

Layer 114: LR_STS18c_and_VC4_6c (only on ONS 15454-ANSI)

Layer 115: LR_STS36c_and_VC4_12c (only on ONS 15454-ANSI)

Layer 14: LR_STS1_and_AU3_High_Order_VC3 (only on ONS 15600)

Layer 15: LR_STS3c_and_AU4_VC4 (only on ONS 15600)

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


CSCtn95802

Symptom    PM data is not retrieved when using GateWay/CORBA APIs on some layer rates.

Conditions   This problem occurs with the following layer rates:

Layer 114: LR_STS18c_and_VC4_6c (only on ONS 15454-ETSI)

Layer 115: LR_STS36c_and_VC4_12c (only on ONS 15454-ETSI)

Layer 15: LR_STS3c_and_AU4_VC4 (only on ONS 15600-ETSI)

Workaround   None.

NE-Specific Caveats

This section includes the following information:

Cisco MGX Voice Gateway

Cisco ONS 15216 EDFA

Cisco ONS 15302 and 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 ONS 15800, Cisco ONS 15801, and Cisco ONS 15808

Cisco MGX Voice Gateway


CSCse39608

Symptom    The CTM Alarm Log continues to report card, line, path, and port modify alarms every eight hours.

Conditions   This problem occurs under normal conditions.

Workaround   Complete the following configuration before starting CTM or the MGX NE service:


Step 1 Enter the following command:

cd opt/svplus/config
 
   

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

Step 3 Search for "PERIODIC_RESYNC_INTERVAL."

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

Step 5 Start CTM or the MGX 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.


CSCsv12810

Symptom    An MGX node is added to a CTM server, but is not included in the automatic backup process.

Conditions   This problem occurs under normal conditions.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, stop and restart the automatic backup process on the server. The new MGX node is listed in the automatic backup process list.


CSCsx52433

Symptom    In the MGX Voice Gateway Configuration Center, the Circuit Identifier field is blank for DS1 and SONET lines on a VXSM card. Also, utilization counters are not enabled in the Diagnostics Center > Resource Control tab.

Conditions   This problem occurs on VXSM release 5.5.0 cards.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, complete the following steps:


Step 1 Back up the following files:

/opt/svplus/xml/diagcenter/Card/VXSM-Card.xml

/opt/svplus/xml/configcenter/Line/VXSM-SONET-Line.xml

/opt/svplus/xml/configcenter/Line/VXSM-DS1-Line.xml

Step 2 Edit the VXSM-Card.xml file by replacing:

<Applicability>(cardVersion GE 5.4.216 and cardVersion LE 5.5) or (cardVersion GE 
5.54.216)</Applicability>
 
   

with:

<Applicability>(cardVersion GE 5.4.216 AND cardVersion LT 5.54) or (cardVersion GE 
5.55)</Applicability>
 
   

Step 3 Edit the VXSM-SONET-Line.xml file by replacing:

<Applicability>(cardVersion GE 5.4.216 and cardVersion LE 5.5) or (cardVersion GE 
5.54.216)</Applicability>
 
   

with:

<Applicability>(cardVersion GE 5.4.216 AND cardVersion LT 5.54) or (cardVersion GE 
5.55)</Applicability>
 
   

Step 4 Edit the VXSM-DS1-Line.xml file by replacing:

<Applicability>(cardVersion GE 5.4.216 and cardVersion LE 5.5) or (cardVersion GE 
5.54.216)</Applicability>
 
   

with:

<Applicability>(cardVersion GE 5.4.216 AND cardVersion LT 5.54) or (cardVersion GE 
5.55)</Applicability>
 
   

Step 5 Restart the NE service process.



CSCsx69981

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

Conditions   This problem occurs when creating an MGC IP address entry with an MGC Index more than 4 and less than 24.

Workaround   Do one of the following:

Create an MGC IP address entry with an MGC Index between 1 and 4.

Use the CLI to create an MGC IP address entry.


CSCsx93323

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

Conditions   This problem occurs when an H248 link is down between a Media Gateway and Media Gateway Controller and a 70635 trap is sent to CTM.

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


CSCsy29600

Symptom    CTM does not receive PM data from managed MGX devices.

Conditions   This problem occurs when PM data is enabled and stored for 30 days.

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


CSCta31966

Symptom    Memory usage for the ooemc process increases over a period of time.

Conditions   This problem occurs when a VXSM card is on the network and multiple resynchronizations occur due to permanent trap loss.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, resolve permanent trap loss or event issues to prevent multiple resynchronizations and delay the impact of increased memory usage. Resynchronizations are scheduled once a week by default, but are also triggered by particular events and permanent trap loss.


CSCtb55280

Symptom    If you remove a multimode fiber from a gigabit Ethernet interface on an RPM card, the PXM reports a critical alarm. However, due to an Oracle exception, CTM does not raise an alarm.

Conditions   This problem occurs on CTM R8.5 and R9.0 and Oracle 10 when:

RPM is running 12.4(15)T9

VXSM is running 5.4(20.201)

PXM is running 5.4(30.200)

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


CSCtc49087

Symptom    CTM displays the MGX 88xx chassis serial number as N/A in the Equipment Inventory table.

Conditions   See Symptom.

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


CSCtc73082

Symptom    Adding a preprovisioned MGX node to a CTM server results in high CPU usage.

Conditions   See Symptom.

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


CSCte65495

Symptom    Server memory usage for ooemc process increases over a period of time with every MGX NE resync.

Symptom    This problem occurs when a VXSM card is on the network and multiple resynchronizations occur.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, restart the MGX NE service when server memory availability decreases below the operational threshold.

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.


CSCsh07187

Symptom    There are no available PTPs on ONS 15216 EDFA NEs when creating manual links to ONS 158xx NEs.

Conditions   When you try to create a link between ONS 15216 EDFA and ONS 158xx NEs using the Configuration menu, there are no PTPs available in the Create Link wizard for ONS 15216 EDFA NEs.

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.


CSCsi39881

Symptom    The default CTM and GateWay/TL1 users of ONS 15216 EDFA3 NEs are the same.

Conditions   Connection problems to ONS 15216 EDFA3 NEs can occur if CTM and CTM GateWay/TL1 are used and configured with the same user. ONS 15216 EDFA3 NEs can accept only one connection per user. Therefore, the NEs must be configured with as many CTM GateWay/TL1 users as the projected number of connections. Every instance of the CTM server can connect to the same NE with up to two clients: ONS 15216 NE Explorer and CTM GateWay/TL1.

Currently, the default users in the Control Panel > CTM Security tab for ONS 15216 EDFA3 NEs have the CISCO15 user. Two different users or empty users should be configured.

Workaround   Manually configure two different users for the ONS 15216 EDFA3 NE in the Control Panel > Security tab or in the Domain Explorer > Network Element Properties pane.


CSCsl06434

Symptom    The communication state of ONS 15216 EDFA3 NEs is Initialization Failed after rebooting the CTM server operating system.

Conditions   This problem applies to ONS 15216 EDFA3 NEs on a dual CTM server installation and occurs after the CTM server operating system reboots.

Workaround   Wait until the NE polling completes or 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.0 patch. See Installing the Latest CTM R9.0 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.


CSCta73923

Symptom    ONS 15216 EDFA3 nodes lose connectivity with CTM.

Conditions   This problem occurs on ONS 15216 EDFA3 nodes managed by CTM.

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

Cisco ONS 15302 and 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 two minutes.

Conditions   This 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 applies to the E100-WAN-8 card of the ONS 15305 NE.

Workaround   Refresh data from the NE to update the status of the VLAN tab.


CSCsh48269

Symptom    The following issues 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 applies to LOP or LOP-V circuits that are created from CTC and then deleted from CTC 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 15302 and ONS 15305 R2.x NEs, the old Cisco logo is shown.

Workaround   None.


CSCta69422 (Related caveat ID: CSCta27875)

Symptom    The ONS 15305 NE Service hangs, and if you try to mark NEs as In Service or Out of Service, CTM returns the following error message:

EID-542: Database error: Cannot modify the NE state.

Conditions   This problem occurs when the ONS 15305 NE Service manages more than 100 ONS 15305 R2.0 NEs and reaches the maximum Java heap size.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternatively, contact the Cisco Technical Assistance Center (TAC) to expand the Java heap size; then, restart the ONS 15305 NE Service.


CSCtc10514

Symptom    CTM does not receive alarms from ONS 15305 R2.0 NEs.

Conditions   This problem occurs randomly when CTM is managing many ONS 15305 R2.0 NEs. The problem affects some—but not all—managed NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, mark the NE as Out of Service and then In Service.


CSCtc20162

Symptom    When a single ONS 15305 NE service manages than one hundred ONS 15305 NEs, the ONS 15305 NE service restarts.

Conditions   This problem occurs because the ONS 15305 NE service runs out of memory if it manages more than one hundred ONS 15305 NEs.

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


CSCts44079

Symptom    CTM Alarm Browser table reports some alarms twice.

Conditions   This behavior occurs under the following conditions:

1. ONS 15305 NEs are configured with SNMP traps.

2. When you reboot the software or hardware of ONS 15305 NE.

3. SNMP trap detects loss of communication (LOC) with CTM.

Workaround   Initiate a rediscovery process for the ONS 15305 NEs.


CSCts60545

Symptom    Cisco Edge Craft 2.2.3 does not work properly.

Conditions   This problem occurs under the following conditions:

1. CEC is installed on a Solaris system.

2. CEC is launched on 15305 CTC-based NEs.

Workaround   Launch CEC 2.2.3 from a Windows system.

Cisco ONS 15310


CSCsi01139

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

Conditions   This problem occurs when you:

1. Enable 15-minute and 1-day robust PM data collection for ONS 15310 CL NEs.

2. Mark the ONS 15310 CL NEs as Out of Service and then In Service.

3. Wait until the next 15-minute PM data collection interval occurs. When you collect PM data for a SONET section with line and physical categories, several robust PM buckets are missing.

Workaround   None.


CSCsl11466

Symptom    CTM does not report creation of or modification to ONS 15310 DS3 or EC1 ports.

Conditions   This problem occurs when you create or modify a broadband port (DS3 or EC1). The information on the DS3 or EC1 tab does not update.

Workaround   None.


CSCsk71210

Symptom    When you change the NE default values on ONS 15310 CL R6.0.3 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 06.03-007D-06.04 of ONS 15310 CL NEs.

Workaround   Do one of the following:

Use CTC to modify the NE default values.

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


CSCsw79969

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

Conditions   This problem occurs when you do the following:

1. From the Domain Explorer, select the ONS 15310 MA NE and choose the Configuration > NE Explorer > Shelf View tab > CTX 2500 card.

2. Change the Admin state to Maintenance.

3. Right-click the card. The Hard Reset option is not available.

Workaround   None.


CSCsx28572

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

Conditions   This problem occurs when you do the following on an ONS 15310 MA NE:

1. From the NE Explorer, click the OSI tab.

2. From the Main Setup subtab, select End system.

3. From the Routers Setup subtab, edit and enable Router 1.

4. From the Subnets subtab, enable the LAN subnet button and click OK. Sometimes this operation fails and displays an error message.

Workaround   Use CTC to change from an end system to an intermediate system; then, enable the LAN on the subnetwork.


CSCta58331

Symptom    The port status incorrectly displays NO-STATUS after creating a 1+1 protection group on an ONS 15310 MA SONET/SDH or ONS 15310 CL CTX card.

Conditions   See Symptom.

Workaround   None.


CSCth48038

Symptom    The CTX Transceiver tab is blank inside NE Explorer for Cisco ONS 15310 MA SDH nodes.

Conditions   This problem only occurs on Cisco ONS 15310 MA SDH nodes.

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

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


CSCea92062

Symptom    When you attempt to switch timing to BITS1, BITS2 from internal while BITS1 and BITS2 sources are not connected, the switch appears not to have taken place, but in fact does take place.

Conditions   Switching occurs successfully from CTM and on the NE, but the NE reverts back to internal immediately, as there was no BITS1 or BITS2 source present to switch to. The NE relays this update to CTM, and CTM updates to internal. The NE should not switch, but should instead send an exception back to CTM.

Workaround   None.


CSCsc66346

Symptom    The IPPM set operation fails on STM-1E cards in the NE Explorer > VC4 tab for NE releases earlier than 7.0.

Conditions   This problem occurs when creating VC4 circuits on STM-1E cards. This problem applies to NE releases earlier than 7.0.

Workaround   None.


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. Change the node positions on the network view using CTC. 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.


CSCsf14512

Symptom    The Use Generic MIB option is missing from the SNMP tab in the NE Explorer of CTC-based R6.2.2 NEs.

Conditions   This problem applies to all CTC-based R6.2.2 NEs.

Workaround   None.


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 applies to the Section Trace tab of MRC-12 cards in the NE Explorer. When you change the New Expected String field from an 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.


CSCsg83146

Symptom    Cannot edit and save NE default values for the ONS 15327 and ONS 15454 NEs.

Conditions   See Symptom.

Workaround   None.


CSCsh20563

Symptom    The Standby Software column in the NE Software table is not updated after performing a software download operation on a TNE or ENE.

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


CSCsh24558

Symptom    NEs do not come up after setting an NE user name and password in the Control Panel and then adding a new NE to CTM.

Conditions   This problem occurs when a new server is installed. Specify the username and password for CTC-based NEs in the Control Panel and then add an NE. The initialization process fails and displays an error message stating that the username and password are wrong.

Workaround   Specify the username and password in the Domain Explorer > Network Element Properties pane.


CSCsh91068

Symptom    Changes to the NE defaults of ONS 15454 SDH R7.x.x NEs are not applied.

Conditions   This problem occurs when you change any attributes in the NE Defaults tab of the ONS 15454 SDH NE Explorer.

Workaround   None.


CSCsh96438

Symptom    Port information on TCA events that are generated on DS3 cards is inconsistent between CTM and CTC.

Conditions   The physical location information in the Alarm Log for TCA events generated on DS3 cards is wrong. 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    Alarms on the DS1 or DS3 port 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. This resynchronizes the alarms.


CSCsk74602

Symptom    When you change the NE default values on ONS 15327 R6.0.3 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 06.03-007D-06.04 of ONS 15327 NEs.

Workaround   Do one of the following:

Use CTC to modify the NE default values.

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


CSCsv34441

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

Conditions   This problem occurs when you do the following:

1. Configure two OTU2_XP cards for TXP mode.

2. Provision the same payload type on all ports.

3. Provision a Y-cable protection group between the two 1-1 client ports.

4. From the card panel, set the card to EFEC mode.

Workaround   Delete the Y-cable protection group and port 1-1; then, reconfigure the cards.


CSCsv59259

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

Conditions   This problem occurs in the slot properties pane of an ONS 15454 SONET or ONS 15454 SDH 4MD_xx.x card.

Workaround   Use CTC.


CSCsw39894

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

Conditions   This problem occurs when you do the following:

1. Configure the OTU2_XP card to Standard Regeneration mode.

2. Configure the payload to10 GE on ports 1-3 and OC192 on ports 2-4.

3. Set the Regen Line Name field for ports 2-4. The Card tab shows that the regeneration line name that you entered for ports 2-4 is also copied on ports 1-3.

Workaround   None.


CSCsw93005

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

Conditions   This problem occurs when you do the following:

1. Configure an OTU2_XP card in Standard Regen mode.

2. From the Slot Properties pane > Card tab, change the ODU Transparency value.

3. Click Apply. The value remains unchanged.

Workaround   In addition to setting the ODU Transparency, change other values; for example, change the Regen Line name. The values are updated correctly.


CSCsw98943

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

Conditions   This problem occurs when you do the following:

1. Configure the OTU2_XP card for TXP mode.

2. Provision the same payload type on all ports. Port 2 moves to IS state.

3. Set the card to EFEC mode. CTM should not allow you to change the card to EFEC mode if the port is not in OOS, DSBLD state.

Workaround   Delete and reprovision the card.


CSCsx15019

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

Conditions   This problem applies only to OPT_BST_L cards.

Workaround   None.


CSCsx15063

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

Conditions   This problem occurs when you have an OTU2_XP card in TXP mode and you provision some ports. For example, if SONET is set as the payload type on ports 3 and 4, and you later provision SONET on port 1, the Card tab values should update. However, the values do not update.

Workaround   From the Card tab, click Cancel.


CSCsy83061

Symptom    From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for release 8.0 NEs.

Conditions   This problem occurs only on 8.0 NEs.

Workaround   Install the latest CTM R9.0 patch. See Installing the Latest CTM R9.0 Patch or Service Pack. Alternately, you can apply the settings multiple times until the change is successful.

Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP


CSCsg69277

Symptom    The 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 the unidirectional link from the line amplifier to the optical channel ROADM card remains valid. An alarm is displayed in the Network Map.

Conditions   This problem occurs when a fiber cut occurs 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 on a heavily-loaded multishelf NE take too long to complete.

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 to the circuit because the other path, which is shorter in terms of the number of 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   Complete the following:

Include or exclude nodes during manual routing.

(Applicable to WXC nodes) Select the outgoing optical side during manual routing.


CSCsh95163

Symptom    Links in the Network Map are shown as valid and no Loss of Signal 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 that does not work correctly when a fiber cut occurs between two NEs. The Loss of Signal 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.


CSCsk82635

Symptom    Unable to change the NE default values on ONS 15454 SDH R7.2.3 NEs.

Conditions   After changing the NE default values on ONS 15454 SDH R7.2.3 NEs, the parameters still display the original values and no error message is displayed.

Workaround   Use CTC to change the NE default values.


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.


CSCsu81327

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

Conditions   This problem occurs only on ONS 15454 NE releases 4.16, 4.62, and 5.08. This problem occurs after you:

1. Save NE default settings to the NE defaults file.

2. Open the NE defaults file, edit the default settings, and save the file.

3. Choose Configuration > CTC-Based SONET NEs > NE Defaults Management and view the default settings. The default settings do not reflect the changes you made to the NE defaults file.

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.


CSCsg61886

Symptom    PM data collection fails on ONS 15600 SDH R1.4 NEs when the cards are preprovisioned.

Conditions   Enable historical PM data collection on ONS 15600 SDH R1.4 NEs that contain preprovisioned cards. The PM table does not show any data after the collection interval.

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.

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


CSCsd19138

Symptom    An ONS 15808 NE is in In Service state, but cannot be launched from the NE Explorer. The software version and version name do not appear in the Identification tab for the node in the Domain Explorer.

Conditions   This problem occurs when the NE being managed by CTM contains a board that has corrupt fields in the flash memory.

Workaround   Complete the following steps to regain functionality:


Step 1 From CTM, mark the NE node as Out of Service.

Step 2 Open a TL1 session (port 1000) on the NE and enter the RTRV-VER::ALL:JJJ; command.

Step 3 Locate the problem card by searching for a card with a corrupt field; for example:

40MD_CO__D-01-03-01:01.00.00,/A"ßÎ...‚ÅyËÍÂ01.01.00-B,01.01.00-B,06021GK1,0,0
 
   

Step 4 Enter the following TL1 command to remove the corresponding slot from the configuration:

DLT-EQPT::01-03-01:AA;
 
   

Step 5 From CTM, mark the NE node as In Service.



CSCse81396

Symptom    The EMSMgr_I::createTopologicalLink command 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 GUI. The link is displayed correctly by APIs such as getTopologicalLink.


CSCsf27800

Symptom    PM data is not collected on ONS 1580x NEs.

Conditions   This problem occurs when PM data collection is enabled even if the ONS 1580x has not been discovered.

Workaround   In the Domain Explorer, mark the ONS 1580x NE as In Service and disable PM data collection on the NE. Then, re-enable PM data collection.


CSCsk23271

Symptom    The correct card status of ONS 1580x NEs is not displayed when you use the SetMEAdminState API.

Conditions   When the status of an ONS 1580x NE is changed from Maintenance to In Service or vice versa using the SetMEAdminState API, the changes are not reflected on the CMP card.

Workaround   Use the CTM GUI to change the NE administrative state.


CSCuk58839

Symptom    A software download using a relative TFTP file path fails unexpectedly on the ONS 15808.

Conditions   This problem occurs when you initiate a CTM software download through TFTP and the relative path begins with a digit, as in the relative path 15808/catalog.txt.

Workaround   Use a relative path that does not begin with a digit; for example, ons15808/catalog.txt.

Related Documentation


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

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

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


Note The Cisco Transport Manager Release 9.0 High Availability Installation Guide is not available online. Contact your Cisco account representative to obtain this guide.


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

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