Have you ever headache with SL64 board COMMUN_FAIL alarm appear and board soft reset?

SL64 is a STM-64 Optical Interface Board, The SL64 is available in the following functional versions: N4, N2 and N1.The SSN2SL64(Ls-64.2,LC) is discontinued. The functions provided by the functional versions are different.

In OSN 3500 running with version V100R008C02

On SL64 alarm appear COMMU_FAIL and after runnig the command “errlog” (To check if the GSCC reset at that time or not)and “mon-get-errlog” find that the SL64 softreset with out any abnormality as command output shown below and also attached dtailed output.

ExceptLog:: total = 1                                                                                                                                                                                       

    :   001# 2014-01-13 13:47:14 ExcptErr:   pc=0x002d9cb8, SR=0x9032, FaultAddr=0x00000300,

No.027:  2014-01-13 13:47:53   BOARD=011    TYPE=0xf0000010    SOFTTYPE=003 



The below alarm appear on T2000 NMS. 

While check the error log of the NE which confirmed the soft reset of above mentioned board. 

ExceptLog:: total = 1                                                                                                                                                                                       

    :   001# 2014-01-13 13:47:14 ExcptErr:   pc=0x002d9cb8, SR=0x9032, FaultAddr=0x00000300,

No.027:  2014-01-13 13:47:53   BOARD=011    TYPE=0xf0000010    SOFTTYPE=003 

1-COMMUN_FAIL causes an alarm. Because the 11th board soft reset 

2-One task in board to routine check the file system to confirm the file is ok . The inspection period was 24 hours. 

3- The inspection process flow exists bug, will cause the time to read the file causes abnormal and soft reset. 

4-  Avoidance scheme is to close the file inspection function, the disadvantage is not checked in time after missing files 

: sftm-set-fpatrol: 11, FILEPATROL, STOP 

4. Permanent solution is to upgrade to R10C03SPC203 and above 



N/A

1- Check the board status found normal, traffic also normal and MSP was in idle state 

2- Check the NE database and found also normal. 

3- Check the reset record of boards by running errlog command on Navigator and found that 11-SL64 board softreset automatically without any abnormality seen. 

4- Test teh MSP switching and found that MSP on 11-SL64 baord is working normaly and found ok. 

5- Check the NE error log through Navigator and confirm the board soft reset status. 

5- Collect the black box of NE to get the analysis from GTAC. 

6- GTAC found that one of the board file was found corrupt to SL64 board due to software bug in V1R8C02 version of OSN 3500. 

Thunder-link.com now have all versions of huawei SL64 board,including :

SSN1SL64(I-64.2,LC), 

SSN1SL64(L-64.2b,LC),

SSN1SL64(Le-64.2,LC),

SSN1SL64(S-64.2b,LC),

SSN1SL64(V-64.2b,LC),

SSN4SL64(Le-64.2,LC),

SSN4SL64(P1L1-2D2,LC),

SSN4SL64(S-64.2b,LC),

SSN4SL64(V-64.2b,LC),

All are original new and have very competitve price. The highest discount reach  98% off list price. Do not hesitate, just come to visit www.thunder-link.com; or email for inquire: sales@thunder-link.com