Table Of Contents
Release Notes Cisco Transport Manager Release 6.0
New Features and Functionality
CTM-Supported NE Software Releases
Adding the ONS 15310 CL R5.0.6 to the Supported NE Table
Adding the ONS 15310 CL R5.0.7 to the Supported NE Table
Adding the ONS 15310 CL R6.0.1 to the Supported NE Table
Adding the ONS 15310 CL R6.0.3 to the Supported NE Table
Adding the ONS 15327 R4.181 to the Supported NE Table
Adding the ONS 15327 R5.0.6 to the Supported NE Table
Adding the ONS 15327 R5.0.7 to the Supported NE Table
Adding the ONS 15327 R6.0.1 to the Supported NE Table
Adding the ONS 15327 R6.0.3 to the Supported NE Table
Adding the ONS 15454 SDH R5.0.6 to the Supported NE Table
Adding the ONS 15454 SDH R6.0.1 to the Supported NE Table
Adding the ONS 15454 SDH R6.0.3 to the Supported NE Table
Adding the ONS 15454 SONET R4.181 to the Supported NE Table
Adding the ONS 15454 SONET R5.0.6 to the Supported NE Table
Adding the ONS 15454 SONET R5.0.7 to the Supported NE Table
Adding the ONS 15454 SONET R6.0.1 to the Supported NE Table
Adding the ONS 15454 SONET R6.0.2 to the Supported NE Table
Adding the ONS 15454 SONET R6.0.3 to the Supported NE Table
Adding the ONS 15600 SONET R5.0.6 to the Supported NE Table
Adding the ONS 15600 SONET R5.0.7 to the Supported NE Table
Adding the ONS 15600 SONET R6.0.1 to the Supported NE Table
Third-Party Patches and Security Notices
Installing the CTM R6.0.0.414.2 Patch
Determining What CTM Patch Is Currently Installed on the CTM System
Backing Up the CTM Database Before Installing the CTM R6.0.0.414.2 Patch
Downloading the CTM R6.0.0.414.2 Patch
Installing the CTM R6.0.0.414.2 Server Patch
Installing the CTM R6.0.0.414.2 Client Patch in Windows
Installing the CTM R6.0.0.414.2 Client Patch in Solaris
Installation and Upgrade Caveats
Cisco Transport Controller Caveats
Cisco ONS 15327 and ONS 15454 SONET
Cisco ONS 15600 SONET and Cisco ONS 15600 SDH
Cisco CRS-1 and Cisco XR 12000
Obtaining Documentation and Submitting a Service Request
Release Notes Cisco Transport Manager Release 6.0
September 18, 2009
These release notes describe the caveats for Cisco Transport Manager (CTM) Release 6.0. These release notes accompany the Cisco Transport Manager Release 6.0 User Guide and the Cisco Transport Manager Release 6.0 Installation Guide.
Note
You can access the most current Cisco documentation, including these release notes, online at http://www.cisco.com/en/US/products/sw/opticsw/ps2204/tsd_products_support_series_home.html.
Contents
These release notes contain the following sections:
•
•
•
•
•
Introduction
Cisco Transport Manager is an advanced management system that provides functionality at the element and network management levels for Cisco optical network elements (NEs). 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 6.0, CTM's expanded charter includes not only management of the Cisco Optical Networking System (ONS) family of optical NEs, but also additional routing and voice platforms. CTM R6.0 supports the Cisco Carrier Routing System 1 (CRS-1), which includes the Cisco Catalyst 6509; the Cisco XR 12000; 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 R6.0.
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 6.0.
NE Software Releases Added
The following NE releases were added to Table 1, "CTM Supported NE Software Releases":
•
Note
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Caveats and Sections Added
The following caveats and sections have been added to the release notes:
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
Caveats and Sections Removed
The following sections were removed, because the CTM R6.0.0.414.2 patch inherits all bug fixes and obsoletes these earlier patches:
•
•
•
•
•
The following caveats were removed, because they are unreproducible:
•
•
CTM-Supported NE Software Releases
The following table lists the NE software releases supported in CTM R6.0.
Caution
Table 2 CTM-Supported NE Software Releases
ONS 15216 100-GHz OADM1/2/4
Release 2.2.2
Release 2.2.3
ONS 15216 EDFA2
Release 2.3
Release 2.4
ONS 15216 EDFA3
Release 1.1
ONS 15216 100-GHz Red/Blue Filters
Passive
ONS 15216 200-GHz Red/Blue Filters
Passive
ONS 15216 200-GHz OADM1/2
Passive
ONS 15216 EDFA1
Passive
ONS 15216 OSC
Passive
ONS 15216 DCU
Passive
ONS 15216 FlexLayer
Passive
ONS 15302
Release 2.0
Release 2.0.1
Release 2.0.2
ONS 15305
Release 2.0
Release 2.0.1
Release 2.0.2
ONS 15310 CL
Release 5.0
Release 5.0.2
Release 5.0.4
Release 5.0.61
Release 5.0.72
Release 6.0
Release 6.0.13
Release 6.0.34
ONS 15327
Release 4.1.3
Release 4.1.4
Release 4.1.5
Release 4.1.6
Release 4.1.8
Release 4.1815
Release 4.6.2
Release 4.6.4
Release 5.0
Release 5.0.2
Release 5.0.4
Release 5.0.66
Release 5.0.77
Release 6.0
Release 6.0.18
Release 6.0.39
ONS 15454 SDH
Release 4.1.4
Release 4.1.8
Release 4.6.3
Release 4.7
Release 5.0
Release 5.0.1
Release 5.0.2
Release 5.0.4
Release 5.0.610
Release 6.0
Release 6.0.111
Release 6.0.312
ONS 15454 SONET
Release 4.0.3
Release 4.1.1
Release 4.1.3
Release 4.1.4
Release 4.1.5
Release 4.1.6
Release 4.1.7
Release 4.1.8
Release 4.18113
Release 4.6.2
Release 4.6.4
Release 4.6.5
Release 4.7
Release 5.0
Release 5.0.2
Release 5.0.3
Release 5.0.4
Release 5.0.614
Release 5.0.715
Release 6.0
Release 6.0.116
Release 6.0.217
Release 6.0.318
ONS 15501
Release 4.1 AC
Release 4.1 DC
ONS 15530
Cisco IOS Release 12.2(25)SV
Cisco IOS Release 12.2(26)SV
Cisco IOS Release 12.2(26)SV1
ONS 15540 Extended Services Platform (ESP)
Cisco IOS Release 12.2(25)SV
Cisco IOS Release 12.2(26)SV
Cisco IOS Release 12.2(26)SV1
ONS 15540 Extended Services Platform with external cross-connect capability (ESPx)
Cisco IOS Release 12.2(25)SV
Cisco IOS Release 12.2(26)SV
Cisco IOS Release 12.2(26)SV1
ONS 15600 SDH
Release 1.4
ONS 15600 SONET
Release 1.1.1
Release 1.3.0
Note
Release 5.0.2
Release 5.0.4
Release 5.0.619
Release 5.0.720
Release 6.0
Release 6.0.121
ONS 15800
Release 2.1 (TL1 Agent Release 2.1)
ONS 15801
Release 2.1 (TL1 Agent Release 2.1)
ONS 15808
Release 2.2 (TL1 Agent Release 2.4)
Cisco CRS-1
Release 3.0
Release 3.2
Release 3.2.1
Cisco Catalyst 650922
CatOS 7.1(1) or later
Cisco XR 12000
Release 3.2
Release 3.2.1
Cisco MDS 9000 Multilayer Director and Fabric Switch
Fabric Manager X-launch
Cisco MGX 8880 Media Gateway
Release 5.0.20
Release 5.2.0
Voice-Enabled Cisco MGX 8850 Multiservice Switch
Release 5.0.20
Release 5.2.0
Voice-Enabled Cisco MGX 8830 Multiservice Switch
Release 5.0.20
Release 5.2.0
VISM-PR
Release 3.3.0
Release 3.3.10
Release 3.3.20 (supporting 3.3.10 features only)
VXSM
Release 5.0.20 (VXSM 1.5)
Release 5.0.70 (VXSM 1.5MR)
Release 5.2.00 (VXSM 2.0)
1 In order for CTM to support the ONS 15310 CL R5.0.6, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R5.0.6 to the Supported NE Table.
2 In order for CTM to support the ONS 15310 CL R5.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R5.0.7 to the Supported NE Table.
3 In order for CTM to support the ONS 15310 CL R6.0.1, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R6.0.1 to the Supported NE Table.
4 In order for CTM to support the ONS 15310 CL R6.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R6.0.3 to the Supported NE Table.
5 In order for CTM to support the ONS 15327 R4.181, you must add the software version to the Supported NE Table. See Adding the ONS 15327 R4.181 to the Supported NE Table.
6 In order for CTM to support the ONS 15327 R5.0.6, you must add the software version to the Supported NE table. See Adding the ONS 15327 R5.0.6 to the Supported NE Table.
7 In order for CTM to support the ONS 15327 R5.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15327 R5.0.7 to the Supported NE Table.
8 In order for CTM to support the ONS 15327 R6.0.1, you must add the software version to the Supported NE table. See Adding the ONS 15327 R6.0.1 to the Supported NE Table.
9 In order for CTM to support the ONS 15327 R6.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15327 R6.0.3 to the Supported NE Table.
10 In order for CTM to support the ONS 15454 SDH R5.0.6, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R5.0.6 to the Supported NE Table.
11 In order for CTM to support the ONS 15454 SDH 6.0.1, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R6.0.1 to the Supported NE Table.
12 In order for CTM to support the ONS 15454 SDH R6.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R6.0.3 to the Supported NE Table.
13 In order for CTM to support the ONS 15454 SONET R4.181, you must add the software version to the Supported NE Table. See Adding the ONS 15454 SONET R4.181 to the Supported NE Table.
14 In order for CTM to support the ONS 15454 SONET R5.0.6, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R5.0.6 to the Supported NE Table.
15 In order for CTM to support the ONS 15454 SONET R5.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R5.0.7 to the Supported NE Table.
16 In order for CTM to support the ONS 15454 SONET R6.0.1, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R6.0.1 to the Supported NE Table.
17 In order for CTM to support the ONS 15454 SONET R6.0.2, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R6.0.2 to the Supported NE Table.
18 In order for CTM to support the ONS 15454 SONET R6.0.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R6.0.3 to the Supported NE Table.
19 In order for CTM to support the ONS 15600 SONET R5.0.6, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R5.0.6 to the Supported NE Table.
20 In order for CTM to support the ONS 15600 SONET R5.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R5.0.7 to the Supported NE Table.
21 In order for CTM to support the ONS 15600 SONET R6.0.1, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R6.0.1 to the Supported NE Table.
22 The Cisco Catalyst 6509 is supported as part of the CRS-1.
Note
•
Adding the ONS 15310 CL R5.0.6 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R5.0.6, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15310 CL R5.0.7 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R5.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15310 CL R6.0.1 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R6.0.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15310 CL R6.0.3 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R6.0.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15327 R4.181 to the Supported NE Table
In order for CTM to support the ONS 15327 R4.181 you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15327 R5.0.6 to the Supported NE Table
In order for CTM to support the ONS 15327 R5.0.6, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15327 R5.0.7 to the Supported NE Table
In order for CTM to support the ONS 15327 R5.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15327 R6.0.1 to the Supported NE Table
In order for CTM to support the ONS 15327 R6.0.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15327 R6.0.3 to the Supported NE Table
In order for CTM to support the ONS 15327 R6.0.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SDH R5.0.6 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R5.0.6, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SDH R6.0.1 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R6.0.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SDH R6.0.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R6.0.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R4.181 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R4.181, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R5.0.6 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R5.0.6, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R5.0.7 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R5.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R6.0.1 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R6.0.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R6.0.2 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R6.0.2, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15454 SONET R6.0.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R6.0.3, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15600 SONET R5.0.6 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R5.0.6, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15600 SONET R5.0.7 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R5.0.7, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Adding the ONS 15600 SONET R6.0.1 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R6.0.1, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Third-Party Patches and Security Notices
Cisco reviews the known Oracle patch alerts every quarter, including patches for security breaches. If any Oracle patch applies to CTM or its components, Cisco tests the Oracle patch and includes it as a requirement for the next CTM patch. Cisco also conducts quarterly reviews of other third-party software products that CTM uses, such as Solaris, Apache, and Java.
Installing the CTM R6.0.0.414.2 Patch
Note
This section describes how to download and install the CTM R6.0.0.414.2 patch, which fixes the following caveats:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CTM R6.0.0.414.2 is intended for customers who are currently using CTM R6.0.0.399, R6.0.0.401.1, R6.0.0.402.1, R6.0.0.405.1, R6.0.0.407.1, or R6.0.0.412.1.
Note
Complete the following procedures to upgrade to the CTM R6.0.0.414.2 patch.
Determining What CTM Patch Is Currently Installed on 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:
showctmThe first line of the output gives you the release and patch level. Before proceeding, make sure that the output results to one of the following:
•
•
•
•
•
•
Backing Up the CTM Database Before Installing the CTM R6.0.0.414.2 Patch
Before installing the CTM R6.0.0.414.2 patch, it is strongly recommended that you back up the existing database. To back up CTM, refer to the following sections in Chapter 4 of the Cisco Transport Manager Release 6.0 User Guide:
•
•
Downloading the CTM R6.0.0.414.2 Patch
Step 1
Step 2
Step 3
Step 4
Note
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
cd /<directory_name>unzip CTM6.0.0.414.2.patch.zipFor example, to extract the .zip file to the /temp directory, enter:
cd /tempunzip CTM6.0.0.414.2.patch.zipStep 12
a.
b.
c.
d.
e.
Installing the CTM R6.0.0.414.2 Server Patch
To apply the CTM R6.0.0.414.2 patch to the server, complete the following steps:
Step 1
a.
b.
c.
The CTM server will be shut down in 5 minutes. Please log out of the CTM client before then.d.
e.
Step 2
a.
b.
c.
d.
Note
e.
This operation will log out the selected CTM user. The process will take approximately 1 minute and this CTM client will be unusable until then. Do you wish to continue?Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the request is complete. Log out all of the users listed in the Logged In CTM Users table to make sure that all user sessions are terminated.
Step 3
ctms-stopStep 4
./server_patch.shStep 5
ctms-startStep 6
showctmYou should see the following version string in the first line of output for the preceding command:
Cisco Transport Manager Server Version: 6.0 Build: 414 Patches: 2
Installing the CTM R6.0.0.414.2 Client Patch in Windows
The following steps describe how to patch a CTM client installation in Windows. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1
Step 2
client_patchYou can also use the Windows Explorer folder view to access the directory where the patch files were extracted and double-click the client_patch.bat file.
Step 3
Step 4
•
Client: 6.0 Build: 414 Patches: 2 (client configuration size)•
6.0 [6.0.0.414.2]
Installing the CTM R6.0.0.414.2 Client Patch in Solaris
The following steps describe how to patch a CTM client installation in Solaris. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1
Step 2
./client_patch.shStep 3
ctmc-startStep 4
•
Client: 6.0 Build: 414 Patches: 2 (client configuration size)•
6.0 [6.0.0.414.2]
Resolved Caveats
The following table lists caveats that are resolved as of the latest CTM R6.0 patch.
Table 3 Caveats Resolved as of the Latest CTM R6.0 Patch
CSCea14023
In the ONS 15454 SDH PM tables, TCA indications are not shown for the RS parameters on transponder trunk ports.
CSCea14157
PM statistics for nXP modules are not colored purple when TCAs are raised.
CSCec59052
CTM GateWay/CORBA does not show STS path PM TCAs.
CSCed32605
There is an FC_MR-4 bandwidth mismatch between CTM and CTC.
CSCed39576
When creating an L2 service, the service spontaneously disappears from the L2 Service table after 5 minutes; the ML card shows the L2 service does not exist; and traffic does not flow on the L2 service.
CSCed43082
When Multiprotocol Label Switching (MPLS) tunnels are configured on the CRS-1, they appear in the logical interface list.
CSCed58491
The Modify Front Ports screen shows all the ports as disabled.
CSCed65576
Some fields in the CRS-1 NE Explorer are read-only, yet you can change these fields in the tabular view by double-clicking a row and modifying the column value. You cannot make changes to these same fields in the editable section at the bottom of the window.
CSCed83344
Adding gigabit Ethernet interfaces to the Label Distribution Protocol (LDP) Configuration application generates the error message "Shared Media not supported - ApplicationName=LDP..."
CSCee23550
When a card is removed and reinserted, the reinserted card is not visible, or the interfaces associated with the card are not visible. (Related caveat ID: CSCeg33542.)
CSCee28913
Occasionally, an alarm is not displayed in the Alarm Browser when filtering on a specific time.
CSCee72306
In the Control Panel > ONS 15454 SDH/ONS 15600 SDH NE Service properties pane > Robust Fault Synchronization area, the ONS 15454 SDH and ONS 15600 SDH share the same Enable check box. It is impossible to set the values separately.
CSCee87992
An exception is returned when trying to perform a Force Switch operation through CTM GateWay/CORBA on 1+1 protection for the ONS 15600 SDH node.
CSCee95044
Protection switching values are shown as -1 instead of N/A in the real-time ONS 15600 SONET Line PM table.
CSCef02318
In some configuration applications, the Undo button does not work the first time you click it. However, it works the second time you click it.
CSCef02380
The Default All button does not work correctly with check boxes.
CSCef17170
An error message is received when configuring the authentication, authorization and accounting (AAA) application timeout for the first time.
CSCef18461
In the ONS 15600 SONET NE Explorer and ONS 15600 SDH NE Explorer > Alarm tab > Alarm Behavior subtab, there are no rows for Filler cards. Therefore, you cannot change the alarm profile for Filler cards.
CSCef22077
Cannot add another group to the root-system group user.
CSCef22430
When adding a policymap entry in the CRS-1 NE Explorer, if the only policing parameter that is configured is Congestion Avoidance > IP Precedence, you will receive the client-side validation error "Entry incomplete: At least one action for this class must be specified."
CSCef25359
The Control Panel does not refresh automatically or the Refresh Data tool does not flash to indicate that the CTM GateWay/CORBA component is installed.
CSCef61886
In a small configuration, CTM cannot process alarms at a rate of 20 alarms per second, and the Oracle database consumes a high amount of CPU.
CSCef64456
The bulk PM output reports invalid entries for VT circuits on optical ports on the ONS 15310 CL. (Related caveat ID: CSCin81278.)
CSCef69046
When an NE with a TCC2P card in Secure Config mode is changed to an end network element (ENE), CTM does not recognize the ENE.
CSCef69396
A previously generated loss of communication (LOC) alarm might not clear even after connectivity is restored successfully to the NE. (Related caveat ID: CSCeh49691.)
CSCef89152
CTM does not report link up or link down traps for ML cards in an ENE proxy/firewall setup. (Related caveat ID: CSCed52513.)
CSCef91402
After migrating the database, if you try to enable an L2 topology that is in L2ServiceNotReady state, the operation fails.
CSCef96838
A user profile that has read/write permission for the NE Explorer, read-only permission for the NE configuration, and read-only permission for L1 provisioning can download and upload TCC files from ML cards.
CSCeg03971
Manual links are never colored gray in the Network Map, yet autodiscovered links are sometimes colored gray (for example, when USE_FOR_ROUTING equals FALSE).
CSCeg05749
Bandwidth is not calculated for a virtual concatenation (VCAT) L2 topology that is equipped with multiple VLANs. (Related caveat IDs: CSCin85412, CSCeh57508.)
CSCeg16903
PM path parameters are shown as N/A (not supported) for the DS3XM-12 card. Also, PM statistics are not colored purple when TCAs are raised.
CSCeg17587
The CTM server does not start correctly, or does not collect PM data. The Error Log reports errors such as "ORA-14400: Inserted partition key does not map to any partition" and "ORA-06512: at line 1."
CSCeg20618
For the CRS-1, the Paste Special button does not work after the refresh/apply operation.
CSCeg20939
The Layer 2 Topology table shows "N/A" for available bandwidth.
CSCeg23854
If you reset the SSXC card when there are circuits on the card, CTC allows the Force Hard Reset operation after returning a warning message. The same operation fails in CTM.
CSCeg27903
When querying the MLL_INV_VIEW, total CPU usage is 100% and Oracle database CPU usage is 85%. Each query to the MLL_INV_VIEW consumes 2% to 3% of CPU and takes 30 seconds. The view returns approximately 12,000 records.
CSCeg28213
If all the links between two NEs are invalid, the link color indicates the highest severity alarm on the member links. Instead, the link color should be gray.
CSCeg29286
Cannot set the LED display on the route processor card in the CRS-1 NE Explorer > Rack view.
CSCeg33534
When an alarm is generated on an interface on the CRS-1, the alarm is shown on the back card instead of on the front card in the rack view and tree view of the CRS-1 NE Explorer.
CSCeg41647
When multiple CTM clients are logged in simultaneously with the same username, the x and y NE icon coordinates in the Network Map are not synchronized for all clients. The Refresh Data tool does not synchronize the map coordinates.
CSCeg42035
In the CRS-1 NE Explorer > MPLS-TE Configuration application, the Tunnel Head tab functionality is broken.
CSCeg43076
An exception occurs when launching the AF window inside the BGP application. The exception prevents data in the AF window from being committed on the router, and the AF configuration is not usable.
CSCeg43399
Cannot launch the text editor application from the CRS-1 SSHv2 window.
CSCeg43447
When launched for the ONS 15600 SONET, the Alarm Browser shows the wrong value in the Affected Object field when a path protection switch is performed.
CSCeg44313
Adding or deleting an ONS 15310 ML-100T-8 card to or from an existing L2 topology causes a loss of traffic.
CSCeg46836
A random health poll fails on some NEs in the DCN.
CSCeg46904
The active or standby state of protection groups is shown incorrectly for the ASAP card.
CSCeg46992
When CRS-1 NE Explorer applications are open while a configuration file is being restored, some event notifications might be dropped due to an internal event size limitation in CTM. When the configuration file restoration is complete, the Refresh Data toolbar icon might not flash in some of the open NE Explorer applications.
CSCeg48146
CTM cannot manage all NEs in a ring, and the log file records an INVALID_IP_ADDRESS message.
CSCeg49665
The Circuit Trace window displays incorrect information for an ONS 15600 circuit that is in Roll_Pending state. Only the Roll To circuit path is shown; the Roll From path is incorrect.
CSCeg49810
When using the Create Link wizard to create a Y-cable protected patchcord link, CTM shows all the compatible termination points in the Link Destination panel, even if the termination points do not belong to the same protection group. If you select the wrong termination point, the link is created, even though it is invalid.
CSCeg50938
In the ONS 15600 NE Explorer, the Force Hard Reset option fails for the SSXC card.
CSCeg50967
For the ONS 15600 TSC card, the Hard Reset option is enabled when the administrative state of the card is not OOS_MT.
CSCeg50976
Multiple null pointer exception errors are seen in the ONS15454NEService and CorbaServiceError logs.
CSCeg51929
CTM automatically removes a manual link between an OC-n or STM-n line card and a transponder or muxponder card when the transponder or muxponder termination point is deleted. Instead of being removed from the Link table and Network Map, the link should be marked as Invalid.
CSCeg53302
The real-time STS Path PM table shows a negative value (-1) for STS path parameters when CTC shows no data for the same parameters.
CSCeg53432
The CTM client does not restart after a failover.
CSCeg54264
If the CTM Apache web server stops, it does not restart automatically.
CSCeg54562
A unidirectional manual link is not removed automatically after creating a patchcord link.
CSCeg54684
CTM does not dynamically detect a failover on the Catalyst 6509 supervisor card.
CSCeg54751
Cannot set the GateWay/TL1 - NE Connection username and password for ONS 15454 SDH NEs.
CSCeg55394
The ONS 15310 NE Explorer > Network tab > SNMP subtab is missing information.
CSCeg55512
The ONS 15310 NE Explorer > Network tab > RIP subtab is missing mask address details. Also, the help file for the Create RIP Address Summary dialog box does not open.
CSCeg55698
Provisioner users cannot view or create STS-v or VT-v circuits.
CSCeg57018
In the ONS 15310 NE Explorer > Network tab > RIP subtab, the contents of the RIP Address Summary table are deleted if you enable or disable authentication for RIP version 2.0.
CSCeg57150
In the IOS Users table, it is possible to delete the IOS user who has been configured in the Control Panel for CTM-to-ML card connections.
CSCeg57165
The Network Map does not update the CRS-1 link status when all alarms are cleared.
CSCeg57986
When an existing routing policy is assigned as an access control list (ACL) name and committed, the error message that is returned is not intuitive.
CSCeg59500
After changing the SDH TCC2P LAN interface from a LAN connected NE (LNE) to an ENE, CTM loses connectivity to all DCC-connected NEs.
CSCeg60500
Rarely, CTM cannot discover a created topology.
CSCeg61474
Cannot mark a DCC-connected NE as an ENE.
CSCeg63838
Remote monitoring (RMON) threshold parameter options are not complete for CE-100T-8 cards.
CSCeg66331
The TL1 interface launched from an ENE does not open a session to the gateway network element (GNE).
CSCeg66371
A resilient packet ring (RPR) L2 topology is discovered in Incomplete state on 2-fiber MS-SPRings with one GNE and multiple ENEs.
CSCeg72114
The section trace Disable AIS/RDI on TIM-S check box is grayed out.
CSCeg72127
The section trace Disable check box is grayed out after selecting a trace line entry.
CSCeh46416
Software download fails on the ONS 1530x.
CSCeh46485
The CE-100T-8 NE Explorer does not display port status states.
CSCeh50246
The shutdown command is enabled in the ONS 15310 configuration file.
CSCeh56748
An error message is received when creating an L2 service for a GNE/ENE.
CSCeh57302
The Alarm Browser does not show traps for link up or link down alarms.
CSCeh57848
Manual circuit creation for a Layer 2 RPR causes an intermittent exception.
CSCeh58871
The Affected Object field in the Alarm Browser window displays a null value for PM alarms.
CSCeh58899
An L2 topology goes into Sync Failed state after an ML IOS user is added with no password. Removing the user with no password does not recover the L2 topology.
CSCeh58900
When you try to delete a pluggable port module (PPM) port on a transponder or muxponder card, you receive the error message "Failed to perform DELETE_PORT action."
CSCeh60004
Usage of the name "CIR_PIR" for a QoS profile type and for a default QoS profile of Advanced Type is confusing.
CSCeh60187
During L2 service creation, you can use a check box to enable or disable PM. However, when you then launch the Layer 2 Service Drop Ports table on the new service, the PM State value is shown as "N/A" instead of Enabled or Disabled.
CSCeh60202
CTM accepts invalid range values for QoS parameters. If you enter a value that is out of range, CTM automatically reverts the parameter to the current value, but no error message is shown.
CSCeh60269
CoS accounting is not applied consistently from the NE Explorer.
CSCeh60273
The CTM GUI indicates that the L2 bandwidth modification succeeded, but the ML card console shows error messages.
CSCeh60275
The NE service crashes or cannot be brought up.
CSCeh60401
The NE Explorer does not indicate whether GFP-F or HDLC mode is enabled.
CSCeh61602
The L2 Topology table shows multiple entries with the same name and Incomplete status.
CSCeh62153
Java exceptions occur while configuring an ONS 15600 SONET as a GNE-ENE.
CSCeh62328
When the ONS 15600 uses an IP address as its NE ID, the ENE Devices table does not list that NE in the filter option. Therefore, you cannot filter on an ONS 15600 NE that has an IP address as its ID.
CSCeh62617
An error message is displayed when you click the real-time PM button for the ONS 15305.
CSCeh62645
Multiple drop additions on the same ML module are not updated in the configuration. (Related caveat ID: CSCeh72670.)
CSCeh63608
A change from ENE to LNE fails for the ONS 15600 SONET and SDH.
CSCeh64051
While creating a point-to-point topology with a name that matches an existing L1 circuit name, you receive the error message "A circuit with the same name already exists. Enter a unique L2 topology name."
CSCeh64717
After the CTM R5.0.2 installation completes successfully, CTM fails to start.
CSCeh65187
If an ML module is removed from an L2 topology, CTM does not perform a validation to check for existing VLANs on the module being removed and clean the module's configuration.
CSCeh66007
The Alarm Browser menu option is available for passive ONS 15216 OADM NEs, yet launching the Alarm Browser generates an error message.
CSCeh66098
The create link behavior for ONS 15216 OADM NEs is inconsistent between the Domain Explorer and the Network Map.
CSCeh67115
A Java null pointer exception occurs while adding the ONS 15600 SONET to the CTM server. The NE is discovered, but exceptions occur and the Error Log records a major error.
CSCeh67380
The getAllEMSAndMEActiveAlarms method returns a ProcessingFailureException when there are CRS-1 NEs managed by the CTM server. The ProcessingFailureException indicates "Unsupported NE model" as the error reason.
CSCeh70850
In the Create L2 Service wizard and Add/Remove Cards wizard, data does not display correctly when you scroll or pan across the screen.
CSCeh71593
The IAUninstaller.sh server script does not remove the S99CTMServer script during the CTM server uninstallation process.
CSCeh71615
The IAUninstaller.sh server script does not remove the CTM Oracle SSID from the oratab file.
CSCeh71635
The IAUninstaller.sh server script does not remove the ctms-abort, ctms-start, ctms-stop, and ctms-stop-service scripts from the /usr/bin directory during the CTM server uninstallation process.
CSCeh83555
By default, the NE service for all NE types is shown as Active in the Control Panel window. When deactivating the NE service for NEs that have not been added to CTM, the following error message is received:
EID-5026: The CTM service is not connected to Service Manager. An error occurred while stopping this service.
By default, the PM Service for all NE types is shown as Not Active in the Control Panel window. When activating the PM Service for NEs that have not been added to CTM, following message is received:
EID-5025: The CTM service is currently connected to Service Manager. An error occurred while starting this service. Verify that the service is installed on the CTM server and retry.
CSCeh84563
NEs of the same type show a high number of Loss of Communication alarms.
Note
CSCei20759
During L2 service creation, if you set a class map name in CTM that contains more than 24 characters, the ML card crashes, and you cannot use the card.
Note
CSCei57964
The About Cisco Transport Manager screen and the initial splash screen display the CTM server version as Unknown.
Note
CSCei67988
Cannot set OPR for Optics or Physical thresholds on MRC cards. (Related caveat IDs: CSCsd13877, CSCsd36732.)
Note
CSCei72696
The operational state of an ONS 155xx NE remains permanently as In Service-Initializing.
Note
CSCei74892
VLANs created with only one drop are discovered as Incomplete in CTM.
CSCei80883
CTM loses connectivity to all NEs managed by a specific CTC-based NE service. The logs show CORBA timeout errors when attempting to reconnect to the problematic NEs. (Related caveat ID: CSCei92304.)
Note
CSCei86342
Cannot enable or disable the AIS and RDI on the J2-TIM for DS3XM VT circuits.
Note
CSCei86578
The following error message is returned when trying to open the Alarm Log:
EID-315: Cannot retrieve data from database.Note
CSCei95305
Cannot use the Create Circuit wizard to create STS-18c/VC4-6c and STS-36c/VC4-12c circuits.
Note
CSCej01043
One L2 topology splits into multiple topologies.
Note
CSCin48556
When using the getCTMHistoryPMData method to retrieve section PM parameters for an OC-3 card, some of the returned data is marked invalid.
CSCin55315
When the MS-SPRing table and the BLSR table are open simultaneously, the Edit, Upgrade, and Exercise buttons do not work in the BLSR table.
CSCin63805
When the NE name contains a comma (,), the following operations fail: memory backup and restore, NE authentication, NE security features, create NE user using the NE User Access Administration table, launch CTC (CTC menu option is disabled), and software download.
CSCin65753
The getTCATPParams method does not retrieve all line parameters.
CSCin66373
The Create SNMP Trap Destination and Modify SNMP Trap Destination dialog boxes display an extra attribute, "Max Traps per Second." This field is invalid and is no longer required.
CSCin66530
CTM fails to detect that a critical process has been stopped.
CSCin66815
Cannot change the frame format on DS3I cards from CTM GateWay/CORBA.
CSCin73061
The alarm count on a link is not correct in the Link table or Network Map.
CSCin73425
The API setTPData method throws an exception when trying to change the service state of a loopback port from Out of Service-Maintenance to In Service.
CSCin73434
Cannot create an RPR topology for 24c circuits on SONET NEs.
CSCin73668
When adding a CTM GateWay/TL1 user, the OSS Profile Name field in the Add GateWay/ TL1 User dialog box does not accept special characters (; : ,). An error message is generated if you use special characters in the OSS profile name.
CSCin74400
After migration, the Password Set Time field for users is set to the current time in the CTM Users table.
CSCin75118
In the Network Map, discovered ONS 15454 SDH NE icons are shown as "ONS 15454 unknown" instead of "ONS 15454 SDH."
CSCin75143
The error message that appears in the CTM GateWay/TL1 window when the CANC-USER command is entered appears with wrong username.
CSCin75152
The API getContainedPotentialTP returns /ds=1 for a preprovisioned XTC protect card on a DS3 port. The API is invoked for a physical termination point (PTP) /rack=1/shelf=1/slot=5/port=30.
CSCin75538
The Control Panel shows that an enabled CTM GateWay/CORBA service is stopped even if it is running.
CSCin75609
A facility loopback cannot be applied on a CTP loopback (DS1 circuit in a DS3XM card) in CTM GateWay/CORBA.
CSCin75664
The setTPData method does not allow changing the service state of a port on an OC-3_8 card from Out of Service-Auto In Service Soak to any other service state.
CSCin76280
The setTPData method allows setting the XC loopback on an STM1E-12 card. Since the STM1E-12 is an electrical card, it should not be possible to set XC loopbacks on it.
CSCin76771
TrailTraceMonitor (J1 path trace) is allowed in setTPData for DS1 circuits and DS1 ports on XTC cards. It should not be allowed.
CSCin77779
The Equipment Inventory table is empty for ONS 15454 SDH ENEs when the GNE is an ONS 15600 SDH.
CSCin83543
CTM allows you to create PTP and RPR Layer 2 topologies on ML cards that have different framing modes.
CSCin83931
A "Carrier Loss on LAN" alarm is not generated on an ML card for the ONS 15454 R4.6.2.
CSCin84307
There is a mismatch between historical and real-time PM data for the XTC card on the ONS 15327.
CSCin84683
Cannot create a Layer 2 service on a Layer 2 topology with 24 or more drop ports on an RPR, or 10 or more drop ports on a point-to-point topology.
CSCin84847
In the slot properties pane for the DS3XM-12 card, the Alarm Behavior tab is missing rows for odd port numbers greater than 12.
CSCin84906
The AdminSSM value is editable when EnableSyncMsg is false.
CSCin84974
The VCAT Member table does not report the VCAT state of member circuits.
CSCin85046
The ONS 15454 SDH Section PM table shows an RS-UAS value of 0 for STM-n cards.
CSCin85067
The Create Circuit wizard displays the error message "Index:0 Size:0," then hangs.
CSCin85105
During VT circuit creation, an automatically created VAP circuit is not deleted if the VT circuit creation is cancelled.
CSCin85120
During VT circuit creation, an automatically created VT tunnel is not deleted if the VT circuit creation is cancelled.
CSCin85299
After the password expires, the Change Password dialog box closes before you can change the password.
CSCin85480
In the J1 Path Trace and J2 Path Trace dialog boxes, the Expected String field accepts a 64-byte entry, even though the maximum transmit string length is 16 bytes.
CSCin85582
When using the CTM GateWay/CORBA APIs to retrieve PM data for the STM1-8 multiplex section, the PMP_ES value for the far-end section is not retrieved.
CSCin85805
The 1-day real-time PM value for the RS-BBE parameter on the STM4_4 card is not updated.
CSCin86042
The PM Query by NE Model wizard contains duplicate module entries when the number of objects to be polled exceeds the allowed limit.
CSCin86183
In the NE Explorer for the ONS 15327, ONS 15454 SONET, ONS 15454 SDH, and ONS 15600, the card slot properties pane > Module View tab shows ports with no alarms, even when alarms exist on the ports.
CSCin86241
Due to the lack of required routing, RPR creation fails. An error message is returned, indicating that topology creation failed. However, the Circuit table shows that some circuits were created successfully. Because not all the circuits could be created, the topology creation fails.
CSCin86375
If you create a VC-4 circuit on an E1 card on an ONS 15454 SDH NE, there is no circuit-related data shown in the NE Explorer > E1 properties pane > VC-12 tab, even though the Circuit table contains circuit data.
CSCin86380
Cannot change the severity level of LOC alarms in the Control Panel.
CSCin86449
The ONS 15454 MSTP NE Explorer does not reflect a change in the administrative state of an OADM, amplifier, or multiplexer/demultiplexer card.
CSCin86450
QoS profile creation fails when the Description field contains more than 50 characters.
CSCin86562
Using CTM GateWay/CORBA, you can set the link cost to a negative value.
CSCin88601
The real-time Physical PM table appears blank when DWDM cards with PIM or PPM ports are selected along with fixed-port cards.
CSCin90864
The CTM GateWay/CORBA getL2Topology method retrieves the wrong number of VCAT member circuits.
CSCin90935
Cannot create manual links on ONS 15600 SDH R1.4 NEs.
CSCin90951
Cannot use CTM GateWay/CORBA to create a VLAN with a dot1q drop port on an ML-100T-8 card.
CSCin90959
Using CTM GateWay/CORBA, the modifyMLVLANAddFrontPorts method fails to add drop ports to an existing L2 service.
CSCin93648
Cannot create manual links at the physical or SONET/SDH layer if the link source or link destination is a CTC-based NE running CTC version 4.14-004C-09.23.
CSCin94865
Cannot create manual links at the physical or SONET/SDH layer if the link source or link destination is an ONS 15327 OC-48 card. This problem applies only to the ONS 15327 R5.0 and R5.0.2.
CSCin95359
When a set of GNEs and ENEs connected in a DCC ring is added to CTM, some ENEs always remain in In Service-Initializing state.
CSCsb32554
The method ManagedElementManager_I::getAllDestPTPsforSNCProvisioning does not work for XTC cards on ONS 15327 NEs.
Note
CSCsb47470
Cannot create more than 28 LDCC connections on an NE. A similar problem occurs on CTC.
CSCsb66104
The methods ManagedElementManager_I::getAllSrcPTPsForSNCProvisioning and ManagedElementManager_I::getAllDestPTPsForSNCProvisioning do not return the available PTPs for SNC provisioning on DS3XM-12 cards.
Note
CSCsb66107
When you launch Cisco Edge Craft from the CTM client, you cannot view the Cisco Edge Craft online help or release notes or run the internal VT100 terminal.
Note
CSCsb67401
The CTM server crashes. When the CTM server is restarted after the crash, the operational state of the NEs does not change to In Service. (Related caveat ID: CSCsb71319.)
Note
CSCsb70689
Cannot launch the Link Utilization table from the Link table for ONS 15327 NEs.
Note
CSCsb87835
The Alarm Browser and Alarm Log do not display DBOSYNC alarms from ONS 15600 R1.13 NEs.
Note
CSCsb93921
Out of Service/In Service operations and scheduled configuration resynchronizations on an NE do not synchronize the inventory table for the NE.
Note
CSCsb95230
Creation of an STS-n circuit between E100 cards 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>Note
CSCsc01865
After changing the IP address from the NE Explorer and rebooting the NE, the IP address changes in CTC, but the CTM Domain Explorer and database still show the old IP information. The NE undergoes a loss of connectivity, and marking the NE as Out of Service and then In Service does not help.
Note
CSCsc19490
CTM shows invalid or incorrect values for some 15-minute performance data parameters for ML/Ethernet cards.
Note
CSCsc20505
Client login takes a long time.
Note
CSCsc22000
Need to enhance CTM debug tools to show NE information from the NEService cache.
Note
CSCsc39785
The L2 service is stuck in a partially complete state in a GNE/ENE topology and the IOS Users table is missing the required entries for the ENEs.
Note
CSCsc47089
Stopping the CTMTL1FWDService process from the Control Panel does not stop it on the server.
Note
CSCsc50889
L1 circuits are shown in partial state, causing problems in L2 topologies.
Note
CSCsc50897
Topologies split or become incomplete after restarting the NE service or marking NEs as Out of Service and then In Service.
Note
CSCsc52838
In the Network Map, if the view is filtered on SONET/SDH, you cannot create links.
Note
CSCsc57099
Some L2 service drops are missing from the L2 Topology table.
Note
CSCsc57101
Topologies A and B are incomplete and their circuits are exchanged.
Note
CSCsc57167
The Change Card operation fails for the ONS 15454 SONET and ONS 15454 SDH.
Note
CSCsc57914
Cannot create an L2 topology with a name that was used before and then deleted.
Note
CSCsc57940
An L2 topology changes to Incomplete state after NEs are marked as Out of Service and then In Service.
Note
CSCsc63992
The Alarm Browser does not show VC group alarms on ONS 15305 and ONS 15302 NEs.
Note
CSCsc64485
The SDH NE BITS timing always shows a locked state.
Note
CSCsc65994
Some L2 topologies are not discovered.
Note
CSCsc67873
CTM circuit information does not synchronize with CTC circuit path information.
Note
CSCsc71029
An ENE is not discovered correctly after it is moved from another location. CTM still discovers the ENE with the old IP address and the old GNE that it is no longer attached. All settings appear to be correct in CTC launched from Internet Explorer.
Note
CSCsc91975
Clicking the Create button for a pluggable port module (PPM) does not display the dialog box for creating PPMs on the ASAP card.
Note
CSCsc91984
PM data collection fails and the Alarm Browser reports Lost 15-minute/1-day PM alarms. The Error Log contains "HTTP Server too busy" or "HTTP Error: 401" messages for the NE. (Related caveat IDs: CSCsb92174, CSCsd29273.)
Note
CSCsd05320
It is possible to retrieve the NE backup memory from CTM and save it to the CTM client machine. However, CTM reports the retrieval and saving of the memory as successful even when the file saving to the client machine has failed.
Note
CSCsd12352
An error message is returned when attempting to create a virtual link between two non-DCC connected nodes connected via MRC_12 cards.
Note
CSCsd12649
An RPR VCAT splits under certain conditions.
Note
CSCsd26043
When you drag and drop a DS1 line on a VXSM card with a CALEA image (5.50(70.200)), an SNMP error is returned.
Note
CSCsd31853
RPR creation fails for a CTM user with Provisioner privileges.
Note
CSCsd57819
The ML card traffic classification does not change into the newly applied QoS values.
Note
CSCsd70181
The Error Log shows a major error with the following message:
Finding NE IP Add in NE Info Table: VALUEGNECONNECTED
Note
CSCsd71619
When an NE or a network service is managing multiple NE versions, for example, NE R4.6.x and R6.x, the R4.6.x NEs are managed by the NE or network service but NE R6.x and later do not come up. The NE or network service uses an IIOP port to bind R4.6.x NEs but it needs a defined SSLIOP port to bind NE R6.x and later.
Note
CSCsd78026
When BLSR exercise jobs are scheduled, the first job is executed correctly on the east and west ports but the next scheduled job shows that both BLSR exercise jobs are scheduled on the west port. No job is shown on the east port.
Note
CSCse17022
PM collection fails for ONS 1580x NEs.
Note
CSCse18080
The port name is not displayed under the Physical Location column of the Alarm Browser.
Note
CSCse35917
After upgrading an NE release from 5.0.x to 6.0, CTM does not clean up the original port connection to the NE.
Note
CSCse51521
The Alarm Browser and the Network Map are not synchronized. Both do not display consistently the alarm status. The Alarm Browser displays the correct values.
Note
CSCsg04592
The CTM client exits if you enter the wrong login password in the CTM Locked dialog box.
Note
CSCsg35907
Cannot clear the Max Login Attempts Exceeded alarm for an unknown user.
Note
CSCsg65879
CTM GateWay/CORBA does not send NE unreachable messages to the OSS. When the NE is marked as Out of Service, the communication state should be CS_UNAVAILABLE in the notifications.
Note
CSCsh06817
The "Maximum login attempts exceeded" alarm is not cleared after unchecking the Infinite check box in the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area.
Note
CSCsh45398
The TCA_EVENT_TABLE is not pruned and grows to millions of rows. The huge number of rows causes high CPU usage and performance degradation.
Note
CSCsh46229
PM data collection takes longer than 15 minutes, resulting in high CPU usage.
Note
CSCsh79249
The oraclesw9i/admin/udump directory contains a prune_pm.err error log file that reports the following error message: "ORA-14083: Cannot drop the only partition of a partitioned table." (Related caveat ID: CSCsh70233.)
Note
CSCsh92123
When you perform a lot of manual alarm acknowledgement, the size of the ACK_TABLE increases. When this happens, it takes too long to show alarms in the Alarm Browser and to manually acknowledge selected alarms.
Note
CSCsi03340
All NEs in a GNE/ENE ring are shown as ENEs. The GNEs are also shown as ENEs.
Note
CSCsi97803
When you log into CTM as an Operator, Provisioner, Network Admin, or SysAdmin user, the number of alarms shown on the Dashboard is inconsistent with the number of alarms reported by the Alarm Browser.
Note
CSCsk17081
Cannot connect to ONS 15600 SONET R1.1.1 NEs.
Note
CSCsl02048
After alarm pruning, the ACK_TABLE contains old data and a pruning error is logged.
Note
CSCuk48769
Provisioner users have access to restricted Administration menu options.
CSCuk48857
The Test NE Connectivity feature does not work for ONS 1580x NEs.
CSCuk49660
When SNMP PM data is not collected on ML-series cards, a 15-minute PM lost alarm is raised against each ML-series card. It would be preferable to see a single EMS alarm for the NE instead of multiple 15-minute PM lost alarms on the ML-series cards on the NE.
CSCuk53105
In the OTN tab > Trail Trace Identifier subtab, the current transmit and current expected strings are not updated with the trail trace identifier level selected.
CSCuk53272
After migrating the database from CTM R4.6 or CTM R4.7 to CTM R5.0.x, some alarms in the Alarm Log show "Bad Value" instead of "Equipment" in the Affected Object field.
CSCuk53578
Cannot sort on the Interface column in PM tables.
CSCuk54024
Cannot change the ML card microcode from the NE Explorer.
CSCuk54816
The Circuit table does not display circuit destination endpoints in the correct sequence for optical channel network connection (OCHNC) circuits.
CSCuk55015
The line Ethernet Maximum Size parameter is not updated automatically in the NE Explorer > 10GE Line Config subtab when this parameter is changed in CTC.
CSCuk55018
PM statistics for 32WSS and 32DMX cards are not colored purple when TCAs are raised.
CSCuk55036
The real-time Ethernet PM table for DWDM-series cards shows additional data for non-Ethernet supporting modules.
CSCuk55054
An unknown card is not shown in the NE Explorer when the card is inserted after the NE is in service.
CSCuk55129
Real-time PM tables report valid data for 32WSS and 32DMX card ports that are not in service.
CSCuk55136
The Locate Alarm/Event menu option and toolbar icon are disabled for ONS 15216 OADM alarms.
CSCuk55143
Ethernet PM table is missing two 8b10b parameters for DM_2.5G and DMP_2.5G cards provisioned for ONE_GE payload.
CSCuk55217
15-minute and 1-day PM tables for FEC statistics display rows for DM_2.5G and DMP_2.5G cards.
CSCuk55317
ONS 15216 DWDM and ONS 15216 OADM NEs allow links on the chassis PTP in opposite directions. That is, the PTP functions as a transceiver when it should allow links in only one direction (Tx or Rx).
CSCuk55578
The Power Add value in the 32WSS card properties pane > Optical Channel Connector tab does not update when you click the Update button.
CSCuk55600
The real-time Optical Physical PM table displays two rows with the same time stamp and the same slot and port number for each PM sample.
CSCuk56171
A major Link Down trap alarm is generated when you modify an Ethernet port that is already shut down. The generated alarm is not cleared automatically.
CSCuk58293
Cannot create bidirectional optical channel network connection (OCHNC) circuits on ONS 15454 SONET R5.0.2 or ONS 15454 SDH R5.0.2 NEs.
Open Caveats
The following sections describe the caveats that were reported against CTM R6.0:
•
•
Note
Note
Installation and Upgrade Caveats
•
Symptom If you repeat migration from CTM R4.7.x to CTM R6.0 after the first migration attempt fails, and if you enter the wrong password for the ctmanager user, the installation does not detect the incorrect password.
Conditions
Workaround
cp /opt/olddbinfo /opt/newdbinfo•
Symptom When you connect a CTM R4.7 or R5.0.x client with a small memory configuration to a CTM R6.0 server, the client upgrade to R6.0 starts automatically. During the upgrade, if you select a different memory configuration (for example, medium), the new CTM R6.0 client launches for the first time with a small memory configuration instead of medium.
Conditions
•
•
Workaround
•
Symptom After migrating the database from CTM R5.0 to R6.0, the alarm configuration is reset to the default value.
Conditions
Workaround
•
Symptom If CTM is installed on a server that does not have adequate disk space, the install script does not detect this condition correctly and return an error message. The installation is allowed to continue, but CTM does not install correctly.
Conditions
Workaround
If you do not check disk space before installation and encounter errors during installation, complete the following steps to recover:
Step 1
cd /opt/CiscoTransportManagerServerdf -k .
Note
cd /optrm -rf CiscoTransportManagerServer*Step 2
Step 3
•
Symptom You cannot create a new FTP account on standby node.
Conditions
Workaround
Step 1
•
•
•
For example:
cp /cdrom/cdrom0/Disk1/InstData/Solaris/VM/createUserID.sh /tmpcp /cdrom/cdrom0/Disk1/InstData/Solaris/VM/createGroupID.sh /tmpcp /cdrom/cdrom0/Disk1/InstData/Solaris/VM/createUserGroupIDModule.sh /tmp
Note
Step 2
Note
Step 3
Note
•
Symptom Database migration from CTM R5.0.x to CTM R6.0 fails when the ONS15454_FC_PM_TABLE contains partitions that cross years.
Conditions
To verify whether you will experience this migration problem, enter the following commands and then check the partition data:
sqlplus ctmanager/ctm123!SQL> set pages 1000SQL> select partition_name from user_segments where segment_name ='ONS15454_FC_PM_TABLE';SQL> exitWorkaround
Step 1
Step 2
Step 3
Step 4
Note
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
•
Symptom The migration from CTM R5.0.x to CTM R6.0 fails.
Conditions
su - oraclesqlplus ctmanager/ctm123!SQL> select npid from subnetwork_tableIf any network partition ID is greater than 9, you must perform the following workaround.
Workaround
Step 1
Step 2
Step 3
Step 4
Note
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
CTM Client Caveats
This section contains the following information:
Alarm Management
•
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
Workaround
•
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
Workaround
•
Symptom
EID-315: Cannot retrieve data from database.Conditions
Workaround
sqlplus /nologconnect /as sysdbaALTER TABLESPACE TEMP_TABLESPACE ADD TEMPFILE `/db02/CTM5_0/CTM5_0_temp_1.dbf'SIZE 209715200 REUSE AUTOEXTEND ON NEXT 104857600 MAXSIZE unlimited; ExitAlternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom CTM and CTC do not show the actual equipment type for G1K-4 and TCC2 cards.
Conditions
Workaround
•
Symptom The Alarm Log does not display alarms when CoS RMON exceeds the threshold value.
Conditions
Workaround
•
Symptom The Domain Explorer does not show the correct alarm status for MGX NEs. The Alarm Browser does not show connection-related alarms.
Conditions
Workaround
•
Symptom Port name is not displayed under the Physical Location column of the Alarm Browser.
Conditions
Workaround
•
Symptom The Alarm Browser and the Network Map are not synchronized. Both do not display consistently the alarm status. The Alarm Browser displays the correct values.
Conditions
Workaround
•
Symptom When you log into CTM as an Operator, Provisioner, Network Admin, or SysAdmin user, the number of alarms shown on the Dashboard is inconsistent with the number of alarms reported by the Alarm Browser.
Conditions
Workaround
•
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
Workaround
•
Symptom The CTM client does not send notification dialogs or audible notifications for ONS 1580x alarms.
Conditions
Workaround
Circuit and Link Management
•
Symptom You cannot create a circuit with a secondary destination and dual-ring interconnect (DRI) protection.
Conditions
Workaround
•
Symptom Automatic routing of I-DRI circuits fails. However, routing is successful when the primary and secondary destinations are swapped.
Conditions
Workaround
•
Symptom Cannot change the administrative state to Out of Service-Out of Group (OOS_OOG) for VCAT circuits or VCAT member circuits.
Conditions
•
•
Workaround
•
Symptom A manual link is not removed automatically when a patchcord link with the same layer type is created between the same endpoints.
Conditions
Workaround
•
Symptom Cannot create a physical layer unidirectional link between ONS 15216 NEs and ONS 15454 multiplexer cards.
Conditions
Workaround
•
Symptom Cannot create links between ONS 15454 ITU cards and ONS 15454 multiplexer cards.
Conditions
Workaround
•
Symptom The BLSR Creation wizard does not display link labels correctly.
Conditions
Workaround
•
Symptom During low-order (LO) VCAT circuit creation, VC LO options, which could include the following, are not available: Create VC Tunnel on Transit Nodes, Create VC LO Aggregation Point, None, and so on.
Conditions
Workaround
•
Symptom Manual circuit creation details are cluttered, garbled, and difficult to read.
Conditions
Workaround
•
Symptom The Link Utilization table contains an invalid entry for a protected low-order circuit passing through a tunnel.
Conditions
Workaround
•
Symptom The J1 path trace displays expected and received bytes at the source end for unidirectional circuits.
Conditions
Workaround
•
Symptom In the Link table, the provision type for MDS 9000 links is shown as Unmanaged.
Conditions
Workaround
•
Symptom Cannot enable or disable the AIS and RDI on the J2-TIM for DS3XM VT circuits.
Conditions
Workaround
•
Symptom The Protection field in the Link table is empty for links on MDS 9000 NEs.
Conditions
Workaround
•
Symptom Cannot use the Create Circuit wizard to create STS-18c/VC4-6c and STS-36c/VC4-12c circuits.
Conditions
Workaround
•
Symptom When a monitor circuit is created from CTM, the Circuit Status might be shown as Incomplete in CTC.
Conditions
Workaround
•
Symptom The protection type for physical layer links is not automatically modified when the underlying protection in the NE is deleted.
Conditions
Workaround
•
Symptom The Repair Circuit menu option is grayed out for ONS 15327 NEs.
Conditions
Workaround
•
Symptom Diverse shared risk link group (SRLG) constraints are not validated during manual circuit creation.
Conditions
Workaround
•
Symptom
Conditions
Workaround
•
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
Workaround
•
Symptom CTM supports manual link creation for SONET or SDH layer rates only.
Conditions
Workaround
•
Symptom When DCC links are deleted, CTM does not display patchcord links between the same nodes.
Conditions
Workaround
•
Symptom Patchcord links with Y-cable protection are shown with no protection in the Link table.
Conditions
1.
2.
3.
4.
Workaround
•
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
Workaround
•
Symptom A bidirectional optical channel (OCH) link between two BT10E-LC cards on different ONS 15808 terminal NEs does not show the correct alarm status. The link is always shown as green, even if an LOS alarm is present on one card.
Conditions
Workaround
•
Symptom SONET or SDH links between an ONS 1580x and another type of NE are shown incorrectly as invalid.
Conditions
Workaround
•
Symptom Manual link creation between transponder and muxponder client ports fails with the error message "Create link action was not completed."
Conditions
Workaround
•
Symptom Cannot launch the Link Utilization table from the Link table for ONS 15327 NEs.
Conditions
Workaround
•
Symptom The Link table does not update when the Layer 2 Topology table is modified.
Conditions
Workaround
•
Symptom Cannot create dual rolls manually for VT PCA circuits.
Conditions
Workaround
•
Symptom Creation of an STS-n circuit between E100 cards 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
Workaround
•
Note
•
•
•
•
Symptom L1 circuits are shown in partial state, causing problems in L2 topologies.
Conditions
Workaround
•
Symptom In the Network Map, if the view is filtered on SONET/SDH, you cannot create links.
Conditions
Workaround
•
Symptom The SDH NE BITS timing always shows a locked state.
Conditions
Workaround
•
Symptom CTM circuit information does not synchronize with CTC circuit path information.
Conditions
Workaround
•
Symptom An error message is returned when attempting to create a virtual link between two non-DCC connected nodes connected via MRC_12 cards.
Conditions
Workaround
•
Symptom Circuit creation fails and the circuit is not visible in the GUI. The CTM NE service records an error similar to the following:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1Conditions
su - oraclesqlplus ctmanager/ctm123!SQL> set pagesize 1000SQL> select npid from subnetwork_table;Workaround
Step 1
Step 2
Step 3
Step 4
Note
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
su - oraclesqlplus ctmanager/ctm123!SQL> @/tmp/patch_cir.sql•
Symptom 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.Conditions
•
•
•
•
•
Workaround
•
Symptom The Circuit table does not contain the expected circuits.
Conditions
Workaround
•
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
Workaround
•
Symptom The link alarm count and link color are not updated.
Conditions
Workaround
User Management
•
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
Workaround
•
Symptom A Cisco IOS user created on the ML CLI with no password is not displayed in the IOS Users table.
Conditions
Workaround
•
Symptom Cannot unlock the CTM client until the CTC username and password are entered.
Conditions
Workaround
•
Symptom A SysAdmin user is disabled after 60 days of nonuse.
Conditions
Workaround
Data Services
•
Symptom If the Layer 1 circuit in a point-to-point Layer 2 topology is in Partial state, the topology is not discovered. If the Layer 1 circuit is related to an RPR, the RPR is not discovered by CTM if all the circuits are in Partial state. If one or more circuits in the RPR are in Partial state, the RPR is discovered as an incomplete topology.
Conditions
Workaround
•
Symptom The Layer 2 Service Drop Ports table shows the QoS profile name as "Custom QoS" even though you have applied a specific QoS profile from CTM.
Conditions
policy-map POLICY_GIGE1_INclass CLASS_BG2_ADVANCED_2_1police 2000000 8000 pir 64000000 conform-action set-cos-transmit 5 exceed-action set-cos-transmit 7 violate-action set-cos-transmit 7
Note
CLI accepts the preceding commands without any errors. However, if you enter the following class-map command:
class-map match-all CLASS_BG1_ADVANCED_1_1match bridge-group 1match cos 2match ip dscp 22The show run command returns the following output:
class-map match-all CLASS_BG1_ADVANCED_1_1match bridge-group 1match cos 2match ip dscp af23Workaround
•
Symptom The VLAN ID displayed in CTM is retrieved from the SPR/POS subinterface and not from the encapsulation command that is executed for the SPR/POS subinterface.
Conditions
Workaround
•
Symptom After the CTM server is rebooted, Layer 2 RPR services take about 20 minutes to get to "Complete" L2 Sync State.
Conditions
Workaround
•
Symptom Cannot delete VLANs in an RPR configuration.
Conditions
Workaround
•
•
•
Symptom When adding a port with a custom profile, all other VLAN ports defined as CIR_PIR and Best_Effort become Custom QoS. The port QoS changes for all ports.
Conditions
Workaround
•
Symptom You can create a new QoS profile successfully, but you cannot use the new profile without closing and reopening the Create/Modify Layer 2 Service Drops wizard.
Conditions
Workaround
•
Symptom CTM fails to create an L2 service on an RPR ring when there are approximately 110 services created on the ML card.
Conditions
Workaround
•
Symptom
Conditions
Workaround
•
Symptom An RPR is shown as up even though the station IDs are not unique.
Conditions
Workaround
•
Symptom
Conditions
Workaround
•
Symptom The multilayersubnetwork.idl file returns errors when it is compiled with a third-party IDL compiler.
Conditions
Workaround
•
Symptom One L2 topology splits into multiple topologies.
Conditions
Workaround
Alternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom The Diverse SRLG option is disabled in the Routing Preferences pane during RPR Layer 2 topology creation.
Conditions
Workaround
•
Symptom If one or more L1 circuits related to an RPR are deleted, the L2 topology's resync status changes to In Progress and does not recover.
Conditions
Workaround
•
Symptom
Conditions
Workaround
•
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
Workaround
•
•
•
•
Symptom It is possible to modify bandwidth parameters on an ML card that is already part of another PTP topology.
Conditions
Workaround
•
Symptom Two RPRs are discovered when NEs are added to the CTM server for the first time.
Conditions
Workaround
•
Symptom L2 topology PTPs and RPRs are not discovered and displayed in the L2 Topology table.
Conditions
Workaround
•
Symptom The L2 service is stuck in a partially complete state in a GNE/ENE topology and the IOS Users table is missing the required entries for the ENEs.
Conditions
Workaround
•
Symptom Topologies split or become incomplete after restarting the NE service or marking NEs as Out of Service and then In Service.
Conditions
Workaround
Step 1
Step 2
SQL> select TOPOSTATUS, TOPOLOGY_NAME from l2topology_table;TOPOSTATUS TOPOLOGY_NAME--------------------------------------2 RPR A1Y22 DEMO GOB NL 4SQL> delete from l2topology_table;2 rows deleted.SQL> select TOPOSTATUS, TOPOLOGY_NAME from l2topology_table;no rows selectedSQL> commit 2;Commit completeStep 3
Alternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom Some L2 service drops are missing from the L2 Topology table.
Conditions
Workaround
•
Symptom Topologies A and B are incomplete and their circuits are exchanged.
Conditions
Workaround
•
Symptom Cannot create an L2 topology with a name that was used before and then deleted.
Conditions
Workaround
delete from L2topology_table where topology_name like '<SPECIFY THE TOPOLOGY NAME>'; commit;Alternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom An L2 topology changes to Incomplete state after NEs are marked as Out of Service and then In Service.
Conditions
Workaround
•
Symptom Some L2 topologies are not discovered.
Conditions
1.
2.
3.
Workaround
•
Symptom An RPR VCAT splits under certain conditions.
Conditions
Workaround
•
Symptom RPR creation fails for a CTM user with Provisioner privileges.
Conditions
Workaround
•
Symptom Not all PoS ports are enabled after an add/remove card operation.
Conditions
Workaround
•
Symptom Marking the NEs as Out of Service and then In Service shuts down the ML card POS ports. This affects traffic passing through the ML card. Traffic still goes through in wrap state, but does not pass through the newly added ML card.
Conditions
Workaround
•
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
A sample problem configuration is shown as follows:
class-map match-any AVVID_VOICE_VIDEOmatch cos 1 2match cos 5Workaround
•
Symptom The ML card traffic classification does not change into the newly applied QoS values.
Conditions
Workaround
•
•
•
Domain Explorer
•
Symptom After an LNE is changed to a GNE, it takes approximately 15 minutes for the DCC-connected NEs to become ENEs.
Conditions
Workaround
•
Symptom In CTM, ENEs go into LOC state when there are no remaining GNEs in a DCC ring.
Conditions
Workaround
Note
•
Symptom If you change proxy settings on an NE, the NE does not always come up.
Conditions
Workaround
•
Symptom When all the required ports are not enabled for a firewall between CTM and a GNE, the GNE fails to come up in CTM. Consequently, ENEs that are connected to this GNE also fail to come up.
Conditions
Workaround
•
Symptom An NE with one TCC card goes into LOC state if the TCC card is swapped without a synchronization.
Conditions
Workaround
•
Symptom The operational state of an ONS 155xx NE remains permanently as In Service-Initializing.
Conditions
Workaround
•
Symptom After the CTM server is restarted, unmanaged NEs have a red check mark next to them in the Domain Explorer, indicating that their configuration synchronization failed.
Conditions
Because these NEs are unmanaged, no actual configuration synchronization would ever occur. However, the config sync status for these NEs should always show success (a green check mark).
Workaround
•
Symptom CTM loses connectivity to all NEs managed by a specific CTC-based NE service. The logs show CORBA timeout errors when attempting to reconnect to the problematic NEs.
Conditions
Workaround
•
Symptom For CTC NEs in a GNE/ENE setup, if the NE is configured as an ENE and its shell access state is set to Secure, you cannot launch the CLI for ML or CE data cards on the node.
Conditions
•
•
•
This problem affects only the CLI console launch from CTM; it does not affect L2 provisioning.
Workaround
•
Symptom The Domain Explorer > NE Authentication tab is empty for ONS 15540 ESP NEs. The Username, Password, and Confirm Password values are not displayed. The same tab is shown correctly for ONS 15540 ESPx NEs.
Conditions
Workaround
•
Symptom An ENE is not discovered correctly after it is moved from another location. CTM still discovers the ENE with the old IP address and the old GNE that it is no longer attached. All settings appear to be correct in CTC launched from Internet Explorer.
Conditions
Workaround
NE Explorer
•
Symptom Setting the RIP metric to zero does not generate an error message.
Conditions
Workaround
•
Symptom The NE Explorer does not refresh the Secure Config Mode value after a mode change.
Conditions
1.
2.
3.
4.
5.
Workaround
•
Symptom Clicking the Apply button after modifying the SNMP UDP port does not save the modified value.
Conditions
Workaround
•
Symptom Cannot launch the CLI to a proxy-only, DCC-connected NE.
Conditions
Workaround
•
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
Workaround
•
Symptom Cannot set the Encap CRC value to None for ONS 15600 SONET ASAP_4 cards.
Conditions
Workaround
•
Symptom For low-order VC-3 VCAT circuits on CE-100T-8 cards, the ONS 15454 SDH NE Explorer > J1 Path Trace tab shows the circuit type incorrectly as VC.
Conditions
Workaround
•
Symptom The current bandwidth usage is not shown for G1000-2 cards in ONS 15327 NEs.
Conditions
Workaround
•
Symptom In the NE Explorer card slot properties pane for the MRC-12 card, the information in the first row disappears from the Pluggable Provisioning, Line, STS, VC-4, and Loopback tabs. The information in this row is replaced by the information for the row that was just modified, meaning there are two rows that contain the same information and information for one row is lost completely.
Conditions
Workaround
•
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
Workaround
•
Symptom When you choose NE Explorer > Configuration > Export NE Configuration, no data is exported for the NE or the cards. The file where the configuration is exported lists only tab names.
Conditions
Workaround
•
Symptom While editing section trace parameters in the NE Explorer, it is possible to enter the expected string in automatic mode.
Conditions
Workaround
•
Symptom For the ONS 15454 SDH E3 card, VC-3 threshold names are shown incorrectly as CV-V-5579, BBE-V-5579, SES-V-5579, UAS-V-5579, and so on.
Conditions
Workaround
•
Symptom In the NE Explorer XTC card slot properties pane > DS-3 tab, the Customer Info subtab is blank.
Conditions
Workaround
•
Symptom If you try to change the port rate on an MRC-12 PPM and the operation fails, no error message or warning is returned.
Conditions
Workaround
•
Symptom The default RIP summary address is not created when activating RIP from CTM.
Conditions
Workaround
•
Symptom No range address is created when enabling OSPF on a LAN from CTM.
Conditions
Workaround
•
Symptom When a 1:1 protection group is created for a DS3XM card on an ONS 15454 NE, the protection group is not visible immediately.
Conditions
Workaround
•
Symptom When a DS3XM-12 card is provisioned on an ONS 15454 NE, the card does not appear immediately in the NE Explorer window. The client window goes blank for several minutes before the card appears.
Conditions
Workaround
•
Symptom In the ONS 15600 SDH NE Explorer > Security tab, the Users, Active Logins, and Policy subtabs are missing.
Conditions
Workaround
•
Symptom In the NE Explorer for an OC192 LR card > ALS tab, a manual laser restart fails and the laser shutdown status is not displayed.
Conditions
Workaround
•
Symptom In the ONS 15454 SDH NE Explorer > DCC/GCC/OSC tab > RS-DCC subtab, OC-n is shown instead of STM-n.
Conditions
Workaround
•
Symptom Cannot edit OSI and IP parameters such as ISH, ESH, and IIH.
Conditions
Workaround
•
Symptom After changing the IP address from the NE Explorer and rebooting the NE, the IP address changes in CTC, but the CTM Domain Explorer and database still show the old IP information. The NE undergoes a loss of connectivity, and marking the NE as Out of Service and then In Service does not help.
Conditions
Workaround
Alternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom The Change Card operation fails for the ONS 15454 SONET and ONS 15454 SDH.
Conditions
1.
2.
3.
Workaround
•
Symptom After marking NEs as Out of Service and then In Service, the Customer ID and Service ID values are lost.
Conditions
Workaround
•
Symptom Cannot set OPR for Optics or Physical thresholds on MRC cards.
Conditions
Workaround
•
Symptom CTM and CTC behave differently when setting the Trace mode for MRC_12 cards.
Conditions
1.
2.
3.
4.
5.
6.
7.
8.
CTC and CTM should set the Trace mode the same way.
Workaround
•
Symptom Cannot set the Admin SSM value for MRC_12 cards.
Conditions
Workaround
•
Symptom It is possible to change the OC-n port type from SONET to SDH when Send<FF>DoNotUse is checked.
Conditions
Workaround
•
Symptom Cannot change the Flow Control Low and Flow Control High fields for a custom water mark value for G1000 cards.
Conditions
Workaround
•
Symptom Cannot change the cost value for static routes in CTM.
Symptom In the ONS 15454 NE Explorer > Network tab > Static Routes subtab, if you try to modify the cost value, CTM does not allow the change and constantly returns the message "Do you want to apply the change?" CTC allows you to edit the cost value for static routes.
Workaround
•
Symptom CTM allows you to change the facility type, but CTC does not.
Conditions
Workaround
•
Symptom Cannot set the AIS threshold in the NE Explorer > Timing tab > General subtab.
Conditions
Workaround
•
Symptom Cannot set the MS-SPRing Ext. Byte value on STM-16 line cards.
Conditions
Workaround
•
Symptom CTM shows far-end electrical path thresholds for E1-42 cards.
Conditions
Workaround
•
Symptom In the node-level NE Explorer > Network tab > SNMP subtab, the Use Generic MIB check box is missing.
Conditions
Workaround
Performance Monitoring
•
Symptom A query for ONS 15310 STS path PM data for a specific port type shows all port types in the results.
Conditions
Workaround
•
Symptom When the PM service is restarted, the error message "Cannot collect PM on <NE_name>" is logged in the error log during the first PM collection interval.
Conditions
Workaround
•
Symptom Cannot collect valid real-time PM data for ML1000-2 cards on release 4.6.x NEs.
Conditions
Workaround
•
Symptom Cannot collect high-order path real-time PM data at the near or far end for CTX, DS-1, DS1_E1_56, DS3I, and XTC cards.
Conditions
•
•
•
Workaround
•
Symptom The VC3 number is shown incorrectly in the Interface Type column of the Low Order VC3 PM table.
Conditions
Workaround
•
Symptom Some real-time PM tables for MRC-12 cards show the interface name as FAC instead of OC-n or STM-n.
Conditions
•
•
•
•
Workaround
•
Symptom Data for unsupported DS-1 far-end PM parameters is displayed inconsistently.
Conditions
Workaround
•
Symptom The real-time Physical PM table for ONS 15310 NEs shows data for EC-1 ports.
Conditions
Workaround
•
Symptom The DS1 PM table for DS3XM-12 cards contains CV-L, ES-L, SES-L, and LOSS-L parameters.
Conditions
Workaround
•
Symptom When you click OK in the Graph Parameters Selection dialog box, the selected parameters are not graphed correctly.
Conditions
1.
2.
3.
The graph shows only one parameter; two parameters are missing.
Workaround
•
Symptom After a normalization operation on a PM graph, the maximum value of the Y axis is not displayed.
Conditions
Workaround
•
Symptom When you launch the DS-1 PM table for an ONS 15310 NE, the FC-P (Tx) parameter is missing.
Conditions
Workaround
•
Symptom CTM does not report PM values at time 00:00 for an ONS 1580x card.
Conditions
Workaround
•
Symptom Cannot collect valid real-time Storage Area Network (SAN) PM data for NEs earlier than release 5.0.
Conditions
Workaround
•
Symptom The real-time CoS PM table shows all values as Not Available.
Conditions
Workaround
•
Symptom When the near-end DS1 PM table is launched for a DS1_E1_56 or DS3XM-12 card, the PM parameters ESNE-NP, SESNE-NP, and UASNE-NP are not displayed.
Conditions
Workaround
•
Symptom During the launch of a real-time PM table for an ONS 15600 SONET or ONS 15600 SDH NE, modules that are not actually present in the selected slots are shown as selectable options.
Conditions
Workaround
•
Symptom Cannot collect real-time PM data for GFP statistics on ONS 15454 SONET DM_2.5G and DMP_2.5G cards.
Conditions
Workaround
•
Symptom If you launch the real-time 8B10B PM table for all ports, the Invalid Ordered Sets counter is missing on 2.5G_DM and 2.5G_DMP cards.
Conditions
Workaround
•
Symptom If you choose Performance > PM Query by Category and launch the 1-day Ethernet PM table for an ONS 15454 SONET or ONS 15454 SDH with Ethernet cards, CTM displays the 15-minute Ethernet PM table.
Conditions
Workaround
•
Symptom After creating a DCC with OSI support, the corresponding OSI subnet is shown incorrectly as Port 0 or is empty.
Conditions
Workaround
•
Symptom PM data collection fails and the Alarm Browser reports Lost 15-minute/1-day PM alarms. The Error Log contains "HTTP Server too busy" or "HTTP Error: 401" messages for the NE.
Conditions
-> tickGetvalue = -332642796 = 0xec2c4614 ...If the first value in the tickGet command output is negative, the NE has exceeded the 414 day threshold and CTM cannot collect PM data from the NE.
Workaround
•
Symptom CTM shows invalid or incorrect values for some 15-minute performance data parameters for ML/Ethernet cards.
Conditions
Workaround
•
Symptom PM collection fails for ONS 1580x NEs.
Conditions
Workaround
•
Symptom PM data collection takes longer than 15 minutes, resulting in high CPU usage.
Conditions
Workaround
•
Symptom TCAs are shown one hour late in PM tables when the NE switches automatically from daylight saving time to standard time.
Conditions
Workaround
•
Symptom For nodes equipped with PPM-provisioned transponder and muxponder cards, the reported Average Transmit Power value is incorrect.
Conditions
Workaround
Network Map
•
Symptom Cannot configure default layouts in the Network Map as expected.
Conditions
Workaround
Control Panel
•
Symptom Cannot restart the NE service after stopping it from a service instance node.
Conditions
Workaround
•
Symptom When you stop an NE service in the Control Panel, there is no confirmation dialog box to prompt you before stopping the service immediately.
Conditions
Workaround
•
Symptom Stopping the CTMTL1FWDService process from the Control Panel does not stop it on the server.
Conditions
Workaround
•
Symptom In the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area, the Max Retries value does not work correctly.
Conditions
Maximum number of unlock attempts exceeded. Application will be shut down.Workaround
•
Symptom The "Maximum login attempts exceeded" alarm is not cleared after unchecking the Infinite check box in the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area.
Conditions
Workaround
•
Symptom The TCA_EVENT_TABLE is not pruned and grows to millions of rows. The huge number of rows causes high CPU usage and performance degradation.
Conditions
Workaround
Miscellaneous
•
Symptom The dashboard comes to the front when the Solaris desktop is locked.
Conditions
Workaround
•
Symptom The Equipment Inventory table shows TCC2P as TCC2.
Conditions
Workaround
•
Symptom CTM shows a blank password.
Conditions
Workaround
•
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
Workaround
•
Symptom ONS 1580x TL1 user passwords are logged in clear on the CTM server.
Conditions
Workaround
•
Symptom The CTM client hangs while opening the Network Map and NE Explorer windows.
Conditions
Workaround
•
Symptom Using the Statistics Report tool for MGX devices, the Raw Data Report shows the wrong calendar date. For example, the Raw Data Report shows August 25, 2005 as a Friday instead of a Thursday.
Conditions
Workaround
•
Symptom The Alarm Browser and Alarm Log do not display DBOSYNC alarms from ONS 15600 R1.13 NEs.
Conditions
Workaround
INSERT INTO ALARM_EVENT_TYPE_ENUM_TABLE VALUES (17214, `Standby Database Out of Sync', `DBOSYNC', `UNIDENTIFIED', 1);commit;Alternately, install the CTM R6.0.0.414.2 patch. See Installing the CTM R6.0.0.414.2 Patch.
•
Symptom Out of Service/In Service operations and scheduled configuration resynchronizations on an NE do not synchronize the inventory table for the NE.
Conditions
Workaround
Step 1
Step 2
Step 3
Note
Step 4
•
Symptom Client login takes a long time.
Conditions
Workaround
•
Symptom Need to enhance CTM debug tools to show NE information from the NEService cache.
Conditions
Workaround
•
Symptom CTM Solaris hangs when doing regular operations in the CTM GUI.
Conditions
Workaround
•
Symptom It is possible to retrieve the NE backup memory from CTM and save it to the CTM client machine. However, CTM reports the retrieval and saving of the memory as successful even when the file saving to the client machine failed.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom The Error Log shows a major error with the following message:
Finding NE IP Add in NE Info Table: VALUEGNECONNECTEDConditions
Workaround
•
Symptom After upgrading an NE release from 5.0.x to 6.0, CTM does not clean up the original port connection to the NE.
Conditions
Workaround
•
Symptom The CTM client exits if you enter the wrong login password in the CTM Locked dialog box.
Conditions
Workaround
•
Symptom
Guest
