Table Of Contents
Release Notes for Cisco Transport Manager Release 8.5
New Features and Functionality
Sections and Caveats Modified or 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
Installing the CTM R8.5.0.390.3 Patch
Determining What CTM Patch Is Currently Installed in the CTM System
Backing Up the CTM Database Before Installing the CTM R8.5.0.390.3 Patch
Downloading the CTM R8.5.0.390.3 Patch
Installing the CTM R8.5.0.390.3 Server Patch on the Same or Separate Workstation(s)
Installing the CTM R8.5.0.390.3 Client Patch in Windows
Installing the CTM R8.5.0.390.3 Client Patch in Solaris
Upgrading to CTM R9.0 Using a Service Pack
Installation and Upgrade Caveats
CTM Server and Database Caveats
Cisco Transport Controller Caveats
Cisco ONS 15302 and Cisco ONS 15305
Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET
Cisco ONS 15600 SONET and Cisco ONS 15600 SDH
Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Transport Manager Release 8.5
November 4, 2009
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
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.
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":
•
–
–
–
–
–
–
–
–
–
–
–
–
–
•
Note
–
–
–
–
–
Note
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Sections and Caveats Added
The following sections and caveats were added to the release notes:
•
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
Sections and Caveats Modified or Removed
The following sections were removed, because the CTM R8.5.0.390.3 patch inherits all bug fixes and obsoletes these earlier patches:
•
•
•
•
•
•
•
•
•
The following caveat was moved from the Resolved Caveats table to the Open Caveats section:
CTM-Supported NE Software Releases
The following table lists the NE software releases supported in CTM R8.5.
Caution
Table 2 CTM-Supported NE Software Releases
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
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.76
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.17
08.51-008B-14.13
Release 8.5.38
08.53-008J-17.07
Release 8.69
08.60-009B-11.08
ONS 15327
Release 4.1.310
04.13-003L-19.01
Release 4.1.4
04.14-004C-09.23
Release 4.1.611
04.16-004I-10.23
Release 4.1.82
04.182-006-L2805
Release 4.6.212
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.713
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.314
04.13-003L-19.01
Release 4.6.215
04.62-004E-23.20
Release 5.0.416
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.717
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.118
08.51-008B-14.13
Release 8.5.219
08.52-008E-25.04
Release 8.5.320
08.53-008J-17.07
Release 8.6
08.60-009B-11.0821
ONS 15454 SONET
Release 4.1.322
04.13-003L-19.01
Release 4.1.4
04.14-004C-09.23
Release 4.1.623
04.16-004I-10.23
Release 4.1.82
04.182-006-L2805
Release 4.6.224
04.62-004E-23.20
Release 4.7 (MSTP only)
04.70-004I-14.01
Release 5.0.425
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.726
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.127
08.51-008B-14.13
Release 8.5.228
08.52-008E-25.04
Release 8.5.3 29
08.53-008J-17.07
Release 8.6
08.60-009B-11.0830
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
01.30-004D-01.20
Release 5.0.431
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.3032
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
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
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.0033
5.4.00
1 In order for CTM to support the ONS 15305 R2.0.2, you must add the software version to the Supported NE table. See Adding the ONS 15305 R2.0.2 to the Supported NE Table.
2 In order for CTM to support the ONS 15305 CTC R3.0.6, you must install the Installing the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
3 In order for CTM to support the ONS 15310 CL R5.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R5.0.4 to the Supported NE Table.
4 In order for CTM to support the ONS 15310 CL R8.5.1, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R8.5.1 to the Supported NE Table.
5 In order for CTM to support the ONS 15310 CL R8.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
6 In order for CTM to support the ONS 15310 MA R7.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.0.7 to the Supported NE Table.
7 In order for CTM to support the ONS 15310 MA R8.5.1, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R8.5.1 to the Supported NE Table.
8 In order for CTM to support the ONS 15310 MA R8.5.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R8.5.3 to the Supported NE Table.
9 In order for CTM to support the ONS 15310 MA R8.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
10 In order for CTM to support the ONS 15327 R4.1.3, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
11 In order for CTM to support the ONS 15327 R4.1.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
12 In order for CTM to support the ONS 15327 R4.6.2, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
13 In order for CTM to support the ONS 15327 R7.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.0.7 to the Supported NE Table.
14 In order for CTM to support the ONS 15454 SDH R4.1.3, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
15 In order for CTM to support the ONS 15454 SDH R4.6.2, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
16 In order for CTM to support the ONS 15454 SDH R5.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R5.0.4 to the Supported NE Table.
17 In order for CTM to support the ONS 15454 SDH R7.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.0.7 to the Supported NE Table.
18 In order for CTM to support the ONS 15454 SDH R8.5.1, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R8.5.1 to the Supported NE Table.
19 In order for CTM to support the ONS 15454 SDH R8.5.2, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R8.5.2 to the Supported NE Table.
20 In order for CTM to support the ONS 15454 SDH R8.5.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R8.5.3 to the Supported NE Table.
21 In order for CTM to support the ONS 15454 SDH R8.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
22 In order for CTM to support the ONS 15454 SONET R4.1.3, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
23 In order for CTM to support the ONS 15454 SONET R4.1.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
24 In order for CTM to support the ONS 15454 SONET R4.6.2, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
25 In order for CTM to support the ONS 15454 SONET R5.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R5.0.4 to the Supported NE Table.
26 In order for CTM to support the ONS 15454 SONET R7.0.7, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.0.7 to the Supported NE Table.
27 In order for CTM to support the ONS 15454 SONET R8.5.1, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R8.5.1 to the Supported NE Table.
28 In order for CTM to support the ONS 15454 SONET R8.5.2, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R8.5.2 to the Supported NE Table.
29 In order for CTM to support the ONS 15454 SONET R8.5.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R8.5.3 to the Supported NE Table.
30 In order for CTM to support the ONS 15454 SONET R8.6, you must install the CTM R8.5.0.390.3 patch. See Installing the CTM R8.5.0.390.3 Patch.
31 In order for CTM to support the ONS 15600 SONET R5.0.4, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R8.5.3 to the Supported NE Table.
32 In order for CTM to support the MGX Voice Gateway R5.3.30, you must add the software version to the Supported NE table. See Adding the MGX Voice Gateway R5.3.30 to the Supported NE Table.
33 VQM is supported in VXSM R5.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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
Step 2
Step 3
Step 4
Step 5
Step 6
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
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.
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
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.
(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
Step 2
# ctms-stopStep 3
Step 4
# cd /tmp# unzip CTM85_JRE_UPGRADE_1_5.zipThis creates a new directory called JRE.
Step 5
# cd JREStep 6
Step 7
Step 8
Caution
Step 9
# cp jre-1_5_0_16-solaris-sparc.sh /tmp/JRE# chmod +x jre-1_5_0_16-solaris-sparc.shStep 10
# ./installNewJre.sh jre-1_5_0_16-solaris-sparc.shStep 11
# Do you agree to the above license terms? [yes or no]Step 12
# cd /opt/CiscoTransportManagerServer/bin# grep jre ctms-startIn 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:$CLASSPATHAlso, the following listings should point to the new JRE path:
ls -ltra /usr/bin/javals -ltra /usr/bin/javanels -ltra /usr/bin/javapmls -ltra /usr/bin/javaorbls -ltra /usr/bin/javacorbagwls -ltra /usr/bin/ctmsjavaStep 13
# ctms-start
Upgrading the CTM R8.5 Solaris Client to JRE Version 1.5.0_16
Step 1
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.
b.
c.
# cd /tmp# unzip CTM85_JRE_UPGRADE_1_5.zipThis creates a new directory called JRE.
d.
# cd JREe.
f.
g.
h.
# cp jre-1_5_0_16-solaris-sparc.sh /tmp/JRE# chmod +x jre-1_5_0_16-solaris-sparc.shi.
# ./installNewJre.sh jre-1_5_0_16-solaris-sparc.shj.
# Do you agree to the above license terms? [yes or no]Step 2
# cd /opt/CiscoTransportManagerClientStep 3
# jre/bin/java -versionIn the output, you should see:
java version "1.5.0_16"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
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
# cd C:\Cisco\TransportManagerClient8_5\jre\binStep 8
# java -versionIn the output, you should see:
java version "1.5.0_16"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
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
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
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:
•
•
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.
2.
3.
4.
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
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
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
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
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
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
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
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
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
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
CSCsl34530
The network topology is not updated in CTM.
Note
CSCsl37264
The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
Note
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
CSCsl48499
The backup files are not listed in the Backup File dialog box after choosing Administration > Memory Backup Upload in the Domain Explorer.
Note
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
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
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
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
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
CSCsm84722
Cannot install CTM patches in a dual-server setup.
Note
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
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
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
CSCso00769
Unable to delete or modify drops or VLANs that are associated with custom QoS profiles.
Note
CSCso01840
It takes a long time to discover NEs after the NE service restarts.
Note
CSCso01900
The CTC-based NE service takes a long time to reconnect and discover NEs.
Note
CSCso01942
CTM takes a long time to discover a large network of GNEs and ENEs.
Note
CSCso35202
The Oracle shutdown script does not work while the server workstation is shutting down.
Note
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
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
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
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
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
CSCsq11152
Due to security issues, CTM must support a new JRE version.
Note
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
CSCsq26342
The getHistoryPMData API takes longer than 15 minutes to return data.
Note
CSCsq26362
The output file generated from getHistoryPMData returns duplicate rows.
Note
CSCsq31631
Memory backup and memory restore fail on MGX nodes when Telnet is disabled.
Note
CSCsq32073
Due to security issues, CTM must support Apache web server version 2.0.63.
Note
CSCsq65111
In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.
Note
CSCsq67942
The NE User Access Administration table and Modify NE User wizard show different values for the same fields.
Note
CSCsq80551
CTM must add support for ONS 15305 R3.0.6 NEs.
Note
CSCsq87850
SVLAN ports are not displayed correctly.
Note
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
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
CSCsq94272
You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.
Note
CSCsq96596
In the NE Explorer for a GE_XP card, the SVLAN tab does not work correctly.
Note
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
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
CSCsr16489
CTM must add support for release 4.1.3 NEs.
Note
CSCsr30785
The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
Note
CSCsr44800
CTM must add support for release 4.1.6 NEs.
Note
CSCsr53609
A CTM server core dump file is created when the CTM server shuts down.
Note
CSCsr60497
When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
Note
CSCsr61773
CTM must add support for release 4.6.2 NEs.
Note
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
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
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
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
CSCsr91285
CTC cross-launch fails when multiple software versions are present.
Note
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
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
CSCsu18321
The Circuit Repair window does not automatically close when the repair operation is finished.
Note
CSCsu22851
A memory leak occurs on the CTM server because of zombie lightweight process (LWP) creation.
Note
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
CSCsu50742
The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.
Note
CSCsu56857
The Circuit table loses values for the following fields: Customer ID, Service ID, and Description.
Note
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
CSCsu66316
Cannot launch CTC from CTM for an ONS 15454 MSTP R8.5.2 node.
Note
CSCsu67460
Even though automatic alarm acknowledgement is enabled, cleared alarms do not move from the Alarm Browser to the Alarm Log.
Note
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
CSCsu86435
Occasionally, Cisco Edge Craft does not launch from CTM.
Note
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
CSCsu88903
The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
Note
CSCsu90020
Manual circuit routing through a server trail fails.
Note
CSCsu90217
Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
Note
CSCsu90286
Circuit routing through a server trail fails.
Note
CSCsv04954
When logging into the CTM client, the login fails.
Note
CSCsv07073
The Circuit table loses values for the following fields: Circuit Alias Name, Note, Customer ID, Service ID, and Description.
Note
CSCsv07090
The Circuit table loses additional values after marking a node as Out of Service/In Service and restarting the NE service.
Note
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
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
CSCsv12810
An MGX node is added to the CTM server, but is not included in the Auto Backup process.
Note
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
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
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
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
CSCsv70799
CTM and CTC show different values for LBC and OPT parameters on MRC-25G-4 cards.
Note
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
CSCsv81066
The NE service freezes after discovering a large NE network.
Note
CSCsw43520
A memory leak occurs on the CTM server because of zombie LWP creation during startup.
Note
CSCsw73743
The getAllCrossConnections API returns an error if the node does not contain circuits.
Note
CSCsw88114
In a filter dialog box, the User Specified radio button allows only 2009 to 2018 as the year.
Note
CSCsw91974
In a large network of GNEs and ENEs, CTM fails to collect PM data.
Note
CSCsw91994
The CTM database contains unusable indexes, which means that PM tables and audit logs contain no data.
Note
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
CSCsx22431
CTM and CTC show different wavelength calculations for OCHNC circuits.
Note
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
CSCsx50126
Due to security issues, CTM must support Apache web server version 2.2.11.
Note
CSCsx50161
Due to security issues, Apache Tomcat must be disabled.
Note
CSCsx56687
The SPAN_BS_TABLE database table displays incorrect working and protected values.
Note
CSCsx81985
Archive log pruning degrades as database usage increases, and the /db05 directory fills up.
Note
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
CSCsy23134
CTM must add support for ONS 15310 CL, ONS 15310 MA, ONS 15454 SONET, and ONS 15454 SDH R8.6 NEs.
Note
CSCuk55231
TCAs are shown one hour late in PM tables when the NE switches automatically from Daylight Saving Time to standard time.
CSCsz63889
Sometimes 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
CSCsz83568
•
[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.NullPointerExceptionNote
CSCta69923
Cleared alarms are not removed from the Alarm Browser.
Note
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
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
CSCtb21147
CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.
Note
CSCtb34284
The core_pmon.sh script that checks the status of critical CTM processes runs every 30 seconds instead of every 5 minutes.
Note
Installing the CTM R8.5.0.390.3 Patch
Note
The CTM R8.5.0.390.3 patch is installed like a regular CTM patch.
This section describes how to download and install the CTM R8.5.0.390.3 patch, which contains new fixes for the following caveats:
Note
•
•
•
•
[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•
•
EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too many open files.•
•
•
Note
This patch also inherits fixes of all earlier CTM R8.5 patches for the following caveats:
Fixed in the CTM R8.5.0.387.6 service pack:
•
•
•
•
•
•
•
•
•
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•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed in previous CTM 8.5 patches:
•
•
•
•
•
•
•
•
EID-932: Failed to route the circuit. Details: client timeout reached.•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
EID-382: The CTM server is initializing. Please try again after some time.•
•
•
•
•
•
(Too many open files)(No such file or directory)•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing object•
•
•
•
•
•
Executing pre requisite sql fixes for 361 patch5589 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.•
•
•
•
•
•
CTM R8.5.0.390.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, or R8.5.0.387.6.
Note
•
Complete the following procedures to upgrade to the CTM R8.5.0.390.3 patch.
Determining What CTM Patch Is Currently Installed in the CTM System
To check your current CTM release and patch level, log into the CTM server as the root user and enter the following command:
showctmThe first line of the output gives you the release and patch level. Before proceeding, verify that the output results to one of the following:
•
•
•
•
•
•
•
•
•
•
Backing Up the CTM Database Before Installing the CTM R8.5.0.390.3 Patch
Before installing the CTM R8.5.0.390.3 patch, it is strongly recommended that you back up the existing database. To back up the CTM database, refer to the following sections in Chapter 4 of the Cisco Transport Manager Release 8.5 User Guide:
•
•
Downloading the CTM R8.5.0.390.3 Patch
Step 1
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
cd /<directory_name>unzip CTM8.5.0.390.3.patch.zipFor example, to extract the file to the /temp directory, enter:
cd /tempunzip CTM8.5.0.390.3.patch.zipThis creates a directory called 390, which contains all of the patch-related files.
Step 11
cd 390Step 12
a.
b.
c.
d.
e.
Installing the CTM R8.5.0.390.3 Server Patch on the Same or Separate Workstation(s)
Step 1
a.
rsh <IP_address_of_CTM_server> lsb.
# cat >> /.rhosts << EOF<database_workstation_name> rootEOFwhere <database_workstation_name> is the hostname of the CTM database workstation.
Step 2
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 3
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 verify that all user sessions are terminated.
Step 4
ctms-stopStep 5
./server_patch.sh
Note
Step 6
ctms-startStep 7
showctmYou should see the following version string in the first line of output for the preceding command:
Cisco Transport Manager Server Version: 8.5 Build: 390 Patches: 3Step 8
Installing the CTM R8.5.0.390.3 Client Patch in Windows
Note
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
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: 8.5 Build: 390 (client configuration size)•
8.5 [8.5.0.390]Step 5
Installing the CTM R8.5.0.390.3 Client Patch in Solaris
Note
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
Step 2
./client_patch.shStep 3
ctmc-startStep 4
•
Client: 8.5 Build: 390 (client configuration size)•
8.5 [8.5.0.390]Step 5
Upgrading to CTM R9.0 Using a Service Pack
Complete the following steps when upgrading to CTM R9.0:
Step 1
Step 2
Open Caveats
The following sections describe the caveats that are not resolved in the CTM R8.5 software:
•
•
•
Note
Installation and Upgrade Caveats
•
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/InstallThis 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
•
You pressed Cancel/Upgrade/InstallSQL*Plus: Release 9.2.0.7.0 - Production on Mon Apr 30 15:54:35 2007Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.Connected to:Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production With thePartitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.7.0 -ProductionSQL> SQL> 2'NEWDBVERSION'||ACTIVEVALUE--------------------------------------------------------------------------------newdbversion 8.0SQL> SQL> Disconnected from Oracle9i Enterprise Edition ReleaseSQL> SQL> 9.2.0.7.0 - 64bit ProductionWith 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 withUpgrade•
You pressed Cancel/Upgrade/InstallSQL*Plus: Release 9.2.0.7.0 - Production on Tue May 29 13:44:51 2007Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.ERROR ORA-12545 : connection failed because target host does not exists.SP2-0306: Invalid OptionSP2-0157: unable to connect to Oraclegrep: can't open /temp/newdbversion.lstThe Database version retrieved isThe user has clicked CancelWorkaround
•
Symptom Due to security issues, CTM must support Apache web server version 2.0.61.
Conditions
Workaround
•
Symptom The CTM client shows the wrong installation status of CTM GateWay/CORBA.
Conditions
Workaround
•
Symptom Oracle startup fails due to lack of memory after a dual-server installation. The following message appears:
SQL> ORA-27102: out of memorySVR4 Error: 22: Invalid argumentConditions
Workaround
•
Symptom Unable to determine the status of the database when the migration or export operation fails.
Conditions
Workaround
•
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.oraORA-27102: out of memorySVR4 Error: 22: Invalid argumentConditions
prctl -n project.max-shm-memory -i project user.rootproject: 1: user.rootNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memoryprivileged 4.00GB - deny -system 16.0EB max deny -Workaround
•
Symptom Unable to view server trails in CTM.
Conditions
Workaround
ALTER TABLE LINK_TABLE MODIFY STNODEID NUMBER(10);ALTER TABLE LINK_TABLE MODIFY STUNIQUEID NUMBER(10);•
Symptom Cannot install CTM patches in a dual-server setup.
Conditions
Workaround
•
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
Workaround
•
Symptom The /oracle partition grows indefinitely until it reaches 100 percent of storage, and CTM crashes.
Conditions
Workaround
Step 1
Step 2
#log_archive_dest = /db05/CTM/CTM#log_archive_format = %t_%s_%r.arcStep 3
•
Symptom After upgrading to CTM R8.5 from an earlier CTM release, the database contains invalid objects.
Conditions
Workaround
select object_name from dba_objects where status='INVALID';Then, enter the following SQL commands to remove the invalid views:
su - oraclesqlplus ctmanager/ctm123!drop view <view_name>exitexit•
Symptom Due to security issues, CTM must support a new JRE version.
Conditions
Workaround
•
Symptom Due to security issues, CTM must support Apache web server version 2.0.63.
Conditions
Workaround
•
Symptom CTM R8.5 does not start.
Conditions
Exception in thread "main" java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PasswordFinderat com.cisco.stardm.platform.Decrypt.main(Decrypt.java:65)Error in add_log_parts.shAdd log partition error: Please Check if ORACLE is installed and CTM DB is running**Abort** ctms-startThe 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
•
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/PasswordFinderat com.cisco.stardm.platform.Decrypt.main(Decrypt.java:65)Conditions
•
•
•
Workaround
•
Symptom An error message is returned when you install additional patches after installing the Oracle 10.2.0.3 patch.
Conditions
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
Workaround
•
•
Step 1
Step 2
Step 3
Step 4
•
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 objectConditions
Workaround
•
Symptom The following SQL errors are generated during patch installation:
Executing pre requisite sql fixes for 361 patch5589 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.Conditions
Workaround
•
Symptom The CTM R8.5.0.378.3 patch fails to install in a dual-server configuration.
Conditions
Workaround
•
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
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
•
Symptom Due to security issues, CTM must support Apache web server version 2.2.11.
Conditions
Workaround
•
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
Workaround
This procedure applies only to small CTM configurations that:
•
•
•
•
Step 1
#prtdiag -v | grep -i memoryStep 2
Downloading the CTM R8.5.0.240 Patch
Step 1
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
cd /<directory_name>unzip CTM8.5.0.240.patch.zipFor example, to extract the file to the /temp directory, enter:
cd /tempunzip CTM8.5.0.240.patch.zipThis creates a directory called 240, which contains all of the patch-related files.
Step 11
cd 240Applying the Patch and Installing CTM R8.5
Step 1
Step 2
a.
b.
c.
•
•
d.
Step 3
#cd ./T2_small_install#ls -l *.sh#chmod +x *.shStep 4
Caution
Step 5
#cd /T2_small_install#./fix_installation.shAfter 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
# ./fix_installation.shUsage: ./fix_installation.sh <CTM_version(8.5)> <SID>
Example:
./fix_installation.sh 8.5 CTMStep 6
Please PRESS INSTALL NOW on Pre-Installation Summary screenStep 7
The script runs during the CTM installation and continuously prints the following output until the fix is complete:
Script ./fix_installation.sh is running ...Once complete, the script exits with the following messages:
___ PFILE has been created___ Modifying pfile ...___ <SID> pfile has been modified.Script ./fix_installation.sh has completed successfully•
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
Workaround
•
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
Workaround
•
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
# prtdiag -v | grep MemoryWorkaround
•
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
Workaround
•
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
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
•
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
Workaround
cd /optrm -r CiscoTransportManagerServerrm CiscoTransportManagerServer8.5ln -s CiscoTransportManagerServer-old-<timestamp> CiscoTransportManagerServerrm CiscoTransportManagerServer.oldCTM•
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
1.
2.
3.
4.
Workaround
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 CTM and CTC do not show the actual equipment type for G1K-4 and TCC2 cards.
Conditions
Workaround
•
Symptom A mismatch alarm is raised incorrectly in CTC and CTM.
Conditions
Workaround
•
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
Workaround
•
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
Workaround
•
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
Workaround
•
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
Workaround
•
Symptom The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM cards in the network.
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 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
Workaround
•
Symptom Cleared alarms are not removed from the Alarm Browser.
Conditions
Workaround
•
Symptom CTM manages incorrectly DS1 alarms that originate on VT circuits on DS3XM_12 cards. CTM fails to report major DS1 alarms.
Conditions
Workaround
•
Symptom Continuous 15-minute and 1-day PM lost bucket alarms occur for a node and do not clear.
Conditions
Workaround
Circuit and Link Management
•
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 The J1 path trace displays expected and received bytes at the source end for unidirectional circuits.
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 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 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 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
Workaround
•
Note
•
•
•
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
Workaround
•
•
•
Symptom International characters can be entered in fields that do not support them.
Conditions
Workaround
•
Symptom Server trails cannot be created for any port other than port 1 of an E1 card. An "Invalid Preferences" error appears.
Conditions
Workaround
•
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
Workaround
•
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
Workaround
•
•
•
Symptom The ONS 155xx Circuit table does not show circuit information for circuits whose names are modified using CTM.
Conditions
Workaround
•
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
Workaround
•
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
Workaround
•
Symptom The number of TL1 circuits in the Circuit table increases after marking NEs as Out of Service and then In Service.
Conditions
Workaround
su - oraclesqlplus ctmanager/ctm123!SQL> delete circuit_bs_tbl where cktstate=12;SQL> commit;•
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
Workaround
•
Symptom Manual link creation fails.
Conditions
Workaround
•
Symptom The VC3 value is zero in the Link Utilization table for VC3 port group circuits.
Conditions
Workaround
•
Symptom The Circuit table does not contain the expected circuits.
Conditions
Workaround
•
Symptom Creating an L1 circuit fails and the following message appears: "EID-932: Failed to route the circuit. Details: client timeout reached."
Conditions
Workaround
•
Symptom The following error message appears: "The selected NEs do not support bidirectional circuit creation."
Conditions
Workaround
•
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
Workaround
•
Symptom Updated link cost and shared risk link group (SRLG) values are not available after migration.
Conditions
Workaround
•
Symptom CTM GateWay/CORBA can retrieve Ethernet circuits using the CTP naming convention.
Conditions
Workaround
•
Symptom Unable to create circuits on optical nodes that belong to the default Network Partition 1.
Conditions
Workaround
•
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
Workaround
•
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
Workaround
•
Symptom If you use textual routing to provision protected contiguous concatenation (CCAT) circuits, the operation might fail.
Conditions
Workaround
Step 1
Step 2
Step 3
•
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
Workaround
•
Symptom Duplicate circuit names appear in CTM when a circuit name is updated in CTC.
Conditions
Workaround
•
Symptom When provisioning a circuit manually between ONS 15454 NEs, the map view displays blank nodes.
Conditions
Workaround
•
Symptom The Circuit Repair window does not automatically close when the repair operation is finished.
Conditions
Workaround
•
Symptom The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.
Conditions
Workaround
•
Symptom When creating multiple STS circuits, an error is returned.
Conditions
Workaround
•
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
Workaround
To enable duplicate IP address detection at the NE service level:
Step 1
Step 2
Step 3
-Dctm.duplicated-ip-detection=duplicated-ip-detection-disabled \Step 4
•
-Dctm.duplicated-ip-detection=duplicated-ip-detection-enabled \•
-Dctm.duplicated-ip-detection=duplicated-ip-detection-enabled \Step 5
Step 6
To enable duplicate IP address detection at the CTM service level:
Step 1
Step 2
Step 3
-Dctm.sms.dupIpPoller.Enabled=false \Step 4
•
-Dctm.sms.dupIpPoller.Enabled=true \•
-Dctm.sms.dupIpPoller.Enabled=true \Step 5
-Dctm.sms.dupIpPoller.Interval.hours=<number_of_hours> \Step 6
-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
-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
-Dctm.sms.dupIpPoller.Enable.NodeName=true \Step 9
Step 10
If the duplicate IP address problems persist, contact your Cisco account representative for recovery procedures.
•
Symptom Manual circuit routing through a server trail fails.
Conditions
Workaround
•
Symptom Circuit routing through a server trail fails.
Conditions
Workaround
•
Symptom The Circuit table loses values for the following fields:
•
•
•
•
•
Conditions
Workaround
•
Symptom The Circuit table loses additional values after marking a node as Out of Service/In Service and restarting the NE service.
Conditions
Workaround
•
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
Workaround
•
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
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 If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
Conditions
Workaround
•
Symptom In CTM, if you create a circuit that uses a server trail link, the circuit is discovered as Partial in CTC.
Conditions
Workaround
•
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
Workaround
•
Symptom Circuits remain in the CTM database with a CktState value equal to 12.
Conditions
•
•
Workaround
•
Symptom The Circuit wizard returns an error message regarding an invalid circuit state, and a VCAT circuit changes to Partial.
Conditions
Workaround
•
Symptom The SPAN_BS_TABLE database table displays incorrect working and protected values.
Conditions
Workaround
•
Symptom In the Create Circuit wizard, tunnel links are not available for VT circuit routing.
Conditions
Workaround
•
Symptom Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
Conditions
Workaround
•
Symptom Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.
<
Guest
