Guest

Cisco ONS 15200 Series DWDM Systems

Field Notice 18687: ONS15200 : CLIPs Do not Appear in the Management System Inventory


Updated May 7, 2002

April 10, 2002


Products Affected

Product

Top Assembly

Comments

Part Number

Rev.

CH23/M/P/SC/15200=

800-09473-01

-H0

CLIP Chan 23, Med Range, Protected

CH25/M/P/SC/15200=

800-13404-01

-H0

CLIP Chan 25, Med Range, P

CH27/M/P/SC/15200=

800-13405-01

-H0

CLIP Chan 27, Med Range, Protected

CH29/M/P/SC/15200=

800-13406-01

-H0

CLIP Chan 29, Med Range, Protected

CH31/M/P/SC/15200=

800-13407-01

-H0

CLIP Chan 31, Med Range, Protected

CH33/M/P/SC/15200=

800-13408-01

-H0

CLIP Chan 33, Med Range, Protected

CH35/M/P/SC/15200=

800-13409-01

-H0

CLIP Chan 35, Med Range, Protected

CH37/M/P/SC/15200=

800-13410-01

-H0

CLIP Chan 37, Med Range, Protected

CH43/M/P/SC/15200=

800-13411-01

-H0

CLIP Chan 43, Med Range, Protected

CH45/M/P/SC/15200=

800-13412-01

-H0

CLIP Chan 45, Med Range, Protected

CH47/M/P/SC/15200=

800-13413-01

-H0

CLIP Chan 47, Med Range, Protected

CH49/M/P/SC/15200=

800-13414-01

-H0

CLIP Chan 49, Med Range, Protected

CH51/M/P/SC/15200=

800-13415-01

-H0

CLIP Chan 51, Med Range, Protected

CH53/M/P/SC/15200=

800-13416-01

-H0

CLIP Chan 53, Med Range, Protected

CH55/M/P/SC/15200=

800-13417-01

-H0

CLIP Chan 55, Med Range, Protected

CH57/M/P/SC/15200=

800-13418-01

-H0

CLIP Chan 57, Med Range, Protected

CH23/L/P/SC/15200=

800-13419-03

-A0

CLIP Chan 23, Long Range, Protected

CH25/L/P/SC/15200=

800-13420-03

-A0

CLIP Chan 25, Long Range, Protected

CH27/L/P/SC/15200=

800-13421-03

-A0

CLIP Chan 27, Long Range, Protected

CH29/L/P/SC/15200=

800-13422-03

-A0

CLIP Chan 29, Long Range, Protected

CH31/L/P/SC/15200=

800-13423-03

-A0

CLIP Chan 31, Long Range, Protected

CH33/L/P/SC/15200=

800-13424-03

-A0

CLIP Chan 33, Long Range, Protected

CH35/L/P/SC/15200=

800-13425-03

-A0

CLIP Chan 35, Long Range, Protected

CH37/L/P/SC/15200=

800-13426-03

-A0

CLIP Chan 37, Long Range, Protected

CH43/L/P/SC/15200=

800-13427-03

-A0

CLIP Chan 43, Long Range, Protected

CH45/L/P/SC/15200=

800-13428-03

-A0

CLIP Chan 45, Long Range, Protected

CH47/L/P/SC/15200=

800-13429-03

-A0

CLIP Chan 47, Long Range, Protected

CH49/L/P/SC/15200=

800-13430-03

-A0

CLIP Chan 49, Long Range, Protected

CH51/L/P/SC/15200=

800-13431-03

-A0

CLIP Chan 51, Long Range, Protected

CH53/L/P/SC/15200=

800-13432-03

-A0

CLIP Chan 53, Long Range, Protected

CH55/L/P/SC/15200=

800-13433-03

-A0

CLIP Chan 55, Long Range, Protected

CH57/L/P/SC/15200=

800-13434-03

-A0

CLIP Chan 57, Long Range, Protected

CH23/M/U/SC/15200=

800-13502-01

-H0

CLIP Chan 23, Med Range, Unprotected

CH25/M/U/SC/15200=

800-13435-01

-H0

CLIP Chan 25, Med Range, Unprotected

CH27/M/U/SC/15200=

800-13436-01

-H0

CLIP Chan 27, Med Range, Unprotected

CH29/M/U/SC/15200=

800-13437-01

-H0

CLIP Chan 29, Med Range, Unprotected

CH31/M/U/SC/15200=

800-13438-01

-H0

CLIP Chan 31, Med Range, Unprotected

CH33/M/U/SC/15200=

800-13439-01

-H0

CLIP Chan 33, Med Range, Unprotected

CH35/M/U/SC/15200=

800-13440-03

-H0

CLIP Chan 35, Med Range, Unprotected

CH37/M/U/SC/15200=

800-13441-01

-H0

CLIP Chan 37, Med Range, Unprotected

CH43/M/U/SC/15200=

800-13442-01

-H0

CLIP Chan 43, Med Range, Unprotected

CH45/M/U/SC/15200=

800-13443-01

-H0

CLIP Chan 45, Med Range, Unprotected

CH47/M/U/SC/15200=

800-13444-01

-H0

CLIP Chan 47, Med Range, Unprotected

CH49/M/U/SC/15200=

800-13445-01

-H0

CLIP Chan 49, Med Range, Unprotected

CH51/M/U/SC/15200=

800-13446-01

-H0

CLIP Chan 51, Med Range, Unprotected

CH53/M/U/SC/15200=

800-13447-01

-H0

CLIP Chan 53, Med Range, Unprotected

CH55/M/U/SC/15200=

800-13448-01

-H0

CLIP Chan 55, Med Range, Unprotected

CH57/M/U/SC/15200=

800-13449-01

-H0

CLIP Chan 57, Med Range, Unprotected

CH23/L/U/SC/15200=

800-13450-03

-A0

CLIP Chan 23, Long Range, Unprotected

CH25/L/U/SC/15200=

800-13451-03

-A0

CLIP Chan 25, Long Range, Unprotected

CH27/L/U/SC/15200=

800-13452-03

-A0

CLIP Chan 27, Long Range, Unprotected

CH29/L/U/SC/15200=

800-13453-03

-A0

CLIP Chan 29, Long Range, Unprotected

CH31/L/U/SC/15200=

800-13454-03

-A0

CLIP Chan 31, Long Range, Unprotected

CH33/L/U/SC/15200=

800-13455-03

-A0

CLIP Chan 33, Long Range, Unprotected

CH35/L/U/SC/15200=

800-13456-03

-A0

CLIP Chan 35, Long Range, Unprotected

CH37/L/U/SC/15200=

800-13457-03

-A0

CLIP Chan 37, Long Range, Unprotected

CH43/L/U/SC/15200=

800-13458-03

-A0

CLIP Chan 43, Long Range, Unprotected

CH45/L/U/SC/15200=

800-13459-03

-A0

CLIP Chan 45, Long Range, Unprotected

CH47/L/U/SC/15200=

800-13460-03

-A0

CLIP Chan 47, Long Range, Unprotected

CH49/L/U/SC/15200=

800-13461-03

-A0

CLIP Chan 49, Long Range, Unprotected

CH51/L/U/SC/15200=

800-13462-03

-A0

CLIP Chan 51, Long Range, Unprotected

CH53/L/U/SC/15200=

800-13463-03

-A0

CLIP Chan 53, Long Range, Unprotected

CH55/L/U/SC/15200=

800-13464-03

-A0

CLIP Chan 55, Long Range, Unprotected

CH57/L/U/SC/15200=

800-13465-03

-A0

CLIP Chan 57, Long Range, Unprotected

Note: All of the revision levels above use Firmware revision 0.3(8).

Problem Description

In a well installed system the amount of Data Communication Proprietary Protocol (QPP) traffic is low. In an inproper system installation (installed by not following the installation manual), the QPP communication links over the fibers can cause an abnormally high amount of message transfers which increase the possibility to any of the following issues. A possible indication of this behavior is the toggling of QPP alarms on the management interface.

  1. CLIPs in the system do not appear, or appear intermittently, in the management system inventory.

  2. Some CLIPs have wrong Network Element Identifier (NEID) register values.

  3. Some CLIPs cannot carry traffic after power-up.

Background

Investigation shows the reason for problem (A) is a massive amount of traffic on the internal communication network (DCN). The main reason for the traffic is a number of bouncing messages between CLIPs. A bouncing message is created when the destination or source address in a message gets corrupted and there is a CLIP inserted in the slot of the corrupted address (heavy traffic load on the CAN and QPP busses, caused by toggling QPP alarms, is the likely cause of the corrupted CAN packet destination address).

Analysis of problem A

A timing problem has been found in the interface between the FPGA and the CAN driver device on the CLIP. A corrupted destination or source field may cause bouncing messages.

Analysis of problem B

The timing problem can also cause a corrupted message payload. There is a possibility that this can lead to the modification of register values.

Analysis of problem C

This problem is related to an occasional glitch which has been found on a signal in the interface between the FPGA and the serial EEPROM device, where the calibration data is stored. The glitch may cause a write operation to fail. The next time this CLIP is power cycled, it will fail during initialization and the lasers will not be turned on. Because of the retransmissions and timeouts mentioned earlier, there will be an abnormal amount of write operations to the CLIPs in the system.

Problem Symptoms

  1. CLIPs in the system do not appear, or appear intermittently, in the management system inventory.

  2. Some CLIPs have wrong NEID register values. Further analysis of the memory dumps of these boards shows that also other register values are modified. If multiple CLIPs obtain identical (corrupted) NEIDs, the management system will logically OR all of the information and display it as one CLIP.

  3. Some CLIPs cannot carry traffic after power-up.

Workaround/Solution

Solution

Problem (A) is not traffic affecting. Reseating the CIM board resolves the problem on the (electrical) CAN bus in the MCU. This will clear all CAN bus traffic (including bouncing messages) within the MCU. If the problem resides on the optical layer, an upgrade to the new Firmware 1.2(2) is required to clear bouncing QPP messages on the optical layer, such as QPP traffic between MCU-SCU and SCU-SCU.

Problem (B) is not traffic affecting and can be resolved by upgrading to the new Firmware 1.2(2).

Problem (C) can be resolved by a Firmware upgrade from the current Firmware version 0.3(8) to the new 1.2(2) version.

Recommendations

  • If the system is operating under normal conditions (installation in accordance with the installation manual, and a low rate of management traffic), no immediate action is required.

  • In case any of the problems mentionned are seen on the network, upgrade the CLIPs. An increased number of QPP and CAN Alarms raised is an indication of the system degradation.

Mixing old 0.3(8) and new 1.2(2) Firmware

Mixing of firmware is allowed and compatible under the following circumstances.

  • All hub to hub configurations

  • Mixing Clips in an MCU (Electrical CAN bus)

  • Mixing Clips in one optical Channel (Optical CAN bus)

Old 0.3(8) and new 1.2(2) Firmware are compatible with each other if not used in the configuration detailed below.

If a CLIP board with FW 0.3(8) is located in a site where there is a NCB-board (Site 1), CLIP boards on the remote CAN-bus (Site 2) must not be equipped with FW 1.2(2) in order to have management visibility of the CLIPs reached through the remote CAN-bus (Site 3) with QPP.

{---Site 1----}      {------------Site 2-----------}     {-----Site 3----}
Optical(QPP)     Electrical(CAN)     Optical (QPP)
CLIP(FW 0.3(8)) ----> CLIP(FW x) ---->CLIP(FW 1.2(2)) ----> CLIP(FW x)
Assumption:
NCB-board resides in Site 1.
FW x = FW 0.3(8) or 1.2(2)

Upgrade instructions to Clip boards with new Firmware 1.2(2)

Customers will be contacted directly by their account teams to schedule a strategy for replacement of affected units.

Units with the potential for this problem, but not currently experiencing the impact of it, will not be replaced through the return materials authorization (RMA) process. Please contact your account team for more details.

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.

NetPro Discussion Forums - Featured Conversations

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.