Maintenance Manual-Alarm and Performance Event

1 Generation of Alarm and Performance Event ............................................ 1.1 Overview of SDH Alarm and Performance Event ................................... 1.
2 Generation and Detection of Alarm and Performance Event in Signal Flow of Higher Order Part ................................................................. 1.2.1 Downlink Signal Flow ..................................................................... 1.2.2 Uplink Signal Flow ......................................................................... 1.3 Generation of Alarm and Performance in Signal Flow of Lower Order Part ..................................................................................................... 1.3.1 Downlink Signal Flow ..................................................................... 1.3.2 Uplink Signal Flow ......................................................................... 1.3.3 Difference between 34M/140M Electrical Interface Alarm Signal and 2M Electrical Interface Alarm Signal ..................................... 1.4 SDH Alarm Suppression ........................................................................ 1.5 Generation and Detection of SDH Performance Event .......................... 1.5.1 Bit Error .......................................................................................... 1.5.2 Pointer Justification ........................................................................ 1.6 Application of Locating a Fault According to Signal Flow ....................... 1.6.1 Bit Error .......................................................................................... 1.6.2 Alarm .............................................................................................. 1.6.3 Summary ........................................................................................ 2 Alarm Handling ............................................................................................. APS_FAIL ..................................................................................................... APS_INDI ..................................................................................................... APS_PARA_ERR ......................................................................................... A_LOC .......................................................................................................... A_LO_J1 ...................................................................................................... AU_AIS......................................................................................................... AU_LOP ....................................................................................................... B1B_EXC ..................................................................................................... B1_EXC ........................................................................................................ B1_SD .......................................................................................................... B2_EXC ........................................................................................................ B2_SD .......................................................................................................... B3_EXC ........................................................................................................ B3_SD .......................................................................................................... BD_STATUS ................................................................................................ BIP_EXC ...................................................................................................... BIP_SD......................................................................................................... BUF_ERR ..................................................................................................... BUS_LOC .....................................................................................................
1-1 1-1 1-4 1-5 1-8 1-10 1-11 1-13 1-14 1-15 1-17 1-17 1-20 1-23 1-23 1-24 1-26 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20
CC_LOC ....................................................................................................... CFG_OVFLOW ............................................................................................ COMMUN_FAIL ........................................................................................... CONF_DATA_LOS ...................................................................................... COOL_CUR_OVER ..................................................................................... DBMS_ERROR ............................................................................................ DBMS_PROTECT_MODE ........................................................................... D_LO_J1 ...................................................................................................... DOWN_E1_AIS ............................................................................................ E1_LOS ........................................................................................................ ETH_LOS ..................................................................................................... EXER_FAIL .................................................................................................. EXT_SYNC_LOS ......................................................................................... FAN_FAIL ..................................................................................................... FI_FAIL......................................................................................................... FPGA_ABN .................................................................................................. HARD_BAD .................................................................................................. HCS .............................................................................................................. HPAD_CROSSTR ........................................................................................ HP_CROSSTR ............................................................................................. HP_LOM ....................................................................................................... HP_RDI ........................................................................................................ HP_REI ........................................................................................................ HP_R_FIFO .................................................................................................. HP_SLM ....................................................................................................... HP_T_FIFO .................................................................................................. HP_TIM ........................................................................................................ HP_UATEVENT ........................................................................................... HP_UNEQ .................................................................................................... IN_PWR_ABN .............................................................................................. IN_PWR_FAIL .............................................................................................. J0_MM .......................................................................................................... K1_K2_M...................................................................................................... K2_M ............................................................................................................ LCD .............................................................................................................. LOCK_CUR_FAIL ........................................................................................ LOOP_ALM .................................................................................................. LP_AIS ......................................................................................................... LP_CROSSTR ............................................................................................. LP_RDI ......................................................................................................... LP_REI .........................................................................................................
2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 2-30 2-31 2-32 2-33 2-34 2-35 2-36 2-37 2-38 2-39 2-40 2-41 2-42 2-43 2-44 2-45 2-46 2-47 2-48 2-49 2-50 2-51 2-52 2-53 2-54 2-55 2-56 2-57 2-58 2-59 2-60 2-61
LP_RFI ......................................................................................................... 2-62 LP_R_FIFO .................................................................................................. 2-63 LP_SIZE_ERR ............................................................................................. 2-64 LP_SLM ........................................................................................................ 2-65 LP_T_FIFO................................................................................................... 2-66 LP_TIM ......................................................................................................... 2-67 LP_UATEVENT ............................................................................................ 2-68 LP_UNEQ ..................................................................................................... 2-69 LSR_WILL_DIE ............................................................................................ 2-70 LTI ................................................................................................................ 2-71 MAIL_ERR ................................................................................................... 2-72 MEM_ERR ................................................................................................... 2-73 MSAD_CROSSTR ....................................................................................... 2-74 MS_AIS ........................................................................................................ 2-75 MS_CROSSTR ............................................................................................ 2-76 MSP_INFO_LOSS ....................................................................................... 2-77 MS_RDI ........................................................................................................ 2-78 MS_REI ........................................................................................................ 2-79 M_S_SW ...................................................................................................... 2-80 MS_UATEVENT ........................................................................................... 2-81 NE_SF_LOST .............................................................................................. 2-82 NESTATE_INSTALL .................................................................................... 2-83 NO_BD_SOFT ............................................................................................. 2-84 OCD ............................................................................................................. 2-85 OTH_BD_STATUS....................................................................................... 2-86 OUT_PWR_ABN .......................................................................................... 2-87 OUT_PWR_UNDULATE .............................................................................. 2-88 POWER_FAIL .............................................................................................. 2-89 PS ................................................................................................................. 2-90 PWR_MAJ_ALM .......................................................................................... 2-91 PWR_MIN_ALM ........................................................................................... 2-92 P_LOS .......................................................................................................... 2-93 RAM_ERR .................................................................................................... 2-94 RAM_LOC .................................................................................................... 2-95 RELAY_ALARM ........................................................................................... 2-96 RR_LOC ....................................................................................................... 2-97 RS_CROSSTR ............................................................................................. 2-98 RS_UATEVENT ........................................................................................... 2-99 R_APS .......................................................................................................... 2-100 R_FIFO_E .................................................................................................... 2-101 R_LOF .......................................................................................................... 2-102
R_LOS .......................................................................................................... R_OOF ......................................................................................................... S1_SYN_CHANGE ...................................................................................... SECU_ALM .................................................................................................. SL4_ALM...................................................................................................... STM_ERR .................................................................................................... SUBCARD_ABN .......................................................................................... SYN_BAD ..................................................................................................... SYNC_C_LOS .............................................................................................. TAIP_LOC .................................................................................................... T_ALOS ........................................................................................................ T_DLOS ....................................................................................................... TEMP_ALARM ............................................................................................. TEMP_OVER ............................................................................................... TEM_HA ....................................................................................................... TF ................................................................................................................. T_FIFO_E ..................................................................................................... T_LOC .......................................................................................................... T_LOS .......................................................................................................... T_LOTC ........................................................................................................ T_LOXC ....................................................................................................... TR_LOC ....................................................................................................... T_TDM ......................................................................................................... TU_AIS ......................................................................................................... TU_LOP ....................................................................................................... UHCS ........................................................................................................... UP_E1_AIS .................................................................................................. VC_AIS......................................................................................................... VC_RDI ........................................................................................................ VER_MISMATCH ......................................................................................... VP_AIS ......................................................................................................... VP_RDI ........................................................................................................ WORK_CUR_OVER .................................................................................... W_R_FAILURE ............................................................................................ WRG_BD_TYPE .......................................................................................... 3 Performance Event Handling ....................................................................... 3.1 Performance Events of SDH Service ..................................................... 3.2 ATM Service Performance Event ........................................................... 3.3 Performance Events of Ethernet Service ............................................... AUPJCHIGH .................................................................................................
2-103 2-104 2-105 2-106 2-107 2-108 2-109 2-110 2-111 2-112 2-113 2-114 2-115 2-116 2-117 2-118 2-119 2-120 2-121 2-122 2-123 2-124 2-125 2-126 2-127 2-128 2-129 2-130 2-131 2-132 2-133 2-134 2-135 2-136 2-137 3-1 3-1 3-6 3-7 3-9
AUPJCLOW ................................................................................................. TUNPJC ....................................................................................................... TUPPJC ....................................................................................................... HPBBE ......................................................................................................... HPCSES ....................................................................................................... HPES............................................................................................................ HPFEBBE ..................................................................................................... HPFEES ....................................................................................................... HPFESES ..................................................................................................... HPSES ......................................................................................................... HPUAS ......................................................................................................... LPBBE .......................................................................................................... LPCSES ....................................................................................................... LPES ............................................................................................................ LPFEBBE ..................................................................................................... LPFECSES................................................................................................... LPFEES ........................................................................................................ LPFESES ..................................................................................................... LPSES .......................................................................................................... LPUAS .......................................................................................................... MSBBE ......................................................................................................... MSCSES ...................................................................................................... MSES ........................................................................................................... MSFEBBE .................................................................................................... MSFECSES .................................................................................................. MSFEES ....................................................................................................... MSFESES .................................................................................................... MSSES ......................................................................................................... MSUAS......................................................................................................... RSBBE ......................................................................................................... RSCSES ....................................................................................................... RSES............................................................................................................ RSOFS ......................................................................................................... RSOOF......................................................................................................... RSSES ......................................................................................................... RSUAS .........................................................................................................
3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 3-35 3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45
HUAWEI
OptiX 2500+(Metro3000) Mutil-service Optical Transmission System Maintenance Manual Alarm and Performance Event V100R006
OptiX 2500+(Metro3000) Mutil-service Optical Transmission System Maintenance Manual

Volume Manual Version Product Version BOM Alarm and Performance Event T2-040382-20040528-C-1.61 V100R006 31033382
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office, customer care center or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District, Shenzhen, P. R. China Postal Code: 518129 Website: http://www.huawei.com Email: support@huawei.com
Copyright 2004 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd. All other trademarks mentioned in this manual are the property of their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has been made in the preparation of this manual to ensure accuracy of the contents, but all statements, information, and recommendations in this manual do not constitute the warranty of any kind, express or implied.
OptiX 2500+(Metro3000) MM-APE
1 About This Manual
Related Manuals
The manual package for an optical network product is shipped with the product. The table below lists the manual for the products. Manual Manuals shipped with the product Volume Usage
Introduces the functionality, structure, performance, specifications, and theory of the product. Introduces the hardware of the product, including cabinet, subrack, power, fan, board, and a variety of interfaces. Guides the on-site installation of the product and provides the information of the structural parts. Routine Maintenance OptiX 2500+(Metro3000) Multi-Service Optical Transmission System Maintenance Manual Troubleshooting Alarm and Performance Event Guides the analysis and troubleshooting of common faults.
OptiX 2500+(Metro3000) Multi-Service Optical Transmission System Technical Manual OptiX 2500+(Metro3000) Multi-Service Optical Transmission System Hardware Description Manual OptiX 2500+(Metro3000) Multi-Service Optical Transmission System Installation Manual
About This Manual
Organization
The manual has the following organization: Chapter
Chapter 1 Principle for Generation Chapter 2 Alarm Handling Chapter 3 Performance Event Handling
Description
Introduces in detail the generation of alarms and performance events and their relationships. It is a base to use alarms and performance events to solve problems. Provides a list of alarms with name, generation cause, and troubleshooting. It provides a way of diagnostic analysis for the user. Introduces the meaning and troubleshooting of performance events in the transmission hierarchy in an order of functions.
Intended Audience
This manual is for:
Maintenance engineer
About This Manual
Conventions
The following conventions are used throughout this publication. Symbol Description
Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Means reader be careful. The equipment is static-sensitive. Means reader be careful. In this situation, the high voltage could result in harm to yourself or others. Means reader be careful. In this situation, the strong laser beam could result in harm to yourself or others.
Means reader take note. Notes contain helpful suggestions or useful background information.
Release Upgrade Description

Release
T2-040382-20040105-C-1.60 T2-040382-20040528-C-1.61
Release upgrade description

This manual is the first release. Appendix the alarm of EGT2 and EFT.
Contents
Generation of Alarm and Performance Event

1.1 Overview of SDH Alarm and Performance Event 1.2 Generation and Detection of Alarm and Performance Event in Signal Flow of Higher Order Part 1.2.1 Downlink Signal Flow 1.2.2 Uplink Signal Flow 1.3 Generation of Alarm and Performance in Signal Flow of Lower Order Part 1.3.1 Downlink Signal Flow 1.3.2 Uplink Signal Flow 1.3.3 Difference between 34M/140M Electrical Interface Alarm Signal and 2M Electrical Interface Alarm Signal 1.4 SDH Alarm Suppression 1.5 Generation and Detection of SDH Performance Event 1.5.1 Bit Error 1.5.2 Pointer Justification 1.6 Application of Locating a Fault According to Signal Flow 1.6.1 Bit Error 1.6.2 Alarm 1.6.3 Summary 1-14 1-15 1-17 1-17 1-20 1-23 1-23 1-24 1-26 1-10 1-11 1-13 1-4 1-5 1-8 1-1
Alarm Handling
APS_FAIL APS_INDI APS_PARA_ERR A_LOC A_LO_J1 AU_AIS AU_LOP B1B_EXC 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9
Contents
B1_EXC B1_SD B2_EXC B2_SD B3_EXC B3_SD BD_STATUS BIP_EXC BIP_SD BUF_ERR BUS_LOC CC_LOC CFG_OVFLOW COMMUN_FAIL CONF_DATA_LOS COOL_CUR_OVER DBMS_ERROR DBMS_PROTECT_MODE D_LO_J1 DOWN_E1_AIS E1_LOS ETH_LOS EXER_FAIL EXT_SYNC_LOS FAN_FAIL FI_FAIL FPGA_ABN HARD_BAD HCS HPAD_CROSSTR HP_CROSSTR HP_LOM HP_RDI
2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 2-30 2-31 2-32 2-33 2-34 2-35 2-36 2-37 2-38 2-39 2-40 2-41 2-42
ii
Contents
HP_REI HP_R_FIFO HP_SLM HP_T_FIFO HP_TIM HP_UATEVENT HP_UNEQ IN_PWR_ABN IN_PWR_FAIL J0_MM K1_K2_M K2_M LCD LOCK_CUR_FAIL LOOP_ALM LP_AIS LP_CROSSTR LP_RDI LP_REI LP_RFI LP_R_FIFO LP_SIZE_ERR LP_SLM LP_T_FIFO LP_TIM LP_UATEVENT LP_UNEQ LSR_WILL_DIE LTI MAIL_ERR MEM_ERR MSAD_CROSSTR MS_AIS
2-43 2-44 2-45 2-46 2-47 2-48 2-49 2-50 2-51 2-52 2-53 2-54 2-55 2-56 2-57 2-58 2-59 2-60 2-61 2-62 2-63 2-64 2-65 2-66 2-67 2-68 2-69 2-70 2-71 2-72 2-73 2-74 2-75
iii
Contents
MS_CROSSTR MSP_INFO_LOSS MS_RDI MS_REI M_S_SW MS_UATEVENT NE_SF_LOST NESTATE_INSTALL NO_BD_SOFT OCD OTH_BD_STATUS OUT_PWR_ABN OUT_PWR_UNDULATE POWER_FAIL PS PWR_MAJ_ALM PWR_MIN_ALM P_LOS RAM_ERR RAM_LOC RELAY_ALARM RR_LOC RS_CROSSTR RS_UATEVENT R_APS R_FIFO_E R_LOF R_LOS R_OOF S1_SYN_CHANGE SECU_ALM SL4_ALM STM_ERR
2-76 2-77 2-78 2-79 2-80 2-81 2-82 2-83 2-84 2-85 2-86 2-87 2-88 2-89 2-90 2-91 2-92 2-93 2-94 2-95 2-96 2-97 2-98 2-99 2-100 2-101 2-102 2-103 2-104 2-105 2-106 2-107 2-108
iv
Contents
SUBCARD_ABN SYN_BAD SYNC_C_LOS TAIP_LOC T_ALOS T_DLOS TEMP_ALARM TEMP_OVER TEM_HA TF T_FIFO_E T_LOC T_LOS T_LOTC T_LOXC TR_LOC T_TDM TU_AIS TU_LOP UHCS UP_E1_AIS VC_AIS VC_RDI VER_MISMATCH VP_AIS VP_RDI WORK_CUR_OVER W_R_FAILURE WRG_BD_TYPE
2-109 2-110 2-111 2-112 2-113 2-114 2-115 2-116 2-117 2-118 2-119 2-120 2-121 2-122 2-123 2-124 2-125 2-126 2-127 2-128 2-129 2-130 2-131 2-132 2-133 2-134 2-135 2-136 2-137
Contents
Performance Event Handling

3.1 Performance Events of SDH Service 3.2 ATM Service Performance Event 3.3 Performance Events of Ethernet Service AUPJCHIGH AUPJCLOW TUNPJC TUPPJC HPBBE HPCSES HPES HPFEBBE HPFEES HPFESES HPSES HPUAS LPBBE LPCSES LPES LPFEBBE LPFECSES LPFEES LPFESES LPSES LPUAS MSBBE MSCSES MSES MSFEBBE MSFECSES MSFEES 3-1 3-6 3-7 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 3-25 3-26 3-27 3-28 3-29 3-30 3-31 3-32 3-33 3-34 3-35
vi
Contents
MSFESES MSSES MSUAS RSBBE RSCSES RSES RSOFS RSOOF RSSES RSUAS
3-36 3-37 3-38 3-39 3-40 3-41 3-42 3-43 3-44 3-45
vii
1 Generation of Alarm and Performance Event
This chapter introduces: Generation of SDH service alarm and performance event Application of SDH service alarm and performance event in fault locating
1.1 Overview of SDH Alarm and
Performance Event
There are abundant overhead bytes in SDH frame structure, including regenerator section overhead, multiplex section overhead, and path overhead. These overhead bytes carry alarm and performance event information, thus enabling SDH system a strong ability of on-line alarm and error monitoring. An understanding of the generation and monitoring modes of the alarm information allows you to locate the failure rapidly. The SDH alarm signal flow is shown in Figure 1-1.
1-1

Physical Regenerator Multiplex Section Section Section SPI RST (Note 1) MST MSA LOS LOF RS-BIP Error (B1) Regenerated signal1 passed through MS-AIS MS-Exc. Error (B2) MS-BIP Error (B2) MS-FERF MS-FERF AU-AIS AU-LOP HO Path signal passed through HOVC with POH and unspecified payload HO unequipped signal 1 1
Higher Order Path

HPOM HUG HPC HPT HPA LPOM
Lower Order Path

LUG LPC LPT LPA
AU-AIS
1 1
Unused HPC output/ HQ-UNEQ
HP-UNEQ HP-TIM HP-SLM HP-BIP Error (B3) HP-FEBE HP-FERF HP-FERF HP-FEBE TU-AIS HP-LOM/TU-LOP LO Path signal passed through LOVC with POH and unspecified payload LO unequipped signal
TU-AIS
1 1
Unused LPC output/ LP-UNEQ
LP-UNEQ LP-TIM LP-SLM LP-BIP Error (B3/V5) LP-FEBE LP-FERF LP-FERF LP-FEBE
T1512780-93/d02
1 AIS FEBE FERF LOF LOM LOP LOS SLM TIM UNEQ
Detection Generation Insertion of all-ones (AIS) signal Alarm Indication Signal Far End Block Error Far End Receive Failure Loss Of Frame Loss Of Multiframe Loss Of Pointer Loss Of Signal Signal Label Mismatch Trace Identifier Mismatch Unequipped signal per Recommendation G.709
Figure 1-1 SDH alarm signal flow
1-2
Generation of Alarm and Performance Event 1. Terminology agreement
In order to describe the positions where common alarms and performance events are generated and the generation modes, it is better to describe these common alarms and performance events in detail along the signal flow. Signal flow, here, will be classified into downlink and uplink signal flows according to the signal flow directions. The so-called downlink signal flow refers to the signal direction from the SDH interface, to the cross-connect board, and then to the PDH interface. On the contrary, the uplink signal flow refers to the signal direction from the PDH interface, to cross-connect board, and then to the SDH interface. The cross-connect board does not process any overhead byte in the signal flow. In order to describe signal flow in hierarchy, signal flow is divided into lower order part (between the cross-connect board and the PDH interface) and higher order part (between the SDH interface and the cross-connect board), with the cross-connect board as the boundary. 2. Two common alarms AIS alarm (i.e. all "1"s alarm) inserts the all "1"s signal to the lower level circuits, indicating that the signal is unavailable. Common AIS signals include MS-AIS, AU-AIS, TU-AIS and E1-AIS. RDI (remote defect indication) alarm: Indicates the alarm transferred back to the home station from the opposite station after the opposite station has tested alarms of LOS (loss of signal), AIS and TIM (trace identifier mismatch). Common RDI alarms include MS-RDI, HP-RDI and LP-RDI. Note: Note that the station does not necessarily have problem when an alarm is detected on it. The alarm detected may be caused by the opposite station or due to other causes. For example, R-LOS alarm is caused by broken fiber, and HP-LOM (higher order path loss of multiframe) alarm at the home station is caused by the failed cross-connect board at the opposite station.
1-3
1.2 Generation and Detection of
Alarm and Performance Event in Signal Flow of Higher Order Part

The fault locating principle is "line first, then tributary; high level first, then low level". Since the alarm and performance data generated in the higher order part will cause the report of the lower order alarm and performance data. We shall first focus on the alarm, performance information generated between the SDH interface and the cross-connect board during maintenance. The signal flow chart of this route is illustrated in Figure 1-2.
Frame synchronizer and RS overhead processor (RST) STM-N optical LOF interface A1, A2
BI Err. LOS "1"
MS overhead processor (MST)

AIS MS-AIS "1"
Pointer processor and HP overhead processor (MSA, HPT)

AIS AU-AIS AU-LOP HP-TIM
K2 B2
B2-Err. MS-REI
H1,H2 H1,H2
J1 HP-UNEQ C2 C2
HP-SLM
"1"
Cross-connect unit
B1
M1 k2
MS-RDI
H4 HP-LOM B3 HP-REI G1 HP-RDI G1 Alarm report or return Alarm termination point (Report to SCC unit)
B3 Err.
Downlink signal flow Signal transfer point (Insert down all "1"s signal)
Figure 1-2 Flowchart of alarm signals generated between the SDH interface and the cross-connect board
Note: According to the processing positions of various overhead bytes in the STM-1 frame structure, we divide the overhead bytes into four modules: regenerator section overhead, multiplex section overhead, and higher order path overhead and pointer. If the first two modules have problems, generally all the higher order paths will be affected, while the problem occurs in the overhead bytes of the last module willonly affect a certain higher order paths. Therefore, we can usually deduce the influencing factor of the problem, and how to select the paths during the test.
1-4
We'll describe the signal flow and processing of each overhead byte module by module in the following.
1.2.1 Downlink Signal Flow

1. Frame synchronizer and regenerator section overhead processor Regenerator section overheads related to alarms and performances that will be mainly processed in this section are: framing byte (A1, A2), regenerator section trace byte (J0), error monitor byte (B1). The alarm signal flow is as follows:
(1) When the STM-N optical signal from the optical line enters the optical receiving module, first, it is recovered into electrical signal after optical/electrical conversion (O/E conversion) and then sent into frame synchronizer and scrambler for processing. In this process, the O/E module monitors this signal. If it is found that there is no light in the input signal, optical power excessively low or high and rate of the input signal mismatch, R-LOS (loss of signal) alarm will be reported.
Prompt: No light usually occurs in the case that the fiber is broken, the optical transmitting module at the opposite station fails or the optical receiving module at the home station fails. The cause of excessively low optical power may be too much fiber attenuation or poor contact of the optical joint, etc. Over high optical power refers to the received optical power overload. If this happens, check whether the optical attenuator is damaged, or the transmission distance of the optical board is suitable, etc. The code type mismatch usually occurs when the signal rate between upstream station and downstream station is inconsistent, or failed STG board at upstream station will cause data transmission disorder, etc. At this moment it is necessary to check whether the optical board at upstream station is matched or the STG board and cross-connect board are in normal operation, etc. R-LOS alarm has no relation with overhead bytes, and it is only related to the quality of input signal.
After R-LOS alarm occurs, only when optical receiving module at the home station has continuously tested two correct patterns of code type, and meanwhile it has not tested any new R-LOS alarm, can SDH equipment quit from R-LOS status and enter normal status. In case R-LOS alarm occurs, the system will insert all "1"s signal to the lower level circuits.
1-5
(2) After frame synchronizer has received STM-N signal sent from the optical/electrical conversion module, it captures A1, A2 framing bytes in the signal. Meanwhile it extracts line reference synchronous timing source from the signal and sends it to the STG board for clock locking.
Normally, the A1 value is F6H, and the A2 value is 28H. If incorrect A1 and A2 values are detected in five successive frames, R-OOF (out of frame) alarm will be reported. If R-OOF alarm lasts for more than 3 ms, it will report loss of frame alarm R-LOF and insert all "1"s signal. In case of R-LOF alarm, if the frame alignment state lasts for more than 1 ms, that means the equipment has resumed to normal. J0 byte is used to confirm that both ends of the regenerator section are in continuous connecting state. It requires that J0 bytes at receive end and transmit end be fully matched. If they are not matched, the equipment will report J0-MM trace identifier mismatch alarm. Scrambler is mainly engaged in unscrambling the bytes in the STM-N signals except for the A1, A2 and J0 bytes.
(3) The regenerator section overhead processor extracts and processes other regenerator section overhead bytes in the STM-N signal. Among all the bytes, B1 byte is of utmost importance.
If the B1 byte recovered from STM-N signal is not in compliance with BIP-8 computing result of the preceding STM-N frame, it will report B1 error. If the number of B1 bit errors exceeds the threshold 10-3, the B1-OVER alarm will be reported. When ten serious errored seconds (SES, i.e. the errored blocks reach to 30% in one second) in regenerator section appear consecutively, it is considered that RSUATEVENT (regenerator section unavailable time event) occurs. At the same time, in this section these bytes, such as F1, D1~D3 and E1, which have nothing to do with alarm will be sent to the SCC board and OHP board. 2. Multiplex section overhead processor Multiplex overhead bytes that are related to alarm and performance and will be processed in this part include: automatic protection switching channels (K1, K2), BIP-N24 (B2), multiplex section remote error indication (M1). The signal flow is as follows:
(1) Multiplex section overhead processor extracts multiplex section overhead bytes in STM-N signal for processing and completes SF and SD detection. It sends D4~D12, S1 and E2 to the SCC unit and overhead unit, meanwhile realizes the shared multiplex section protection (MSP) function by the cooperation of the SCC unit, cross-connect board and K1, K2 bytes.
If the b6-b8 of K2 byte is detected as 111, the MS-AIS alarm will be reported and all 1s signal will be inserted.If the b6-b8 of K2 byte is detected as 110, the MS-RDI alarm will be reported.
1-6
(2) If the B2 byte recovered from the STM-N signal does not consist with the computing result of BIP-24 in the lastly received STM-N frame (All bits expect for the regenerator section overhead), then the processor reports the B2 bit error.
Whether to report MS-REI is determined by M1 bytes. MS-REI transfers the number of error interleaved block detected by B2 byte. If B2 bit error exceeds the threshold 10-6, B2-SD alarm will be generated. If the B2 bit error exceeds the threshold 10-3, B2-OVER alarm will be reported. In multiplex section protection mode, the B2-SD and B2-OVER alarms will give rise to the multiplex section protection switching. When B2 byte detects SES consecutively for 10 seconds (errored block reaches 30% in one second), it is considered as an MSUATEVENT (multiplex section unavailable time event). 3. Pointer processor and higher order path overhead processor. This part processes higher order pointer justification and higher order path overhead. Bytes related to pointer justification are H1, H2 and H3, and those related to alarm and error are path trace byte (J1), signal label byte (C2), path BIP-8 (B3), path status byte (G1), position indicator byte (H4). Their alarm flows are as follows:
(1) The pointer processor interprets and justifies the pointer on the basis of H1, H2 bytes of each AU-4, completes frequency and phase calibration and tolerates phase jitter and wander in the network. At the same time, it locates each VC-4 and sends it to corresponding higher order path overhead processor. If H1 and H2 bytes of AU pointer are detected to be all "1"s, AU-AIS (administrative unit-alarm indication signal) alarm will be reported and all "1"s signal will be inserted. If the indicator values of H1 and H2 are illegal (not in the normal range of 0~782) and receives illegal pointers consecutively in eight frames, then it will report AU-LOP (administrative unit-loss of pointer) alarm and insert all "1"s signal.
In case AU pointer positive justification occurs, the number of the PJCHIGH of the MSA increases by 1. In case AU pointer negative justification occurs, the number of the PJCLOW of MSA increases by 1.
(2) Higher order path overhead processor processes higher order path overhead (HPOH) bytes received in N VC-4s. The processing mode for each byte is as follows.
If J1 byte value detected is not the same as the preset, HP-TIM alarm will be reported and all "1"s signal will be inserted. If C2 byte is detected as 00, Higher Order Path- Unequipped (HP-UNEQ) alarm will
1-7
be reported and all "1"s signal will be inserted. When C2 byte detected is different from the preset, Higher Order path - Signal Label Mismatch (HP-SLM ) alarm will be reported and all "1"s signal will be inserted. Note: Some of the line boards of the OptiX 2500+ detect HP_TIM and HP_SLM, but they do not insert AIS.
If B3 byte recovered from HPOH is not in compliance with BIP-8 computing result of VC-4 signal of the preceding frame, B3 bit error will be reported. In OptiX STM-N (N<=4) lower order SDH interface board, when extracting TU-12 signal from VC-4, H4 byte is required to indicate which frame of the current multiframe the current TU-12 is in. When H4 byte is tested as illegal, then Higher Order Path- Loss of Multiframe (HP-LOM ) alarm will be reported, and all "1"s signal will and normal H4 byte will be inserted. If the b5 of G1 byte is detected 1, HP-RDI alarm will be reported. Whether to report HP-REI alarm depends on the value of G1 (b1-b4). If the value of G1 (b1-b4) is 1~8, HP-REI alarm will be reported. When B3 has detected SES consecutively for ten seconds (errored block reaches 30% in one second), it is considered as an HVCUATEVENT (higher order virtual container unavailable time event). Other overhead bytes F3, K3, N1 are reserved for future use.
(3) Finally, N STM-1 payload processed in the above way is sent to the cross-connect board for cross connection of higher order path and lower order path.
1.2.2 Uplink Signal Flow

The extraction and termination of overhead bytes are completed in the downlink signal flow of higher order part, and the generation of initial value for overhead byte and the return of alarm signal to the opposite station are completed in the uplink signal flow of higher order part. 1. Pointer processor and higher order path overhead processor.
(1) N STM-1 payload signals from the cross-connect board is firstly sent to higher order path overhead processor. (2) The higher order path overhead processor generates N higher order path overhead bytes, which are sent to pointer processor together with N payload. Along the uplink direction, the setting function of higher order path
1-8
overhead bytes (including J1, C2, B3, G1, F2, F3 and N1) can be completed. If AU-AIS, AU-LOP, HP-UNEQ or HP-LOM (HP-TIM and HP-SLM optional) alarms are detected in downlink signal flow, set the b5 of G1 byte to 1 and HP-RDI alarm will be returned to the remote. If B3 bit errors are tested in the downlink signal, set the b1-b4 of G1 byte to a corresponding bit error value (ranging 1~8) according to the error value tested, and HP-REI alarm will be returned to the remote end. H4 byte will not be processed in the uplink direction.
(3) Pointer processor generates N AU-4 pointers, adapts VC-4 into AU-4, among which AU-4 pointer is represented by H1 and H2 bytes, then N AU-4s are multiplexed into STM-N signal by multiplexing processor and sent to multiplex section overhead processor.
2. Multiplex section overhead processor Multiplex section overhead processor sets MSOH bytes (including K1, K2, D4-D12, S1, M1, E2 and B2) for the received STM-N signal. If R-LOS, R-LOF or MS-AIS alarms are detected in the downlink signal flow, the b6-b8 of K2 byte will be set to 110 and MS-RDI will be returned to the remote. If B2 bit errors are tested in the downlink signal flow, MS-REI alarm will be returned to the remote via the M1 byte.. 3. Frame synchronizer and regenerator section overhead processor
(1) Regenerator section overhead processor sets overhead bytes in regenerator section (including A1, A2, J0, E1, F1, D1-D3 and B1), and send a complete STM-N electrical signal to frame synchronizer and scrambler. (2) Frame synchronizer and scrambler scrambles STM-N electrical signals (except for A1, A2, J0), then STM-N electrical signal is converted into STM-N optical signal by the E/O module and sent out of the optical interface.
1-9
1.3 Generation of Alarm and
Performance in Signal Flow of Lower Order Part

PDH services include 1.5Mbit/s, 2Mbit/s, 34Mbit/s and 140Mbit/ services. PDH services at different rates use different path overhead bytes. Thus the alarm signal generation modes differ slightly. The following will describe the processing of the signal flow between PDH interface and the cross-connect board, and the generation of alarms by taking 2Mbit/s service as an example. The alarm signal flow is as shown in Figure 1-3.
HPA , LPT LPA E1-AIS All "1''s V5 Cross-connect board V5 J2 V1, V2 V1, V2 LP-SLM LP-UNEQ LP-TIM TU-LOP TU-AIS LP-TFIFO E1 interface PPI T-ALOS
H4 HP-LOM V5 LP-RDI E1-AIS V5 V5 LP-RFIFO BIP-2 LP-REI All "1''s
Signal flow Signal transfer point (Insert down all "1"s signal)
Alarm report or return Alarm termination point (Report to the SCC unit)
Figure 1-3 Flow chart of the generation of alarm signals between the 2M PDH interface and the cross-connect unit
In view of different characteristics of processing the overhead bytes in each part, the lower order part is divided into several functional modules in the above diagram. They are higher order path adapter (HPA), lower order path terminal (LPT), lower order path adapter (LPA) and asynchronous physical interface in sequence. In the
1-10
following, we will take these functional modules as index to introduce alarm signal flow.
1.3.1 Downlink Signal Flow

1. Higher order path adaptation (HPA) and lower order path terminal (LPT) This part is the core of lower order part, because most of the lower order overhead bytes are processed here, including lower order path pointer indicator bytes (V1, V2, V3), V5 byte, and path trace byte (J2).
(1) VC-4 signal from the cross-connect unit is sent to HPA. (2) HPA demaps the VC-4 into VC-12. Pointers of all VC-12s are decoded, so as to provide, between the VC-4 and the VC-12, the frame offset information in byte.
When node clock at TU-12 assembler is different from local reference clock, this process needs continuous pointer justification. Positive TU pointer justification (LPPPJE) and negative TU pointer justification (LPNPJE) will be tested in downlink signal flow. The TU pointer justification count threshold-crossing (The threshold is adjustable) is expressed in a group of alarms HPADCROSSTR. HPADCROSSTR includes: HPADPJCHIGHCX15 (TU pointer positive justification count threshold-crossing for 15 minutes); HPADPJCHIGHCX24 (TU pointer positive justification count threshold-crossing for 24 hours); HPADPJCLOWCX15 (TU pointer negative justification count threshold-crossing for 15 minutes); and HPADPJCLOWCX24 (TU pointer negative justification count threshold-crossing for 24 hours). If incorrect H4 multiframe byte sequence is detected in the downlink, then the HP-LOM alarm is reported. If V1 and V2 are detected to be all 1s, TU-AIS alarm will be reported. If the values of V1 and V2 are tested illegal, TU-LOP alarm will be reported. If either of these two alarms occur, all "1"s signal will be inserted down to the next function block. In addition, if TU-AIS alarm is received, AIS signal will be inserted in the downward data, and LP-RDI will be returned. To return LP-RDI is to set the b8 of V5 byte to "1".
(3) The VC-12 signal flow is sent to the LPT unit for the V5 byte processing.
Composition of timeslot structure of V5 byte is as shown in Figure 1-4.
1-11

V5 byte
b1
b2
b3
b4
b5
b6
b7
b8
BIP-2 error check Inconsistent:LPBBE 1:LP-REI Unused
Signal label 000:LP-UNEQ 1:LP-RDI
Figure 1-4 The structure of V5 byte
Detect the b5-b7 of V5 byte in the downlink signal flow, and report them as signal labels. If they are 000, it means that lower order paths are not equipped (LP-UNEQ), insert AIS signal into the lower level circuit. If signal labels mismatch, LP-SLM will be reported and AIS signal will be inserted to the lower level circuit. Path RDI information in the b8 of V5 byte will be terminated, and REI will be reported. Detect error monitoring bits of the b1 and b2 of V5 byte and calculate BIP-2 for VC-12. BIP-2 value calculated for the current frame will be compared with the b1 and b2 of V5 byte recovered from the next frame. LPBBE will be reported if they are inconsistent. Meanwhile the b3 of V5 byte is recovered, and if it is "1", it means that the remote has BIP-2 bit error and will report it as LPFEBBE. The b4 of V5 byte is not used. When BIP-2 finds ten consecutive SESs (errored block reaches 30% in one second) appears continuously during the test, it is considered as an LVCUATEVENT (lower order virtual container unavailable time event).
(4) At the same time, the lower order path trace identifier J2 will be recovered and it tests whether the value of J2 byte received is equal to the expected value. If they are not equal, lower order path trace identifier mismatch alarm (LP-TIM) will be reported.
2. Lower order path adaptation (LPA) and asynchronous physical interface (PPI)
(1) C-12 data processed in the above way are sent to LPA. Subscriber data stream and the related clock reference signals are recovered from the container simultaneously, and sent to PPI as data and timing reference. (2) The data and clock, after being processed by LPA, are sent to PPI, forming a 2048kbit/s signal.
1-12
1.3.2 Uplink Signal Flow

1. Lower order path adaptation (LPA) and Plesiochronous physical interface (PPI)
(1) When E1 electrical signal enters PPI and after clock extraction and dada regeneration, it is sent to mapping and de-mapping processor, meanwhile jitter suppression will be performed.
PPI checks and terminates the T-ALOS alarm. When it tests T-ALOS alarm, it will insert all "1"s signals in the upper level circuit.
(2) LPA completes the data adaptation

If it receives E1-AIS, it will report E1-AIS alarm. T-ALOS alarm can cause E1-AIS alarm, but in case T-ALOS alarm occurs, E1-AIS alarm will be suppressed. If the deviation of uplink data rate is too great, it will result in FIFO overflow at the transmit end of lower order path, thus LP-TFIFO will be reported. 2. Higher order path adaptation (HPA) and lower order path terminal (LPT)
(1) LPT allows the POH to be inserted in the C-12 to constitute the VC-12.
LPT inserts "signal label" in the b5-b7 of V5 byte, calculate BIP-2 for the previous multiframe data and set the result to the b1 and b2 of V5 byte in the frame. If it is tested in downlink signal flow that the downlink data has "path terminal error", the b3 of V5 byte will be set to "1" in the next frame and return LP-PEI.
(2) HPA adapts VC-12 into TU-12, then maps it into higher order VC-4, and sends it to the cross-connect unit. The frame offset in byte between the VC-12 and the VC-4 is expressed in a TU-12 pointer. Each frame defines one of V1, V2, V3, and V4 bytes, and every four frames compose a multiframe, and, the H4 byte that is used to determine the value of V byte is also generated here.
1-13
1.3.3 Difference between 34M/140M Electrical Interface Alarm Signal and 2M Electrical Interface Alarm Signal
For 34Mbit/s and 140Mbit/s PDH services, the flow of signal processing is the same as that of 2Mbit/s PDH service But there is still much difference. For example: 1. Same type of alarms with different names
(1) For 2M electrical interface board (such as PD1), the external signal loss alarm of its PDH interface is T-ALOS alarm. For 34M electrical interface unit (such as PL3), the external signal loss of its PDH interface is indicated by P-LOS. For 140M electrical interface unit (such as PL4), this alarm is indicated by EXT-LOS. (2) In 2M electrical interface board (such as PD1), when signals in downlink signal flow are detected as all "1"s, it will report TU-AIS alarm. In 34M electrical interface (such as PL3), it will report E3-AIS alarm. In 140M electrical interface unit (such as PL4), C4-RLAISD is used to indicate that the payloads tested in downlink direction are all "1"s, but C4-TLAISD is used to indicate that the payloads tested in uplink direction are all "1"s. EXT-LOS alarm will cause C4-TLAISD alarm.
2. Path overhead bytes used for alarm and performance monitoring are different The path overhead bytes used in 34M interface unit and 140M interface unit are B3, J1, C2 and G1 bytes. Among them, B3 byte is used for error monitoring with the even BIP-8 code. Its function is the same as that of the b1-b2 of V5 byte. The function of J1 byte is the same as that of J2 byte. C2 byte is the signal label byte and its function is the same as the b5-b7 of V5 byte. G1 byte is used for generating alarm reply. Its bit structure diagram is shown in Figure 1-5.
b1 b2 b3 b4 b5 b6 b7 b8
LP-REI
LP-RDI
Reserved
Spare
Figure 1-5 G1 bit structure
Here, the coding meaning of b1 to b4 of G1 byte is: 0000-1000 indicates that there are 0 to 8 errors respectively, and 1001-1111 indicates that is no errors.
1-14
1.4 SDH Alarm Suppression

Through the above analysis of various common alarms in the alarm signal flow, we find that the alarms are associated with each other. Some alarms trigger other alarms. In particular, higher order alarms often generate lower order alarms. Here is a simple example. If R-LOS is generated on the optical board due to optical path fault, AIS is inserted into the downstream circuit, i.e., the overhead bytes are all "1"s. It triggers a series of alarms, such as R-LOF, R-OOF, and MS-AIS etc. The generation of these alarms is natural, but it is not practical for the maintenance personnel. As the upstream node fails, it is not necessary to talk about the downstream nodes. In addition, the downstream alarms triggered increase the amount of data reported and the workload of the NMS and the SCC if they are all reported simultaneously networkwide. They also increase the complexity of the problem for the user. To avoid it, alarm suppression comes into picture to suppress the alarms that are not necessary to report. The following explains how the suppression of the main alarms is done, as shown in Figure 1-6.
R-LOS R-LOF
B2-EXC
MS-AIS
AU-LOP
AU-AIS
HP-UNEQ
HP-TIM
HP-SLM
TU-AIS
Figure 1-6 Suppression tree of main alarms
The higher level alarm on the tail side of the arrow will suppress the lower level alarms on the head side of the arrow. In this way, we can locate the higher level alarm when a fault occurs.
1-15
Prompt: Note that performance event data at different levels cannot be suppressed, though alarms at different levels may be suppressed. For example, when B1 bit error occurs, the system will not act to generate B2 bit error. B2 bit error is generated based on the computing of data within its working scope.
1-16
1.5 Generation and Detection of
SDH Performance Event

The performance of an SDH network includes bit error performance, jitter performance, wander performance, and availability indices. They are important for the transmission QoS of the SDH network.
1.5.1 Bit Error

1. Generation mechanism The SDH system adopts bit interleaved parity (BIP) to detect bit error, i.e., BIP is done on the BIP matrix of the regenerator section, multiplex section, higher order path, and lower order path with the B1, B2, B3 and V5 bytes. The B1 byte is allocated for the regenerator section error monitoring function. This function shall be a Bit Interleaved Parity 8 (BIP-8) code using even parity. The working mechanism for the B1 byte is as follows: At the transmit end the BIP-8 is computed over all bits of the previous STM-N frame after scrambling and the result is placed in the B1 byte of the current frame before scrambling. At the receive end the BIP-8 is computed over all bits of the current STM-(N-1) frame before descrambling and the result is compared with the value of B1 byte of the next STM-N frame after descrambling. If the two values are different, conduct exclusive-OR operation on them. The number of "1"s in the result is the number of errored blocks in the STM-N frame during transmission. The B2 byte is allocated for multiplex section error monitoring function and its mechanism is similar to that of B1 byte. This function shall be a Bit Interleaved Parity N 24 code (BIP-N 24) using even parity. The B1 byte monitors the errors occurring in the whole STM-N frame during transmission. One STM-N frame has one B1 byte. The B2 byte monitors the errors occurring in every STM-1 frame of the STM-N frame. There are N 3 B2 bytes in an STM-N frame, namely, three B2 bytes for one STM-1 frame. The mechanism for the B2 byte monitoring is that at the transmit end the BIP-24 is computed over all bits of the previous STM-1 frame except for the RSOH and the result is placed in B2 bytes of the current frame before scrambling. At the receive end the BIP-24 is computed over all bits of the current frame STM-1 after descrambling except for the RSOH and conducts exclusive-OR operation between the parity result and B2 bytes in the next frame after descrambling. The number of "1"s in the result of the exclusive-OR operation is the number of errored blocks occurring in this STM-1 frame within the STM-N frame during transmission. This method can at most monitor 24 errored blocks. The B3 byte is allocated for monitoring the bit error performance of VC-4 within the STM-N frame during transmission, i.e., monitoring the error performance of 140Mbit/s signal within the STM-N frame. Its monitoring mechanism is similar to that
1-17
of the B1 and B2 bytes except that it is used to process BIP-8 parity for the VC-4 signal. The V5 byte provides the functions of error monitor, signal label and path status of the VC-12 path. Bits 1- 2 convey the BIP-2. If the receive end monitors errored blocks through BIP-2 and will display the errored blocks as performance events. Bit 3 of the V5 byte returns lower order path remote error indication (LP-REI) to the transmit end and LP-REI will be displayed as performance event in the transmit end. 2. Error detection and report Figure 1-7 shows the error detection relation and location.
LPT HPT MST RST RST MST HPT LPT
B1 B2 B3 V5
Figure 1-7 Error detection relation and location
In Figure 1-7 RST is regenerator section terminal, MST is multiplex section terminal, HPT is higher order path terminal, and LPT is lower order terminal. The B1, B2, B3 and V5 bytes are allocated to monitor them respectively. Figure 1-7 shows that errors occurring in lower order path will not be detected in higher order path, multiplex section and regenerator section. If errors occur in regenerator section, they will occur to multiplex section, higher order path and lower order path as well. Generally higher order bit errors will trigger lower order errors. If there is B1 error, B2 ,B3 and V5 errors will usually be generated. If V5 bit error occurs, B3, B2 and B1 bit errors do not necessarily occur. When it detects errors, the SDH system reports error performance or alarm and notifies the remote end through overhead bytes about error detection 3. Terms Errored block (EB) is a block in which one or more bits are in error. Background block error (BBE) is an errored block not occurring as part of an SES. Far-end background block error (FEBBE) is a BBE event detected at the far-end. Errored second (ES) is a one second period with one or more errored blocks or at least one defect.
1-18
Far-end errored second (FEES) is an ES event detected at the far-end. Severely errored second (SES) is a one-second period which contains 30% errored blocks or at least one serious disturbance period (SDP). Here, the SDP is a period of at least four consecutive blocks or 1ms (taking the longer one) where the error ratios of all the consecutive blocks are 10-2 or loss of signal occurs. Far-end severely errored second (FESES) is a SES event detected at the far-end. Consecutive severely errored seconds (CSES) are that the SES events consecutively occur, but last for no more than 10 seconds. Far-end consecutive severely errored seconds (ECSES) is a CSES event detected at the far-end. Unavailable second (UAS) is a period of unavailable time begins at the onset of ten consecutive SES events. These ten seconds are considered to be part of unavailable time. 4. Relationship with alarms The SDH system reports error performance or alarm event to the home station and returns error detection information to the remote stationvia overhead bytes. Based on these performance and alarm events from the home station and remote station, we can locate faulty section of the path or locate the direction where errors occur. Table 1-1 lists the performance and alarm events related with errors.
Table 1-1 Monitor positions and functions of alarm and performance events for bit error threshold crossing
Item
Performance event
Performance events both detected and reported by the home station Performance events detected by the remote station, while reported by the home station MSFEBBE HPFEBBE LPFEBBE
Alarm event
Alarm events reported by the home station when it detects error threshold-crossing B1_OVER B2_OVER HPCROSSTR LPCROSSTR Alarm events reported by the home station when the remote station detects error threshold-crossing MS_REI HP_REI LP_REI
Regenerat or section Multiplex section Higher order path Lower order path
RSBBE MSBBE HPBBE LPBBE
(1) If the B1 byte recovered from STM-N signal is not consistent with BIP-8 computing result of the previous STM-N frame, B1 bit error will be reported. (2) If the B2 byte recovered from the STM-N signal does not consist with the result of BIP-24 computing over all bits expect for the regenerator section
1-19
overhead in the previous STM-N frame, B2 bit error will be reported.
(3) If the B3 byte recovered from HPOH is not in compliance with BIP-8 computing result of VC-4 signal of the previous frame, B3 bit error will be reported. (4) If B1, B2 and B3 bit errors exceed 10-6 , such alarms as B1_SD, B2_SD, B3_SD will occur. If B1, B2 and B3 bit errors exceed 10-3, such alarms as B1_OVER, B2_OVER and B3_OVER will occur.
When B1 detects ten SES events in regenerator section appear consecutively , it is considered as an RSUATEVENT (regenerator section unavailable time event). When B2 detects the SES consecutively for 10 seconds, it is considered as a MSUATEVENT (multiplex section unavailable time event) . When B3 tests the SES consecutively for 10 seconds, it is considered that HVCUATEVENT (higher order virtual container unavailable time event) happen.
1.5.2 Pointer Justification

Pointer justification is a phenomenon especially for the SDH network. The occurring of pointer justification indicates that there exists the NE out of synchronization in the SDH network Payload pointer in the SDH can be classified into administrative unit pointer (AU_PTR) and tributary unit pointer (TU_PTR), and so pointer justification falls into administrative unit pointer justification and tributary unit pointer justification. 1. Generation mechanism of AU pointer justification In the AU-4 frame as shown in Figure 1-8, several bytes in specific locations (the first nine bytes in the four row) are used to record the location of the starting point of data information (to represent the data information phase). These bytes are called pointer.Here, H1 and H2 are pointers, and three H3s are negative pointer justification opportunities.
9 row H1 Y Y H2 1* 1* H3 H3 H3 1 9 10 270 column VC-4
AU- 4 PTR Y 1* Byte : 1001SS11 11111111 Byte :
(S Unspecified )
Figure 1-8 AU pointer location and content
When the network is synchronous, the pointer is used to make phase alignment
1-20
among synchronous signals. If the SDH NEs work in the same clock, the signals sent from various NEs to a certain NE have the same clock frequency, it is unnecessary to make rate adjustment. In the transient point of view, it may be either a little faster or slower, and so the phase alignment is needed. When the network is out of synchronization, different NEs will work with phase difference, and the pointer is used for frequency justification. The pointer justification can also be used to tolerate the frequency jitter and wander of the network. If the frame rate of the VC is different from that of the AUG, information will be stuffed in the H3 bytes of AU pointer area or idle bytes stuffed with pseudo-random information will be inserted to decrease or increase the frame rate of the VC. Meanwhile the pointer value will be incremented or decremented to raise or drop the frame rate of the VC. Thus, the pointer positive justification and negative justification are generated as shown in Table 1-2.
Table 1-2 Pointer justification state
State name
Pointer zero justification Pointer positive justification Pointer negative justification
Byte numbering and content of the fourth row in the STM-1 frame 7 8 9 10 11 12
H3 H3 H3 Information Information Information
Rate relation
Information rate = container rate Information rate < container rate Information rate > container rate
H3
H3
H3
Stuffing
Stuffing
Stuffing
Information
Information
Information
Information
Information
Information
All the NEs in the SDH network are normally well synchronized, the pointer justification seldom occurs. Actual monitoring on the pointer justification performance of the network proves that AU pointer justification seldom occur and TU pointer justification is also few. It is difficult to guarantee all the NEs are well synchronized in all the time during the long-term network running. If one or several NEs is out of synchronization, and even if this situation lasts for a very short time, a great amount of pointer justifications will occur. Pointer positive or negative justification consecutively appear to adjust phase forward or backward to realize frequency justification. 2. Generation mechanism of TU pointer justification The causes of TU pointer justification are as follows:
(1) Transformed from the AU pointer justification

TU pointer justification cannot appear when E1 signal is adapted into VC-12, then into STM-1. If there is frequency offset between E1 signal of the switch and SDH clock, adapt it to realize synchronization. So the TU pointer justification detected on
1-21
the tributary board are generally transformed from the AU pointer justification. The TU pointer justification happens during the demultiplexing.
(2) The system clock is not consistent with the receiving clock, and TU pointer justification will be generated during the demultiplexing. (3) When the service passes through the upstream NE which has pointer justification, TU pointer justification will appear at the home station during the demultiplexing.
3. Detection and reporting of the pointer justification There are two modes of detection and reporting of AU pointer justification: remote detection and home detection. [Remote detection] In this mode the AU pointer justification generated at the home station is transferred to the remote station via H1 and H2 bytes. The remote station realizes the reporting of the AU pointer justification by interpretation of H1 and H2 bytes. So in this mode, if the remote station reports AU pointer justification event, it indicates that home station has pointer justification. Here, the remote station refers to the downstream station along the clock tracing direction. [Home detection] In this mode the AU pointer justification generated at home station is detected and reported at the home station. So, if the home station reports AU pointer justification event, it indicates that the home station has pointer justification. In SDH system the AU pointer justification events of a majority of optical boards are detected and reported by interpreting H1 and H2 bytes. That is, remote detection mode is generally adopted. The TU pointer justification reported on the tributary board is a interpretation of transforming AU pointer justification into TU pointer justification. Since the transformation of AU pointer justification into TU pointer justification may happen at the upstream station, it does not necessarily indicate that the home station has pointer justification if the tributary board reports pointer justification events. Generally, AU pointer justification is generated at the upstream station, while detected and reported at the downstream station. TU pointer justification is generated at the station where AU pointer justification is transformed into the TU pointer, and detected and reported at the tributary board of the station where the service is terminated.
1-22
1.6 Application of Locating a Fault
According to Signal Flow

Through the above study we are clear about the alarm signal flow, and we lay a theoretical foundation for practical application. It is our ultimate goal to guide practice with theory in promptly locating and removing the faults according to the signal flow principles. The following describes two typical cases and we hope they help in our troubleshooting.
1.6.1 Bit Error

(1) Networking diagram
Figure 1-9 shows a certain networking diagram.
W A W B E W C
Figure 1-9 Networking diagram in analysis of error problem
It is a chain network formed by three OptiX 2500+ NEs at the rate of 2.5Gbit/s. Station A is a gateway station. There is 2Mbit/s service among the stations in distributed service mode.
(2) Fault phenomena

Query the tested performance data from the NMS. It is found at station A that the services between Stations A and B, between Stations A and C have a large amount of LPBBE in the tributary, and a great deal of HPBBE, MSBBE in the westbound line. Check Station B, and find a great number of HPFEBBE, MSFEBBE in the eastbound line, and the service between Stations A and C has a majority of LPFEBBE in the tributary, but the services between Stations B and C is normal. Check Station C, and find that the service between Stations C and A has a number of LPFEBBE only in the tributary.
(3) Fault analysis

According to the principle of " station first, board second", locate the faulty NE first. There are bit errors between Stations A and B, between Stations A and C, and no bit error between Stations B and C. According to this we can judge that the fault lies between Stations A and B. Because all services with errors pass this section of route. But is the problem in Station A or B, or in the optical path? We have to analyze performance data. First, we analyze the performance data in the line according to the principle of "higher level first, lower level second, and line first, tributary second".
1-23
From the signal flow knowledge mentioned above, we may know that there are three types of bit error monitoring overhead bytes B1, B2, B3 in the line. B1 byte monitors the route between regenerator sections of two stations; B2 byte monitors the route between the multiplex sections of the two stations; B3 byte monitors only the route between higher order paths of the two stations. Obviously, the route monitored by B3 byte covers that monitored by B2 and B1 bytes, and the route monitored by B2 byte covers that monitored by B1 byte. As seen from the on-site data, there are only B2 and B3 bit errors. This means that the route between the regenerator sections of the two stations is sound, thus excluding the possibility of the optical path fault. If there are B2 bit error, there may be a failure on the route between the multiplex sections of the two stations. In terms of the contents of bit error data, Station A has BBE, and Station B has FEBBE. It shows that the bit errors in the signal are tested at Station A, but it does not mean that the problem must be in Station A as the bit errors are all tested in downlink signal flow. Therefore, the bit errors tested in Station A may come either from the receive end of the home station or from the transmit end of remote station B. Now, we may troubleshoot station one by one. First self-loop the westbound optical line of Station A and find that the errors of this station disappear, then the problem is not in this station. Replace the westbound optical board S16 of Station B, and find that the bit errors of the whole network disappear, then the problem is solved. Tips: In the analysis of the above problem, according to the coverage relation of routes tested by B1, B2 and B3 bytes, we take such an assumption as B1 bit error would cause B2 and B3 bit errors, and B2 bit error would cause B3 bit error. But, in fact, this regularity is not absolute. Though the routes tested by B1, B2 and B3 bytes have coverage relation, the contents tested by the three bytes respectively don't have coverage relation. B1 byte detects all bytes of STM-N frame, but B2 byte only detects all bytes except regenerator section overhead and B3 byte only detects all bits of VC-3 and VC-4 of each path. Hence, if the overhead bytes get bit errors, the inclusion relation among the three will be broken off. For example, if errors tested in regenerator section overhead byte B1 cannot be tested by B2 and B3 bytes. However, in actual maintenance it is seldom to find that the errors only occur in the overhead byte. We can make use of the route coverage relation of B1, B2 and B3 bytes to locate the failure as a rule of thumb.
1.6.2 Alarm
The thought of troubleshooting according to the alarm is similar to that of troubleshooting according to the performance parameters. The only difference is that bit error problem is simple in variety, while alarm problem is rather complicated. Many kinds of alarms are often mixed together which brings difficulty in troubleshooting. If we consider alarms comprehensively according to their
1-24
generation mechanism in signal flow, common problems can be solved. The following describes a simple example.
(1) Networking diagram

Figure 1-10 shows the networking diagram.
W E F W E D C A E W B E
Figure 1-10 Networking diagram in analysis of alarm problem
Six OptiX 2500+ NEs of A, B, C, D, E and F form a multiplex section ring of 2.5Gbit/s. It is a centralized service. Each station has service with Station A.
(2) Fault phenomena

After the equipment operates for a period of time, it is often found that abnormal switching occurs in the whole network, resulting in the interruption of all services. Specific phenomena are as follow: Query the switching status of each station and find that Stations A and B are eastbound and westbound switching respectively, and, Stations C, D and E are in pass-through status, but Station A is always in idle status. When the switching occurs, the eastbound and westbound optical boards of Station A have momentary T-LOS (transmitting loss of signal) alarms. The eastbound optical board of Station F and the westbound optical board of Station B have HP-LOM alarms respectively. Each station has PS alarm except Station A. Services of all stations have TU-AIS alarms.
(3) Fault analysis

According to the principle of "station first, board second", first locate the problem in a single station. The T-LOS alarm usually indicates that the cross-connect board sends no signal or the signal without frame structure to the line board. This alarm is the one tested in the uplink signal flow. The HP-LOM alarm is the one tested in the downlink signal flow. It shows that H4 byte is illegal in the route from the opposite station generation point to the termination point of the home station. These two alarms are both probably related with Station A. Hence, we can locate the problem in Station A. Through the analysis of these two alarms, we know that why H4 becomes illegal is the poor coordination of the cross-connect board and line board, or the line board failure or the cross-connect board failure. Usually, T-LOS alarm is related to the
1-25
signal sent to line unit by the cross-connect unit. Meanwhile, considering that the eastbound and westbound optical boards of Station A report T-LOS alarms at the same time, and the cross-connect board is more likely faulty compared with the line board. Then try replacing the cross-connect board. After replacing the cross-connect board, observe it for some time and find that fault phenomena do not reappear. The problem has been removed.
1.6.3 Summary
Taking the advantage of generation locations of various alarms in the alarm signal flow, you can narrow down the problem area step by step, thus achieving rapid fault locating. Therefore, it is essential for professional maintenance personnel to grasp the corresponding principles of the alarm and performance signal flow.
1-26
2 Alarm Handling
In the maintenance of OptiX 2500+ equipment many alarms need to be dealt with, and an effective analysis of alarms is the key to solve the problem. To find out the source of the problem, find the causes of the alarms first. Then use effective methods to remove them. The following describes the causes and Handling of the alarms generated in the OptiX transmission equipment as a reference for maintenance. Note: 1. Alarm level is the default one. 2. In terms of alarm generation and treatment, the alarms are classified into equipment alarm, Communication alarm, QoS alarm, processing alarm, environment alarm and security alarm.
2-1
Alarm Handling
APS_FAIL
Item
Alarm name Full name Alarm level Alarm type Alarm board Alarm indication Causes
Description
APS_FAIL APS protection switching failed Major Communication alarm SCC Alarm indicator flashes twice every other second (1) MSP switching failed; (2) Wrong settings of MS node; (3) Information of MS node lost.
Handling
(1) Check whether the current configuration of NE multiplex section protection switching is correct; if not, configure it again; (2) Check whether the K byte pass-through and automatic report of the NE are normal and replace the faulty board with a new one.
Remarks
2-2
Alarm Handling
APS_INDI
Item
Descriptin
APS_INDI APS protection switching indication Major Communication alarm SCC Alarm indicator flashes twice every other second (1) MSP switching occurred.
Handling
(1) For the networking in ring multiplex section protection mode, the alarm indicates that multiplex section protection switching happens. Please locate the reason of protection switching; (2) For the networking in non-ring multiplex section protection mode, the alarm indicates APS protocol is started abnormally and protection switching happens. The cause may be that the parameter of APS node is set incorrectly, please check whether the configuration is wrong or re-make the configuration; if the configuration is correct, replace the SCC board with a new one.
Remarks
2-3
Alarm Handling
APS_PARA_ERR
Item
Description
APS_PARA_ERR Fail to verify multiplex section node parameter Major Processing alarm SCC Alarm indicator flashes twice every other second (1) MS node parameters not configured; (2) Configuration of MS node parameters error; (3) MS node parameters configured anti-clockwise.
Handling
Remarks
2-4
Alarm Handling
A_LOC
Item
Description
A_LOC Add to bus - loss of clock Major System alarm PL3/PQ3 Alarm indicator flashes twice every other second (1) Cross-connect board failed or not in position; (2) The STG failed or not in position.
Handling
(1) Check whether the cross-connect board and STG board are in position and whether the running indicator and alarm indicator are normal. If they are in position, reset or swap them; (2) Replace the cross-connect board or STG board.
Remarks
2-5
Alarm Handling
A_LO_J1
Item
Description
A_LO_J1 Adding signal - J1 lost Minor Communication alarm PL3 Flash once every other second (1) Cross-connect board failed or not in position; (2) Board failure.
Handling
(1) Check whether the cross-connect board is in position and whether the running indicator and alarm indicator are normal. (2) Reset or swap the cross-connect board; (3) Replace the cross-connect board.
Remarks
2-6
Alarm Handling
AU_AIS
Item
Description
AU_AIS AU alarm indication Major Communication alarm S16/SD4/SQ1/SD1/SDE /SL1/SL4/SQE/SV4/AL1/SPQ4/EMS1/EFS0/EGT/EGT2 Alarm indicator flashes twice every other seond. (1) Received AU-AIS signal of opposite end; (2) Fault in transmitting part of opposite end; (3) Fault in receiving part of this station.
Handling
(1) MS_AIS, R_LOS and R_LOF alarms of the home station trigger AU_AIS alarm in the corresponding VC-4 path. (2) The corresponding VC4 path does not receive service it should receive, resulting in AU-AIS alarm on the corresponding path. In this case, TU-AIS alarm will occur on the corresponding TU. At this time, check whether the station where AU-AIS alarm occurs and its interworking station are normal and check whether the timeslot configuration of intermediate station is wrong. (3) Replace the corresponding cross-connect board and line board of the opposite station. (4) Replace the line board and cross-connect board at the home station.
Remarks
2-7
Alarm Handling
AU_LOP
Item
Description
AU_LOP AU Loss of Pointer Major Communication alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE/SV4/SL1/AL1/SPQ4/EGT/EGT2 Alarm indicator flashes twice every other second. (1) Fault in transmitting part of opposite end; (2) Payload configuration of opposite end is wrong; (3) Too much receiving error of this station.
Handling
(1) Check whether service configurations of the opposite station and home station are correct. If not, reconfigure the service. (2) Generally, 155M optical interface board has no such failure. If it has, it is very possible that the 155M optical interface board is not correctly configured. And if 622M optical interface board receive AU-LOP alarm, check the STG board of the opposite station for normal operation and whether the cross-connect board has detected the clock. (3) If it is 140M service, check whether the service is correctly accessed. (4) Replace the corresponding cross-connect board and line board at the opposite station in turn and locate the fault. (5) Replace the line board and the cross-connect board at the home station.
Remarks
2-8
Alarm Handling
B1B_EXC
Item
Description
B1B_EXC B1 error code over threshold per second Minor QoS S16/AL1 Flash once every other second (1) Too much attenuation from the receiving signal; (2) Fault in transmitting part of opposite end; (3) Dirty head of fiber or connector damaged; (4) Fault in receiving part of the station
Handling
(1) The cause may be optical power overload, too much optical attenuation or line board fault of two terminal stations; (2) Clean the optical fiber connector and check whether the receiving/transmitting optical powers of terminal stations are normal; (3) Perform self-loop for two terminal stations respectively. The one with the alarm is the faulty board, replace it.
Remarks
2-9
Alarm Handling
B1_EXC
Item
Description
B1_EXC Regenerator section B1 excessive bit error indication Minor QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4 Alarm indicator flashes once every other second (1) Too much attenuation from the receiving signal; (2) Fault in transmitting part of opposite end; (3) Dirty head of fiber or connector damaged; (4) Fault in receiving part of the station
Handling
(1) Check whether the receiving optical power is normal. If too low, check whether optical cable is intact and the optical fiber connector is clean, and then check whether the launched optical power of the opposite optical board is normal. (2) Loop back the home station, if bit errors disappear, the opposite optical board fails, replace it. If bit errors increase, the home optical board fails, replace it. (3) Check whether the operating temperature is too high. (4) If there is no problem as mentioned above, replace the failed board.
Remarks
Looping back the optical board will negatively influence the service.
2-10
Alarm Handling
B1_SD
Item
Description
B1_SD Regenerator section(B1) signal degraded Minor QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4 Alarm indicator flashes once every other second. (1) Too much attenuation from the receiving signal; (2) Fault in transmitting part of opposite end; (3) Dirty head of fiber or connector damaged; (4) Fault in receiving part of the station
Handling
(1) Clean the optical fiber connector and check the receiving/transmitting optical power of the two terminal stations to determine whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform self-loop for two terminal stations respectively to locate the faulty board and replace it.
Remarks
2-11
Alarm Handling
B2_EXC
Item
Description
B2_EXC Indication of excessive B2 error in the multiplex section Major QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4 Alarm indicator flashes twice every other second. (1) Too much attenuation from the receiving signal; (2) Dirty head of fiber or connector damaged; (3) Fault in transmitting part of opposite end; (4) Fault in receiving part of the station
Handling
(1) If B1 bit errors also appear, clear B1 bit error first. (2) If there are only B2 bit errors, the fault is usually with the optical interface board, replace it; (3) Check if the operating temperature of equipment is too high. (4) If there is no problem as mentioned above, replace the failed board.
Remarks
2-12
Alarm Handling
B2_SD
Item
Description
B2_SD Signal deterioration indication Minor QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4 Alarm indicator flashes once every other second. (1) Too much attenuation from the receiving signal; (2) Dirty head of fiber or connector damaged; (3) Fault in transmitting part of opposite end; (4) Fault in receiving part of the station
Handling
Remarks
2-13
Alarm Handling
B3_EXC
Item
Description
B3_EXC Higher order path (B3) excessive errors Major QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes twice every other second. (1) Too much attenuation from the receiving signal; (2) Dirty head of fiber or connector damaged; (3) Fault in transmitting part of opposite end; (4) Fault in receiving part of the station
Handling
(1) If B1 and B2 bit errors also appear, clear B1 and B2 bit errors first. (2) If there are only B3 bit errors, the fault is usually with the optical interface board, replace it; (3) Check if the operating temperature of equipment is too high. (4) If there is no problem as mentioned above, replace the failed board.
Remarks
2-14
Alarm Handling
B3_SD
Item
Description
B3_SD Higher order path (B3) signal degraded Minor QoS alarm S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes once every other second. (1) Too much attenuation from the receiving signal; (2) Dirty head of fiber or connector damaged; (3) Fault in transmitting part of opposite end; (4) Fault in receiving part of the station
Handling
Remarks
2-15
Alarm Handling
BD_STATUS
Item
Description
BD_STATUS Board not in position alarm Major Equipment alarm PD1/PQ1/PM1/PQM/PL3/PQ3/TDA/BA2/BPA/COA/PMU/S16/SD4/SQ1/SD1/SDE/SL4/SQE /SV4/SL1/AL1/SPQ4/EIPC/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes twice every other second (1) Not install board; (2) Jack of board becomes loose; (3) Fault in mailbox.
Handling
(1) Check whether the board is in position; (2) Swap the faulty board, if the problem remains, replace the board; (3) If the alarm occurs in multiple boards of the same NE, the mailbox of a specific board may be faulty and negatively influence the mailboxes of other boards. Unplug all the boards and then plug them one by one, so as to find the faulty board and replace it.
Remarks
2-16
Alarm Handling
BIP_EXC
Item
Description
BIP_EXC BIP excessive errors Minor QoS alarm PD1/PQ1/PM1/PQM/PL3/PQ3/SPQ4/EMS1/EFS0 Alarm indicator flashes twice every other second (1) Too much BIP2 error.
Handling
(1) Reset or swap the board; (2) Replace the faulty board.
Remarks
2-17
Alarm Handling
BIP_SD
Item
Description
BIP_SD BIP signal degraded Minor QoS alarm PD1/PQ1/PM1/PQM/PL3/PQ3/SPQ4/EMS1/EFS0/EFT Alarm indicator flashes once every other second. (1) Too much BIP2 error.
Handling
Remarks
2-18
Alarm Handling
BUF_ERR
Item
Description
BUF_ERR Board buffer error Minor Processing alarm SDE/SL4/SQE /SL1/AL1/SPQ4 Alarm indicator flashes once every other second. (1) Board failure.
Handling
(1) Reset or swap the board; (2) Replace the faulty board with a new one.
Remarks
2-19
Alarm Handling
BUS_LOC
Item
Description
BUS_LOC Bus dropping loss of clock Major Equipment alarm PD1/PQ1/PM1/PQM/SDE/SL4/SQE /SL1/SPQ4/ET1/ET1S Alarm indicator flashes twice every other second (1) Payload configuration error; (2) STG board failure.
Handling
(1) Check whether service configuration is correct; (2) Check whether the STG board is in the position, whether the running and alarm indicators are normal; (3) Swap the STG board or replace it
Remarks
2-20
Alarm Handling
CC_LOC
Item
Description
CC_LOC Signal is lost in the continuous check Major QoS AL1 Alarm indicator flashes twice every other second Fiber of service broken
Handling
Remarks
2-21
Alarm Handling
CFG_OVFLOW
Item
Description
CFG_OVFLOW Configuration overflow Major Equipment alarm XCS/XCL Alarm indicator flashes twice every other second. (1) The configuration data is beyond the capacity of the cross-connect board
Handling
(1) Adjust timeslot allocation and make the configuration again.
Remarks
2-22
Alarm Handling
COMMUN_FAIL
Item
Description
COMMUN_FAIL Board serial port Communication failure Major Equipment alarm PD1/PQ!/PM1/PL3/PQ3/SPQ4/XCS/XCL/ET1/ET1S/SDE /SQ1/SD1/SL4/SD4/S16/AL1/BPA/BA2/EIPC Alarm indicator flashes twice every other second. (1) Board serial port Communication failure
Handling
(1) If the alarm is reported by a specific board, it means that the 485 Communication port of that board is damaged, replace the faulty board. (2) If the alarms are reported by multiple boards, the chip of a specific board may be damaged, resulting in the voltage of 485 serial port bus increasing. Pull out these boards one by one to check whether the alarm disappears. If yes, it means that some problem exist on the pulled-out board; (3) If the problem remains after the board is replaced, the backplane slot may be damaged. Choose another slot.
Remarks
2-23
Alarm Handling
CONF_DATA_LOS
Item
Description
CONF_DATA_LOS Configuration data loss Minor Processing alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Configuration data in board lost.
Handling
(1) Reset, swap the board, or send the configuration again; (2) Replace the faulty board.
Remarks
2-24
Alarm Handling
COOL_CUR_OVER
Item
Description
COOL_CUR_OVER Cooling current override Major Equipment alarm BPA/BA2/COA Alarm indicator flashes twice every other second. EDFA module failure.
Handling
(1) Replace the faulty board.
Remarks
2-25
Alarm Handling
DBMS_ERROR
Item
Description
DBMS_ERROR Databases error Major Processing alarm SCC Alarm indicator flashes twice every other second. (1) Operation to database error; (2) Data of database damaged; (3) Board failure.
Handling
(1) Replace the faulty board.
Remarks
2-26
Alarm Handling
DBMS_PROTECT_MODE
Item
Description
DBMS_PROTECT_MODE Databases in protection mode Critical Processing alarm SCC Alarm indicator flashes three times every other second. (1) Database in protection mode
Handling
(1) Replace the SCC board of this station.
Remarks
2-27
Alarm Handling
D_LO_J1
Item
Description
D_LO_J1 Drop bus J1 lock lost Major Communication alarm PL3 Alarm indicator flashes twice every other second. (1) The cross-connect board is faulty or not in position.
Handling
(1) Check whether the cross-connect board is in position, and whether the running and alarm indicators are normal; (2) Reset or swap the cross-connect board board; (3) Replace the cross-connect board.
Remarks
2-28
Alarm Handling
DOWN_E1_AIS
Item
Description
DOWN_E1_AIS 2M down signal alarm indication Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) 2M down signal alarm indication
Handling
(1) It may be caused by higher order alarms, remove them. (2) Replace the tributary board. If the alarm is ineffective yet, replace the cross-connect board.
Remarks
2-29
Alarm Handling
E1_LOS
Item
Description
E1_LOS 2M line loss of signal indication Minor Communication alarm PD1/PQ1/PM1/PQM/ET1 Alarm indicator flashes once every other second. (1) Fault in cable of 2M signal; (2) No 2M payload input.
Handling
(1) Loop back the related path at equipment interface part. If the alarm remains, check whether the contact with the electrical interface board is good, or replace the board; (2) If the alarm disappears, then the fault is not with the transmission equipment. Perform loopback on the DDF to check whether there exists problem on the cable. If the alarm disappears, loop back the switch on the DDF to determine whether the fault exists on the switch.
Remarks
2-30
Alarm Handling
ETH_LOS
Item
Description
ETH_LOS Ethernet Receive loss of input signal Critical Communication alarm ET1/ET1S/EMS1/EFS0/EGT/EGT2/EFT Alarm indicator flashes three times every other second. (1) Ethernet Receive loss of input signal.
Handling
Remarks
2-31
Alarm Handling
EXER_FAIL
Item
Description
EXER_FAIL Practice switching failed Major Communication alarm SCC Alarm indicator flashes twice every other second. (1) MSP configuration error; (2) Settings error
Handling
(1) Check whether the current configuration of NE multiplex section protection switching is correct; if not, reconfigure it; (2) Check whether the K byte pass-through and automatic report of the NE are normal and replace the faulty board.
Remarks
2-32
Alarm Handling
EXT_SYNC_LOS
Item
Description
EXT_SYNC_LOS Loss of external synchronous source Critical Equipment alarm XCS/TDA Alarm indicator flashes three times every other second. (1) Signal of External synchronous clock source lost.
Handling
(1) Check whether the input cable of external clock is connected properly; (2) Check whether the equipment which provides external clock is working normally.
Remarks
2-33
Alarm Handling
FAN_FAIL
Item
Description
FAN_FAIL Fan failed Major Equipment alarm SCC/ET1S Alarm indicator flashes twice every other second. (1) Fan not be turned on; (2) Fan out of work
Handling
(1) Check whether the power switch on the fan subrack is turned on. (2) Check whether the cable connection from the fan subrack to main subrack is intact. (3) Check whether the fan operates normally.
Remarks
2-34
Alarm Handling
FI_FAIL
Item
Description
FI_FAIL F interface Communication alarms failed Major Communication alarm SCC Alarm indicator flashes twice every other second. (1) Serial port line doesn't connect well; (2) Board failure.
Handling
(1) Check whether the serial port line in the interface part is normal; (2) Reset or swap the board; (3) Replace the faulty board.
Remarks
2-35
Alarm Handling
FPGA_ABN
Item
Description
FPGA_ABN Writing/Reading wrong Major Equipment alarm S!6/SD4/SL4/SQ1/SD1/SV4/AL1/SDE/SQE /BPA/BA2/COA/PL3/PQ3/PD1/PQ1/ PM1/PQM/SPQ4/ET1/ET1S/TDA/EIPC/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes twice every other second. (1) Wrong FPGA software
Handling
(1) The board is faulty, and replace it.
Remarks
2-36
Alarm Handling
HARD_BAD
Item
Description
HARD_BAD Hardware fails Critical Equipment alarm SCC/S16/SD4/SL4/SQ1/SD1/SV4/AL1/SDE/SQE /BPA/BA2/COA/PL3/PQ3/PD1/ PQ1/PM1/PQM/SPQ4/ET1/ET1S/TDA/EIPC/EFT/EGT/EGT2/EMS1/EFS0 Alarm indicator flashes three times every other second. (1) Hardware failure.
Handling
Remarks
2-37
Alarm Handling
HCS
Item
Description
HCS One bit head error which can be corrected Minor Communication alarm AL1 Flash once every other second Find that it has one bit head error which can be corrected, and several bit errors which can not be corrected
Handling
Remarks
2-38
Alarm Handling
HPAD_CROSSTR
Item
Description
HPAD_CROSSTR Higher order path adaptation performance parameter override alarm Minor QoS alarm PD1/PQ1/PM1/PQM/ET1/ET1S/EGT Alarm indicator flashes once every other second. (1) Loss of clock lock.
Handling
(1) Check whether the clock trace setting of this station is correct; (2) Check whether the clock trace setting of the entire network is correct; (3) Check whether the STG board is normal; if not, reset or swap the STG board. (4) Replace the STG board with a new one.
Remarks
2-39
Alarm Handling
HP_CROSSTR
Item
Description
HP_CROSSTR Higher order path performance parameter override alarm Minor QoS alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE /SPQ4 Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance
Handling
(1) The cause may be optical power overload, too much optical attenuation or line board fault of two terminal stations; (2) Clean the optical fiber connector and check whether the receiving/transmitting optical power of terminal stations are normal; (3) Check whether the clock trace setting of the entire network is correct; (4) Perform self-loop for two terminal stations respectively. The one with alarm happening is the faulty board, please replace it.
Remarks
2-40
Alarm Handling
HP_LOM
Item
Description
HP_LOM Higher order Path Loss of Multiframe Major Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE /PD1/PQ1/PM1/PQM/ET1/ET1S/EFT/EGT2 The alarm indicator flashes twice every other second. (1) Payload configuration error; (2) H4 byte is wrong or lost.
Handling
Remarks
2-41
Alarm Handling
HP_RDI
Item
Description
HP_RDI Higher order path remote defect indication Minor Communication alarm S16/SD4/SL4/SV4/SQ1/SD1/SL1/AL1/SQE/SDE /SPQ4/EGT Alarm indicator flashes once every other second. (1) Opposite end received AU-AIS/AULOP signal; (2) Fault in receiving part of opposite end; (3) Fault in transmitting part of this station.
Handling
(1) When this alarm occurs, check whether the equipment has higher order alarm according to the flow chart of alarm. If it has the alarm, analyze the cause. (2) Check the corresponding path of the line board at the opposite station for AU-AIS and AU-LOP alarms. If it has the alarm, process it. After processing, HP-RDI alarm should disappear. (3) If the opposite station has no alarm or after the corresponding alarm stops, HP-RDL alarm still continues, it can be decided that the board fails, and replace the board.
Remarks
2-42
Alarm Handling
HP_REI
Item
Description
HP_REI Higher order path remote error indication Prompt QoS alarm SD4/SL4/SV4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator does not flash (1) Opposite end received B3 error.
Handling
(1) Check whether the opposite station has B3 bit errors. If yes, and at the same time alarms B1 and B2 occur, it is usually due to excessive line attenuation or optical interface board failure. The localization method is the same as that when R-LOS occurs. (2) If only a few B3 bit errors appear at the remote, generally, it is not caused by optical path failure, while it is often the problem of the equipment itself. It is necessary to check whether the cross-connect board and tributary board on the opposite equipment are normal. (3) Check whether the cross-connect board and tributary board at the home station are normal. (4) Check whether the equipment is well grounded or there is a great interference source near the equipment.
Remarks
2-43
Alarm Handling
HP_R_FIFO
Item
Description
HP_R_FIFO FIFO overflow on the HP receiving side Minor Equipment alarm SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes once every other second. (1) Inferior clock performance of receiving.
Handling
(1) Check whether the STG board is working normally; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform loopback level by level on the line to locate the faulty station, and replace the faulty STG board.
Remarks
2-44
Alarm Handling
HP_SLM
Item
Description
HP_SLM Higher order path signal identification mismatch Minor Communication alarm S16/SD4/SL4/EGT/SQ1/SD1/SL1/AL1/SQE/SDE /SPQ4 Alarm indicator flashes once every other second. (1) The C2 byte that the board should receive is not consistent with the C2 byte that should be sent from the upstream station; (2) Payload configuration error
Handling
(1) Check whether the signal label configuration of corresponding higher order path of the line board in opposite station is the same as that in this station. If not, modify it and re-send it. If the configurations are the same, it can be determined the problem is with the board, replace it.; (2) Check service configurations of both the opposite station and this station. If any error found, modify and re-send the configuration.
Remarks
2-45
Alarm Handling
HP_T_FIFO
Item
Description
HP_T_FIFO FIFO overflow on the HP transmission side Minor Equipment alarm SL1/SQ1/SQE/SDE/AL1 Alarm indicator flashes once every other second. (1) Inferior clock performance of transmitting.
Handling
(1) Check whether the STG board is working normally; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform loopback level by level on the line to locate the faulty station, and then replace the faulty STG board.
Remarks
2-46
Alarm Handling
HP_TIM
Item
Description
HP_TIM Higher order path tracking identification mismatch Minor Communication alarm S16/SD4/SL4/EGT/EGT2/SQ1/SD1/SL1/AL1/SQE/SDE /SPQ4 Alarm indicator flashes once every other second. (1) The tracing byte that the board should receive is not consistent with the tracing byte that should be sent from the upstream station; (2) Payload configuration error.
Handling
(1) Check whether the corresponding higher order path trace byte configuration on the line board of the opposite station is the same as that on the home station. If the configurations are different, modify and re-send them. If the configurations are identical, it can be decided that the board fails. Replace the board. (2) Check the service configurations of the opposite station and home station. If the configurations are wrong, modify and re-send them.
Remarks
2-47
Alarm Handling
HP_UATEVENT
Item
Description
HP_UATEVENT Higher order path unavailable time alarm Minor Communication alarm S16/SD4/SL4/EGT/EGT2/SQ1/SD1/SL1/AL1/SQE/SDE/SPQ4 Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance
Handling
(1) The cause may be optical power overload, too much optical attenuation or line board fault of two terminal stations; (2) Clean the optical fiber connector and check whether the receiving/transmitting optical powers of terminal stations are normal; (3) Check whether the clock trace setting of the entire network is correct; (4) Perform self-loop for two terminal stations respectively. The one with alarm happening is the faulty board, please replace it.
Remarks
2-48
Alarm Handling
HP_UNEQ
Item
Description
HP_UNEQ No loading error in the higher order path Minor Communication alarm S16/SD4/SL4/SV4/SQ1/SD1/SL1/AL1/SQE/SDE/SPQ4/EGT/EGT2 Alarm indicator flashes once every other second. (1) The value of C2 Byte is 0.
Handling
(1) Check whether the C2 byte is correctly configured. If it wrongly configured, modify and re-send the configuration. If it is correctly configured, it can be determined that the board fails. Replace the board.
Remarks
2-49
Alarm Handling
IN_PWR_ABN
Item
Description
IN_PWR_ABN Input power abnormal Major Equipment alarm S16/BPA/BA2/COA Alarm indicator flashes twice every other second. (1) Fiber bended overly; (2) Dirty head of fiber or connector damaged; (3) Fault in the detector or in the amplifying circuit.
Handling
(1) Clean the optical fiber connector and check whether the receiving/transmitting optical powers of terminal stations are normal; (2) Replace the faulty board.
Remarks
2-50
Alarm Handling
IN_PWR_FAIL
Item
Description
IN_PWR_FAIL Input power fail Critical Equipment alarm BPA/BA2/COA Alarm indicator flashes three times every other second. (1) Broken fiber occurs; (2) Fault occurs to the detector or amplifier circuit.
Handling
(1) Fiber broken; (2) Fault in the detector or in the amplifying circuit
Remarks
2-51
Alarm Handling
J0_MM
Item
Description
J0_MM Trace identifier mismatch Minor Communication alarm S16/SD4/SL4/SV4/SQ1/SD1/SL1/AL1/SQE/SDE/SPQ4 Alarm indicator flashes once every other second. (1) J0 byte mismatched.
Handling
(1) From the NMS, check the J0 byte configurations of the two stations to which alarms occurs; if they are inconsistent, reconfigure J0 byte to Huawei SBS; (2) Perform hardware self-loop for the corresponding boards of two stations respectively, and replace the board in which the alarm remains with a new one.
Remarks
2-52
Alarm Handling
K1_K2_M
Item
Description
K1_K2_M K1, K2 mismatch Minor Communication alarm SCC Alarm indicator flashes once every other second. (1) K2 byte received mismatches K1 byte transmitted; (2) Fault in device
Handling
(1) Typically, the cause is that the K1 and K2 path addresses in the downlink signal flow are mismatched. Replace the transmitting optical board of the opposite station; (2) If the problem remains after the above operation, replace the optical board of the home station.
Remarks
2-53
Alarm Handling
K2_M
Item
Description
K2_M K2 mismatch Minor Communication alarm SCC Alarm indicator flashes once every other second. (1) K2 byte received mismatches that transmitted;(2) Fault in device
Handling
(1) Typically, the cause is that the K2 path address in the downlink signal flow is wrong. Replace the opposite transmitting optical board; (2) If the problem remains after the above operation, replace the optical interface board of the home station.
Remarks
2-54
Alarm Handling
LCD
Item
Description
LCD Loss of Cell Delineation Major Communication alarm AL1 Alarm indicator flashes twice every other second (1) Cross-connect board failed or not in position; (2) Board failure; (3) Optical fiber failure.
Handling
(1) Check whether the cross-connect board is in position and whether the running indicator and alarm indicator are normal; (2) Reset or swap the board; (3) Replace the board; (4) Check whether the optical fiber is normal or not.
Remarks
2-55
Alarm Handling
LOCK_CUR_FAIL
Item
Description
LOCK_CUR_FAIL Working current lock failed Critical Equipment alarm BPA/BA2/COA Alarm indicator flashes three times every other second. (1) EDFA module failure; (2) Fault in driving device of exterior bias current
Handling
Remarks
2-56
Alarm Handling
LOOP_ALM
Item
Description
LOOP_ALM Loop alarm Minor Equipment alarm S16/SD4/SQ1/SD1/SL1/AL1/SPQ4/PL3/PQ3/PD1/PQ1/PM1/PQM/ET1/ET1S/EMS1/EFS0/E FT/EGT/EGT2 Alarm board flashes once every other second. (1) Circuitry board occur loop in or loop out.
Handling
(1) Set the line board to non-loopback.
Remarks
2-57
Alarm Handling
LP_AIS
Item
Description
LP_AIS Lower order path alarm indication Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Payload configuration error; (2) Generated by higher order alarm, such as RLOS
Handling
(1) Check and treat the higher order alarms; (2) Check the service configuration. After correcting the mistake, re-send the configuration.
Remarks
2-58
Alarm Handling
LP_CROSSTR
Item
Description
LP_CROSSTR Lower order path performance parameter override alarm Minor QoS alarm PD1/PQ1/PL3/PQ3/PM1/PQM/ET1/ET1S/EFT Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance.
Handling
Remarks
2-59
Alarm Handling
LP_RDI
Item
Description
LP_RDI Lower order path remote defect indication Minor Communication alarm PD1/PQ1/PM1/PQM/PL3/PQ3/ET1/ET1S/EMS1/EFS0/EGT/EGT2/EFT Alarm indicator flashes once every other second. (1) Opposite end received TU_AIS/TU_LOP signal; (2) Fault in receiving part of opposite end; (3) Fault in transmitting part of this station
Handling
(1) Check if the corresponding path of the tributary board of the opposite station has TU-AIS and TU-LOP alarms. If it has the alarms, process them. After the processing, LP-RDL alarm should disappear. (2) If the opposite station has no alarm or LP-RDL alarm still exists after other alarms disappear, it shows that the board fails. Replace the faulty board.
Remarks
2-60
Alarm Handling
LP_REI
Item
Description
LP_REI Lower order path remote error indication Minor QoS alarm PD1/PQ1/PM1/PQM/PL3/PQ3/ET1/ET1S/EMS1/EFS0/EFT Alarm indicator flashes once every other second. (1) Opposite end received BIP2 error
Handling
(1) Check and treat the alarms of the opposite station;
Remarks
2-61
Alarm Handling
LP_RFI
Item
Description
LP_RFI Lower order path remote fault indication Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/EMS1 Alarm indicator flashes once every other second. (1) LP receiving part out of work of opposite end.
Handling
(1) Check and treat the alarms of the opposite station; (2) Typically there also exists some problem on the transmitting signal of the tributary board of the home station that reports alarms. Replace the tributary board.
Remarks
2-62
Alarm Handling
LP_R_FIFO
Item
Description
LP_R_FIFO FIFO overflow on the receiving side of the lower order path Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Payload configuration error.
Handling
(1) Check the service configuration. After correcting the mistake, re-send the configuration.
Remarks
2-63
Alarm Handling
LP_SIZE_ERR
Item
Description
LP_SIZE_ERR Lower order path V5 identification mismatch Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Configuration of MAP is wrong.
Handling
(1) Check and treat the alarms of the opposite tributary board; (2) Replace the tributary board of the home station. (3) Replace the tributary board of the opposite station.
Remarks
2-64
Alarm Handling
LP_SLM
Item
Description
LP_SLM Lower order path signal identification mismatch Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/EMS1/EFS0/EFT/EGT/EGT2 Alarm board flashes once every other second (1) The signal identifier that the board should receive is not consistent with the signal identifier that should be sent from the upstream station; (2) Payload configuration error.
Handling
(1) Check whether the signal label byte configuration of the corresponding lower order path on the tributary board of the opposite station is the same as that of the home station. If the configurations are different, modify and re-send them. If the configurations are identical, it can be decided that the board fails. Replace the board. (2) Check the service configurations of the opposite station and home station. If the configurations are wrong, modify and re-send them.
Remarks
2-65
Alarm Handling
LP_T_FIFO
Item
Description
LP_T_FIFO FIFO overflow on the transmission side of the lower order path Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Frequency deviation of PDH input signal is too much.
Handling
(1) Check whether the input PDH signal frequency deviation falls into the frequency deviation range required for the equipment.
Remarks
2-66
Alarm Handling
LP_TIM
Item
Description
LP_TIM Lower order path tracking identification mismatch Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes once every other second. (1) The LP tracing identifier that the board should receive is not consistent with the tracing identifier that should be sent from the upstream station; (2) Payload configuration error.
Handling
(1) Check whether the corresponding lower order path trace byte configuration of the tributary board of the opposite station is the same as that of the home station. If the configurations are different, modify and re-send them. If the configurations are identical, it can be decided that the board fails. Replace the board. (2) Check the service configurations of the opposite station and home station. If the configurations are wrong, modify and re-send them.
Remarks
2-67
Alarm Handling
LP_UATEVENT
Item
Description
LP_UATEVENT Lower order path unavailable time alarm Minor Communication alarm PD1/PQ1/PM1/PQM/PL3/PQ3/ET1/ET1S Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance.
Handling
(1) Clean the optical fiber connector and check the receiving/transmitting optical power of the two terminal stations to determine whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform self-loop for two terminal stations respectively to locate the faulty board and replace it to solve the problem.
Remarks
2-68
Alarm Handling
LP_UNEQ
Item
Description
LP_UNEQ No payload indication of the lower order path Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/EMS1/EFS0/EFT/EGT/EGT2 Alarm indicator flashes once every other second. (1) No 2M net payload. Please check 2M cable.
Handling
(1) Check the service configurations of the opposite station and home station. If the configurations are wrong, modify and re-send them. (2) Check whether the attribute configurations of the tributary boards of both stations are correct.
Remarks
2-69
Alarm Handling
LSR_WILL_DIE
Item
Description
LSR_WILL_DIE Laser will be out of work Critical System alarm S16 Alarm indicator flashes three times every other second (1) Aging of Laser.
Handling
Remarks
2-70
Alarm Handling
LTI
Item
Description
LTI Loss of synchronous source Major Equipment alarm XCS/TDA Alarm indicator flashes twice every other second. In non-S1 byte mode: (1) Optical fiber is broken (if tracing line clock source). (2) External source clock stops inputting (if tracing external clock source). (3) The synchronous source is configured as unrecoverable. (4) The synchronous clock source traced is blocked. (5) The synchronous clock source is wrongly configured. In S1 byte mode: (1) Broken fiber occurs; (2) Enter the free-run mode. (3) The synchronous source is incorrectly configured.
Handling
(1) Check whether the synchronous clock source is configured to trace nonexistent clock source. If the configuration is incorrect, modify and re-send it. (2) If the configuration is correct, check whether the traced synchronous source is normal. If not, eliminate the corresponding failure to make it normal. If it is configured as tracing line clock and there is signal loss alarm on the line, eliminate the signal loss alarm first. If tracing external clock, check whether the external clock is normal and whether the external clock line is in good contact. (3) If the traced synchronous source is normal, it can be decided that the board fails. Replace the board.
Remarks
2-71
Alarm Handling
MAIL_ERR
Item
Description
MAIL_ERR Mail Communication alarm error Major Communication alarm SCC Alarm indicator flashes twice every other second. (1) Mailbox failure.
Handling
(1) Swap the board (2) Replace the faulty board.
Remarks
2-72
Alarm Handling
MEM_ERR
Item
Description
MEM_ERR Memory error Major Equipment alarm SCC Alarm indicator flashes twice every other second. (1) Board failure.
Handling
Remarks
2-73
Alarm Handling
MSAD_CROSSTR
Item
Description
MSAD_CROSSTR Multiplex section adapting performance parameter override alarm Minor QoS alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/EGT Alarm indicator flashes once every other second. (1) Loop clock out of frame.
Handling
Remarks
2-74
Alarm Handling
MS_AIS
Item
Description
MS_AIS Multiplex section alarm indication signal Major Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/EGT Alarm indicator flashes twice every other second. (1) Received MS-AIS signal of opposite end; (2) No clock or signal (internal) of opposite end; (3) Fault in receiving part of this station.
Handling
(1) Check whether the line board of the opposite station fails. Reset or replace the board to check whether the alarm disappears. (2) Check the line board of the home station. Reset or replace the board to check whether the alarm disappears.
Remarks
2-75
Alarm Handling
MS_CROSSTR
Item
Description
MS_CROSSTR Multiplex section performance parameter override alarm Minor QoS alarm S16/SD4/SL4/SQ1/SD1/SL1/SP8/AL1/SDE/EGT Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance.
Handling
Remarks
2-76
Alarm Handling
MSP_INFO_LOSS
Item
Description
MSP_INFO_LOSS Multiplex section node parameter loss Critical Processing alarm SCC Alarm indicator flashes three times every other second. (1) Information of MS node parameters lost.
Handling
(1) Check whether the node parameter of multiplex section is normal; if not, modify and re-send it. (2) If the phenomena occurs frequently, re-send the main control software or replace the SCC board.
Remarks
2-77
Alarm Handling
MS_RDI
Item
Description
MS_RDI Multiplex section remote defect indication Minor Communication alarm S16/SD4/SL4/SV4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes once every other second. (1) Opposite end received LOS/LOF/MS-AIS signal; (2) Fault in receiving part of opposite end; (3) Fault in transmitting part of this station.
Handling
(1) Check whether there are R-LOS, R-LOF and MS-AIS alarms on the line board of the opposite station. If there are, remove them. Then the MS-RDI alarm at the home station should disappear. (2) If there is no alarm or MS-RDI alarm still exists after the corresponding alarms disappear, it can be decided that the board is failed. Replace it. (3) Fiber cut seldom happens, because this alarm can only occur when the transmitting fiber is broken, while the receiving fiber of the home station is intact. If the transmitting/receiving fibers are all broken, MS-RDI alarm can not be returned to the home station. The key is to check the fiber connection at the home station and opposite station (ODF side, optical interface board side).
Remarks
2-78
Alarm Handling
MS_REI
Item
Description
MS_REI Multiplex section remote error indication Prompt QoS alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator does not flash. (1) Opposite end received B2 error.
Handling
(1) Self-loop the corresponding optical interface board of the home station and check whether the bit errors in MS-REI performance event at the home station is still increasing. Then use this as a basis to decide the problem lies with the transmitting part of the home terminal or the receiving part of the opposite station. (2) If the bit errors do not increase, it shows that the receiving part of the opposite board fails. Replace the board. (3) If the bit errors keep on increasing, it shows that the transmitting part of the board at the home station fails. Replace the board.
Remarks
When the service has been loaded, self-loop of optical path is prohibited.
2-79
Alarm Handling
M_S_SW
Item
Description
M_S_SW Relationship of active and standby switching Critical Equipment alarm XCS/XCL Alarm indicator flashes three times every other second. (1) Board dropped off; (2) Board state changed
Handling
(1) Check whether the active board is in position and running normally; (2) Reset or swap the active board; (3) Replace the active board with a new one.
Remarks
2-80
Alarm Handling
MS_UATEVENT
Item
Description
MS_UATEVENT Multiplex section unavailable time alarm Minor Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance.
Handling
(1) Clean the optical connector and check the receiving/transmitting optical power of the two terminal stations to determine whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform self-loop for two terminal stations respectively to locate the faulty board and replace it to solve the problem.
Remarks
2-81
Alarm Handling
NE_SF_LOST
Item
Description
NE_SF_LOST It lacks a set of NE software Major Equipment alarm SCC Alarm indicator flashes twice every other second. It lacks a set of NE software.
Handling
(1) Load the NE software.
Remarks
2-82
Alarm Handling
NESTATE_INSTALL
Item
Description
NESTATE_INSTALL NE state install Critical Processing alarm SCC Alarm indicator flashes three times every other second. (1) NE is in installation state.
Handling
(1) Check the configuration data. After modification, re-send the configuration.
Remarks
2-83
Alarm Handling
NO_BD_SOFT
Item
Description
NO_BD_SOFT No board software Critical Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE/PQ3/PD1/PQ1/PQM/ET1/ET1S /SCC/XCS/XCL/BPA/BA2/SP8/EGT/PMCU/EC4 Alarm indicator flashes three times every other second. (1) No Board software loaded.
Handling
(1) Re-load the board software to the board. (2) Replace the faulty board.
Remarks
2-84
Alarm Handling
OCD
Item
Description
OCD Out of Cell Delineation Major Communication alarm AL1 Alarm indicator flashes twice every other second (1) Cross-connect board failed or not in position; (2) Board failure.
Handling
(1) Check whether the XCS board is in position and whether the running indicator and alarm indicator are normal; (2) Check whether the board is normal; (3) Replace the XCS board.
Remarks
2-85
Alarm Handling
OTH_BD_STATUS
Item
Description
OTH_BD_STATUS Another board pulled out or plugged in (state variation) Prompt Equipment alarm SL4/SD4/SL1/SD1/SQ1/AL1/SQE/SDE Alarm indicator does not flash (1) The status of another board has changed.
Handling
(1) Check whether the opposite board is working normally; if not, check the alarm and treat it; (2) Reset or swap the board; (3) Replace this board.
Remarks
2-86
Alarm Handling
OUT_PWR_ABN
Item
Description
OUT_PWR_ABN Output power abnormal Critical Equipment alarm S16/BA2/BPA/COA Alarm indicator flashes three times every other second. (1) Aging of EDFA module; (2) Fault in measuring circuit or in amplifying circuit; (3) Fault in input optical loop.
Handling
Remarks
2-87
Alarm Handling
OUT_PWR_UNDULATE
Item
Description
OUT_PWR_UNDULATE Output power jittering Minor Equipment alarm S16/BPA/BA2 Alarm indicator flashes once every other second. (1) Aging of EDFA module; (2) Fault in measuring circuit or in amplifying circuit; (3) No optical input
Handling
Remarks
2-88
Alarm Handling
POWER_FAIL
Item
Description
POWER_FAIL Power failure Major Equipment alarm SCC/PMU Alarm indicator flashes twice every other second. (1) Switch of power board is not on; (2) Power board out of work; (3) XCS board damaged or not in the proper position; (4) The battery is damaged or the output power of battery is too low
Handling
(1) Check whether the power switch of the power board is turned on. If not, turn it on. (2) Check whether the STG board is in position and if it is running normally. (3) Check whether the output of power board is normal. If not, replace the failed board.
Remarks
2-89
Alarm Handling
PS
Item
Description
PS Protection switching happened indication Major Equipment alarm XCS/XCL/PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/SPQ4/EIPC Alarm indicator flashes twice every other second. (1) Protection switching occurs; (2) Board parameters are set incorrectly.
Handling
PS alarm on the tributary board (1) In path protection ring, when PS alarm occurs on the tributary board, check whether there are alarms such as R-LOS, R-LOF, and excessive bit errors which initiate protection switching. If there are such alarms, treat them first. (2) In chain network or multiplex section protection ring, when there is PS alarm on the tributary board, check whether the tributary board is configured as non-protection correctly. PS alarm on the cross-connect board (1) In multiplex section protection ring, when PS alarm appears on the cross-connect board, check whether there are alarms such as R-LOS, R-LOF, excessive bit errors which generate protection switching. If there are such alarms, remove them first. (2) If the service is interrupted due to switching, restart after the multiplex section protection protocol of the whole network has stopped. (3) If there is no alarm which results in switching, check whether protection switching protocol of each NE is correct and whether it is correctly started.
Remarks
2-90
Alarm Handling
PWR_MAJ_ALM
Item
Description
PWR_MAJ_ALM Serious under/over voltage Critical Environment alarm PMU Alarm indicator flashes three times every other second. (1) Input voltage abnormal.
Handling
(1) Check whether the input voltage of the power supply where the alarm occurs is normal; (2) Check whether the wiring between connection post and the power supply box is normal.
Remarks
2-91
Alarm Handling
PWR_MIN_ALM
Item
Description
PWR_MIN_ALM Common under/over -voltage Minor Environment alarm PMU Alarm indicator flashes once every other second. (1) Input voltage abnormal.
Handling
(1) Check the input voltage of the power supply where the alarm occurs is normal; (2) Check whether the wiring between the connection post and the power supply box is normal.
Remarks
2-92
Alarm Handling
P_LOS
Item
Description
P_LOS PDH interface - loss of signal Major System alarm PQ3 Flash twice every other second (1) Transmission failure of PDH equipment connected to this station; (2) The output port of PDH equipment connected to this station broken off or loose; (3) The PDH signal input port of this station broken off or loose; (4) Board failure; (5) Cable failure.
Handling
Method of performing self-loop section by section can be used to narrow down the alarm section and find out the faulty point: (1) Confirm the slot and path number where the alarm occurs; (2) Self-loop the path with alarm on the PDH interface board. If the alarm still exists, check whether the interface is in good contact. If the contact is perfect, replace the tributary board; (3) If the alarm disappears after the self-loop is performed, it can be determined that the transmission equipment is all right. Then, perform self-loop at the DDF to the cable between DDF and transmission equipment. If the alarm remains, certainly it indicates that the problem is with the cable between the DDF connector and the interface board; (4) If the alarm disappears after the above self-loop on DDF is performed, perform self-loop on the DDF to the switch equipment to see whether the problem is with the part between the DDF and switch or with the switch itself.
Remarks
2-93
Alarm Handling
RAM_ERR
Item
Description
RAM_ERR Internal memory reading and writing error Major Equipment alarm PD1/PQ1/PM1/PQM/PD4/ET1/ET1S Alarm indicator flashes twice every other second. (1) Board failure.
Handling
Remarks
2-94
Alarm Handling
RAM_LOC
Item
Description
RAM_LOC Overhead processing -RAM loss of clock Major Equipment alarm PL3/PQ3/SQE/SDE/SL1/AL1/SPQ4 Alarm indicator flashes twice every other second. (1) Board failure.
Handling
Remarks
2-95
Alarm Handling
RELAY_ALARM
Item
Description
RELAY_ALARM Relay alarm Critical Environment alarm PMU Alarm indicator flashes three times every other second (1) Change in relay status
Handling
(1) Check whether state of the alarm access equipment has changed.
Remarks
2-96
Alarm Handling
RR_LOC
Item
Description
RR_LOC Line receive loss of clock Major System alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes twice every other second (1) XCS board of opposite end damaged or not in proper position
Handling
(1) Check whether the XCS board and STG board of the opposite station are in position and work properly; (2) Reset or swap the XCS board and STG board of the opposite station; (3) Replace the XCS board and STG board of the opposite station.
Remarks
2-97
Alarm Handling
RS_CROSSTR
Item
Description
RS_CROSSTR Regenerator section performance parameter override alarm Minor QoS S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/EGT Flash once every other second (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance
Handling
(1) Clean the optical fiber connector and check transmitted/received optical power of the two terminal stations to see whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Loop back the two terminal stations respectively to determine board of which side is faulty. Replace the faulty board.
Remarks
2-98
Alarm Handling
RS_UATEVENT
Item
Description
RS_UATEVENT Regenerator section unavailable time event Minor Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Flash once every other second (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance
Handling
(1) Clean the optical fiber connector and check transmitted/received optical power of the two terminal stations to see whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Loop back the two terminal stations respectively to determine board of which side is faulty. Replace the faulty board.
Remarks
2-99
Alarm Handling
R_APS
Item
Description
R_APS K1, K2 bytes receiving failed Minor Communication alarm SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes once every other second. (1) Inferior laser performance in the upstream station; (2) Too low or too high receiving optical power in this station; (3) Inferior clock performance at opposite end; (4) Inferior fiber performance.
Handling
(1) Clean the optical fiber connector and check the receiving/transmitting optical power of the two terminal stations to determine whether there exists broken fiber or the attenuation of optical path is too much; (2) Check whether the clock trace setting of the entire network is correct; (3) Perform self-loop for two terminal stations respectively to locate the faulty board and replace it to solve the problem.
Remarks
2-100
Alarm Handling
R_FIFO_E
Item
Description
R_FIFO_E Receiving FIFO overflow Minor Equipment alarm S16/SPQ4/PQ3 Alarm indicator flashes once every other second. (1) Caused by high order alarm; (2) Board failure.
Handling
(1) Check and treat the higher order alarm; (2) Reset or swap the board; (3) Replace the faulty board.
Remarks
2-101
Alarm Handling
R_LOF
Item
Description
R_LOF Receive loss of frame Critical Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes three times every other second (1) Too much attenuation from the receiving signal; (2) Transmitting signal of opposite end has no frame; (3) Fault in devices of the receiving direction
Handling
(1) If there is R-LOS, generally, it is due to broken fiber, too much fiber attenuation, board failure etc. (2) Check whether the fiber is intact. (3) Check whether the connector of the fiber is in good contact and clean the connector of the fiber. (4) If the board is faulty, replace it.
Remarks
2-102
Alarm Handling
R_LOS
Item
Description
R_LOS Receive loss of signal Critical Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes three times every other second (1) Fiber broken; (2) Too much attenuation on the line; (3) Opposite end laser damaged, line transmission failed; (4) XCS board of the opposite end damaged or not in the proper position.
Handling
(1) Generally, it is due to broken fiber, too much fiber attenuation, board failure, etc. (2) Check whether the optical cable is intact and the optical connector is in good contact. Clean the optical cable connector. (3) If the receiving optical power is overloaded, add an attenuator. (4) If the board is faulty, replace it.
Remarks
2-103
Alarm Handling
R_OOF
Item
Description
R_OOF Receive out of frame Critical Communication alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes three times every other second (1) Too much attenuation from the receiving signal; (2) Excessive bit error in transmission process; (3) Fault in the transmission direction of the opposite end; (4) Fault in devices of the receiving direction
Handling
(1) Generally, it is due to broken fiber, too much fiber attenuation, board failure, etc. (2) Check whether the optical cable is intact and the optical connector is in good contact. Clean the optical cable connector. (3) If the receiving optical power is overloaded, add an attenuator. (4) If the board is faulty, replace it.
Remarks
2-104
Alarm Handling
S1_SYN_CHANGE
Item
Description
S1_SYN_CHANGE Clock reference Source Change In S1_Mode Major Equipment alarm XCS Alarm indicator flashes twice every other second. (1) Fiber broken; (2) External bits broken; (3) Upriver station occur this alarm
Handling
(1) It means that the clock source protection switching occurs to this network. Check the status of the entire network clock switching; (2) Check whether the alarm caused by the above reasons occurs to the entire network; (3) The alarm is generally unrelated to this station.
Remarks
2-105
Alarm Handling
SECU_ALM
Item
Description
SECU_ALM Security alarm Major Security alarm SCC Locking screen (1) Input wrong password more than three times during login.
Handling
(1) Ask the administrator for the correct password and use the correct password to unlock the login.
Remarks
2-106
Alarm Handling
SL4_ALM
Item
Description
SL4_ALM Other alarms of 622M optical interface line unit Minor Equipment alarm SL4/SD4 Alarm indicator flashes once every other second. (1) Board failure.
Handling
Remarks
2-107
Alarm Handling
STM_ERR
Item
Description
STM_ERR STM type error Minor Processing alarm S16/SD4/SL4/SQ1/SD1/SL1/SQE/SDE Alarm indicator flashes once every other second. (1) Register setting error.
Handling
Remarks
2-108
Alarm Handling
SUBCARD_ABN
Item
Description
SUBCARD_ABN Find the fault of sub-card Major Communication alarm AL1/ET1/PQ3 Alarm indicator flashes twice every other second. (1) Detect the sub-card status error.
Handling
(1) Check whether cross-connect board is in position and whether running indicator and alarm indicator are normal; (2) Reset or swap the cross-connect board; (3) Replace the faulty board.
Remarks
2-109
Alarm Handling
SYN_BAD
Item
Description
SYN_BAD Synchronous source degraded Minor Equipment alarm XCS Alarm indicator flashes once every other second. (1) Synchronous source deteriorated.
Handling
(1) Check and process the bit errors and pointer justification performance events occurring in the direction of clock source traced. (2) When setting clock trace, do not form clock tracing loop.
Remarks
2-110
Alarm Handling
SYNC_C_LOS
Item
Description
SYNC_C_LOS Synchronous source level loss Major Equipment alarm XCS/TDA Alarm indicator flashes twice every other second. In non-S1 byte mode: High level clock source is unavailable: (1) Optical fiber is broken (if tracing line clock source). (2) External source clock stops inputting (if tracing external clock source) In S1 byte mode: (1) S1 byte switching occurs at the home station. (2) External clock (BITS) input has changed.
Handling
(1) Reset the priority level of clock source. (2) If tracing line clock source, check whether there is R-LOS alarm and treat it. (3) If tracing tributary clock source, check whether there is T-ALOS alarm and treat it. (4) If tracing external clock, check whether the external clock source operates normally.
Remarks
2-111
Alarm Handling
TAIP_LOC
Item
Description
TAIP_LOC Alarm serial port transmitting clock loss Minor Equipment alarm SQE/SDE/SL1/SQ1/AL1 Alarm indicator flashes once every other second. (1) Board failure.
Handling
Remarks
2-112
Alarm Handling
T_ALOS
Item
Description
T_ALOS 2M interface loss of analog signal Major Communication alarm PD1/PQ1/PM1/PQM/TDA Alarm indicator flashes twice every other second. (1) No 2M Payload Input; (2) 2M Interface of DDF broken off or loose; (3) 2M interface of this station broken off or loose; (4) Board failure; (5) Cable failure.
Handling
Gradually pinpoint the alarm area on the link-by-link self-loop basis to locate the alarm point. (1) Confirm the board position and path number where the alarm is generated via the NMS. (2) Self-loop the path on 2M interface board. If the alarm still does not disappear after self-loop, check whether the interface board is in good contact. If the contact is good, replace 2M tributary board. (3) If the alarm disappears after performing self-loop on the interface board, it can be determined that the transmission equipment does not fail. On the DDF, loop back the transmission equipment and confirm whether the problem is with the cable between the DDF and transmission equipment. If the alarm does not disappear after self-loop, surely the connector of the DDF and the connection cable between the DDF and interface board have problems. (4) If the alarm disappears after performing self-loop at the DDF, loop back the exchange equipment on the DDF and determine whether the problem exists between the DDF and the exchange or the problem lies with the exchange itself.
Remarks
2-113
Alarm Handling
T_DLOS
Item
Description
T_DLOS 2M interface loss of digital signal Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1 Alarm indicator flashes once every other second. (1) No 2M Payload Input; (2) 2M Interface of DDF broken off or loose; (3) 2M interface of this station broken off or loose; (4) Board failure; (5) Cable failure.
Handling
Gradually pinpoint the alarm area on the link-by-link self-loop basis to locate the alarm point. (1) Confirm the board position and path number where the alarm occurs via the NMS. (2) On the 2M interface board, loop back all alarm paths to locate the fault. (3) Replace the failed board and 2M cable. (4) If it is the problem of the exchange, turn to the engineer for exchange maintenance.
Remarks
2-114
Alarm Handling
TEMP_ALARM
Item
Description
TEMP_ALARM Temperature override Minor Environment alarm PMU/ET1/ET1S/EGT Alarm indicator flashes once every other second. (1) Environment temperature over threshold.
Handling
(1) The environment temperature value exceeds the specified range. Please clean the fan in time and pay attention to the maintenance for the equipment room environment.
Remarks
2-115
Alarm Handling
TEMP_OVER
Item
Description
TEMP_OVER Optical module working temperature override Major Equipment alarm XCS/XCL/BPA/BA2/COA/EMS1/EFS0/EFT/EGT2 Alarm indicator flashes twice every other second. (1) Too high environment temperature; (2) Fault in cooling device; (3) Board failure
Handling
(1) Clean the fan in time and pay attention to the maintenance for the equipment room environment; (2) Reset the board. (3) Replace the board.
Remarks
2-116
Alarm Handling
TEM_HA
Item
Description
TEM_HA Laser temperature is too high Major System alarm S16 Alarm indicator flashes twice every other second (1) Too high working temperature; (2) Fault in Laser.
Handling
(1) Check whether the board temperature is too high. If it is, clean the fan. (2) If the alarm still exists after the fan cleaning, replace the optical board.
Remarks
2-117
Alarm Handling
TF
Item
Description
TF Laser failure Critical Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1 Alarm indicator flashes three times every other second. (1) Fault in laser of this board.
Handling
Remarks
2-118
Alarm Handling
T_FIFO_E
Item
Description
T_FIFO_E Transmission FIFO overflow Minor System alarm S16/PL3/PQ3/SPQ4 Flash once every other second (1) Input signal isn't right PDH signal; (2) Board failure.
Handling
(1) Check whether the input signal is normal; (2) Reset or swap the board; (3) Replace the faulty board.
Remarks
2-119
Alarm Handling
T_LOC
Item
Description
T_LOC Transmit loss of clock Major Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes twice every other second. (1) XCS board damaged or not in the proper position.
Handling
(1) Check whether the XCS board are in position and working normally; (2) Reset or swap theXCS board; (3) Replace the XCS board.
Remarks
2-120
Alarm Handling
T_LOS
Item
Description
T_LOS Transmit loss of signal Major Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/EMS1/EFS0 Alarm indicator flashes twice every other second. (1) Payload configuration error.
Handling
(1) Check the service configuration for correctness. After modification, re-send it; (2) Reset or swap the board; (3) Replace the faulty board.
Remarks
2-121
Alarm Handling
T_LOTC
Item
Description
T_LOTC 2M interface loss of transmit clock Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Board failure.
Handling
Remarks
2-122
Alarm Handling
T_LOXC
Item
Description
T_LOXC 2M interface loss of external clock Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Board failure.
Handling
Remarks
2-123
Alarm Handling
TR_LOC
Item
Description
TR_LOC Line transmit loss of clock Major Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE Alarm indicator flashes twice every other second. (1) XCS board damaged or not in proper position.
Handling
(1) Check whether the cross-connect board and STG board are in position and working normally; (2) Reset or swap the cross-connect board and STG board; (3) Replace the cross-connect board and STG board.
Remarks
2-124
Alarm Handling
T_TDM
Item
Description
T_TDM Faulty transmission driving equipment Minor Equipment alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) Board failure.
Handling
Remarks
2-125
Alarm Handling
TU_AIS
Item
Description
TU_AIS TU alarm indication Major Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/EMS1/EFS0/EGT/EGT2/EFT Alarm indicator flashes twice every other second. (1) Payload configuration error; (2) opposite path invalidation; (3) Generated by higher order alarm, such as R_LOS ; (4) Fault in cross-connect board.
Handling
(1) Check whether there is higher order alarm such as R-LOS. If there are such alarms, eliminate them. (2) Check whether service configuration is correct. (3) If it is caused by failures of cross-connect board and tributary board, replace the failed board.
Remarks
2-126
Alarm Handling
TU_LOP
Item
Alarm name Full name Alarm level Alarm level Alarm type Alarm board Alarm indication Causes
Description
TU_LOP TU loss of pointer TU loss of pointer Major Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S/PL3/PQ3/EMS1/EFS0/EGT/EGT2/EFT Alarm indicator flashes twice every other second. (1) Fault in the interface between the tributary and the cross-connect board; (2) Payload configuration error.
Handling
(1) Check whether the configurations of cross-connect board and tributary board are correct. If not, modify and re-download them. (2) Check whether there are bent pins on the backplane at both terminal stations by means of self-loop method. Replace the board positions of the corresponding tributary board and cross-connect board in sequence.
Remarks
2-127
Alarm Handling
UHCS
Item
Description
UHCS Uncorrected HCS Minor Communication alarm AL1 Flash once every other second Find the cell head errors which can not be corrected
Handling
Remarks
2-128
Alarm Handling
UP_E1_AIS
Item
Description
UP_E1_AIS 2M up signal alarm indication Minor Communication alarm PD1/PQ1/PM1/PQM/ET1/ET1S Alarm indicator flashes once every other second. (1) AIS alarm indication.
Handling
(1) It may be caused by higher order alarms, so remove higher order alarms first. (2) Tributary board fails. Replace it. (3) If this method does not work, replace the cross-connect board.
Remarks
2-129
Alarm Handling
VC_AIS
Item
Description
VC_AIS Virtual channel alarm signal indication Major Communication alarm AL1 Flash twice every other second The system receives the alarms of LOS, LOF and LCD etc.
Handling
Remarks
2-130
Alarm Handling
VC_RDI
Item
Description
VC_RDI Virtual channel remote fault indication Major Communication alarm AL1 Alarm indicator flashes twice every other second Insert RDI after receiving AIS
Handling
Remarks
2-131
Alarm Handling
VER_MISMATCH
Item
Description
VER_MISMATCH Board software version mismatch Major Processing alarm SCC Alarm indicator flashes twice every other second. (1) Board software mismatches NE software.
Handling
(1) Collect the version information of the board software and NE software and compare them with the version matching table to check whether they are matched; if not, ask to change one of them; (2) If the version matching is right, the alarm may be mis-reported by the board. Reset or swap the board to solve the problem.
Remarks
2-132
Alarm Handling
VP_AIS
Item
Description
VP_AIS Virtual channel alarm signal indication Major Communication alarm AL1 Flash twice every other second The system receives the alarms of LOS, LOF and LCD etc.
Handling
Remarks
2-133
Alarm Handling
VP_RDI
Item
Description
VP_RDI Virtual channel remote fault indication Major Communication alarm AL1 Alarm indicator flashes twice every other second Insert RDI after receiving AIS
Handling
Remarks
2-134
Alarm Handling
WORK_CUR_OVER
Item
Description
WORK_CUR_OVER Working current override Major Equipment alarm BPA/BA2/COA Alarm indicator flashes twice every other second. (1) Aging of EDFA module.
Handling
Remarks
2-135
Alarm Handling
W_R_FAILURE
Item
Description
W_R_FAILURE Reading or writing single chip register failed Major Equipment alarm S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE /SPQ4/PL3/PQ3/PD1/PQ1/PM1/PQM/ ET1/ET1S/EMS1/EFS0/EFT/EGT/EGT2/TDA/BPA/BA2/COA/XCS/XCL/SCC Alarm indicator flashes twice every other second. (1) The board is faulty; (2) Fault occurs to the STG board.
Handling
(1) Replace the corresponding board; (2) Replace the STG board of the home NE.
Remarks
2-136
Alarm Handling
WRG_BD_TYPE
Item
Description
WRG_BD_TYPE Wrong inserted board type Major Equipment alarm SCC Alarm indicator flashes twice every other second. (1) The incorrect board is plugged in; (2) The board configuration is incorrect.
Handling
(1) Check whether the configured board type is consistent with the actual one; (2) Check whether the type of the board software is matched with the hardware.
Remarks
2-137
3 Performance Event Handling
3.1 Performance Events of SDH
Service
The performance events of the SDH service can be classified into three types: pointer justification, bit error and equipment function.
Table 3-1 List of pointer justification performance events
Abbreviation
AUPJCHIGH AUPJCLOW TUNPJC TUPPJC
Detailed information
AU positive pointer justification count AU negative pointer justification count TU negative pointer justification count TU positive pointer justification count
Board supported
S16/SD4/SL4/SQ1/SD1/ SL1/ SDE/ SP8
PD1/PQ1/ PQM/ PQ3/ET1
3-1
Table 3-2 List of bit error performance events of regeneration section
Abbreviation
RSBBE RSCSES RSES RSOFS RSOOF RSSES RSUAS
Regeneration section background block error Regeneration section consecutive severely errored second Regeneration section errored second Regeneration section out-of-frame second Regeneration section out-of-frame count Regeneration section severely errored second Regeneration section unavailable second
Board supported
S16/SD4/SL4/ SQ1/SD1/SL1/AL1/S DE/ SP8
Table 3-3 List of bit error performance events of multiplex section
Abbreviation
MSBBE MSCSES MSES MSFEBBE MSFECSES MSFEES MSFESES MSSES MSUAS
Multiplex section background block error Multiplex section consecutive severely errored second Multiplex section errored second Multiplex section far-end background block error Multiplex section consecutive severely errored second Multiplex section far-end errored second Multiplex section far-end severely errored second Multiplex section severely errored second Multiplex section unavailable second
Board supported
S16/SD4/SL4/ SQ1/SD1/SL1/AL1/ SDE/ /SP8
3-2
Table 3-4 List of bit error performance events of higher order path
Abbreviation
HPBBE HPCSES HPES HPFEBBE HPFEES HPFESES HPSES HPUAS
Higher order path background block error Higher order path consecutive severely errored second Higher order path errored second Higher order path far-end background block error Higher order path far-end errored second Higher order path far-end severely errored second Higher order path severely errored second Higher order path unavailable second
Board supported
S16/SD4/SL4/ SQ1/SD1/SL1/AL1/ SDE/ SP8
Table 3-5 List of bit error performance events of lower order path
Abbreviation
LPBBE LPCSES LPES LPFEBBE LPFECSES LPFEES LPFESES LPSES LPUAS
Lower order path background block error Lower order path consecutive severely errored second Lower order path errored second Lower order path far-end background block error Lower order path far-end consecutive severely errored second Lower order path far-end errored second Lower order path far-end severely errored second Lower order path severely errored second Lower order path unavailable second
Board supported
PD1/PQ1/. PQM/ PQ3/ET1
3-3

Table 3-6 List of equipment function performance events
Abbreviation
BCVAVG BCVMAX BCVMIN CCVAVG CCVMAX CCVMIN EDWCSAVG EDMCSMAX EDWCSMIN ENV-TMPCUR ENV-TMPMAX ENV-TMPMIN PUMPTECCCUR RPLCUP RPLMAX RPLMIN TLBCUR TLBMAX TLBMIN TPLCUR TPLMAX TPLMIN WCVAVG
Average back facet detection current of pump laser Maximum back facet detection current of pump laser Minimum back facet detection current of pump laser Average cooling current of erbium doped fiber amplifier (EDFA) laser Maximum cooling current of EDFA laser Minimum cooling current of EDFA laser Average working current setting of pump laser Maximum working current setting of pump laser Minimum working current setting of pump laser Current environment temperature Maximum environment temperature Minimum environment temperature Current pump laser cooling current Current input optical power Maximum input optical power Minimum input optical power Current laser bias current Maximum laser bias current Minimum laser bias current Current output optical power Maximum output optical power Minimum output optical power Average pump laser working current
Board supported
BA2/BPA
S16/SD4/SL4/ SQ1/SD1/SL1/ SDE/BA2/BPA
BA2/BPA
BA2/BPA/XCS
BA2/BPA
S16/SD4/SL4/ SQ1/SD1/BA2/BPA
S16/SD4/SL4/SQ1/ SD1
S16/SD4/SL4/SQ1/ SD1/BA2/BPA
BA2/BPA
3-4
Performance Event Handling Abbreviation

WCVMAX WCVMIN
OptiX 2500+(Metro3000) MM-APE Detailed information

Maximum pump laser working current Minimum pump laser working current
Board supported
3-5
3.2 ATM Service Performance Event

Table 3-7 List of ATM service performance event
Abbreviation
ATM-TOTAL-LOSTUSERCELL0 ATM-TOTAL-LOSTUSERCELL01 ATM-TRANCELL-COUNT
Description
The total number of lost cells of 0 priority The total number of lost cells of 0 and 1 priority The total number of cells transmitted at the ATM physical port The total number of transmitted cells of 0 priority The total number of transmitted cells of 0 and 1 priority
Related board
AL1
ATM-TRANSMITTEDUSERCELL0 ATM-TRANSMITTEDUSERCELL01
3-6
3.3 Performance Events of Ethernet
Service
Abbreviation
RX-BYTE-BAD-CNT RX-PKT-1024-CNT(1024~1518) RX-PKT-128-CNT(128~255) RX-PKT-1519-CNT(1519~MAX) RX-PKT-256-CNT(256~511) RX-PKT-512-CNT(512~1023) RX-PKT-65-CNT(65~127) TX-BRD-OK-CNT TX-BYTE-BAD-CNT TX-BYTE-OK-CNT TX-COL-CNT TX-DEFER-CNT TX-ERR-CNT TX-LCOL-CNT TX-LOST-CNT TX-MLT-OK-CNT TX-MUL-COL-OK-CNT RXB-OK-CNT RXF-PAUSE-CNT TX-PKT-1024-CNT(1024~1518)
Count of bad packet bytes received Count of received packets with length of 1024~1518 bytes (including error packet) Count of received packets with length of 128~255 bytes (including error packets) Count of received packets with length of 1519~MAX bytes (including error packets) Count of received packets with length of 256~511 bytes (including error packets) Count of received packets with length of 512~1023 bytes (including error packets) Count of received packets with length of 65~127 bytes (including error packets) Count of correctly transmitted broadcast packets Count of abnormally transmitted packet bytes Count of correctly transmitted packet bytes Count of collision during transmission Count of deferred transmitted packets Count of transmitted error packets due to underflow Count of packets stopped being transmitted due to late collision Count of lost packets Count of correctly transmitted multicast packets Count of correctly transmitted packets after multiple collisions Count of correctly transmitted packets Count of transmitted PAUSE packets Count of transmitted packets with length of 1024~1518 bytes (including error packets)
Board supported
ET1
3-7
Performance Event Handling Abbreviation

TX-PKT-128-CNT(128~255) TX-PKT-1519-CNT(1519~MAX) TX-PKT-256-CNT(256~511) TX-PKT-512-CNT(512~1023) TX-PKT-64-CNT TX-PKT-65-CNT(65~127) TX-SIG-COL-OK-CNT RXF-UNI-OK-CNT TX-XCOL-CNT RX-BRD-OK-CNT RX-BYTE-OK-CNT RXF-CRC-CNT RXF-LONG-CRC-CNT RXF-LONG-OK-CNT RX-MLT-OK-CNT RXB-OK-CNT RXF-PAUSE-CNT RXF-PKT-64-CNT RXF-SHORT-CRC-CNT RXF-SHORT-OK-CNT RXF-TOOLONG-CNT RX-UNI-OK-CNT(64~MAX)
OptiX 2500+(Metro3000) MM-APE Detailed information

Count of transmitted packets with length of 128~255 bytes (including error packets) Count of transmitted packets with length of 1519~MAX bytes (including error packets) Count of transmitted packets with length of 256~511 bytes (including error packets) Count of transmitted packets with length of 512~1023 (including error packets) Count of transmitted packets with length of 64 bytes (including error packets) Count of transmitted packets with length of 65~127 bytes (including error packets) Count of correctly transmitted packets after first collision Count of correctly transmitted non-broadcast packets Count of packets after more than 16 collisions Count of correctly received broadcast packets Count of received correct bytes Count of received packets with CRC error Count of super long packets with CRC error Count of correctly received super long packets Count of correctly received multicast packets Count of correctly received packets Count of correctly received traffic control packets Count of received packets with length of 64 bytes (including error packets) Count of short packets with CRC error Count of correctly received short packets (<64) Count of received super long packets Count of correctly received (64~MAX) non-broadcast packets
Board supported
ET1
3-8
AUPJCHIGH
Item
Performance event name Full name Board supported Causes
Description
AUPJCHIGH Administrative Unit Pointer Justification Count HIGH S16/SD4/SL4/SQ1/SD1/SL1/SQE/SDE/SDE2/SPQ4 The fundamental reason of the AU pointer justification is that the clocks of the NEs in the SDH network are not synchronous. (1) Performance deterioration of the external clock. (2) Misconnection of optical fibers causes mutual tracing. (3) Performance deterioration of equipment due to extra-high equipment temperature (4) Clock configuration error; (5) The clock quality is deteriorated because the SSM clock protection is not started. (6) The clock ID is not configured, so the loss of the master clock source leads to pointer justification in the whole network. (7) Performance deterioration of the line board (8) Performance deterioration of the clock board
Treatments
(1) Check whether there is any clock alarm, such as SYN_BAD, LTI, S1_SYN_CHANGE, EXT_SYN_LOS, etc. Please handle these alarms first. (2) In the case of the networkwide pointer justification, please check whether the clock configuration is correct, including the clock ID, SSM protocol, clock tracing level, etc. (3) In the case of non-networkwide pointer justification, please check whether the equipment environment temperature is normal, whether the line board performance is normal and replace the faulty board.
Remarks
For the handling of pointer justifications, please refer to the section of Pointer Justification Fault Handling in Trouble Shooting
3-9
AUPJCLOW
Item
Performance event name. Full name Board supported Causes
Description
AUPJCLOW Administrative Unit Pointer Justification Count LOW S16/SD4/SL4/SQ1/SD1/SL1/SQE/SDE/SDE2/SPQ4 The fundamental reason of the AU pointer justification is that the clocks of the NEs in the SDH network are not synchronous. (1) Performance deterioration of the external clock. (2) Misconnection of optical fibers causes mutual tracing (3) Performance deterioration of equipment due to extra-high equipment temperature (4) Clock configuration error (5) The clock quality is deteriorated because the SSM clock protection is not started. (6) The clock ID is not configured, so the loss of the master clock source leads to the pointer justification in the whole network. (7) Performance deterioration of the line board (8) Performance deterioration of the clock board.
Treatments
(1) Check whether there is any clock alarm, such as SYN_BAD, LTI, S1_SYN_CHANGE, EXT_SYN_LOS, etc.. Please handle these alarms first. (2) In the case of the networkwide pointer justification, please check whether the clock configuration is correct, including the clock ID, SSM protocol, clock tracing level, etc. (3) In the case of the networkwide pointer justification, please check whether the equipment environment temperature is normal, whether the line board performance is normal and replace the faulty board.
Remarks
For the handling of pointer justifications, please refer to the section of Pointer Justification Fault Handling in the Trouble Shooting.
3-10
TUNPJC
Item
Performance event name. Full name Board supported Generation principle Causes
Description
TUNPJC TU Negative Pointer Jitter Count PD1/PQ1/PM1/PQM/PL3/PQ3/ET1 The reason of the AU pointer justification is that the AU pointer justification is transformed into the TU pointer justification during the demultiplexing. The TU pointer justification is generated on the cross-connect unit but reported on the tributary board. (1) The AU pointer justification occurs in the network. (2) Cross-connect board fault. (3) Tributary board fault.
Treatments
(1) Handle the AU pointer justification. (2) Replace the faulty board.
Remarks
For the handling of pointer justifications, please refer to the section of Pointer Justification Fault Handling in the Trouble Shooting.
3-11
TUPPJC
Item
Description
TUPPJC TU Positive Pointer Jitter Count PD1/PQ1/PM1/PQM/PL3/PQ3/ET1 The reason of the AU pointer justification is that the AU pointer justification is transformed into the TU pointer justification during the demultiplexing. The TU pointer justification is generated on the cross-connect board but reported on the tributary board. (1) The AU pointer justification occurs in the network. (2) Cross-connect board fault (3) Tributary board fault.
Treatments
(1) Handle the AU pointer justification first. (2) Replace the faulty board.
Remarks
For the handling of pointer justification, please refer to the section of Pointer Justification Fault Handling in the Trouble Shooting
3-12
HPBBE
Item
Description
HPBBE HP Background Block Error S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order bit error refers to the error generated when detecting B3 byte. The background block error is the block in which one or more bits are in error during transmission. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying alarm, regeneration section and multiplex section bit error report, please remove other alarms and performance events according to the priority.
Remarks
The performance event priority is: regeneration section bit error, multiplex section bit error, higher order path bit error and lower order path bit error. For the detailed procedures of bit error handling, please refer to the chapter of Bit Error Fault Handling.
3-13
HPCSES
Item
Description
HPCSES HP Consecutive Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The severely errored second is the one-second period which contains 30% errored blocks. Generally, the consecutive severely errored second will be accompanied with the B3_OVER alarm, and possibly the service will be interrupted. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of alarm, regeneration section and multiplex section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the interconnected switching equipment is normal. (4) Check whether the optical power is normal; (5) Replace the faulty board.
Remarks
The performance event priority is: regeneration section bit error, multiplex section bit error, higher order path bit error and lower order path bit error. For the detailed procedures of bit error handling, please refer to the chapter of Bit Error Fault Handling.
3-14
HPES
Item
Description
HPES HP Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The errored second is a one second period with one or more errored blocks or at least one defect. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm, regeneration section and multiplex section bit errors, please remove other alarms and performance events according to the priority.
Remarks
The performance event priority is: regeneration section bit error, multiplex section bit error, higher order path bit error and lower order path bit error.
3-15
HPFEBBE
Item
Description
HPFEBBE HP Far-End Background Block Error S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The background block error is the block in which one or more bits are in error during transmission. The far-end background block error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
Remarks
3-16
HPFEES
Item
Description
HPFEES HP Far-End Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The errored second is a one second period with one or more errored blocks or at least one defect. The far-end errored second means the bit error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
(1) If this performance event is independently reported, it is most likely due to external equipment factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the alarm, regeneration section and multiplex section bit errors, please remove other alarms and performance events according to the priority.
Remarks
3-17
HPFESES
Item
Description
HPFESES HP Far-End Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The severely errored second is the one-second period which contains 30% errored blocks. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm, regeneration section and multiplex section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the interconnected switching equipment is normal. (4) Check whether the receiving optical power is normal; (5) Replace the faulty board.
Remarks
3-18
HPSES
Item
Description
HPSES HP Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The severely errored second is the one-second period which contains 30% errored blocks. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
Remarks
3-19
HPUAS
Item
Description
HPUAS HP Unavailable Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The higher order path bit error refers to the error generated when detecting B3 byte. The unavailable second is a period of unavailable time begins at the onset of ten consecutive severely errored seconds. In this case the service is interrupted and the corresponding alarm is generated until the fault is removed. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Timing board fault (7) Tributary board fault.
Treatments
Remarks
3-20
LPBBE
Item
Description
LPBBE LP Background Block Error PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order bit error refers to the error generated when detecting V5 byte. The background block error is the block in which one or more bits are in error during transmission. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-21
LPCSES
Item
Description
LPCSES LP Consecutive Severely Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The severely errored second is the one-second period which contains 30% errored blocks. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm, and regeneration section, multiplex section and higher order path bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the interconnected switching equipment is normal. (4) Check whether the receiving optical power is normal; (5) Replace the faulty board.
Remarks
3-22
LPES
Item
Description
LPES LP Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The errored second is a one second period with one or more errored blocks or at least one defect. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-23
LPFEBBE
Item
Description
LPFEBBE LP Far-End Background Block Error PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The background block error is the block in which one or more bits are in error during transmission. The far-end background block error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-24
LPFECSES
Item
Description
LPFECSES LP Far-End Consecutive Severely Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The severely errored second is the one-second period which contains 30% errored blocks. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section, multiplex section and higher order path bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the interconnected switching equipment is normal. (4) Check whether the receiving optical power is normal; (5) Replace the faulty board.
Remarks
3-25
LPFEES
Item
Description
LPFEES LP Far-End Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The errored second is a one second period with one or more errored blocks or at least one defect. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting if the alarm, regeneration section and multiplex section bit errors, please remove other alarms and performance events according to the priority.
Remarks
3-26
LPFESES
Item
Description
LPFESES LP Far-End Severely Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The severely errored second is the one-second period which contains 30% errored blocks. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-27
LPSES
Item
Description
LPSES LP Severely Errored Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error refers to the error generated when detecting V5 byte. The severely errored second is the one-second period which contains 30% errored blocks. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-28
LPUAS
Item
Description
LPUAS LP Unavailable Second PD1/PQ1/.PM1/PQM/PL3/PQ3/ET1 The lower order path bit error is the error generated when detecting V5 byte. The unavailable second is a period of unavailable time begins at the onset of ten consecutive severely errored seconds. In this case the service is interrupted and the corresponding alarm is generated until the fault is removed. (1) External environment interference; (2) Fault of the switching equipment interconnected with the SDH equipment; (3) Signal cable fault; (4) Line board fault; (5) Cross-connect board fault. (6) Tributary board fault.
Treatments
Remarks
3-29
MSBBE
Item
Description
MSBBE MS Background Block Error S16/SD4/SL4/SQ1/SD1/SL1/AL1/SQE/SDE/SDE2/SPQ4 The multiplex section bit error refers to the error generated when detecting B2 byte. The background block error is the block in which one or more bits are in error during transmission. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit error, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Replace the faulty unit with a new one.
Remarks
3-30
MSCSES
Item
Description
MSCSES MS Consecutive Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The severely errored second is the one-second period which contains 30% errored blocks. Generally, the consecutive severely errored second will be accompanied by the B2_OVER alarm, and the service may be interrupted. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance event according to the priority. (3) Check whether the receiving optical power is normal; (4) Check whether the clock configuration is correct. (5) Replace the faulty board.
Remarks
3-31
MSES
Item
Description
MSES MS Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The errored second is a one second period with one or more errored blocks or at least one defect. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external equipment factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal. (4) Replace the faulty board.
Remarks
3-32
MSFEBBE
Item
Description
MSFEBBE MS Far-End Background Block Error S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The background block error is the block in which one or more bits are in error during transmission. The far-end background block error refers to the error detected at the far-end. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit error, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Replace the faulty board.
Remarks
3-33
MSFECSES
Item
Description
MSFECSES MS Far-End Consecutive Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The severely errored second is the one-second period which contains 30% errored blocks. Generally, the consecutive severely errored second will be accompanied by the B2_OVER alarm, and the service may be interrupted. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Check whether the clock configuration is correct. (5) Replace the faulty board.
Remarks
3-34
MSFEES
Item
Description
MSFEES MS Far-End Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The errored second is a one second period with one or more errored blocks or at least one defect. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Replace the faulty board.
Remarks
3-35
MSFESES
Item
Description
MSFESES MS Far-End Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The severely errored second is the one-second period which contains 30% errored blocks. Generally, the consecutive severely errored second will be accompanied by the B2_OVER alarm, and the service may be interrupted. The far-end bit error refers to the error detected at the far-end. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-36
MSSES
Item
Description
MSSES MS Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The severely errored second is the one-second period which contains 30% errored blocks. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) Check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is associated alarm and regeneration section bit error report, please solve other alarms and performance event according to the priority. (3) Check whether the receiving optical power is normal; (4) Check whether the clock configuration is correct. (5) Replace the faulty board.
Remarks
3-37
MSUAS
Item
Description
MSUAS MS Unavailable Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The multiplex section bit error refers to the error generated when detecting B2 byte. The unavailable second is a period of unavailable time begins at the onset of ten consecutive severely errored seconds. In this case the service is interrupted and the corresponding alarm is generated until the fault is removed. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-38
RSBBE
Item
Description
RSBBE RS Background Block Error S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to error generated when detecting B1 byte. The background block error is the block in which one or more bits are in error during transmission. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-39
RSCSES
Item
Description
RSCSES RS Consecutive Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The severely errored second is the one-second period which contains 30% errored blocks. Generally, the consecutive severely errored second will be accompanied by the B2_OVER alarm, and the service may be interrupted. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-40
RSES
Item
Description
RSES RS Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The errored second is a one second period with one or more errored blocks or at least one defect. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-41
RSOFS
Item
Description
RSOFS RS Out-of-Frame Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The Out-of-Frame (OOF) means the loss of the frame alignment byte and the OOF second refers to the second in which at least one OOF occurs. After lasting 3ms, the OOF will become the Loss of Frame (LOF). (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external equipment factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Replace the faulty board.
Remarks
3-42
RSOOF
Item
Description
RSOOF RS Out of Frame S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The OOF refers to the loss of the frame alignment byte and the count of the OOF refers to the occurrence times of the OOF. After lasting 3ms, the OOF will become the LOF. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
(1) If this performance event is independently reported, it is most likely due to external equipment factors. Please check whether there is any electromagnetic interference upon the equipment, whether the operating temperature of the equipment is normal and whether the equipment is well grounded. (2) If the performance event is reported accompanying the reporting of the alarm and regeneration section bit errors, please remove other alarms and performance events according to the priority. (3) Check whether the receiving optical power is normal; (4) Replace the faulty board.
Remarks
3-43
RSSES
Item
Description
RSSES RS Severely Errored Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The severely errored second is the one-second period which contains 30% errored blocks. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-44
RSUAS
Item
Description
RSUAS RS Unavailable Second S16/SD4/SL4/SQ1/SD1/SL1/AL1/SDE The regeneration section bit error refers to the error generated when detecting B1 byte. The unavailable second is a period of unavailable time begins at the onset of ten consecutive severely errored seconds. In this case the service is interrupted and the corresponding alarm is generated until the fault is removed. (1) External environment interference; (2) Fiber performance fault; (3) Line board fault; (4) XCS board fault
Treatments
Remarks
3-45

Maintenance Manual-Alarm and Performance Event

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Maintenance Manual-Alarm and Performance Event

Diunggah oleh

Hak Cipta:

Format Tersedia

1 Generation of Alarm and Performance Event ............................................ 1.1 Overview of SDH Alarm and Performance Event ................................... 1.

OptiX 2500+(Metro3000) Mutil-service Optical Transmission System Maintenance Manual

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

OptiX 2500+(Metro3000) MM-APE

1 About This Manual

About This Manual

OptiX 2500+(Metro3000) MM-APE

About This Manual

OptiX 2500+(Metro3000) MM-APE

Release Upgrade Description

Release upgrade description

OptiX 2500+(Metro3000) MM-APE

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

OptiX 2500+(Metro3000) MM-APE

OptiX 2500+(Metro3000) MM-APE

OptiX 2500+(Metro3000) MM-APE

OptiX 2500+(Metro3000) MM-APE

Performance Event Handling

OptiX 2500+(Metro3000) MM-APE

OptiX 2500+(Metro3000) MM-APE

1 Generation of Alarm and Performance Event

1.1 Overview of SDH Alarm and

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

Higher Order Path

Lower Order Path

Unused HPC output/ HQ-UNEQ

Unused LPC output/ LP-UNEQ

Figure 1-1 SDH alarm signal flow

Generation of Alarm and Performance Event 1. Terminology agreement

OptiX 2500+(Metro3000) MM-APE

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

1.2 Generation and Detection of

Alarm and Performance Event in Signal Flow of Higher Order Part

MS overhead processor (MST)

Pointer processor and HP overhead processor (MSA, HPT)

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

1.2.1 Downlink Signal Flow

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

1.2.2 Uplink Signal Flow

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

1.3 Generation of Alarm and

Performance in Signal Flow of Lower Order Part

H4 HP-LOM V5 LP-RDI E1-AIS V5 V5 LP-RFIFO BIP-2 LP-REI All "1''s

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE

1.3.1 Downlink Signal Flow

Generation of Alarm and Performance Event

OptiX 2500+(Metro3000) MM-APE