Wednesday, March 23, 2016

Precaution for Upgrade of V100R007C00SPC100, V100R007C00SPC200, and V100R007C02SPC100

Summary: NEs using software packages including the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, and V100R007C00SPC100 need to be upgrade to the related GA versions or maintenance versions. Precautions need to be taken during the version upgrade.
Product Line:Transport network product line    Product Family:WDM products
Product Model:OptiX OSN      OptiX OSN 6800    OptiX OSN 3800
Keywords: NG WDM, V100R007C00, V100R007C02, TN54NS4, TN54TSC, TN54TTX
[Problem Description]
On the live network, NEs using software packages including the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, and V100R007C02SPC100 have risks during long-time operation. They need to be upgraded to mainstream maintenance versions according to version policies.
During the version upgrade, some 100G boards have risks and therefore spare boards must be prepared for them before the version upgrade.
The following lists the versions need to be upgraded:
OptiX OSN 8800 T32 V100R007C00SPC100 (ESS version)
OptiX OSN 8800 T32 V100R007C00SPC200 (ESS version)
OptiX OSN 8800 T32 V100R007C02SPC100 (TR5 version)
Trigger condition:
When NEs are using software packages including the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, and V100R007C02SPC100, they need to upgrade to the related GA versions or maintenance versions according to the upgrade paths listed in the following table.
Current Version
Target Version
OptiX OSN 8800 T32 V100R007C00SPC100
OptiX OSN 8800 T32 V100R007C00SPC300(5.51.08.16)
OptiX OSN 8800 T32 V100R007C00SPC100
OptiX OSN 8800 T32 V100R007C00SPC310(5.51.08.33)
OptiX OSN 8800 T32 V100R007C00SPC200
OptiX OSN 8800 T32 V100R007C00SPC300(5.51.08.16)
OptiX OSN 8800 T32 V100R007C00SPC200
OptiX OSN 8800 T32 V100R007C00SPC310(5.51.08.33)
OptiX OSN 8800 T32 V100R007C02SPC100
OptiX OSN 8800 T32 V100R007C02SPC200(5.51.08.32)
OptiX OSN 8800 T32 V100R007C02SPC100
OptiX OSN 8800 T32 V100R007C02SPC300(5.51.08.38)

Symptom:
None
Identification method:
The NE uses a software package of the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, or V100R007C02SPC100.

[Root Cause]
NEs have risks during long-time operation using software packages including the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, and V100R007C00SPC100. They need tobe upgraded to GA versions or maintenance versions according to upgrade policies.

[Impact and Risk]
An NE using a software package of the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, or V100R007C00SPC100 has risks during the version upgrade if it uses a TN54NS4, or TN54TSC, or TN54TTX board.
Specifically, the TN54NS4, TN54TSC, and TN54TTX boards use earlier-version FPGA which has a defect. Due to this defect, during the NE upgrade, there is a 0.45% probability that the NE becomes suspended when later-version FPGA is loaded to the NE and the NE cannot be recovered. When this occurs, the board must be replaced.
The NE has risks and special measures need to be taken (as described in "Preventive measures") if the TN54NS4, TN54TSC, or TN54TTX board meets the following conditions:
The board manufacturing date is earlier than March 31, 2013. In other words, the value indicating the date in the board barcode is equal to or less than "D3".
When the board undergoes a cold reset during NE upgrade, services over the board are interrupted and alarms such as OTUk_LOF and OTUk_DEG are reported.

[Measures and Solutions]
Recovery measures:
None
Workarounds:
None
Preventive measures:
Upgrade the NE using a software package of the OptiX OSN 8800 T32 V100R007C00SPC100, V100R007C00SPC200, or V100R007C00SPC100 to the related GA or maintenance version.
If the TN54NS4, TN54TSC, or TN54TTX board is used on the NE, the following operations are recommended during the NE upgrade:
Isolate the boards, prepare spare boards at a ratio of 1% of the boards (at least two spare boards of the same board type). After the NE upgrade is completed, release the board isolation. If the services are interrupted and alarms such as OTUk_LOF and OTUk_DEG are reported after automatic board package matching is completed and the boards undergo a cold reset, replace the boards at both ends.


More blog:

How to Clear the DBMS_ERROR Alarm Reported After an Upgrade

No comments:

Post a Comment