Keywords: TNF1LDX, TNF2LSX, TNF2ELOM, OptiX OSN 1800
Summary:
On the TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for the OptiX OSN 1800 of
V100R003C01SPC300 and earlier versions, the ZL80018 chips in version H occasionally fail
to be configured. As a result, bit errors are generated on the WDM side of the peer end or services
are unavailable. This issue has been rectified in version V100E003C01SPC300.
[Problem Description]
Trigger condition:
This issue occasionally occurs when the TNF1LDX, TNF2LSX, or TNF2ELOM board intended
for OptiX OSN 1800 is powered off or (cold) reset, or the services on any of the boards are changed.
Symptom:
After the TNF1LDX (03021ETT), TNF2LSX (03021FTM), or TNF2ELOM (03030MSG) board used
during the network deployment or on the live network is powered off or (cold) reset, or the services
on any of the boards are changed, the services will be unavailable or bit errors will be generated.
The typical symptom is as follows: An ODU0_LOFLOM, ODU1_LOFLOM, ODU2_PM_BDI, or
BEFFEC_EXC alarm is reported on the WDM side of the peer board. An ODU0_PM_BDI,
ODUFLEX_PM_BDI, or ODU1_PM_BDI alarm is reported on the WDM side of the local board.
Identification method:
You can determine that this issue occurs when the following conditions are met:
1. After the TNF1LDX, TNF2LSX, or TNF2ELOM board used is powered off or (cold) reset, or the
services on any of the boards are changed, the services are unavailable or bit errors are generated.
To be specific, an ODU0_LOFLOM, ODU1_LOFLOM, ODU2_PM_BDI, or BEFFEC_EXC alarm
is reported on the WDM side of the peer board, and an ODU0_PM_BDI, ODUFLEX_PM_BDI,
or ODU1_PM_BDI alarm is reported on the WDM side of the local board.
2. The NE software version satisfies either of the following requirements:
The NE software version is earlier than V100R003C01SPC300 and is not upgraded after a fault occurs.
The NE software version is earlier than V100R003C01SPC300 when a fault occurs and then is
upgraded to V100R003C01SPC300 or later, but no cold reset is performed on the TNF1LDX,
TNF2LSX, or TNF2ELOM board.
3. The ZL80018 chip in version H is used and the boards satisfy the following requirements:
TNF1LDX: manufactured after December 14, 2012 and board barcode being numbered after
021ETT10CB000492
TNF2LSX: manufactured after December 14, 2012 and board barcode being numbered after
021FTM10CC000157
TNF2ELOM: manufactured after December 28, 2012 and board barcode being numbered after
030MSG10CC000745
[Root Cause]
The ZL80018 chip has a defect. It may fail to be configured, which has a higher probability for
ZL80018 chips in version H. The TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for
OptiX OSN 1800 do not strictly comply with the latest erata code standards of the ZL80018 chip
and cannot completely prevent the defect. As a result, the ZL80018 chip in version H used on the
TNF1LDX, TNF2LSX, and TNF2ELOM boards intended for OptiX OSN 1800 earlier than
V100R003C01SPC300 occasionally fails to be configured. Consequently, the clock performance
is affected and the services on the boards are unavailable or bit errors are generated.
[Impact and Risk]
For OptiX OSN 1800 earlier than V100R003C01SPC300, when the TNF1LDX, TNF2LSX, or
TNF2ELOM board using the ZL80018 chip in version H is powered off, (cold) reset, or services
are changed, bit errors will be occasionally generated or services will be occasionally unavailable.
This issue, however, will not occur during the normal running of the boards.
[Measures and Solutions]
Recovery measures:
Perform a cold reset on the involved boards (sometimes cold resets may need to be performed several times).
Workarounds:
None
Preventive measures:
This issue has been rectified since OptiX OSN 1800 V100R003C01SPC300. Therefore, upgrade the NE
software version to OptiX OSN 1800 V100R003C01SPC300 or later. When this issue occurs, upgrade
the NE software and perform a cold reset on the TNF1LDX, TNF2LSX, or TNF2ELOM board.
Comments are closed