Table Of Contents
Release Notes for Cisco Transport Manager Release 8.0
New Features and Functionality
CTM-Supported NE Software Releases
Adding the ONS 15310 CL R6.0.3 to the Supported NE Table
Adding the ONS 15310 CL R7.0.5 to the Supported NE Table
Adding the ONS 15310 CL R7.2.2 to the Supported NE Table
Adding the ONS 15310 CL R7.2.3 to the Supported NE Table
Adding the ONS 15310 MA R7.0.5 to the Supported NE Table
Adding the ONS 15310 MA R7.0.7 to the Supported NE Table
Adding the ONS 15310 MA R7.2.2 to the Supported NE Table
Adding the ONS 15310 MA R7.2.3 to the Supported NE Table
Adding the ONS 15327 R6.0.3 to the Supported NE Table
Adding the ONS 15327 R7.0.5 to the Supported NE Table
Adding the ONS 15327 R7.0.7 to the Supported NE Table
Adding the ONS 15327 R7.2.2 to the Supported NE Table
Adding the ONS 15327 R7.2.3 to the Supported NE Table
Adding the ONS 15454 SDH R6.0.3 to the Supported NE Table
Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table
Adding the ONS 15454 SDH R7.0.7 to the Supported NE Table
Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table
Adding the ONS 15454 SONET R6.0.3 to the Supported NE Table
Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table
Adding the ONS 15454 SONET R7.0.7 to the Supported NE Table
Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table
Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table
Adding the ONS 15600 SONET R7.2.3 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_15
Upgrading the CTM R8.0 Server to JRE Version 1.5.0_15
Upgrading the CTM R8.0 Solaris Client to JRE Version 1.5.0_15
Upgrading the CTM R8.0 Windows Client to JRE Version 1.5.0_15
Installing the CTM R8.0.0.912.1 Patch
Determining What CTM Patch Is Currently Installed in the CTM System
Backing Up the CTM Database Before Installing the CTM R8.0.0.912.1 Patch
Downloading the CTM R8.0.0.912.1 Patch
Installing the CTM R8.0.0.912.1 Server Patch on the Same or Separate Workstation(s)
Installing the CTM R8.0.0.912.1 Client Patch in Windows
Installing the CTM R8.0.0.912.1 Client Patch in Solaris
Installation and Upgrade 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 15501, Cisco ONS 15530, and Cisco ONS 15540
Cisco ONS 15600 SONET and Cisco ONS 15600 SDH
Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808
Cisco CRS-1 and Cisco XR 12000
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Transport Manager Release 8.0
September 18, 2009
These release notes describe the caveats for Cisco Transport Manager (CTM) Release 8.0. These release notes accompany the Cisco Transport Manager Release 8.0 User Guide and the Cisco Transport Manager Release 8.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), routers, 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.0, CTM supports the Cisco 7600 Series Edge Router (Cisco 7600); the Cisco Optical Networking System (ONS) family of optical NEs; 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.
Note
New Features and Functionality
The following table describes the new features and functionality in CTM R8.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 8.0.
NE Software Releases Added
The following NE releases were added to Table 2, "CTM Supported NE Software Releases":
•
Note
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Sections and Caveats Added
The following sections and caveats were added to the release notes:
•
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
Sections and Caveats Removed
•
–
–
–
–
–
–
–
–
–
•
–
–
–
–
–
CTM-Supported NE Software Releases
The following table lists the NE software releases supported in CTM R8.0.
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.1
2.0.1
Release 2.0.2
2.0.2
ONS 15305
Release 2.0.2
2.0.2
Release 2.0.3
2.0.3
ONS 15305 CTC
Release 3.0.5
04.60-X06F-28.14
ONS 15310 CL
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.0.31
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.52
07.05-007D-20.22
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22.007B-08.193
07.22-007B-15.13
Release 7.2.34
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
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.55
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.197
07.22-007B-15.13
Release 7.2.38
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
ONS 15327
Release 4.1.3
04.13-003L-19.01
Release 4.1.4
04.14-004C-09.23
Release 4.1.82
04.182-006-L2805
Release 4.6.6
04.66-005K-09.00
Release 5.0.4
05.04-005G-13.18
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.0.39
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.510
07.05-007D-20.22
Release 7.0.711
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22.007B-08.1912
07.22-007B-15.13
Release 7.2.313
07.23-007F-22.02
ONS 15454 SONET
Release 4.1.4
04.14-004C-09.23
Release 4.1.6
04.16-004I-10.23
Release 4.1.82
04.182-006-L2805
Release 4.6.5
04.65-005C-23.19
Release 4.6.6
04.66-005K-09.00
Release 4.7 (MSTP only)
04.70-004I-14.01
Release 5.0.6
05.06-005H-23.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.2 (MSPP only)
06.02-006K-21.13
Release 6.0.314
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.515
07.05-007D-20.22
Release 7.0.716
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
07.20-M06H-22.00
Release 7.2.2
07.22-007B-15.13
Release 7.2.317
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
ONS 15454 SDH
Release 4.6.3
04.63-004I-30.23
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.318
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.519
07.05-007D-20.22
Release 7.0.720
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
07.20-M06H-22.00
Release 7.2.2
07.22-007B-15.13
Release 7.2.321
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
ONS 15501
Release 4.1 AC
4.1
Release 4.1 DC
4.1
ONS 15530
Cisco IOS Release 12.2(29)SV
12.2(29)SV
ONS 15540 Extended Services Platform (ESP)
Cisco IOS Release 12.2(29)SV
12.2(29)SV
ONS 15540 Extended Services Platform with external cross-connect capability (ESPx)
Cisco IOS Release 12.2(29)SV
12.2(29)SV
ONS 15600 SONET
Release 1.3.1
Note
01.30-004D-01.20
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.2
06.20-006C-17.10
Release 6.2.2
06.22-006F-23.21
Release 6.2.4
06.24-006L-15.00
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.2
07.20-006E-04.17
Release 7.2.2
07.22.007B-08.1922
07.22-007B-15.13
Release 7.2.323
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
ONS 15600 SDH
Release 1.4
01.40-004A-15.18
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
CRS-1
Release 3.2
3.2.0
Release 3.2.1
3.2.1
Release 3.2.2
3.2.2
Release 3.3
3.3.0
Release 3.3.1
3.3.1
Release 3.3.2
3.3.2
XR 12000
Release 3.2
3.2.0
Release 3.2.1
3.2.1
Release 3.2.2
3.2.2
Release 3.3
3.3.0
Release 3.3.1
3.3.1
Release 3.3.2
3.3.2
Cisco 7609
12.2(18)SXF
—
Cisco Catalyst 6509
CatOS 7.1(1) or later
Most recent CatOS release
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.3024
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.0025
5.4.00
Release 5.54.0020
5.54.00
1 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.
2 In order for CTM to support the ONS 15310 CL R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.0.5 to the Supported NE Table.
3 In order for CTM to support the ONS 15310 CL R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.2.2 to the Supported NE Table.
4 In order for CTM to support the ONS 15310 CL R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 CL R7.2.3 to the Supported NE Table.
5 In order for CTM to support the ONS 15310 MA R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.0.5 to the Supported NE Table.
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 R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.2.2 to the Supported NE Table.
8 In order for CTM to support the ONS 15310 MA R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15310 MA R7.2.3 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 15327 R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.0.5 to the Supported NE Table.
11 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.
12 In order for CTM to support the ONS 15327 R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.2.2 to the Supported NE Table.
13 In order for CTM to support the ONS 15327 R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15327 R7.2.3 to the Supported NE Table.
14 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.
15 In order for CTM to support the ONS 15454 SONET R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.0.5 to the Supported NE Table.
16 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.
17 In order for CTM to support the ONS 15454 SONET R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SONET R7.2.3 to the Supported NE Table.
18 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.
19 In order for CTM to support the ONS 15454 SDH R7.0.5, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.0.5 to the Supported NE Table.
20 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.
21 In order for CTM to support the ONS 15454 SDH R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15454 SDH R7.2.3 to the Supported NE Table.
22 In order for CTM to support the ONS 15600 SONET R7.2.2, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R7.2.2 to the Supported NE Table.
23 In order for CTM to support the ONS 15600 SONET R7.2.3, you must add the software version to the Supported NE table. See Adding the ONS 15600 SONET R7.2.3 to the Supported NE Table.
24 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.
25 VQM is supported in VXSM R5.4.00 and R5.54.00.
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 15310 CL R7.0.5 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R7.0.5, 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 R7.2.2 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R7.2.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 R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15310 CL R7.2.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 15310 MA R7.0.5 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R7.0.5, 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 R7.2.2 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R7.2.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 MA R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15310 MA R7.2.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 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 15327 R7.0.5 to the Supported NE Table
In order for CTM to support the ONS 15327 R7.0.5, 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 15327 R7.2.2 to the Supported NE Table
In order for CTM to support the ONS 15327 R7.2.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 15327 R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15327 R7.2.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 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 SDH R7.0.5 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R7.0.5, 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 R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SDH R7.2.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 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 15454 SONET R7.0.5 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R7.0.5, 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 R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15454 SONET R7.2.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 R7.2.2 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R7.2.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 15600 SONET R7.2.3 to the Supported NE Table
In order for CTM to support the ONS 15600 SONET R7.2.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 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.0.
Table 3 CTM-Supported JRE Versions
1.5.0_6
—
—
This JRE version was used when CTM R8.0 was released.
1.5.0_11
CSCsj41105
An old JRE version causes security issues in CTM.
This JRE version was supported starting in CTM R8.0.0.863.3.
1.5.0_12
CSCsk28346
This caveat applies to CTM R8.0 only. Later CTM releases will contain the new JRE version.
This JRE version was supported starting in CTM R8.0.0.871.4.
1.5.0_15
CSCsq11152
—
This JRE version was supported starting in CTM R8.0.0.907.3. This JRE version is optional; it is not mandatory that you upgrade to JRE version 1.5.0_15. See (Optional) Upgrading to JRE Version 1.5.0_15.
(Optional) Upgrading to JRE Version 1.5.0_15
CTM R8.0 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_15. It is not mandatory that you upgrade to JRE version 1.5.0_15.
Upgrading the CTM R8.0 Server to JRE Version 1.5.0_15
Step 1
Step 2
# ctms-stopStep 3
Step 4
# cd /tmp# unzip CTM80_JRE_UPGRADE_1_5.zipThis creates a new directory called JRE.
Step 5
# cd JRE
Step 6
Step 7
Step 8
Caution
Step 9
# cp jre-1_5_0_15-solaris-sparc.sh /tmp/JRE# chmod +x jre-1_5_0_15-solaris-sparc.shStep 10
# ./installNewJre.sh jre-1_5_0_15-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_15/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-startStep 14
COMPLETED APPLICATION OF JRE INSTALLER PATCHcp: cannot access /opt/CiscoTransportManagerClient/ctmc-startcp: cannot access /opt/CiscoTransportManagerClient/ctmcdebug-startcp: cannot access /opt/CiscoTransportManagerClient/ctmc.shcp: cannot access /opt/CiscoTransportManagerClient/startcwmapp.kshcp: cannot access /opt/CiscoTransportManagerClient/UninstallerData/IAuninstaller.shcat: cannot open /opt/CiscoTransportManagerClient/ctmc-startcp: cannot create /opt/CiscoTransportManagerClient/ctmc-start: No such file or directorycat: cannot open /opt/CiscoTransportManagerClient/ctmcdebug-startcp: cannot create /opt/CiscoTransportManagerClient/ctmcdebug-start: No such file or directorycat: cannot open /opt/CiscoTransportManagerClient/ctmc.shcp: cannot create /opt/CiscoTransportManagerClient/ctmc.sh: No such file or directorycat: cannot open /opt/CiscoTransportManagerClient/startcwmapp.kshcp: cannot create /opt/CiscoTransportManagerClient/startcwmapp.ksh: No such file or directorycat: cannot open /opt/CiscoTransportManagerClient/UninstallerData/IAuninstaller.shcp: cannot create /opt/CiscoTransportManagerClient/UninstallerData/IAuninstaller.sh: No such file or directory
Upgrading the CTM R8.0 Solaris Client to JRE Version 1.5.0_15
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_15:
a.
b.
c.
# cd /tmp# unzip CTM80_JRE_UPGRADE_1_5.zipThis creates a new directory called JRE.
d.
# cd JREe.
f.
g.
h.
# cp jre-1_5_0_15-solaris-sparc.sh /tmp/JRE# chmod +x jre-1_5_0_15-solaris-sparc.shi.
# ./installNewJre.sh jre-1_5_0_15-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_15"Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)
Upgrading the CTM R8.0 Windows Client to JRE Version 1.5.0_15
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
# cd C:\Cisco\TransportManagerClient8_0\jre\binStep 8
# java -versionIn the output, you should see:
java version "1.5.0_15"Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)
Resolved Caveats
The following table lists caveats that are resolved as of the latest CTM R8.0 patch or service pack.
Table 5 Caveats Resolved in CTM R8.0
CSCeg49544
A manual link is not removed automatically when a patchcord link with the same layer type is created between the same endpoints.
CSCeh69324
After a new MGX node is added to the CTM client through the Domain Explorer, that node cannot be seen in the tree view of the Configuration Center, Chassis View, Statistics Report, and Diagnostic Center windows.
CSCei76087
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.
CSCei76154
The multilayersubnetwork.idl file returns errors when it is compiled with a third-party IDL compiler. (Related caveat ID: CSCse64642)
CSCin81696
When a 1:1 protection group is created for a DS3XM card on an ONS 15454 NE, the protection group is not visible immediately.
CSCin92735
In the ONS 15600 SDH NE Explorer > Security tab, the Users, Active Logins, and Policy subtabs are missing.
CSCsb46479
When data communications channel (DCC) links are deleted, CTM does not display patchcord links between the same nodes.
CSCsb69664
After creating a DCC with Open System Interconnection (OSI) support, the corresponding OSI subnet is shown incorrectly as Port 0 or is empty.
CSCsc21241
Echo mode in CTM GateWay/TL1 does not work correctly or can be disabled, requiring local echo to be enabled on the Telnet client. The password is not hidden.
CSCsc32223
The export configuration data does not export any data for the NE or the cards. Incorrect shelf ID management occurs when preprovisioning and configuring single shelf in multishelf NEs.
CSCsc48173
The NE service name for one event does not match the name used in the Audit Log filter. The following message might not appear in the Audit Log:
AUD-7000: Subnetwork Mode Automatic - MGX88xxSubnetManager Started > > >regrouping of managed NEs in subnetworks mgx88xx-ne
CSCsc68111
The getSNC application program interface (API) fails to retrieve any OCH trail tunnel circuits from the CORBA gateway.
CSCsc75969
CTM GateWay/TL1 commands require that Enter be pressed, even when the command ends with a semicolon.
CSCsc81901
When the historical STS Path PM table is launched on a DS1_84xx card provisioned on DS1 ports, the Interface column displays the STS number as 1 instead of as 2 or 3.
CSCsc84285
When an STS3C circuit is created on a DS1_E1_56 card in E1 mode and the real-time VT-2 PM table is launched, VT Group Num and VT Num In Group in the Interface field are incorrect.
CSCsc84872
When a gateway network element (GNE)/NE configuration has an internal LAN configured on the link that interconnects the ONS 155xx nodes, the discovery process displays the internal IP address on the properties pane of the Domain Explorer for all end network element (ENE) nodes, but the internal IP address cannot be changed to a public IP address.
CSCsc84893
Added shelves are not displayed on the NE Explorer.
CSCsc85207
A card state change through CTM GateWay/TL1 is not reflected on the CTM client.
CSCsc86149
Span loss calculation fails with the error message "Operation partially completed." After the error message is displayed, the span loss values are empty.
CSCsc90221
For a multishelf NE, the state change from Out of Service to In Service is inconsistent and occurs without a configuration synchronization.
CSCsc92667
When you add an unmanaged NE to CTM and mark it as In Service, the unmanaged NE shows a red check mark (unreachable) instead of a green check mark (reachable).
CSCsc96230
The MGX Voice Gateway R5.3.00 is missing from the Supported NE table.
CSCsc98405
Cannot perform a forced soft reset on CTX cards in the ONS 15310 MA.
CSCsd01309
In the MGX Voice Gateway Equipment Inventory table the Description, Reset Reason, and State columns are not sorted correctly.
CSCsd01713
The tooltip is not updated when the card state changes.
CSCsd01798
FMEC cards are shown as active, even when shelf is in the Delete state.
CSCsd05277
For DS3XM cards on ONS 15454 SONET R4.6.4 NEs, the 15-minute PM data on the STS path near end shows pointer-related PM parameters.
CSCsd05423
Threshold crossing alerts (TCAs) are not displayed for the RS-UAS parameter in the SDH Regeneration Section PM table.
CSCsd07586
The tree view is not updated in certain scenarios when card-related operations are performed on the controller card.
CSCsd10715
For DM_2.5G and DMP_2.5G cards with ESCON pluggable modules, duplicate pluggable port module (PPM) entries are recorded after a card reset.
CSCsd11702
Cannot change fields on the Control Panel because an error dialog box is displayed with the following message:
EID-192: The server configuration has been modified by another user since it was last read. You must refresh this view before any changes can be made to the server configuration file.
CSCsd17128
SNMP traps are not received from an ENE if configuration is done from the CTM client.
CSCsd21280
CTM manages ONS 15454 events when the node is under maintenance.
CSCsd25419
Cannot determine whether the laser is on or off for STM-64 cards.
CSCsd28522
The external alarm description field does not work on the ONS 15310 MA platform.
CSCsd29921
Far-end STS PM tables are blank for DS3_EC1_48 cards in NE release 5.0.2.
CSCsd30268
The DCC link between the TXP client port and the line card is discovered at the physical layer instead of the SDCC layer.
CSCsd30368
Composite net links created in the network are not discovered in CTM if the NEs are already discovered or added in CTM. If the NEs are added to CTM after the link is created, the discovery works as expected.
CSCsd30391
Composite net links are displayed in the CTM Network Map when they should not be.
CSCsd31644
Cannot retrieve 15-minute or 1-day VT1.5 PM thresholds on CTX optical cards on ONS 15310 MA NEs from CTM GateWay/CORBA.
CSCsd31850
On NE version 6.2, coding, framing, and AIS thresholds are editable in BITS-OUT on the ONS 15454 SONET and SDH. The issue is fixed in SDH but not in SONET.
CSCsd32041
A protection group is not listed among protection groups at the shelf level.
CSCsd32439
If you choose to upgrade from the existing release, the Previous button is dimmed.
CSCsd32830
An alarm entry is missing from the active_alarm_table.
CSCsd35616
The far-end 15-minute and 1-day PM tables display meaningless negative values for DS1 cards that do not support NP parameters in Extended Superframe (ESF) mode.
CSCsd35746
The setTP API does not succeed for FTPs on CE-100T-8 cards on ONS 15454 or ONS 15310 MA NEs. The command fails without an error message or exception. (Related caveat ID: CSCse66559)
CSCsd37522
When you try to launch the NE Explorer by double-clicking a GNE node, an error message is returned.
Note
CSCsd39577
An L2 topology is shown as Incomplete when the status should be Complete. All circuits are shown as discovered in the Circuit table.
CSCsd43544
After changing the protection group name, the default name is still shown.
CSCsd44356
The circuit alias and topology alias do not work in a mixed-size L2 topology.
CSCsd44908
The self alarm of a PXM card in the primary slot is missing from the Chassis View. (Related caveat ID: CSCse12717)
CSCsd45038
After adding an ONS 15454 MSTP node to a DWDM span, the new optical transmission section (OTS) links (layer = physical, layer details = OTS) are not discovered if the old invalid links were not deleted previously.
The OTS links with layer = Transmission Section and Layer Details = OTS are discovered correctly and the old invalid links are removed automatically. The same behavior should occur for OTS links at the physical layer.
CSCsd45491
When the topology name is longer than 26 characters, after a card is added the new circuit is not discovered correctly and the RPR wraps. CTM appends the time stamp to the newly created circuit name on the added card. This sometimes causes naming problems.
CSCsd45581
For server trails created on ONS 15310 MA NEs, the wrong physical location is shown for all path alarms such as Encapsulation Mismatch and TIM-P. CTM shows the physical location with port 0. For example, if an alarm is raised on slot 1, port-29-56, the physical location is shown as slot 1, port 0.
CSCsd46307
An invalid link becomes valid when NEs are marked as Out of Service and then In Service. This problem applies to links that are invalid because one or both ports of the link are marked as Out of Service, or because a fiber cut occurs on the link.
CSCsd46817
Cannot use the CTM NE Explorer to create a 2-fiber bidirectional line switch ring (BLSR) on the ONS 15327.
CSCsd46844
The Squelch table is blank for ONS 15327 NEs but correct for ONS 15454 SONET NEs.
CSCsd46879
The FC-P counter for 15-minute or 1-day far-end STS thresholds shows near-end values instead of far-end values. Even if you change the values of FC-P to far end, the changes occur at the near end for the OC192 XFP card.
CSCsd47150
The IOS Users table is blank for ENEs in a GNE-ENE setup after changing ENEs to GNEs and GNEs to ENEs, and changing the community strings for the ENEs.
CSCsd47274
The IOS Users table is blank for a GNE-ENE setup with ONS 15600 NEs as GNEs. The SNMP community string is blank for all ENEs in the Domain Explorer. The community string was configured as public for all NEs in CTC. Because of this problem, L2 does not work in a GNE-ENE setup where ONS 15600 NEs are configured as GNEs.
CSCsd47319
The wrong reversion time option is shown in the Timing tab for ONS 15310 MA NEs.
CSCsd48566
In the CTM client, you cannot view or edit the SNMP community strings for an ONS 15600 that supports SNMP traps.
CSCsd50813
The following null pointer exception is generated during STS creation in the Source/Destination pane:
EID-915: Failed to retrieve STSs.
java.land.NullPointerException.
Also, you cannot route a circuit manually through available STSs. The manual routing wizard returns the error message "STSs are not available."
CSCsd52436
After migrating from CTM R6.0 to CTM R7.0, R7.1, or R7.2, the valid links on ONS 15216 NEs become invalid.
CSCsd53003
The Add Drop wizard shows RSTP is disabled on the existing drops when STP is actually enabled on the existing drops.
CSCsd53108
When RADIUS relay is enabled on the card, IOS user creation is shown as successful, but the users are not visible in the IOS Users table. Instead, CTM should return an error that IOS users could not be created.
CSCsd53747
Cannot set PMP_UAS for regenerator section for STM1 cards on ONS 15454 SDH NEs.
CSCsd54654
The SetTPData API does not work on PPM ports.
CSCsd54727
For 15-minute and 1-day near-end line thresholds, six thresholds are missing for OC-192 cards.
CSCsd54772
The Raise AIS for LOF option for DS1 cards on ONS 15454 NEs should be removed, because it is not applicable. (Related caveat ID: CSCse58821)
CSCsd54789
For optical cards such as the OC-12 or OC-48 that do not support historical 15-minute STS path far-end PM collection, CTM should not collect and display PM data.
CSCsd54810
Cannot restart the laser for CTX cards in ONS 15310 CL nodes. The option to restart the laser is dimmed.
CSCsd55013
An hourglass is shown on the Circuit Trace window when the WDM Topology check box is checked. It takes 15 seconds or longer for the circuit trace to refresh.
CSCsd55060
A patchcord link between a trunk port and a channel port is shown in the Link table at the Physical layer.
CSCsd55132
The getTCATPParams command does not show NPJC_PGEN. Instead, the command shows NPJC_PDET twice on STM-1_8 on ONS 15454 SDH NEs.
CSCsd55139
Cannot filter the Equipment Inventory table for the "Other" filter option.
CSCsd55143
The Multicast Bandwidth class of service (CoS) value is set to 0 (zero) on a newly added card.
CSCsd56066
The getAllPTPsForSNCProvisioning method returns all DS3 ports on DS3_EC1_48 cards for layer rate 14. The method should return only EC1 ports for layer rate 14. DS3 ports should be returned only for layer rate 4; instead, the method returns DS3 ports for layer rates 4 and 14.
CSCsd56923
If you cancel the CTM upgrade after finishing all GUI selections and then retry the upgrade, a "Version not supported" error is returned.
CSCsd57835
For Cisco IOS XR-based NE types, the Routing Policy application is not supported in Cisco IOS XR release 3.3 and later. To access this application, open the NE Explorer and choose Configuration > Policy > Routing Policy. The menu option is dimmed for NEs running Cisco IOS XR release 3.3 or later.
CSCsd58131
The GetManangedElement method returns an empty supportedRates list for some managed elements.
CSCsd82349
Patchcords between splitter-protected transponders and MUX/DMX cards are created with a "Y-cable" protection attribute. The correct attribute is "Protected."
CSCsd82603
In the Control Panel > Security Properties pane > CTM Security tab > Login Preferences area, the Max Retries value does not work correctly.
CSCsd86921
For the Cisco 7600, the Active Software field in the NE Software table is not populated with any data, and the Running Software field shows the value Not Available.
CSCsd92046
For the Cisco 7600, when you click the Finish button in the Template Manager > Apply Template wizard, a template provisioning job is not created in the Job Monitor table.
CSCsd93868
Cannot display 24-hour PM data for ONS 155xx NEs.
CSCse11954
When setting the ONS 15808 craft tool password to all uppercase and all alphanumeric, an error message appears. If you select a password such as abc123/, CTM schedules the job and reports in the Job Monitor table that the job succeeded, but a different password (ABC123/) is set on the NE. All attempts to log in fail using the password abc123/.
CSCse19751
The getPortName and setPortName APIs fail for E100 and E1000 cards on ONS 15454 SDH NEs. (Related caveat ID: CSCsf03360)
CSCse22241
The setTPData API fails for FC_MR cards.
CSCse44269
The GetAssociatedTopologicalLinks API does not return any values for ONS 1580x NEs.
CSCse52287
In the NE Explorer for the ASAP CC card, the Shelf View and Module View tabs incorrectly show the card as ASAP MB.
CSCse52310
The ASAP card state is shown incorrectly as "Standby" in the NE Explorer > Module view when it is actually "Active." The Equipment Inventory table shows the equipment state incorrectly as "Standby."
CSCse53332
The name of a Y-cable protection group is not reported correctly in the NE Explorer > Protection Groups tab. Instead, the default value is reported.
CSCse54602
Alarms are not summarized on autodiscovered links between DWDM transponder client ports when configured with SONET or SDH payload.
CSCse57499
Cannot provision reach and wavelength parameters for MRC_12 and OC-192 XFP cards on the ONS 15454 SONET and ONS 15454 SDH R7.2.
CSCse57741
The getAllActiveAlarms API shows the layer rate as 0 for the RAN_SVC cards.
CSCse58070
The list of modules is blank when you select far-end PM data for an STM-4 card on an ONS 15454 SDH NE.
CSCse58271
The number of unacknowledged alarms shown on the Dashboard is not the same as the number of unacknowledged alarms shown in the Alarm Browser.
CSCse58325
The setTPData API fails for ONS 15600 SDH NEs.
CSCse58431
The Administration > SNTP Configuration menu option is dimmed for ONS 15600 SDH R1.4 NEs.
CSCse59300
CTM does not update RPM-XF traps in real time.
Note
CSCse59857
If you use the createTopologicalLink API to create a physical link on ONS 15216 NEs, CTM GateWay/CORBA returns the following error and the link is not created:
The aEndTP is not an available TP for this TopologicalLink creation.
CSCse60078
XUA application server (AS) creation fails from the MGX Configuration Center for the VXSM 2.5 image.
CSCse60213
Port numbers are shown incorrectly at the card level for ASAP cards on ONS 15600 SONET NEs.
CSCse60508
For Link Up and Link Down traps shown in the Alarm Browser, the corresponding CTM GateWay/TL1 command rtrv-alm-all shows the physical location as "not used."
CSCse60708
The VISM_LINE table is not populated with any entries in the database.
CSCse60764
The setTPData API fails for the Enable Sync Msg and line coding attributes for DS1_E1_56 cards.
CSCse62188
Cannot create CTM GateWay/TL1 Event Forwarding Discriminator (EFD) filters for ONS 15454 SDH NEs.
CSCse63352
Cannot set autodetect credits on an FC_MR card through CTM when the enable distance extension is not set.
CSCse63409
After the Memory Restore operation on an ONS 15216 EFDA3 is complete, only the SNMP Trap table is restored. All other values (such as thresholds, latitude, and longitude) are not restored.
CSCse63492
The alarm severity of discovered SDH links remains critical even if the alarms are cleared.
CSCse64026
In a 24-card RPR, the Alias field is not set to the user-specified value. (Related caveat ID: CSCsd44356)
CSCse64156
The laser status is not shown for OC-192 cards. You cannot determine whether the laser is on or off, because the status field is always blank.
CSCse64267
DS3 real-time PM data collection returns the wrong data for DS3 cards.
CSCse65722
When creating a manual link between CRS-1 and ONS NEs, the list of physical termination points (PTPs) displayed includes those that are already in use. The list should display only available PTPs.
CSCse65760
When creating a manual link between CRS-1 and ONS NEs, the list of PTPs displayed is not filtered by wavelength. The PTPs used for optical channel client connection (OCHCC) circuits should be configured for the same wavelength. (Related caveat ID: CSCse41517)
CSCse66792
TCAs are not shown in PM data for ONS 15600 SONET R7.2 NEs.
CSCse67644
When the server is migrated from CTM R6.0 to CTM R7.2 and robust PM data collection is enabled on the NEs, data is lost for the migrated interval.
CSCse68674
CTM GateWay/TL1 ignores user-entered commands when the network contains a high number of unresponsive NEs.
CSCse69351
Name changes of parent virtual concatenation (VCAT) circuits made from CTC do not reflect in CTM.
CSCse71108
When an ML card reset is in progress, you can modify the Ethernet ports. CTM confirms that the port modification succeeded, even though no changes were actually applied to the card.
CSCse71474
CTM supports two invalid admin states—OOS and OOS AINS—for ONS 15310 MA R7.2 NEs. (Related caveat ID: CSCsg11609)
CSCse72287
The Alarm Browser and Alarm Log do not display DBOSYNC alarms from ONS 15600 SONET R1.3.1 NEs.
CSCse72619
It takes approximately 2.5 minutes to open the Control Panel window.
CSCse72690
For VCAT Group Down alarms generated on ML-100T-8 cards, the layer rate is shown as 0.
CSCse72696
For ASAP_4 cards and XFP OC-192 SRI modules, CTM GateWay/CORBA shows the incorrect layer rate for SONET section and SONET line alarms.
CSCse73260
If you create a manual link between a 2.5G_DM trunk (on the source node) and an STM-16 TXP client (on the destination node), the STM-16 layer detail is not available. The STM-16 layer is available only if the link is created in the other direction (on the 2.5G_DM on the destination node).
CSCse73643
The detected line type is shown as E1_MF for DS3IN cards on ONS 15454 SONET NEs.
CSCse74063
The CTM R7.2 client uses 100% CPU.
CSCse74210
The Squelch table is incorrect for ONS 15600 SDH NEs. For STM-64 two-fiber BLSRs, the Squelch table shows 96 entries. For STM-16 MS-SPRings, the Squelch table shows 25 entries. The table should show 32 entries for STM-64 and 8 entries for STM-16.
CSCse75411
If the network contains both optical channel network connection (OCHNC) circuits (between ONS NEs) and OCHCC circuits (between CRS-1 NEs), the Circuit table for an ONS 15454 MSTP shows OCHCC circuits with "Bad Value" listed in many of the fields.
CSCse75608
The Locate Alarm feature does not work for environmental alarms; it returns a "String not found" error. (Related caveat ID: CSCsf17110)
CSCse75609
The layer rate is shown as zero for alarms on the optical ports of ONS 15305 NEs.
CSCse75765
The Alarm Browser does not display the port name for any alarms.
CSCse76839
When changing the SNMP community string for a GNE, the community string does not change for the ENE. The string does not change even after marking the NEs as Out of Service and then In Service.
CSCse76870
Manual link validity between a CSR-1 and ONS 15454 is not handled correctly when there is a loss of connectivity to the ONS 15454.
CSCse76895
When a CRS-1 NE is marked as Out of Service, all of the OCHCC circuits that are provisioned by the NE (with the ONS cloud) are shown incorrectly as In Service and Active. The correct states are Out of Service and Errored.
CSCse79186
Cannot perform read/write operations for reach and wavelength parameters on CTX cards on the ONS 15310 CL and ONS 15310 MA.
CSCse79378
The cross-connect (XC) utilization for STS and VT circuits is not populated on ONS 15310 NEs.
CSCse79489
The layer rate information is incorrect for LOS alarms generated on EC1 ports on ONS 15310 CL NEs.
CSCse80635
An invalid admin state is supported for the RAN_SVC card on ONS 15454 SDH NEs.
CSCse81636
You can edit the DCC on a port where regenerator section DCC (RS-DCC) and MS-DCC are enabled. (Related caveat ID: CSCsc61912)
CSCse81989
The setTPData API fails and generates exceptions for client ports on MXP_MR_10DME cards. The command works correctly for trunk ports.
CSCse82465
The following CTM GateWay/CORBA commands display incorrect port numbers and interface names:
•
•
•
•
•
CSCse82623
When using the CTM GateWay/CORBA interface, the managedElementManager::ManagedElementManager_I::getAssociatedTopologicalLinks command returns an empty list.
CSCse83633
When a CRS-1 OCHCC circuit is provisioned using OCHNC, events from ONS NEs must be propagated to CRS-1 modules in order for the circuit status to update correctly. (Related caveat ID: CSCse87778)
CSCse84755
When creating VT-VCAT circuits on CE-100T-8 cards on ONS 15310 CL NEs, invalid VT thresholds are created on DS1 interfaces on CTX cards.
CSCse85982
CTM supports an invalid admin state for CTX-2500 ports on ONS 15310 MA NEs.
CSCse86393
The NE Explorer > Alarm Behavior tab does not show GFP ports for read/write operations, so you cannot suppress or enable alarms on GFP ports on MXP_MR_10DME cards.
CSCse86395
AINS soak countdown values are not shown for DWDM cards such as MXP_MR_10DME and MXP_2.5G_10E. You can set the AINS soak time interval, but you cannot see the AINS soak countdown time.
CSCse86405
The IS AINS admin state is missing for the trunk (line) ports of MXP_MR_10DME cards. Using CTC, you can put the port in IS AINS state, but you cannot perform the same task in CTM.
CSCse87371
If you try to enable CoS accounting on ONS 15454 SONET R4.1 NEs, you receive a warning message that CoS accounting is not supported on the NE, which is the correct behavior. However, you can enable CoS accounting on ONS 15454 SDH R4.1 NEs, even though ML cards do not support CoS accounting for the ONS 15454 SDH R4.1.
CSCse87585
Cannot retrieve a J1 path trace for ONS 15600 SONET NEs or for any of the cards.
CSCse88621
The NE takes a long time to synchronize if ML cards are not loaded with a barebone configuration.
CSCse89050
Cannot load saved templates for the DPNSS configuration in the Configuration Center GUI.
CSCse90123
Cannot change the IP address in the NE Explorer.
CSCse91283
The createTopologicalLink API does not work correctly.
CSCse91892
The getAllSupportedPTPs API fails to retrieve data for DS1_84 and DS3_EC1_3 line cards that have DS3 ports.
CSCse91995
The CTM client freezes during object-creation or object-deletion event processing, and when the Circuit table is in autorefresh mode and contains a large number of circuits that are being discovered.
CSCse93968
The getAllCrossConnections API returns cross-connects for CTX cards with incorrect PTP details on ONS 15310 MA NEs.
CSCse94028
For the MRC_12 card, reach and wavelength PPM values are shown as N/A in CTM. CTC shows the correct values.
CSCse94115
The Exercise Ring operation fails on an ENE not directly connected to the GNE.
CSCse94192
While adding NE defaults from one NE to another, an IDL/config exception is generated.
CSCse94210
When trying to create users on multiple NEs from the Domain Explorer > Administration > NE User Access Administration menu option, the Job Monitor table shows the task status as Failed for some nodes, even though the user is created.
CSCse94236
Trying to restore memory on an ONS 15600 SONET NE generates a java.lang.ArrayIndexOutOfBoundsException on the console window.
CSCse95128
Cannot collect DS1 far-end PM data for DS3XM cards.
CSCse96654
The subnetwork automatic grouping feature does not work after a TCC reset.
CSCse97249
The getAllSNCs API on a node fails with a CTM GateWay/CORBA exception such as "The srcNodeId is null for the circuit with <node_ID>."
CSCse97951
Cannot retrieve VT1.5 PM thresholds for VT circuits on XTC cards on ONS 15327 NEs.
CSCse98401
CTM does not show the "LP-UNEQ - SLMF-Unequipped Low Order - Path Unequipped" alarms on ONS 15305 CTC NEs. The same alarm is visible in CTC and Cisco Edge Craft.
CSCse99103
Cannot enable retiming on DS1 ports of CTX cards on ONS 15310 CL R7.2 NEs. The operation fails with an error message in CTM, yet works correctly in CTC.
CSCse99116
Cannot perform send code operations (such as send line loopback and send payload loopback) on DS1 ports of CTX cards on ONS 15310 CL NEs.
CSCse99713
CTM GateWay/CORBA returns the wrong name for the PPM creation and deletion notification.
CSCsf00469
Cannot restart the laser for OSC-CSM and OSCM modules.
CSCsf00804
CTM client performance decreases during normal operations.
CSCsf05571
The CTM client on Windows 2000 and Windows XP does not support the Daylight Saving Time (DST) changes for March 2007 in the United States by the Energy Policy Act of 2005. The CTM client disregards the DST changes and displays the time according to the existing DST settings.
CSCsf09835
For an STS-1 circuit on an EC1 interface on all CTC-based NEs except for the ONS 15454 SONET, you cannot set TCAs at the STS path.
CSCsf12195
Connection termination point (CTP) naming differs from what is reported in the Cisco Transport Manager Release 7.2 GateWay/CORBA User Guide and Programmer Manual. For STS-1 CTPs, values for k > 3 are shown in all APIs that contain CTPs.
Note
CSCsf15991
For links terminating on ONS 15600 SONET or ONS 15600 SDH NEs, the Link Utilization table shows the wrong VC4/STS number when a low-order circuit traverses the link over a tunnel. The Circuit Trace report for the low-order circuit shows the VT/VC3 number as 255. The Circuit Span table for the low-order circuit shows 255 for endpoints on the ONS 15600 SONET or ONS 15600 SDH NEs.
CSCsf16108
In the SONET automatic protection switching (APS) application, you cannot configure preconfigured interfaces in the table.
CSCsf16285
An ENE is not reachable in a GNE/ENE setup because its name is the same as one of the NEs in CTM.
CSCsf17873
When using CTM to configure the NE timing reference or the BITS-1/BITS-2 OUT reference on a multishelf NE, the TCC reloads, causing a loss of communication with the NE. The new timing reference values are not set on the NE.
CSCsf18143
After 5 days of testing, CPU utilization is 90 percent in a network with 45 NEs and a small server configuration.
CSCsf20220
The VC-4 Threshold tab for STM-1_E cards is missing the following values: PPJC-PDET, NPJC-PDET, PPJC-PGEN, NPJC-PGEN, PJCDIFF, PJCS-PDET, PJCS-PGEN.
CSCsf20430
Occasionally, alarms in the NE Explorer rack view are not consistent with alarms in the Alarm Browser. Alarms in the NE Explorer tree view are correct.
CSCsf20434
In a configuration with a CRS-1 with 4x10GE-ITU-C ports and an ONS 15454 with MXP and TXP cards, you cannot create a bidirectional link from the CRS-1 to the ONS 15454. However, you can create a bidirectional link from the ONS 15454 to the CRS-1.
CSCsf21826
When creating manual links, STM-256 is not listed in the layer rate details.
CSCsf21849
Cannot create 1xOC768-ITU-C SDH circuits because the STM-256 data rate is missing.
CSCsf21864
You can create an OCHCC circuit with 1xOC768-ITU-C cards and mismatched framing (where one side of the circuit is SONET and the other side is SDH). Instead, circuit creation should fail when circuit endpoints do not have the same framing type.
CSCsf21876
The Create Circuit wizard allows you to set up an SDH- or SONET-sized circuit group; however, the wizard does not filter the endpoint based on the framing type.
CSCsf22002
CRS-1 manual links for DWDM PLIMs do not support multiple layers (such as DWDM and SONET layers).
CSCsf22379
Cannot set the timing for the BITS IN facility on an ONS 15454 SONET R6.2 NE. (Related caveat ID: CSCsf32258)
CSCsf23141
You can create CRS-1 —> ONS 15454 —> CRS-1 circuits with CRS-1 NEs in one subnetwork and ONS 15454 NEs in another subnetwork. Instead, circuit creation should fail when the NEs belong to different subnetworks.
CSCsf23328
Occasionally, when you launch the Circuit table for CRS-1 circuits, the table shows the wrong number of circuit spans.
CSCsf23760
Whenever the SM service is restarted, a new syslog service instance is created. The previous syslog service instance is not stopped, resulting in multiple service instances. The syslog service count increases by one with every SM service restart.
CSCsf24240
If you try to launch CTC from CTM for an ONS 15600 SONET R7.0.2 NE, the login dialog box opens repeatedly, even after entering the correct username and password.
CSCsf24895
For CRS-1 circuits with an ONS 15454 cloud, if the wavelength of a port used by the circuit is changed, the circuit status does not change accordingly.
CSCsf24978
The Catalyst 6509 goes into LOC state if the CatOS version is not listed in the Supported NE table.
CSCsf26013
When a subnet containing an ENE is moved to a different network partition, the ENE goes into LOC state.
CSCsf26330
CPU utilization is very high because of an SNMP trap service deadlock.
CSCsf26887
Shutting down a 4x10GE-ITU-C interface belonging to a circuit does not cause the circuit to show "errored."
CSCsf27791
CTM GateWay/TL1 does not respond to user commands.
CSCsf28149
Cannot use CTM GateWay/CORBA to provision an STM-1_4 card on an ONS 15454 SDH R6.2 NE.
CSCsf28158
CTM GateWay/TL1 does not correctly show the current logged in user sessions in the CTM GateWay/TL1 Logged In Users table.
CSCsf28238
For all MGX alarms, CTM GateWay/TL1 shows the physical location as Not Supported, but without a physical location, an alarm is meaningless. CTM GateWay/TL1 either should not show MGX alarms or should show the correct physical location.
CSCsf28816
Cannot use CTM GateWay/CORBA to unprovision a PPM client port on an ONS 15454 MSTP transponder.
CSCsf29211
The getTP API does not work on transponder client ports with multiple PPMs.
CSCsf29570
The ONS 15310 MA R7.0.2 is missing from the Supported NE table.
CSCsg60510
When creating an ONS 15454 internal patchcord link that involves a transponder or muxponder card as an endpoint, the trunk port of the transponder or muxponder is not available as the source port.
CSCsg67176
Cannot change parameters for the CE-100T card in the NE Explorer.
CSCsg72820
Cannot set the Admin SSM value for MRC_12 cards.
CSCsg74283
For the set operation on SendDoNotUse for STM1_E12 cards, the Send<<FF>DoNotUse attribute is incorrect.
CSCsg79219
When the CTM server is started with the ctms-start command, the add_log_partition.sh script returns an error that the CTM database cannot be found.
CSCsg79457
SVLAN data is not updated after adding a PPM trunk that is created on GE_XP or 10GE_XP cards.
Note
CSCsg90763
A misleading error message is displayed when creating HTML reports from CTM tables.
CSCsg92911
Cannot perform get/set operations on hardware that is running an SNMP agent.
Note
CSCsh22076
A traffic loss of 15 seconds occurs through a VLAN created on an RPR Layer 2 topology.
Note
CSCsh69456
The TL1 interface contains junk characters when you launch it on an NE.
Note
CSCsh70890
SNMP traffic uses random ports.
Note
CSCsh77677
Custom QoS profile information is lost after some time.
Note
CSCsh78003
CTM client freezes for about one minute. Afterwards, the POS tab information displays correctly in the NE Explorer.
Note
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 OC192."
Note
CSCsh79073
Unable to modify the debug options for an NE service module after marking the NEs as Out of Service and then In Service and adding the NEs to a new partition.
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."
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.
Note
CSCsh92692
CTM GateWay/TL1 core dumps occur on the network.
Note
CSCsh94186
The confirmation dialog box is not displayed after uploading a configuration file to a TCC card.
Note
CSCsh95002
Cannot clear the Maximum Login Attempts Exceeded alarm for an unknown user. (Related caveat ID: CSCsg35907)
Note
CSCsh98865
The following alarms are shown incorrectly in the Alarm Browser:
•
•
•
Note
CSCsi03340
All NEs in a GNE/ENE ring are shown as ENEs. The GNEs are also shown as ENEs.
Note
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.
Note
CSCsi05518
CTM GateWay/TL1 temporarily stops forwarding events to the OSS.
Note
CSCsi06828
The pruning operation on an ONS 15454 SDH audit trail parameter does not work correctly.
Note
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."
Note
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."
Note
CSCsi08236
CTM GateWay/TL1 logs wrap quickly, meaning important information is lost and debugging becomes difficult.
Note
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.
Note
CSCsi12991
CTM GateWay/TL1 returns a DENY response to any command, indicating that the NEs are not connected and the login failed:
M c04 DENY
PIUI
"Privilege, Illegal User Identity"
/*Gateway Login To NE Failed */
Note
CSCsi20156
CTM GateWay/TL1 crashes randomly when it is stopped from the Control Panel while it is processing a command or sending responses to the OSS client.
Note
CSCsi27588
Circuit autorouting takes more time compared to earlier releases.
Note
CSCsi29165
The class order changes after creating a QoS profile.
Note
CSCsi29816
The SNMP and Alarm Behavior tables are empty for ONS 15216 EDFA3 NEs.
Note
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. (Related caveat ID: CSCsk76179)
Note
CSCsi40250
CTC displays the following error message when you set up timing in CTM: "EID-3225: Error while refreshing pane."
Note
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.
Note
CSCsi75389
The get/setTCA API fails for near- and far-end STM-1 path thresholds on MRC_12 cards.
Note
CSCsi75723
The Circuit table does not display the port name for DS3E, DS3XM, and DS3XM_12 cards.
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
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
CSCsj05733
Domain Manager Mode (DMM) commands such as rtrv-alm-all, rtrv-alm-ems, rtrv-ne-ems, and rtrv-subntwrk-ems are truncated to 20 rows, which results in missing information. The output is incomplete and an error message is displayed.
Note
CSCsj07316
Cannot set the Admin SSM value for the MRC_12 cards on R6.x NEs.
Note
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.
Note
CSCsj12833
After upgrading to CTM R8.0, users associated with custom CTM profiles cannot log into the CTM server.
Note
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.
Note
CSCsj34451
The Resync L2 Topology operation fails for a Cisco RPR that contains an ONS 15454 R4.1.82 NE.
Note
CSCsj34528
The Add/Remove Card operation fails for a Cisco RPR that contains an ONS 15454 R4.1.82 NE.
Note
CSCsj40223
Retrieval of OCHCC circuits from the CTM GateWay/CORBA client fails.
Note
CSCsj41401
The CTM server takes a long time to discover CTC-based NEs.
Note
CSCsj41573
Unable to launch CTC from the Domain Explorer and NE Explorer.
Note
CSCsj43760
The incorrect software version is displayed in the Control Panel.
Note
CSCsj47081
As of March 2007, DST start and end dates for the United States transitioned to comply with the Energy Policy Act of 2005. DST dates in the United States now start three weeks earlier (2:00 a.m. on the second Sunday in March) and end one week later (2:00 a.m. on the first Sunday in November).
Note
CSCsj51055
After applying customized settings on an ML card, you cannot change the QoS profile on a VLAN drop port.
Note
CSCsj52259
After a CTM server restart, the Alarm Browser reports a loss of communication between CTM and ONS 15305 NEs. The NEs are stuck in Initialization Failed state with an incorrect username/password error.
Note
CSCsj60001
Restarting CTM with AuthNoPriv- and NoAuthNoPriv-profiled SNMPv3 users in the database prevents some or all of the nondefault user NEs from synchronizing.
Note
CSCsj62479
The Error Log reports the following invalid error message for the MS-ISC card: "EID-6059: ML Card resync failure for NE: <NE_ID> - slot: 6 - Reason: IOS Config is empty and/or not found."
Note
CSCsj64171
CTM GateWay/CORBA uses abnormal amounts of CPU when you end an active CTM GateWay/CORBA user session from the Active GW/CORBA Users table.
Note
CSCsj66589
The CTM server is unable to complete the discovery of ONS 15454 NEs.
Note
CSCsj70311
The debug output of the CTMServer process, which is saved in the /opt/CiscoTransportManagerServer/log/CTMServer.log file, is unreadable after some time.
Note
CSCsj70432
The CTM server overwrites the most recent log files in the archive log directory.
Note
CSCsj76500
Some PM data for CTC-based NEs is not stored in the database when the PM service experiences high load conditions.
Note
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.
Note
CSCsj83214
The Circuit table displays TL1 circuits incorrectly.
Note
CSCsk00354
Unable to view or modify the MG-MGC association on VXSM R5.2.10. The following error message appears: "No data available."
Note
CSCsk20958
CTM GateWay/CORBA APIs return an exception with the following error reason: "The srcNodeId is null for the circuit with nodeId <node_ID>."
Note
CSCsk28346
CTM R8.0 must support a new JRE version.
Note
CSCsk28871
The /db05 partition is 100 percent full and the CTM server shuts down automatically.
Note
CSCsk29330
The port status is not displayed in the NE Explorer shelf view of ONS 15454 and ONS 15600 nodes. (Related caveat ID: CSCsk55740)
Note
CSCsk34774
The CTM debug log files in the /opt/CiscoTransportManagerServer/log directory do not show the thread names. All threads are traced with the Logging Event Queue Processor name instead of the actual thread name. This makes it difficult to troubleshoot issues in the CTM application.
Note
CSCsk52028
Setting the alarm type for an ONS 15454 SONET or ONS 15454 SDH NE with an AIC or AIC-I card fails and an error message appears.
Note
CSCsk44773
Due to security issues, CTM must support Apache web server version 2.0.61.
Note
CSCsk57463
Unable to manually route LO VCAT circuits between ONS 15305 NEs.
Note
CSCsk58050
Two circuits have the same name in the Circuit table.
Note
CSCsk69463
There are invalid objects in the database procedures of the CTM server after applying the CTM R8.0.0.871.2 patch.
Note
CSCsk70856
A database timeout occurs when you retrieve circuits from the Link table and no circuits are displayed on the Link table. An error message appears.
Note
CSCsk84707
CTM PM pruning fails due to a buffer overflow error.
Note
CSCsk84731
The getCTMHistoryPMData API does not return any CTP data when used on a managed element.
Note
CSCsk90404
The following messages, which do not indicate an error condition, are shown incorrectly in the Error Log with a severity level of Major instead of Debug:
•
•
Note
CSCsk92923
The OSS client cannot specify the time stamp as the local time in delta format because CTM misinterprets the format.
Note
CSCsk98333
CTM GateWay/CORBA reports a NullPointerException when the OSS client enters a nonzero value for the time stamp's tenths of a second.
Note
CSCsl00118
The RPR-east and RPR-west ports of an ML card that is adjacent to a newly added or deleted ML card are managed incorrectly. The following issues are observed:
•
•
At the end of the process, the ML card is added or deleted from the RPR ring.
Note
CSCsl09775
NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
Note
CSCsl12064
ONS 15454 SDH NEs do not go into In Service state after upgrading from CTM R7.0 to R8.0 and then to R8.5. The ONS 15454 SDH network service reloads every 10 to 20 minutes.
Note
CSCsl12277
When exporting the database from CTM R7.0 to R8.0, the export fails with critical error messages that are similar to the following:
EXP-00056: ORACLE error 904 encounteredORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalididentifier. . exporting table DEF$_AQCALL 0 rows exportedNote
CSCsl23824
The Oracle database does not shut down correctly when the CTM server shuts down. This can cause physical damage to the disk or other severe Oracle performance problems.
Note
CSCsl26312
The Enable SysAdmin parameter in the Control Panel is set to the wrong default value after migrating from CTM R8.0 to R8.5.
Note
CSCsl28305
Unable to determine the status of the database when the migration or export operation fails.
Note
CSCsl46302
Some MGX test cases fail after installing the patch that fixes CSCsk44773 and upgrades the Apache web server to R2.0.61.
Note
CSCsl47537
PM pruning fails.
Note
CSCsl48499
Cannot see the files while backing up the memory.
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
The alarm ID and time stamp are assigned a new alarm ID and time stamp in the Alarm Browser when the node is marked as Out of Service and then In Service. The alarm notes are also lost.
Note
CSCsm21463
The Circuit table does not show port names for circuits on E1-42 cards (on the source or destination NE) and STM1 cards (on the destination NE).
Note
CSCsm84722
Cannot install CTM patches in a dual-server setup.
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
On a migrated setup, you cannot delete or modify the drops associated with a custom QoS profile that was created in CTM R5.0. Also, you cannot delete or modify any VLANs associated with those drops.
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
CSCso52471
When you run the script server_patch.sh on the CTM server, the following error message appears in the servepatch.log file:
ERROR at line 1: ORA-00001: unique constraint (CTMANAGER.OPERATION_PERMISSION_PK) violated ORA-06512: at line 8 Table dropped.
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
CSCsq87850
SVLAN ports are not displayed correctly.
Note
CSCsq88110
A traffic loss occurs after modifying SVLAN port information.
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
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
CSCsr16276
The Veritas Cluster Server HA agent does not work with Apache version 2.0.63.
Note
CSCsr53609
A CTM server core dump file is created when the CTM server shuts down.
Note
CSCsw88229
When you start the CTM client in Debug mode and then choose Administration > Memory Backup, the client hangs and an error message appears in the console window where you entered the ./ctmcdebug-start command.
Note
CSCsw98539
Cannot set signal degrade (SD) and signal failure (SF) values for low-order (LO) circuits. (Related caveat ID: CSCsh64456)
Note
CSCuk57153
Cannot launch CTC from CTM on an ONS 15305 R3.0 NE.
CSCuk58334
Intermediate path performance monitoring (IPPM) information does not refresh correctly in the ONS 15454 SONET and ONS 15454 SDH NE Explorer windows.
Installing the CTM R8.0.0.912.1 Patch
Note
•
This section describes how to download and install the CTM R8.0.0.912.1 patch, which fixes the following caveats:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
•
•
•
•
•
•
•
•
•
M c04 DENYPIUI"Privilege, Illegal User Identity"/*Gateway Login To NE Failed */•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
•
•
•
–
–
At the end of the process, the ML card is added or deleted from the RPR ring.
•
•
•
EXP-00056: ORACLE error 904 encounteredORA-00904: "SYS"."DBMS_EXPORT_EXTENSION"."FUNC_INDEX_DEFAULT": invalididentifier. . exporting table DEF$_AQCALL 0 rows exported•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ERROR at line 1: ORA-00001: unique constraint (CTMANAGER.OPERATION_PERMISSION_PK) violated ORA-06512: at line 8 Table dropped.•
•
•
•
•
•
•
•
•
•
•
•
•
•
CTM R8.0.0.912.1 is intended for customers who are currently using CTM R8.0.0.856, R8.0.0.857.2, R8.0.0.859.2, R8.0.0.863.3, R8.0.0.867.1, R8.0.0.871.4, R8.0.0.875.3, R8.0.0.877.1, R8.0.0.890.1, R8.0.0.905.3, or R8.0.0.907.3.
Note
•
Complete the following procedures to upgrade to the CTM R8.0.0.912.1 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, make sure that the output results to one of the following:
•
•
•
•
•
•
•
•
•
•
•
Backing Up the CTM Database Before Installing the CTM R8.0.0.912.1 Patch
Before installing the CTM R8.0.0.912.1 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.0 User Guide:
•
•
Downloading the CTM R8.0.0.912.1 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 CTM8.0.0.912.1.patch.zipFor example, to extract the file to the /temp directory, enter:
cd /tempunzip CTM8.0.0.912.1.patch.zipThis creates a directory called 912, which contains all of the patch-related files.
Step 12
cd 912Step 13
a.
b.
c.
d.
e.
Installing the CTM R8.0.0.912.1 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 make sure that all user sessions are terminated.
Step 4
ctms-stopStep 5
./server_patch.shStep 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.0 Build: 912 Patches: 1Step 8
Installing the CTM R8.0.0.912.1 Client Patch in Windows
Note
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: 8.0 Build: 912 (client configuration size)•
8.0 [8.0.0.912]Step 5
Installing the CTM R8.0.0.912.1 Client Patch in Solaris
Note
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: 8.0 Build: 912 (client configuration size)•
8.0 [8.0.0.912]Step 5
Open Caveats
The following sections describe the caveats that are not resolved in the CTM R8.0 software:
•
•
–
–
–
–
–
–
Note
Installation and Upgrade Caveats
•
Symptom The installer displays a warning message that the resolve.conf file is missing and then exits.
Conditions
Workaround
Step 1
vi /etc/resolve.confStep 2
Step 3
•
Symptom The file system becomes full when you repeatedly cancel an upgrade process and then restart it.
Conditions
Workaround
If you cancelled the upgrade, you should:
Step 1
Step 2
Step 3
Step 4
Step 5
•
Symptom The CTM server does not come up after the machine is restarted. When you enter the ctms-start command, it returns the error message "The CTM server is already running."
Conditions
Workaround
•
Symptom The CTM client uninstalls after displaying a warning message.
Conditions
Workaround
•
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 the Partitioning, 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 with Upgrade•
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 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.
Conditions
Workaround
•
Symptom After upgrading to CTM R8.0, you cannot set the TL1 Tunnel Connection Timeout value in the Control Panel window.
Conditions
Workaround
•
Symptom After upgrading to CTM R8.0, users associated with custom CTM profiles cannot log into the CTM server.
Conditions
Workaround
•
Symptom 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.
Conditions
Workaround
•
Symptom If you install a CTM client patch for Windows and the directory path contains special characters, the client_patch.bat script fails and you cannot launch CTC from the CTM client.
Conditions
The Control Panel and the About dialog box show the CTM client version as 0.0. You cannot launch CTC from the CTM client.
Workaround
•
Symptom When you run the /cdrom/cdrom0/ctmc/CopyUpgradeFiles.sh script, it copies the Solaris client upgrade files and then prompts you for a second CD. However, there is only one client CD for both the Solaris and Windows clients.
Conditions
Workaround
•
Symptom The CopyUpgradeFiles.sh script fails with the following message:
Copying the client upgrade files can take several minutes.Copying CTM client upgrade files...Copying Solaris client upgrade filesSolaris client upgrade files copiedNo default media availableERROR: CDROM device busy.., please quit other session accessing CD ROMUpgrade is abort, please run it again after fix CD ROM issueConditions
Workaround
•
Symptom The CTM server patch installs successfully, yet the following warning messages are generated:
Starting install for CTM server patch <patch_number>...Current CTM version detected as: <version_number>Optical module has been installed on this server.Patching files...cp: cannot create /opt/CiscoTransportManagerServer/cwm/svplus/bin/ooemc: No such file or directorychmod: WARNING: can't access /opt/CiscoTransportManagerServer/cwm/svplus/bin/ooemccp: cannot create /opt/CiscoTransportManagerServer/cwm/svplus/xml/ruledata.xml: No such file or directorychmod: WARNING: can't access /opt/CiscoTransportManagerServer/cwm/svplus/xml/ruledata.xmldone.Server patch installed successfully!Conditions
Workaround
•
Symptom CTM R8.0 must support a new JRE version. This caveat replaces CSCsj41105.
Conditions
Workaround
•
Symptom 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.
Conditions
Workaround
•
Symptom Due to security issues, CTM must support Apache web server version 2.0.61.
Conditions
Workaround
•
Symptom When installing the CTM server on the CTM server workstation, the installation fails when you select the CTM server and CTM GateWay/CORBA at the Select Products to Install screen.
Conditions
Workaround
•
Symptom Upgrading to CTM R8.0 fails after installing the CTM R7.0.0.405.1 patch or later. Upgrading to CTM R8.0 also fails after installing the CTM R7.2.0.199.1 patch or later.
Conditions
Workaround
•
Symptom Unable to determine the status of the database when the migration or export operation fails.
Conditions
Workaround
•
Symptom Some MGX test cases fail after installing the patch that fixes CSCsk44773 and upgrades the Apache web server to R2.0.61.
Conditions
•
•
•
•
Workaround
cp -R -P /opt/CiscoTransportManagerServer/webServer.orig/cgi-bin /opt/CiscoTransportManagerServer/webServercp -R -P /opt/CiscoTransportManagerServer/webServer.orig/htdocs/CWMClient /opt/CiscoTransportManagerServer/webServer/htdocs•
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 The following error message appears after clicking the Upload Log Files button in the Control Panel > Logging Properties > General tab: "Error reading Configuration Properties from Server..."
Conditions
Workaround
•
Symptom The following invalid CTM views are seen when the database is upgraded from CTM R6.0 to CTM R8.0 and only optical modules are installed on CTM R8.0:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Conditions
select object_name from dba_objects where status='INVALID';Workaround
su - oraclesqlplus ctmanager/ctm123!drop view <view_name>exitexit•
Symptom Upgrading the CTM server workstation from CTM R8.0 to R8.5 fails. 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 Veritas Cluster Server HA agent does not work with Apache version 2.0.63.
Conditions
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
Step 1
which javaThe command output is similar to:
/bin/javaStep 2
ls -ltra /bin/javaThe command output is similar to:
lrwxrwxrwx 1 root root 25 Sep 2 22:12 /bin/java -> /opt/jre1.5.0_X/bin/javawhere X is typically 12, 15, or 16, depending on the JRE patch version you are using.
Step 3
ln -s <target_Java_binary_location> /bin/javaFor example, if the target binary location is /opt/jre1.5.0_15/bin/java, enter:
ln -s /opt/jre1.5.0_15/bin/java /bin/javaStep 4
ls -ltra /bin/javane•
Symptom When you apply the CTM R8.0.0.907.3 service pack on a migrated CTM R7.0 system, the following SQL error is returned:
sqlplus.out ERROR at line 1: ORA-00955: name is already used by an existing objectConditions
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 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 A mismatch alarm is raised incorrectly from 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 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 When an alarm is cleared, it disappears from the Alarm Browser and is not visible in the Alarm Log, even though automatic alarm acknowledgement is enabled in the Control Panel > UI Properties pane.
Conditions
This problem occurs when automatic alarm acknowledgement and automatic pruning of fault management (FM) data are enabled. To check whether your system is affected by this problem, enter the following SQL command on the CTM database:
SQL> select * from ACK_TABLE where ACKINDEX=-1;If the query returns zero records, your system is affected by this problem.
Workaround
SQL> insert into ACK_TABLE values (-1, 'CTM', '', 1);SQL> commit;This problem might reappear when the next FM pruning occurs. Repeat this workaround to restore Alarm Log functionality.
•
Symptom The alarm ID and time stamp are assigned a new alarm ID and time stamp in the Alarm Browser when the node is marked as Out of Service and then In Service. The alarm notes are also lost.
Conditions
Workaround
•
Symptom CTM retrieves old and new alarms that are identical when a node is marked as Out of Service and then In Service. The same problem occurs when the NE service is restarted.
Conditions
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
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 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 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 After upgrading from CTM R6.0, the Link Validity value changes from Valid to Invalid for some links between ONS 1580x NEs or between an ONS 15454 and an ONS 1580x NE.
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 The Circuit table updates continuously and discovers sections of the network that are not in its selection context.
Conditions
•
•
•
•
Workaround
•
Symptom The Circuit table does not display the port name for DS3E, DS3XM, and DS3XM_12 cards.
Conditions
Workaround
•
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 Cannot create an OTS patchcord link when the source NE contains only OSC_CSM cards.
Conditions
•
•
The link creation fails with the error message "EID-739: Cannot retrieve possible link sizes or link protection information."
Workaround
•
Symptom The Circuit table displays TL1 circuits incorrectly.
Conditions
Workaround
•
Symptom CTM and CTC do not discover server trail links that are created in opposite directions.
Conditions
Workaround
•
Symptom Unable to manually route LO VCAT circuits between ONS 15305 NEs.
Conditions
Workaround
•
Symptom Two circuits have the same name in the Circuit table.
Conditions
Workaround
•
Symptom The Circuit table does not display some TL1 circuits.
Conditions
Workaround
•
Symptom The CTM GateWay/CORBA API getAllTopologicalLinks does not retrieve server trail links.
Conditions
Workaround
•
Symptom A database timeout occurs when you retrieve circuits from the Link table and no circuits are displayed on the Link table. An error message appears.
Conditions
Workaround
•
Symptom The Circuit Span table displays circuit spans incorrectly.
Conditions
Workaround
•
Symptom 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.
Conditions
Workaround
•
Symptom Some circuits remain in Partial state after network discovery is complete.
Conditions
Workaround
•
Symptom The Circuit table does not contain the expected circuits.
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 show port names for circuits on E1-42 cards (on the source or destination NE) and STM1 cards (on the destination NE).
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 The Circuit table loses values for the following fields:
•
•
•
•
•
Conditions
Workaround
•
Symptom The Circuit table loses values for the following fields:
•
•
•
•
•
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 Cannot set SD and SF values for low-order circuits.
Conditions
Workaround
•
Symptom In the Create Circuit wizard, tunnel links are not available for VT circuit routing.
Conditions
Workaround
User Management
Guest
