Monthly Archives: March 2015

Be aware of SSN3PSXCSA replace Cross-connect Board on OptiX OSN 3500

Summary:

When an SSN3PSXCSA (Ver.B) board is used to replace another cross-connect board, after the SSN3PSXCSA (Ver.B) board is inserted into the subrack, the state of the original active cross-connect board is abnormal and NE services are interrupted. After about 40s, the state of the original active board is back to normal and services recover.

[Problem Description]Fault symptoms:

When an SSN3PSXCSA (Ver.B) board is inserted into the slot of the standby cross-connect board, the ACT indicator of the active cross-connect board turns from steady green to off and services are interrupted. The NE may report the PLL_FAIL alarm of service boards.
Trigger conditions:
Use an SSN3PSXCSA (Ver.B) board to replace another kind of cross-connect board. This problem does not occur if the original active cross-connect board is an SSN3PSXCSA board.
Identification method:
This problem can be identified if the following conditions are met.

  • Services are interrupted for about 40s when you use an Huawei OptiX OSN 3500 SSN3PSXCSA (Ver.B) board to replace a non-SSN3PSXCSA cross-connect board.
  • The new board must be an SSN3PSXCSA board in Ver.B, which can be verified by checking the silkscreen on the board, as is shown in the following figure:

SSN3PSXCSA in Ver.B,

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

After the board starts, you can also obtain the board version using the NMS.

[Root Cause]
When the SSN3PSXCSA (Ver.B) board is powered on as a standby cross-connect board, before the logic is loaded, the status bus sent to the active cross-connect board is incorrect. As a result, the active cross-connect board is switched to be a standby board and services are interrupted. After the logic of the board is loaded, the status bus sent to the original active board, the status of the original active board and NE services are all back to normal. The service interruption lasts for about 40s.

[Impact and Risks]
When the SSN3PSXCSA (Ver.B) board is inserted into the slot of standby cross-connect board and the active cross-connect board is not an SSN3PSXCSA (Ver.B) board, services are interrupted for about 40s.

[Measures and Solutions]
Recovery measures:
Remove the SSN3PSXCSA (Ver.B) board from the slot of standby cross-connect board.
Workaround:
For different board versions, when a board is used to replace a different board, different commands are required to forcibly stop the active/standby switching. For a specific scenario, contact GTAC to obtain the corresponding command.
Solution:
Use an SSN3PSXCSA in Ver.C to perform the board replacement.
Material handling after replacement:
Use SSN3PSXCSA (Ver.B) boards as good boards to replace other SSN3PSXCSA boards on huawei transmission equipment.

 

TwitterLinkedInGoogle+FacebookPinterestTumblrStumbleUponRedditShare

Cautions for Drive Failure on the SSX2T2TM Module

Summary:
A 10G OTU board reports an OTU2_LOF alarm at a low probability on the Huawei WDM side during the running. When this alarm is reported, services are interrupted and the alarm persists.

[Problem Description]
Trigger conditions:
This problem has no external trigger conditions, and occurs at a 1% probability during normal running.

Symptom:
An OTU2_LOF alarm is reported and persists during the normal running of a 10G OTU board.

Identification method:
1. An OTU2_LOF alarm is reported on the board and persists. In addition, services are interrupted.
2. After a self-loop is performed on the IN port and OUT port of the peer board, an OTU2_LOF alarm is reported or the pre-FEC BER of the board is in the range of 1E-3 to 1E-11; however, no exception occurs after a WDM-side software loopback is performed.
3. According to the board manufacturer information, boardtype contains SSX2T2TM and the time specified by Manufactured is earlier than April 2010.

The following describes the procedure for querying Huawei board manufacturer information:
Step 1 From the main menu of the NMS, choose Report > Board Manufacturer Information Report.

Board Manufacturer Information Report.

Step 2 On the Board Manufacturer Information Report tab in the window that is displayed, view the board manufacturer information, especially the fields that are highlighted in the following figure.

Board Manufacturer Information Report2

[Root Cause]
Air and moisture enter the SiN passivation layer and erode the electrode on the FET grid of the SSX2T2TM module, causing a decrease of output amplitude of the drive on the SSX2T2TM module. As a result, the drive on the SSX2T2TM module fails.

[Impact and Risk]
If the drive on the local board fails, an OTU2_LOF alarm will be reported on the peer board and persist. In addition, services will be interrupted.

[Measures and Solutions]
Recovery measures:
Replace the local board.(click here for more Huawei transmission equipment)
Workarounds:
No workaround is available.

Pay attention to Optical Power Reporting of Modules in WDM Products

Summary:
When fibers on boards that use the HXFP8240, HXFP8440, or HXFP8441 pluggable module on dwdm huawei boards are being removed or inserted, the reported optical power at the receive end is sometimes lower than the actual optical power.

[Problem Description]
Trigger conditions:
The problem occasionally occurs when customer fibers are removed and re-inserted.
Symptom:

  •  In the site deployment phase, customer-purchased fibers are used to connect optical modules. The reported receive optical power on some boards is over 3 dB lower than the actual optical power measured using an optical power meter. Sometimes, an IN_POWER_LOW alarm is reported. The reported optical power may be normal after the fibers are removed and re-inserted for several times.
  • When customer-purchased fibers are removed and re-inserted during normal system operating, the reported receive optical power on some boards is over 3 dB lower than the actual optical power measured using an optical power meter. Sometimes, an IN_POWER_LOW alarm is reported. The reported optical power may be normal after the fibers are removed and re-inserted for several times.

Identification method:
The problem occurs when the following conditions are present:

  • The problem occasionally occurs during site deployment or a fiber is removed or inserted.
  • In the queried board manufacturer information, the huawei osn 8800 optical module type is HXFP8240, HXFP8440, or HXFP8441, as shown in Figure 1. Or the optical module type indicated on the label attached to the optical module is HXFP8240, HXFP8440, or HXFP8441, as shown in Figure 2 or Figure 3.

Figure 1

HXFP8441  Figure

 

 

 

 

 

 

 

 

 

Figure 2

HXFP8441 Module

Figure 3

HXFP8240 Modul

A customer-purchased fiber is used to connect the optical module. The reported receive optical module is over 3 dB lower than the actual optical power. After a fixed optical attenuator (FOA) is connected to the fiber, the reported o0070tical power is normal. For example, the measured actual optical power is –5.1 dBm. After a 2 dB FOA is connected to the fiber, the reported optical power is approximately –7 dBm.

[Root Cause]
According to the YD1272-1 standard, the LC ferrule elasticity and size B are two major indicators to determine the quality of an LC connector. If either indicator does not satisfy requirements, the problem may result.

  • The elasticity of the LC ferrule does not satisfy the requirement of 5–6 N and is much smaller than the stress between the receive-end optical device and the ceramic sleeve. Consequently, a gap is generated between the fiber and the end face of the optical device ferrule and excessive insertion loss results. As a result, the reported optical power is much lower than the actual optical power.

LC ferrule

 

 

 

 

 

 

 

 

 

  • The LC size B refers to the fiber area inserted to the optical device, which indicates the contact area between the fiber and the optical device. The size B of the customer fiber does not satisfy the requirement and causes excessive insertion loss. As a result, the reported optical power is much lower than the actual optical power.

LC ferrule size B

 [Impact and Risk]

At the board receive end, the reported optical power is over 3 dB lower than the actual optical power. Sometimes, an IN_POWER_LOW alarm is reported or the receive-end bit error rate (BER) deteriorates.
[Measures and Solutions]
Recovery measures:

  • Connect a 0 dB, 2 dB, or 3 dB FOA to the fiber before inserting the fiber to an optical module.
  • Replace the fiber jumper.

Workarounds:
None.
Preventive measures:
Replace the customer fibers with fibers that satisfy requirements. The fibers provided by Jonhon, Acon, and Foxconn are recommended. For more huawei transmission equipment, please get through at www.thunder-link.com.

3G service not pass in STM-1 due to SNCP problem

【Problem Summary】”3G service not pass in STM-1 by LAG_Ticket

【Problem Details】Product Information: OptiX OSN 3500 Version Information: V1R8 SR Severity: Major Problem Description: 3G service not pass in STM-1 by LAG

Customer requirement:

to pass combined (2G+3G service) through 2 path as active and protection.

 

1.    MW path

2.    Huawei Optix STM-1 path

Due to SNCP by EG4 card SNCP not possibileafter using EFP8 card as SNCP sink,SNCP possible.【Resolution Summary】
【Resolution Details】

there are physical connecting between EG4 and EFP8.

 

The service route is IF — EG4(Eth port) — EFP8(Eth port) — SPDH — IF     — SL1D  — IF

 

SNCP configuration should be configured on Huawei optical interface board–EFP8.

SNCP configuration

 

 

 

 

Why just get 10M by using MAC in loop test on EFT8 board of OSN500

One day, x operator report that they use ethernet tester to test an EPL service between OSN3500 and OSN500 and set MAC in loop, they just get 10M bandwidth when

bind 2 VC3
OSN3500  5.21.18.50     N2EFS4
OSN 500   5.62.02.12     EFT8

none
Because the chip of EFT8 board has limition

EFT8 board
1,Because OSN500 use SD579 and BCM5248 chip to realize ethernet service transimit function.
2,When BCM5248 chip has not finished negotiation, such as not connct lan cable, lan cable is cut off, or the SMI path which connect PHY and MAC chip, it will work
at 10M mode defaultly
3,The working mode of SD579 chip will select the value of PHY chip.
4,when SD579 set MAC in-loop, software will cut off SMI path, this time PHY chip will work at 10M, so MAC will work at 10M.
Customer test using MAC inloop, the chip will work at 10M mode defaultly, so customer can only get 10M bandwidth.
N/AAsk customer to change the test method, use tester to loop or create two EPL service to use lan cable to loop, the bandwith is ok
The EFT8 board of Huawei optix OSN500 has limition, so don’t use MAC in-loop to test the bandwith

Be Aware of SSN4SL64 Board ID on MSTP Products

Summary:

Due to incorrect uploading of image files, the ID of an SSN4SL64 board of Ver.C fails to be recognized after a power-on, resulting in a board failure to start up. SSN4SL64 boards of Ver.C must be rectified.

[Problem Description]
Trigger conditions:
Problematic SSN4SL64 boards of Ver.C were manufactured between May 20 and July 24 in 2013. For specific manufacture date of an SSN4SL64 board, see the bar code of the board, which can be looked up in the Board Delivery Details attachment.
Symptom:
The ID of an SS4NSL64 board of Ver.C fails to be recognized after a power-on. The board fails to start up.
Identification method:
To check whether an SSN4SL64 board is of Ver.C, query board manufacture information on the NMS or view the PCB silkscreen. Then check if the bar code of the board is in the Board Delivery Details attachment. If yes, the SSN4SL64(P1L1-2D2,LC) Board is of Ver.C.

[Root Cause]
Due to incorrect uploading of image files in software of the SSN4SL64 board of Ver.C, the file system may be corrupted after the board is powered on. Board read/write operations fail and the board fails to start up.
[Impact and Risk]
The following two situations may occur:

  •  The board fails to start up after being deployed.
  •  The board can start up, but is likely to fail after a cold reset or a version upgrade/downgrade is performed.

[Measures and Solutions]
Recovery measures:
None.
Workarounds:
None.
Preventive measures:

Solution 1
Format the flash memory through the COM port. Upload correct board software using FTP. For details, see the SSN4SL64 Board Upgrade Guide.
Version support for this solution is listed in the following table.

SSN4SL64 COM PORT

Note: R10C03SPC202 and later R10C03 versions, as well as R012 versions are subject to the Huawei BlueSky regulations and their COM ports are unavailable.

Solution 2
Replace the problematic SSN4SL64 Board (Ver.C manufactured between May 20 and July 24 in 2013) with a new board, For more huawei transmission equipment, please get through at www.thunder-link.com.

Notice on TN11PIU Wrongly Reported THUNDERALM Alarm on OptiX OSN 6800

Summary:
When the TN52SCC board is used on OptiX OSN 6800, the power module of the TN11PIU board interferes with lightning protection alarm signals. As a result, a detection error occurs and the THUNDERALM alarm is wrongly reported.

OSN 6800

[Problem Description]
Trigger condition:
The TN52SCC board is used on DWDM Huawei OptiX OSN 6800 and the fan tray assembly is running at high speed.

Symptom:
When the TN52SCC board is used on OptiX OSN 6800 and the fan tray assembly is running at high speed, the TN11PIU board reports a THUNDERALM alarm.

Identification method:
When the OptiX OSN 6800 uses the TN52SCC board, identify the problem as follows:
1. Set the fan tray assembly to low speed. The THUNDERALM alarm is cleared 10 seconds later.
2. Set the high speed again. The alarm is reported 10 seconds later.
If the preceding symptoms occur, the alarm is wrongly reported and the TN11PIU board is involved in the problem.
Note: After the above identification operations are completed, you must restore the fan try assembly speed to prevent impact on NE heat dissipation.

[Root Cause]
The power module of the TN11PIU board supplies power to the fan tray assembly. If the fan tray assembly is running at high speed, the load current of the power module is great and the power module noise is increased accordingly, interfering with lightning protection signals. If at this time the TN52SCC board is used, it detects lightning protection signals at a high frequency. Therefore a detection error occurs and the THUNDERALM alarm results. If the TN51SCC board is used, it detects the signals at a low frequency and therefore no detection error or related alarm results. If the fan tray assembly is running at low speed, the load current of the power module is small and therefore the power module noise is small. Therefore, no detection error or related alarm results.

[Impact and Risk]
If an error occurs in detecting the lightning protection signals, the THUNDERALM alarm will be wrongly reported by the TN11PIU board but services are not affected.

[Measures and Solutions]
Recovery measures:
None.
Workarounds:
None.
Preventive measures:
Not available currently. If any preventive measure is available, the notice will be updated.
Material handling after replacement:
None.

Cautions for CF Card Failure on TN11SCC in OptiX OSN 6800

Summary:
When the TN11SCC board is in V100R004C01 or an earlier version, the lifecycle of the CF card on the board may be shorter than expected.

[Problem Description]
Trigger condition:
Periodical database and log backup, and upgrade in package loading mode on the Huawei dwdm board TN11SCC are properly implemented.

Symptom:
An SWDL_NEPKGCHECK alarm is reported.

Identification method:
The CF card is faulty when all the following conditions are met:
1. The TN11SCC board is in V100R004C01 or an earlier version.
2. The CF card has been used for more than five years.
3. An SWDL_NEPKGCHECK alarm is reported.
4. The access to the cfs1 area of the board fails using a command on the Navigator. For example, a board in slot 18 reports an SWDL_NEPKGCHECK alarm as shown in the following figure..

SWDL_NEPKGCHECK alarm

A command on the Navigator is delivered as shown in the following figure.

Navigator

However, a failure message is returned. When this occurs, the CF card has been faulty.

[Root Cause]
As confirmed by the CF card supplier WD, the CF card will become faulty upon multiple times of rewrite operations and cannot be read or write any longer. Since there are frequent
database and log backup operations for Huawei OptiX OSN 6800 V100R004C01 and earlier versions, the CF card can be used for five years at most. The card lifecycle is closely related to the size of the NE database and logs. In versions later than V100R004C01, the backup frequency and method are modified. After the modification, the CF card can be used for at least 100 years as estimated.

[Impact and Risk]
Upgrade in package loading mode and software synchronization will be affected, but services are not affected.

[Measures and Solutions]
Recovery measures:
Replace the TN11SCC board when the CF card of the board becomes faulty.

Workarounds:
Before the CF card becomes faulty, upgrade the TN11SCC board to V100R004C04SPC800 or
a later version.

Preventive measures:
1. If the CF card on a TN11SCC board has been faulty, replace the board. For more Huawei transmission board please have reference on www.thunder-link.com
2. If the CF card has not been faulty, upgrade the TN11SCC board to V100R004C04SPC800 or a later version.

Material handling after replacement:
Return the TN11SCC board for repair.

Watch out Wavelength Information of the TNF1X40 on the OSN 1800

Summary:

The wavelength information of the huawei dwdm TNF1X40 board is not verified at the equipment manufacturing and assembly stage. As a result, wavelength information at some ports of the board is not recorded.

[Problem Description]

Trigger conditions:

Wavelength informaion is not properly displayed when the wavelength information of the TNF1X40 board is queried.

Symptom:

Wavelength informaion of the TNF1X40 board is not properly displayed.

Identification method:

  •  When the wavelength information of the TNF1X40 board is queried through the NMS, the wavelength information of some ports is not displayed.

For example, the wavelength information of the MD02 and MD03 ports is not displayed, as shown in the following figure.

TNF1X40 board MD02 and MD3 ports

  • When the wavelength information of the TNF1X40 board is queried through the Navigator, the wavelength information of some ports is displayed as 255. For example, the wavelength information of the MD02 port (optical port 3, in slot 3) is displayed as 255, as shown in the following figure.

TNF1X40 board MD02 ports

[Root Cause]

The wavelength information of the TNF1X40 board is not verified during manufacturing tests. As a result, wavelength information at some ports of the board is not recorded.

[Impact and Risk]

Wavelength information of the TNF1X40 board cannnot be properly reported, and logical fiber connections fail to be established. Services are not affected.

[Measures and Solutions]

The recovery measures apply to the case of TNF1X40 used on the  OptiX OSN 1800 I/II Chassis, if the board need to be record is used on the OptiX OSN 1800 OADM Frame, please replace it on the Huawei OptiX OSN 1800 I/II Chassis.

Recovery measures:

Complete the following steps:

1. Record wavelength by running the :optp:$hexbid,1,83,1,13,08,$port,3,$num command, wherein Hexbid indicates the slot ID (hexadecimal) of the TNF1X40 board, Port indicates the port ID, and Num indicates the wavelength number.

Note: For information about the port ID and wavelength number used in the command, refer to Attachment 1. For example, to record the wavelength of the MD09 port of the TNF1X40 board in slot 3, run the :optp:3,1,83,1,13,08,a,3,1d command.

2. Verify the wabelength records by querying the wavelength information of each port of the huawei dwdm TNF1X40 board through the NMS and comparing the queried information with the standard wavelength information in Attachment 2.

Workarounds:

None.

Preventive measures:

On March 15th, 2013, the manufacturing and assembly department updated the software version for testing and added wavelength recording into the updated version.

Why all the boards on OSN 3500 become grey?

Problem: no operation do, but all the board of osn3500 become grey. service is ok.

version: OSN3500 V100R009C04SPC200

OSN 3500 SLOT

the possible reasons for this issue:

1. NE of Huawei MSTP OSN 3500 is in install status

2. some task of soft are suspended

 

handle procedures:

1. confirm with l1 that service is ok

2. check current alarm, no install alarm on NE

3. use :sys-get-alltaskinfo check all task status. find task of TALM is suspended. normally, there should only two tasks are suspended(tIonNbsSch and VOS_Entry).

#9-50:szhw [1000_Khuvayd_2  ][][2014-08-07 15:34:13+08:00]>
:sys-get-alltaskinfo
SYSTEM-TASK-LIST
Task-Name        Mod-Name         State    Prio
BOX                               READY    170
_TIL                              PEND     0
VIDL                              READY    254
TICK                              PEND     1
tExcTask                          PEND     0
tVosTimer                         PEND     55
tVos100ms                         PEND     100
tVos1s                            PEND     100
tVfsWorker       VOS              PEND     90
tVfsSender       VOS              PEND     110
tVfsSchemer      VOS              DELAY    150
tBDMLow1S        BDM              DELAY    150
tDmmCCardSend    DMM              PEND+T   70

……
ERRPICK          ERRPICK          PEND     100
018tMon          MON              READY    120
tSnmpRsp         SNMP             PEND     100
tSnmpReq         SNMP             DELAY    100
tBmMain          BM               PEND     120
tBMR             BM               PEND     100
TALM             MALM             SUSPEND  130
018tFiP          MALM             DELAY    150
……

               TNTPHSC          NTP              PEND     80
TNTPMML          NTP              PEND     80
TNTPP            NTP              PEND     110
tIonDmmRcv       ION              PEND     75
tIonNbsSch       ION              SUSPEND  70
tIonSckRcv       ION              DELAY    75
tIpAround        ION              PEND     100
TPTHPKG          BDM              PEND     130
TSRLMHSC         BDM              PEND     80
tCOARx           CoaAdp           READY    120
tCOATx           CoaAdp           PEND+T   120
tCOAPP           CoaAdp           READY    120
037TBDMcmd       BDM              PEND     120
037TBDMcmdreset  BDM              DELAY    120
037tDBD          Harddriver       DELAY    130
……
tPortmapd                         PEND     54
tTelnetd                          PEND     55
tFtpdTask                         PEND     55
tWdbTask                          PEND     3
tChkAux                           DELAY    100
VOS_Entry                         SUSPEND  70
OSPCLK                            DELAY    1
tVosClearDog                      DELAY    250
MccRxTask                         PEND     50
MccFlowTask                       DELAY    100
……
Total records :180    

 

4. after warm reset the master scc, Huawei transmission boards become green. NE works normal.   

the task of TALM  is suspended abnormally, then cause this issue.

warm reset the master scc can restart all the tasks.