Table Of Contents
Release Notes for Cisco Transport Manager Release 8.5
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
Adding the ONS 15310 CL R5.0.4 to the Supported NE Table
Adding the ONS 15310 CL R8.5.1 to the Supported NE Table
Adding the ONS 15310 MA R7.0.7 to the Supported NE Table
Adding the ONS 15310 MA R8.5.1 to the Supported NE Table
Adding the ONS 15310 MA R8.5.3 to the Supported NE Table
Adding the ONS 15327 R7.0.7 to the Supported NE Table
Adding the ONS 15454 SDH R5.0.4 to the Supported NE Table
Adding the ONS 15454 SDH R7.0.7 to the Supported NE Table
Adding the ONS 15454 SDH R8.5.1 to the Supported NE Table
Adding the ONS 15454 SDH R8.5.2 to the Supported NE Table
Adding the ONS 15454 SDH R8.5.3 to the Supported NE Table
Adding the ONS 15454 SONET R5.0.4 to the Supported NE Table
Adding the ONS 15454 SONET R7.0.7 to the Supported NE Table
Adding the ONS 15454 SONET R8.5.1 to the Supported NE Table
Adding the ONS 15454 SONET R8.5.2 to the Supported NE Table
Adding the ONS 15454 SONET R8.5.3 to the Supported NE Table
Adding the ONS 15600 SONET R5.0.4 to the Supported NE Table
Adding the MGX Voice Gateway R5.3.30 to the Supported NE Table
Third-Party Patches and Security Notices
CTM-Supported JRE and Apache Versions
(Optional) Upgrading to JRE Version 1.5.0_16
Upgrading the CTM R8.5 Server to JRE Version 1.5.0_16
Upgrading the CTM R8.5 Solaris Client to JRE Version 1.5.0_16
Upgrading the CTM R8.5 Windows Client to JRE Version 1.5.0_16
Resolved Caveats
Installing the CTM R8.5.0.430.3 Service Pack
Determining What CTM Patch Is Currently Installed in the CTM System
Backing Up the CTM Database Before Installing the CTM R8.5.0.430.3 Service Pack
Downloading the CTM R8.5.0.430.3 Service Pack
Installing the CTM R8.5.0.430.3 Server Service Pack on the Same or Separate Workstation(s)
Installing the CTM R8.5.0.430.3 Client Service Pack in Windows
Installing the CTM R8.5.0.430.3 Client Service Pack in Solaris
Upgrading to CTM R9.0 Using a Service Pack
Open Caveats
Installation and Upgrade Caveats
CTM Client Caveats
Alarm Management
Circuit and Link Management
User Management
Data Services
Domain Explorer
NE Explorer
Network Map
Performance Monitoring
Miscellaneous
CTM Server and Database Caveats
Cisco Transport Controller Caveats
High Availability Caveats
CTM GateWay/TL1 Caveats
CTM GateWay/CORBA Caveats
NE-Specific Caveats
Cisco MGX Voice Gateway
Cisco ONS 15216 EDFA
Cisco ONS 15302 and Cisco ONS 15305
Cisco ONS 15310
Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET
Cisco ONS 15454 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 8.5
December 1, 2010
These release notes describe the caveats for Cisco Transport Manager (CTM) Release 8.5. These release notes accompany the Cisco Transport Manager Release 8.5 User Guide and the Cisco Transport Manager Release 8.5 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 R8.5.0.430.3 Service Pack
•Open Caveats
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Introduction
Cisco Transport Manager is an advanced management system that provides functionality at the element and network management levels for Cisco optical network elements (NEs) and switches. CTM supports fault, configuration, performance, and security management functional areas. CTM also serves as a foundation for integration into a larger overall Operations Support System (OSS) environment by providing northbound gateway interfaces to higher layer management systems.
In Release 8.5, 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 R8.5.
Table 1 New Features in CTM R8.5
New Feature
|
Description
|
Server Platform Enhancements
|
Support for Oracle 10g
|
The CTM database uses Oracle 10g for Standard Edition and Enterprise Edition database installations.
|
Basic external authentication
|
CTM supports basic external username and password authentication via eTrust SiteMinder, a third-party application. Users with the appropriate privileges can enable or disable external authentication.
Note The license for basic external authentication is sold separately. If you are using this feature in a production environment, you must purchase a license.
|
Client Enhancements
|
Scheduled inventory export
|
You can schedule the export of the Equipment Inventory table contents to a flat file. This feature was introduced in CTM R8.0 for certain NEs and is expanded in CTM R8.5 to all NEs that support inventory retrieval.
|
Optical Enhancements
|
Support for Cisco Transport Controller (CTC)-based NE Release 8.5
|
Expands CTM's scope to include operations, administration, management, and provisioning (OAM&P) for the following CTC-based NE releases:
•ONS 15310 CL Release 8.5
•ONS 15310 MA Release 8.5
•ONS 15454 MSPP (SONET/SDH) Release 8.5
•ONS 15454 MSTP (ANSI/ETSI) Release 8.5
|
Support for new optical cards
|
CTM manages the following new cards on optical devices:
•CE-MR-10—ONS 15454 SONET, ONS 15454 SDH
•ML-MR-10—ONS 15454 SONET, ONS 15454 SDH
•ADM_10G—ONS 15454 SDH, ONS 15454 MSTP, and ONS 15454 MSPP
•OPT-AMP-C—ONS 15454 MSTP
•CE-MR-6—ONS 15310 MA SONET
Note Support for the CE-MR-6 card is available only after installing CTM R8.5.0.410.3 or later.
|
Even band support
|
Management of autodiscovered, manual, and patchcord links and DWDM optical channel network connection (OCHNC) circuits is extended to the physical termination points (PTPs) and connection termination points (CTPs) introduced with the following 40-channel even-band cards:
•15454-40-WSS-CE—40-channel wavelength selective switch-C-band (Even)
•15454-40-DMX-CE—40-channel demultiplexer-C-band (Even)
|
Ring information shown in the tooltip
|
During manual circuit routing, you can point to a link and view the following information in the tooltip:
•Port name
•Shared risk link group (SRLG)
•Name (alias) of the link—If the link alias is the same as the link name, the tooltip shows only the link alias. Otherwise, the tooltip shows both the link name and link alias.
•Ring ID (if the link is part of a BLSR or MS-SPRing)
|
Provision CCAT or VCAT circuits using CE-MR-10 cards in Manual mode
|
Allows you to create contiguous concatenation (CCAT) or virtual concatenation (VCAT) circuits or manage members of existing VCAT circuits by using CE-MR-10 cards in Manual mode as source or destination endpoints.
|
Data Enhancements
|
Ability to find Layer 2 topologies from the Domain Explorer
|
You can filter the Domain Explorer window to find specific Layer 2 topologies from among all of the topologies in the network. Results are displayed in the Layer 2 Topology table.
|
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 8.5.
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 15305 CTC R3.0.6
–ONS 15310 CL R8.6
–ONS 15310 CL R8.6.1
–ONS 15310 MA R8.5.4
–ONS 15310 MA R8.6
–ONS 15310 MA R8.6.1
–ONS 15327 R4.1.3
–ONS 15327 R4.1.6
–ONS 15327 R4.6.2
–ONS 15454 SDH R4.1.3
–ONS 15454 SDH R4.6.2
–ONS 15454 SDH R8.5.4
–ONS 15454 SDH R8.6
–ONS 15454 SDH R8.6.1
–ONS 15454 SONET R4.1.3
–ONS 15454 SONET R4.1.6
–ONS 15454 SONET R4.6.2
–ONS 15454 SONET R8.5.4
–ONS 15454 SONET R8.6
–ONS 15454 SONET R8.6.1
•Manually added to CTM:
Note You can manually add new NE software releases to CTM R8.5.0.231 or later.
–ONS 15305 R2.0.2
–ONS 15310 CL R5.0.4
–ONS 15310 CL R8.5.1
–ONS 15310 MA R7.0.7
–ONS 15310 MA R8.5.1
–ONS 15310 MA R8.5.3
–ONS 15327 R7.0.7
–ONS 15454 SDH R5.0.4
–ONS 15454 SDH R7.0.7
–ONS 15454 SDH R8.5.1
–ONS 15454 SDH R8.5.2
–ONS 15454 SDH R8.5.3
–ONS 15454 SONET R5.0.4
–ONS 15454 SONET R7.0.7
–ONS 15454 SONET R8.5.1
–ONS 15454 SONET R8.5.2
–ONS 15454 SONET R8.5.3
–ONS 15600 SONET R5.0.4
–MGX Voice Gateway R5.3.30
Sections and Caveats Added
The following sections and caveats were added to the release notes:
•The section CTM-Supported JRE and Apache Versions was added to list the JRE and Apache versions supported in CTM R8.5.
•The section Third-Party Patches and Security Notices was added.
•The section Installing the CTM R8.5.0.430.3 Service Pack was added.
•The following sections were added to describe how to add support for new NE releases:
–Adding the ONS 15305 R2.0.2 to the Supported NE Table
–Adding the ONS 15310 CL R5.0.4 to the Supported NE Table
–Adding the ONS 15310 CL R8.5.1 to the Supported NE Table
–Adding the ONS 15310 MA R7.0.7 to the Supported NE Table
–Adding the ONS 15310 MA R8.5.1 to the Supported NE Table
–Adding the ONS 15310 MA R8.5.3 to the Supported NE Table
–Adding the ONS 15327 R7.0.7 to the Supported NE Table
–Adding the ONS 15454 SDH R5.0.4 to the Supported NE Table
–Adding the ONS 15454 SDH R7.0.7 to the Supported NE Table
–Adding the ONS 15454 SDH R8.5.1 to the Supported NE Table
–Adding the ONS 15454 SDH R8.5.2 to the Supported NE Table
–Adding the ONS 15454 SDH R8.5.3 to the Supported NE Table
–Adding the ONS 15454 SONET R5.0.4 to the Supported NE Table
–Adding the ONS 15454 SONET R7.0.7 to the Supported NE Table
–Adding the ONS 15454 SONET R8.5.1 to the Supported NE Table
–Adding the ONS 15454 SONET R8.5.2 to the Supported NE Table
–Adding the ONS 15454 SONET R8.5.3 to the Supported NE Table
–Adding the MGX Voice Gateway R5.3.30 to the Supported NE Table
•The following caveats were added:
–CSCse91435
–CSCsh98117
–CSCsl34542
–CSCsl69043
–CSCsl84311
–CSCsm14884
–CSCsm46882
–CSCsm64677
–CSCso07731
–CSCso35202
–CSCso80680
–CSCso92761
–CSCsq50589
–CSCsq78385
–CSCsq91933
–CSCsr24435
–CSCsr52735
–CSCsr55311
–CSCsr55335
–CSCsr67129
–CSCsr70890
–CSCsr71261
–CSCsr71468
–CSCsu24300
–CSCsu26103
–CSCsu30979
–CSCsu54034
–CSCsu54724
–CSCsu88903
–CSCsu82028
–CSCsu88218
–CSCsu96767
–CSCsv07090
–CSCsv14849
–CSCsw28308
–CSCsw37547
–CSCsw48791
–CSCsw51242
–CSCsw53135
–CSCsw53170
–CSCsw61167
–CSCsw61380
–CSCsw62624
–CSCsy01229
–CSCsy18486
–CSCsy66604
–CSCsy69011
–CSCsy79681
–CSCsy95377
–CSCsz26474
–CSCsz58653
–CSCsz72892
–CSCta27875
–CSCta93568
–CSCtb25595
–CSCtb54366
–CSCtb62164
–CSCtb65065
–CSCtb67646
–CSCtb75511
–CSCtb81830
–CSCtb83268
–CSCtb97851
–CSCtc33026
–CSCtc45424
–CSCtc54674
–CSCtd01497
–CSCtd50613
–CSCtd60987
–CSCtd78067
–CSCtf08332
–CSCtg80725
–CSCth87771
–CSCth97940
Sections Removed
The following sections were removed, because the CTM R8.5.0.430.3 service pack inherits all bug fixes and obsoletes these earlier patches and service packs:
•Installing the CTM R8.5.0.350.1 Patch
•Installing the CTM R8.5.0.359.1 Patch
•Installing the CTM R8.5.0.361.2 Patch
•Installing the CTM R8.5.0.368.3 Patch
•Installing the CTM R8.5.0.375.2 Patch
•Installing the CTM R8.5.0.378.3 Patch
•Installing the CTM R8.5.0.381.3 Patch
•Installing the CTM R8.5.0.384.3 Patch
•Installing the CTM R8.5.0.387.6 Service Pack
•Installing the CTM R8.5.0.390.3 Patch
•Installing the CTM R8.5.0.392.2 Patch
•Installing the CTM R8.5.0.410.3 Service Pack
CTM-Supported NE Software Releases
The following table lists the NE software releases supported in CTM R8.5.
Caution Before updating the software image on an NE, check the following table to verify whether the NE software version is supported in this CTM release. If you add an unsupported NE software version, the CTM server might not communicate with one or more NEs in the domain, causing erroneous behavior.
Table 2 CTM-Supported NE Software Releases
Product
|
Software Release
|
NE Version String
|
ONS 15216 100-GHz OADM1/2/4
|
Release 2.2.2
|
soadma.out-Ver2.2.2
|
Release 2.2.2
|
soadmb.out-Ver2.2.2
|
Release 2.2.3
|
soadma.out-Ver2.2.3
|
Release 2.2.3
|
soadmb.out-Ver2.2.3
|
ONS 15216 200-GHz OADM1/2
|
Passive
|
1.0
|
ONS 15216 DCU
|
Passive
|
2.0
|
ONS 15216 DWDM Filter (including ONS 15216 100-GHz Red/Blue Filters and ONS 15216 200-GHz Red/Blue Filters)
|
Release 2.1
|
2.1
|
ONS 15216 EDFA1
|
Passive
|
1.0
|
ONS 15216 EDFA2
|
Release 2.3
|
v2.3.0
|
Release 2.4
|
v2.4.0
|
ONS 15216 EDFA3
|
Release 1.1
|
01.01.00
|
ONS 15216 FlexLayer
|
Passive
|
1.0
|
ONS 15216 OSC
|
Passive
|
2.0
|
ONS 15302
|
Release 2.0.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.62
|
04.60-X08D-26.11
|
ONS 15310 CL
|
Release 5.0.43
|
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.04
|
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.14
|
08.51-008B-14.13
|
Release 8.65
|
08.60-009B-11.08
|
Release 8.6.16
|
08.61-010F-07.11
|
ONS 15310 MA
|
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.77
|
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.18
|
08.51-008B-14.13
|
Release 8.5.39
|
08.53-008J-17.07
|
Release 8.5.410
|
08.54-010D-30.09
|
Release 8.611
|
08.60-009B-11.08
|
Release 8.6.112
|
08.61-010F-07.11
|
ONS 15327
|
Release 4.1.313
|
04.13-003L-19.01
|
Release 4.1.4
|
04.14-004C-09.23
|
Release 4.1.614
|
04.16-004I-10.23
|
Release 4.1.82
|
04.182-006-L2805
|
Release 4.6.215
|
04.62-004E-23.20
|
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.04
|
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.716
|
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 SDH
|
Release 4.1.317
|
04.13-003L-19.01
|
Release 4.6.218
|
04.62-004E-23.20
|
Release 5.0.419
|
05.04-005G-13.18
|
Release 5.0.6
|
05.06-005H-23.18
|
Release 6.0
|
06.00-005H-18.21
|
Release 6.0.1
|
06.01-005L-10.05
|
Release 6.0.3
|
06.03-007D-06.04
|
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.720
|
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
|
08.50-P07I-19.18
|
Release 8.5.121
|
08.51-008B-14.13
|
Release 8.5.222
|
08.52-008E-25.04
|
Release 8.5.323
|
08.53-008J-17.07
|
Release 8.5.424
|
08.54-010C-12.19
|
Release 8.625
|
08.60-009B-11.08
|
Release 8.6.126
|
08.61-010F-07.11
|
ONS 15454 SONET
|
Release 4.1.327
|
04.13-003L-19.01
|
Release 4.1.4
|
04.14-004C-09.23
|
Release 4.1.628
|
04.16-004I-10.23
|
Release 4.1.82
|
04.182-006-L2805
|
Release 4.6.229
|
04.62-004E-23.20
|
Release 4.7 (MSTP only)
|
04.70-004I-14.01
|
Release 5.0.430
|
05.04-005G-13.18
|
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.04
|
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.731
|
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.132
|
08.51-008B-14.13
|
Release 8.5.233
|
08.52-008E-25.04
|
Release 8.5.3 34
|
08.53-008J-17.07
|
Release 8.5.435
|
08.54-010C-12.19
|
Release 8.636
|
08.60-009B-11.08
|
Release 8.6.137
|
08.61-010F-07.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 SDH
|
Release 1.4
|
01.40-004A-15.18
|
Release 8.0
|
08.00-007A-27.16
|
ONS 15600 SONET
|
Release 1.3.1
Note Release 1.3.1 is the same as 1.3.0.
|
01.30-004D-01.20
|
Release 5.0.438
|
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.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
|
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.2.10
|
5.2.10
|
Release 5.3.10
|
5.3.10
|
Release 5.3.3039
|
5.3.30
|
Release 5.4.00
|
5.4.00
|
Voice-Enabled Cisco MGX 8850 Multiservice Switch
|
Release 5.2.10
|
5.2.10
|
Release 5.3.10
|
5.3.10
|
Release 5.3.30
Note See footnote about adding support for this software release.
|
5.3.30
|
Release 5.4.00
|
5.4.00
|
Voice-Enabled Cisco MGX 8830 Multiservice Switch
|
Release 5.2.10
|
5.2.10
|
Release 5.3.10
|
5.3.10
|
Release 5.3.30
Note See footnote about adding support for this software release.
|
5.3.30
|
Release 5.4.00
|
5.4.00
|
VISM-PR
|
Release 3.3.20
|
3.3.20
|
Release 3.3.25
|
3.3.25
|
Release 3.3.30
|
3.3.30
|
VXSM
|
Release 5.2.10
|
5.2.10
|
Release 5.3.10
|
5.3.10
|
Release 5.3.30
|
5.3.30
|
Release 5.4.0040
|
5.4.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.
Adding the ONS 15310 CL R5.0.4 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R5.0.4, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 CL" as the NE model, "05.08-006J-16.07" as the software version, and "15310 CL 5.08" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 05.04-005G-13.18 in the Software Version field. Change the Version Name field to 15310 CL 5.04.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15310 CL R8.5.1 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R8.5.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 CL" as the NE model, "08.50-007I-19.18" as the software version, and "15310 CL 8.50" 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 08.51-008B-14.13 in the Software Version field. Change the Version Name field to 15310 CL 8.51.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15310 MA R7.0.7 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R7.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 MA" as the NE model, "07.04-007A-08.16" as the software version, and "15310 MA 7.04" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 07.07-007L-03.20 in the Software Version field. Change the Version Name field to 15310 MA 7.07.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15310 MA R8.5.1 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R8.5.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 MA" as the NE model, "08.50-007I-19.18" as the software version, and "15310 MA 8.50" 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 08.51-008B-14.13 in the Software Version field. Change the Version Name field to 15310 MA 8.51.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15310 MA R8.5.3 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R8.5.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 MA" as the NE model, "08.50-007I-19.18" as the software version, and "15310 MA 8.50" 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 08.53-008J-17.07 in the Software Version field. Change the Version Name field to 15310 MA 8.53.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15327 R7.0.7 to the Supported NE Table
In order for CTM to support the ONS 15327 R7.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15327" as the NE model, "07.04-007A-08.16" as the software version, and "15327 7.04" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 07.07-007L-03.20 in the Software Version field. Change the Version Name field to 15327 7.07.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SDH R5.0.4 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R5.0.4, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "04.13-003L-19.01" as the software version, and "15454 SDH 4.13" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 05.04-005G-13.18 in the Software Version field. Change the Version Name field to 15454 SDH 5.04.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SDH R7.0.7 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R7.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "07.04-007A-08.16" as the software version, and "15454 SDH 7.04" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 07.07-007L-03.20 in the Software Version field. Change the Version Name field to 15454 SDH 7.07.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SDH R8.5.1 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R8.5.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "08.50-007I-19.18" as the software version, and "15454 SDH 8.50" 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 08.51-008B-14.13 in the Software Version field. Change the Version Name field to 15454 SDH 8.51.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SDH R8.5.2 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R8.5.2, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "08.50-007I-19.18" as the software version, and "15454 SDH 8.50" 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 08.52-008E-25.04 in the Software Version field. Change the Version Name field to 15454 SDH 8.52.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SDH R8.5.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R8.5.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454 SDH" as the NE model, "08.50-007I-19.18" as the software version, and "15454 SDH 8.50" 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 08.53-008J-17.07 in the Software Version field. Change the Version Name field to 15454 SDH 8.53.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SONET R5.0.4 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R5.0.4, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454" as the NE model, "04.70-004I-14.01" as the software version, and "15454 4.70" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 05.04-005G-13.18 in the Software Version field. Change the Version Name field to 15454 5.04.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SONET R7.0.7 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R7.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454" as the NE model, "07.04-007A-08.16" as the software version, and "15454 7.04" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 07.07-007L-03.20 in the Software Version field. Change the Version Name field to 15454 7.07.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SONET R8.5.1 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R8.5.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454" as the NE model, "08.50-007I-19.18" as the software version, and "15454 8.50" 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 08.51-008B-14.13 in the Software Version field. Change the Version Name field to 15454 8.51.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SONET R8.5.2 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R8.5.2, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454" as the NE model, "08.50-007I-19.18" as the software version, and "15454 8.50" 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 08.52-008E-25.04 in the Software Version field. Change the Version Name field to 15454 8.52.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15454 SONET R8.5.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R8.5.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15454" as the NE model, "08.50-007I-19.18" as the software version, and "15454 8.50" 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 08.53-008J-17.07 in the Software Version field. Change the Version Name field to 15454 8.53.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the ONS 15600 SONET R5.0.4 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R5.0.4, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15600" as the NE model, "01.30-004D-01.20" as the software version, and "15600 1.30" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 05.04-005G-13.18 in the Software Version field. Change the Version Name field to 15600 5.04.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Adding the MGX Voice Gateway R5.3.30 to the Supported NE Table
In order for CTM to support the MGX Voice Gateway R5.3.30, you must add the software version to the Supported NE table. Complete the following steps:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco MGX Voice Gateway" as the NE model, "5.2(10.0)" or "5.3(10.0)" as the software version, and "MGX VG 5.2(10.0)" or "MGX VG 5.3(10.0)" as the version name.
Step 3 Choose Edit > Add (or click the Add Supported NE tool). The Add Supported NE dialog box opens.
Step 4 Enter 5.3(30.0) in the Software Version field. Change the Version Name field to MGX VG 5.3(30.0).
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Third-Party Patches and Security Notices
Cisco reviews the known Oracle patch alerts every quarter, including patches for security breaches. If any Oracle patch applies to CTM or its components, Cisco tests the Oracle patch and includes it as a requirement for the next CTM patch. Cisco also conducts quarterly reviews of other third-party software products that CTM uses, such as Solaris, Apache, and Java.
CTM-Supported JRE and Apache Versions
The following tables list the JRE and Apache versions supported in CTM R8.5.
Table 3 CTM-Supported JRE Versions
JRE Version
|
Caveat ID
|
Caveat
|
Comment
|
1.5.0_12
|
—
|
—
|
This JRE version was used when CTM R8.5 was released.
|
1.5.0_16
|
CSCsq11152
|
Due to security issues, CTM must support a new JRE version.
|
This JRE version was supported starting in CTM R8.5.0.368.3. This JRE version is optional; it is not mandatory that you upgrade to JRE version 1.5.0_16. See (Optional) Upgrading to JRE Version 1.5.0_16.
|
Table 4 CTM-Supported Apache Versions
Apache Version
|
Caveat ID
|
Caveat
|
Comment
|
2.0.43
|
—
|
—
|
This Apache version was used when CTM R8.5 was released.
|
2.0.61
|
CSCsk44773
|
Due to security issues, CTM must support Apache web server version 2.0.61.
|
This Apache version was supported starting in CTM R8.5.0.350.1.
|
2.0.63
|
CSCsq32073
|
Due to security issues, CTM must support Apache web server version 2.0.63.
|
This Apache version was supported starting in CTM R8.5.0.368.3.
|
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 R8.5.0.387.6.
|
(Optional) Upgrading to JRE Version 1.5.0_16
CTM R8.5 uses JRE version 1.5. See Table 3 for the latest supported JRE versions.
This section describes how to upgrade to JRE version 1.5.0_16. It is not mandatory that you upgrade to JRE version 1.5.0_16.
Upgrading the CTM R8.5 Server to JRE Version 1.5.0_16
Step 1 The CTM JRE upgrade tool is packaged with the latest CTM R8.5 patch or service pack as a single file called CTM85_JRE_UPGRADE_1_5.zip. After applying the latest CTM R8.5 patch or service pack, locate the CTM85_JRE_UPGRADE_1_5.zip file in the /opt/CiscoTransportManagerServer/bin directory.
Step 2 As the root UNIX user, enter the following command to shut down the CTM server:
Step 3 Copy the CTM85_JRE_UPGRADE_1_5.zip file to the /tmp directory.
Step 4 Enter the following commands to unzip the file:
# unzip CTM85_JRE_UPGRADE_1_5.zip
This creates a new directory called JRE.
Step 5 Enter the following command to enter the directory:
Step 6 Go to http://java.sun.com/javase/downloads/index_jdk5.jsp and download Java Runtime Environment (JRE) 5.0 Update 16.
Step 7 Save the file to /tmp/JRE.
Step 8 Verify that the correct JRE version is installed. You must use the Solaris SPARC 32-bit self-extracting file named jre-1_5_0_16-solaris-sparc.sh.
Caution If you install the wrong JRE version, CTM does not start.
Step 9 Enter the following commands to copy the installer to the JRE directory and add executable permissions for the file:
# cp jre-1_5_0_16-solaris-sparc.sh /tmp/JRE
# chmod +x jre-1_5_0_16-solaris-sparc.sh
Step 10 Enter the following command to update the current JRE version to 1.5.0_16:
# ./installNewJre.sh jre-1_5_0_16-solaris-sparc.sh
Step 11 Enter yes at the following license agreement prompt:
# Do you agree to the above license terms? [yes or no]
Step 12 All required CTM scripts are updated to point to the new JRE version. Enter the following commands to check that the JRE has been updated correctly:
# cd /opt/CiscoTransportManagerServer/bin
In the output, you should see:
CLASSPATH=/opt/jre1.5.0_16/lib/rt.jar:$OPENFUSION_HOME/classes:$OPENFUSION_LIB/avalon-fram
ework.jar:$OPENFUSION_LIB/logkit.jar:$OPENFUSION_LIB/jacorb.jar:$CLASSPATH
Also, the following listings should point to the new JRE path:
ls -ltra /usr/bin/javaorb
ls -ltra /usr/bin/javacorbagw
ls -ltra /usr/bin/ctmsjava
Step 13 Enter the following command to start the CTM server:
Upgrading the CTM R8.5 Solaris Client to JRE Version 1.5.0_16
Step 1 If the CTM client is installed on the same workstation as the CTM server, and if you completed the previous section to upgrade the CTM server to JRE version 1.5.0_16, the CTM client was upgraded automatically to JRE version 1.5.0_16. The installNewJre.sh script upgrades the client-side JRE when it upgrades the server JRE. In this case, skip to Step 2.
If the CTM client and the CTM server are installed on separate workstations, complete the following substeps to upgrade the CTM client to JRE version 1.5.0_16:
a. As the root UNIX user, use File Transfer Protocol (FTP) to transfer CTM85_JRE_UPGRADE_1_5.zip from the /opt/CiscoTransportManagerServer/bin directory on the server to the client workstation.
b. Copy the CTM85_JRE_UPGRADE_1_5.zip file to the /tmp directory.
c. Enter the following commands to unzip the file:
# unzip CTM85_JRE_UPGRADE_1_5.zip
This creates a new directory called JRE.
d. Enter the following command to enter the directory:
e. Go to http://java.sun.com/javase/downloads/index_jdk5.jsp and download Java Runtime Environment (JRE) 5.0 Update 16.
f. Save the file to /tmp/JRE.
g. Verify that the correct JRE version is installed. You must use the Solaris SPARC 32-bit self-extracting file named jre-1_5_0_16-solaris-sparc.sh.
h. Enter the following commands to copy the installer to the JRE directory and add executable permissions for the file:
# cp jre-1_5_0_16-solaris-sparc.sh /tmp/JRE
# chmod +x jre-1_5_0_16-solaris-sparc.sh
i. Enter the following command to update the JRE version to 1.5.0_16:
# ./installNewJre.sh jre-1_5_0_16-solaris-sparc.sh
j. Enter yes at the following license agreement prompt:
# Do you agree to the above license terms? [yes or no]
Step 2 All required CTM scripts are updated to point to the new JRE version. Enter the following commands to check that the JRE has been updated correctly:
# cd /opt/CiscoTransportManagerClient
Step 3 Enter the following command to check the JRE version used by the CTM client:
In the output, you should see:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Server VM (build 1.5.0_16-b02, mixed mode)
Upgrading the CTM R8.5 Windows Client to JRE Version 1.5.0_16
Step 1 Go to http://java.sun.com/javase/downloads/index_jdk5.jsp and download Java Runtime Environment (JRE) 5.0 Update 16. The JRE installable for Windows is named jre-1_5_0_16-windows-i586-p.exe.
Step 2 Go to C:\Program Files\Java\ and copy the directory with the latest JRE version, jre1.5.0_16.
Step 3 Paste it into the CTM client directory C:\Cisco\TransportManagerClient8_5.
Step 4 Rename the original JRE directory in C:\Cisco\TransportManagerClient8_5 as jre.orig.
Step 5 Rename the new JRE directory (jre1.5.0_16) that you pasted into the CTM client directory as jre.
Step 6 Open a command prompt by choosing Start > Run and entering cmd.
Step 7 Enter the following command to change directories to jre\bin:
# cd C:\Cisco\TransportManagerClient8_5\jre\bin
Step 8 Enter the following command:
In the output, you should see:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Server VM (build 1.5.0_16-b04, mixed mode)
Resolved Caveats
The following table lists caveats that are resolved as of the latest CTM R8.5 patch or service pack.
Table 5 Caveats Resolved in CTM R8.5
Caveat ID
|
Caveat
|
CSCeh15110
|
The CoS accounting command for Ethernet interfaces is not cleared when VLANs are deleted. (Related caveat ID: CSCse91457.)
|
CSCsb62632
|
The Domain Explorer does not show the correct alarm status for MGX NEs. The Alarm Browser does not show connection-related alarms. (Related caveat ID: CSCsh96119.)
|
CSCsc46226
|
The HdlcRxAborts counter is shown as 0 instead of blank.
|
CSCsc52186
|
CTM does not report link up/down alarms.
|
CSCsc66935
|
Rack 1 cannot be dragged to Rack 8.
|
CSCsd09757
|
Discovered NEs go to the wrong group.
|
CSCsd11028
|
Customer information is not sorted correctly when table headers are used for sorting.
|
CSCsd21128
|
Alarm profile management operations fail.
|
CSCsd37522
|
When you try to launch the NE Explorer by double-clicking a gateway network element (GNE) node, an error message is returned.
|
CSCse40480
|
Circuits do not appear in the Circuit table after deleting and recreating circuits.
|
CSCse59300
|
CTM does not update RPM-XF traps in real time.
|
CSCse61127
|
For the ONS 15216 EDFA2, the NE alarm time is incorrect in the Alarm Browser and Alarm Log.
|
CSCse91332
|
CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCse94192
|
While adding NE defaults from one NE to another, an IDL/config exception is generated.
|
CSCse97179
|
The CTM Dashboard does not show tooltips.
|
CSCsg03634
|
Any provisioning operation in the Ports tab of the NE Explorer for ADM_10G cards causes CTM to refresh the property sheet and set focus on the SONET Line tab.
|
CSCsg21686
|
The Reference List subtab under the Timing tab of the NE Explorer does not automatically refresh.
|
CSCsg22838
|
A "Process restarted" event is generated continuously and must be cleared manually from the Alarm Browser.
|
CSCsg23173
|
When you click Cancel in the Line tab of the NE Explorer for ADM_10G cards, you are directed to the Ethernet subtab.
|
CSCsg34257
|
Spans for cards that are in 802.17 resilient packet ring (RPR) mode are shown as 0 and 1 in the Circuit Creation wizard, Circuit table, and Link table. Spans should show RPR East and RPR West.
|
CSCsg53530
|
Resync Alarm activity is not traced in the Audit Log.
|
CSCsg55562
|
The Equipment Inventory table does not reflect the changes made when shelves in a multishelf NE (MSNE) are moved between racks.
|
CSCsg57005
|
An IP SLA configured interface displays an incorrect subnet mask.
|
CSCsg60513
|
OTN G.709 performance monitoring (PM) tables display blank rows for interlink ports on ADM_10G cards.
|
CSCsg70987
|
The layer rate of an SDCC link shown in the Network Map or Link table is incorrect. It should be STM-16 instead of STM-64.
|
CSCsg79420
|
The ONS 15216 EDFA3 NE and configuration synchronization information are not displayed in the Self Monitor table.
|
CSCsg79457
|
SVLAN data is not updated after adding a PPM trunk that is created on GE_XP or 10GE_XP cards.
|
CSCsg79872
|
The Enable Shell Password check box is dimmed in CTM.
|
CSCsg83043
|
The RS-OFS counter is shown as N/A in RS PM tables.
|
CSCsg83062
|
Cannot create or delete patchcords on ONS 15327 NEs.
|
CSCsg85385
|
After adding NEs to CTM, every time you select the NE, a popup window appears, asking you to save changes made to the property sheet.
|
CSCsg87580
|
The SetTCATpParameters application program interface (API) does not work on ONS 15454 DWDM cards. This problem occurs in both SONET and SDH configurations.
|
CSCsg87585
|
The getTCAtpParameters API does not work on ONS 15454 DWDM cards. This problem occurs in both SONET and SDH configurations.
|
CSCsg91696
|
Cannot monitor the 40WSS_CE and 40DMX_CE cards after deleting them and then reprovisioning them in the NE Explorer.
|
CSCsg92911
|
Cannot perform get/set operations on hardware that is running an SNMP agent.
|
CSCsh18645
|
The file system becomes full when you repeatedly cancel an upgrade process and then restart it.
|
CSCsh33254
|
End network elements (ENEs) go down but come up a long time after changing the IP address of a GNE.
|
CSCsh40095
|
The layer for composite links is zero.
|
CSCsh51513
|
CTM requires too much time to mark an ONS 15454 as Out of Service and then In Service.
|
CSCsh51790
|
A tunnel does not open because of unknown errors.
|
CSCsh53496
|
When circuits are created from CTC, CTM discovers the circuits but displays their circuit alias name as Unknown. The circuit name is correct.
|
CSCsh57727
|
The RPR-IEEE0 protection card interface is not enabled when you create 802.17 RPR L2 topologies.
|
CSCsh60556
|
Cannot specify the admin SSM value of optical cards in the Line tab of the NE Explorer. Only six attributes are displayed instead of ten.
|
CSCsh60776
|
CTC shows ten possible values for the Admin SSM field while CTM shows only eight possible values. The missing possible values in CTM are transit node clock (TNC) and stratum 3E (ST3E).
|
CSCsh62458
|
The IP SLA delete operation fails intermittently.
|
CSCsh64385
|
Cannot set the wavelength for trunk ports on 10GE_XP and GE_XP cards that are provisioned as L2 over DWDM.
|
CSCsh64456
|
Cannot set signal degrade (SD) and signal failure (SF) values for low-order (LO) circuits.
|
CSCsh66343
|
The Create Link wizard does not allow you to select mux/demux ports of ONS 15454 MSTP NEs as endpoints of physical, unidirectional, manual link types. The mux/demux endpoints are not available even if the mux/demux cards are provisioned on the ONS 15454 MSTP NEs.
|
CSCsh67841
|
GNEs are shown as ENEs after changing the IP address of the GNE.
|
CSCsh67863
|
NEs do not change to In Service state.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsh69456
|
The TL1 interface contains junk characters when you launch it on an NE.
|
CSCsh69527
|
The getAllEquipment API does not retrieve the new configuration after changing the multishelf node configuration.
|
CSCsh71080
|
Cannot customize the Link Utilization table view.
|
CSCsh71549
|
SONET/SDH composite links are removed from the Link table when one of the composite links becomes invalid.
|
CSCsh72595
|
The following problems are observed in the Configuration Center > VBD tab > Event Profile category:
•You can select v110 as the event index type for VXSM images earlier than R5.4. The v110 option should only be available for VXSM images R5.4 and later.
•When the event handle type is None for VXSM images R5.4 and later, the event profile index should be dimmed but the GUI allows you to modify values using values 1 to 25.
|
CSCsh72631
|
In a scalability setup with approximately 3000 nodes, CTM GateWay/TL1 does not respond to commands with the CTM domain as the target ID (TID). The commands with the node as the TID work correctly.
|
CSCsh72874
|
The protected port's administration state is not updated after creating an STS circuit that connects the ADM_10G trunk ports.
|
CSCsh74746
|
Protected ports do not go into In Service state when creating SDCCs.
|
CSCsh76335
|
OCHNC-based circuits cannot be automatically routed even if all the required nodes and links are available.
|
CSCsh77519
|
Some ML cards are not listed in the Add/Remove Cards wizard.
|
CSCsh77603
|
ENEs of tunnel network elements (TNEs) take a long time to come up.
|
CSCsh77770
|
Cannot select side constraints in the Routing Preferences pane of the Circuit wizard to change the sequence of the nodes in a routing path. An error message is displayed: "EID-932: Failed to route the circuit."
|
CSCsh77880
|
The J1 path trace option is not available in the popup menu on ports listed in the Circuit Trace window.
|
CSCsh77907
|
Composite net links are invalid after deleting and then adding back GCC or DCC terminations.
|
CSCsh77983
|
Links between SONET nodes are not discovered after disconnecting DCN. When this happens, circuits go into Partial state and you cannot provision the circuits using the affected links.
|
CSCsh78003
|
CTM client freezes for about one minute. Afterward, the POS tab information displays correctly in the NE Explorer.
|
CSCsh78011
|
The CTM GUI freezes for approximately 30 seconds when you change the ML-series card's hostname using CTM. Afterward, the hostname is successfully changed in the ML-series card.
|
CSCsh78070
|
The circuit name alias shows .xxxxxxxxxxxxx when you add a card to an existing topology.
|
CSCsh78085
|
A CTM GateWay/CORBA API reports an incorrect CTP string of STS-24c circuits that involve a GE port of an ADM_10G card. For example, if the CTP string of an STS-24c circuit that is created in CTM is /sts24c_vc4_8c=1 -r=-1 and it is used to create an STS-24c circuit using a CTM GateWay/CORBA API, the following error message is displayed: "To create SNC with layer rate - sts24c, you must select OC48 or OC 192."
|
CSCsh78187
|
The L2 topology goes into Incomplete state when you add cards to a large RPR ring using the Add Card option in the NE Explorer. A large RPR ring typically contains 10 to 15 ML-series cards.
|
CSCsh78251
|
It takes too long to create, discover, and configure large RPR rings that contain 10 to 15 ML-series cards.
|
CSCsh78449
|
The PM Query by NE Model wizard is available for ONS 15305 R3.x NEs.
|
CSCsh79196
|
Cannot edit Foreign and Foreign IP fields when creating an SDCC or GCC.
|
CSCsh79344
|
The Lock On button is not available on working ports of ADM_10G cards.
|
CSCsh79618
|
When you use the createSNC API and specify the correct CTP when creating an STS circuit that includes an OC-xx port configured as SDH, an error message is displayed: "Source CTP is not available." This problem occurs in the CTM GateWay/CORBA interface.
|
CSCsh79827
|
An existing GCC termination that is related to a TXP card becomes invalid after creating a new GCC termination.
|
CSCsh80594
|
Cannot set AIS threshold values in the BITS OUT Facilities area of the NE Explorer.
|
CSCsh80798
|
Cannot delete the trunk port rate on ADM_10G cards.
|
CSCsh80894
|
An error occurs and the graph of PM data is not displayed when you remove the Time Stamp column from the PM table, save the customized view, and then close and reopen the PM table.
|
CSCsh81007
|
Only 32 wavelengths in the C-band can be provisioned over trunk ports on ADM_10G and GE_XP cards.
|
CSCsh82631
|
The NEs in a GNE-ENE setup do not synchronize correctly when you:
1. Mark the NEs as Out of Service.
2. Delete the NEs.
3. Undelete the NEs from the Deleted Network Elements group.
4. Mark the NEs as In Service.
|
CSCsh84176
|
Even if a new NGNE IP address is specified during a Modify Tunnel operation, CTM still uses the old IP address of the NGNE to create a tunnel.
|
CSCsh85850
|
After changing the shell access state of an NE that contains ML cards from Disable to Secure or Non-secure, the ML cards do not automatically synchronize.
|
CSCsh85942
|
The Ethernet PM table of ADM_10G cards shows incorrect values for Rx and Tx Ethernet Utilization parameters.
|
CSCsh86025
|
Incorrect link status of ONS 155xx NEs.
|
CSCsh87374
|
A scheduled image download job for an MGX NE remains in Wait state, blocking other jobs from starting.
|
CSCsh87646
|
A Y-cable-protected, autodiscovered DCC link is shown in CTM with a PCA protection attribute. The correct attribute should be Y-cable.
|
CSCsh88632
|
After performing the first Enable L2 Service operation and before the topology goes into Complete Resync state, there are no indications that the Enable L2 Service operation is going on in the background. This is misleading because it suggests that the Enable L2 Service operation is unsuccessful, and users retry the operation.
|
CSCsh89135
|
Policers are shown in incorrect order in the Modify Drops wizard.
|
CSCsh89406
|
Discovery of the SONET test network through the GNE is very slow. It is possible that the NE service is blocked for some time due to timeouts. Marking the NEs managed by the NE service as Out of Service and then In Service does not work correctly. It takes 25 minutes for all NEs to be discovered and go into In Service state on a newly installed CTM build.
|
CSCsh89434
|
Patchcord links are not completely discovered by the Network Control Protocol (NCP) component. Because of this, circuits that are routed through those links remain in Partial state.
|
CSCsh92748
|
The Affected Object field in the Alarm Browser shows incorrect values for CTM alarms raised because of problems with MGX nodes. (Related caveat ID: CSCsg22838.)
|
CSCsh92935
|
Unable to change the admin state for STM-6_16 or TSC card because the Admin State field is missing in the ONS 15600 SDH NE Explorer for these cards.
|
CSCsh92964
|
Link validity is not recalculated after restarting the NE service.
|
CSCsh94232
|
Graphs cannot be plotted for an STS category of a DS3 card if there are multiple entries in the PM table for a given port number.
|
CSCsh94767
|
Manual links become invalid after changing the link cost.
|
CSCsh94779
|
The nodes that are connected by a manual link are moved to different subnetworks after marking the nodes as Out of Service and then In Service. Furthermore, circuit creation is denied.
|
CSCsh94941
|
When PPMs are created on preprovisioned ASAP cards, the related information is not shown in the Line and Loopback tabs.
|
CSCsh95146
|
The Equipment Inventory table does not show a 40-WSS card in slot 14 or 15.
|
CSCsh96419
|
Multiple circuit deletion fails for high-order (HO) VC3 circuits created on ONS 15600 SDH NEs.
|
CSCsh96439
|
Unable to set the AIS threshold on ONS 15600 SONET NEs.
|
CSCsh97588
|
Cannot set the admin state of a port while creating an SDCC on ONS 15310 CL and ONS 15310 MA NEs.
|
CSCsh98137
|
The RPR interface is enabled in the running configuration but is not enabled in the startup configuration.
|
CSCsh98161
|
ST3E and TNC are available as possible values for the Admin SSM field of ONS 15310 CL CTX cards. These two attributes are not available in CTC.
|
CSCsh98517
|
The tunnel is not opened when you modify the GNE Login Required option. In this case, the GNE Login Required option does not work. It works properly when you add a TNE for the first time. Succeeding changes to the GNE Login Required option are not applied.
|
CSCsi00585
|
Real-time PM data on OCH ports of 40-WXC cards is not retrieved. The values are shown as N/A.
|
CSCsi01628
|
When an FTP error occurs, the following major alarm is generated: "Stats file transfer error." The alarm never gets cleared.
|
CSCsi02089
|
Change the CTM GateWay/TL1 username and password in the Control Panel, Securities properties. Mark the NE as Out of Service and then In Service. The new username and password are not applied to CTM GateWay/TL1.
|
CSCsi04794
|
The STS path frame on a VXSM OC3 card shows the wrong payload type for the VT payload path. Also, the VT tab is disabled when viewing the information in tabular form and when you launch the path entities.
|
CSCsi05177
|
When you start the CTM client and entered an incorrect password, you will not be connected but you can change the name of the CTM server hostname or IP address.
|
CSCsi05192
|
The configuration engine and CWM processes continue to run after executing the ctms-stop command.
|
CSCsi05508
|
When you use the RTRV-ALM-ALL command to retrieve ONS 1580x NE alarms, the alarms do not contain the rack, subrack, slot, and card information.
|
CSCsi06718
|
Sometimes it is impossible to create phantom links if a provisioned patchcord has been previously provisioned and then deleted.
|
CSCsi06828
|
The pruning operation on an ONS 15454 SDH audit trail parameter is not working properly.
|
CSCsi06851
|
Unable to complete the pruning operation on the Server Monitor table. The /oraclesw91/CTM/udump/prune_servermonitor.err log file contains the following error message: "ORA-01843: Not a valid month."
|
CSCsi06873
|
Unable to complete the pruning operation on the Admin Job table. The /oraclesw91/admin/CTM/udump/prune_adminjob.err log file contains the following error message: "ORA-01849: hour must be between 1 and 12."
|
CSCsi07958
|
The getActiveMaintenanceOperation API does not work on the MXP_MR_10DME card for both SONET and SDH configurations.
|
CSCsi08904
|
Real-time physical PM data is incorrect when you perform a PM query by category on L-band cards (for example, OPT_BST_L, 32WSS_L, 32DMX_L, and OPT_BST_L cards) of NE R7.0 and R7.2. This problem does not occur when you perform a PM query by NE model.
|
CSCsi09013
|
When you retrieve real-time PM information on 10GE-XP and GE-XP cards, the AVG Tx power value is incorrect for all selected ports.
|
CSCsi12214
|
The Alarm Browser does not show any ONS 15600 SDH alarms after enabling robust fault synchronization for the NE and marking the NE as Out of Service and then In Service.
|
CSCsi13707
|
Values of the PSC-S and PSD-S fields of ASAP cards with OC-48 PPMs are shown as N/A.
|
CSCsi15086
|
Connect an OSS client to CTM GateWay/TL1 and leave it for twelve hours. The OSS client receives no update from CTM GateWay/TL1, and CTM GateWay/TL1 does not respond to any requests made by the OSS client.
|
CSCsi15415
|
An error occurs after executing the getCTPsAndTopologicalLinks API.
|
CSCsi15485
|
The Filter operation does not work on the Circuit table.
|
CSCsi16349
|
NE Defaults in CTM are not synchronized with the NE Defaults in CTC.
|
CSCsi16553
|
The CTM client uninstalls after displaying a warning message.
|
CSCsi17070
|
In a high availability (HA) environment, the resource CTM_SID is shown as offline when Oracle processes are up and running.
|
CSCsi27588
|
Circuit routing takes more time compared to earlier releases.
|
CSCsi34326
|
The Circuit table updates continuously and discovers sections of the network that are not in its selection context.
|
CSCsi39771
|
The sort operation on the Domain NE table does not always work. For example, sorting the NE model column of the Domain NE table fails, but sorting the NE ID column works correctly.
|
CSCsi48269
|
The Treat LOF as Defect field is not available on XTC cards.
|
CSCsi59605
|
The Equipment Inventory table shows a single row marked as Chassis after removing and reinserting a fan tray. It does not show the fan tray or fan slot.
|
CSCsi88931
|
After installing the CTM R7.0.0.370.1 patch or any later CTM R7.0 patch, an upgrade to CTM R7.2 or R8.0 fails.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsj01791
|
The following error message is returned when you try to create a unidirectional manual link from an ONS 15454 SONET NE to an ONS 15216 EDFA NE:
EID-733: The node <node_name> is not available or there are no available physical termination
points for the given link size 10G-ITU in the specified layer and direction.
|
CSCsj02032
|
The msgTokenType MIB object is not represented in the database and is not shown in the Configuration Center.
|
CSCsj07317
|
In the NE Explorer, when you change the NE ID for an ONS 15454 R4.1.4 and click Apply, an error message is returned.
|
CSCsj07520
|
Cannot create 1:1 or 1:N protection between DS1, DS1N, or DS3XM cards on ONS 15454 SONET or ONS 15454 SDH R4.1.4 NEs.
|
CSCsj09127
|
If you add a TL1 gateway node to CTM R8.0, the node is added as a LAN-connected network element (LNE), not as a TNE. If you launch the TNE Devices table, a collapsed empty Java window opens.
|
CSCsj12599
|
After upgrading to CTM R8.0, you cannot set the TL1 Tunnel Connection Timeout value in the Control Panel window.
|
CSCsj14805
|
The CTM installer shows the Solaris patch 121265-03 as a required patch for the CTM server. However, this patch should not be installed because it applies to Sun T2000 servers, which are not supported by CTM. The Solaris patch 121265-03 is therefore not required and should not be installed.
|
CSCsj19520
|
The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service or CTM server is restarted.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsj30693
|
The NE Explorer shelf view is blank for ONS 15327 R4.1.82 NEs.
|
CSCsj32566
|
The Equipment State and Admin State fields are missing for ML cards on ONS 15454 SONET R4.1.82 NEs.
|
CSCsj34451
|
The Resync L2 Topology operation fails for a Cisco RPR that contains an ONS 15454 R4.1.82 NE.
|
CSCsj34528
|
The Add/Remove Card operation fails for a Cisco RPR that contains an ONS 15454 R4.1.82 NE.
|
CSCsj41573
|
Unable to launch CTC from the Domain Explorer and NE Explorer.
|
CSCsj43760
|
The incorrect software version is displayed in the Control Panel.
|
CSCsj43900
|
The RPR 802.17 PM table does not show the Time Last Cleared time stamp under any conditions.
|
CSCsj45195
|
Cannot create a circuit if the port name contains an open parenthesis character.
|
CSCsj52599
|
The management of the Apache Web Server service does not detect failure conditions such as kill -9 on httpd PID. The monitoring of http processes should be improved to detect failures on the Apache Web Server service.
|
CSCsj52896
|
PM services do not initialize correctly after a CTM server restart. Consequently, PM data is not collected for some NEs.
|
CSCsj70396
|
Cannot create an optical transmission section (OTS) patchcord link when the source NE contains only OSC_CSM cards.
|
CSCsj70432
|
The CTM server overwrites the most recent log files in the archive log directory.
|
CSCsj76500
|
When the PM service experiences high load conditions, some PM data for CTC-based NEs is not stored in the database.
|
CSCsj80112
|
When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.
|
CSCsj84148
|
The POS PM table shows the wrong value for the Alias ID parameter.
|
CSCsk20958
|
CTM GateWay/CORBA APIs return an exception with the following error reason: "The srcNodeId is null for the circuit with nodeId <node_ID>."
|
CSCsk21490
|
CTM GateWay/CORBA APIs return an exception with the following error reason: "Failed to get containing equipment for a PTP."
|
CSCsk28871
|
The /db05 partition is 100 percent full and the CTM server shuts down automatically.
|
CSCsk28922
|
During the CTM server installation, if you select "All of the Above Modules" in the Select Modules to Install screen, the UNIX user for the FTP server is not created. This problem occurs even though you selected the option to create an FTP user.
|
CSCsk34541
|
The PM Query by NE Model wizard and the PM Query by Category wizard do not open the RPR 1-day historical PM table.
|
CSCsk44463
|
Links remain invalid after resetting the GNEs.
|
CSCsk44773
|
Due to security issues, CTM must support Apache web server version 2.0.61.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsk53826
|
CTM and CTC do not discover server trail links that are created in opposite directions.
|
CSCsk59882
|
Passive ONS 15216 NEs are not discovered correctly when you log into the CTM client as an Operator. When you select a passive ONS 15216 node, the cursor remains an hourglass icon, indicating that CTM is retrieving data.
|
CSCsk61775
|
The secondary state of a transponder client port is not updated with events, which causes a mismatch between CTM and CTC. (Related caveat ID: CSCsk52028.)
|
CSCsk65341
|
The CTM GateWay/CORBA API getAllTopologicalLinks does not retrieve server trail links.
|
CSCsk72558
|
Circuit spans are not displayed properly in the Circuit Span table.
|
CSCsk74382
|
CTM does not discover more than two server trail links created between the same ports on the same VC-4 between two ONS 15454 SDH NEs. The Link table displays the first two server trail links with the wrong names, including an incorrect VC-12/VC-11/VC-3 number. CTC correctly discovers these server trail links.
|
CSCsk84166
|
Unable to set the EMS session port from the Control Panel.
|
CSCsk84707
|
CTM PM pruning fails due to a buffer overflow error.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsk92923
|
The OSS client is unable to set the time stamp to the local time (delta format) because CTM misinterprets the time format.
|
CSCsk98333
|
CTM GateWay/CORBA does not accept time stamps that use tenths of a second instead of zero.
|
CSCsl06203
|
The Create Link wizard does not open and an error message is displayed.
|
CSCsl07946
|
There are two entries in the Link Utilization table for a protected circuit that contains two spans, and each entry has a different Switch State value.
|
CSCsl09775
|
NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl20872
|
Creating an L1 circuit fails and the following message appears: "EID-932: Failed to route the circuit. Details: client timeout reached." (Related caveat ID: CSCsr20363.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl26108
|
CTM does not perform quickly when connecting, discovering, and resynchronizing CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl28104
|
The CTM server does not start automatically after completely restoring the database.
|
CSCsl28305
|
Unable to determine the status of the database when the migration or export operation fails.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl34530
|
The network topology is not updated in CTM.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl37264
|
The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl48499
|
The backup files are not listed in the Backup File dialog box after choosing Administration > Memory Backup Upload in the Domain Explorer.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsl95721
|
The Circuit table does not 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).
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsm37071
|
Implementation Repository (IMR) is an OpenFusion service that is required for the correct behavior of the CTM server. In certain environments, IMR shuts down unexpectedly, causing the SM service and any connected services to shut down and restart.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsm41384
|
The /tmp directory on the application server for log4j contains error messages and cleared CTM alarms that are unacknowledged. log4j is the library that manages log messages in the database and in the log files.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsm84722
|
Cannot install CTM patches in a dual-server setup.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsm85018
|
There are compatibility issues between CTM R8.5 and the CTM GateWay/CORBA R8.0 client after changing the CTM R8.5 notifications.idl file located in the /opt/CiscoTransportManager/idl directory.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsm99421
|
CTP values of alarms are printed when you run the getAllActiveAlarms API. But for certain alarms where the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso00123
|
The CTM client cannot connect to the CTM server. The following error message appears: "EID-382: The CTM server is initializing. Please try again after some time."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso00769
|
Unable to delete or modify drops or VLANs that are associated with custom QoS profiles.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso01840
|
It takes a long time to discover NEs after the NE service restarts.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso01900
|
The CTC-based NE service takes a long time to reconnect and discover NEs.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso01942
|
CTM takes a long time to discover a large network of GNEs and ENEs.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso35202
|
The Oracle shutdown script does not work while the server workstation is shutting down.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso44701
|
CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job Monitor table displays the following message:
(Too many open files)
(No such file or directory)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso44836
|
On a dual-server setup, the automatic pruning of the /db05 directory does not work. CTM*.arc files accumulate in /db05 and do not move automatically to /ctm_backup.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso62224
|
Upgrading the CTM server workstation from CTM R8.0 to R8.5 fails on a dual-server setup. When the Upgrade from Existing CTM Release check box is checked, the following error message appears: "Can't find database name and version information, abort."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCso76700
|
The CTM GateWay/CORBA northbound interface (NBI) creates additional proxy consumers if you do not stop CTM GateWay/CORBA before executing the ctms-stop or ctms-start commands.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq11152
|
Due to security issues, CTM must support a new JRE version.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq26342
|
The getHistoryPMData API takes longer than 15 minutes to return data.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq26362
|
The output file generated from getHistoryPMData returns duplicate rows.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq31631
|
Memory backup and memory restore fail on MGX nodes when Telnet is disabled.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq32073
|
Due to security issues, CTM must support Apache web server version 2.0.63.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq65111
|
In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq67942
|
The NE User Access Administration table and Modify NE User wizard show different values for the same fields.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq80551
|
CTM must add support for ONS 15305 R3.0.6 NEs.
Note This caveat is fixed with the CTM R8.5.0.368.3 or later patch.
|
CSCsq87850
|
SVLAN ports are not displayed correctly.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq94272
|
You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsq96596
|
In the NE Explorer for a GE_XP card, the SVLAN tab does not work correctly.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr13995
|
In the NE Explorer for a GE_XP card, when you switch from the QoS tab of one GE_XP card to the QoS tab of a different GE_XP card, the information from the QoS tab of the first GE_XP card is added to the information in the QoS tab of the second GE_XP card.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr16489
|
CTM must add support for release 4.1.3 NEs.
Note This caveat is fixed with the CTM R8.5.0.368.3 or later patch.
|
CSCsr30785
|
The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr44800
|
CTM must add support for release 4.1.6 NEs.
Note This caveat is fixed with the CTM R8.5.0.375.2 or later patch.
|
CSCsr53609
|
A CTM server core dump file is created when the CTM server shuts down.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr60497
|
When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr61773
|
CTM must add support for release 4.6.2 NEs.
Note This caveat is fixed with the CTM R8.5.0.375.2 or later patch.
|
CSCsr62641
|
When you delete NEs from the Deleted NEs group, a warning message should report that the NEs are scheduled for permanent deletion. To confirm that NEs have been deleted, check the Audit Log for the message "AUD-5015: <NE ID> has been successfully purged."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr65306
|
When upgrading from one CTM release to the next (as detailed in the Cisco Transport Manager Installation Guide), the migration scripts fail with Java exceptions.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr70191
|
When the system date is changed while the CTM server is running, the CTM server shuts down the NE, PM, and NBI services within five minutes.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr71540
|
When you apply a CTM patch on a migrated CTM system, the following SQL error is returned:
sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing object
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr91285
|
CTC cross-launch fails when multiple software versions are present.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr94216
|
Some of the fields that are present in the CTM Alarm Browser are missing from the CTM GateWay/CORBA output. For example, the Object and Module Name fields are missing from the events retrieved by CTM GateWay/CORBA.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsr95859
|
A CTM server core dump file (ilogCleanup) is created when the CTM server shuts down.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu10502
|
The export_full_db.sh script creates large hidden tar files under the /ctm_backup directory. With multiple database exports, the /ctm_backup file system becomes full, and CTM crashes.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu18321
|
The Circuit Repair window does not automatically close when the repair operation is finished.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu22851
|
A memory leak occurs on the CTM server because of zombie lightweight process (LWP) creation.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu26072
|
CTM deletes valid, discovered OCH patchcords that are created by CTC.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu26107
|
CTM users cannot create an OCH patchcord trunk or client from the CTC interface on a card configured with a wavelength higher than 32.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu37369
|
The Audit Log records a flood of events that are similar to the following:
AUD-147: NE (xxx) Property Changed - New Subnet Id (nn)
AUD-5018: NE (xxx) has changed its Subnetwork ID from ...
AUD-169: Topology Changed - Subnet (Subnetwork-nn) Added
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu49494
|
The Circuit table does not show the port name for circuits with a source or destination on ML-MR-10 or CE-MR-10 cards.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu50742
|
The Circuit table does not show the port name for STM1E_12 cards for source and destination NEs.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu56857
|
The Circuit table loses values for the following fields: Customer ID, Service ID, and Description.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu62835
|
The following SQL errors are generated during patch installation:
Executing pre requisite sql fixes for 361 patch
5589 rows deleted. Commit complete. Table altered. ALTER TABLE ACTIVE_ALARM_TABLE ADD
CONSTRAINT ... ERROR at line 1: ORA-00955: name is already used by an existing object Commit
complete.
done.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu66316
|
Cannot launch CTC from CTM for an ONS 15454 MSTP R8.5.2 node.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu67460
|
Even though automatic alarm acknowledgement is enabled, cleared alarms do not move from the Alarm Browser to the Alarm Log.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu68317
|
The northbound CORBA interface returns incorrect cross-connect table information. The getAllCrossConnections API returns a CTP name retrieved by a VC-12 circuit in the format /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu86435
|
Occasionally, Cisco Edge Craft does not launch from CTM.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu88344
|
CTM performance degrades severely when the managed domain contains duplicate IP addresses. Furthermore, CTM does not display a warning message about the duplicate IP addresses.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu88903
|
The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu90020
|
Manual circuit routing through a server trail fails.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu90217
|
Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsu90286
|
Circuit routing through a server trail fails.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv00207
|
When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv04954
|
When logging into the CTM client, the login fails.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv07073
|
The Circuit table loses values for the following fields: Circuit Alias Name, Note, Customer ID, Service ID, and Description.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv07090
|
The Circuit table loses additional values after marking a node as Out of Service/In Service and restarting the NE service.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv07267
|
After marking an NE as Out of Service > In Service > Out of Service > In Service, cross-connections are no longer discovered for that NE.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv07682
|
You cannot save a VLAN database. The job does not appear in the Job Monitor table, or the operation fails with the error "ORA-01461."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv12810
|
An MGX node is added to the CTM server, but is not included in the Auto Backup process.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv33266
|
If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv40528
|
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. (Related caveat ID: CSCsw22308.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv47526
|
The setTPData and getTP APIs might fail and generate a null pointer exception for a CTP whose native name involves an MRC-12 card.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv52311
|
The getSNC and getAllSubnetworkConnections APIs return CTPs in the format /sts1_au3-j=1-k=[1..192] instead of /sts1_au3-j=[1..64]-k=[1..3]. Also, the setTPData API might fail for CTPs created on OC-192 XFP cards, which generates a null pointer exception.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv70799
|
CTM and CTC show different values for LBC and OPT parameters on MRC-25G-4 cards.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv70863
|
In the card-level NE Explorer > Line tab > Line Config subtab > Admin State field, if you change the administrative state of the port from In Service to Out of Service, a warning dialog box prompts you for confirmation. If you click Yes, the port changes to Out of Service. If you click No, the port remains In Service. If you click the X in the upper corner of the warning dialog box to cancel the operation, the port changes to Out of Service.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv81066
|
The NE service freezes after discovering a large NE network.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsv97842
|
A memory leak occurs on the CTM server because of uncontrolled thread creation.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw37526
|
When you zoom in on the Network Map and save the view as the default, the following error message is generated:
EID-700: An error occurred while saving nodes coordinates to the database. Refresh the view
and retry.
(Related caveat ID: CSCtb98889.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw43520
|
A memory leak occurs on the CTM server because of zombie LWP creation during startup.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw68952
|
A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw73743
|
The getAllCrossConnections API returns an error if the node does not contain circuits.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw88114
|
In a filter dialog box, the User Specified radio button allows only 2009 to 2018 as the year.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw91974
|
In a large network of GNEs and ENEs, CTM fails to collect PM data.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw91994
|
The CTM database contains unusable indexes, which means that PM tables and audit logs contain no data.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsw98325
|
Cannot export tables in HTML format from the CTM client.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx09374
|
In an HA setup, if you install CTM R8.5.0.350.1 or later, the Apache web server is no longer controlled by the Veritas Apache agent. Even if the web server is running, the Veritas Apache agent does not acknowledge it.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx17951
|
The Find dialog box > Metro DWDM Circuits option does not find ONS 15454 OCH circuits.
Note This caveat is resolved with a change to the Cisco Transport Manager Release 8.5 User Guide. Section 1.5.5.1, "Finding Data," now includes this note: "The Metro DWDM Circuits option applies only to ONS 155xx NEs. For other NE types—such as the ONS 15454—the Metro DWDM Circuits option returns no results. To filter circuits on ONS 15454 NEs, use the Circuit table filter."
|
CSCsx22431
|
CTM and CTC show different wavelength calculations for OCHNC circuits.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx47556
|
After backing up the CTM R8.5 database from the Control Panel or with the backupdb.sh command, the log file backup_db.log is not generated. The backup_db.log file is not written to the /oracle/admin/CTM/udump directory because there is a space character added when assigning the PATH to the file.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx50111
|
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.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx50126
|
Due to security issues, CTM must support Apache web server version 2.2.11.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx50161
|
Due to security issues, Apache Tomcat must be disabled.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx52287
|
Event notification is not audible.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx55667
|
The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx56687
|
The SPAN_BS_TABLE database table displays incorrect working and protected values.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx81985
|
Archive log pruning degrades as database usage increases, and the /db05 directory fills up.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsx93323
|
CTM displays a "Media Gateway Link state, pendingIs" alarm with a "Warning" severity. In other Element Managers, this type of alarm is set with a "Major" severity.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsy10635
|
When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0 on a single-server setup installed with optical modules only, a warning message says problems occurred during the upgrade. The CTM server starts correctly despite the warning message.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsy23134
|
CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6 NEs.
Note This caveat is fixed with the CTM R8.5.0.387.6 or later patch.
|
CSCsy29600
|
CTM does not receive PM data from managed MGX devices.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsy56348
|
Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsy93198
|
On the CTM client, the following MGX windows take approximately 15 minutes to load:
•MGX Chassis View
•Configuration Center
•Diagnostics Center
•Performance screens
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsz63889
|
Occasionally, memory backups fail for CTC-based NEs with release 6.0.1.
|
CSCsz75781
|
The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM cards in the network. (Related caveat ID: CSCtb15132.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsz79773
|
Occasionally, NE backup files are canceled when automatic daily backups are scheduled. The Job Monitor table shows two backups running at the same time for the same NE, yet only one backup executes successfully. The second backup fails with the following exception: "Cannot execute Backup Database; A similar task is already running."
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCsz83568
|
•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
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta30985
|
A memory leak occurs on the CTM server because of zombie LWP creation when a user is in locked state.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta31966
|
Memory usage for the ooemc process increases over a period of time.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta42487
|
The SM service disconnects during a JMOCO hello message, and the CTM server restarts. (Related caveat ID: CSCtf17428.)
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta69019
|
The ctms-stop and ctms-abort scripts do not work when Oracle is down.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta69923
|
Cleared alarms are not removed from the Alarm Browser.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta73380
|
Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCta95729
|
NEs cannot be moved to the bottom right corner of the Create Circuit wizard map view.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb01411
|
The network services and network service instances cannot be stopped or started from the Control Panel. The SMService-0-<timestamp>.log file shows the following error message:
EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too
many open files.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb05738
|
CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC are assigned to a queue based on the value of the NE node ID. Because the node ID often has an even value, only queues with an even ID are used to process events. Consequently, half of the threads are instantiated but are never used to process events.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb21147
|
CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb34284
|
The core_pmon.sh script that checks the status of critical CTM processes runs every 30 seconds instead of every 5 minutes.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. However, if a previous workaround was applied, edit the core-pmon.sh file and remove the row that contains "sleep 270." Installing the CTM R8.5.0.392.2 or later patch will not overwrite the file.
|
CSCtb55280
|
If you remove a multimode fiber from a gigabit Ethernet interface on an RPM card, the PXM reports a critical alarm. However, due to an Oracle exception, CTM does not raise an alarm.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb73160
|
The Circuit table does not display port names for ONS 15454 SONET DS1_E1_56 and OC192_XFP cards.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb78977
|
The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb85880
|
After performing NE software upgrades, the SM service restarts NE services.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtb98230
|
The CTM Alarm Browser does not display an alarm when the system uptime of service modules exceeds the threshold.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtc12055
|
Cannot use automatic or manual backup to prune MGX data.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtc28944
|
From CTM, you cannot launch CTC on a CTC-based R8.5.1 NE.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtc49087
|
CTM displays the MGX 88xx chassis serial number as N/A in the Equipment Inventory table.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtc49689
|
The Oracle Alert log displays deadlock error messages.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtc55148
|
Automatic and manual PM data pruning does not work on small CTM servers.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtd50557
|
Cannot install the client patch if the installation directory name contains a blank space.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCte41594
|
CTM does not support the Carrier Ethernet Multirate 6 (CE-MR-6) card.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCte69670
|
The PM service logs contain errors, and PM data is not collected for some rows.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCte77971
|
From CTM, you cannot launch CTC or add new R8.5.1 or R8.6 NEs.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCte65495
|
Memory usage for the ooemc process increases when cache Roguewave lists are cleared.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf06220
|
Database migration to CTM R9.1 hangs when ARCHIVELOG mode is enabled. The /db05 file system fills up, and the migration hangs.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf06511
|
If you upgrade to CTM R9.1 on a week day (not on a weekend), the following error occurs: ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf08344
|
The CTP EMS native name is incorrect for a low-order (LO) VC circuit alarm.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf25363
|
The CTP EMS native name is incorrect for a low-order (LO) VT circuit alarm.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf27628
|
The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does not update. This issue causes problems with Oracle statistics management and node connectivity.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtf30749
|
CTM must add support for ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.5.4 NEs.
Note These NE releases are supported in CTM R8.5.0.430.3 or later.
|
CSCtf45430
|
After migrating to CTM R9.0 or R9.1, the processes parameter value is not set correctly in the initCTM.ora file.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCtg94496
|
CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6.1 NEs.
Note These NE releases are supported in CTM R8.5.0.430.3 or later.
|
CSCth21611
|
Loss of communication alarm storms occur periodically on CTC-based network services.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCth64373
|
The CTP EMS native name is incorrect for LO VT circuits when getSNC and getAllSnc APIs are used.
Note This caveat is fixed with the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
|
CSCuk55231
|
TCAs are shown one hour late in PM tables when the NE switches automatically from Daylight Saving Time to standard time.
|
Installing the CTM R8.5.0.430.3 Service Pack
This section describes how to download and install the CTM R8.5.0.430.3 service pack, which inherits all fixes from previous patches and service packs.
Caution Due to CSCtc55148, if the following conditions exist, you must truncate all non-empty PM tables in the database before installing the CTM R8.5.0.430.3 service pack:
— You are using a small CTM server configuration
— You installed the CTM R8.5.0.387.6 patch
— PM collection is enabled
Note that by truncating PM tables, you will lose all historical PM data. Contact the Cisco Technical Assistance Center (TAC) for assistance.
The following caveats are fixed in the CTM R8.5.0.430.3 service pack:
•CSCtb55280: If you remove a multimode fiber from a gigabit Ethernet interface on an RPM card, the PXM reports a critical alarm. However, due to an Oracle exception, CTM does not raise an alarm.
•CSCtb85880: After performing NE software upgrades, the SM service restarts NE services.
•CSCte69670: The PM service logs contain errors, and PM data is not collected for some rows.
•CSCtf25363: The CTP EMS native name is incorrect for an LO VT circuit alarm.
•CSCtf30749: CTM must add support for ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.5.4 NEs.
•CSCtg94496: CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6.1 NEs.
•CSCth21611: Loss of communication alarm storms occur periodically on CTC-based network services.
•CSCth64373: The CTP EMS native name is incorrect for LO VT circuits when getSNC and getAllSnc APIs are used.
The following NE software releases are supported in the CTM R8.5.0.430.3 service pack:
•ONS 15310 MA Release 8.5.4
•ONS 15454 SDH Release 8.5.4
•ONS 15454 SONET Release 8.5.4
•ONS 15310 CL Release 8.6.1
•ONS 15310 MA Release 8.6.1
•ONS 15454 SONET R8.6.1
•ONS 15454 SDH R8.6.1
The following caveats are fixed in the CTM R8.5.0.410.3 service pack:
•CSCsr95859: A CTM server core dump file (ilogCleanup) is created when the CTM server shuts down.
•CSCta31966: Memory usage for the ooemc process increases over a period of time.
•CSCta42487: The SM service disconnects during a JMOCO hello message, and the CTM server restarts. (See also CSCtf17428.)
•CSCtc28944: From CTM, you cannot launch CTC on a CTC-based R8.5.1 NE.
•CSCtc49689: The Oracle Alert log displays deadlock error messages.
•CSCte41792: The code fix for CSCsh98117 changed the Admin State behavior for CTC-based circuits. The correct circuit Admin State behavior must be restored.
•CSCte65495: Memory usage for the ooemc process increases when cache Roguewave lists are cleared.
•CSCte77971: From CTM, you cannot launch CTC or add new R8.5.1 or R8.6 NEs.
•CSCtf06220: Database migration to CTM R9.1 hangs when ARCHIVELOG mode is enabled. The /db05 file system fills up, and the migration hangs.
•CSCtf06511: If you upgrade to CTM R9.1 on a week day (not on a weekend), the following error occurs: ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running.
•CSCtf08344: The CTP EMS native name is incorrect for a low-order (LO) VC circuit alarm.
•CSCtf27628: The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does not update. This issue causes problems with Oracle statistics management and node connectivity.
•CSCtf45430: After migrating to CTM R9.0 or R9.1, the processes parameter value is not set correctly in the initCTM.ora file.
The CTM R8.5.0.410.3 service pack provides support for the Carrier Ethernet Multirate 6 (CE-MR-6) card.
The following caveats are fixed in the CTM R8.5.0.392.2 patch:
•CSCsu26072: CTM deletes valid, discovered OCH patchcords that are created by CTC.
•CSCsu26107: CTM users cannot create an OCH patchcord trunk or client from the CTC interface on a card configured with a wavelength higher than 32.
•CSCsu49494: The Circuit table does not show the port name for circuits with a source or destination on ML-MR-10 or CE-MR-10 cards.
•CSCsv00207: When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.
•CSCsv97842: A memory leak occurs on the CTM server because of uncontrolled thread creation.
•CSCsw37526: When you zoom in on the Network Map and save the view as the default, the following error message is generated:
EID-700: An error occurred while saving nodes coordinates to the database. Refresh the
view and retry.
•CSCsw68952: A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
•CSCsw98325: Cannot export tables in HTML format from the CTM client.
•CSCsx17951: The Find dialog box > Metro DWDM Circuits option does not find ONS 15454 OCH circuits.
Note This caveat is resolved with a change to the Cisco Transport Manager Release 8.5 User Guide. Section 1.5.5.1, "Finding Data," now includes this note: "The Metro DWDM Circuits option applies only to ONS 155xx NEs. For other NE types, such as the ONS 15454, the Metro DWDM Circuits option returns no results. To filter circuits on ONS 15454 NEs, use the Circuit table filter."
•CSCsx47556: After backing up the CTM R8.5 database from the Control Panel or with the backupdb.sh command, the log file backup_db.log is not generated. The backup_db.log file is not written to the /oracle/admin/CTM/udump directory because there is a space character added when assigning the PATH to the file.
•CSCsx52287: Event notification is not audible.
•CSCsx55667: The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
•CSCsx93323: CTM displays a "Media Gateway Link state, pendingIs" alarm with a "Warning" severity. In other Element Managers, this type of alarm is set with a "Major" severity.
•CSCsy29600: CTM does not receive PM data from managed MGX devices.
•CSCsy56348: Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
•CSCsy93198: On the CTM client, the following MGX windows take approximately 15 minutes to load:
–MGX Chassis View
–Configuration Center
–Diagnostics Center
–Performance screens
•CSCsz79773: Occasionally, NE backup files are canceled when automatic daily backups are scheduled. The Job Monitor table shows two backups running at the same time for the same NE, yet only one backup executes successfully. The second backup fails with the following exception: "Cannot execute Backup Database; A similar task is already running."
•CSCta30985: A memory leak occurs on the CTM server because of zombie LWP creation when a user is in locked state.
•CSCta69019: The ctms-stop and ctms-abort scripts do not work when Oracle is down.
•CSCta73380: Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.
•CSCta95729: NEs cannot be moved to the bottom right corner of the Create Circuit wizard map view.
•CSCtb73160: The Circuit table does not display port names for ONS 15454 SONET DS1_E1_56 and OC192_XFP cards.
•CSCtb78977: The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
•CSCtb98230: After a card restarts, the MGX device log correctly reports a card uptime problem. However, CTM never shows the same alarm.
•CSCtc12055: Cannot use automatic or manual backup to prune MGX data.
•CSCtc49087: CTM displays the MGX 88xx chassis serial number as N/A in the Equipment Inventory table.
•CSCtc55148: Automatic and manual PM data pruning does not work on small CTM servers.
•CSCtd50557: Cannot install the client patch if the installation directory name contains a blank space.
The following caveats are fixed in the CTM R8.5.0.390.3 patch:
•CSCsu90217: Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
•CSCsz63889: Occasionally, memory backups fail for CTC-based NEs with release 6.0.1.
•CSCsz75781: The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM cards in the network. (Related caveat ID: CSCtb15132.)
•CSCsz83568: 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
•CSCta69923: Cleared alarms are not removed from the Alarm Browser.
•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.IOException:
Too many open files.
•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.
•CSCtb21147: CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.
•CSCtb34284: The core_pmon.sh script that checks the status of critical CTM processes runs every 30 seconds instead of every 5 minutes.
Note If a previous workaround was applied, edit the core-pmon.sh file and remove the row that contains "sleep 270." Installing the CTM R8.5.0.392.2 or later patch does not overwrite the file.
The following caveats are fixed in the CTM R8.5.0.387.6 service pack:
•CSCso44836: On a dual-server setup, the automatic pruning of the /db05 directory does not work. CTM*.arc files accumulate in /db05 and do not move automatically to /ctm_backup.
•CSCso62224: Upgrading the CTM server workstation from CTM R8.0 to R8.5 fails on a dual-server setup. When the Upgrade from Existing CTM Release check box is checked, the following error message appears: "Can't find database name and version information, abort."
•CSCsq67942: The NE User Access Administration table and Modify NE User wizard show different values for the same fields.
•CSCsr60497: When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
•CSCsr62641: When you delete NEs from the Deleted NEs group, a warning message should report that the NEs are scheduled for permanent deletion. To confirm that NEs have been deleted, check the Audit Log for the message "AUD-5015: <NE ID> has been successfully purged."
•CSCsr65306: When upgrading from one CTM release to the next (as detailed in the Cisco Transport Manager Installation Guide), the migration scripts fail with Java exceptions.
•CSCsr91285: CTC cross-launch fails when multiple software versions are present.
•CSCsu10502: The export_full_db.sh script creates large hidden tar files under the /ctm_backup directory. With multiple database exports, the /ctm_backup file system becomes full, and CTM crashes.
•CSCsu37369: The Audit Log records a flood of events that are similar to the following:
AUD-147: NE (xxx) Property Changed - New Subnet Id (nn)
AUD-5018: NE (xxx) has changed its Subnetwork ID from ...
AUD-169: Topology Changed - Subnet (Subnetwork-nn) Added
•CSCsu66316: Cannot launch CTC from CTM for an ONS 15454 MSTP R8.5.2 node.
•CSCsu67460: Even though automatic alarm acknowledgement is enabled, cleared alarms do not move from the Alarm Browser to the Alarm Log.
•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.
•CSCsu90020: Manual circuit routing through a server trail fails.
•CSCsu90286: Circuit routing through a server trail fails.
•CSCsv04954: When logging into the CTM client, the login fails.
•CSCsv07267: After marking an NE as Out of Service > In Service > Out of Service > In Service, cross-connections are no longer discovered for that NE.
•CSCsv07682: You cannot save a VLAN database. The job does not appear in the Job Monitor table, or the operation fails with the error "ORA-01461."
•CSCsv12810: An MGX node is added to the CTM server, but is not included in the Auto Backup process.
•CSCsv33266: If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
•CSCsv40528: 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. (Related caveat ID: CSCsw22308.)
•CSCsv47526: The setTPData and getTP APIs might fail and generate a null pointer exception for a CTP whose native name involves an MRC-12 card.
•CSCsv52311: The getSNC and getAllSubnetworkConnections APIs return CTPs in the format /sts1_au3-j=1-k=[1..192] instead of /sts1_au3-j=[1..64]-k=[1..3]. Also, the setTPData API might fail for CTPs created on OC-192 XFP cards, which generates a null pointer exception.
•CSCsv70799: CTM and CTC show different values for LBC and OPT parameters on MRC-25G-4 cards.
•CSCsv70863: In the card-level NE Explorer > Line tab > Line Config subtab > Admin State field, if you change the administrative state of the port from In Service to Out of Service, a warning dialog box prompts you for confirmation. If you click Yes, the port changes to Out of Service. If you click No, the port remains In Service. If you click the X in the upper corner of the warning dialog box to cancel the operation, the port changes to Out of Service.
•CSCsw43520: A memory leak occurs on the CTM server because of zombie LWP creation during startup.
•CSCsw73743: The getAllCrossConnections API returns an error if the node does not contain circuits.
•CSCsw88114: In a filter dialog box, the User Specified radio button allows only 2009 to 2018 as the year.
•CSCsw91974: In a large network of GNEs and ENEs, CTM fails to collect PM data.
•CSCsw91994: The CTM database contains unusable indexes, which means that PM tables and audit logs contain no data.
•CSCsx09374: In an HA setup, if you install CTM R8.5.0.350.1 or later, the Apache web server is no longer controlled by the Veritas Apache agent. Even if the web server is running, the Veritas Apache agent does not acknowledge it.
•CSCsx22431: CTM and CTC show different wavelength calculations for OCHNC circuits.
•CSCsx50111: 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.
•CSCsx50126: Due to security issues, CTM must support Apache web server version 2.2.11.
•CSCsx50161: Due to security issues, Apache Tomcat must be disabled.
•CSCsx56687: The SPAN_BS_TABLE database table displays incorrect working and protected values.
•CSCsx81985: Archive log pruning degrades as database usage increases, and the /db05 directory fills up.
•CSCsy10635: When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0 on a single-server setup installed with optical modules only, a warning message says problems occurred during the upgrade. The CTM server starts correctly despite the warning message.
•CSCsy23134: CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6 NEs.
The following caveats are fixed in earlier CTM 8.5 patches:
•CSCse91332: CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.
•CSCsh67863: NEs do not change to In Service state.
•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.
•CSCsk44773: Due to security issues, CTM must support Apache web server version 2.0.61.
•CSCsk84707: CTM PM pruning fails due to a buffer overflow error.
•CSCsl09775: NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
•CSCsl20872: Creating an L1 circuit fails and the following message appears:
EID-932: Failed to route the circuit. Details: client timeout reached.
•CSCsl26108: CTM does not perform quickly when connecting, discovering, and resynchronizing CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
•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.
•CSCsl34530: The network topology is not updated in CTM.
•CSCsl37264: The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
•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.
•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 not 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.
•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.
•CSCsm37071: IMR is an OpenFusion service that is required for the correct behavior of the CTM server. In certain environments, IMR shuts down unexpectedly, causing the SM service and any connected services to shut down and restart.
•CSCsm41384: The /tmp directory on the application server for log4j contains error messages and cleared CTM alarms that are unacknowledged. log4j is the library that manages log messages in the database and in the log files.
•CSCsm84722: Patches cannot be installed in dual-server setup.
•CSCsm85018: There are compatibility issues between CTM R8.5 and the CTM GateWay/CORBA R8.0 client after changing the CTM R8.5 notifications.idl file located in the /opt/CiscoTransportManager/idl directory.
•CSCsm99421: CTP values of alarms are printed when you run the getAllActiveAlarms API. But for certain alarms where the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.
•CSCso00123: The CTM client cannot connect to the CTM server. The following error message appears:
EID-382: The CTM server is initializing. Please try again after some time.
•CSCso00769: Unable to delete or modify drops or VLANs that are associated with custom QoS profiles.
•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.
•CSCso35202: The Oracle shutdown script does not work while the server workstation is shutting down.
•CSCso44701: CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job Monitor table displays the following message:
(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.
•CSCsq11152: Due to security issues, CTM must support a new JRE version.
•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.
•CSCsq65111: In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.
•CSCsq80551: CTM must add support for ONS 15305 R3.0.6 NEs.
•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.
•CSCsq96596: In the NE Explorer for a GE_XP card, the SVLAN tab does not work correctly.
•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.
•CSCsr13995: In the NE Explorer for a GE_XP card, when you switch from the QoS tab of one GE_XP card to the QoS tab of a different GE_XP card, the information from the QoS tab of the first GE_XP card is added to the information in the QoS tab of the second GE_XP card.
•CSCsr16489: CTM must add support for release 4.1.3 NEs.
•CSCsr30785: The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
•CSCsr44800: CTM must add support for release 4.1.6 NEs.
•CSCsr53609: A CTM server core dump file is created when the CTM server shuts down.
•CSCsr61773: CTM must add support for release 4.6.2 NEs.
•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.
•CSCsr71540: When you apply a CTM patch on a migrated CTM system, the following SQL error is returned:
sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing object
•CSCsr94216: Some of the fields that are present in the CTM Alarm Browser are missing from the CTM GateWay/CORBA output. For example, the Object and Module Name fields are missing from the events retrieved by CTM GateWay/CORBA.
•CSCsu18321: The Circuit Repair window does not automatically close when the repair operation is finished.
•CSCsu22851: A memory leak occurs on the CTM server because of zombie LWP creation.
•CSCsu50742: The Circuit table does not show the port name for STM1E_12 cards for source and destination NEs.
•CSCsu56857: The Circuit table loses values for the following fields: Customer ID, Service ID, and Description.
•CSCsu62835: The following SQL errors are generated during patch installation:
Executing pre requisite sql fixes for 361 patch
5589 rows deleted. Commit complete. Table altered. ALTER TABLE ACTIVE_ALARM_TABLE ADD
CONSTRAINT ...
ERROR at line 1: ORA-00955: name is already used by an existing object Commit
complete.
•CSCsu86435: Occasionally, Cisco Edge Craft does not launch from CTM.
•CSCsu88344: CTM performance degrades severely when the managed domain contains duplicate IP addresses. Furthermore, CTM does not display a warning message about the duplicate IP addresses.
•CSCsu88903: The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
•CSCsv07073: The Circuit table loses values for the following fields: Circuit Alias Name, Note, Customer ID, Service ID, and Description.
•CSCsv07090: The Circuit table loses additional values after marking a node as Out of Service/In Service and restarting the NE service.
•CSCsv81066: The NE service freezes after discovering a large NE network.
CTM R8.5.0.430.3 is intended for customers who are currently using CTM R8.5.0.231, R8.5.0.350.1, R8.5.0.359.1, R8.5.0.361.2, R8.5.0.368.3, R8.5.0.375.2, R8.5.0.378.3, R8.5.0.381.3, R8.5.0.384.3, R8.5.0.387.6, R8.5.0.390.3, R8.5.0.392.2, or R8.5.0.410.3.
Note•Install the CTM R8.5.0.430.3 service pack only in a non-high availability setup. If you are using a high availability setup, contact your Cisco account representative before installing the service pack.
•In a dual-server setup, comment the stty values in the .cshrc file of the database host machine to allow the database host machine to copy and execute the service pack scripts remotely. Also, make sure that there is a .rhosts file in the / directory of the server machine before installing the service pack.
Complete the following procedures to upgrade to the CTM R8.5.0.430.3 service pack.
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, verify that the output results to one of the following:
•Cisco Transport Manager Server Version: 8.5 Build: 231
•Cisco Transport Manager Server Version: 8.5 Build: 350
•Cisco Transport Manager Server Version: 8.5 Build: 359
•Cisco Transport Manager Server Version: 8.5 Build: 361
•Cisco Transport Manager Server Version: 8.5 Build: 368
•Cisco Transport Manager Server Version: 8.5 Build: 375
•Cisco Transport Manager Server Version: 8.5 Build: 378
•Cisco Transport Manager Server Version: 8.5 Build: 381
•Cisco Transport Manager Server Version: 8.5 Build: 384
•Cisco Transport Manager Server Version: 8.5 Build: 387
•Cisco Transport Manager Server Version: 8.5 Build: 390
•Cisco Transport Manager Server Version: 8.5 Build: 392
•Cisco Transport Manager Server Version: 8.5 Build: 410
Backing Up the CTM Database Before Installing the CTM R8.5.0.430.3 Service Pack
Before installing the CTM R8.5.0.430.3 service pack, 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 8.5 User Guide:
•Backing Up the CTM Database from the CTM GUI
•Backing Up the CTM Database from the CLI
Downloading the CTM R8.5.0.430.3 Service Pack
Step 1 Go to http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=278875317.
Step 2 At the Select a Product screen, expand Cisco Transport Manager.
Step 3 Click Cisco Transport Manager 8.5.
Step 4 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 5 At the Select a Release screen, click Expand all and click 8.5.0.430.3.
Step 6 In the right pane, click Download Now to download CTM8.5.0.430.3.patch.zip.
Step 7 At the Download Software screen, click Proceed With Download.
Step 8 At the License Agreement screen, read the terms of the license agreement and click Agree.
Step 9 Download the CTM8.5.0.430.3.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 CTM8.5.0.430.3.patch.zip
For example, to extract the .zip file to the /temp directory, enter:
unzip CTM8.5.0.430.3.patch.zip
This creates a directory called 430, which contains all of the service pack-related files.
Step 11 Enter the following command to enter the directory:
Step 12 In Windows, download the CTM8.5.0.430.3.patch.zip file to the client workstation. Extract the file using a tool such as WinZip, as follows:
a. Open the CTM8.5.0.430.3.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 R8.5.0.430.3 Server Service Pack on the Same or Separate Workstation(s)
Step 1 If you are installing the CTM R8.5.0.430.3 server service pack on separate workstations, you must enable the remote shell (rsh) on the server in order to install the service pack successfully. Complete the following substeps:
a. Enter the following command to verify that the rsh is enabled:
rsh <database_workstation_IP_address> ls
b. If an error is returned, open a shell on the database workstation and edit the /.rhosts file. As the root user, enter the following commands to modify the /.rhosts file:
<CTM_server_workstation_name> root
where <CTM_server_workstation_name> is the hostname of the CTM server workstation.
Step 2 Complete the following substeps to notify all CTM users before shutting down the CTM server:
a. In the Domain Explorer window, choose File > Notify Users. The Notify Users dialog box opens.
b. In the Message Targets area, click the All CTM Users radio button.
c. Type the message in the Message area. Customize the message as appropriate for your organization. A sample message might read:
The CTM server will be shut down in 5 minutes. Please log out of the CTM client before
then.
d. Click Send.
e. Wait an appropriate amount of time for the CTM users to log out.
Step 3 At the end of the grace period, complete the following substeps to log out all of the CTM clients:
a. Log into the CTM server using an account with SuperUser privileges.
b. In the Domain Explorer window, choose Administration > CTM Users.
c. In the CTM Users table, choose Administration > Logged In CTM Users.
d. In the Logged In CTM Users table, select a user and choose Administration > Log Out User (or click the Log Out User tool).
Note This menu option is disabled if you selected your own session.
e. Click Yes at the following prompt:
This operation will log out the selected CTM user. The process will take approximately
1 minute and this CTM client will be unusable until then. Do you wish to continue?
Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the request is complete. Log out all of the users listed in the Logged In CTM Users table to verify that all user sessions are terminated.
Step 4 As the root user, enter the following command at the UNIX prompt to stop the CTM server:
Step 5 To patch the server, enter the following command in the 430 directory where the service pack was extracted:
Note The script might take awhile to complete, depending on the database size. Do not interrupt the script before it finishes.
Step 6 As the root user, enter the following command at the UNIX prompt on the CTM server workstation to start the CTM server:
Step 7 As the root user, enter the following command at the UNIX prompt on the CTM server workstation to verify the service pack installation:
You should see the following version string in the first line of output for the preceding command:
Cisco Transport Manager Server Version: 8.5 Build: 430 Patches: 3
Step 8 After installing the service pack, you have the option of upgrading your JRE version. See Upgrading the CTM R8.5 Server to JRE Version 1.5.0_16.
Installing the CTM R8.5.0.430.3 Client Service Pack in Windows
Note This procedure also applies to a dual-server setup.
The following steps describe how to patch a CTM client installation in Windows. Before proceeding, verify 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 430 service pack directory that was extracted with the WinZip utility.
Step 2 Using the command prompt, go to the directory where the service pack 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 service pack files were extracted and double-click the client_patch.bat file.
Step 3 Double-click the CTM 8.5 desktop icon or choose the CTM 8.5 Start menu shortcut to start the client.
Step 4 To verify the service pack 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: 8.5 Build: 430 (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:
Step 5 After installing the service pack, you have the option of upgrading your JRE version. See Upgrading the CTM R8.5 Windows Client to JRE Version 1.5.0_16.
Installing the CTM R8.5.0.430.3 Client Service Pack in Solaris
Note This procedure also applies to a dual-server setup.
The following steps describe how to patch a CTM client installation in Solaris. Before proceeding, verify 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 430 directory where the service pack 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 service pack 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: 8.5 Build: 430 (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:
Step 5 After installing the service pack, you have the option of upgrading your JRE version. See Upgrading the CTM R8.5 Solaris Client to JRE Version 1.5.0_16.
Upgrading to CTM R9.0 Using a Service Pack
Complete the following steps when upgrading to CTM R9.0:
Step 1 Install the latest service pack, if any. See the Migration Matrix for CTM Service Pack Releases.
Step 2 Start the upgrade process. For instructions, see Chapter 3 of the Cisco Transport Manager Release 9.0 Installation Guide.
Open Caveats
The following sections describe the caveats that are not resolved in the CTM R8.5 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
Note Some of the caveats are resolved in a CTM R8.5 patch or service pack. In such cases, the patch or service pack that contains the fix is indicated as a workaround.
Installation and Upgrade Caveats
•CSCsi71655
Symptom During the CTM installation, after you click the Done button on the last installation screen, the
following message is displayed on the shell:
You pressed Cancel/Upgrade/Install
This message is displayed even though you did not cancel the installation. The message might be followed by the output of an SQL statement as shown in the following Conditions.
Conditions The message "You pressed Cancel/Upgrade/Install" is displayed during a new CTM installation and during an upgrade from a previous CTM release. The output depends on the type of installation:
•When the CTM server and database are installed on the same workstation, the following messages are displayed:
You pressed Cancel/Upgrade/Install
SQL*Plus: Release 9.2.0.7.0 - Production on Mon Apr 30 15:54:35 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production With the
Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.7.0 -
'NEWDBVERSION'||ACTIVEVALUE
--------------------------------------------------------------------------------
SQL> SQL> Disconnected from Oracle9i Enterprise Edition Release
SQL> SQL> 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.7.0 -
Production The Database version retrieved is 8.0 The user has already started with
•When the CTM server and database are installed on separate workstations and you are upgrading from CTM R8.0 to R8.5, the following messages are displayed:
You pressed Cancel/Upgrade/Install
SQL*Plus: Release 9.2.0.7.0 - Production on Tue May 29 13:44:51 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR ORA-12545 : connection failed because target host does not exists.
SP2-0157: unable to connect to Oracle
grep: can't open /temp/newdbversion.lst
The Database version retrieved is
The user has clicked Cancel
Workaround Ignore the misleading messages described in this caveat. The CTM installation succeeds despite these messages.
•CSCsk44773
Symptom Due to security issues, CTM must support Apache web server version 2.0.61.
Conditions Due to a known security alert, CTM must support Apache web server version 2.0.61. For information on Apache vulnerability alerts, see http://httpd.apache.org/security/vulnerabilities_20.html.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsk52250
Symptom The CTM client shows the wrong installation status of CTM GateWay/CORBA.
Conditions This problem occurs when you install CTM GateWay/CORBA while the CTM server is running. Open the Control Panel and CTM GateWay/CORBA is shown as "Not Installed."
Workaround Click the Refresh button on the Control Panel or keep the Control Panel open while installing CTM GateWay/CORBA.
•CSCsl11930
Symptom 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
Conditions The database server in a CTM dual-server setup is not compliant with the RAM system requirement listed in the Cisco Transport Manager Release 8.5 Installation Guide.
Workaround Reinstall CTM and select an installation size that meets the RAM system requirement listed in the Cisco Transport Manager Release 8.5 Installation Guide.
•CSCsl28305
Symptom Unable to determine the status of the database when the migration or export operation fails.
Conditions This problem occurs when performing a migration or database export operation.
Workaround Install the latest CTM R8.5 patch before performing a migration or database export operation. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsm14884
Symptom The following error messages are generated while installing the CTM database in a high-end
configuration:
SQL> startup nomount pfile= /oracle/admin/CTM/pfile/initCTM.ora
SVR4 Error: 22: Invalid argument
Conditions In a high-end configuration, if the user.root project of the project.max-shm-memory parameter is less than 12 GB, error messages are returned during the CTM database installation. For example, the following command output indicates that the maximum shared memory is 4.00 GB:
prctl -n project.max-shm-memory -i project user.root
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
privileged 4.00GB - deny -
Workaround Reset the limit project.max-shm-memory parameter to a value greater than 12 GB.
•CSCsm46882
Symptom Unable to view server trails in CTM.
Conditions When you create a server trail in CTM or CTC after migrating from CTM R6.0 to CTM R7.0 or later, you cannot view the server trail in the CTM Link table.
Workaround Enter the following SQL commands:
ALTER TABLE LINK_TABLE MODIFY STNODEID NUMBER(10);
ALTER TABLE LINK_TABLE MODIFY STUNIQUEID NUMBER(10);
•CSCsm84722
Symptom Cannot install CTM patches in a dual-server setup.
Conditions CTM patches do not support dual-server scenarios. Therefore, fixes cannot be applied to servers in a dual-server setup.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCso62224
Symptom Upgrading the CTM server workstation from CTM R8.0 to R8.5 fails on a dual-server setup.
When the Upgrade from Existing CTM Release check box is checked, the following error message
appears: "Can't find database name and version information, abort."
Conditions This problem occurs when the CTM server and database are installed on different UNIX workstations.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, copy the /opt/newdbinfo file from the CTM database workstation to the CTM server workstation; then, restart the upgrade process.
•CSCso80680
Symptom The /oracle partition grows indefinitely until it reaches 100 percent of storage, and CTM
crashes.
Conditions This problem occurs when you migrate a CTM R8.0 server with ARCHIVELOG mode enabled to CTM R8.5.
Workaround Complete the following steps:
Step 1 Shut down the CTM server and Oracle.
Step 2 Uncomment the following lines in the initCTM.ora file in the /oracle/product/10.2.0/dbs directory:
#log_archive_dest = /db05/CTM/CTM
#log_archive_format = %t_%s_%r.arc
Step 3 Restart the CTM server and Oracle.
•CSCso92761
Symptom After upgrading to CTM R8.5 from an earlier CTM release, the database contains invalid
objects.
Conditions This problem occurs when you upgrade your database from CTM R7.0 to R8.0 and then to R8.5, and your database contains only optical modules.
Workaround Ignore the invalid objects in the database. To see if your database contains invalid objects, enter the following SQL command:
select object_name from dba_objects where status='INVALID';
Then, enter the following SQL commands to remove the invalid views:
sqlplus ctmanager/ctm123!
•CSCsq11152
Symptom Due to security issues, CTM must support a new JRE version.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq32073
Symptom Due to security issues, CTM must support Apache web server version 2.0.63.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq91933
Symptom CTM R8.5 does not start.
Conditions After installing Solaris patches, the following errors occur when you use the ctms-start script to start CTM:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/bouncycastle/openssl/PasswordFinder
at com.cisco.stardm.platform.Decrypt.main(Decrypt.java:65)
Error in add_log_parts.sh
Add log partition error: Please Check if ORACLE is installed and CTM DB is running
The Solaris patches update the JRE_HOME variable to point to /usr/java/bin/java as the default path. However, the JRE_HOME variable used by the ctms-start script uses /jre/bin/java as the default Java path. Therefore, CTM cannot access the correct Java executable.
Workaround After installing Solaris patches, verify that the JRE_HOME variable points to the correct Java path.
•CSCsr65306
Symptom When upgrading from one CTM release to the next (as detailed in the Cisco Transport
Manager Installation Guide), the migration scripts fail due to the following Java exception:
Executing the SQL pre-upgrade script...
Exception in thread "main" java.lang.NoClassDefFoundError:
org/bouncycastle/openssl/PasswordFinder
at com.cisco.stardm.platform.Decrypt.main(Decrypt.java:65)
Conditions This problem occurs when upgrading from:
•CTM R7.2 to CTM R8.0
•CTM R8.0 to CTM R8.5
•CTM R8.x to CTM R9.0
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr67129
Symptom An error message is returned when you install additional patches after installing the
Oracle 10.2.0.3 patch.
Conditions After you install the Oracle 10.2.0.3 patch, the Cisco Transport Manager Release 8.5 Installation Guide tells you to install the patch 4898608 to migrate the Opatch utility from 10.2.0.1.4 to 10.2.0.3.2. See section 2.1.1.6, "Downloading and Installing the Additional Patches Required After Installing the Oracle 10g 10.2.0.3 Patch Set 2 for the Solaris Operating System (SPARC 64-Bit)."
However, on June 9, 2008, Oracle released a new version of the Opatch installer with the same bug ID: 4898608. When you apply patch 6235161 per the Cisco Transport Manager Release 8.5 Installation Guide using this new version of the Opatch installer, an error message is returned. The error message instructs you to apply the Opatch installer referenced by bug ID 6880880, since the Opatch installer referenced by bug ID 4898608 is obsolete.
The Oracle MetaLink document ID 602334.1 references the error. The workaround to continue with the Oracle installation is described in 602334.1, as well as in the error message described above.
Note For the latest procedure on how to install the Oracle 10.2.0.3 patch, refer to the official Oracle documentation.
Workaround Complete one of the following workarounds:
•Follow the workaround that is provided with the error message.
•Use the guidelines that are listed in the Oracle MetaLink document 602334.1. To access that document:
Step 1 Go to http://metalink.oracle.com and click Login to MetaLink.
Step 2 Enter your Oracle MetaLink username and password.
Step 3 Click the Knowledge tab.
Step 4 Search for document ID 602334.1.
•CSCsr71540
Symptom When you apply a CTM patch on a migrated CTM system, the following SQL error is returned:
sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing object
Conditions This problem occurs on all CTM releases whenever a migration is involved, or when a service pack or patch is applied to a previously patched server.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu62835
Symptom The following SQL errors are generated during patch installation:
Executing pre requisite sql fixes for 361 patch
5589 rows deleted. Commit complete. Table altered. ALTER TABLE ACTIVE_ALARM_TABLE ADD
CONSTRAINT ... ERROR at line 1: ORA-00955: name is already used by an existing object
Commit complete.
Conditions This problem occurs after applying any patch level from CTM R8.5.0.361.2 to CTM R8.5.0.378.3 on a CTM system whose database was exported and then imported.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu88903
Symptom The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
Conditions When installing the CTM R8.5.0.378.3 patch, an error appears stating that it cannot find the database.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsx09374
Symptom In an HA setup, if you install CTM R8.5.0.350.1 or later, the Apache web server is no longer
controlled by the Veritas Apache agent. Even if the web server is running, the Veritas Apache agent does
not acknowledge it.
Conditions This problem applies only to an HA setup and occurs only when CTM is started with the ctms-start command. The CTM R8.5.0.350.1 (or later) patch upgrades the Apache web server, but the /opt/CiscoTransportManager/webServer/bin/apachectl file contains incorrect references to the /opt/CiscoTransportManagerServer/webServer/ directory. Instead, the apachectl file should contain references to the /Apache/ directory.
As a result of this problem, the Apache web server is not acknowledged as up and running when the CTM server is started with the ctms-start command. In the long term, this problem could cause the CTM server to switch from the primary server to the secondary server.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsx50126
Symptom Due to security issues, CTM must support Apache web server version 2.2.11.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsy01229
Symptom When installing CTM R8.5 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 R8.5 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 an 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 R8.5.0.240 patch and then install CTM.
Downloading the CTM R8.5.0.240 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 8.5.
Step 5 At the Select a Release screen, click Expand all and click 8.5.0.240.1.
Step 6 In the right pane, click CTM8.5.0.240.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 CTM8.5.0.240.patch.zip
For example, to extract the file to the /temp directory, enter:
unzip CTM8.5.0.240.patch.zip
This creates a directory called 240, which contains all of the patch-related files.
Step 11 Enter the following command to enter the directory:
Applying the Patch and Installing CTM R8.5
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 8.5 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 8.5 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 onscreen. 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(8.5)> <SID>
Example:
./fix_installation.sh 8.5 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
•CSCsy10635
Symptom When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0 on a single-server setup installed
with optical modules only, a warning message says problems occurred during the upgrade. The CTM
server starts correctly despite the warning message.
Conditions This problem occurs when the CTM R8.0 or CTM R8.5 single server is installed with optical modules only, and you upgrade to CTM R9.0. The upgrade ends with a warning message, yet the CTM R9.0 server starts and runs correctly.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, ignore the misleading warning message and start the CTM R9.0 server.
•CSCsy79681
Symptom When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0 on a dual-server setup installed
with optical modules only, a warning message says problems occurred during the upgrade. The CTM
server starts correctly despite the warning message.
Conditions This problem occurs when the CTM R8.0 or CTM R8.5 dual server is installed with optical modules only, and you upgrade to CTM R9.0. The upgrade ends with a warning message, yet the CTM R9.0 server starts and runs correctly.
Workaround Ignore the misleading warning message and start the CTM R9.0 server.
•CSCsy95377
Symptom During the CTM R8.5 server installation on a T2 workstation in a small network configuration,
the installation stalls at the RAM check. The following error message appears:
The recommended RAM for small configuration is 4 GB. Currently it is 3 GB. Please increase
it to 4 GB.
Conditions This problem occurs when the RAM size is less than 4 GB, and you are installing the CTM server on a SPARC Enterprise T5120 workstation. The T2 comes equipped with an exact RAM size of 3968 MB. Enter the following command to check the RAM size:
# prtdiag -v | grep Memory
Workaround Install with the "-dev" option to skip the RAM check.
•CSCsz72892
Symptom If the Apache web server is upgraded multiple times when installing CTM patches, the
previous Apache installation is not backed up correctly; that is, the webServer.orig directory does not
contain the previous Apache installation.
Conditions This problem occurs when the Apache web server is upgraded at least twice as part of multiple CTM patch installations. For example, this problem occurs when you install the CTM R8.5.0.350.1 patch and later you install the CTM R8.5.0.368.3 patch.
Workaround None.
•CSCta93568
Symptom MGX GUI windows do not open, because the UNIX permissions on the files in the
/opt/CiscoTransportManagerServer/webServer/cgi-bin directory do not have read and execute
permissions for all users.
Conditions This problem occurs when CTM is installed with the MGX module selected, and the CTM installation is interrupted while the background script setup.sh is running. For example, the CTM installation is interrupted if you reboot the workstation or close the windows on which the CTM installer was started.
The CTM installation is complete only when the following message is displayed:
Installation complete. Please see <installation directory>/install.log for details. Please
REBOOT THE SYSTEM before starting Cisco Transport Manager Server.
Workaround Reinstall the CTM server and verify that the installation completed successfully.
•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 CiscoTransportManagerServer8.5
ln -s CiscoTransportManagerServer-old-<timestamp> CiscoTransportManagerServer
rm CiscoTransportManagerServer.oldCTM
•CSCtc33026
Symptom While installing CTM, if you choose "Add new modules" at the Installation Options screen
and add MGX modules, CTM cannot connect to those MGX devices.
Conditions This problem occurs under the following conditions:
1. Your ORACLE_SID value in the /var/opt/oracle/oratab file is not the default value, CTM.
2. During the CTM installation, you choose "Add new modules" at the Installation Options screen and add MGX modules.
3. After you install MGX modules, the .cshrc and .profile files in the /opt/CiscoTransportManagerServer/cwm/svplus directory are not updated with the current ORACLE_SID value.
4. When you launch CTM, connectivity to the MGX devices fails.
Workaround Determine the ORACLE_SID value in the /var/opt/oracle/oratab file. Then, manually change the ORACLE_SID value in .profile and .cshrc to match the ORACLE_SID value in the /var/opt/oracle/oratab file.
•CSCtd50557
Symptom Cannot install the client patch if the installation directory name contains a blank space.
Conditions This problem occurs if the directory where the CTM client is installed has a blank space in the name. For example, if the installation directory is C:\Program Files\CTM (with a space between Program and Files), you cannot install the client patch.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, change the name of the directory where the CTM client is installed.
•CSCtf06220
Symptom Database migration hangs when ARCHIVELOG mode is enabled. The /db05 file system fills
up, and the migration hangs.
Conditions This problem occurs when many archive log files are created under the /db05 file system. When the /db05 file system fills, it blocks the database migration.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternately, remove the archive log files manually from the /db05 file system, or use the logarch.sh script to remove the files.
•CSCtf06511
Symptom If you upgrade to CTM R9.1 on a week day (not on a weekend), the following error occurs:
ORA-27366: job "SYS.GATHER_STATS_CTM_JOB" is not running.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtf27628
Symptom The database upgrade to CTM R9.1 finishes without errors; however, the initCTM.ora file does
not update. This issue causes problems with Oracle statistics management and node connectivity.
Conditions This problem occurs after migrating the CTM server to CTM R9.1.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtf45430
Symptom After migrating to CTM R9.0 or R9.1, the processes parameter value is not set correctly in the
initCTM.ora file.
Conditions This problem occurs in a high-end setup after upgrading from CTM R8.5.0.387.6 to CTM R9.0 or R9.1.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternately, shut down the CTM server and Oracle database; then, in the /oracle/admin/<CTM_SID>/pfile/init<CTM_SID>.ora file, change the processes parameter value to 5000.
•CSCth87771
Symptom Sudo software version 1.6.6 (bundled with CTM) has a potential security vulnerability or
exposure (CVE-2010-1646).
Conditions This problem occurs when Sudo is installed with CTM. For more information on CVE-2010-1646, see the CVE website at http://cve.mitre.org/.
Workaround None.
CTM Client Caveats
This section contains the following information:
•Alarm Management
•Circuit and Link Management
•User Management
•Data Services
•Domain Explorer
•NE Explorer
•Network Map
•Performance Monitoring
•Miscellaneous
Alarm Management
•CSCec49029
Symptom In the Alarm Browser, the module name "TCC" (Timing Communications and Control) is
displayed regardless of the actual equipment type. For example, alarms reported on TCC, TCC1, and
TCC2 cards all display "TCC" as the module name.
Conditions TCC2 and TCC1 alarms display the module name as "TCC" in the Alarm Browser and Alarm Log.
Workaround None.
•CSCeg14267 (Related caveat IDs: CSCef94105, CSCef89143)
Symptom Link down alarms, syslog events, and configuration messages are not received for ML cards
on ENEs behind the firewall when SNMP v2 is enabled.
Conditions This problem occurs when you enable SNMP v2 for the CTM server trap destination on an ONS 15310 or ONS 15454 ENE behind the firewall. If the ENE contains ML cards and you generate a link down trap on one of the ports on the ML card, the Alarm Browser does not report the link down trap as an alarm. This problem applies to NE releases earlier than R5.0.
Workaround Use SNMP v1 for ENEs behind the firewall if the CTM server is the trap destination.
•CSCin76849
Symptom CTM and CTC do not show the actual equipment type for G1K-4 and TCC2 cards.
Conditions See Symptom.
Workaround None.
•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.
•CSCsm17261 (Related caveat ID: CSCsq24237)
Symptom 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.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsm99421
Symptom CTP values of alarms are printed when you run the getAllActiveAlarms API. But for certain
alarms where the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.
Conditions This problem occurs on SDH NEs where the affected object of an alarm is VC4.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr55311
Symptom When you filter alarms that have CTM as the affected object, the alarm does not appear in the
Alarm Browser or Alarm Log.
Conditions See Symptom.
Workaround None.
•CSCsu90217
Symptom Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
Conditions This problem occurs under normal CTM operation.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, mark the NE as Out of Service and then In Service.
•CSCsv00207
Symptom When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm
Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties
pane.
Conditions With automatic alarm acknowledgement, the server should automatically acknowledge alarms when they are cleared and move them from the Alarm Browser to the Alarm Log. When this problem occurs, the cleared alarm disappears from the Alarm Browser and is not shown in the Alarm Log.
This problem occurs when automatic alarm acknowledgement and automatic pruning of fault management data are enabled. To check whether your system is affected by this problem, enter the following SQL command on the CTM database:
SQL> select * from ACK_TABLE where ACKINDEX=-1;
If the query returns zero records, your system is affected by this problem.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsz75781 (Related caveat ID: CSCtb15132)
Symptom The Error Log contains meaningless error messages that pertain only to DWDM cards, yet
there are no DWDM cards in the network.
Conditions This problem occurs while provisioning a line card; for example, an OC-3 line card.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, 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.
•CSCsz79773
Symptom Occasionally, NE backup files are canceled when automatic daily backups are scheduled. The
Job Monitor table shows two backups running at the same time for the same NE, yet only one backup
executes successfully. The second backup fails with the following exception: "Cannot execute Backup
Database; A similar task is already running."
Conditions This problem occurs when you use the Control Panel to schedule automatic backups for ONS 15454 NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, disable and re-enable automatic backup in the Control Panel.
After the patch is applied, the backup file is created in the correct folder. However, the Job Monitor table still shows two backups running at the same time for the same NE, and only one backup executes successfully. The second backup fails with the following exception: "Unknown exception."
•CSCta69923
Symptom Cleared alarms are not removed from the Alarm Browser.
Conditions This occurs in CTM R8.5. To confirm whether this problem affects your network, turn on the service logs and monitor whether or not alarm clear messages in the logs are shown correctly in the Alarm Browser.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, mark affected nodes In Service and then Out of Service.
•CSCtb05738
Symptom CTM event dispatcher threads are not distributed effectively. Events that arrive from CTC are
assigned to a queue based on the value of the NE node ID. Because the node ID often has an even value,
only queues with an even ID are used to process events. Consequently, half of the threads are instantiated
but are never used to process events.
Conditions This problem occurs when there are many uncleared alarms, and CTM performance degrades.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtb21147
Symptom CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards.
CTM fails to report major DS1 alarms.
Conditions This problem applies to NEs that are equipped with DS3XM_12 cards and provisioned with VT circuits. When CTM receives a DS1 alarm from a VT circuit on a DS3XM_12 card, the "ds1Num" field is always set incorrectly to -1.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, apply an NE alarm profile that suppresses the reporting of VT termination alarms on DS3XM_12 cards. Refer to the NE hardware documentation for the procedure to modify an NE alarm profile.
•CSCtb25595
Symptom Alarm icons display incorrect information in the Domain Explorer tree.
Conditions This problem occurs on a scalability test with a simulated network of 4000 NEs. This problem occurs in rare conditions.
Workaround None.
•CSCtb78977
Symptom The CTM Alarm Browser incorrectly displays an Above Normal alarm for an MGX node.
Conditions This problem occurs when there is a high voltage in an MGX node.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtb98230
Symptom The CTM Alarm Browser does not display an alarm when the system uptime of service
modules exceeds the threshold.
Conditions When the service modules (PXM45, PXM1E, AXSM, MPSM) run for longer than 440 or 460 days, the trap 60067 is generated for PXM, AXSM, and MPSM cards. When CTM receives the trap, it should display the following alarm in the Alarm Browser:
•A major alarm if the card exceeds the low threshold (by default, 440 days)
•A critical alarm if the card exceeds the high threshold (by default, 460 days)
Note The trap 60067 should be generated when the low threshold exceeds 430 days; however, due to CSCtd62409, the trap is generated only when the low threshold exceeds 440 days.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, reset the service module manually and clear the alarms in the Alarm Browser.
•CSCtd78067
Symptom Occasionally, daily backups scheduled automatically from CTM are duplicated on some NEs.
When this problem occurs, the Job Monitor table shows two backups running at the same time for the
same NE.
Conditions This problem occurs when you use the Control Panel to schedule automatic backups for ONS 15454 NEs.
Workaround Disable and re-enable automatic backup in the Control Panel.
•CSCuk58912
Symptom It is possible to set alarm threshold values on ONS 1580x measurement points that are outside
the range of possible values. For example, you can set a negative power threshold (in milliwatts).
Conditions See Symptom.
Workaround Refer to the appropriate hardware documentation before attempting to set thresholds on ONS 1580x cards. The hardware documentation lists the range of possible values.
Circuit and Link Management
•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.
•CSCin65850
Symptom The protection type for physical layer links is not automatically modified when the underlying
protection in the NE is deleted.
Conditions If you configure the protection type on two NEs, you can create a manual link with that particular protection. If the protection is deleted from the two terminating NEs, the protection type for the manual link is changed to Unprotected only if the link is in the SONET/SDH layer, but not when the link is in the physical layer.
Workaround Delete the manual links; then, recreate them without protection.
•CSCsb36751
Symptom When you open the Link table from the domain level, the table takes a long time to open and
you receive the error message "An error occurred while retrieving data from the database."
Conditions This problem occurs when you open the Link table from the domain node and the table contains thousands of rows.
Workaround Limit the scope of the query by opening the Link table for a group or NE node.
•CSCsb59118
Symptom When launching the Circuit table at the domain level, the table contains zero entries and the
following error message is displayed: "An error occurred while retrieving data from the database."
Conditions This problem occurs when the network contains a high number of NEs with many circuits.
Workaround Try to launch the Circuit table on a domain with fewer NEs.
•CSCsb95230
Symptom Creation of an STS-n circuit between E100 cards using CTM fails with the following error:
EID-931: Failed to provision the circuit.
Unable to provision circuit. Circuit provision error.
Unable to create the VLANs for the circuit at <node_name>.
Conditions This 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.
•CSCsc78150
Symptom The Link Utilization table shows the VC3 as 0 for all VC3 members of the VC tunnel circuit
with VC3 port grouping. It also shows an unused entry for the VC4. This happens only in circuits with
multiple hops.
Conditions Unknown.
Workaround Use the following guidelines, depending on the symptom:
•VC3 appearing as 0: The database is updated in two cycles. In the first cycle, the VC4 values are updated, and in the second cycle the VC3 values are correctly stored in the database. If you notice this problem, wait briefly before launching the Link Utilization table. The inconsistency will be removed automatically.
•Unused entry: Once the used entries show the correct values, the unused entries will be corrected automatically.
•CSCsc87791
Symptom International characters can be entered in fields that do not support them.
Conditions If you enter an international character in a nonalias field, the entry is permitted.
Workaround Do not enter non-English characters in nonalias fields.
•CSCsc93614
Symptom Server trails cannot be created for any port other than port 1 of an E1 card. An "Invalid
Preferences" error appears.
Conditions This problem occurs if you select a different VT/VC3/VC12/VC11 number for the source and destination while creating the server trail.
Workaround None.
•CSCsd02541
Symptom An error appears when attempting to route a circuit after an upgrade from OC-192 XFP to
OC-192. The Link table shows the link as valid, and the 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 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.
•CSCsh98117
Symptom When modifying an OCH Trail circuit, the Circuit Admin State field displays an inaccurate
circuit state.
Conditions This problem occurs when you create a CTC-based circuit and provision the Admin State value. When you open the Modify Circuit dialog box, the Admin State field contains a list of all provisionable states, with the circuit state preselected. However, the preselected circuit state is invalid, because it applies only to the circuit's cross-connections, and could have been applied with different values. For example, an OCH trail circuit with IS, AINS as the Admin State is converted to IS when applied to the cross-connections on the trunk ports.
Note This problem only occurs if the CTM R8.5.0.410.3 service pack has been installed.
Workaround None.
•CSCsj80220
Symptom Manual link creation fails.
Conditions This problem occurs when a patchcord is already provisioned on the same endpoint.
Workaround Create the manual link before creating a provisioned patchcord.
•CSCsk78622
Symptom The VC3 value is zero in the Link Utilization table for VC3 port group circuits.
Conditions This problem occurs when you create a VC3 port group circuit by selecting VC_LO_PATH_TUNNEL and checking the Port Grouping Only check box.
Workaround Mark the NEs involved in the circuit as Out of Service and then In Service.
•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 No workaround in CTM. You can view the circuit information in CTC.
•CSCsl20872 (Related caveat ID: CSCsr20363)
Symptom Creating an L1 circuit fails and the following message appears: "EID-932: Failed to route the
circuit. Details: client timeout reached."
Conditions This problem occurs when you create a circuit in a meshed network with several constraints in order to force a complex route with 20 spans.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, use manual routing and specify the complete route.
•CSCsl22134
Symptom The following error message appears: "The selected NEs do not support bidirectional circuit
creation."
Conditions The error message appears when creating an OCHNC circuit between NE R5.x and R6.x.
Workaround Create two unidirectional circuits.
•CSCsl25990
Symptom A manual SONET or SDH link is shown as valid/nonrouteable in the Link table and cannot be
used for manual circuit routing or as link constraints during automatic routing.
Conditions This problem occurs after migrating from CTM R7.0 to R8.5.
Workaround Delete the link and create it again.
•CSCsl26070
Symptom Updated link cost and shared risk link group (SRLG) values are not available after migration.
Conditions This problem occurs after migrating from CTM R7.0 to R8.5.
Workaround Manually update the links using the CTM link wizard.
•CSCsl34203
Symptom CTM GateWay/CORBA can retrieve Ethernet circuits using the CTP naming convention.
Conditions This problem occurs on Ethernet circuits that are provisioned on ADM-10G cards.
Workaround Ignore the CTP naming convention that is applied to the Ethernet circuits. Once a port is traversed by an Ethernet circuit, it cannot be used by other circuits. Create an STS24c or VC4-8c circuit so you can use all the available bandwidth that carries 1-Gigabit traffic.
•CSCsl39284
Symptom Unable to create circuits on optical nodes that belong to the default Network Partition 1.
Conditions This problem occurs when CTM is installed with only the MGX modules and then optical modules are added. When you create circuits on the optical NEs, the operation fails because the NEs belong to Network Partition 1.
Workaround Create a new network partition and move all the optical NEs to the new network partition.
•CSCsl95721
Symptom The Circuit table does not 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).
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsm21463
Symptom 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.
Conditions If a circuit is created with an E1-42 card whose port name is configured as the source or destination NE, the Circuit table does not display that port name. If a circuit is created with an STM-1 card whose port name is configured as the destination NE, the Circuit table does not display that port name.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCso07731
Symptom If you use textual routing to provision protected contiguous concatenation (CCAT) circuits, the
operation might fail.
Conditions This problem occurs when you use the CTM Circuit wizard to provision a protected CCAT circuit that crosses at least one BLSR or MS-SPRing. When you reach the textual routing pane, you can successfully provision the primary path. However, if you use the Alternate Route function to provision the secondary path, you come to the first node in the BLSR or MS-SPRing, and you cannot add the protected link of the BLSR or MS-SPRing because it has already been added to the primary path. Therefore, you cannot complete the textual routing.
Workaround Complete the following steps to finish the circuit provisioning:
Step 1 Click Add to include the protected link.
Step 2 Acknowledge the error message that says the link is already added to the circuit route.
Step 3 Click Next Hop to skip to the next node.
•CSCso51993
Symptom 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.
Conditions This problem occurs after the NE service restarts, or after NEs are marked as Out of Service and then In Service. If you then open the Link table, circuits related to a specific link are not shown.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, delete the manual link and then recreate it manually.
•CSCsr55335
Symptom Duplicate circuit names appear in CTM when a circuit name is updated in CTC.
Conditions This problem occurs when you change the name of a circuit to an existing circuit name in CTC. For example, you have circuits A, B, and C. Using CTC, change the name of circuit B to the same name as circuit A. In CTM, circuits A and B appear with the same name. Using CTC, change the name of circuit C to the same name as circuit A. In CTM, circuits A, B, and C appear with the same name but the name of circuits B and C are affixed with the word "Duplicate."
Workaround None.
•CSCsr60497
Symptom When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank
nodes.
Conditions This problem is seen only in the map view when creating a circuit manually using the Create Circuit Wizard. The node names are shown correctly in the network map from the Domain Explorer.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu18321
Symptom The Circuit Repair window does not automatically close when the repair operation is finished.
Conditions This problem occurs when there is a large number of circuits to repair; for example, 100 circuits.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, when the circuit status changes from partial to discovered, refresh the window manually. If the window remains open and all circuits are repaired, a window appears with a message stating that the operation was successful.
•CSCsu26072
Symptom CTM deletes valid, discovered OCH patchcords that are created by CTC.
Conditions See Symptom. If the same OCH patchcord is created by CTM, the problem does not occur.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu26107
Symptom CTM users cannot create an OCH patchcord trunk or client from the CTC interface on a card
configured with a wavelength higher than 32.
Conditions This problem occurs on cards that support 40 channels.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu49494
Symptom The Circuit table does not show the port name for circuits with a source or destination on
ML-MR-10 or CE-MR-10 cards.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu50742
Symptom The Circuit table does not show the port name for STM1E_12 cards for source and destination
NEs.
Conditions If a circuit is created with an STM1E_12 card whose port name is configured as the source or destination NE, the Circuit table does not display that port name.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu88218
Symptom When creating multiple STS circuits, an error is returned.
Conditions This problem occurs when you create multiple STS circuits using a port on the CTX card on an ONS 15310 MA SONET node, and the line is set to SDH over SONET.
Workaround Create circuits one at a time.
•CSCsu88344
Symptom CTM performance degrades severely when the managed domain contains duplicate IP
addresses. Furthermore, CTM does not display a warning message about the duplicate IP addresses.
Conditions This problem occurs when CTM manages different networks that contain ENE nodes with the same IP address (private IP addresses).
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. After the service pack is installed, complete the following procedures to enable the duplicate IP detection feature in CTM.
To enable duplicate IP address detection at the NE service level:
Step 1 Log into the CTM server as the root user.
Step 2 Go to the /opt/CiscoTransportManagerServer/bin/ directory and make a backup copy of the jnet.sh file.
Step 3 Using an editor such as vi, search for the following string inside the jnet.sh file:
-Dctm.duplicated-ip-detection=duplicated-ip-detection-disabled \
Step 4 Complete one of the following actions:
•If the preceding string is present, modify it to read:
-Dctm.duplicated-ip-detection=duplicated-ip-detection-enabled \
•If the string is not present, insert the following line between the Java properties, which begin with the "-D" prefix:
-Dctm.duplicated-ip-detection=duplicated-ip-detection-enabled \
Step 5 Save the changes and exit the jnet.sh file.
Step 6 Using the CTM Control Panel, restart all NE services.
To enable duplicate IP address detection at the CTM service level:
Step 1 Log into the CTM server as the root user.
Step 2 Go to the /opt/CiscoTransportManagerServer/bin/ directory and make a backup copy of the jne.sh file.
Step 3 Using an editor such as vi, search for the following string inside the jne.sh file:
-Dctm.sms.dupIpPoller.Enabled=false \
Step 4 Complete one of the following actions:
•If the preceding string is present, modify it to read:
-Dctm.sms.dupIpPoller.Enabled=true \
•If the string is not present, insert the following line between the Java properties, which begin with the "-D" prefix:
-Dctm.sms.dupIpPoller.Enabled=true \
Step 5 (Optional) To modify the time interval between checks, add the following line, where the minimum value is 1 hour, the maximum is 720 hours, and the default is 12 hours:
-Dctm.sms.dupIpPoller.Interval.hours=<number_of_hours> \
Step 6 (Optional) To modify the time interval between the CTM server restart and the first execution, add the following line, where the minimum value is 1 minute, the maximum is 1440 minutes, and the default is 0 minutes:
-Dctm.sms.dupIpPoller.start.delay.min=<number_of_minutes> \
The default value (0) indicates that after the CTM server restarts, the check will run for the first time after the interval specified by the ctm.sms.dupIpPoller.Interval.hours property.
Step 7 (Optional) To modify the number of times the check runs after the CTM server restarts, add the following line, where the minimum value is 1, the maximum is 2,147,483,647, and the default is 0:
-Dctm.sms.dupIpPoller.occurrences=<number_of_occurrences> \
The default value (0) indicates that the duplicate IP address check will be executed an infinite number of times.
Step 8 (Optional) To enable the Error Log to display the names of ENEs with duplicate IP addresses, add the following line, where the default value is false:
-Dctm.sms.dupIpPoller.Enable.NodeName=true \
Step 9 Save the changes and exit the jne.sh file.
Step 10 Restart the CTM server.
If the duplicate IP address problems persist, contact your Cisco account representative for recovery procedures.
•CSCsu90020
Symptom Manual circuit routing through a server trail fails.
Conditions This problem occurs when you manually route a circuit through a server trail. If you use automatic routing, the circuit creation succeeds.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu90286
Symptom Circuit routing through a server trail fails.
Conditions This problem occurs when you select a server trail link as a constraint for circuit routing.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv07073 (Related caveat ID: CSCsu56857)
Symptom The Circuit table loses values for the following fields:
•Circuit Alias Name
•Note
•Customer ID
•Service ID
•Description
Conditions This problem occurs when NEs are marked as Out of Service and then In Service. There is no way to recover the data that is missing from the Circuit table. To prevent this problem, wait for some time before moving out-of-service NEs back to In Service.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv07090
Symptom The Circuit table loses additional values after marking a node as Out of Service/In Service and
restarting the NE service.
Conditions This problem occurs when the NE service restarts while NEs are marked as Out of Service. There is no way to recover the data that is missing from the Circuit table. To prevent this problem, restart the NE service only when all of the NEs are marked as In Service and all of the circuits have been discovered correctly.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv07267
Symptom After marking an NE as Out of Service > In Service > Out of Service > In Service,
cross-connections are no longer discovered for that NE.
Conditions This problem occurs after repeatedly marking an NE as Out of Service and then In Service, and that NE contains intranode circuits.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, restart the NE service.
•CSCsv07682
Symptom You cannot save a VLAN database. The job does not appear in the Job Monitor table, or the
operation fails with the error "ORA-01461."
Conditions This problem occurs with large VLAN databases that contain more than 1000 VLANs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv14849
Symptom When a Provisioner user tries to modify, reconfigure, or delete a low-order path (LOP) VCAT
circuit, the following error messages are generated:
EID-989: Access violation. Verify that you have user privileges to perform this operation
on this circuit.
EID-943: Circuit deletion failed. Failed to delete the following circuit(s):
<circuit_name>.
Conditions The error messages described in the Symptom are generated when a user with Provisioner privileges opens the Circuit table and tries to modify, reconfigure, or delete an LOP VCAT circuit of size VC12 or VC3 on an SDH NE. As a result of this problem, L2 topologies based on LOP-v circuits cannot be removed.
Workaround Log into the CTM client with SuperUser privileges to modify, reconfigure, or delete LOP VCAT circuits.
•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 Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, use CTC to perform the span switch.
•CSCsw28308
Symptom In CTM, if you create a circuit that uses a server trail link, the circuit is discovered as Partial
in CTC.
Conditions This problem occurs when you use manual routing to create a circuit in CTM, and you select a server trail link for a span. If the server trail's VC4 or STS source differs from the destination, the circuit is discovered as Partial in CTC.
Workaround In CTM, use automatic routing to create the circuit. Alternatively, use CTC to create the circuit.
•CSCsw36905
Symptom Circuit provisioning fails with the following error message:
EID-927: Failed to provision the circuit manually.
Detail: Unable to provision the circuit. A circuit provisioning error occurred.
A connection cannot be created on the destination node. The path is already in use.
Conditions This problem occurs when you use a VT aggregation point (VAP) circuit to create a low-order path circuit on an SDH NE.
Workaround Use automatic routing to create the circuit.
•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.
•CSCsw48791
Symptom The Circuit wizard returns an error message regarding an invalid circuit state, and a VCAT
circuit changes to Partial.
Conditions This problem occurs when you add members to an existing VCAT circuit, and you specify an admin state other than the one set when the VCAT was created.
Workaround Mark the NE as Out of Service and then In Service.
•CSCsx56687
Symptom The SPAN_BS_TABLE database table displays incorrect working and protected values.
Conditions This problem occurs when circuits are routed over VT tunnels.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsy18486
Symptom In the Create Circuit wizard, tunnel links are not available for VT circuit routing.
Conditions The problem occurs when you launch the Create Circuit wizard and use previously created tunnel circuits to create new VT circuits.
Workaround Restart the NE service.
•CSCsy56348
Symptom Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsz58653
Symptom Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit
wizard.
Conditions This problem occurs when you use manual routing or constrained routing to create a VT circuit.
Workaround Mark the NEs that are involved in the circuit as Out of Service and then In Service.
•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 Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•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 Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtb73160
Symptom The Circuit table does not display port names for ONS 15454 SONET DS1_E1_56 and
OC192_XFP cards.
Conditions This problem occurs with circuits created between DS1_E1_56 and OC192_XPF cards.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtb75511
Symptom Adding a new member to a VCAT circuit fails. After clicking Next from the Route Constrain
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 Route 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 Route Preference pane.
•CSCte41792
Symptom The code fix for CSCsh98117 changed the Admin State behavior for CTC-based circuits. The
correct circuit Admin State behavior must be restored.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
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
•CSCeh50962
Symptom After the CTM server is rebooted, Layer 2 RPR services take about 20 minutes to get to
"Complete" L2 Sync State.
Conditions After the server reboots, Layer 2 RPR services with VLANs remain in L2ServiceNotReady L2 Sync State in the Layer 2 Topology table for about 20 minutes.
Workaround None.
•CSCeh51003
Symptom Cannot delete VLANs in an RPR configuration.
Conditions This problem was observed while trying to create an RPR topology with ONS 15310 and ONS 15454 ML-100T cards with five VLANs.
Workaround Complete one of the following workarounds, depending on the situation:
•If the startup configuration is accessed while CTM tries to apply the barebone configuration, a wr mem failure occurs. Wait for some time; then, apply the command again.
•If there is a difference between the startup configuration and the running configuration on the ML card, enter the wr mem command on the card.
•CSCeh97834
Symptom CTM fails to create an L2 service on an RPR ring when there are approximately 110 services
created on the ML card.
Conditions This problem occurs when ML cards take a long time to store the running configuration on the startup configuration. CTM times out in the request response condition and propagates an error message, even though the VLAN is created eventually.
Workaround If the VLAN is not discovered, mark the NEs as Out of Service and back In Service. This restarts the topology and VLAN discovery process. Entering the wr mem command on the cards where the VLAN is configured helps rediscover the missing VLANs.
•CSCei37993
Symptom An RPR is shown as up even though the station IDs are not unique.
Conditions If an RPR has duplicate stations IDs, it should not be shown as up. However, CTM displays an RPR with duplicate station IDs as up.
Workaround None.
•CSCei58026
Symptom After creating an L2 service in an RPR in a large network, the L2 topology goes into
L2ServiceNotReady or Sync Failed state and does not recover.
Conditions In large RPRs involving many ML cards, it takes CTM a long time to create L2 service drops. During this time, the L2 topology might go into L2ServiceNotReady or Sync Failed state without recovery.
Workaround Wait for 30 to 45 minutes for CTM to recover the resynchronization state. If the L2 topology has not recovered after 45 minutes, mark the NEs as Out of Service (in the Network Element Properties pane > Status tab > Operational State field) and click Save. Then, mark the NEs as In Service and click Save. This restarts the VLAN discovery process, which discovers the VLANs and their associated drops.
•CSCsb38681
Symptom The L2 Topology table launched for an NE shows all topologies in that subnetwork.
Conditions See Symptom.
Workaround None.
•CSCsb57054
Symptom An L2 topology goes into L2ServiceNotReady state during RPR creation and cannot recover.
The Alarm Browser contains the warning alarm "Need to save running config."
Conditions This problem applies to ML cards used in RPR creation.
Workaround Try any of the following:
•Reboot the ML cards on which the warning alarm occurs. Then, use the Enable L2 Service option to reapply the base card configuration.
•Telnet into the cards and enter the wr mem command so that both the startup and running configurations are the same. Then, use the Enable L2 Service option to reapply the base card configuration.
•Restart the topology creation by reloading the barebone configuration and rebooting the cards in the L2 topology.
•CSCsb66827
Symptom Two RPRs are discovered when NEs are added to the CTM server for the first time.
Conditions This problem occurs when NEs are added to the CTM server for the first time and there is a delay in the NE synchronization.
Workaround Mark all NEs involved in the RPR as Out of Service. After the L2 links are deleted, mark the NEs as In Service. If the problem still exists, restart the NE service.
•CSCsb66965
Symptom L2 topology PTPs and RPRs are not discovered and displayed in the L2 Topology table.
Conditions This problem was observed during regression testing of L2 topologies. When the problem occurs, L2 topologies are not visible in the L2 Topology table. The problem persists even after marking the NEs as Out of Service and In Service, or after reloading or resetting the configuration. This problem was also observed when the CTM server does not have enough time to clean some database configuration before creating another one.
Workaround Restart the NE service or delete the NEs from CTM and then add them again.
•CSCsc82864
Symptom A topology with 24 cards takes longer than 90 minutes to come up.
Conditions See Symptom.
Workaround Complete the following steps:
Step 1 Verify that the SNMP trap settings have been configured correctly on all NEs.
Step 2 Before creating the L2 topology, verify that the card has synchronized with CTM. To do this, launch the IOS Users table on the group and verify that the table contains entries pertaining to the card.
Step 3 Allow 15 minutes to recreate a topology on a card after deleting the old topology on the card.
•CSCsc91219
Symptom A four-card RPR with 50 VLANs does not synchronize.
Conditions See Symptom.
Workaround None.
•CSCsd25352
Symptom Topology discovery does not occur on the monitoring server.
Conditions Unknown.
Workaround Mark the NEs as Out of Service (in the Network Element Properties pane > Status tab > Operational State field) and click Save. Then, mark the NEs as In Service and click Save. Alternatively, restart the NE service for the NEs.
•CSCsd31676
Symptom For an L2 topology with segments of varying sizes, the sizes and number of VCAT members
are displayed incorrectly.
Conditions Unknown.
Workaround None.
•CSCsd53332
Symptom After performing a remove card operation, PoS ports are not enabled.
Conditions Unknown.
Workaround Use the NE Explorer or Modify Ports dialog box to make PoS state changes.
•CSCsd54231
Symptom Not all PoS ports are enabled after an add/remove card operation.
Conditions This problem occurs because CTM cannot enable all of the PoS ports that were shut down during an add/remove card operation.
Workaround Wait for the L2 topology to go into Sync Complete state. Then, use the Modify Ports dialog box or the NE Explorer to enable the PoS ports that were shut down during the add/remove card operation.
•CSCsd57810
Symptom While trying to modify L2 topology bandwidth, the following error is returned:
EID-368: Error occurred while modifying L2 topology bandwidth. Could not modify bandwidth
values.
Conditions This problem occurs on ML cards if there are two match cos commands under class-map. CTM can only support one match cos command. The second match cos command is shown as "null" in the CTM GUI. When you try to modify L2 topology bandwidth, the error message is generated.
A sample problem configuration is shown as follows:
class-map match-any AVVID_VOICE_VIDEO
Workaround From the CTM GUI, delete the last null value, make the necessary topology bandwidth modifications, and click Apply. The multiple match cos command problem should be corrected and you should not receive any error messages.
•CSCsd88540
Symptom You cannot add drops of newly added cards to an existing VLAN.
Conditions This problem occurs when a VLAN was created on a topology and you add a card to that topology. The new card ports cannot be added as drops to the existing VLAN.
Workaround None.
•CSCse71564
Symptom After an ML card reset, the L2 topology goes into L2 Service Not Ready state and never
transitions to Complete state.
Conditions This problem applies to ONS 15454 R7.0 NEs.
Workaround None.
•CSCse73576
Symptom An error message is returned when trying to launch the L2 Topology table. Also, the Circuit
table launches but freezes the CTM client.
Conditions This problem occurs only on certain large-scale setups and is due to CTM database-related issues.
Workaround None.
•CSCse76654
Symptom It is possible to create two PTP L2 topologies with different class maps using the same ML
cards.
Conditions This problem occurs only when you begin creating the second PTP topology on the ML card before CTM discovers the first PTP topology. This problem does not occur if you wait for CTM to discover the first PTP topology on the ML card before you begin creating the second PTP topology.
Workaround Ensure that all PTP topologies related to the selected ML card are discovered before trying to create a second PTP topology on the same ML card. The CTM client provides a warning message if you try to create a second PTP topology before the first one is discovered.
•CSCse82387
Symptom A VLAN created in CTC is not visible in the VLAN tab of the CTM NE Explorer for Ethernet
cards.
Conditions This problem applies to Ethernet cards on ONS 15305 R3.0 and ONS 15454 NEs.
Workaround To display VLAN data correctly, refresh data from the server.
•CSCse83853
Symptom An RPR topology is shown as complete when it contains only one circuit.
Conditions This problem occurs under the following conditions:
1. Creating a TL1 circuit from ML POS 0 to ML POS 1.
2. CTM discovers the topology as an incomplete RPR.
3. Using the Reconfigure Circuit(s) option to change the circuit to a normal CTC circuit.
4. The circuit state changes from Discovered_TL1 to Discovered and the L2 topology shows the status as complete. However, the RPR ring is not complete, because it contains only one circuit.
Workaround Mark the NEs involved in the RPR as Out of Service and then In Service.
•CSCsf20093
Symptom RPR topology creation fails, creating incomplete topologies.
Conditions This problem occurs when the server is overloaded and invalid entries are present in the Circuit Drop Selection pane, causing wizard parameters to initialize incorrectly. Consequently, an incorrect wizard navigation is set.
Workaround Click the Back button instead of the Next button in the wizard. This ensures a reinitialization of the incorrect parameters and sets the correct wizard navigation.
•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.
•CSCsh32836
Symptom Cannot view the ML card's VLAN port IP address and corresponding NE and slot number after
creating an L2 service.
Conditions See Symptom.
Workaround Create managed VLANs to view the mapping between the NE ID or slot number and the IP address.
•CSCsh69305
Symptom Active and standby ML cards are not shown when creating VLANs on 802.17 RPR topologies
using the corresponding wizard.
Conditions Create an 802.17 RPR topology that includes active and standby ML cards. When the topology is in Complete state, the Protect Card column in the ML Card table does not show the card protection value until the next L2 resynchronization cycle. Open the Create L2 Service wizard and the active and standby ML cards are not shown.
Workaround Create the L2 service after the L2 resynchronization polling cycle completes.
•CSCsk48068
Symptom When you delete a VLAN from an L2 topology, the following error message appears: "Could
not delete VLAN completely."
Conditions This problem occurs when you create an L2 topology and then create some VLAN services on the newly created L2 topology.
Workaround Remove the VLAN using the Cisco IOS CLI interface.
•CSCsk68874
Symptom It takes too long for a newly created L2 topology to appear in the L2 Topology table.
Conditions This problem occurs when you create an RPR L2 topology in a CTM server that contains 3000 configured NEs.
Workaround Wait for a couple of minutes for the L2 topology to appear in the L2 Topology table.
•CSCsl08269
Symptom A timeout operation occurs when you remove an ML card from an RPR topology. However,
the ML card has been provisioned correctly.
Conditions This problem occurs when you create an L2 RPR topology and then remove an ML card from the topology. A timeout occurs when CTM sends the Cisco IOS command to re-enable the POS ports to the corresponding ML cards.
Workaround Perform the operation again after the next L2 resynchronization cycle, which is ten minutes by default.
•CSCsl22254
Symptom Some L2 topologies are not displayed or they appear as split topologies in the Layer 2
Topology table.
Conditions Perform one of the following actions in a scenario where the CTM server is fully loaded with NEs:
•Create a new RPR L2 topology.
•Import a ring of NEs that contains a configured RPR L2 topology.
•Perform a database migration where some RPR L2 topologies are already configured.
Wait until the process completes and then open the Layer 2 Topology table.
This problem occurs when Layer 2 links are discovered as invalid links during Layer 1 circuit discovery.
Workaround Mark the NEs of the RPR L2 topology ring as Out of Service and then In Service.
•CSCso00769
Symptom Unable to delete or modify drops or VLANs that are associated with custom QoS profiles.
Conditions This problem occurs after migrating from CTM R5.0 to a later CTM release.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, enter the following CLI commands:
No interface <interface_name>
Policy-map <policy_map_name>
No class class-map <class_map_name>
•CSCsu30979
Symptom 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.
Then, the drop is removed from the VLAN.
Conditions This problem occurs when the sum of the bandwidth parameters of the new advanced/CIR-PIR QoS profile exceeds the available bandwidth of the drop.
Workaround None.
•CSCsu54034
Symptom The VLAN Database Profile Management wizard hangs when you try to modify a VLAN
database profile on a GE_XP card.
Conditions This problem occurs when you choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > VLAN DB Profile Management and use the wizard to change the ID of an existing VLAN on a GE_XP card.
Workaround Remove the VLAN; then, add a new VLAN with the correct VLAN ID.
•CSCsw62624
Symptom The service ID and customer ID information disappears for VLAN services.
Conditions This problem occurs under the following conditions:
1. In a GNE-ENE setup, create an L2 topology and VLAN services.
2. Add the service ID and customer ID information for the VLAN services.
3. Change the IP address of the ENE that is carrying the VLAN.
4. Restart the NE service.
After the NE service restarts, the service ID and customer ID information is missing for the VLAN services.
Workaround None.
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.
•CSCsd46616
Symptom An LOC occurs and a DCC NE keeps changing to any of the following: GNE, LNE, and ENE.
Conditions This problem occurs when many NEs are synchronizing per partition.
Workaround After restarting the NE service or server, mark a few rings as In Service, in sequence.
•CSCse65683
Symptom 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 and then marked Out of Service and then In Service using CTM.
Workaround None.
•CSCsq50589
Symptom In the Domain Explorer, you can set any password for CTM server-to-NE connections, because
the password syntax is not verified correctly.
Conditions This problem occurs when you add an ONS 15454 SONET NE in the Domain Explorer, select it, and click the NE Authentication tab. In the CTM Server - NE Connection area, you can enter any password without the usual restrictions on password syntax.
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 Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtb54366
Symptom ONS 15305 NEs experience periodic loss of connectivity.
Conditions This problem occurs when the ONS 15305 NE service manages a high number of NEs. When ONS 15305 NEs generate SNMP traps, those traps are queued but not dequeued, because the thread responsible for handling SNMP traps is dead. This problem causes memory issues and then loss of connectivity on the NEs.
Workaround None.
•CSCtc19328
Symptom The CTM Domain Explorer window freezes and you cannot select other NEs.
Conditions This problem occurs on some NEs that have the wrong community string.
Workaround None.
•CSCtc45424
Symptom The ONS 15305 NE Service restarts due to lack of memory.
Conditions This problem occurs when more than 500 NEs are connected to the same ONS 15305 NE service.
Workaround None.
NE Explorer
•CSCed15994
Symptom Setting the Routing Information Protocol (RIP) metric to zero does not generate an error
message.
Conditions In the ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE Explorer > Network tab > RIP subtab, if you change the default RIP metric to 0 (zero), the value is not accepted. There is no error message to inform you that the change is not accepted.
Workaround Zero is not a valid value for the RIP metric. Specify a different value.
•CSCef65097
Symptom The NE Explorer does not refresh the Secure Config Mode value after a mode change.
Conditions This problem occurs under the following conditions:
1. Select an NE with a TCC2 card and insert a TCC2P card in the standby slot. Wait for the TCC2P card to synchronize with the active TCC2 card and become standby.
2. Remove the TCC2 card.
3. Select the NE and launch the NE Explorer. Click the Network tab > Secure Config Mode subtab.
4. Change to secure config mode. Provide the IP address and netmask. The TCC2P card reboots. After several minutes, CTM re-establishes connectivity to the NE and synchronizes the NE data.
5. Return to the NE Explorer window and verify the NE connectivity. The cursor in the NE Explorer window remains an hourglass icon, and the data does not refresh.
Workaround Close and reopen the NE Explorer.
•CSCeh45510
Symptom Clicking the Apply button after modifying the SNMP User Datagram Protocol (UDP) port
does not save the modified value.
Conditions If you modify the SNMP UDP port value and then click Apply, the change is not saved.
Workaround Click any other cell in the table; then, click the Apply button.
•CSCei18858 (Related caveat ID: CSCei18705)
Symptom After entering an invalid value or changing a value in the NE Explorer > NE Defaults tab, the
CTM client hangs for approximately 3 minutes.
Conditions If you change a value or enter a value in the NE Explorer > NE Defaults tab that is outside the valid range, the CTM client hangs for approximately 3 minutes. CTM does not perform fixed field validation on NE defaults values, so there is nothing to prevent you from entering an invalid value. There is no error message displayed before the client recovers.
Workaround None.
•CSCei60347
Symptom The DS3XM-12 NE Explorer > Customer Info tab does not show values for the transmux
conversion ports, which are DS3XM-12 card ports used for VT-DS3 mapping.
Conditions During circuit creation, if you check the VT-DS3 Mapping Conversion check box in the Routing Preferences pane, customer information data is not shown for the transmux conversion ports in the DS3XM-12 card slot NE Explorer.
Workaround None. These ports are used internally for mapping only; customer and service IDs are not attached to these ports.
•CSCin62527 (Related caveat ID: CSCsw61167)
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. Alternatively, 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. Alternatively, 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.
•CSCsl37264
Symptom The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
Conditions When you launch the NE Explorer for an ONS 15454 SDH, the incorrect label "Battery A" is shown on the MIC-A/P module in slot 23. The incorrect label "Battery B" is shown on the MIC-C/T/P module in slot 24. CTM should show Battery B in Slot-23:MIC-A/P and Battery A in Slot-24:MIC-C/T/P.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq87850
Symptom SVLAN ports are not displayed correctly.
Conditions This problem occurs when a VLAN name contains the underscore (_) character.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, do not include the underscore character in a VLAN name.
•CSCsq89269
Symptom 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.
Conditions This problem occurs when you open the NE Explorer for a GE_XP card. If you click the SVLAN tab and then select another GE_XP card on the same NE, the same SVLAN tab is shown, but with the same ports enabled as on the first GE_XP card. Only if you close and reopen the NE Explorer window do you see different data for the two different GE_XP cards.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq96596
Symptom In the NE Explorer for a GE_XP card, the SVLAN tab does not work correctly.
Conditions This problem applies to a GE_XP card with only one PPM. It does not apply to GE_XP cards that have at least two PPMs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr06975
Symptom In the NE Explorer for a GE_XP card, if you click the SVLAN tab, deselect all SVLANs, and
click Apply, an error occurs.
Conditions An error is generated only if CTM debug traces are enabled.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr13995
Symptom In the NE Explorer for a GE_XP card, when you switch from the QoS tab of one GE_XP card
to the QoS tab of a different GE_XP card, the information from the QoS tab of the first GE_XP card is
added to the information in the QoS tab of the second GE_XP card.
Conditions This problem occurs while switching between two GE_XP cards on the same node.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu54724
Symptom In the NE Explorer for a GE_XP card, the list of configured SVLANs is not available.
Conditions This problem applies to the client port of a GE_XP card configured in Selective mode.
Workaround From the Domain Explorer, choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > VLAN DB Profile Management and view the list of configured VLANs.
•CSCsv70799
Symptom CTM and CTC show different values for LBC and OPT parameters on MRC-25G-4 cards.
Conditions In the MRC-25G-4 card NE Explorer > Transceiver tab, CTM shows incorrect values for LBC and OPT parameters. Instead, CTM should show blank values for these parameters.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv70863
Symptom In the card-level NE Explorer > Line tab > Line Config subtab > Admin State field, if you
change the administrative state of the port from In Service to Out of Service, a warning dialog box
prompts you for confirmation. If you click Yes, the port changes to Out of Service. If you click No, the
port remains In Service. If you click the X in the upper corner of the warning dialog box to cancel the
operation, the port changes to Out of Service.
Conditions If you click the X in the upper corner of the warning dialog box to cancel the operation, the port changes to Out of Service. The port should remain In Service.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•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.
•CSCsw53135
Symptom In the NE Explorer for an AIC card, the Alarm Extenders tab > External Alarms subtab >
Raised check box does not indicate that an alarm has been raised.
Conditions This problem occurs when you create an external alarm for an AIC card. The Alarm Browser shows that the alarm was raised. However, in the NE Explorer for the AIC card, the Raised check box remains unchecked in the Alarm Extenders tab > External Alarms subtab. In CTC, the Raised check box is checked.
Workaround None.
•CSCsw53170
Symptom In the NE Explorer for a DS1 card, the VT tab > Customer Info fields are empty.
Conditions This problem occurs when you create an STS circuit on a DS1 card. The VT tab populates correctly after synchronizing with CTC. However, the Customer Info fields remain empty.
Workaround None.
•CSCsw61167
Symptom Cannot create the default RIP address summary.
Conditions This problem occurs under the following conditions:
1. Launch the NE Explorer for any CTC-based NE.
2. In the Network tab > RIP subtab, check the RIP Active check box.
3. Click Apply.
After 30 minutes or longer, the default address summary is not created. Even if you refresh, update, or close and reopen the NE Explorer, the default address summary is not visible in CTC or CTM. The same operation works correctly in CTC.
Workaround None.
•CSCsw61380
Symptom It is possible to create a RIP address without first activating RIP.
Conditions This problem occurs under the following conditions:
1. Launch the NE Explorer for any CTC-based NE.
2. In the Network tab > RIP subtab, check the RIP Active check box.
3. Click Create and create a default entry.
4. Click Apply. The RIP Active check box becomes disabled, and the RIP entry is created.
5. Select a row in the RIP Address Summary table. The Create and Delete buttons are enabled. The RIP Active check box remains disabled.
6. Create another RIP address. The new address is created successfully and appears in CTC. However, the RIP Active check box remains disabled.
Workaround None.
•CSCsy66604
Symptom In CTM, you cannot change any address settings when the node is in secure config mode.
Conditions This problem occurs when the node is in secure config mode. If you change any setting in the NE Explorer > Network tab > Address subtab, the operation fails with the following error message: "EID-465: The change was not saved successfully. Data will be reset to the previous values." The same operation works correctly in CTC.
Workaround None.
•CSCsy69011
Symptom NEs become unreachable after a secure IP address change.
Conditions This problem occurs when you use the NE Explorer > Network tab > Secure Config Mode subtab to change the secure IP address of a node. After the IP address change, CTM loses connectivity to the NE.
Workaround Complete the following steps:
Step 1 After you change the secure IP address and CTM loses connectivity to the NE, mark the NE as Out of Service.
Step 2 In the Domain Explorer > Address tab, manually change the NE IP address of the GNE by inserting the new back panel IP address (the secure IP address).
Step 3 Mark the NE as In Service.
•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 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.
Network Map
•CSCsb52823
Symptom Cannot configure default layouts in the Network Map as expected.
Conditions This problem applies to a ring that contains 10 or more NEs.
Workaround Configure the view manually.
•CSCsk27692
Symptom 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.
Conditions This problem occurs after using the Add/Remove Card wizard to add a new card to an L2 topology.
Workaround Mark the nodes at either end of the link as Out of Service and then back In Service.
•CSCsk80234
Symptom Some NEs are not visible in the Network Map.
Conditions This problem occurs when you set the declutter layout and change the zoom in the Network Map.
Workaround None.
•CSCsk80234
Symptom Some NEs are not visible in the Network Map.
Conditions This problem occurs when you set the declutter layout and change the zoom in the Network Map.
Workaround None.
•CSCsw37526 (Related caveat ID: CSCtb98889)
Symptom When you zoom in on the Network Map and save the view as the default, the following error
message is generated:
EID-700: An error occurred while saving nodes coordinates to the database. Refresh the
view and retry.
Conditions This problem occurs whenever you zoom in on the Network Map. This problem also occurs intermittently when you try to save the map view.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
Performance Monitoring
•CSCei10567
Symptom When the PM service is restarted, the error message "Cannot collect PM on <NE_name>" is
recorded in the Error Log during the first PM collection interval.
Conditions In a GNE-ENE scenario, when the PM service is restarted, the error message "Cannot collect PM on <NE_name>" is recorded in the Error Log. This problem occurs intermittently when the PM collection fails for the first interval.
Workaround Before restarting the PM service, enable robust PM data collection for the NEs in a GNE-ENE setup. When the first collection interval is successfully retrieved after the PM service restarts, you can disable robust PM data collection if it is not required.
•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 to GFP. It should be displayed as N/A when the ports are not set.
2. The CTM GateWay/CORBA real-time PM (RTPM) is not working. Ports 1 and 0 are generating incorrect data, which does not match the data in CTM or CTC. The RTPM generates a -1 value instead of N/A when the ports are provisioned as HDLC.
Conditions This problem occurs when the POS ports are set to HDLC for the ML cards. The bulk PM response should give an empty string for GFP parameters instead of 0.
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.
•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.
•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 be Selected 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
|
•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 table.
•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 back 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:
•CSCsk86875
Symptom Some 1-day PM buckets are missing.
Conditions This problem occurs when PM collection is enabled on ONS 15600 SONET or ONS 15600 SDH NEs, and the NE time zone is not GMT. The nodes collect the 1-day PM data at midnight. In order for all nodes to collect the PM data at the same time, their clocks must be set to the GMT time zone. The ONS 15600 SONET and ONS 15600 SDH NEs do not support a different time zone. A CTC bug exists (CSCsk98397).
Workaround Set the node clocks to the same GMT time zone to enable all the nodes to collect the PM data at the same time.
•CSCsl22172
Symptom 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.
Conditions This problem occurs when you use the PM Query by Category wizard on ML-MR-10 cards for real-time PM. This problem does not affect other cards or any historical PM data.
Workaround Use the PM Query by NE Model wizard.
•CSCsl37025
Symptom The PM service restarts after several days. The error log contains a large number of errors
associated with writing PM data to the database.
Conditions This problem occurs when there are several PM service instances running for the same PM service. It also occurs when the PM service is activated before the NE discovery process starts.
Workaround Deactivate and then reactivate all PM service instances. To avoid this problem, activate the PM service only after the network has been completely discovered, and all NEs are in service.
•CSCsq26362
Symptom The output file generated from getHistoryPMData returns duplicate rows.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv40528 (Related caveat ID: CSCsw22308)
Symptom VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information
is shown with incorrect numbers, making it impossible to tell which VT the PM data is for.
Conditions For VT1.5 PM data for DS3XM-12 cards, the numbers in the Physical Location and Interface columns are jumbled, making it impossible to tell which VT PM you are looking at on a given line. This problem occurs with CTC releases 6.0.1, 7.0.0, 7.2.2, and 8.0.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsw91974
Symptom In a large network of GNEs and ENEs, CTM fails to collect PM data.
Conditions This problem occurs when each PM service instance manages a large network of GNEs and ENEs, and each GNE manages more than 10 ENEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. After installing the service pack, 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. In the CTM Control Panel, stop all CTC-based NE services.
b. Log into the CTM server as the root user.
c. Go to the /opt/CiscoTransportManagerServer/bin directory and make a backup copy of the jnet.sh file.
d. Using vi to edit the jnet.sh file, search for the string "Dctm.xmlFW.processFaults" and add the following lines. Do not add any blank lines or any spaces after the slash (\).
-Dctm.ne.dssPollerEnabled=true \
-Dctm.ne.dssPollerCacheEnabled=true \
-Dctm.ne.dssPollerNumOfRetry=2 \
-Dctm.ne.dssPollerConfiguratorInterval=30 \
e. Save the changes and exit.
f. In the CTM Control Panel, restart the CTC-based NE services.
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.ne.dssPollerGlobalFilePath="/opt/CiscoTransportManagerServer/cfg" \
where ctm.ne.dssPollerGlobalFilePath is the directory that contains the list of DSSs in the network written by the NE service.
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 300 seconds. Do not add any blank lines or any spaces after the slash (\).
Step 7 Save the changes and exit.
Step 8 In the CTM Control Panel, restart the CTC-based PM services.
•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.
•CSCsz83568
Symptom The following null pointer exception appears in the pmservice.log file for MRC-12 cards:
[com.cisco.stardm.service.pm.ons15454.ONS15454DBWriter,DB WriterWorker#18]
NE UMSWMIR030 : VT1-5-10-1-4-7-4-10 - module Type: 219 at shelf 1 and slot 5 raised
NullPointerException in parse() method.
java.lang.NullPointerException
Conditions This problem occurs on MRC-12 cards where VT circuits are provisioned.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtc55148
Symptom Automatic and manual PM data pruning does not work on small CTM servers.
Conditions This problem occurs after installing the CTM R8.5.0.387.6 patch on a small CTM server.
Workaround Truncate all non-empty PM tables in the database. Then, install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCte69670
Symptom The PM service logs contain errors, and PM data is not collected for some rows.
Conditions This problem applies to DS3XM-12 cards on NE release 6.0.1.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
Miscellaneous
•CSCec49550
Symptom The dashboard comes to the front when the Solaris desktop is locked.
Conditions Start the CTM client and keep the dashboard open, then wait for Solaris to lock due to inactivity. Even when the desktop is locked, the dashboard comes to the top of the locked Common Desktop Environment (CDE).
Workaround From the CDE window Style Manager, uncheck Allow primary windows on top.
•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.
•CSCsb69510
Symptom The CTM client hangs while opening the Network Map and NE Explorer windows.
Conditions When you open the Network Map and NE Explorer (and other windows) in quick sequence, a Java problem with managing animated icons could occur, causing the CTM client GUI to freeze.
Workaround Close and reopen the CTM client.
•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 The 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.
•CSCse50587
Symptom The number of alarms shown in the CTM Dashboard is not synchronized with the number of
alarms shown in the Domain Explorer's Management Domain Properties.
Conditions This problem occurs when a high number of alarms is raised constantly.
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, you must 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 on which CTM works correctly.
•CSCsj54751
Symptom The CTM client user interfaces are dimmed for several minutes.
Conditions This problem occurs when the NE default data is retrieved from remote, DCC-connected NEs.
Workaround None.
•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 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 Synchronize from the CTM server to refresh the line parameter information.
•CSCsk44426
Symptom The CTM client crashes.
Conditions The CTM client virtual machine crashes because of a Java bug. See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6337544.
Workaround None.
•CSCsk71257
Symptom The Change Card function does not change the card in the shelf, module, and tree views.
Conditions If a card is changed using the Change Card menu option, the new card is not displayed in CTM but the Line tab in the NE Explorer contains the port information of the old and new cards. The new card is visible in CTC. The issue is that CTC does not send the events related to deleting the old card.
Workaround Force a Refresh from NE operation.
•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:
•Modify the NE default values using CTC.
•Save the NE default values in a file using the Save to file option in the NE Defaults Management wizard. Modify the file using an editor and load the modified NE default values using CTC.
•CSCsk96257
Symptom The CTM client freezes.
Conditions This problem occurs when the Active GateWay/CORBA Users table is in auto-refresh mode and there is an excessively large flow of events.
Workaround None.
•CSCsl15115
Symptom 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.
Conditions This problem occurs in very rare conditions.
Workaround Restart the NE service, if possible. This disconnects all of the nodes managed by the NE service instance.
•CSCsl17182
Symptom Unable to open or modify a TL1 tunnel.
Conditions This problem occurs when a TNE is in Preprovisioned state.
Workaround Mark the TNE as In Service and then repeat the operation.
•CSCsl26218
Symptom 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.
Conditions This problem occurs when the CTM server manages 3000 NEs, most of which are simulated NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, restart the network service.
•CSCsl31836
Symptom 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.
Conditions This problem occurs when the OtherLegal.txt file is present on the CTM server workstation.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsl34530
Symptom The network topology is not updated in CTM.
Conditions In some cases, you are unable to receive the link status events for the entire topology if an NE release 8.0 or earlier is down, turned off, or unreachable. The CTM NCP is frozen until the NE is turned on or marked as Out of Service.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, mark the unreachable NE as Out of Service and then In Service.
•CSCsl48499
Symptom The backup files are not listed in the Backup File dialog box after choosing Administration >
Memory Backup Upload in the Domain Explorer.
Conditions This problem occurs on a node that has a space in the node name.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, rename the node. The new name should not contain any spaces.
•CSCso01840
Symptom It takes a long time to discover NEs after the NE service restarts.
Conditions This problem occurs in a network of GNEs and ENEs when all of the NEs are in service before the NE service restarts.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. After installing the service pack, you must complete the following steps to enable the dynamic DSS:
Step 1 In the CTM client Control Panel, stop all CTC-based NE services.
Step 2 As the root user, log into the CTM server workstation.
Step 3 Go to the /opt/CiscoTransportManagerServer/bin directory.
Step 4 Make a backup copy of the jnet.sh file.
Step 5 Use vi to edit the jnet.sh file. Search for the string Dctm.xmlFW.processFaults and add the following lines. Do not add any blank lines or any spaces after the slash (\).
-Dctm.ne.dssPollerEnabled=true \
-Dctm.ne.dssPollerCacheEnabled=true \
-Dctm.ne.dssPollerNumOfRetry=2 \
-Dctm.ne.dssPollerConfiguratorInterval=30 \
Step 6 Save the changes and exit.
Step 7 In the Control Panel, restart the CTC-based NE services.
•CSCso01900
Symptom The CTC-based NE service takes a long time to reconnect and discover NEs.
Conditions This problem occurs in a large or high-end network of GNEs or ENEs under one of the following conditions:
•A circuit is created or modified.
•A system parameter is modified.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCso01942
Symptom CTM takes a long time to discover a large network of GNEs and ENEs.
Conditions This problem occurs when each NE service instance manages a large network of GNEs and ENEs, and each GNE manages more than ten ENEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. After installing the service pack, you must complete the following steps to enable the dynamic DSS:
Step 1 In the CTM client Control Panel, stop all CTC-based NE services.
Step 2 As the root user, log into the CTM server workstation.
Step 3 Go to the /opt/CiscoTransportManagerServer/bin directory.
Step 4 Make a backup copy of the jnet.sh file.
Step 5 Use vi to edit the jnet.sh file. Search for the string Dctm.xmlFW.processFaults and add the following lines. Do not add any blank lines or any spaces after the slash (\).
-Dctm.ne.dssPollerEnabled=true \
-Dctm.ne.dssPollerCacheEnabled=true \
-Dctm.ne.dssPollerNumOfRetry=2 \
-Dctm.ne.dssPollerConfiguratorInterval=30 \
Step 6 Save the changes and exit.
Step 7 In the Control Panel, restart the CTC-based NE services.
•CSCsq80551
Symptom CTM must add support for ONS 15305 R3.0.6 NEs.
Conditions See Symptom.
Workaround Install the CTM R8.5.0.368.3 or later patch.
•CSCsq94272
Symptom You cannot schedule a job after December 31, 2008, because the highest value allowed for the
year is 2008.
Conditions This problem applies to all scheduled jobs, such as Administration > Memory Backup, Memory Restore, Software Download, and so on. To reproduce this problem, choose Administration > Memory Backup. In the Time area, click the At Time radio button; then, try to set a date after December 31, 2008. The operation fails because you cannot select a year later than 2008.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr16489
Symptom CTM must add support for release 4.1.3 NEs.
Conditions See Symptom.
Workaround Install the CTM R8.5.0.368.3 or later patch.
•CSCsr44800
Symptom CTM must add support for release 4.1.6 NEs.
Conditions See Symptom.
Workaround Install the CTM R8.5.0.375.2 or later patch.
•CSCsr61773
Symptom CTM must add support for release 4.6.2 NEs.
Conditions See Symptom.
Workaround Install the CTM R8.5.0.375.2 or later patch.
•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 the automatic refresh.
Conditions This problem occurs in CTM R8.5.
Workaround Do one of the following workarounds:
•Click the Refresh button.
•Close and then reopen the window.
•CSCsr70890
Symptom The designated GNE list is incomplete. It does not contain all the IP addresses listed in the
designatedGnes.cfg file.
Conditions This problem occurs when the designatedGnes.cfg file is uploaded to the system before the NE service of CTC-based NEs is started. This problem applies only to static DSS functionality. If the list of DSS IP addresses is not correctly filled out, some GNEs may be identified as LNEs and therefore cannot proxy for other NEs such as ENEs.
Workaround Upload the designatedGnes.cfg file only after the NE service has started.
•CSCsr71261
Symptom The designated GNE list, which includes the SOCKS server list, contains incorrect IP
addresses.
Conditions This problem occurs when the dynamic DSS functionality is disabled while the caching mechanism is enabled. This problem also occurs when the dynamic DSS is enabled and then disabled.
Workaround Add the following property to the /opt/CiscoTransportmanagerServer/bin/jnet.sh script; then, restart the NE service:
-Dctm.ne.dssPollerCacheEnabled=false \
•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.
•CSCsu26103
Symptom The Supported NE table > Add Supported NE dialog box shows incongruous data.
Conditions Like most CTM tables, the Add Supported NE table supports a customize view function that allows you to select the columns to be displayed, and the order in which to display them. CTM allows you to save your customized table view so that the next time you open the table, it is displayed in the same manner in which it was saved.
With this caveat, however, when you customize the Supported NE table and then launch the Add Supported NE dialog box, the dialog box shows data in the wrong fields or shows empty fields.
Workaround Move the columns in the Supported NE table back to their original order.
•CSCsu37369
Symptom The Audit Log records a flood of events that are similar to the following:
AUD-147: NE (xxx) Property Changed - New Subnet Id (nn)
AUD-5018: NE (xxx) has changed its Subnetwork ID from ...
AUD-169: Topology Changed - Subnet (Subnetwork-nn) Added
Conditions This problem occurs during the discovery of a complex meshed network, when you mark NEs as Out of Service and then In Service.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsw88114
Symptom In a filter dialog box, the User Specified radio button allows only 2009 to 2018 as the year.
Conditions Many CTM tables have Filter dialog boxes that let you filter data in different ways and display the results in a table. You can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour. When this bug occurs, you can only select from 2009 to 2018 as the year.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsw98325
Symptom Cannot export tables in HTML format from the CTM client.
Conditions This problem occurs if the directory where the CTM client is installed has a blank space in the name. For example, if the installation directory is C:\Program Files\CTM (with a space between Program and Files), you cannot export tables in HTML format.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, export tables in .csv format or change the name of the directory where the client is installed.
•CSCsx17951
Symptom The Find dialog box > Metro DWDM Circuits option does not find ONS 15454 OCH circuits.
Conditions In the Domain Explorer window, if you choose Edit > Find and choose Metro DWDM Circuits from the Object Type drop-down list, the search does not find any ONS 15454 OCH circuits. This problem occurs because the Metro DWDM Circuits option applies only to ONS 15501, ONS 15530, and ONS 15540 NEs. It does not apply to other NE types, such as the ONS 15454.
Workaround This caveat is resolved with a change to the Cisco Transport Manager Release 8.5 User Guide. Section 1.5.5.1, "Finding Data," now includes this note: "The Metro DWDM Circuits option applies only to ONS 155xx NEs. For other NE types—such as the ONS 15454—the Metro DWDM Circuits option returns no results. To filter circuits on ONS 15454 NEs, use the Circuit table filter."
•CSCsx52287
Symptom Event notification is not audible.
Conditions After multiple reconfigurations of "Play Audible Notification For" in the User Preferences dialog box, the sound notification might stop working, although the CTM client generates a notification dialog box when new events arrive. This problem is not always reproducible.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsy23134
Symptom CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and
ONS 15454 SDH R8.6 NEs.
Conditions See Symptom.
Workaround Install the CTM R8.5.0.387.6 or later 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 through CORBA), the CTM client froze.
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
Symptom After performing NE software upgrades, the SM service restarts NE services.
Conditions This problem occurs if the Java Virtual Machine (JVM) PermGen memory space is full. The NE service logs contain a PermGen OutOfMemoryException.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternately, increase PermGen memory by modifying the /opt/CiscoTransportManagerServer/bin/ jnet.sh file, as follows:
•Replace -XX:MaxPermSize=128m with -XX:MaxPermSize=256m
•Replace -XX:PermSize=128m with -XX:PermSize=256m
•Add -XX:+CMSPermGenSweepingEnabled
•Add -XX:+CMSClassUnloadingEnabled
•CSCte41594
Symptom CTM does not support the Carrier Ethernet Multirate 6 (CE-MR-6) card.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtf30749
Symptom CTM must add support for ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.5.4
NEs.
Conditions See Symptom. Note the following constraints for the ONS 15310 MA:
•The CTM R8.5.0.410.3 patch supports the ONS 15310 MA R8.5.4 with NE version string 08.54-010D-07.11.
•The CTM R8.5.0.430.3 and later patch supports the ONS 15310 MA R8.5.4 with NE version string 08.54-010D-30.09.
If you are using CTM R8.5.0.410.3, you can manually add the 08.54-010D-30.09 version string to the Supported NE table. To do this:
Step 1 In the Domain Explorer window, choose Administration > Supported NE Table.
Step 2 Select a row that lists "Cisco ONS 15310 MA" as the NE model, "08.50-007I-19.18" as the software version, and "15310 MA 8.50" 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 08.54-010D-30.09 in the Software Version field. Change the Version Name field to 15310 MA 8.54.
Step 5 Click OK.
Step 6 CTM asks for confirmation to manage the new version. Click OK.
Workaround Install the CTM R8.5.0.430.3 or later patch. The 8.5.4 NE version is added automatically to CTM when the CTM R8.5.0.430.3 or later patch is installed.
•CSCtg80725
Symptom After a successful login, the CTM client remains stuck at the Welcome screen. The shell where
the CTM client was started with the ctmcdebug-start command reports the following exception:
Exception in thread "main" java.lang.NoSuchMethodError:
org.apache.log.output.io.rotate.RotatingFileTarget.<init>(ZLorg/apache/log/format/Formatter;Lorg/apach
e/log/output/io/rotate/RotateStrategy;Lorg/apache/log/output/io/rotate/FileStrategy;)V
at org.jacorb.util.LogKitLoggerFactory.setDefaultLogFile(LogKitLoggerFactory.java:207)
at org.jacorb.util.Environment.initLogging(Environment.java:597)
at org.jacorb.util.Environment.addProperties(Environment.java:397)
at org.jacorb.orb.ORB.set_parameters(ORB.java:1602)
at org.omg.CORBA.ORB.init(Unknown Source)
at com.cisco.stardm.framework.utils.GlobalUtils.initORB(GlobalUtils.java:194)
at com.cisco.stardm.framework.CTMClient.initConfigManager(CTMClient.java:1395)
at com.cisco.stardm.framework.CTMClient.<init>(CTMClient.java:676)
at com.cisco.stardm.framework.CTMClient.main(CTMClient.java:154)
Conditions See Symptom.
Workaround As the user running the CTM client, go to the home directory (which is / for the root user). In the home directory, locate the jacorb.properties file and rename it to jacorb.properties.old.
CTM Server and Database Caveats
•CSCsc41831
Symptom Client disconnection occurs during bulk NE discovery.
Conditions This problem occurs when you add 500 nodes to CTM. When the nodes are in In-Sync configuration and you add another 500 nodes, the client might crash.
Workaround Add a small numbers of nodes, then wait for the synchronization to finish. Add another small number of nodes and wait for synchronization to complete. Continue until you reach the maximum number of supported NEs.
•CSCsd67571
Symptom Clearing alarms associated with NEs that are marked as Out of Service takes a long time.
Conditions When an NE is marked Out of Service, CTM disconnects from the NE and clears NE job, alarm, and other information. Clearing the data may take several minutes. During this process, the NE is shown as Out of Service but the server continues to clear the NE data.
Workaround After marking the NE as Out of Service, wait at least one minute after all alarms on the NE disappear before marking the NE as In Service.
•CSCsf96121
Symptom If you provide a valid configuration that is inconsistent with the current configuration, the NE
generates a warning message rejecting the configuration. But the warning message that is generated by
the NE will not be displayed as part of the popup message in the GUI that notifies you of the failed
configuration.
Conditions This applies to any valid configuration that cannot be done because it conflicts with the current NE configuration.
Workaround Complete the following steps:
Step 1 Perform a resynchronization and verify the updated configuration.
Step 2 Perform one of the following based on the result of Step 1:
•Correct the attempted configuration and reapply it.
•Modify the existing configuration to complement the attempted configuration and reapply the existing configuration.
•CSCsi06511
Symptom Unable to complete a database backup in the Control Panel because of the tar operation in the
/oraclesw9i directory. The database backup process gets stuck at some point and no further logs are
created.
Conditions This problem occurs on a high-end CTM server.
Workaround Get a database backup manually. For example, execute the backupdb.sh script from the server.
•CSCsi25561
Symptom 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."
Conditions See Symptom.
Workaround Ignore the error message.
•CSCsj01676
Symptom 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.
Conditions If you log in as an unknown user, an alarm is generated in the Alarm Browser and the following error message appears: "EID-197: Max no. of login attempts exceeded. Application will be shut down." If you try the same operation several times, the Alarm Browser is filled with the same alarm because the alarms are not cleared even after 30 minutes. The Login Disable Period is set to 30 seconds.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, change the Login Disable Period to 5 seconds. All of the alarms are cleared in the Alarm Browser.
•CSCsk19647
Symptom 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.
Conditions This problem occurs when CTM manages a large number of NEs in a single network partition that is near its 500 NE limit, and a GNE is added. If the NEs attached to the newly added GNE exceed the network partition limit, the excess NEs are added, but CTM cannot manage or connect to them.
Workaround None.
•CSCsk50113
Symptom The CTM client gets disconnected from the CTM server.
Conditions This problem occurs on a highend CTM server installation with 3000 NEs, 30 alarms generated per second, CTM GateWay/TL1, CTM GateWay/CORBA, and CTM GateWay/SNMP running, and 30 CTM clients connected. Two of the four CTM GateWay/TL1 users who were initially connected to the CTM server were disconnected and then reconnected. A circuit is created and deleted every minute.
Workaround Restart the CTM client.
•CSCsk63579
Symptom NE alarms are not saved in the database and not displayed in the Alarm Browser and Alarm
Log.
Conditions This problem occurs when the number of alarms stored in the database exceeds the 8-digit limit of the ACTIVEALARMINDEX column of the Active_Alarm_Table. Enter the following command to verify this problem:
SELECT MAX (ACTIVEALARMINDEX) from ACTIVE_ALARM_TABLE;
A value of 100,000,000 exceeds the limit of the ACTIVEALARMINDEX column.
Workaround Complete the following steps:
Step 1 Enter the ctms-stop command to shut down the CTM server.
Step 2 Enter the following command:
alter table ACTIVE_ALARM_TABLE modify ACTIVEALARMINDEX number (16);
Step 3 Enter the ctms-start command to start the CTM server.
•CSCsk84707
Symptom CTM PM pruning fails due to a buffer overflow error.
Conditions The following error message appears in the prune*.err files generated in the /oraclesw9i/admin/CTM/udump directory:
ORA-20000: ORU-10027: buffer overflow, limit of 20000 bytes, -20000
In CTM R8.5, the files are generated in the /oracle/admin/CTM/udump directory.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. If the service pack does not resolve the issue, connect to the database as ctmanager and execute the prune_pm_enterprise.sh script. The script increases the buffer size.
•CSCsl06339
Symptom 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 other start time of other processes. All
other processes work correctly, including CTM GateWay/CORBA, which is based on the notification
service.
Conditions The notification service is started and used only when CTM GateWay/CORBA is installed and running. It does not restart under normal conditions. The root cause of the restart is unknown.
Workaround None.
•CSCsl09775
Symptom NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the
/$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
Conditions This problem occurs in medium, large, and high-end servers.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, as the ctmanager user, run the prune_optical_package_enterprise.sql script from SQL*PLUS.
•CSCsl12064
Symptom ONS 15454 SDH NEs do not go to In Service state after upgrading from CTM R7.0 to R8.0
and then to R8.5. The ONS 15454 SDH network service reloads every 10 to 20 minutes.
Conditions This problem occurs if you have a high-end network configuration and upgrade from CTM R7.0 to R8.0 and then to R8.5.
Workaround Open a shell on the CTM server workstation and complete the following:
Step 1 Enter the following command to enter the bin directory:
cd /opt/CiscoTransportManagerServer/bin
Step 2 Enter the following command to get a copy of the jnet.sh script:
Step 3 Enter the following command to add a write permission to the jnet.sh script:
Step 4 Enter the following command to edit the jnet.sh script using a Vi editor:
Step 5 Locate the following line:
and replace it with the following:
$jrepath -server $4 -Xmx2750m \
Step 6 Save your changes.
Step 7 Restart the ONS 15454 SDH NE services in the CTM client.
•CSCsl22236
Symptom 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.
Conditions This problem occurs if the network contains any of the preceding NEs.
Workaround None.
•CSCsl26108
Symptom CTM does not perform quickly when connecting, discovering, and resynchronizing
CTC-based devices such as the ONS 15310, ONS 15327, ONS 15454, and ONS 15600.
Conditions This problem occurs very rarely. It is caused by wrong formats of XML messages. It does not affect any CTM functionality but it impacts CTM performance.
Workaround Since the XML messages are stored inside a volatile cache, the problem is resolved when the cache is automatically discarded by the Java virtual machine. Alternatively, you can perform either of the following workarounds:
•Restart the affected CTM NE service.
•Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsl34139
Symptom The MGX NE service does not start automatically even if some MGX NEs are present in the
network. The MGX NEs are connected but cannot be managed.
Conditions This problem occurs when you upgrade to CTM R8.0 from CTM R7.0, which contains MGX modules. After upgrading, add several MGX NEs to CTM R8.0 and then upgrade to CTM R8.5. The exact migration path is CTM R7.0 to CTM R7.0.0.370.1 to CTM R7.0.0.410.1 to CTM R8.0 to CTM R8.0.0.877.1 to CTM R8.5.
Workaround Complete the following steps:
Step 1 As a root user, enter the following command:
cp /opt/CiscoTransportManagerServer/bin/admin_MGX8880.sql <Oracle_home>
where <Oracle_home> is the home directory of the Oracle user. For example, the home directory is /oraclesw9i for Oracle9i and /oracle for Oracle 10.
Step 2 Enter the following commands:
chown oracle:dba admin_MGX8880.sql
Step 3 Enter the following command to log into the CTM server as the Oracle user:
Step 4 Enter the following commands to connect to the database:
sqlplus CTMANAGER/CTM123!
•CSCsl34542
Symptom 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.
Conditions This problem occurs under the following conditions:
1. In the CTM client Domain Explorer window, choose Administration > Control Panel > Database Operations > Export and export the database while the server is running and updating the database.
2. Import the database on another CTM server.
3. Upgrade the CTM server to the next CTM release.
The root cause of this problem is an inconsistent creation of the database export dump. This problem is not systematic.
Workaround Repeat the database export, but first shut down the CTM server or reduce the CTM server activity to a minimum. In doing so, the export dump will be consistent.
•CSCsl45830
Symptom CTM GateWay/TL1 restarts.
Conditions This problem occurs on a scalability test server with 3000 NEs, and OSS TL1 clients are disconnected and reconnected periodically. Users who do not use CTM GateWay/TL1 are not affected. This problem occurs in rare conditions.
Workaround None.
•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 R8.5, 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.
•CSCsl84311
Symptom Some debug and performance tuning tools show wait events on semaphore resources. This
problem does not cause major loss of system functionality.
Conditions This problem is due to incorrect settings on the following kernel parameters:
Workaround Using the commands reported in the Cisco Transport Manager Release 8.5 Installation Guide, set the correct number of semaphores on the following kernel parameters:
For high-end installations, it is recommended that you configure the Oracle resource processes in the parameter file to 2000. Complete the following steps:
Step 1 Enter the following commands:
cd $ORACLE_BASE/admin/$ORACLE_SID/pfile
Step 2 Locate the file init$<ORACLE_SID>.ora. For example, if the Oracle SID is CTM, locate the file named initCTM.ora.
Step 3 Enter the following command to copy the file:
cp init$ORACLE_SID.ora init$ORACLE_SID.ora_BCK
Step 4 Use an editor to modify the file. Search for the "processes" string and change the value to 2000.
Step 5 To enable the setting, shut down and restart Oracle.
•CSCsm37071
Symptom IMR is an OpenFusion service that is required for the correct behavior of the CTM server. In
certain environments, IMR shuts down unexpectedly, causing the SM service and any connected
services to shut down and restart.
Conditions This problem occurs when the CTM server is running with IMR enabled, and something causes an uncontrolled shutdown of IMR.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsm41384
Symptom The /tmp directory on the application server for log4j contains error messages and cleared
CTM alarms that are unacknowledged. log4j is the library that manages log messages in the database
and in the log files.
Conditions This problem occurs when an acknowledged alarm is generated on a node, but the error log in the /tmp directory does not report the acknowledged alarm. The /tmp directory contains error messages that are similar to the following:
log4j:ERROR DBException while writing audit message to DB.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCso00123
Symptom The CTM client cannot connect to the CTM server. The following error message appears:
"EID-382: The CTM server is initializing. Please try again after some time."
Conditions This problem occurs after adding 250 ONS 15454 SDH NEs using bulk NE addition in the Domain Explorer. While the NE discovery is in progress, shut down CTM using the ctms-stop command; then, reboot the UNIX server. When the CTM server starts up automatically, the CTM client is unable to connect to the CTM server.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, enter the commands ctms-stop and ctms-start to restart the CTM server. If the EID-382 error message appears while connecting to the server, check the /opt/CiscoTransportManagerServer/cfg/ServiceManager.ior file. If the file exists but the size is zero, it means that the caveat condition was met. Restart the CTM server to clear the error.
•CSCso35202
Symptom 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.
Conditions No specific conditions are noted.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, to fix the shutdown problem, enter the following commands to manually shut down Oracle before shutting down the server workstation:
shutdownimmediate $ORACLE_HOME"
To fix the startup problem, enter the following commands:
•CSCso44836
Symptom On a dual-server setup, the automatic pruning of the /db05 directory does not work. CTM*.arc
files accumulate in /db05 and do not move automatically to /ctm_backup.
Conditions This problem occurs under the following conditions:
•The CTM server and the CTM database are installed on separate UNIX workstations.
•CTM is installed in ARCHIVELOG mode.
•Automatic pruning of /db05 is enabled in the Control Panel > Database Properties pane > Database Operations tab.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. To prevent /db05 from filling up, manually move the *.arc files to another file system (such as /ctm_backup).
•CSCsq24237
Symptom 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.
Conditions This problem is a result of integrating code changes that fix CSCsm17261.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr53609
Symptom A CTM server core dump file is created when the CTM server shuts down.
Conditions This problem occurs when the logging level is set to Trace.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, set the logging level to an error level other than Trace before entering the ctms-stop command to shut down the CTM server.
•CSCsr70191
Symptom 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.
Conditions This problem occurs when you log into the UNIX shell and change the system date of the UNIX workstation on which the CTM server is running.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr95859
Symptom A CTM server core dump file (ilogCleanup) is created when the CTM server shuts down.
Conditions This problem occurs on a Sun Solaris 10 CTM server when CTM processes are started using the ctms-start CLI command; then, the NE Service process is stopped from the CTM GUI.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu22851
Symptom A memory leak occurs on the CTM server because of zombie LWP creation.
Conditions This problem occurs when you cross-launch a CLI or TL1 interface from the CTM client to an NE; for example, when you choose Configuration > CTC-Based SONET NEs > Launch TL1 Interface. The same module is used when you open the NE Explorer, double-click an NE, double-click an ML card, click the Configuration tab, and click Launch CLI.
If you continuously open CLI or TL1 telnet sessions, the memory leaks could cause the CTM server to exhaust 4 GB of memory, at which point the CTM server restarts.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, open TL1 or CLI telnet sessions directly on the node, if possible.
•CSCsu67460
Symptom Even though automatic alarm acknowledgement is enabled, cleared alarms do not move from
the Alarm Browser to the Alarm Log.
Conditions This problem occurs when the alarms clear during a period when CTM is not monitoring the node, and when the Robust Fault Synchronization feature is enabled on CTM.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Note that if the Alarm Browser contains cleared alarms when you apply the service pack, those alarms will remain in the Alarm Browser. You must manually acknowledge the alarms to move them to the Alarm Log.
•CSCsv04954
Symptom When logging into the CTM client, the login fails.
Conditions This problem occurs with cipher text of an encrypted password when the first byte is set to zero (0). For example, the password "cisco456" does not work.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv81066
Symptom The NE service freezes after discovering a large NE network.
Conditions This problem occurs when the CTM server is managing large networks.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv97842
Symptom A memory leak occurs on the CTM server because of uncontrolled thread creation.
Conditions This problem occurs when a CTM user tries to log in with credentials that the CTM server does not recognize (for example, the username is mistyped or does not exist). The failed login attempt is registered in the CTM Users table. The CTM server stores the IP address used to log in, as well as the number of login attempts for that IP address. If the number of login attempts exceeds the Max Retries value, the IP address is locked. When the Login Disable Period expires, the IP address is unlocked, and a thread is created. The thread updates the CTM Users table and exits. The thread becomes a zombie thread (or lightweight process), because the thread creation is not controlled.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, choose Administration > Control Panel. In the Security Properties pane > Login Preferences area, check the Infinite check box.
•CSCsw43520
Symptom A memory leak occurs on the CTM server because of zombie LWP creation during startup.
Conditions This problem occurs during CTM server startup. The poll_main LWP (a Solaris thread) main function was commented out, but the thread creation function was not removed. When poll_main exits, a zombie thread is created. This causes a memory leak, because the thread stack space is not freed.
The CTM server does not malfunction due to this memory leak, because the problem occurs only once, upon startup.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsw68952
Symptom A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.
Conditions This problem occurs due to certain content in some tables. For example, literal IDs associated with circuits or NEs, or special characters in descriptions might cause the database export to fail.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, 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.
•CSCsw91994
Symptom The CTM database contains unusable indexes, which means that PM tables and audit logs
contain no data.
Conditions The problem is due to the table partitioning. When a partition is added or deleted, the index might become unusable. This is a known Oracle issue.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsx81985
Symptom Archive log pruning degrades as database usage increases, and the /db05 directory fills up.
Conditions This problem occurs when the database is under heavy load; for example, when you remove more than 200 NEs that are loaded with historical PM data.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, manually move the *.arc files from /db05/CTM to another file system (such as /ctm_backup).
•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.
•CSCsx47556
Symptom After backing up the CTM R8.5 database from the Control Panel or with the backupdb.sh
command, the log file backup_db.log is not generated. The backup_db.log file is not written to the
/oracle/admin/CTM/udump directory because there is a space character added when assigning the PATH
to the file.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, remove the space when assigning the PATH to the file.
•CSCsz63889
Symptom Occasionally, memory backups fail for CTC-based NEs with release 6.0.1.
Conditions This problem occurs when the NE security ticket is negative.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCta30985
Symptom A memory leak occurs on the CTM server because of zombie LWP creation when a user is in
locked state.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, disable user lockout in the Control Panel > Security Properties pane > CTM Security tab > Client Inactivity Timer Settings area.
•CSCta42487 (Related caveat ID: CSCtf17428)
Symptom The SM service disconnects during a JMOCO hello message, and the CTM server restarts.
Conditions This problem occurs infrequently during stress and soak testing on a T2 server in a high-end setup.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCta69019
Symptom The ctms-stop and ctms-abort scripts do not work when Oracle is down.
Conditions This problem occurs when Oracle is down. The ctms-stop and ctms-abort scripts contain an incorrect check. The scripts assume that Oracle is always up. Note that this problem rarely occurs, because the CTM server does not work correctly if Oracle is down.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
Alternatively, 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 Start Oracle.
Step 6 Enter the ctms-start command to restart CTM.
•CSCtb01411
Symptom The network services and network service instances cannot be stopped or started from the
Control Panel. The SMService-0-<timestamp>.log file shows the following error message:
EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too
many open files
Conditions Although the issue is not systematic, it might occur when the CTM server has been running for a long time.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, enter the commands ctms-stop and ctms-start to restart the CTM server. Note, however, that the problem can occur again after a long time.
•CSCtb34284
Symptom The core_pmon.sh script that checks the status of critical CTM processes runs every
30 seconds instead of every 5 minutes.
Conditions This problem occurs only on CTM R8.5.0.381.3 or later. Earlier patch versions are not affected.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. However, if a previous workaround was applied, edit the core-pmon.sh file and remove the row that contains "sleep 270." Installing the CTM R8.5.0.392.2 or later patch will not overwrite the file.
Alternatively, complete the following steps only for CTM R8.5.0.381.3 or later:
Step 1 Log into the CTM server as the root user.
Step 2 Enter the following command to change directories to the /opt/CiscoTransportManagerServer/bin/ directory:
# cd /opt/CiscoTransportManagerServer/bin
Step 3 Enter the following command to make a backup copy of the core_pmon.sh script:
# cp core_pmon.sh core_pmon.sh.original
Step 4 Enter the following command to edit the core_pmon.sh script:
Step 5 Add the following row at the beginning of the script:
Step 6 Save and close the file.
•CSCtb62164
Symptom After running the getinfo.sh script, the following error message appears:
Permission denied while running "rsh". Check the environment and make sure the root is
permitted to run "rsh" on host.
Conditions This problem occurs on a single server installation where rsh is not configured. The /.rhosts file is missing.
Workaround Create the .rhosts file.
•CSCtb81830
Symptom Multiple initial poll jobs are created for the same NE.
Conditions Due to an overload of the CTM server, the network service process cannot complete the initial poll for NEs within the polling interval (240 seconds by default). The network service schedules a new initial poll for the same NE every 240 seconds, without first checking whether the initial poll is already in the queue.
The network service log reports the following errors:
2010-08-12 10:47:53,369] [WARN Initial Poll DispatcherWorker#4 on CERENT167] EID-2089:
InitialPoll to NE is failed
2010-08-12 11:00:48,642] [WARN Initial Poll DispatcherWorker#7 on CERENT167] EID-2089:
InitialPoll to NE is failed
2010-08-12 11:13:40,081] [WARN Initial Poll DispatcherWorker#4 on CERENT167] EID-2089:
InitialPoll to NE is failed
2010-08-12 11:26:35,081] [WARN Initial Poll DispatcherWorker#3 on CERENT167] EID-2089:
InitialPoll to NE is failed
Workaround Restart the network service to clear all initial poll jobs from the queue.
•CSCtb83268
Symptom Some optical NEs (such as the ONS 15454) are shown with a red check mark in the Domain
Explorer tree. If these NEs are marked as Out of Service and then In Service, the red check mark persists,
and the NEs are not discovered. Restarting the NE service does not resolve the problem.
Conditions This problem occurs when the CTM database contains inconsistent data. The inconsistency might have been caused by an earlier CTM upgrade.
Workaround None.
•CSCtc49689
Symptom The Oracle Alert log displays deadlock error messages.
Conditions This problem occurs when a database trigger or an NE service access the ALARM_COUNT_TABLE at the same time. This problem rarely occurs and does not cause any system or performance issues.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtd01497
Symptom Automatic database pruning does not work.
Conditions This problem occurs in a dual-server CTM configuration.
Workaround Create an /oracle/admin/CTM/udump directory.
•CSCtd50613
Symptom When you import large database dump files, the /db05 file system fills up.
Conditions This problem occurs if ARCHIVELOG mode is enabled when you import a large database dump file. If the database contains a large amount of data, the import produces many archived redo logs, and the /db05 file system partition fills up.
Workaround Disable ARCHIVELOG mode before importing the database. Re-enable ARCHIVELOG mode after the import procedure completes.
•CSCth21611
Symptom Loss of communication alarm storms occur periodically on CTC-based network services.
Conditions This problem occurs when the CTM server manages more than 100 fully equipped NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternately, enable the Parallel Garbage Collection strategy by adding the -XX:+UseParallelOldGC property to the jnet.sh file; then, restart the CTC-based network services.
•CSCth97940
Symptom In a medium-sized configuration, CTM stops collecting historical PM data, audit log data, and
audit trail data if database pruning is not performed every three months.
Conditions If the database pruning period is longer than three months, the historical PM data, audit log data, and audit trail information can fill the Oracle database tablespaces, preventing the storage of new data.
Workaround Set the database pruning interval to 30 days and wait 1 day for the pruning process to complete.
Cisco Transport Controller Caveats
•CSCeb39352
Symptom A DRI circuit does not have DRI protection. Instead, it has only path/SNCP protection.
Conditions This problem can occur under any of the following conditions:
•There is no DRI segment in the network, but CTC still succeeds in creating a DRI circuit by creating only a path protection/SNCP circuit.
•The primary and secondary nodes of a DRI circuit are set up such that the path from source to primary destination might end up the same as the path by way of the secondary destination.
•The SNCP path is the shorter path, as compared to the DRI path.
Workaround Use manual routing.
•CSCsu66316
Symptom Cannot launch CTC from CTM for an ONS 15454 MSTP R8.5.2 node.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtc28944
Symptom From CTM, you cannot launch CTC on a CTC-based R8.5.1 NE.
Conditions This problem occurs when you install the CTM R8.5.0.387.6 service pack and then manually add any of the following NE releases to the Supported NE table:
•ONS 15310 CL R8.5.1
•ONS 15310 MA R8.5.1
•ONS 15454 SONET R8.5.1
•ONS 15454 SDH R8.5.1
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCte77971
Symptom From CTM, you cannot launch CTC or add new R8.5.1 or R8.6 NEs.
Conditions This problem occurs after you install the CTM R8.5.0.387.6 service pack.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
High Availability Caveats
Note The following caveat applies only to customers who have purchased the high availability (HA) option.
•CSCtc54674
Symptom In a high availability setup, users cannot execute sudo commands on the secondary CTM
server.
Conditions This problem occurs in an HA setup with local redundancy.
Workaround Copy the /etc/sudoers file from the primary server to the secondary server.
CTM GateWay/TL1 Caveats
•CSCin76320
Symptom For the ONS 15216 EDFA2 R2.4, the ED-NE-GEN command fails in the CTM GateWay/TL1
session.
Conditions In a CTM GateWay/TL1 session, the ED-NE-GEN command is denied with the message "GateWay not ready for Network Element." The command does not work because the CTM server is not informed of the change.
Workaround None.
•CSCsc97629
Symptom The CTM GateWay/TL1 response is missing the GNE ID or contains the incorrect GNE for
LNE in the NEDBCHG message.
Conditions See Symptom.
Workaround None.
•CSCsd13126
Symptom The CTM GateWay/TL1 session times out on ONS 15530 and ONS 15540 nodes if kept idle
for longer than 60 minutes.
Conditions This problem applies to TL1 sessions left idle for longer than 60 minutes on ONS 15530 or ONS 15540 NEs.
Workaround None.
•CSCsl21987
Symptom Random CTM GateWay/TL1 CPU usage is higher than normal. It shows approximately 10%
with peaks of up to 15%.
Conditions This problem occurs on a highend-configured CTM server and CTM GateWay/TL1 is started.
Workaround Start and stop the CTM GateWay/TL1 process.
•CSCsq65111
Symptom In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains
incorrect values.
Conditions When you open the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column incorrectly reports the values that are shown in the Event Reporting column.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, to see the correct values in the Alarm Reporting column, select a row in the table, open the Modify Event Forwarding Discriminator Profile dialog box, and verify whether the Alarm Reporting check box is checked. If it is checked, alarm reporting is enabled; if unchecked, alarm reporting is disabled.
CTM GateWay/CORBA Caveats
Note The following caveats apply only to customers who have purchased the CTM GateWay/CORBA option.
•CSCeb43036
Symptom Cannot set J1 path trace parameters immediately after circuit creation.
Conditions This problem occurs if you create a subnetwork connection (SNC) between any two NEs, and then immediately try to set J1 trace parameters by using the ManagedElementManager_I::setTPData method.
Workaround First, either set the IPPM parameter by using the ManagedElementManager_I::setTPData method, or set threshold parameters by using the PerformanceManagementManager_I::setTCATPParameter method. Then, set J1 trace parameters by using the ManagedElementManager_I::setTPData method.
•CSCed42655
Symptom CTM GateWay/CORBA is not installed when the server and the database are installed on
separate machines.
Conditions This problem occurs if the CTM database is installed alone on one machine, and the CTM server and CTM GateWay/CORBA are installed on a second machine.
Workaround Install CTM GateWay/CORBA on both the server and database machines. Select the Install GateWay/CORBA option for both the CTM server installation and the CTM database installation. On the CTM server machine, CTM GateWay/CORBA error messages might be displayed; you can ignore these.
•CSCin75602
Symptom CTM GateWay/CORBA returns the XC loopback values for CTPs even when the loopback is
present in the corresponding line.
Conditions This problem occurs when a loopback is active on a corresponding line.
Workaround Ignore the XC loopback value.
•CSCin94462
Symptom A CTM GateWay/CORBA user is able to perform operations even after being logged out from
the CTM client.
Conditions A CTM GateWay/CORBA user is not logged out immediately when a forced logout is performed from the CTM client. This problem occurs because the user session that is used to connect to the CORBA gateway service is cleared in CTM GateWay/CORBA. The OSS user will notice the loss of session during the next ping cycle to the EMS or when trying to perform an operation on a different manager object.
Workaround After a forced user logout, the OSS connection must wait until the next ping cycle to the emsSession or until another operation is performed on a different manager object.
•CSCsb58067
Symptom The methods getAllTopLevelTopologicalLinks and LinkNames fail through
CTM GateWay/CORBA.
Conditions See Symptom.
Workaround None.
•CSCse82549
Symptom The emsMgr::EMSMgr_I::createTopologicalLink API returns an exception with the message
"Failed to get containing equipment for a PTP."
Conditions This problem occurs when you use a CTM GateWay/CORBA interface.
Workaround Create the link in the CTM client GUI. The link is displayed correctly by APIs such as getTopologicalLink.
•CSCse86815
Symptom The getAllEquipment API returns the value "Unequipped" in the Equipment field when an
ONS 15302 R2.0 card is preprovisioned. Instead, the equipment name should be returned.
Conditions This problem applies to a preprovisioned card on an ONS 15305 R2.0 NE.
Workaround None.
•CSCse91332
Symptom CTM GateWay/CORBA does not send a notification event when a new network partition is
created in CTM.
Conditions This problem occurs when you create a new network partition in CTM using the CTM client or the emsMgr::EMSMgr_I::addNetworkPartition API.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCse91435
Symptom CTM GateWay/CORBA does not send a notification event when an existing network partition
is deleted from CTM.
Conditions This problem occurs when you delete a network partition from CTM using the CTM client or the emsMgr::EMSMgr_I::addNetworkPartition API.
Workaround None.
•CSCsj19520
Symptom The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service
or CTM server is restarted.
Conditions After you enable log file archiving, the logs of all services, including CTM GateWay/CORBA, are archived. If the CTM GateWay/CORBA service or the CTM server is restarted, log file archiving stops.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsl17291
Symptom Unable to create a manual link using CTM GateWay/CORBA.
Conditions This problem occurs when you use the createTopologicalLink API when creating a manual link that involves ONS 15302 and ONS 15305 R2.0 NEs. The API call fails and returns an exception.
Workaround Use the CTM client GUI to create the manual links.
•CSCsl18238
Symptom The CTM GateWay/CORBA service uses the default dynamic ports and you need to use the
static ports for security reasons.
Conditions This problem occurs when you use the CTM GateWay/CORBA service with static ports and/or firewall.
Workaround Change the default settings of the port. See Chapter 12 of the Cisco Transport Manager Release 8.5 User Guide.
•CSCsm64677
Symptom The restoreME API does not work correctly, so you cannot use CTM GateWay/CORBA to
restore the managed element (ME) configuration file.
Conditions This problem occurs when a CORBA gateway user tries to restore the ME configuration file on CTM R8.5.
Workaround Use the CTM client GUI to restore the ME configuration file.
•CSCsm85018
Symptom There are compatibility issues between CTM R8.5 and the CTM GateWay/CORBA R8.0 client
after changing the CTM R8.5 notifications.idl file located in the /opt/CiscoTransportManager/idl
directory.
Conditions This problem occurs when you use a CTM GateWay/CORBA client that is based on a release 8.0 interface description language (IDL).
Workaround Recompile the CTM GateWay/CORBA client with a release 8.5 IDL. Alternatively, install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Changes to the notification.idl file are reverted after applying the CTM R8.5 service pack to avoid the compatibility issue when migrating to CTM R8.5.
•CSCso76700
Symptom 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.
Conditions This problem occurs when CTM GateWay/CORBA is running and you execute the ctms-stop or ctms-start commands. Ten new proxy consumers are created in addition to the ten existing proxy consumers. Only ten proxy consumers are used.
Workaround Before stopping the CTM server, use the CTM client or the gwcorba-stop command to stop CTM GateWay/CORBA. This workaround deletes the existing proxy consumers before creating new ones. Alternatively, install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq26342
Symptom The getHistoryPMData API takes longer than 15 minutes to return data.
Conditions When you use the getHistoryPMData API to retrieve data for an ME, the request might take longer than 15 minutes, depending on the node configuration and the server activities.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq78385
Symptom The SMService_port property generates a random value even if it is set to a fixed value.
Conditions This problem occurs when you:
1. Set the value of the jacorb.use_imr property in the jacorb.properties file to the following:
2. Set the value of the SMService_port property in the gwcorba.properties file to the following:
SMService_port=<fixed_value>
3. Restart the CTM server.
Workaround None.
•CSCsr24435
Symptom Server trail creation fails though CTM GateWay/CORBA when a port name is set.
Conditions The CORBA API createServerTrailLink returns a processing failure exception with the error reason "No PTPs in the NE <NE_ID> for server trail creation." This problem occurs when the port name is set on at least one of the link PTP endpoints.
Workaround Use the CTM client GUI to create the server trail link.
•CSCsr94216
Symptom Some of the fields that are present in the CTM Alarm Browser are missing from the
CTM GateWay/CORBA output. For example, the Object and Module Name fields are missing from the
events retrieved by CTM GateWay/CORBA.
Conditions This problem affects events with an Affected Object value like "VC4-*-*-*-*-*" on ONS 15600 SDH NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu24300
Symptom For the getAllCurrentPMData API, CTM GateWay/CORBA does not retrieve real-time PM
data for FC, GFP, and ISC layer rates.
Conditions If you try to retrieve real-time PM data for FC, GFP, or ISC layer rates, CTM GateWay/CORBA returns the following message: "No data in the holder."
Workaround Use the CTM client GUI to retrieve real-time PM data for FC, GFP, and ISC layer rates.
•CSCsu68317
Symptom 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.
Conditions This problem occurs when low-order circuits are routed through tunnel circuits.
Workaround Install the latest CTM R8.5 patch See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsu82028
Symptom The APIs getTCATPPParams and setTCATPParams do not work for trunk ports on GE_XP
and 10GE_XP cards.
Conditions On GE_XP and 10GE_XP cards, the APIs getTCATPPParams and setTCATPParams fail for trunk ports for the following layer rates:
•LR_Physical_10_Gigabit_ITU
•LR_Optical_Transport_Path
•LR_Optical_Transport_Section
•LR_Optical_Transport_FEC
When this problem occurs, you cannot get or set TCATPParams for optical or OTN thresholds on trunk ports for the selected layer rate.
Workaround None.
•CSCsv47526
Symptom The setTPData and getTP APIs might fail and generate a null pointer exception for a CTP
whose native name involves an MRC-12 card.
Conditions A null pointer exception is generated when the selected CTP native name has an index j > 1 and an index k of any value; for example, /sts1_au3-j=3-k=1.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv52311
Symptom The getSNC and getAllSubnetworkConnections APIs return CTPs in the format
/sts1_au3-j=1-k=[1..192] instead of /sts1_au3-j=[1..64]-k=[1..3]. Also, the setTPData API might fail for
CTPs created on OC-192 XFP cards, which generates a null pointer exception.
Conditions This problem occurs when the CORBA APIs are called on circuits that include OC-192 XFP cards.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsw73743
Symptom The getAllCrossConnections API returns an error if the node does not contain circuits.
Conditions This problem occurs if the node does not contain circuits and CTM GateWay/CORBA logging is set to Debug mode.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, go to the Control Panel > GateWay/CORBA Service > Debug tab and disable debug logging for CTM GateWay/CORBA.
•CSCsx55667
Symptom The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an
exception with the message "no rows from db."
Conditions This problem occurs when the connection between the CTM system and a remote NE is lost momentarily. For example, DCN instability or a network delay might cause the connection to drop for a short time.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, mark the NE as Out of Service and then In Service.
•CSCtf08332
Symptom The CTM GateWay/CORBA GetRollsToPTPs API does not return a list of available PTPs.
Conditions This problem occurs when using the CTM GateWay/CORBA GetRollsToPTPs API, which requests available PTPs moving from one circuit to another.
Workaround None.
•CSCtf08344
Symptom The CTP EMS native name is incorrect for a low-order (LO) VC circuit alarm.
Conditions This problem occurs on every alarm raised for LO VC-3, VC-11, and VC-12 circuits.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtf25363
Symptom The CTP EMS native name is incorrect for an LO VT circuit alarm.
Conditions This problem occurs on every alarm raised for LO VT1, VT2, and VT 1.5 circuits.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCth64373
Symptom The CTP EMS native name is incorrect for LO VT circuits when getSNC and getAllSnc APIs
are used.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCth68019
Symptom For the getTPHistoryPMData API, CTM GateWay/CORBA does not retrieve historical and
real-time PM data on transmit (Tx) ports of the DS-n layer rate. CTM GateWay/CORBA retrieves PM
data only on receive (Rx) ports.
Conditions This problem occurs when CTM manages ONS 15310 CL R8.6.1 NEs.
Workaround None.
NE-Specific Caveats
This section includes the following information:
•Cisco MGX Voice Gateway
•Cisco ONS 15216 EDFA
•Cisco ONS 15302 and Cisco ONS 15305
•Cisco ONS 15310
•Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET
•Cisco ONS 15454 MSTP
•Cisco ONS 15600 SONET and Cisco ONS 15600 SDH
•Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808
Cisco MGX Voice Gateway
•CSCsb69274
Symptom The Statistics Report application provides three types of reports for VISM connections: Raw
Data Report, Utilization Data Report, and Performance Data Report. When you request the Utilization
Data Report for VISM connections, you receive the error message "No report found."
Conditions See Symptom.
Workaround None.
•CSCsb69421
Symptom The PXM45 and PXM1E node-level, port-related statistics files go into the
/opt/svplus/purge/Badfilelist. The node-level data is not inserted into the pnni_port_data table and
consequently cannot be reported.
Conditions This problem occurs when the node-level statistics for the PXM45 and PXM1E node ports are enabled through the CLI command cnfpnstat -allintfstats enable, and when PM data collection is enabled for these NEs. This problem is due to a missing subobject_type column in the pnni_port_data table.
Workaround Complete the following steps to add the subobject_type column to the pnni_port_data table:
Step 1 Create an add_column.sql file.
Step 2 Edit the add_column.sql with the following content:
DROP TABLE pnni_port_data;
CREATE TABLE pnni_port_data (
subobject_type NUMBER(5),
) TABLESPACE MGX8880_DATA_TABLESPACE ;
Step 3 Enter the following command:
cat <add_column.sql_file_path> | /oraclesw9i/product/9.2/bin/sqlplus -S
ctmanager@CTM/ctm123!
•CSCse39608
Symptom The CTM Alarm Log continues to report card, line, path, and port modify alarms every eight
hours.
Conditions The problem occurs in normal conditions.
Workaround Complete the following configuration before starting CTM or the MGX VG NE service:
Step 1 Enter the following command:
Step 2 Open the NMServer.conf file using a text editor.
Step 3 Search for "PERIODIC_RESYNC_INTERVAL."
Step 4 Change the value from 8 to 0. It should show PERIODIC_RESYNC_INTERVAL 0.
Step 5 Start CTM or the MGX VG NE service.
•CSCse96373
Symptom CTM is not synchronized with the MGX NEs or the SNMPs that CTM requests from the MGX
NEs are not successful. Also, the Alarm Browser reports frequently a Process Restarted alarm.
Conditions This problem occurs when MGX NEs that are supported in CTM R8.5 are installed on a Solaris 10 machine.
Workaround By default, Solaris 10 machines run the Internet information server of port 9010, which is required in one of the CTM processes. To stop the process in a session, enter the following commands on the Solaris server with SuperUser privileges:
ps -aef | grep "htt+server"
At this time, the MGX NE service can be stopped and then started for all CTM processes managing the MGX NEs. Enter the following commands on the Solaris server with SuperUser privileges to stop the Internet/Intranet Input Method (IIIM) server from restarting after the system reboots:
find ./ -type f | xargs grep "htt"
The entries in the resulting rc*.d files need to be removed or the files need to moved to a different location if they are meant for the IIIM process.
These steps should be performed by users with System Administrator privileges.
•CSCsg19780
Symptom The wrong icon is displayed in the Domain Explorer tree when an MGX NE is added to
CTM R8.5 as a preprovisioned NE. It shows an MGX-specific icon instead of the common icon used for
all platforms. After the MGX NE goes into In Service state, the MGX-specific icon should be used.
Conditions This affects only the icon display and does not impact any CTM operation.
Workaround Add the MGX NE as In Service NE.
•CSCsg27309
Symptom MGX nodes encounter errors or do not synchronize after configuration.
Conditions This problem occurs when you enter the command ps -aef | grep "htt". The following message is returned: "/usr/lib/im/htt -port 9010 -syslog -message_locale C >/dev/null 2 >&1 &."
Workaround Verify that the following ports are available:
•9000
•9003
•9004
•9006
•9007
•9008
•9010
•Udp 2500
If you need to use the IIIM server, the base ports of the MGX process must be remapped in the /opt/svplus/config/process.conf file to a port other than 9000. You must do this before starting CTM with MGX support on Solaris 10 machines.
•CSCsg97551
Symptom Cannot retrieve MGX NE information from the audit trail.
Conditions This problem occurs when using CTM GateWay/CORBA with Orbix R6.0. This problem is resolved in Orbix R6.3.
Workaround Close CTM, restart Orbix, and restart CTM.
•CSCsh26407
Symptom When an MGX NE is added to CTM, one of the following scenarios occurs:
•Scenario 1
–The MGX NE is in SNMPv3 mode and is added to CTM in SNMPv3 mode.
–The SNMPv3 mode of the MGX NE is changed to SNMPv1 mode after sync-up.
•Scenario 2
–The MGX NE is in SNMPv1 mode and is added to CTM in SNMPv1 mode.
–The SNMPv1 mode of the MGX NE is changed to SNMPv3 mode after sync-up.
Synchronization is complete when one of the following occurs:
•Automatic resynchronization occurs.
•Resynchronization is performed in the Diagnostic Center.
•The MGX NE is marked as Out of Service and then In Service.
Conditions This problem occurs when:
•The MGX NE in SNMPv1 mode is changed to SNMPv3 mode.
•The MGX NE in SNMPv3 mode is changed to SNMPv1 mode.
Workaround Perform one of the following:
•Mark the NE as Out of Service and then In Service.
•Perform an L2 resynchronization in the Diagnostic Center.
•CSCsh46506
Symptom 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.
Conditions This problem occurs when you start or restart CTM.
Workaround The default debug levels in the MGX management module of CTM have been reduced. Complete the following steps to clear the logs:
Step 1 Stop the CTM or MGX VG NE service.
Step 2 Enter the following command:
Step 3 Enter the following command to remove the log files:
Step 4 Restart the CTM or MGX VG NE service.
•CSCsh91128
Symptom No error message is shown if more than 20 MGX nodes are added to a medium-sized CTM
server.
Conditions See Symptom.
Workaround Install a large or high-end CTM server when you need to manage more than 20 MGX nodes.
•CSCsi04811
Symptom The Event Handle Type field allows configuration with invalid handle type values for event
mapping configuration.
Conditions This problem occurs after selecting an event index for mapping configuration.
Workaround To avoid errors from the NE agent, use only correct values for event handle types.
•CSCsk00034
Symptom 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.
Conditions This problem occurs if one end of a connection has no statistics support. This bug does not have any impact on configuration.
Workaround Use the CLI to perform polling operations.
•CSCsk31966 (Related caveat ID: CSCso92358)
Symptom Disabled tabs are enabled when performing operations in the navigation tree.
Conditions This problem occurs when tabs are disabled because of certain attribute values and you select a node from the navigation tree while main operations are running. The problem does not apply to main or alternate operations supported by the Configuration Center. For example, you have a DnD VXSM card in TGCP-cable mode in the Configuration Center. Disable the TGCP bearer security from the Media Gateway tab. When you click the Media Security drop-down menu from the workflow area, the Media Gateway tab gets enabled in the configuration frame, which allows you to modify parameters. All the disabled tabs in the Configuration Center have the same problem on the card, line, path, and port levels.
Workaround To switch between tabs, click the tabs directly instead of selecting the workflow or navigation tree nodes.
•CSCsl43107
Symptom 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.
Conditions This problem occurs when the CTM client is connected to a CTM server that has MGX NEs. This problem is observed in both Windows and Solaris platforms.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCso44701
Symptom CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job
Monitor table displays the following message:
(No such file or directory)
Conditions This problem occurs when multiple memory backups are scheduled simultaneously on MGX NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsq31631
Symptom Memory backup and memory restore fail on MGX nodes when Telnet is disabled.
Conditions This problem occurs because SSH support is not available in the scripts, and Telnet is disabled on the MGX switch.
Workaround Complete any of the following workarounds:
•Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•Enable Telnet access on the switch.
•Use CLI commands to save the configuration.
•CSCsq92344
Symptom 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.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsr30785
Symptom The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
Conditions This problem occurs when the MGX STM-1 VXSM interfaces use AU4 KLM format.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsv12810
Symptom An MGX node is added to the CTM server, but is not included in the Auto Backup process.
Conditions This problem occurs under normal conditions.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, stop and restart automatic backup on the server. The new MGX is listed in the Auto Backup process list.
•CSCsx93323
Symptom CTM displays a "Media Gateway Link state, pendingIs" alarm with a "Warning" severity. In
other Element Managers, this type of alarm is set with a "Major" severity.
Conditions This problem occurs when an H248 link is down between a Media Gateway and Media Gateway Controller and a 70635 trap is sent to CTM.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsy29600
Symptom CTM does not receive PM data from managed MGX devices.
Conditions This problem occurs when PM data is enabled and stored for 30 days.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCsy93198
Symptom On the CTM client, the following MGX windows take approximately 15 minutes to load:
•MGX Chassis View
•Configuration Center
•Diagnostics Center
•Performance screens
Conditions This problem occurs when the MGX module is installed, and one of the following CTM R8.5 patches is installed or was installed on the server:
•008.005(000.368.001)
•008.005(000.375.001)
•008.005(000.378.001)
•008.005(000.381.003)
•008.005(000.384.003)
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
Alternatively, complete the following steps:
Step 1 Enter the following commands to verify whether your CWMclient/ directory is configured correctly:
cd /opt/CiscoTransportManagerServer/webServer/htdocs/CWMclient
If the configuration is correct, the output displays:
lrwxrwxrwx 1 root root <date> cwm_orbix_domain.cfg
-> /opt/svplus/orbix_domain/domains/cwm_<hostname>_domain.cfg
If the configuration is incorrect, the output contains a file instead of a symbolic link. To fix the configuration, enter the following commands:
cd /opt/CiscoTransportManagerServer/webServer/htdocs/CWMclient
cp cwm_orbix_domain.cfg cwm_orbix_domain.cfg_orig
ln -s /opt/svplus/orbix_domain/domains/cwm_<hostname>_domain.cfg cwm_orbix_domain.cfg
where <hostname> is the hostname of your server.
Step 2 Close and reopen the CTM client; then, relaunch the MGX windows.
•CSCta31966
Symptom Memory usage for the ooemc process increases over a period of time.
Conditions This problem occurs when a VXSM card is on the network and multiple resynchronizations occur due to permanent trap loss.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternately, resolve permanent trap loss or event issues to prevent multiple resynchronizations and delay the impact of increased memory usage. Resynchronizations are scheduled once a week by default, but are also triggered by particular events and permanent trap loss.
•CSCtb55280
Symptom If you remove a multimode fiber from a gigabit Ethernet interface on an RPM card, the PXM
reports a critical alarm. However, due to an Oracle exception, CTM does not raise an alarm.
Conditions This problem occurs on CTM R8.5 and Oracle 10 when:
•RPM is running 12.4(15)T9
•VXSM is running 5.4(20.201)
•PXM is running 5.4(30.200)
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtc12055
Symptom Cannot use automatic or manual backup to prune MGX data.
Conditions This problem occurs when CTM manages MGX NEs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCtc49087
Symptom CTM displays the MGX 88xx chassis serial number as N/A in the Equipment Inventory table.
Conditions See Symptom.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
•CSCte65495
Symptom Memory usage for the ooemc process increases when cache Roguewave lists are cleared.
Conditions This problem occurs when a resynchronization occurs.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack.
Cisco ONS 15216 EDFA
•CSCsg11604
Symptom CTM does not detect the temporary failure if a LAN connection to an NE is lost temporarily
and then restored within a short time.
Conditions CTM does not detect a lost connection if the network connection to an NE is lost and regained in between two CTM health polls, with default values of four minutes. This applies to ONS 15216 EDFA2 and ONS 15216 EDFA3 NEs.
Workaround Reduce the health poll interval in the Control Panel to increase the probability of detecting the lost connection. However, this is not recommended because reducing the health poll interval can adversely affect system performance.
•CSCsg79599
Symptom Cannot create an ONS 15216 EDFA2 SNMP community view using a wildcard mask.
Conditions This problem occurs when you add an ONS 15216 EDFA2 R2.4 NE.
Workaround None.
•CSCsh07187
Symptom There are no available PTPs on the ONS 15216 EDFA NEs when creating manual links to ONS
158xx NEs.
Conditions When you choose to create a link between ONS 15216 EDFA and ONS 158xx NEs using the Configuration menu, there are no PTPs available in the Create Link wizard for ONS 15216 EDFA NEs.
Workaround None.
•CSCsi32169
Symptom The NE Explorer does not refresh and shows blank fields when you perform a Refresh from
NE operation.
Conditions This problem occurs when you perform a Refresh from NE operation from the NE Explorer after the ONS 15216 EDFA3 NE has been up and running for a long time, and there are no actions performed on the NE.
Workaround Mark the NE as Out of Service and then In Service.
•CSCsi39881
Symptom The default CTM and GateWay/TL1 users of ONS 15216 EDFA3 NEs are the same.
Conditions Connection problems to ONS 15216 EDFA3 NEs can occur if CTM and the GateWay/TL1 are used and configured with the same user. ONS 15216 EDFA3 NEs can accept only one connection per user. Therefore, the NEs must be configured with as many GateWay/TL1 users as the projected number of connections. Every instance of the CTM server can connect to the same NE with up to two clients: ONS 15216 NE Explorer and GateWay/TL1.
Currently, the default users in the CTM Security tab of the Control Panel for ONS 15216 EDFA3 NEs have the CISCO15 user. Two different users or empty users should be configured.
Workaround Manually configure two different users for the ONS 15216 EDFA3 NE in the Security tab of the Control Panel or in the Network Element Properties pane of the Domain Explorer.
•CSCsl06434
Symptom The communication state of the ONS 15216 EDFA3 NEs is Initialization Failed after rebooting
the CTM server operating system.
Conditions This problem applies to ONS 15216 EDFA3 NEs on a dual CTM server installation and occurs after the CTM server operating system reboots.
Workaround Wait until the NE polling completes or mark the NE as Out of Service and then In Service.
•CSCuk53021
Symptom Users who are logged into an ONS 15216 EDFA3 NE cannot be logged out from CTM.
Conditions The Log Out User feature in the NE Active User List table is not available for ONS 15216 EDFA3 NEs.
Workaround Use the TL1 command DLT-USER-SECU::userid:123; to delete the user.
•CSCuk53024
Symptom The NE Active User List table for the ONS 15216 EDFA3 does not update when users log into
or out of an NE.
Conditions This problem occurs when you select an EDFA3 NE in the Domain Explorer and choose Administration > ONS 15216 > NE User Access Administration. In the NE User Access Administration table, choose Edit > NE Active Users. The table shows a list of users who are logged into the NE when the NE was marked as In Service in CTM. New updates are not reflected.
Workaround Click the Refresh Data tool in the NE Active User List table.
Cisco ONS 15302 and Cisco ONS 15305
•CSCeh40971 (Related caveat ID: CSCuk59381)
Symptom The remote console echoes the password back to the user.
Conditions This problem occurs when you start a remote console on the ONS 1530x from a CTM client running on Solaris. As you type the password, the Telnet session echoes back the password in plain text instead of asterisks (******).
Workaround Before typing the password, change the Telnet client mode from Line to Character. Enter Ctrl + ] and then type mode character and press Enter. You are now in Character mode.
•CSCsd28777
Symptom When the timing standard is changed from SONET to SDH, the update appears only after a 1-
to 2-minute delay.
Conditions See Symptom.
Workaround Wait until the tab updates correctly.
•CSCsd57233
Symptom When circuits are deleted, the DCC terminations of the ports involved in the circuit and ports
related to endpoints are deleted from the CTM database. DCC terminations are not shown in the NE
Explorer > DCC tab.
Conditions This problem applies to DCC terminations and ports related to endpoints on STM cards on ONS 15305 NEs when circuits are deleted.
Workaround Synchronize the NE.
•CSCsd59855
Symptom The alarm severity of discovered SDH links remains critical even if alarms are cleared.
Conditions This problem applies to a DCC link between two ONS 15305 NEs or between an ONS 15305 and an ONS 15454 NE.
Workaround Mark one or both nodes as Out of Service, remove the invalid link, and mark the node(s) back In Service.
•CSCsd90033
Symptom Cannot delete DCC terminations on STM-1 ports when a 1+1 MSP protection group has been
created.
Conditions This problem applies to STM-1 ports on ONS 15305 R3.0 NEs with 1+1 MSP protection groups.
Workaround None.
•CSCse02069
Symptom ONS 15305 NEs (NE releases 2.0.0, 2.0.1, 2.0.2) lose connectivity with CTM. After all nodes
recover connectivity with CTM, one ONS 15305 displays the message "Error: Value NA" or "Error: Not
Connected" instead of the node name (TID) in the NE Explorer tree. The correct node name is displayed
in the Network Map.
Conditions This problem occurs if there are connectivity problems in the network when NE discovery begins.
Workaround Mark the ONS 15305 NE as Out of Service. Then, mark it as In Service.
•CSCse80101
Symptom The ONS 15305 R3.0 NE Explorer > Alarm tab lists two profiles: Default and Node. No matter
which profile you select, the Profile column is always set to Node.
Conditions This problem applies to all cards, backplane, and noncard objects on ONS 15305 R3.0 NEs.
Workaround None.
•CSCsg79603
Symptom When you perform a Force or Lockout switch on a 1+1 protection group between ports 1 and
2 of the STM-1S1.1-1-LC/E1-21 card, the switch automatically clears within two minutes.
Conditions This applies to 1+1 protection groups between ports 1 and 2 of STM-1S1.1-1-LC/E1-21 cards.
Workaround None.
•CSCsg90604
Symptom A caret (^) is added to the circuit name when the circuit is created between ONS 15305 and
ONS 15454 NEs.
Conditions This problem occurs when the circuit is created between ONS 15305 and ONS 15454 NEs.
Workaround None.
•CSCsh15353
Symptom The VLAN tab in the NE Explorer of the E100-WAN-8 card is not refreshed when you perform
a Tagged or Untagged operation.
Conditions This applies to the E100-WAN-8 card of the ONS 15305 NE.
Workaround Refresh from the NE to update the status of the VLAN tab.
•CSCsh48269
Symptom The following issues were observed:
•Some alarms show the wrong NE alarm time stamp and NE clear alarm time stamp. Both time stamps are different from those shown in CTC.
•The CTM server is notified of some alarms twice.
Conditions This problem occurs when a circuit is created and then fiber cuts are performed to generate loss of signal, loss of frames, and RDI alarms.
Workaround None.
•CSCsh51435
Symptom The NE service restarts while creating low-order circuits that involve ONS 15305 NEs. All
ONS 15305, ONS 15454 SDH, and ONS 15600 SDH NEs that are managed by the same NE service go
into Disconnected state because the NE service restarted.
Conditions This problem occurs when creating single or multiple VC LO path circuits using ONS 15305 STM cards.
Workaround There is no workaround because the NE service restarted. To avoid this problem, do not create multiple circuits.
•CSCsh53422
Symptom Low-order circuits between ONS 15305 and ONS 15454 SDH NEs remain in Partial state in
CTC when the circuit is deleted in CTM. After a rediscovery process, the circuits are also in Partial state
in CTM.
Conditions This applies to LOP or LOP-V circuits that are created from CTC and then deleted from CTC or vice versa.
Workaround Perform an NE discovery before completely deleting from CTM the circuit that is in Partial state.
•CSCsh62476
Symptom The old Cisco logo is shown in the Cisco Edge Craft splash screen, About Cisco Edge Craft
dialog box, and program icon in the Cisco Edge Craft main window.
Conditions You can view the Cisco Edge Craft for ONS 15302 and ONS 15305 R2.x NEs.
Workaround None.
•CSCsu86435
Symptom Occasionally, Cisco Edge Craft does not launch from CTM.
Conditions This problem occurs when you open up to 40 Cisco Edge Craft sessions from 10 CTM clients simultaneously.
The code that CTM uses to communicate with ONS 15305 devices means that only the first 10 CTM clients opened can launch Cisco Edge Craft sessions. No subsequent CTM clients can launch Cisco Edge Craft, unless one of the original 10 CTM clients is closed and a new CTM client is opened.
For example, assume that each of the following CTM clients is opened in chronological order:
•Client 1
•Client 2
•Client 3
•Client 4
•Client 5
•Client 6
•Client 7
•Client 8
•Client 9
•Client 10
CTM client 11 cannot launch a Cisco Edge Craft session, even if there are no Cisco Edge Craft sessions open on CTM clients 1 to 10.
If you close CTM client 5, CTM client 11 still cannot open a Cisco Edge Craft session.
However, if you open a new CTM client 12, you can launch a Cisco Edge Craft session for CTM client 12, because it uses the ports that were freed up from CTM client 5.
Also, CTM clients 1 to 10 can launch Cisco Edge Craft sessions at any time.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, close some of the original 10 CTM clients if they are not using Cisco Edge Craft; then, open a new CTM client and launch a Cisco Edge Craft session.
•CSCta27875
Symptom The ONS 15305 NE Service hangs, and if you try to mark NEs as In Service or Out of Service,
CTM returns the following error message:
EID-542: Database error: Cannot modify the NE state.
Conditions This problem occurs when the ONS 15305 NE Service manages more than 100 NEs and reaches the maximum Java heap size.
Workaround Contact TAC to expand the Java heap size; then, restart the ONS 15305 NE Service.
Cisco ONS 15310
•CSCsi01139
Symptom There is missing SONET PM data for a 15-minute robust PM data collection interval on
ONS 15310 CL NEs.
Conditions This problem occurs when you:
1. Enable 15-minute and 1-day robust PM data collection for ONS 15310 CL NEs.
2. Mark the ONS 15310 CL NEs as Out of Service and then In Service.
3. Wait until the next 15-minute PM data collection interval occurs. When you collect PM data for a SONET section with line and physical categories, several robust PM buckets are missing.
Workaround None.
•CSCsk71210
Symptom When you change the NE default values on ONS 15310 CL R6.0.3 NEs, the following error
message appears: "Error in setting the values. Please choose a valid value from the range displayed."
Conditions This problem occurs on version 06.03-007D-06.04 of ONS 15310 CL NEs.
Workaround Do one of the following:
•Modify the NE default values using CTC.
•Save the NE default values in a file using the Save to file option in the NE Defaults Management wizard. Modify the file using an editor and load the modified NE default values using CTC.
•CSCtd60987
Symptom RFI-V alarms on ONS 15310 R8.6 NEs remain stuck in CTM.
Conditions This problem applies to RFI-V alarms on ONS 15310 R8.6 NEs.
Workaround To refresh the alarms, mark the NE as Out of Service and then In Service.
Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET
•CSCea92062
Symptom When you attempt to switch timing to BITS1, BITS2 from internal while BITS1 and BITS2
sources are not connected, the switch appears not to have taken place, but in fact does take place.
Conditions Switching does occur successfully from CTM and on the NE, but the NE reverts back to internal immediately, as there was no BITS1 or BITS2 source present to switch to. The NE relays this update to CTM, and CTM updates to internal. The NE should not switch, but should instead send an exception back to CTM.
Workaround None.
•CSCsc66346
Symptom The IPPM set operation fails on STM-1E cards in the NE Explorer > VC4 tab for NE releases
earlier than 7.0.
Conditions This problem occurs when creating VC4 circuits on STM-1E cards. This problem applies to NE releases earlier than 7.0.
Workaround None.
•CSCsc99611
Symptom On a release 4.1.4 NE, the Local Orderwire and Express Orderwire tabs are missing.
Conditions See Symptom.
Workaround Launch CTC.
•CSCsd11274
Symptom A J1 path trace mismatch occurs on hex values for the expected string.
Conditions See Symptom.
Workaround None.
•CSCse13063 (Related caveat ID: CSCsg19595)
Symptom It takes more than 12 hours to synchronize NEs.
Conditions This problem occurs on a high-end network that contains a high circuit span count.
Workaround None.
•CSCsf13620
Symptom The position of the nodes in CTC is not maintained when CTC is launched from CTM.
Conditions This problem applies to all CTC-based NEs. Launch CTC on a node from CTM. Change the node positions on the network view using CTC. Close CTC and relaunch it. The node positions that were changed earlier are not maintained.
Workaround Launch CTC using a web browser to view all saved changes to node positions.
•CSCsf14512
Symptom The Use Generic MIB option is missing from the SNMP tab in the NE Explorer of CTC-based
R6.2.2 NEs.
Conditions This applies to all CTC-based R6.2.2 NEs.
Workaround None.
•CSCsg27470
Symptom Memory restore operation on a TNE fails. An error message is displayed.
Conditions This problem occurs when you perform a memory restore operation on a TNE, view the Job Monitor table, and check the status of the operation. The operation fails and shows an error message about byte mismatch.
Workaround None.
•CSCsg30824
Symptom 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.
Conditions This problem occurs under the following conditions:
1. Create a PPM on an MRC-25G-4 or MRC-25G-12 card.
2. Create a pluggable port on the PPM. The pluggable port should have an OC48 port rate.
3. Create a server trail that contains two MRC-25G-4 or MRC-25G-12 cards and an STS-6c port rate.
4. Change the port rate on the pluggable port from OC48 to OC3. The port rate is successfully changed.
If you try to delete the PPM, you receive an error saying that a server trail exists.
Workaround None.
•CSCsg73328
Symptom NEs do not come up in CTM after exchanging the MAC address between managed NEs.
Conditions The NE does not come up if you assign it a MAC address that belongs to another NE that is managed by CTM. A MAC address that is not used by other NEs can be assigned to any NE.
Workaround Delete the NE from the network and from the CTM server before assigning its MAC address to another NE.
•CSCsg78092
Symptom Cannot change the New Expected String field in the Section Trace tab of MRC-12 cards.
Conditions This applies to the Section Trace tab of MRC-12 cards in the NE Explorer. When you change the New Expected String field from an ASCII to hexadecimal form, changes are not applied to CTM and CTC.
Workaround None.
•CSCsg78171
Symptom Cannot change the New Expected String field in the Section Trace tab of the NE Explorer.
Conditions This problem occurs when the new string contains invalid characters. The string is updated in CTC when it contains valid characters.
Workaround None. This problem is seen only when using invalid characters.
•CSCsg83146
Symptom Cannot edit and save NE default values for the ONS 15327 and ONS 15454 NEs.
Conditions See Symptom.
Workaround None.
•CSCsg86081
Symptom Unable to retrieve a J1 path trace on ONS 15600 SDH ASAP cards.
Conditions This problem occurs after creating a VC4 circuit between an ONS 15600 ASAP card and ONS 15454 CE1000-4 card and transmitting a CE1000-T string. The ASAP I/O card, where the circuit terminates, does not receive a string.
Workaround None.
•CSCsh20563
Symptom The Standby Software column in the NE Software table is not updated after performing a
software download operation on a TNE or ENE.
Conditions Perform a software download operation on a TNE or an ENE that is connected to the TNE. Open the NE Software table. There are no values listed in the Standby Software column.
Workaround None.
•CSCsh24558
Symptom NEs do not come up after setting an NE username and password in the Control Panel and then
adding a new NE to CTM.
Conditions This problem occurs when a new server is installed. Specify the username and password for CTC-based NEs in the Control Panel and then add an NE. The initialization process fails and displays an error message stating that the username and password are wrong.
Workaround Specify the username and password in the Network Element Properties sheet for the Domain Explorer.
•CSCsh67863 (Related caveat ID: CSCsj29019)
Symptom NEs do not change to In Service state.
Conditions This problem occurs on a DCC ring that contains one GNE and a set of ENEs, and you use the NE Explorer or CTC to change the IP address of the ENE.
This problem can also occur when an out-of-service NE has its IP address changed. When the NE is subsequently marked as In Service, the embedded CTC instance that runs in the network service maintains a reference to the old IP address instead of the new address. CTM then tries to establish a connection to the old IP address instead of the new one.
Workaround Install the latest CTM R8.5 patch. See Installing the CTM R8.5.0.430.3 Service Pack. Alternatively, if the problematic NE is an ENE, delete it from CTM and then restart the NE service. If the problematic NE is not an ENE, keep it as In Service in CTM before changing its IP address. When the node reboots after the IP address change, an LOC alarm is generated and then cleared when the node comes up. If the IP address was changed while the NE was marked as Out of Service, and if the node does not change to In Service, restart the network service that manages the node.
•CSCsh85790
Symptom Cannot collect audit trail data for ONS 15454 SONET R4.7 NEs. If you choose
Administration > CTC-based NEs > Audit Trail Table, the table is blank.
Conditions When audit trail collection is enabled for ONS 15454 SONET R4.7 NEs, the Audit Trail table remains blank. Even if you change the filter to "No time specified" or any other value, no records are retrieved.
Workaround None.
•CSCsh91068
Symptom Changes to the NE Defaults of ONS 15454 SDH R7.x.x NEs are not applied.
Conditions This problem occurs when you change any attributes in the NE Defaults tab of the ONS 15454 SDH NE Explorer.
Workaround None.
•CSCsh96438
Symptom Port information on TCA events that are generated on DS3 cards is inconsistent between CTM
and CTC.
Conditions The physical location information in the Alarm Log for TCA events generated on DS3 cards is wrong. This problem occurs because the port information in CTC is different from the port information in CTM.
Workaround None.
•CSCsj47309
Symptom Cannot set the Send AIS-V for DS-1 AIS field on XTC cards.
Conditions View the slot properties of the XTC card in the NE Explorer. You cannot set the Send AIS-V for DS-1 AIS field in the DS-1 tab, Line Config subtab.
Workaround Use CTC to set the Send AIS-V for DS-1 AIS field.
•CSCsk19478
Symptom The GetEquipment API does not return newly added equipment.
Conditions This problem occurs when you execute the GetEquipment operation after a set operation. This is a timing problem. The set operation is not completely synchronous and finishes before all previously requested operations are complete.
Workaround Perform the GetEquipment operation again after some time has passed.
•CSCsk24889
Symptom Alarms on the DS1 or DS3 port are suppressed.
Conditions This problem occurs if there are alarms on the DS1-n and DS3-n XTC ports of ONS 15327 NEs and the alarms are suppressed.
Workaround Mark the NE as Out of Service and then In Service. This resynchronizes the alarms.
•CSCsk74602
Symptom When you change the NE default values on ONS 15327 R6.0.3 NEs, the following error
message appears: "Error in setting the values. Please choose a valid value from the range displayed."
Conditions This problem occurs on version 06.03-007D-06.04 of ONS 15327 NEs.
Workaround Do one of the following:
•Modify the NE default values using CTC.
•Save the NE default values in a file using the Save to file option in the NE Defaults Management wizard. Modify the file using an editor and load the modified NE default values using CTC.
•CSCsk90677
Symptom Unable to clear the Alarm Suppressed for Maintenance alarm for the OPT_BST card, after the
card is deleted.
Conditions When you mark the port of a preprovisioned OPT_BST card as Maintenance, the Alarm Suppressed for Maintenance alarm is generated and displayed in the Alarm Browser. When you delete the OPT_BST card, the alarm is not cleared.
Workaround Mark the NE as Out of Service and then In Service. The alarms are properly synchronized.
•CSCsu96767
Symptom The Circuit table does not display the port name for DS1_E1_56 cards of ONS 15454 ANSI
NEs.
Conditions This problem occurs on VT circuits created between DS1 named ports of DS1_E1_56 cards.
Workaround None.
Cisco ONS 15454 MSTP
•CSCef51502
Symptom A change to the OPT-BST card's ALS OSRI value is not reflected in CTM.
Conditions If you open the NE Explorer card slot properties pane for the OPT-BST card, click the Automatic Laser Shutdown tab, and change the OSRI value from Off to On or vice versa, the new value is saved on the NE, but CTM does not update. This problem applies only to NE releases 4.6.2 and earlier.
Workaround In the NE Explorer window, click the Refresh Data tool. At the prompt "How would you like to synchronize this NE's configuration?," choose From Network Element. Click OK; then, click Yes. The database is refreshed with the current configuration on the NE and the NE Explorer is updated accordingly.
•CSCsg69277
Symptom The OSC links do not behave correctly in CTM after a fiber cut. Unidirectional links from the
optical channel ROADM card to the line amplifier become invalid, while the unidirectional link from
the line amplifier to the optical channel ROADM card remains valid. An alarm is displayed in the
Network Map.
Conditions This problem occurs when a fiber cut occurs between two nodes on an MSTP ring. Open the Network Map and check the link status.
Workaround None.
•CSCsh54851 (Related caveat ID: CSCsq70978)
Symptom Provisioning operations such as card and PPM provisioning on a heavy-loaded multishelf NE
take too much time to complete.
Conditions This problem occurs when you provision a heavy-loaded multishelf ONS 15454 NE.
Workaround None.
•CSCsh71348
Symptom CTM cannot automatically route an OCHCC circuit.
Conditions The source or destination nodes are connected by either OTS or virtual links. There are two different paths with a different number of hops to terminate the circuit but only one path is available to the circuit because the other path, which is shorter in terms of the number of hops, does not provide optical connectivity to the destination node. The interconnecting node is connected to the destination node with a provisioned patchcord link between the trunk port and the optical channels.
Workaround Complete the following:
•
Feedback
