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
CTM-Supported JRE and Apache Versions
Resolved Caveats
Installing the CTM R9.0.0.620.5 Patch
Determining What CTM Patch Is Currently Installed in the CTM System
Backing Up the CTM Database Before Installing the CTM R9.0.0.620.5 Patch
Downloading the CTM R9.0.0.620.5 Patch
Installing the CTM R9.0.0.620.5 Server Patch
Installing the CTM R9.0.0.620.5 Client Patch in Windows
Installing the CTM R9.0.0.620.5 Client Patch in Solaris
Open Caveats
Installation and Upgrade Caveats
CTM Client Caveats
Alarm Management
Circuit and Link Management
User Management
Data Services
Domain Explorer
NE Explorer
Network Map
Performance Monitoring
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
November 25, 2009
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 CTM R9.0.0.620.5 Patch, page 27
•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 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 log1
|
When a database exception occurs, cleared alarms are dumped into the debug log.
|
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 NEs2
|
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.
|
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 patch or service pack is installed:
–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 SONET R9.0.1
–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 CTM R9.0.0.620.5 Patch was added.
•The section Third-Party Patches and Security Notices was added.
•The following caveats were added:
–CSCsy01229, page 36
–CSCsy74450, page 39
–CSCsy84624, page 59
–CSCsz26474, page 95
–CSCsz43543, page 76
–CSCsz75781, page 91
–CSCta23414, page 95
–CSCta30985, page 96
–CSCta58331, page 117
–CSCta62163, page 105
–CSCta69019, page 96
–CSCta73380, page 61
–CSCta95729, page 61
–CSCtb01411, page 96
–CSCtb14476, page 68
–CSCtb28839, page 97
–CSCtb62164, page 97
–CSCtb67646, page 92
–CSCtb75511, page 62
–CSCtb83002, page 92
–CSCtb83268, page 97
–CSCtb97851, page 39
–CSCtd03803, page 98
–CSCtd26328, page 93
–CSCtd36677, page 62
–CSCtd40139, page 62
Sections Removed
The following sections were removed, because the CTM R9.0.0.620.5 patch. 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
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
|
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.12
|
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.13
|
09.01-009F-20.11
|
ONS 15310 MA SDH
|
Release 9.0
|
09.00-008I-17.17
|
Release 9.0.14
|
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.15
|
09.01-009F-20.11
|
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.16
|
09.01-009F-20.11
|
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.17
|
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.18
|
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.209
|
5.4.20
|
Release 5.5.00
|
5.5.00
|
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.
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.
|
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 VG 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsl26218
|
The NE services freezes 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 Auto Backup process.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsu90217
|
Continuous 15-minute and -day PM lost bucket alarms occur and do not clear.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsw68952
|
A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsw72207
|
The Protection panel shows the wrong name for an OTU2_XP card.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsw91974
|
In a large network of GNEs and ENEs, CTM fails to collect PM data.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsx38325
|
The first database export from the CTM GUI fails.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsx50126
|
Due to security issues, CTM must support Apache web server version 2.2.11.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsx50161
|
The Apache Tomcat software should be disabled to avoid potential security issues.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsx56687
|
The SPAN_BS_TABLE database table displays incorrect working and protected values.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsx81985
|
During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05 directory.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsy14909
|
A VLAN range cannot be added on a 10GE_XP/GE_XP card.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsy29600
|
CTM does not receive PM data from managed MGX devices.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsy95336
|
CTM fails to reconfigure circuits on release 8.5 NEs.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsz33838
|
Cannot add drops on cards configured in Automatic mode.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsz63889
|
Sometimes memory backups fail for CTC-based release 6.0.1 NEs.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsz96763
|
In the Service Up Time log, clicking the Stopped At column does not sort the table.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCsz83568
|
A DB WriterWorker NPE appears in the pmservice.log file for MRC-12 cards.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCta00978
|
When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCta29948
|
Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCta30577
|
The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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.
|
CSCta61660
|
ENE/GNE role changes on the network causes unstable NE service and node connectivity issues.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
CSCta69422
|
Insufficient memory causes ONS 15305 NE connectivity issues. Errors also appear after marking NEs as Out of Service and then In Service.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCta69923
|
Cleared alarms are not removed from the Alarm Browser.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCta73923
|
ONS 15216 EDFA3 nodes lose connectivity with CTM.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtb85880
|
After performing NE software upgrades, the SM service restarts NE services.
(Related caveat ID: CSCtc20552)
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtb30304
|
An error message (EID-315) appears after selecting Edit > Find to search for a circuit.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtb31787
|
CTM R9.0 raises incomplete critical alarms.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtb59547
|
CTM GateWay/CORBA reports incorrect physical location information.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtb78977
|
The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
CSCtb83164
|
After device provision configurations, the following APIs are not updated: getEquipment, getAllEquipment, and getAllEquipmentName.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtc19328
|
The CTM Domain Explorer window freezes and you are unable to select other NEs.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
|
CSCtc70085
|
From the CTM client, you cannot launch CTC on release 9.0.x ENEs.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
CSCtd31222
|
Circuits without a destination are not displayed in the Circuit table.
Note This caveat is fixed with the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch
|
Installing the CTM R9.0.0.620.5 Patch
This section describes how to download and install the CTM R9.0.0.620.5 patch.
Note•Caveats are categorized as a server fix (S), client fix (C), or both (CS).
•This patch inherits all fixes from previous patches.
The following caveats are fixed in the CTM R9.0.0.620.5 patch:
•CSCsl26108 (S): CTM performs slowly while connecting, discovering, and resynchronizing CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
•CSCsu90217 (S): Continuous 15-minute and 1-day PM lost bucket alarms occur and do not clear.
•CSCsz83568 (S): A DB WriterWorker NPE appears in the pmservice.log file for MRC-12 cards.
•CSCta29948 (S): Alarms in the CTM Alarm Browser do not clear or synchronize with CTC.
•CSCta33231 (S): The number of alarms displayed on the dashboard and NE Explorer is wrong. However, the alarm count is shown correctly in the Alarm Browser.
•CSCta39574 (S): When opening the Circuit table from an ONS 15454 node, circuits are not retrieved and a timeout error is displayed.
Note 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.
•CSCta69923 (S): Cleared alarms are not removed from the Alarm Browser.
•CSCta73923 (S): ONS 15216 EDFA3 nodes lose connectivity with CTM.
•CSCtb05738 (S): 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.
•CSCtb13395 (S): 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.
•CSCtb21147 (S): CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.
•CSCtb30304 (C): An error message (EID-315) appears after selecting Edit > Find to search for a circuit.
•CSCtb31787 (S): CTM R9.0 raises incomplete critical alarms.
•CSCtb59547 (CS): CTM GateWay/CORBA reports incorrect physical location information.
•CSCtb65065 (C): 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.
•CSCtb73160 (S): The Circuit table does not display port names for ONS 15454 ANSI DS1_E1_56 and OC192_XFP cards.
•CSCtb78977 (S): The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
•CSCtb83164 (S): After device provision configurations, the following APIs are not updated: getEquipment, getAllEquipment, and getAllEquipmentName.
•CSCtc19328 (C): The CTM Domain Explorer window freezes and you are unable to select other NEs.
•CSCtc70085 (C): From the CTM client, you cannot launch CTC on release 9.0.x ENEs.
•CSCtd03803 (S): ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain in Sync_Config state.
•CSCtd31222 (S): Circuits without a destination are not displayed in the Circuit table.
The following caveats are fixed in the CTM R9.0.0.604.2 patch:
•CSCsz63889 (S): Sometimes memory backups fail for CTC-based release 6.0.1 NEs.
•CSCtb88190 (S): CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs with an Unavailable status.
•CSCtb85880 (S): After performing NE software upgrades, the SM service restarts the NE service. (Related caveat ID: CSCtc20552.)
•CSCtb01411 (S): 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
The following caveats are fixed in the CTM R9.0.0.600.8 patch:
•CSCsq26342 (CS): The getHistoryPMData API takes longer than 15 minutes to return data.
•CSCsr48358 (S): The prune_ne_ipaddress script does not work with IPv6 addresses.
•CSCsu68317 (S): 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.
•CSCsv12810 (S): An MGX is added to a CTM server, but is not included in the Auto Backup process.
•CSCsv33266 (S): If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
•CSCsw22308 (S): 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.
•CSCsw68952 (S): A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
•CSCsw72207 (S): The Protection panel shows the wrong name for an OTU2_XP card.
•CSCsw91974 (S): In a large network of GNEs and ENEs, CTM fails to collect PM data.
•CSCsx22431 (C): For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports the correct wavelength value.
•CSCsx23360 (S): An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle Enterprise Manager or the Alert Log.
•CSCsx26527 (S): The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer do not exist.
•CSCsx38325 (S): The first database export from the CTM GUI fails.
•CSCsx44115 (S): 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.
•CSCsx50126 (S): Due to security issues, CTM must support Apache web server version 2.2.11.
•CSCsx50161 (S): The Apache Tomcat software should be disabled to avoid potential security issues.
•CSCsx52433 (S): 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.
•CSCsx55667 (CS): The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
•CSCsx56687 (S): The SPAN_BS_TABLE database table displays incorrect working and protected values.
•CSCsx64513 (C): 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.
•CSCsx81985 (S): During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05 directory.
•CSCsx93323 (S): 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.
•CSCsy14909 (CS): A VLAN range cannot be added on a 10GE_XP/GE_XP card.
•CSCsy29600 (S): CTM does not receive PM data from managed MGX devices.
•CSCsy30294 (S): 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.
•CSCsy56348 (C): Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
•CSCsy83061 (C): From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for release 8.0 NEs.
•CSCsy95336 (S): CTM fails to reconfigure circuits on release 8.5 NEs.
•CSCsz33838 (S): Cannot add drops on cards configured in Automatic mode.
•CSCsz53477 (S): The Error Log contains multiple errors that are similar to the following:
CTMError: Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290
•CSCsz58653 (S): Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
•CSCsz96763 (S): In the Service Up Time log, clicking the Stopped At column does not sort the table.
•CSCta00978 (S): When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.
•CSCta30577 (S): The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.
•CSCta61660 (S): ENE/GNE role changes on the network causes unstable NE service and node connectivity issues.
•CSCta69422 (S): Insufficient memory causes ONS 15305 NE connectivity issues. Errors also appear after marking NEs as Out of Service and then In Service.
•CSCta69424 (S): If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the CTM client freezes.
CTM R9.0.0.620.5 is intended for customers who are currently using one of the following:
•CTM R9.0.0.507
•CTM R9.0.0.580
•CTM R9.0.0.581
•CTM R9.0.0.600
•CTM R9.0.0.604
Note Install the CTM R9.0.0.620.5 patch only in a non-high availability setup. If you are using a high availability setup, contact your Cisco account representative before installing the patch.
Complete the following procedures to upgrade to the CTM R9.0.0.620.5 patch.
Determining What CTM Patch Is Currently Installed in the CTM System
To check your current CTM release and patch level, log into the CTM server as the root user and enter the following command:
The first line of the output gives you the release and patch level. Before proceeding, make sure that the output results to one of the following:
•Cisco Transport Manager Server Version: 9.0 Build: 507
•Cisco Transport Manager Server Version: 9.0 Build: 580
•Cisco Transport Manager Server Version: 9.0 Build: 581
•Cisco Transport Manager Server Version: 9.0 Build: 600
•Cisco Transport Manager Server Version: 9.0 Build: 604
Backing Up the CTM Database Before Installing the CTM R9.0.0.620.5 Patch
Before installing the CTM R9.0.0.620.5 patch, it is strongly recommended that you back up the existing database. To back up the CTM database, refer to the following sections in Chapter 4 of the Cisco Transport Manager Release 9.0 User Guide:
•Backing Up the CTM Database from the CTM GUI
•Backing Up the CTM Database from the CLI
Downloading the CTM R9.0.0.620.5 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.620.5.
Step 6 In the right pane, click CTM9.0.0.620.5.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 CTM9.0.0.620.5.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:
unzip CTM9.0.0.620.5.patch.zip
For example, to extract the file to the /temp directory, enter:
unzip CTM9.0.0.620.5.patch.zip
This creates a directory called 620, which contains all of the patch-related files.
Step 11 Enter the following command to enter the directory:
Step 12 In Windows, download the CTM9.0.0.620.5.patch.zip file to the client workstation. Extract the file using a tool such as WinZip, as follows:
a. Open the CTM9.0.0.620.5.patch.zip file in WinZip.
b. Click the Extract button.
c. Verify that the Use folder names check box is checked.
d. In the Extract to drop-down list, select the location where you want to extract the files.
e. Click Extract.
Installing the CTM R9.0.0.620.5 Server Patch
To apply the CTM R9.0.0.620.5 patch to the server, complete the following steps:
Step 1 Complete the following substeps to notify all CTM users before shutting down the CTM server:
a. In the Domain Explorer window, choose File > Notify Users. The Notify Users dialog box opens.
b. In the Message Targets area, click the All CTM Users radio button.
c. Type the message in the Message area. Customize the message as appropriate for your organization. A sample message might read:
The CTM server will be shut down in 5 minutes. Please log out of the CTM client before
then.
d. Click Send.
e. Wait an appropriate amount of time for the CTM users to log out.
Step 2 At the end of the grace period, complete the following substeps to log out all of the CTM clients:
a. Log into the CTM server using an account with SuperUser privileges.
b. In the Domain Explorer window, choose Administration > CTM Users.
c. In the CTM Users table, choose Administration > Logged In CTM Users.
d. In the Logged In CTM Users table, select a user and choose Administration > Log Out User (or click the Log Out User tool).
Note This menu option is disabled if you selected your own session.
e. Click Yes at the following prompt:
This operation will log out the selected CTM user. The process will take approximately
1 minute and this CTM client will be unusable until then. Do you wish to continue?
Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the request is complete. Log out all of the users listed in the Logged In CTM Users table to make sure that all user sessions are terminated.
Step 3 As the root user, enter the following command at the UNIX prompt to stop the CTM server:
Step 4 To patch the server, enter the following command in the 620 directory where the patch was extracted:
Note Depending on the size of the database, the script might take a while to complete. Do not interrupt the script before it finishes.
Step 5 As the root user, enter the following command at the UNIX prompt on the CTM server workstation to start the CTM server:
Step 6 As the root user, enter the following command at the UNIX prompt on the CTM server workstation to verify the patch installation:
You should see the following version string in the first line of output for the preceding command:
Cisco Transport Manager Server Version: 9.0 Build: 620 Patches: 5
Installing the CTM R9.0.0.620.5 Client Patch in Windows
The following steps describe how to patch a CTM client installation in Windows. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1 Locate the 620 patch directory that was extracted with the WinZip utility.
Step 2 Using the command prompt, go to the directory where the patch files were extracted, locate the client_patch.bat file, and enter the following command:
You can also use the Windows Explorer folder view to access the directory where the patch files were extracted and double-click the client_patch.bat file.
Step 3 Double-click the CTM 9.0 desktop icon or choose the CTM 9.0 Start menu shortcut to start the client.
Step 4 To verify the patch installation on the CTM client, do one of the following:
•Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version string in the About Cisco Transport Manager dialog box; then, click OK:
Client: 9.0 Build: 620 (client configuration size)
•(Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer. In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab. The Version field indicates the CTM client version number, which should read:
Installing the CTM R9.0.0.620.5 Client Patch in Solaris
The following steps describe how to patch a CTM client installation in Solaris. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1 Go to the 620 directory where the patch files were extracted with the unzip command.
Step 2 Enter the following command:
Step 3 Enter the following command to start the CTM client:
Step 4 To verify the patch installation on the CTM client, do one of the following:
•Choose Help > About Cisco Transport Manager in the Domain Explorer. You should see the following version string in the About Cisco Transport Manager dialog box; then, click OK:
Client: 9.0 Build: 620 (client configuration size)
•(Available only on specific user account types) Choose Administration > Control Panel in the Domain Explorer. In the Control Panel, click CTM to open the CTM Properties pane. Click the Client Configuration tab. The Version field indicates the CTM client version number, which should read:
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
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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:
unzip CTM9.0.0.550.patch.zip
For example, to extract the zip file to the /temp directory, enter:
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:
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:
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:
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
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
___ <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.
•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:
rm -r CiscoTransportManagerServer
rm CiscoTransportManagerServer9.0
ln -s CiscoTransportManagerServer-old-<timestamp> CiscoTransportManagerServer
rm CiscoTransportManagerServer.oldCTM
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.
•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.
•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.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
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:
sqlplus ctmanager/ctm123!
SQL> delete circuit_bs_tbl where cktstate=12;
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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.
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.
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
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 None.
•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.
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 Revert GNE 9.0.x versions shown as ENEs to version 8.5.x. Alternately, install the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 Revert GNE 9.0.x versions shown as ENEs to version 8.5.x. Alternately, install the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
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:
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•CSCuk55603
Symptom For nodes equipped with PPM-provisioned transponder and muxponder cards, the reported
Average Transmit Power value is incorrect.
Conditions If you open the real-time Physical PM table for a particular slot with "All" selected as the port, the Average Transmit Power value is 0.0 dBm. The correct value is -40 dBm, as reported in CTC. This problem applies to R4.7 and R5.0 NEs equipped with PPM-provisioned MXP_2.5G_10E, DMP_2.5G, or TXP_MR_10E cards.
Workaround Open the real-time Physical PM table for a particular slot and port. Do not select "All" as the port; rather, specify a particular port.
Miscellaneous
•CSCeg57848
Symptom The Equipment Inventory table shows TCC2P as TCC2.
Conditions If you open the Equipment Inventory table for an ONS 15454 SDH NE that contains TCC2P modules, the Actual Equipment Type field displays TCC2. The field should distinguish between TCC2 and TCC2P modules.
Workaround None.
•CSCin94007
Symptom CTM shows a blank password.
Conditions An unset password is shown as an empty password field, which therefore reveals the actual password.
Workaround Change the password of all NEs that have a blank password.
•CSCsb29625
Symptom When a new card is provisioned on a filler card on an ONS 15600 SDH NE, the actual
equipment type is blank and a Mismatch of Equipment (MEA) alarm is raised.
Conditions When a new card is provisioned on a filler card on an ONS 15600 SDH NE, the actual equipment type is blank in the Equipment Inventory table. The actual equipment type should report "Filler Card." Also, an MEA alarm is raised on the card. This problem applies only to ONS 15600 SDH NEs.
Workaround None.
•CSCsc61618
Symptom The file CTM Client Home/gcoutput, where CTM Client Home is your client location, is
unreadable.
Conditions When multiple instances of the CTM client are launched on the same Solaris or Windows machine, all instances of the client write GC data to the same output file. The output file becomes unreadable.
Workaround To avoid this problem, change the name of the file the clients write GC data to before launching a client instance.
To change the name of the GC data file on Windows systems:
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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 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. A PermGen OutOfMemoryException can also be found in the NE service logs.
Workaround Install the CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. Alternately, increase PermGen memory by modifying /opt/CiscoTransportManagerServer/bin/ jnet.sh:
•Replace -XX:MaxPermGen=128m with -XX:MaxPermGen=256m
•Replace -XX:PermGen=128m with -XX:PermGen=256m
•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.
CTM Server and Database Caveats
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch. 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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•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 CTM R9.0.0.620.5 patch. See Installing the CTM R9.0.0.620.5 Patch.
•CSCta23414
Symptom When installing the CTM R9.0.0.620.5 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 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 lightweight process (LWP)
creation when a user is in locked state.
Conditions See Symptom.
Workaround Disable user lockout in the Control Panel > Security Properties pane > CTM Security tab > Client Inactivity Timer Settings area.
•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 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 SMService.
Step 5
