Table Of Contents
Release Notes for Cisco Transport Manager Release 9.0
New Features and Functionality
CTM-Supported NE Software Releases
Adding the ONS 15305 R2.0.2 to the Supported NE Table
Third-Party Patches and Security Notices
CTM-Supported JRE and Apache Versions
Installing the CTM R9.0.0.604.2 Patch
Determining What CTM Patch Is Currently Installed in the CTM System
Backing Up the CTM Database Before Installing the CTM R9.0.0.604.2 Patch
Downloading the CTM R9.0.0.604.2 Patch
Installing the CTM R9.0.0.604.2 Server Patch
Installing the CTM R9.0.0.604.2 Client Patch in Windows
Installing the CTM R9.0.0.604.2 Client Patch in Solaris
Installation and Upgrade Caveats
CTM Server and Database Caveats
Cisco Transport Controller Caveats
Cisco ONS 15302 and Cisco ONS 15305
Cisco ONS 15327, Cisco ONS 15454 SDH, and Cisco ONS 15454 SONET
Cisco ONS 15454 MSPP and Cisco ONS 15454 MSTP
Cisco ONS 15600 SONET and Cisco ONS 15600 SDH
Cisco ONS 15800, Cisco ONS 15801, and Cisco ONS 15808
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Transport Manager Release 9.0
November 10, 2009
These release notes describe the caveats for Cisco Transport Manager (CTM) Release 9.0. These release notes accompany the Cisco Transport Manager Release 9.0 User Guide and the Cisco Transport Manager Release 9.0 Installation Guide.
Note
You can access the most current Cisco documentation, including these release notes, online at http://www.cisco.com/en/US/products/sw/opticsw/ps2204/tsd_products_support_series_home.html.
Contents
These release notes contain the following sections:
•
•
•
•
•
•
Introduction
Cisco Transport Manager is an advanced management system that provides functionality at the element and network management levels for Cisco optical network elements (NEs) and switches. CTM supports fault, configuration, performance, and security management functional areas. CTM also serves as a foundation for integration into a larger overall Operations Support System (OSS) environment by providing northbound gateway interfaces to higher layer management systems.
In Release 9.0, CTM supports the Cisco Optical Networking System (ONS) family of optical NEs, the Cisco MGX 8880 Voice Gateway and MGX 8850/8830 Voice-Enabled Multiservice Switch, and the Cisco MDS 9000 Multilayer Director and Fabric Switch.
New Features and Functionality
The following table describes the new features and functionality in CTM R9.0.
Table 1-1 New Features in CTM R9.0
Database migration from:
•
•
You can upgrade your CTM installation and migrate database information from CTM R8.0.x or R8.5.x to R9.0.
Support for up to 4000 NEs in a high-end configuration
In CTM R8.5, the CTM server could support up to 3000 optical NEs in a high-end configuration. In CTM R9.0, the server supports up to 4000 optical NEs.
External authentication with RADIUS support
Enables the CTM server to use the Pluggable Authentication Module (PAM) Solaris library for authentication against RADIUS access servers. In the Security Properties pane of the Control Panel, you can enable external authentication and choose PAM RADIUS as the authentication tool.
IPv6 support between the CTM server and ONS 15000 devices
CTM provides IPv6 support for the following NE releases:
•
•
•
•
•
•
•
Note
Configuring SNMPv3 on CTC-based NEs
CTM discovers, updates, and provisions SNMPv3 NE tables on CTC-based NEs. SNMPv3 offers the following benefits:
•
•
•
•
•
•
•
You can configure SNMPv3 on the following CTC-based tables:
•
•
•
•
•
If the CTC-based NE is configured as a proxy, you can configure SNMPv3 on these additional tables:
•
•
•
Qualification of new T5120 and T5220 Sun servers
The CTM server runs on Sun T5120 and T5220 servers.
Report CTM server availability
You can view current and historical information about NE and PM services.
•
•
Enable or disable CTM server logging
In the Logging Properties pane of the Control Panel, you can enable or disable CTM server logging without affecting the logging operation on other services.
Memory restore displayed in chronological order
In the Memory Restore dialog box > Source area, you can choose Local to retrieve the backup file from the CTM client workstation, or Server to retrieve the backup file from the CTM server workstation.
If you choose the Server radio button, the backup files are listed in chronological order, with the most recent backup file displayed at the top of the list.
The backup file uses the following naming convention:
<NE_model>-<date><time>-backup.cfg
where:
•
•
For example, a valid backup filename is Cisco_ONS_15454-20090201144911-backup.cfg.
Designated SOCKS servers
You can enable or disable designated SOCKS servers on CTC-based NEs.
Cleared alarms in debug log1
When a database exception occurs, cleared alarms are dumped into the debug log.
Support for CTC-based NE Release 9.0
Expands CTM's scope to include operations, administration, management, and provisioning (OAM&P) for the following CTC-based NE releases:
•
•
•
•
•
•
•
ONS 15454 multishelf NEs support up to 12 shelves and racks
In previous CTM releases, a multishelf NE could support up to 8 shelves and racks. In CTM R9.0, a multishelf NE supports up to 12 shelves and racks.
Support for new optical cards
CTM manages the following new cards on optical devices:
•
•
•
•
•
•
•
•
Ability to apply protection to ports in a splitter protection group
In the Circuit Trace window, a new right-click menu option allows you to apply protection to the ports in a splitter protection group.
This feature applies to OCHCC, OCHTRAIL, and OCHNC circuits that use optical protection.
Ability to download software and back up or restore the database to an ENE with firewall enabled
You can configure database backup and restore, and software download to an ENE when proxy/firewall is enabled. CTM lets you provision up to 12 legal FTP hosts that will expire after a configurable amount of time. You can use the Bulk FTP Hosts Configuration feature to create an FTP host in a GNE/ENE firewall environment for multiple NEs simultaneously.
Support for new DS1 line length values on DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards on ONS 15310 MA SONET R9.0.1 and later NEs2
CTM supports the new DS1 line length values on DS1-28/DS3-EC1-3 and DS1-84/DS3-EC1-3 cards:
•
•
•
•
Note
Tracing of incomplete circuits
CTM allows you to trace circuits in Partial state. A circuit trace report is generated for partial circuits that have the source and destination node information.
Zoom levels are available in the Circuit Trace window
CTM allows you to zoom in or zoom out on the Circuit Trace window.
High-level circuit trace
In the High-Level Circuit Trace window, a graphic map uses high-level span information such as NEs and links to display the circuit trace.
Support for grouping during circuit provisioning
The new Graphical Enhanced radio button in the Routing Preferences pane of the Circuit wizard provides top-level and detailed views of the circuit map.
The top-level view displays the subnetworks or groups involved in the CTM system. You can expand the top-level views by right-clicking a subnetwork or group icon and choosing View from the shortcut menu. A detailed view of the circuit map appears and displays the nodes and links that belong to the specific subnetwork or group. From the detailed view, you can select the nodes and links that you need for provisioning the circuit. You can also collapse a detailed view by clicking the Top View button. The circuit map reverts to the top-level view.
Ability to expand or collapse link objects during manual circuit provisioning
While provisioning manual circuit routing in the Create Circuit wizard, you can right-click a link or link bundle in the map view and choose Expand or Collapse from the shortcut menu. If you choose Collapse, the links are hidden and the link bundle is displayed. If you choose Expand, the link bundle is hidden and the links are displayed.
The color of the link bundle represents the link selection status, which has the following order of priority (from highest to lowest):
•
•
•
•
•
The link bundle tooltip reports the number of links in the bundle and the name of each link. The background color of each link name in the tooltip represents the link selection status.
Support for open-ended VCAT circuits
CTM R9.0 supports open-ended virtual concatenation (VCAT) circuits that originate on Ethernet or ML-series cards. The destination can be OC-n or STM-n cards. You can route open-ended VCAT circuits to or from any of the cards or ports where VCAT circuits originate or terminate. Compared to a standard VCAT circuit, an open-ended VCAT circuit has only one virtual concatenation group (VCG).
Support for service provider VLANs (SVLANs)
A new Create SVLAN wizard allows you to configure SVLANs on GE_XP or 10GE_XP cards on ONS 15454 SONET and ONS 15454 SDH R9.0 NEs.
ML card bulk configuration download
Downloads the base card configuration (BCC) barebone file to multiple ML-series cards on the following NEs:
•
•
•
•
•
IEEE 802.3ad link aggregation
CTM R9.0 supports IEEE 802.3ad link aggregation, which allows one or more links to be aggregated into a single link aggregation group. Link aggregation provides link protection, increased bandwidth, increased availability, and load balancing across multiple links. The standard also defines the Link Aggregation Control Protocol (LACP), which is used to configure and control the link aggregation sublayer. LACP provides the ability to continuously monitor the configuration and take appropriate reconfiguration actions.
CTM allows users with the appropriate permissions to select the link aggregation methods. You can see all of the interfaces that belong to a link aggregation group, plus the aggregation method provisioned.
To support link aggregation, CTM supports Ethernet channel configuration on a per-card basis.
VLAN mirroring on standby cards
VLAN services that are provisioned on the working/active ML cards are automatically provisioned on the protect/standby ML cards.
Support for new MGX Voice Gateway releases
Expands CTM's scope to include OAM&P for the following MGX releases:
•
•
•
•
Support for media gateway overload notification on VXSM cards
CTM reports how many calls per second are running in the system. At the VXSM card level, the Resource Control tab contains a Gateway Resource Utilization category. When you select this category, all of the supported resources are selected in the configuration table. The Real-Time Statistics table displays the following statistics:
•
•
•
Select a specific resource and the real-time statistics to retrieve the current values for that resource.
Reporting of card uptime
In the VXSM Card tab > Front Card Configuration category of the Configuration Center, CTM reports uptime for the following MGX cards:
•
•
•
•
•
•
•
VXSM circuit description
In the Configuration Center, you can configure the circuit identifier on the following VXSM cards:
•
•
•
•
Support for super G3 fax spoofing on VSXM cards
Enables or disables fax negotiation spoofs that automatically force Super Group 3 (SG3) fax machines to send faxes over T.38 Group 3 (G3) modulations. You can enable or disable this feature on VXSM cards in the Configuration Center (VXSM Card tab > VBD tab > Fax Relay Profile).
Number of active and emergency calls in progress
In the Diagnostic Center, the Resource Control tab > Call Statistics subtab lists the number of active and emergency calls in an H.248 setup. When the VXSM card is configured for Media Gateway Control Protocol (MGCP) or Trunking Gateway Control Protocol (TGCP), only active calls are listed in the Real Time Statistics table.
Out-of-service and in-service trunks at the E1 level
You can configure the service state of a path or line to down, even if a time-division multiplexing (TDM) configuration exists for that particular path or line. In this way you can prevent the VXSM card from detecting and generating statistical alarms on the TDM configuration.
Diagnostic Center display for DSPCODECPOOLS
In the Diagnostic Center, the Resource Control tab > Codec Pool Stats subtab lists the available coder-decoder (codec) pools with real-time statistics on available and utilized DSP channels.
MGX SFTP support
CTM supports Secure File Transfer Protocol (SFTP) to upload and download configuration and statistics files from MGX devices. With SFTP, all data is encrypted and is safe from interception. The encryption is unique to the SFTP session, making data decryption extremely unlikely. User credentials determine SFTP access.
Support for Daylight Saving Time on MGX devices
You can use the CTM GUI to enable or disable Daylight Saving Time (DST) and configure DST settings on MGX devices. You can enable or disable this feature by selecting a node in the Domain Explorer tree and choosing Configuration > MGX Voice Gateway > Configuration Center > Daylight Savings tab.
Support for SSHv1, FTP, and Telnet access
You can use the CTM GUI to enable or disable SSHv1, FTP, or Telnet access to a switch. You can enable or disable this feature by selecting a node in the Domain Explorer tree and choosing Configuration > MGX Voice Gateway > Configuration Center. In the Node tab, choose the applicable options in the SSHv1, FTP, or Telnet field.
Proactive detection of data path failure for RPM-XF cards
The RPM-XF card runs a data path check (DPC) on the active and standby cards to detect the health of the data path. The results of the RPM-XF data path check are communicated to CTM through traps, and the alarms are displayed in the Alarm Browser.
Support for AnnexAB
You can enable AnnexAB features by choosing Configuration > MGX Voice Gateway > Configuration Center > H.248 tab and selecting the appropriate option under the Profile Undotted Notation or Profile Annexab Enabled field.
Support for SMS detection
You can create event mapping with the event type SMS. You can enable this feature by choosing Configuration > MGX Voice Gateway > Configuration Center > VBD tab and selecting SMS under the Event Index field.
1 This feature is available only after installing the CTM 9.0.0.604.2 or later patch. See Installing the CTM R9.0.0.604.2 Patch.
2 Support for new DS1 length values is available only after installing the CTM 9.0.0.604.2 or later patch. See Installing the CTM R9.0.0.604.2 Patch.
Changes to the Release Notes
This section documents supplemental changes that have been made since the initial release of the Release Notes for Cisco Transport Manager Release 9.0.
Sections and Caveats Added
The following sections and caveats were added to the release notes:
•
•
•
The following section was removed from the release notes:
•
NE Software Releases Added
The following NE releases were added to Table 2, "CTM Supported NE Software Releases":
•
–
–
–
–
–
–
–
•
–
CTM-Supported NE Software Releases
The following table lists the NE software releases supported in CTM R9.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, soadmb.out-Ver2.2.2
Release 2.2.3
soadma.out-Ver2.2.3, soadmb.out-Ver2.2.3
ONS 15216 200-GHz OADM1/2
Passive
1.0
ONS 15216 DCU
Passive
2.0
ONS 15216 DWDM Filter (including ONS 15216 100-GHz Red/Blue Filters and ONS 15216 200-GHz Red/Blue Filters)
Release 2.1
2.1
ONS 15216 EDFA1
Passive
1.0
ONS 15216 EDFA2
Release 2.3
v2.3.0
Release 2.4
v2.4.0
ONS 15216 EDFA3
Release 1.1
01.01.00
ONS 15216 FlexLayer
Passive
1.0
ONS 15216 OSC
Passive
2.0
ONS 15302
Release 2.0.2
2.0.2
ONS 15305
Release 2.0.21
2.0.2
Release 2.0.3
2.0.3
ONS 15305 CTC
Release 3.0.5
04.60-X06F-28.14
Release 3.0.6
04.60-X08D-26.11
ONS 15310 CL
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.0.3
06.03-007D-06.05
Release 6.2
06.20-006C-17.10
Release 6.2.2
06.22-006F-23.21
Release 7.0
07.00-005L-19.20
Release 7.0.2
07.02-006I-06.16
Release 7.0.4
07.04-007A-08.16
Release 7.0.5
07.05-007D-20.22
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-08.19
Release 7.2.3
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
Release 8.5
08.50-007I-19.18
Release 8.5.1
08.51-008B-14.13
Release 9.0
09.00-008I-17.17
Release 9.0.12
09.01-009F-20.11
ONS 15310 MA SONET
Release 7.0
07.00-005L-19.20
Release 7.0.2
07.02-006I-06.16
Release 7.0.4
07.04-007A-08.16
Release 7.0.5
07.05-007D-20.22
Release 7.0.7
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-08.19
Release 7.2.3
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
Release 8.5
08.50-007I-19.18
Release 8.5.1
08.51-008B-14.13
Release 8.5.3
08.53-008J-17.07
Release 9.0
09.00-008I-17.17
Release 9.0.13
09.01-009F-20.11
ONS 15310 MA SDH
Release 9.0
09.00-008I-17.17
Release 9.0.14
09.01-009F-20.11
ONS 15327
Release 4.1.4
04.14-004C-09.23
Release 4.1.82
04.182-006-L2805
Release 4.6.6
04.66-005K-09.00
Release 5.0.4
05.04-005G-13.18
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.0.3
06.03-007D-06.05
Release 6.2
06.20-006C-17.10
Release 6.2.2
06.22-006F-23.21
Release 7.0
07.00-005L-19.20
Release 7.0.2
07.02-006I-06.16
Release 7.0.4
07.04-007A-08.16
Release 7.0.7
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-08.19
Release 7.2.3
07.23-007F-22.02
ONS 15454 SONET
Release 4.1.4
04.14-004C-09.23
Release 4.1.6
04.16-004I-10.23
Release 4.1.82
04.182-006-L2805
Release 4.6.2
04.62-004E-23.20
Release 5.0.2
05.02-005C-26.23
Release 5.0.6
05.06-005H-29.19
Release 5.0.8
05.08-006J-16.07
Release 6.0
06.00-005H-18.21
Release 6.0.1
06.01-005L-10.05
Release 6.0.3
06.03-007D-06.05
Release 6.2
06.20-006C-17.10
Release 6.2.2
06.22-006F-23.21
Release 7.0
07.00-005L-19.20
Release 7.0.1 (MSTP only)
07.01-006D-20.20
Release 7.0.2
07.02-006I-06.16
Release 7.0.3 (MSTP only)
07.03-006I-29.09
Release 7.0.4
07.04-007A-08.16
Release 7.0.5
07.05-007D-20.22
Release 7.0.6 (MSTP only)
07.06-007H-08.13
Release 7.0.7
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-15.13
Release 7.2.3
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
Release 8.5
08.50-007I-19.18
Release 8.5.1
08.51-008B-14.13
Release 8.5.2
08.52-008E-25.04
Release 8.5.3
08.53-008J-17.07
Release 9.0
09.00-008I-17.17
Release 9.0.15
09.01-009F-20.11
ONS 15454 SDH
Release 4.6.2
04.62-004E-23.20
Release 5.0.2
05.02-005C-26.23
Release 5.0.6
05.06-005H-29.19
Release 6.0
06.00-005H-18.21
Release 6.0.1
06.01-005L-10.05
Release 6.0.3
06.03-007D-06.05
Release 6.2
06.20-006C-17.10
06.20-P06C-17.10
Release 6.2.2
06.22-006F-23.21
Release 7.0
07.00-005L-19.20
Release 7.0.1 (MSTP only)
07.01-006D-20.20
Release 7.0.2
07.02-006I-06.16
Release 7.0.4
07.04-007A-08.16
Release 7.0.5
07.05-007D-20.22
Release 7.0.7
07.07-007L-03.20
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-15.13
Release 7.2.3
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
Release 8.0.2
08.02-008G-17.16
Release 8.5
08.50-007I-19.18
08.50-P07I-19.18
Release 8.5.1
08.51-008B-14.13
Release 8.5.2
08.52-008E-25.04
08.52-P08E-25.04
Release 8.5.3
08.53-008J-17.07
Release 9.0
09.00-008I-17.17
Release 9.0.16
09.01-009F-20.11
ONS 15501
Release 4.1 AC
4.1
Release 4.1 DC
4.1
ONS 15530
Cisco IOS Release 12.2(29)SV3
12.2(29)SV3
Cisco IOS Release 12.2(30)S
12.2(30)S
ONS 15540 Extended Services Platform (ESP)
Cisco IOS Release 12.2(29)SV3
12.2(29)SV3
Cisco IOS Release 12.2(30)S
12.2(30)S
ONS 15540 Extended Services Platform with external cross-connect capability (ESPx)
Cisco IOS Release 12.2(29)SV3
12.2(29)SV3
Cisco IOS Release 12.2(30)S
12.2(30)S
ONS 15600 SONET
Release 5.0.8
05.08-006J-16.07
Release 6.0.1
06.01-005L-10.05
Release 6.2.4
06.24-006L-15.00
Release 7.0
07.00-005L-19.20
Release 7.0.4
07.04-007A-08.16
Release 7.2
07.20-006E-04.17
Release 7.2.2
07.22-007B-08.19
Release 7.2.3
07.23-007F-22.02
Release 8.0
08.00-007A-27.16
Release 9.0
09.00-008I-17.17
Release 9.0.17
09.01-009F-20.11
ONS 15600 SDH
Release 1.4
01.40-004A-15.18
Release 8.0
08.00-007A-27.16
Release 9.0
09.00-008I-17.17
Release 9.0.18
09.01-009F-20.11
ONS 15800
Release 2.1 (TL1 Agent Release 2.1)
2.1
ONS 15801
Release 2.1 (TL1 Agent Release 2.1)
2.1
ONS 15808
Release 2.2 (TL1 Agent Release 2.4)
2.4
Cisco MDS 9000
MDS 9000 family, including MDS 9100, MDS 9200, MDS 9500, Port Analyzer Adapter, and Storage Networking Module
—
Cisco MGX 8880 Media Gateway
Release 5.3.10
5.3.10
Release 5.3.20
5.3.20
Release 5.4.10
5.4.10
Release 5.4.30
5.4.30
Release 5.5.00
5.5.00
Voice-Enabled Cisco MGX 8830 Multiservice Switch
Release 5.3.10
5.3.10
Release 5.3.20
5.3.20
Release 5.4.10
5.4.10
Release 5.4.30
5.4.30
Release 5.5.00
5.5.00
Voice-Enabled Cisco MGX 8850 Multiservice Switch
Release 5.3.10
5.3.10
Release 5.3.20
5.3.20
Release 5.4.10
5.4.10
Release 5.4.30
5.4.30
Release 5.5.00
5.5.00
VISM-PR
Release 3.3.25
3.3.25
Release 3.3.30
3.3.30
Release 3.3.35
3.3.35
VXSM
Release 5.3.30
5.3.30
Release 5.4.209
5.4.20
Release 5.5.00
5.5.00
1 In order for CTM to support the ONS 15305 R2.0.2, you must add the software version to the Supported NE table. See Adding the ONS 15305 R2.0.2 to the Supported NE Table.
2 In order for CTM to support the ONS 15310 CL R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
3 In order for CTM to support the ONS 15310 MA SONET R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
4 In order for CTM to support the ONS 15310 MA SDH R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
5 In order for CTM to support the ONS 15454 SONET R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
6 In order for CTM to support the ONS 15454 SDH R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
7 In order for CTM to support the ONS 15600 SONET R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
8 In order for CTM to support the ONS 15600 SDH R9.0.1, you must install the CTM 9.0.0.604.2 patch. See Installing the CTM R9.0.0.604.2 Patch.
9 VQM is supported in VXSM R5.4.20.
Adding the ONS 15305 R2.0.2 to the Supported NE Table
In order for CTM to support the ONS 15305 R2.0.2, you must add the software version to the Supported NE table. Complete the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Third-Party Patches and Security Notices
Cisco reviews the known Oracle patch alerts every quarter, including patches for security breaches. If any Oracle patch applies to CTM or its components, Cisco tests the Oracle patch and includes it as a requirement for the next CTM patch. Cisco also conducts quarterly reviews of other third-party software products that CTM uses, such as Solaris, Apache, and Java.
CTM-Supported JRE and Apache Versions
The following tables list the Java Runtime Environment (JRE) and Apache versions supported in CTM R9.0.
Table 3 CTM-Supported JRE Version
1.5.0_17
—
—
This JRE version was used when CTM R9.0 was released.
Resolved Caveats
The following table lists caveats that are resolved in CTM R9.0.
Table 5 Caveats Resolved in CTM R9.0
CSCse91332
CTM GateWay/CORBA does not send a notification event when a new network partition is created in CTM.
CSCse91435
CTM GateWay/CORBA does not send a notification event when an existing network partition is deleted from CTM.
CSCsg30824
CTM allows you to edit the PPM port rate from OC48 to OC3 when a server trail exists and contains an STS-6c port rate.
CSCsg86081
Unable to retrieve a J1 path trace on ONS 15600 SDH ASAP cards.
CSCsh32836
Cannot view the ML card's VLAN port IP address and corresponding NE and slot number after creating an L2 service.
CSCsh46506
The following problems are observed:
1.
2.
CSCsh69305
Active and standby ML cards are not shown when creating VLANs on 802.17 Resilient Packet Ring (RPR) topologies using the corresponding wizard.
CSCsi25561
When you change the CTM database password from the Database Properties pane of the Control Panel and the preliminary checks fail, the CTM server is not restarted, the database password is not changed, and you are notified of the proper EMS alarms. However, the following error message appears: "Caution: The database password has been changed by a user. The CTM server will restart in 15 seconds."
CSCsj01676
The Maximum Login Attempts alarm for an unknown user is not cleared if you set the Max Retries field in the Control Panel to one.
CSCsj19520
The CTM GateWay/CORBA log file archiving stops when the CTM GateWay/CORBA service or CTM server is restarted.
CSCsj54751
The CTM client user interfaces are dimmed for several minutes.
CSCsk00034
Unable to perform real-time statistics polling on connections that do not have statistics support on one end. The RPM endpoint has no real-time statistics support.
CSCsk19647
Each network partition has a limit of 500 NEs. If NEs are manually added and autodiscovered, and exceed the network partition limit, the NEs are added to the Domain Explorer but not to the network service. As a consequence, CTM cannot manage or connect to the NEs.
CSCsk27692
The Network Map occasionally displays a newly added L2 link in orange (indicating a major alarm), even though no alarms are reported in the Alarm Browser window.
CSCsk28808
Unable to select an alarm profile for interlink ports on SDH ADM_10G cards.
CSCsk44773
Due to security issues, CTM must support Apache web server version 2.0.61.
CSCsk48068
When you delete a VLAN from an L2 topology, the following error message appears: "Could not delete VLAN completely."
CSCsk50113
The CTM client disconnects from the CTM server.
CSCsk52250
The CTM client shows the wrong installation status of CTM GateWay/CORBA.
CSCsk53838
The Audit Trail table does not contain any entries for one or more nodes, or it stops collecting updates on the same nodes. The audit trail data is available in CTC.
CSCsk63579
NE alarms are not saved in the database and not displayed in the Alarm Browser and Alarm Log.
CSCsk68874
It takes too long for a newly created L2 topology to appear in the L2 Topology table.
CSCsk71257
The Change Card function does not change the card in the shelf, module, and tree views.
CSCsk78622
The VC3 value is zero in the Link Utilization table for VC3 port group circuits.
CSCsk80234
Some NEs are not visible in the Network Map.
CSCsk86875
Some 1-day PM buckets are missing.
CSCsk90677
In the Alarm Browser, an "Alarm Suppressed for Maintenance" alarm is displayed for an OPT-BST card and it cannot be cleared.
CSCsk96257
The CTM client freezes.
CSCsl03900
The APC Domain table is empty if you select a node that does not terminate an APC domain.
CSCsl06339
The notification service process restarts. When you use the showctm -v command, the start time of the notification service process is more recent than the start time of other processes. All other processes work correctly, including CTM GateWay/CORBA, which is based on the notification service.
CSCsl08269
A timeout operation occurs when you remove an ML card from an RPR topology. However, the ML card has been provisioned correctly.
CSCsl09775
NE_AUDIT_TRAIL_TABLE pruning fails and the logs are not collected in the /$ORACLE_HOME/admin/$ORACLE_SID/udump directory.
CSCsl11930
Oracle startup fails due to lack of memory after a dual-server installation. The following message appears:
SQL> ORA-27102: out of memory
SVR4 Error: 22: Invalid argument
(Related caveat ID: CSCsq58179)
CSCsl15115
There is a high CPU usage by the CTC-based network service. High CPU usage is normal during provisioning operations or when a large number of alarms is generated on NEs managed by the network service.
CSCsl17182
Unable to open or modify a TL1 tunnel.
CSCsl17291
Unable to create a manual link using CTM GateWay/CORBA.
CSCsl20872
Creating an L1 circuit fails and the following message appears: "EID-932: Failed to route the circuit. Details: client timeout reached."
CSCsl21987
Random CTM GateWay/TL1 CPU usage is higher than normal. It shows approximately 10% with peaks of up to 15%.
CSCsl22134
The following error message appears when creating an OCHNC circuit between NE R5.x and R6.x:
The selected NEs do not support bidirectional circuit creation.
CSCsl22172
The Ethernet PM table shows rxPackets and txPackets counters instead of the rxTotalPkts and txTotalPkts counters. The rxTotalPkts and txTotalPkts counter are shown as N/A.
CSCsl22236
Unable to add manually the following NEs to the CTM client:
•
•
•
•
•
•
If any of the preceding NE versions is previously added to the CTM client, you cannot connect to the NE and mark it as In Service.
CSCsl22254
Some L2 topologies are not displayed or they appear as split topologies in the Layer 2 Topology table.
CSCsl23871
Cannot monitor and provision the auto laser shutdown parameters on the OPT_PRE card. The Auto Laser Shutdown tab is not present in the NE Explorer.
CSCsl26070
Updated link cost and shared risk link group (SRLG) values are not available after migration.
CSCsl26218
The NE services freezes after adding 3000 NEs, deleting 30 NEs, adding a new topology with GNEs, and marking several NEs as Out of Service and then In Service.
CSCsl28305
Unable to determine the status of the database when the migration or export operation fails.
CSCsl31836
In the CTM Login dialog box, the text area with the legal disclaimer displays only 69 characters for each row; it should display 80 characters.
CSCsl34203
CTM GateWay/CORBA can retrieve Ethernet circuits using the CTP naming convention.
CSCsl34542
The upgrade from one CTM release to another CTM release fails due to an error in creating a primary key constraint on the ACTIVE_ALARM_TABLE.
CSCsl37025
The PM service restarts after several days. The error log contains a large number of errors associated with writing PM data to the database.
CSCsl37264
The ONS 15454 SDH NE Explorer shows the wrong battery names in slots 23 and 24.
CSCsl39284
Unable to create circuits on optical nodes that belong to the default Network Partition 1.
CSCsl43107
A background Java/Javaw process is opened and does not close when you close the CTM client. Every time the CTM client is opened, a new Java process is created. Therefore, if the CTM client is opened several times, several dangling Java processes are created.
CSCsl45830
CTM GateWay/TL1 restarts.
CSCsl48499
The backup files are not listed in the Backup File dialog box after choosing Administration > Memory Backup Upload in the Domain Explorer.
CSCsl95721
The Circuit table does now show port names for circuits on MRC-12 cards (on ONS 15454 R6.0.1 NEs) or MRC-4 cards (on ONS 15454 R8.0 NEs). The Circuit table shows incorrect port names for circuits on DS3 cards (on ONS 15454 R6.0.1 NEs).
CSCsm17261
When a node is marked as Out of Service and then In Service, the alarm ID and time stamp are assigned new values in the Alarm Browser. The alarm notes are also missing.
(Related caveat ID: CSCsq24237)
CSCsm21463
The Circuit table does not display the port name for E1-42 cards for source and destination NEs. Also, the Circuit table does not display the port name for STM-1 cards for destination NEs.
CSCsm64677
The restoreME application program interface (API) does not work correctly, so you cannot use CTM GateWay/CORBA to restore the managed element (ME) configuration file.
CSCsm99421
Connection termination point (CTP) values of alarms are printed when you run the getAllActiveAlarms API. But for certain alarms for which the affected object is VC4, the getAllActiveAlarms API prints the wrong CTP values.
CSCso01840
It takes a long time to discover NEs after the NE service restarts.
CSCso01900
The CTC-based NE service takes a long time to reconnect and discover NEs.
CSCso01942
CTM takes a long time to discover a large network of GNEs and ENEs.
CSCso07731
If you use textual routing to provision protected contiguous concatenation (CCAT) circuits, the operation might fail.
CSCso35202
On CTM R8.5, the Oracle shutdown script does not work while the server workstation is shutting down. On CTM R8.0 and R8.5, Oracle occasionally fails to start automatically while the CTM server workstation is starting, and then the CTM server does not start correctly.
CSCso44701
CTM memory backups fail when multiple MGX NEs are selected simultaneously. The Job Monitor displays the following message:
(Too many open files)
(No such file or directory)
CSCso51993
Manual links do not work correctly. In the Link table, circuits related to a specific link are not shown, and manual links are shown as not being used for routing.
CSCso76700
The CTM GateWay/CORBA NBI creates additional proxy consumers if you do not stop CTM GateWay/CORBA before executing the ctms-stop or ctms-start commands.
CSCso92358
Disabled tabs are enabled when performing operations in the navigation tree.
(Related caveat ID: CSCsk31966)
CSCsq24237
CTM retrieves old and new alarms that are identical when a node is marked as Out of Service and then In Service. The same problem occurs when the NE service is restarted.
CSCsq26342
The getHistoryPMData API takes longer than 15 minutes to return data.
CSCsq26362
The output file generated from getHistoryPMData returns duplicate rows.
CSCsq31631
Memory backup and memory restore fail on MGX nodes when Telnet is disabled.
CSCsq32073
Due to security issues, CTM must support Apache web server version 2.0.63.
CSCsq50589
In the Domain Explorer, you can set any password for CTM server-to-NE connections, because the password syntax is not verified correctly.
CSCsq65111
In the GW/TL1 Event Forwarding Discriminator table, the Alarm Reporting column contains incorrect values.
CSCsq78385
The SMService_port property generates a random value even if it is set to a fixed value.
CSCsq87850
SVLAN ports are not displayed correctly.
CSCsq89269
In the NE Explorer for a GE_XP card, if you click the SVLAN tab, the same tab appears when you select another GE_XP card.
CSCsq92344
After upgrading to CTM R8.5, all MGX NEs monitored by the CTM server report voltage sensor alarms against the VXSM card in slot 1. However, if you log into the chassis of the unit, there are no corresponding alarms on the gateway.
CSCsq94272
You cannot schedule a job after December 31, 2008, because the highest value allowed for the year is 2008.
CSCsr06975
In the NE Explorer for a GE_XP card, if you click the SVLAN tab, deselect all SVLANs, and click Apply, an error occurs.
CSCsr30785
The Alarm Browser displays MGX STM-1 interfaces incorrectly as AU3.
CSCsr48358
The prune_ne_ipaddress script does not work with IPv6 addresses.
Note
CSCsr53609
A CTM server core dump file is created when the CTM server shuts down.
CSCsr55311
When you filter alarms that have CTM as the affected object, the alarm does not appear in the Alarm Browser or Alarm Log.
CSCsr55335
Duplicate circuit names appear in CTM when a circuit name is updated in CTC.
CSCsr70191
When the system date is changed while the CTM server is running, the CTM server shuts down the NE, PM, and NBI services within five minutes.
CSCsu26103
The Supported NE table > Add Supported NE dialog box shows incongruous data.
CSCsu30979
If you try to modify a QoS profile on a VLAN drop, the operation fails with the following error message:
EID-874: Failed to modify some drops on the L2 service.
CSCsu50742
The Circuit table does not display the port name for STM1E_12 cards for source and destination NEs.
CSCsu54724
In the NE Explorer for a GE_XP card, the list of configured SVLANs is not available.
CSCsu68317
The northbound CORBA interface returns incorrect cross-connect table information. The getAllCrossConnections API returns a CTP name retrieved by a VC-12 circuit in the format /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.
Note
CSCsu82028
The APIs getTCATPPParams and setTCATPParams do not work for trunk ports on GE_XP and 10GE_XP cards.
CSCsu88218
When creating multiple STS circuits, an error is returned.
CSCsv12810
An MGX is added to a CTM server, but is not included in the Auto Backup process.
Note
CSCsv33266
If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
Note
CSCsw22308
VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with incorrect numbers, making it impossible to tell which VT the PM data is for.
Note
CSCsw68952
A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.Note
CSCsw72207
The Protection panel shows the wrong name for an OTU2_XP card.
Note
CSCsw91974
In a large network of GNEs and ENEs, CTM fails to collect PM data.
Note
CSCsx23360
An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle Enterprise Manager or the Alert Log.
Note
CSCsx22431
For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports the correct wavelength value.
Note
CSCsx26527
The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer do not exist.
Note
CSCsx38325
The first database export from the CTM GUI fails.
Note
CSCsx44115
The CTM server does not send SNMP traps or get IPv6 destinations. The following problems occur:
•
•
Note
CSCsx50126
Due to security issues, CTM must support Apache web server version 2.2.11.
Note
CSCsx50161
The Apache Tomcat software should be disabled to avoid potential security issues.
Note
CSCsx52433
From the MGX Voice Gateway Configuration Center, the Circuit Identifier field is blank for DS1 and SONET lines on a VXSM card. Also, utilization counters are not enabled in the Diagnostics Center > Resource Control tab.
Note
CSCsx55667
The getCTPsAndTopologicaLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
Note
CSCsx56687
The SPAN_BS_TABLE database table displays incorrect working and protected values.
Note
CSCsx64513
A warning message of a possible traffic impact appears when reconfiguring circuits. This warning message should not appear, because reconfiguring circuits does not affect traffic.
Note
CSCsx81985
During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05 directory.
Note
CSCsx93323
CTM displays a "Media Gateway Link state, pendingIs" alarm with a severity set to Warning. In other Element Managers, this type of alarm has a severity set to Major.
Note
CSCsy14909
A VLAN range cannot be added on a 10GE_XP/GE_XP card.
Note
CSCsy29600
CTM does not receive PM data from managed MGX devices.
Note
CSCsy30294
CTM fails to automatically route and create a STS-24c circuit to the 15454-ADM-10G card when entering a value in the Time Slot Restriction field.
Note
CSCsy56348
Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
Note
CSCsy83061
From the NE Explorer > SVLAN tab, GE_XP SVLAN configuration settings are not always applied for 8.0 NEs.
Note
CSCsy95336
CTM fails to reconfigure circuits on release 8.5 NEs.
Note
CSCsz33838
Cannot add drops on cards configured in Automatic mode.
Note
CSCsz53477
The Error Log contains multiple errors that are similar to the following:
CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290Note
CSCsz58653
Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
Note
CSCsz63889
Sometimes memory backups fail for CTC based NEs with release 6.0.1.
Note
CSCsz96763
In the Service Up Time log, clicking the Stopped At column does not sort the table.
Note
CSCta00978
When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.
Note
CSCta30577
The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.
Note
CSCta61660
ENE/GNE role changes on the network causes unstable NE service and node connectivity issues.
Note
CSCta69422
Insufficient memory causes ONS 15305 NE connectivity issues. Errors also appear after marking NEs as Out of Service and then In Service.
Note
CSCta69424
If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the CTM client freezes.
Note
CSCtb01411
The network services and network service instances cannot be stopped or started from the Control Panel. The SMService-0-<timestamp>.log file shows the following error message:
EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too many open filesNote
CSCtb85880
After performing NE software upgrades, the SM service restarts NE services.
(Related caveat ID: CSCtc20552)
Note
CSCtb88190
CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs with an Unavailable status.
Note
Installing the CTM R9.0.0.604.2 Patch
This section describes how to download and install the CTM R9.0.0.604.2 patch.
Note
–
–
•
•
The following caveats are fixed in the CTM R9.0.0.604.2 patch:
•
•
•
•
EID-5016: Exception: %01 occurred while launching serviceprocess.java.io.IOException: Too many open filesThe following caveats are fixed in the CTM R9.0.0.600.8 patch
•
•
•
•
•
•
•
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.•
•
•
•
•
•
•
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290•
•
•
•
•
•
•
CTM R9.0.0.604.2 is intended for customers who are currently using one of the following:
•
•
•
•
Note
Complete the following procedures to upgrade to the CTM R9.0.0.604.2 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 R9.0.0.604.2 Patch
Before installing the CTM R9.0.0.604.2 patch, it is strongly recommended that you back up the existing database. To back up the CTM database, refer to the following sections in Chapter 4 of the Cisco Transport Manager Release 9.0 User Guide:
•
•
Downloading the CTM R9.0.0.604.2 Patch
Step 1
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
cd /<directory_name>unzip CTM9.0.0.604.2.patch.zipFor example, to extract the file to the /temp directory, enter:
cd /tempunzip CTM9.0.0.604.2.patch.zipThis creates a directory called 604, which contains all of the patch-related files.
Step 11
cd 604Step 12
a.
b.
c.
d.
e.
Installing the CTM R9.0.0.604.2 Server Patch
To apply the CTM R9.0.0.604.2 patch to the server, complete the following steps:
Step 1
a.
b.
c.
The CTM server will be shut down in 5 minutes. Please log out of the CTM client before then.d.
e.
Step 2
a.
b.
c.
d.
Note
e.
This operation will log out the selected CTM user. The process will take approximately 1 minute and this CTM client will be unusable until then. Do you wish to continue?Wait until the CTM server completes the operation. The CTM GUI is frozen for approximately 1 minute until the request is complete. Log out all of the users listed in the Logged In CTM Users table to make sure that all user sessions are terminated.
Step 3
ctms-stopStep 4
./server_patch.sh
Note
Step 5
ctms-startStep 6
showctmYou should see the following version string in the first line of output for the preceding command:
Cisco Transport Manager Server Version: 9.0 Build: 604 Patches: 2
Installing the CTM R9.0.0.604.2 Client Patch in Windows
The following steps describe how to patch a CTM client installation in Windows. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1
Step 2
client_patchYou can also use the Windows Explorer folder view to access the directory where the patch files were extracted and double-click the client_patch.bat file.
Step 3
Step 4
•
Client: 9.0 Build: 604 (client configuration size)•
9.0 [9.0.0.604]
Installing the CTM R9.0.0.604.2 Client Patch in Solaris
The following steps describe how to patch a CTM client installation in Solaris. Before proceeding, make sure that there are no instances of the client running in the system. To shut down a running client, choose File > Exit in the Domain Explorer; then, click OK in the confirmation dialog box.
Step 1
Step 2
./client_patch.shStep 3
ctmc-startStep 4
•
Client: 9.0 Build: 604 (client configuration size)•
9.0 [9.0.0.604]
Open Caveats
The following sections describe the caveats that are not resolved in the CTM R9.0 software:
•
•
•
–
–
–
–
–
Installation and Upgrade Caveats
•
Symptom The CTM server cannot connect to and manage MGX NEs.
Conditions
Workaround
•
•
In these files, replace the default Oracle SID (CTM) with the SID that will be specified in the CTM database installation.
•
Symptom After a database migration, there are no modules available for debugging. The list under the Control Panel > Logging Properties > SNMP Trap Service Debug subtab is empty.
Conditions
Workaround
•
Symptom When upgrading from CTM R8.0 or CTM R8.5 to CTM R9.0, if the network configuration size upgrade option is selected, an error appears stating that you must increase disk space to continue with the migration. CTM incorrectly checks the partition free space instead of the partition size. Also, the error message should be a warning message.
Conditions
•
•
•
Workaround
•
Symptom Due to security issues, CTM must support Apache web server version 2.2.11.
Conditions
Workaround
•
Symptom The Apache Tomcat software should be disabled to avoid potential security issues.
Conditions
Workaround
•
Symptom When installing CTM R9.0 on a T2-based server in a small network configuration, the installation fails at the end of disk 3.
Conditions
Workaround
This procedure applies only to small CTM configurations that:
•
•
•
•
Step 1
#prtdiag -v | grep -i memoryStep 2
Downloading the CTM R9.0.0.550 Patch
Step 1
Step 2
Note
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
cd /<directory_name>unzip CTM9.0.0.550.patch.zipFor example, to extract the zip file to the /temp directory, enter:
cd /tempunzip CTM9.0.0.550.patch.zipThis creates a directory called 550, which contains all of the patch-related files.
Step 11
cd 550Applying the Patch and Installing CTM R9.0
Step 1
Step 2
a.
b.
c.
•
•
d.
Step 3
#cd ./T2_small_install#ls -l *.sh#chmod +x *.shStep 4
Caution
Step 5
#cd /T2_small_install#./fix_installation.shAfter you launch the fix_installation script, usage instructions appear on screen. See the usage example below.
When you launch the script, specify the <CTM_version> and <SID>. Be very careful to specify the correct values.
Usage Example
# ./fix_installation.shUsage: ./fix_installation.sh <CTM_version(9.0)> <SID>
Example:
./fix_installation.sh 9.0 CTMStep 6
Please PRESS INSTALL NOW on Pre-Installation Summary screenStep 7
The script runs during the CTM installation and continuously prints the following output until the fix is complete:
Script ./fix_installation.sh is running ...Once complete, the script exits with the following messages:
___ PFILE has been created___ Modifying pfile ...___ <SID> pfile has been modified.Script ./fix_installation.sh has completed successfully•
Symptom In a small network configuration, the CTM server installation fails when the optional db01_rd and db02_rd partitions are configured.
Conditions
Workaround
•
•
•
Symptom The CTM server fails to start. If you run the ctms-start command, the command fails with the following error:
ctms-start: Command not found.Conditions
Workaround
cd /optrm -r CiscoTransportManagerServerrm CiscoTransportManagerServer9.0ln -s CiscoTransportManagerServer-old-<timestamp> CiscoTransportManagerServerrm CiscoTransportManagerServer.oldCTM•
Symptom While installing CTM, if you choose "Add new modules" at the Installation Options screen and add MGX modules, CTM cannot connect to those MGX devices.
Conditions
1.
2.
3.
4.
Workaround
CTM Client Caveats
This section contains the following information:
Alarm Management
•
Symptom In the Alarm Browser, the module name "TCC" (Timing Communications and Control) is displayed regardless of the actual equipment type. For example, alarms reported on TCC, TCC1, and TCC2 cards all display "TCC" as the module name.
Conditions
Workaround
•
Symptom Link down alarms, syslog events, and configuration messages are not received for ML cards on ENEs behind the firewall when SNMP v2 is enabled.
Conditions
Workaround
•
Symptom CTM and CTC do not show the actual equipment type for G1K-4 and TCC2 cards.
Conditions
Workaround
•
Symptom Cannot filter alarms by affected object when the alarms have affected objects such as VFAC, FSTE, VCM, T1, and T3.
Conditions
Workaround
•
Symptom A mismatch alarm is raised incorrectly in CTC and CTM.
Conditions
Workaround
•
Symptom The Alarm Log does not report syslog and configuration trap messages from ENEs in a GNE-ENE setup for SNMPv2. The Alarm Log shows trap messages only for GNEs.
Conditions
Workaround
•
Symptom It is possible to set alarm threshold values on ONS 1580x measurement points that are outside the range of possible values. For example, you can set a negative power threshold (in milliwatts).
Conditions
Workaround
•
Symptom For NE version 7.0, the Alarm Suppressed For Maintenance alarm is not removed from the alarm table when the 32DMX card is deleted.
Conditions
1.
2.
3.
Workaround
•
Symptom The port name (RPR, Ethernet, POS) is incorrect or missing from the alarm table for all ML cards.
Conditions
Workaround
Circuit and Link Management
•
Symptom Cannot change the administrative state to Out of Service-Out of Group (OOS_OOG) for VCAT circuits or VCAT member circuits.
Conditions
•
•
Workaround
•
Symptom The J1 path trace displays expected and received bytes at the source end for unidirectional circuits.
Conditions
Workaround
•
Symptom 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 International characters can be entered in fields that do not support them.
Conditions
Workaround
•
Symptom An error appears when attempting to route a circuit after an upgrade from OC-192 XFP to OC-192. The Link table shows the link as valid, and the PTP ID is not updated.
Conditions
Workaround
•
Symptom When a low-order circuit is created and the option to have the corresponding tunnel created automatically is selected, the alias name of the tunnel and the low-order circuit is the same. When multiple low-order circuits are created through the same operation (the number of circuits is more than 1 in the Create Circuit wizard), the alias of the tunnel is the same as that of the first low-order circuit in the group.
Conditions
Workaround
•
•
•
Symptom The ONS 155xx Circuit table does not show circuit information for circuits whose names are modified using CTM.
Conditions
Workaround
•
Symptom Cannot remove a high-order VCAT circuit between two GE-2-WAN cards on ONS 15305 NEs. CTM returns a message that the circuit has been successfully removed, but the circuit is not removed from the Circuit table.
Conditions
Workaround
•
Symptom Cannot create more than one VT server trail on DS1 cards on ONS 15454, ONS 15310 MA, and ONS 15310 CL NEs when a server trail already exists on the first VT of the selected STS. Although other VTs are available, they are not listed in the server trail creation wizard as possible endpoints. The same operation succeeds in CTC.
Conditions
Workaround
•
Symptom The number of TL1 circuits in the Circuit table increases after marking NEs as Out of Service and then In Service.
Conditions
Workaround
su - oraclesqlplus ctmanager/ctm123!SQL> delete circuit_bs_tbl where cktstate=12;SQL> commit;•
Symptom If a card is changed or upgraded on an NE, all circuits that existed on that slot before the operation still show the module that existed before the change.
Conditions
Workaround
•
Symptom Manual link creation fails.
Conditions
Workaround
•
Symptom The Circuit table does not contain the expected circuits.
Conditions
Workaround
•
Symptom Connecting NE links shown in the Link table become invalid after removing NEs in a BLSR.
Conditions
Workaround
•
Symptom The graphic map displayed for a high-level circuit trace or circuit trace does not update after you switch circuit views.
Conditions
Workaround
•
Symptom The Circuit table contains an invalid partial circuit with a name that ends in "_master".
Conditions
Workaround
•
Symptom The MTU size value is not updated on a protected port.
Conditions
This problem also occurs when an OTU2_XP card is configured in TXP mode and in a Y-cable protection group. The MTU value change on the working client port does not change on the protect client port.
Workaround
•
Symptom Creation of a protected SVLAN circuit (Layer 2 1+1 plus FAPS protection) between 10GE_XP cards fails.
Conditions
Workaround
•
Symptom Cannot create dual-ring interconnect (DRI)-protected STS-v circuits in CTM. DRI protection is not available in the Create Circuit wizard.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom QinQ-Transparent mode settings cannot be deleted or changed from an SVLAN circuit even after the SVLAN settings are deleted.
Conditions
Workaround
•
Symptom Line Data Communications Channel (LDCC) and Section Data Communications Channel (SDCC) links on an OTU2_XP card should not be discovered as routable links.
Conditions
Workaround
•
Symptom When using the Create SVLAN wizard to create a QinQ setting, an incorrect class of service (CoS) value is displayed.
Conditions
Workaround
•
Symptom An incorrect Inner SVLAN value is displayed in the QinQ tab of the GE_XP or 10GE_XP card when using CTC to change the Operation value from Double Add to Add or Translate Add to Translate.
Conditions
Workaround
•
Symptom In the CTM GUI, NEs are constantly being moved and taking a long time to be grouped into subnetworks. Also there is a large amount of database query activity.
Conditions
Workaround
•
Symptom CTM does not return an error if you select 1+1 protection for splitter-protected, optical channel patchcord links on an OTU2_XP card, even though 1+1 protection is invalid for splitter-protected links.
Conditions
Workaround
•
Symptom If you perform a span switch from the Link Utilization table, the switch does not work for all circuits listed in the table.
Conditions
Workaround
•
Symptom Circuit creation does not set the correct OTU2_XP card attributes when the card is in Regeneration mode.
Conditions
Node A ---- node B ---- node C, where:
•
•
•
The OCHCC circuit endpoints are on node A and node C.
The Create Circuit wizard does not set the correct parameters on the OTU2_XP card in Regeneration mode. A G.709/FEC mismatch error occurs. Also, if the port state of the endpoints is IS, the port states of node A and C are also set to IS, while the port state of node B remains OOS. DSBLD breaks the circuit path.
Workaround
•
Symptom Splitter-protected OCHCC routing fails through OTU2_XP cards in Regeneration mode.
Conditions
•
•
•
•
A ------------B-----------C
Splitter EFEC splitter
•
•
•
Workaround
•
Symptom Creation of an OCHCC circuit using PSM in MUX section or path protection is possible in only one direction. Creation of OCHCC should be available in both directions.
Conditions
Workaround
•
Symptom Open VCAT circuit creation fails, and the PTP information is shown incorrectly as VC4=0.
Conditions
Workaround
•
Symptom The port name is not displayed in the Physical Location column of the Alarm Browser for DS1 or DS3 cards.
Conditions
Workaround
•
Symptom Creating a circuit that contains 20 or more constraints causes a timeout error.
Conditions
•
•
Workaround
•
Symptom Circuits remain in the CTM database with a CktState value equal to 12.
Conditions
•
•
Workaround
•
Symptom The Circuit Trace window shows a low-order VT circuit span incorrectly as LAP/VAP.
Conditions
Workaround
•
Symptom The High-Level Circuit Trace graphic map displays a gray link, instead of a green link, for an open-ended VCAT circuit.
Conditions
1.
2.
3.
Workaround
•
Symptom A patchcord link cannot be created between SONET/SDH card ports and SONET/SDH OTU2_XP client ports.
Conditions
1.
2.
A physical SONET/SDH patchcord link cannot be created between the SONET/SDH OTU2_XP client port and a SONET/SDH card port.
Workaround
•
Symptom The Protection panel shows the wrong name for an OTU2_XP card.
Conditions
Workaround
•
Symptom For OCHNC circuits, CTM reports a nonexistent value of 59.98 as the wavelength value. CTC reports the correct wavelength value.
Conditions
Workaround
•
Symptom The status of a VCAT circuit changes to Partial when adding new members to the circuit on SONET NEs.
Conditions
Workaround
•
Symptom The CTM Link table shows valid and active phantom links, but the corresponding links in the NCP CTM layer do not exist.
Conditions
Workaround
•
Symptom You cannot filter the Network Map to show OCH transport unit links.
Conditions
Workaround
•
Symptom In a protected SVLAN circuit, deletion of endpoints does not work correctly from the SVLAN table (Configuration > Delete Drop).
Conditions
Workaround
•
•
Note
If the problem has already occurred and the circuit is discovered in partial state instead of complete state, restart the NE service.
•
Symptom The CVLAN value does not reset to 0 in the QinQ tab of a GE_XP or 10GE_XP card when changing the Operation value from Add, Translate, or Translate Add to Double Add.
Conditions
Workaround
•
Symptom From the SVLAN wizard, the Add Drop operation fails (SVLAN Table > Add Drop).
Conditions
Workaround
•
Symptom The SPAN_BS_TABLE database table displays incorrect working and protected values.
Conditions
Workaround
•
Symptom A warning message of a possible traffic impact appears when reconfiguring circuits. This warning message should not appear, because reconfiguring circuits does not affect traffic.
Conditions
Workaround
•
Symptom A VLAN range cannot be added on a 10GE_XP/GE_XP card.
Conditions
Workaround
•
Symptom CTM fails to automatically route and create a STS-24c circuit to the 15454-ADM-10G card when entering a value in the Time Slot Restriction field.
Conditions
Workaround
•
Symptom Cannot create links between an ONS 15454 10-DME-C card and an ONS 15216 FlexLayer NE.
Conditions
Workaround
•
Symptom The switch selector for UPSR/SNCP circuits is missing from the Circuit Trace window.
Conditions
Workaround
•
Symptom CTM fails to reconfigure circuits on release 8.5 NEs.
Conditions
EID-2328: An error occurred during the circuit reconfiguration.Workaround
•
Symptom Cannot add drops on cards configured in Automatic mode.
Conditions
Workaround
•
Symptom Some tunnel links are missing and are not available for VT circuit routing in the Create Circuit wizard.
Conditions
Workaround
•
Symptom When changing the CVLAN field of a SVLAN circuit, the circuit changes to a Partial state.
Conditions
Workaround
•
Symptom Dragging NEs within the Create Circuit wizard map view does not work correctly. The NEs are moved to an unexpected position.
Conditions
Workaround
•
Symptom NEs cannot be moved to the bottom right corner of the Create Circuit wizard map view.
Conditions
Workaround
•
Symptom Adding a new member to a VCAT circuit fails. After clicking Next from the Route Constraints pane of the Add Member wizard, the Routing Preferences pane appears instead of the Review Route pane.
Conditions
•
•
•
•
Workaround
User Management
•
Symptom When using a Retrieve, Maintenance, or Provisioning user account for CTM server-to-NE connectivity, CTM allows NE user administration operations to be performed on R4.1.4 NEs. User administration should be allowed only for Superuser accounts.
Conditions
Workaround
Data Services
•
Symptom Cannot preprovision the port name of the RAN-SVC card in CTM. CTM does not allow you to change or view the port name.
Conditions
Workaround
•
Symptom It takes a long time to create an 802.17 RPR Layer 2 topology.
Conditions
Workaround
•
Symptom You cannot add or remove protection cards using the Add/Remove Cards wizard.
Conditions
Workaround
•
Symptom In the NE Explorer for ML cards, the Ether tab > Gigabit Ethernet Provisioning or Fast Ethernet Provisioning subtabs are blank.
Conditions
Workaround
•
•
•
•
Symptom Provisioned SVLAN circuits are not displayed if the SVLAN table is started from the card view.
Conditions
Workaround
•
Symptom ENE/GNE role changes on the network cause unstable NE service and node connectivity issues.
Conditions
EID-2017: Exception: %01 for NE: %02 while %03.ORA-12899: value too large for column "CTMANAGER"."NE_INFO_TABLE"."NESNMPCOMMSTRING" (actual: 277, maximum: 256)Workaround
•
Symptom If NE releases earlier than 9.0 are present in the selection context during SVLAN discovery process, the CTM client freezes.
Conditions
Workaround
Domain Explorer
•
Symptom An NE with one TCC card goes into loss of communication (LOC) state if the TCC card is swapped without a synchronization.
Conditions
Workaround
•
Symptom MGX Voice Gateway applications cannot be launched from the CTM Domain Explorer.
Conditions
For example, D:\Program Files\ctm has a space between Program and Files. Installing in this location causes the Symptom described.
Workaround
•
Symptom After a switch activity is performed with a Cisco IOS command on an ONS 155xx with a redundant CPU (active/standby), the node is shown as available in the CTM Domain Explorer but unavailable in the tree view.
Conditions
Workaround
•
Symptom The NE time stamp for syslog messages is the same as the CTM time stamp because the actual NE time stamp when the syslog message was generated is not available. This duplicates the syslog messages in the event log, and each syslog message has a different time stamp.
Conditions
Workaround
•
Symptom Sometimes, the Active IP Address field in the Domain Explorer does not update automatically.
Conditions
•
•
Workaround
•
Symptom Sometimes, when launching the L2 Topology table, the following error message appears: "EID-333: A database timeout occurred."
Conditions
Workaround
•
Symptom Values that are entered in the Network Element Properties pane > NE Authentication tab > CTM Server - SNMP Connection area are not validated when the SNMP protocol is set to SNMPv3.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom After powering down and powering up the CTM server workstation, some duplicate groups appear in the CTM domain. These duplicate groups persist even after the CTM server is restarted.
Conditions
Workaround
•
Symptom When a GNE-ENE setup involves PSM cards with path protection, the Domain Name column in the APC Domain table shows sides as Unknown instead of as side (W) and side (P).
Conditions
1.
2.
3.
Workaround
•
Symptom ENE nodes configured in Secure IP mode do not reconnect to CTM after the node is marked as Out of Service and then In Service.
Conditions
Workaround
1.
2.
3.
Repeat these steps each time the NE goes through an Out of Service/In Service cycle.
•
Symptom In the Domain Explorer > Management Domain Properties pane > Status tab > NE Count by Operational State field, the "NEs in Initialization" counter is always 0 (zero).
Conditions
Workaround
NE Explorer
•
Symptom Setting the Routing Information Protocol (RIP) metric to zero does not generate an error message.
Conditions
Workaround
•
Symptom The NE Explorer does not refresh the Secure Config Mode value after a mode change.
Conditions
1.
2.
3.
4.
5.
Workaround
•
Symptom Clicking the Apply button after modifying the SNMP User Datagram Protocol (UDP) port does not save the modified value.
Conditions
Workaround
•
Symptom The DS3XM-12 NE Explorer > Customer Info tab does not show values for the transmux conversion ports, which are DS3XM-12 card ports used for VT-DS3 mapping.
Conditions
Workaround
•
Symptom The default RIP summary address is not created when activating RIP from CTM.
Conditions
Workaround
•
Symptom No range address is created when enabling Open Shortest Path First (OSPF) on a LAN from CTM.
Conditions
Workaround
•
Symptom The NE ID for the ONS 15600 cannot be modified and the Description field is missing in the NE Explorer.
Conditions
Workaround
•
Symptom A card with a warning is not colored correctly in the rack view.
Conditions
Workaround
•
Symptom In the NE Explorer, the SSXC card is shown as CXC for ONS 15600 SONET R7.2 NEs.
Conditions
Workaround
•
Symptom The Customer Info table is blank for XTC cards on ONS 15327 R4.1.4 and R4.1.8 NEs.
Conditions
Workaround
•
Symptom The power monitor value (ELWBATVG or EHWBATVG) can only be changed once.
Conditions
Workaround
•
Symptom Contact Status and Raised fields are not updated in the External Alarms subtab.
Conditions
1.
2.
3.
When the alarm is created, the Contact Status and Raised fields are synchronized with CTC. However, once the alarm is raised in the Alarm Browser, the Contact Status and the Raised check boxes change (the check boxes are selected). This update is not reflected in CTM. When the Alarm Browser is checked, the alarm is raised. The same conditions exist when the alarm is created from CTM.
Workaround
•
Symptom You cannot set the AINS Soak attribute on an ASAP card.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom Intermediate port information shows incorrect data when upgrading an optical card to an MRC-12 card.
Conditions
Workaround
•
Symptom The IPv6 address format is not reported correctly.
Conditions
1.
2.
3.
4.
5.
On the FTP host subtab, the IPv6 address is reported incorrectly as "0.0.0.0." CTC reports the IPv6 address correctly.
Workaround
•
Symptom EC1 ports are listed in the Optical tab and PPM ports are listed in the EC1 tab of a CTX card.
Conditions
•
•
Workaround
•
Symptom The port status does not update when you select the Force or Clear option from the Protection tab > Protection Groups subtab > Operations subtab > Protection Group Details area.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom Line tab values for Line Thresh 15 Min and 1 Day subtabs do not reset to the correct default values.
Conditions
Workaround
•
Symptom Sometimes, using CTC to change the port mode of an E1_21_DS3_E3_3 card on an E3 interface does not automatically update the information in the Broadband Ports tab.
Conditions
Workaround
•
Symptom The NE Explorer > VC tab of a CTX card shows the wrong high-order (HO) and low-order (LO) VC values.
Conditions
Workaround
•
Symptom A section trace cannot be configured on client ports.
Conditions
1.
2.
3.
Workaround
•
Symptom The VC4 Threshold tab is not available for an E1_63_DS3_E3_3 card.
Conditions
1.
2.
Workaround
•
Symptom After you change an IP address on a managed NE, discovery problems occur if new networks containing the changed IP address are added to CTM.
Conditions
Workaround
•
Symptom The Protection tab > Operation subtab > Protection Group Details area displays "No Status."
Conditions
Workaround
•
Symptom You cannot modify an existing LDCC from OSI and IP (PPP) to IP (PPP) or from IP (PPP) to OSI and IP (PPP).
Conditions
1.
2.
3.
–
–
4.
5.
Workaround
•
Symptom You cannot save an SVLAN name that contains commas.
Conditions
Workaround
•
Symptom ONS 15454 OCHxx circuits are not available from the Edit > Find > Object Type > Metro DWDM Circuits > Circuit Type drop-down list. Instead, the OCHxx circuits are listed under the SONET Circuits > Circuit Type drop-down list.
Conditions
Workaround
•
Symptom The SVLAN fields in the QinQ tab are not automatically updated when VLAN database changes are made.
Conditions
Workaround
•
Symptom You cannot change the LAN configuration on a multishelf R9.0 NE from the CTM GUI.
Conditions
Workaround
•
Symptom Clicking the Help tool from the NE Explorer does not work. Also, the Help menu lists "Pseudo CLI" instead of "Current Window."
Conditions
For 9.0 NEs, the Pseudo CLI window, instead of the online help, appears after clicking the Help tool from the NE Explorer.
Workaround
•
•
•
Symptom In the NE Explorer for the ONS 15310 MA or the ONS 15454 MSPP, the first time you select an optical card, the Transceiver tab is blank.
Conditions
Workaround
•
Symptom CTM displays GNEs with release 9.0.x as ENEs. Also, the corresponding ENEs are displayed as LNEs with an Unavailable status.
Conditions
Workaround
•
Symptom The CTM Domain Explorer window freezes and you are unable to select other NEs.
Conditions
Workaround
Network Map
•
Symptom Line configuration and threshold values are not shown in CTM when creating a new DS3 port through CTC.
Conditions
Workaround
Performance Monitoring
•
Symptom When you click OK in the Graph Parameters Selection dialog box, the selected parameters are not graphed correctly.
Conditions
1.
2.
3.
The graph shows only one parameter; two parameters are missing.
Workaround
•
Symptom After a normalization operation on a PM graph, the maximum value of the Y axis is not displayed.
Conditions
Workaround
•
Symptom When you launch the DS-1 PM table for an ONS 15310 NE, the FC-P (Tx) parameter is missing.
Conditions
Workaround
•
Symptom CTM does not report PM values at time 00:00 for an ONS 1580x card.
Conditions
Workaround
•
Symptom Cannot collect valid real-time Storage Area Network (SAN) PM data for NEs earlier than release 5.0.
Conditions
Workaround
•
Symptom The following problems are observed:
1.
2.
Conditions
Workaround
•
Symptom Real-time PM tables display a Not Available message for PM queries with remote NEs when the selection context is large.
Conditions
Workaround
•
Symptom High bandwidth usage occurs between the CTM client and the CTM server.
Conditions
Workaround
•
Symptom TCAs are not shown in the VC12 PM table for E1 and E1_42 cards.
Conditions
Workaround
•
Symptom PM data collection, audit trail collection, error logging, and audit logging stop abruptly.
Conditions
Workaround
BeginDBMS_JOB.RUN (1,true);DBMS_JOB.RUN (2,true);DBMS_JOB.RUN (3,true);DBMS_JOB.RUN (4,true);End;•
Symptom The ETHERSTATSTXFIFOOVERFLOWEVENTS value for the CE-MR card shows N/A when retrieving historical PM data.
Conditions
Workaround
•
Symptom The wrong physical PM trunk port values are displayed for a 2.5G_DM card. The Physical PM table should show N/A trunk port values for Min TX Power, Avg TX Power, and Max TX Power.
Conditions
Workaround
•
Symptom Unnecessary STS/VC HO path PM data is collected for an Ethernet POS port of an ASAP_4 card.
Conditions
1.
2.
3.
This problem occurs when the two circuits mentioned in Steps 1 and 2 are created separately.
Workaround
•
Symptom An incorrect value (-0.1) is reported on the OTN real-time PM panel even if OTN counters are disabled.
Conditions
Workaround
•
Symptom 1-day PM data shows values for the wrong day.
Conditions
Workaround
•
Symptom The getTCATPParams API shows SONET thresholds for unsupported parameters.
Conditions
1.
2.
Workaround
•
Symptom The SDH LO VC3 PM table displays PM values for a VC12 circuit.
Conditions
1.
2.
3.
Workaround
•
Symptom In a large network of GNEs and ENEs, CTM fails to collect PM data.
Conditions
Workaround
Step 1
a.
b.
c.
Step 2
Step 3
Step 4
Step 5
-Dctm.pm.dssPMPollerEnabled=true \Step 6
-Dctm.pm.refresh.interval=X \where X is the number of seconds after which the PM services reload the DSS list. The default value is 600 seconds. Do not add any blank lines or spaces after the slash (\).
Step 7
Step 8
•
Symptom Performance monitoring for OTN 1-day far-end real-time data does not work correctly for R7.0 NEs.
Conditions
Workaround
•
Symptom For nodes equipped with PPM-provisioned transponder and muxponder cards, the reported Average Transmit Power value is incorrect.
Conditions
Workaround
Miscellaneous
•
Symptom The Equipment Inventory table shows TCC2P as TCC2.
Conditions
Workaround
•
Symptom CTM shows a blank password.
Conditions
Workaround
•
Symptom When a new card is provisioned on a filler card on an ONS 15600 SDH NE, the actual equipment type is blank and a Mismatch of Equipment (MEA) alarm is raised.
Conditions
Workaround
•
Symptom The file CTM Client Home/gcoutput, where CTM Client Home is your client location, is unreadable.
Conditions
Workaround
To change the name of the GC data file on Windows systems:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
To change the name of the GC data file on Solaris systems:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
•
Symptom The taskbar shows all grouped CTM client applications as javaw x instead of CTM.
Conditions
Workaround
•
Symptom A node name change is not reflected in the CTM client.
Conditions
Workaround
•
Symptom The CTM client freezes when connected to a high-end CTM server.
Conditions
Workaround
•
Symptom The number of alarms shown in the CTM Dashboard is not synchronized with the number of alarms shown in the Domain Explorer > Management Domain Properties pane.
Conditions
Workaround
•
Symptom There is a delay when performing a Revert to Default operation on the Network Map.
Conditions
Workaround
•
Symptom NEs do not come up in CTM after exchanging MAC addresses between managed NEs.
Conditions
Workaround
•
Symptom NEs are added successfully, but they do not appear in the Domain Explorer and cannot be located using the Find feature. Moreover, if an NE is moved from one group to another, the NE disappears from the Domain Explorer.
Conditions
Workaround
•
Symptom It takes too long to preprovision cards that have too many ports and there is no indication that the operation is in progress.
Conditions
Workaround
•
Symptom The DS3 tab of the ONS 15310 CL NE Explorer is empty after configuring a broadband port that carries DS3 or EC1 payload.
Conditions
1.
2.
3.
Workaround
•
Symptom When you change the NE default values of ONS 15600 SDH R8.0 NEs, the following error message appears: "Error in setting the values. Please choose a valid value from the range displayed."
Conditions
Workaround
•
•
•
Symptom For a 10GE_XP card, if you launch a pseudo-IOS connection from the Tools menu, the Telnet window launches but does not respond to keyboard entries.
Conditions
Workaround
•
Symptom The Bulk FTP Configuration wizard does not display an error message when you enter invalid parameters. The job is scheduled and fails.
Conditions
1.
2.
3.
Workaround
•
Symptom The Refresh button does not flash when the port name is changed and automatic refresh is disabled. The window does not refresh automatically even after enabling automatic refresh.
Conditions
Workaround
•
Symptom When you add a new CTC-based NE to CTM that is part of a ring, the system takes a long time to discover the new NE and the other nodes of the ring.
Conditions
Workaround
•
Symptom When saving an SVLAN database or profile to a file, CTM should check whether the filename that you enter exists. If the file exists, CTM should prompt you to confirm whether or not you want to replace the existing database or profile file.
Conditions
Workaround
•
Symptom The Bulk FTP Configuration wizard does not display an error when an IPv6 address is entered as the FTP host address for an NE that does not have IPv6 enabled.
Conditions
Workaround
•
Symptom Moving subnetworks across network partitions in the Subnetwork Explorer leads to inconsistent behavior.
Conditions
1.
2.
3.
4.
5.
The operation should succeed under both scenarios.
Workaround
•
Symptom VT1.5 PM information is displayed incorrectly for DS3XM-12 cards. The VT PM information is shown with incorrect numbers, making it impossible to tell which VT the PM data is for.
Conditions
Workaround
•
Symptom The SNMPv3 wizard reappears with values after the client is locked and unlocked.
Conditions
1.
2.
3.
4.
Workaround
•
Symptom Connection with the NE is lost when saving or deleting an SVLAN database that contains several SVLANs on multiple cards.
Conditions
Workaround
•
Symptom Deletion of SVLAN profiles is not saved when saving to a file.
Conditions
1.
1.
2.
3.
4.
5.
6.
Workaround
•
•
•
Symptom The CTM server does not send SNMP traps or gets to IPv6 destinations. The following problems occur:
•
•
Conditions
Workaround
•
Symptom The Error Log contains meaningless error messages that pertain only to DWDM cards, yet there are no DWDM cards in the network.
Conditions
Workaround
•
Symptom In the Service Up Time log, clicking the Stopped At column does not sort the table.
Conditions
Workaround
•
Symptom The CTM client freezes and does not respond to user commands.
Conditions
Workaround
•
Symptom The CTM client freezes and does not respond to user commands.
Conditions
Workaround
•
Symptom After performing NE software upgrades, the SM service restarts NE services.
Conditions
Workaround
•
•
CTM Server and Database Caveats
•
Symptom After a new installation, circuit discovery on a meshed network is slow. It takes a long time to open the Circuit table.
Conditions
Workaround
•
•
•
Symptom The prune_ne_ipaddress script does not work with IPv6 addresses.
Conditions
Workaround
•
Symptom The connectivity state of an unmanaged NE displayed in the Domain Explorer and Control Panel is inconsistent.
Conditions
Workaround
•
Symptom When performing a database backup, the following error message appears: "EID-609: There isn't enough space in backup directory. Do you want to continue?" However, if you continue, the backup operation succeeds. The CTM disk space test is too conservative.
Conditions
Workaround
•
Symptom A database export does not update the database tables correctly.
Conditions
Workaround
•
Symptom A database export fails with the following error:
ORA-00904: "DBMS_JAVA"."LONGNAME": invalid identifier.Conditions
Workaround
•
•
•
Symptom An alert about a security violation on granting EXECUTE privileges on UTL_FILE packages appears in the Oracle Enterprise Manager or the Alert Log.
Conditions
Workaround
•
Symptom During intensive database usage, Archive Log pruning does not efficiently remove files from the /db05 directory.
Conditions
Workaround
•
Symptom The Service Manager (SMService) starts a higher number of ONS 15454 network services than is expected. If the number of network services is too high, the services start and shut down continuously, which degrades the overall performance of the CTM server.
Conditions
Workaround
•
Symptom Sometimes memory backups fail for CTC based NEs with release 6.0.1.
Conditions
Workaround
•
Symptom When installing the CTM R9.0.0.604.2 patch, the following error message is displayed in the log:
The database has been imported, executing security_config.sql
ERROR: ORA-01031: insufficient privileges SP2-0640: Not connectedConsequently, the security_config.sql script does not run and some permissions in the CTM database are incorrect. (The permissions are available to public instead of ctmanager.)
Conditions
•
•
Workaround
•
Symptom A memory leak occurs on the CTM server because of zombie lightweight process (LWP) creation when a user is in locked state.
Conditions
Workaround
•
Symptom The ctms-stop and ctms-abort scripts do not work when Oracle is down.
Conditions
Workaround
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
•
Symptom The network services and network service instances cannot be stopped or started from the Control Panel. The SMService-0-<timestamp>.log file shows the following error message:
EID-5016: Exception: %01 occurred while launching service process.java.io.IOException: Too many open filesConditions
Workaround
•
Symptom CTM does not discover the entire network, and NEs remain in loss of communication (LOC) state with the following error:
OutOfMemoryError: PermGen space:Conditions
Workaround
Original value:
-XX:MaxPermSize=128m-XX:PermSize=128mFixed value:
-XX:MaxPermSize=256m-XX:PermSize=256m•
Symptom After running the getinfo.sh script, the following error message appears:
Permission denied while running "rsh". Check the environment and make sure the root is permitted to run "rsh" on host.Conditions
Workaround
•
Symptom Some optical NEs (such as the ONS 15454) are shown with a red check mark in the Domain Explorer tree. If these NEs are marked as Out of Service and then In Service, the red check mark persists, and the NEs are not discovered. Restarting the NE service does not resolve the problem.
Conditions
Workaround
•
Symptom ENE/GNE configuration changes on the network and node connectivity issues cause the NE to remain in Sync_Config state.
Conditions
Workaround
Cisco Transport Controller Caveats
•
Symptom A DRI circuit does not have DRI protection. Instead, it has only path/SNCP protection.
Conditions
•
•
•
Workaround
•
Symptom When the OSPF Area ID value is set to 1, CTC sends "0:0:0:0:0:0:0:1" instead of "0.0.0.1."
Conditions
Workaround
•
Symptom The first database export from the CTM GUI fails.
Conditions
Workaround
High Availability Caveats
Note
•
Symptom A database restore fails because some of the archive log files are missing from the CTM_backup directory.
Conditions
Workaround
•
Symptom During HA local installation, the /etc/rc2.d/S99dbora and /etc/rc0.d/K10dbora files are not removed from the primary and secondary servers.
Conditions
Workaround
•
Symptom The optional HA feature for managing replication traffic and NE traffic in separate networks does not manage a failover condition that simulates a network crash on the replication network or NE network.
Conditions
Workaround
CTM GateWay/TL1 Caveats
•
Symptom For the ONS 15216 EDFA2 R2.4, the ED-NE-GEN command fails in the CTM GateWay/TL1 session.
Conditions
Workaround
•
Symptom The CTM GateWay/TL1 session times out on ONS 15530 and ONS 15540 nodes if kept idle for longer than 60 minutes.
Conditions
Workaround
•
Symptom When launching the TL1 interface on an ENE, the following error message is shown: "EID-501: Cannot launch a remote console to selected NE." Also, the Managed NEs list from the Control Panel displays the IPv6 address of the ENEs instead of their IPv4 address.
Conditions
Workaround
CTM GateWay/CORBA Caveats
Note
•
Symptom Cannot set J1 path trace parameters immediately after circuit creation.
Conditions
Workaround
•
Symptom CTM GateWay/CORBA is not installed when the server and the database are installed on separate machines.
Conditions
Workaround
•
Symptom CTM GateWay/CORBA returns XC loopback values for CTPs even when the loopback is present in the corresponding line.
Conditions
Workaround
•
Symptom A CTM GateWay/CORBA user is able to perform operations even after being logged out from the CTM client.
Conditions
Workaround
•
Symptom The emsMgr::EMSMgr_I::createTopologicalLink API returns an exception with the message "Failed to get containing equipment for a PTP."
Conditions
Workaround
•
Symptom The getAllEquipment API returns the value "Unequipped" in the Equipment field when an ONS 15302 R2.0 card is preprovisioned. Instead, the equipment name should be returned.
Conditions
Workaround
•
Symptom The getAllEquipment API returns the value "Unequipped" in the Equipment field when an ONS 15302 R2.0 card is preprovisioned. Instead, the equipment name should be returned.
Conditions
Workaround
•
Symptom The getHistoryPMData API takes longer than 15 minutes to return data.
Conditions
Workaround
•
Symptom The getAllSupportedPTPs API fails for an OSCM card and returns an error message.
Conditions
Workaround
•
Symptom Cross-connect table information provided by the northbound CORBA interface is wrong. The CTP name retrieved by a VC12 circuit (when using getAllCrossConnections) is /sts3c_au4-j=62/vt2_tu12-k=0-l=0-m=0.
Conditions
Workaround
•
Symptom You cannot use CTM GateWay/CORBA to set the low power threshold (Power Low) on an OPT_RAMP_C card.
Conditions
Workaround
•
Symptom An exception appears and PM values are not displayed when you use the CTM GateWay/CORBA interface to collect ONS 15310 MA SDH DS3 PM data.
Conditions
Workaround
•
Symptom The getCTPsAndTopologicalLinks API that is called from an OCHCC circuit returns an exception with the message "no rows from db."
Conditions
Workaround
•
Symptom The Error Log contains multiple errors that are similar to the following:
CTMError : Got Exception in CerentObject::getShelfForEntities for CTC Index : 70290Conditions
Workaround
•
Symptom The CTM server aborts automatically because the Implementation Repository (IMR) service is not running.
Conditions
Workaround
Non-HA Configuration
For CTM R9.0 in a non-HA configuration, complete the following steps:
Step 1
#ctms-stopStep 2
# ./run com.prismt.openfusion.tools.ChangeJacORBProperties -r jacorb.use_imr=on jacorb.use_imr=off# ./run com.prismt.openfusion.tools.ChangeJacORBProperties -r jacorb.use_imr_endpoint=on jacorb.use_imr_endpoint=offStep 3
#ctms-startHA Configuration
For CTM R9.0 in an HA configuration, work with a Symantec Veritas expert to complete the preceding steps. Any changes on the primary server must also be made on the secondary server. After the changes are complete, verify that the /opt/CiscoTransportManagerServer/openfusion/classes/jacorb.properties file has been modified correctly on the secondary server.
•
Symptom The setTPData API returns an exception or does not set parameters on ONS 15310 MA SDH NEs.
Conditions
Workaround
NE-Specific Caveats
This section includes the following information:
•
•
•
•
•
Cisco MGX Voice Gateway
•
Symptom &#
Guest
