Guest

Cisco Transport Manager

Field Notice 17682: Cisco Transport Manager Requires a Minimum Software Release of 3.0.3 on ONS 15454, MMX 3.3 for ONS 15327


Revised August 2, 2002

March 23, 2002


Products Affected

Product

Comments

ONS 15454

TCC and TCC+

ONS 15327

XTC-28-3 XTC-14

Cisco Transport Manager 2.2 and 3.0

?

Problem Description

Networks implementing Cisco Transport Manager (CTM) version 2.x and higher with ONS 15454 NE's must be running a minimum of software release 3.0.3. Network Elements running system software releases prior to v. 3.0.3 (ONS15454), could experience connectivity loss and/or TCC resets due to consumption of sockets over an extended period of time when implementing CTM v. 2.x and 3.x. Connectivity loss and resets can also occur while using CTC, but since the usage of CTC is intermittent, as opposed to CTM, which is always active, it is unlikely that the problem will occur. The connectivity loss is characteristic to CTM communication with the network elements, only. This problem can also occur with ONS15327, Current software (1.x) for ONS15327, does not contain the fix for this problem. The fix for this problem is available in MMX version 3.3. In order to use CTM in your network all NE's should be upgraded to release 3.03 (15454), and MMX 3.3 for 15327.

Background

The Object Request Broker (ORB) is application software that provides the Corba layer communication channel between an ONS NE and the CTC/CTM management interfaces. Version 3.2.1.2 of the Highlander ORB software contains a known bug which can result in the problem described by this field notice. All NE software releases prior to 3.0.3 (ONS 15454), and all current versions of ONS 15327 (1.x) contain this version of ORB software.

Release 3.0.3 (ONS 15454) contains the ORB version which fixes the known bug in prior versions of ORB software.

Note:?Release 3.0.2 (ONS 15454) does contain the fix for CSCdv22380 (ORB bug), but we recommend an update to release 3.0.3 (available now), to ensure highest availability. MMX version 3.3 contains the fix for ONS 15327.

Problem Symptoms

The NE is not able to send autonomous events such as alarms and db change msgs. Regular communication is OK between the NE and CTC/CTM. Provisioning can occur and, if you perform actions on the CTC that cause it to poll the NE, some information may be "resychronized" between the NE and CTC which masks this problem. It usually occurs at first connection by CTC/CTM and can continue to occur even after restarting CTC or the NE.

To verify that you are experiencing this problem:

Parse the /opt/CiscoTransportManagerServer/log/NEService-1Error.log file for Chassis is null and CORBA.COMM_FAILURE statements. If these messages are seen in the log file, one or more NEs is exhibiting the Visibroker ORB bug. It does not indicate which NE is exhibiting the bug. Further debugging in the Operating System of the NE is needed to properly diagnose which NE is exhibiting the bug.

Workaround/Solution

Solution

Upgrade all ONS 15454 NEs to CTC version 3.0.3 and remove all ONS 15327 NEs to a separate CTM server. (When MMX 3.3 is used on the network users of the 15327 can then combine the 15454 NEs and 15327 NEs under a single CTM server.

Workaround (prior to upgrade)

To restore communication between the NE and the management interface (CTC/CTM) before an upgrade is complete, the user must close down all CTC sessions and reset the active TCC on the ONS 15454 NE or active XTC on the ONS 15327 NE that is exhibiting signs of this bug.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

?

CSCdv22380

Visibroker ORB Bug, assoc. with Highlander ORB (Object Request Broker) version 3.2.1.2

CSCdu11290

GW/TL1 slows down CTM server

CSCdv08712

TL1: entering greater than 1023 characters reboots the TCC

CSCdv00919

Multiple TCCs reset

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.