Académique Documents
Professionnel Documents
Culture Documents
Upon completion of this course, you will be able to: Know the mechanism of SDH Alarm and performance generation; Analyze and process most of common alarm and performance events.
Page 1
Page 2
Page 3
Terminology
Downlink signal flow & Higher order part
SDH Interface
cross-connect
SDH Interface
unit
PDH interface
Terminology
SDH Interface
cross-connect
SDH Interface
unit
PDH interface
Page 5
Terminology
Two Common Alarms
AIS (Alarm Indication Signal)
Inserts the all 1s signal into the lower level circuits, Indicating that the signal is unavailable. Common AIS alarms include MS_AIS, AU_AIS, TU_AIS and E1_AIS.
RDI (Remote Defect Indication)
Indicates the alarm transferred back to the home station from the opposite station after the opposite station has detected alarms of LOS (loss of signal), AIS and TIM (trace identifier mismatch). Common RDI alarms include MS_RDI, HP_RDI and LP_RDI.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 6
Page 7
Page 8
A1,A2 B1
H1,H2
Downlink signal flow Signal transfer point (Insert down all "1"s signal) HUAWEI TECHNOLOGIES CO., LTD. All rights reserved
Alarm report or return Alarm termination point (Report to SCC unit) Page 9
Optical receiving
Optical/electrical conversion (O/E) O/E module checks Optical signal (If no light in the input signal, optical power excessively low or high or the code type mismatch, R_LOS alarm will be reported) A1, A2 and J0 bytes detecting Search the framing bytes (R_OOF, R_LOF) Extract the line synchronous timing source J0 byte (J0_MM) Scramble B1 byte detecting BIP-8 computing to check bit error (B1_SD, B1_EXC, SES, RSUAT) Process F1, D1 - D3 and E1 bytes
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 10
SF and SD detection Process D4 ~ D12, S1 and E2 bytes MSP protection function MS_AIS, MS_RDI
B2 byte detecting
BIP-24 computing to check bit error (B2_SD and B2_OVER) M1 bytes (MS_REI)
Page 11
Frequency and phase alignment Locate each VC-4 and send it to higher order path overhead processor Generate AU_AIS, AU_LOP J1, C2, B3 and G1 bytes detecting J1 Bytes (HP_TIM) C2 Bytes (HP_UNEQ, HP_SLM) B3 bit error detecting (B3_SD, B3_OVER, SES, HVCUAT) H4 Bytes (For VC12 signal, HP_LOM) G1 Bytes (HP_RDI, HP_REI) F3, K3, N1 Bytes (Reserved)
Page 12
HP_RDI (G1)
HP_REI (G1)
Page 13
Page 14
Page 15
Page 16
H LPT
I LPA
J PPI
K PDH Interface
Page 17
X C S
(PPI)
V5 V5 J2 V1,V2 V1,V2 H4 V5
X C S
Downlink signal flow Signal transfer point (Insert down all "1"s signal)
Page 18
Demap the VC-4 into VC-12s Pointers of all VC-12s are decoded TU_AIS, TU_LOP
V5 Bytes detecting
LP_RDI( b8), LP_UNEQ, LP_SLM( b5-b7), LP_REI( b3) BIP-2 computing to check bit error( b1-b2)
H4 Bytes detecting
HP_LOM
J2 Bytes detecting
LP_TIM
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 19
Recover data stream and the related clock reference signals Detect LP_RFIFO alarm
PDH Physical Interface
Page 20
Data adaptation
Detect LP_TFIFO alarm
PDH Physical Interface
Clock extraction and dada regeneration Detect and terminate the T_ALOS alarm Detect E1_AIS alarm
Page 21
Insert POH in the C-12 (C-12 to VC-12) V5 byte (Insert "signal label" in the b5-b7, calculate BIP-2, set the result to the b1 and b2)
Higher Order Path Adaptation Adapt VC-12 into TU-12 Map TU-12 into higher order VC-4
Page 22
as that of E1 PDH service But there are still some differences: Same Type of Alarms with Different Names 2Mbit/s 34Mbit/s 140Mbit/s T_ALOS P_LOS EXT_LOS TU_AIS E3_AIS C4_R_LAISD/C4_T_LAISD
Path Overhead Bytes Used for Alarm& Performance Monitoring are Different
2Mbit/s: V5 Byte 34Mbit/s, 140Mbit/s: B3, J1, C2 and G1 Bytes
Page 23
Page 24
A1, A2 Bytes
B1_EXEC
B2_EXEC
AU_AIS HP_TI M
AU_LOP
HP_LOM
B1_SD
HP_UNE Q
B2_SD HP_RDI
B3_EXEC
HP_SLM
B3_SD
TU_AIS
LP_UNEQ
TU_LOP
LP_TIM
BIP_EXEC
LP_SLM
Legen d:
A suppress B
BIP_S D
LP_RDI
Page 25
Page 26
next frame
B1: BIP8 for the regenerator section error monitoring function
B2: BIP24 for multiplex section error monitoring function B3: BIP8 for monitoring the bit error performance of VC-4 V5: BIP2 for monitoring the bit error performance of VC-12
order path, higher order bit errors will trigger lower order errors. LPT HPT MST RST B1 RST MST HPT LPT
B2
B3 V5
Page 28
Errored block, in which one or more bits are in error. Background block error, it is an errored block occurring outside of the period of UAT and SES. Far end block of background error, it is a BBE event detected at the far end. Errored second, it is a certain second with one or more errored blocks detected. Far end errored second, in which an ES event detected at the far end. Severely errored second, it is a certain second 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.
SES
Page 29
Far end severely errored second, in which an SES event detected at the remote end.
Consecutive severely errored second, in which the SES events consecutively occur, but last less than 10 seconds. Far end consecutive severely errored second, in which a CSES event detected at the far end.
Unavailable second, it is a period of 10 consecutive seconds during which the bit error ratio per second of the digital signal in either of the transmission directions of a transmission system is inferior to 10-3 . These ten seconds are considered to be part of unavailable time.
UAS
Page 30
Pointer Justification
Mechanism
Adjust pointers as required in practice, so as to tolerate rate asynchronization and phase difference of payload signals. That is, perform pointer justification on information payloads to make the payloads synchronous with the STM-N frame
Sort
Page 31
H1 Y Y H2 F F H3 H3 H3 Causation:
Network is out of synchronization
VC4
1 9
row 10270 Column
Page 32
Page 33
Alarm and Performance are belong to different levels. Alarm indicates the fault of transmission, performance indicates the signal degrade of transmission. If the value of performance is high than threshold it will translate into alarm. For example bit error can translate into EXC alarm then causes the traffic interrupt.
Functions of alarm and performance for bit error threshold crossing
Item RS MS HP LP RSBBE MSBBE HPBBE LPBBE Performance Event Alarm Event
Local end
-
Remote end
MSFEBBE HPFEBBE LPFEBBE
Local end
B1_OVER B2_OVER HPCROSSTR LPCROSSTR -
Remote end
MS_REI HP_REI LP_REI
Page 34
Question
Please describe the suppression correlation between SDH alarms? Whats the mechanism of Pointer justification? Whats the relationship between Performance event and Alarm?
Page 35
Page 36
Page 37
SDH Unit
R_LOF
Introduction:
Page 38
SDH Unit
R_LOS
Introduction: R_LOS alarm indicates receive loss of signal, critical alarm. Probable Causes There is a fiber cut.
Page 39
SDH Unit
R_LOF/R_LOS Clearing Procedure:
Step 1
Action Check whether there is any higher-level R_LOS alarm on the T2000. Clear these higher-level alarms first. If the alarm does not clear, continue with the next step. Check whether the received optical power of the board reporting the alarm is normal. If yes, turn to Step 9.If not, continue with the next step. Clean the fiber connector and the receiving optical interface of the board. If the alarm does not clear, continue with the next step. Check if the connection between local flange and the optical attenuator is correct, and if the attenuation value is too high. If there is a fault, clear it. Then, check if the alarm clears. If the alarm persists, continue with the next step. Check if the transmitting optical power of the opposite station is normal. If not, replace the line board. If yes, clean the fiber connector of the opposite station.
3
4
Page 40
SDH Unit
R_LOF/R_LOS Clearing Procedure:
Step Action If the alarm persists, check if the connection between local flange and the optical attenuator of the opposite station is correct, and if the attenuation value is too high. If there is a fault, clear it. Then, check if the alarm clears. If the alarm persists, continue with the next step. Check the fiber. If there is a problem, clear it. Then, check if the alarm clears. If the alarm persists, continue with the next step. Replace the line board reporting the alarm at the local station. If the alarm does not clear, continue with the next step. Replace the GXCS, EXCS, UXCS, or XCE on the local station. If the alarm does not clear, continue with the next step. Replace the line board on the opposite station. If the alarm does not clear, continue with the next step.
7 8 9 10
11
Page 41
SDH Unit
B2_OVER
Introduction: B2_OVER alarm indicates indication of excessive B2 errors in the multiplex section, major alarm. Probable Causes : The received signal attenuation is excessive. The fiber end is not clean.
Page 42
SDH Unit
B2_OVER Clearing Procedure
Step 1 Action Check whether there are any higher-level alarms, such as R_LOS, R_LOF or B1_EXC on the T2000. Clear these higher-level alarms first. If the alarm does not clear, continue with the next step. Check whether the working temperature of the equipment is too high. If yes, lower the temperature. Then, if the alarm persists, continue with the next step. Replace the line board reporting the alarm at the local station. If the alarm does not clear, continue with the next step. Replace the GXCS, EXCS, UXCS, or XCE on the local station. If the alarm does not clear, continue with the next step. Replace the line board on the opposite station. If the alarm does not clear, continue with the next step. Replace the GXCS, EXCS, UXCS, or XCE on the opposite station.
3 4 5 6
Page 43
SDH Unit
MS_AIS Introduction: MS_AIS alarm indicates multiplex section alarm indication,
Page 44
SDH Unit
MS_AIS Clearing Procedure
Step Action Check whether the corresponding line board reports R_LOS or R_LOF alarm on the T2000. If there is a R_LOS or R_LOF, clear it. Then, check if the alarm clears. If the alarm persists, continue with the next step. Reset or replace the line board on the local station. If the alarm does not clear, continue with the next step. Reset or replace the line board on the opposite station. If the alarm does not clear, continue with the next step. Reset or replace the GXCS, EXCS, UXCS, or XCE on the opposite station.
Page 45
SDH Unit
AU_AIS
The opposite station sends AU_AIS. The transmitter of the opposite station fails. The receiver of the local station fails.
Page 46
SDH Unit
Step AU_AIS Clearing Procedure Action
1 Check whether there are any higher-level alarms, such as R_LOS, R_LOF, B1_EXC or B2_OVER, on the T2000. Clear these higher-level alarms first. If the alarm does not clear, continue. Check whether the NE is under the protection switching. If yes, remove the fault. If the alarm does not clear, continue. Check whether the service configuration of the NE is correct. If not, modify the incorrect configuration. Then, check whether the alarm clears. If not, continue. Use the alarm analysis and loopback methods to find the NE on which a fault occurs. Replace the line board reporting alarms on the faulty NE. If the alarm does not clear, continue. Replace the XCS board on the faulty NE. If the alarm does not clear, continue. Replace the line board of the opposite station. If the alarm does not clear, continue. Replace the GXCS, EXCS, UXCS, or XCE board on the opposite station. Page 47
2 3 4 5 6 7 8
SDH Unit
BD_STATUS Introduction: BD_STATUS alarm indicates board offline, major alarm. Probable Causes: The board is not inserted. The board is not fully inserted. The mailbox fails.
Page 48
SDH Unit
BD_STATUS Clearing Procedure
Step 1 2
Action Check whether the corresponding board is in the slot. Remove and re-insert the board. If the alarm does not clear, continue with the next step.
Replace the board. If the alarm does not clear, continue with the next step.
Page 49
SDH Unit
Other Alarms
Name MS_RDI MS_REI AU_LOP HP_TIM HP_SLM HP_RDI HP_REI HP_UNEQ IN_PWR_ABN Description Multiplex section remote defect indication, minor alarm. Multiplex section remote error indication, warning AU loss of pointer, minor alarm. Higher order path tracking identification mismatch, minor alarm. Higher order path signal identification mismatch, minor alarm. Higher order path remote defect indication, minor alarm. Higher order path remote error indication, minor alarm. No loading error in the higher order path, minor alarm. Input power abnormal, major alarm.
LASER_SHUT
LOOP_ALM COMMUN_FAIL
Page 50
Page 51
PDH Unit
TU_AIS
Probable Causes
There are errors in configuration data. The corresponding path at the opposite station fails. There is a higher level alarm. The cross-connect board fails.
Page 52
PDH Unit
TU_AIS Clearing Procedure
Step
1
Action
Check whether there are any higher-level alarms, such as R_LOS, R_LOF or HP_SLM, on the T2000. Clear these higher-level alarms first. If the alarm does not clear, continue with the next step. Check whether the NE is in the protection switching state. If yes, remove the fault causing the switching. Then, check whether the alarm clears. If not, continue with the next step. Check whether the service configuration of the NE is correct. If not, modify the incorrect configuration. Then, check whether the alarm clears. If not, continue with Step 4. Replace the alarm reporting tributary board. If the alarm does not clear, continue with the next step. Replace the GXCS, EXCS, UXCS, or XCE.
4 5
Page 53
PDH Unit
TU_LOP
Introduction: TU_LOP alarm indicates TU Loss of Pointer, which is a major alarm. Probable Causes:
The interface between the tributary board and the crossconnect board fails.
There are errors in configuration data.
Page 54
PDH Unit
TU_LOP Clearing Procedure
Step Action Check whether there are any higher-level alarms, such as R_LOS, R_LOF or HP_SLM, on the T2000. Clear these higher-level alarms first. If the alarm does not clear, continue with the next step. Check whether the NE is in the protection switching state. If yes, remove the fault causing the switching.
Then, check whether the alarm clears. If not, continue with the next step.
3 4 5 Check whether the service configuration of the NE is correct. If not, modify the incorrect configuration. If the alarm persists, replace the alarm reporting tributary board and then view whether the alarm is removed. If the alarm persists, replace the GXCS, EXCS, UXCS, or XCE.
Page 55
PDH Unit
T_ALOS
Introduction: T_ALOS alarm indicates E1 interface loss of analog signal, which is a major alarm. Probable Causes: No E1 service is accessed. The output port of the E1 interface on the DDF side is disconnected or loosened. The input port of the E1 interface at the local station is disconnected or loosened. Board failure. Cable fails.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 56
PDH Unit
T_ALOS Clearing Procedure
Step 1
Action Check whether the corresponding path of the tributary board reports the TU_AIS or TU_LOP alarm on the T2000. If yes, clear the alarm. Then, check if the T_ALOS clears. If not, continue with the next step. Perform self-loop (hardware inloop) for the path reporting the alarm at the DDF. If the alarm clears, the fault lies in the equipment of the opposite end. Remove the fault. Then, check if the alarm clears. If not, continue with the next step. Perform self-loop (hardware inloop) for the path at the interface board. If the alarm clears, the fault lies in the signal cable connection. Remove the fault. Then, check if the alarm clears. If not, continue with the next step. Perform inloop for the path on the T2000. If the alarm clears, the fault lies in the interface board. Remove and then re-insert or replace the interface board. Then, check if the alarm clears. If not, continue with the next step. Replace the service processing board.
4 5
Page 57
PDH Unit
Other Alarms
Name LP_RDI LP_REI NO_BD_SOFT PS UP_E1_AIS DOWN_E1_AIS ALM_SUBCARD_ABN BD_STATUS Description Lower order path remote defect indication, minor alarm. Lower order path remote error indication, minor alarm. No board software, critical alarm. Protection switching is initiated, major alarm. 2M signal alarm indication, minor alarm. E1 down signal alarm, minor alarm. Find the fault of sub-board, major alarm. Board offline, major alarm.
COMMUN_FAIL
Page 58
Page 59
Ethernet Unit
ALM_SUBCARD_ABN
Introduction:
ALM_SUBCARD_ABN alarm indicates find the fault of subboard, which is a major alarm. Probable Causes: The interface board does not match the processing board. Clearing Procedure:
Step 1 2 Action Check whether the interface board is inserted correctly. If not, re-insert the board. If the alarm persists, check the configuration of the corresponding service processing board on the T2000. Modify the incorrect configuration. All rights reserved Page 60
Ethernet Unit
Other Alarms Name
AU_AIS Description AU alarm indication, major alarm.
ETH_LOS
PROTOCOL_MM NO_BD_SOFT BD_STATUS
COMMUN_FAIL
LOOP_ALM
Page 61
Page 62
Introduction: APS_FAIL alarm indicates APS protection switching failed, which is a major alarm.
Probable Causes:
The multiplex section protection (MSP) parameters of the nodes are incorrect. The MSP parameters of the nodes are lost.
Page 63
Check whether the MSP protocol is normal. If not, stop and then restart the protocol.
Page 64
Introduction:
APS_INDI alarm indicates APS protection switching indication, which is a major alarm. Probable Causes: MSP switching is initiated. Clearing Procedure
Step 1 Action For an MSP ring, this alarm indicates that MSP switching is initiated. Remove the fault. For a non-ring MSP network, this alarm indicates that the APS protocol is initiated abnormally. Check whether the MSP parameters of the nodes are correct. If not, modify the incorrect parameters.
Page 65
Introduction:
The EXT_SYNC_LOS alarm indicates loss of external synchronous source, which is a minor alarm.
The external clock source is lost. Probable Causes:
Clearing Procedure:
Step 1 2 Action Check whether the equipment that provides the external clock works efficiently. Check whether the external clock cable is connected correctly and whether the connectors are in good contact. If there is a fault, remove it.
Page 66
Introduction: LTI alarm indicates loss of synchronization source, which is a major alarm. Probable Causes:
Non S1 mode:
There is a fiber cut (the line clock is traced). No external clock source is input (the external clock is traced). The synchronization source is set as non-retrieve, is blocked or is set incorrectly. S1 mode: There is a fiber cut. The free-run mode is in active. The synchronization source is set incorrectly.
Page 67
External clock source 2 Check whether the output signal of the external clock device is normal. If not, replace the device. Then, check if the alarm clears. If the alarm persists, continue with the next step. Check whether the external clock input mode is proper (2 MHz or 2 Mbit/s). If the mode mismatches each other, correct the setting. Then, check if the alarm clears. If the alarm persists, continue with the next step. Check whether the external clock input impedance is proper ( 75-ohm or 120-ohm). If the impedance mismatches each other, correct the setting. Then, check if the alarm clears. If the alarm persists, continue with the next step. Check whether the clock input cable is connected correctly. If not, connect the cable correctly. Then, check if the alarm clears. If the alarm persists, continue with the next step. Reset or replace the GXCS, EXCS, UXCS, or XCE.
5 6
Page 68
Line clock source Check whether the corresponding line board reports R_LOS alarm through the T2000. If there is a R_LOS alarm, clear it. Then, check if the alarm clears. If the alarm persists, continue with the next step. Reset or replace the line board. 8 If the alarm does not clear, continue with the next step.
Page 69
Name
BUS_ERR CLK_NO_TRACE_MODE S1_SYN_CHANGE SYN_BAD SYNC_C_LOS NO_BD_SOFT COMMUN_FAIL BD_STATUS Bus error, major alarm.
Description
Clock entering into non-tracing running mode, minor alarm. Clock reference source change in S1_Mode, minor alarm. Synchronization source deteriorated, minor alarm. Synchronization source level loss, warning. No board software, critical alarm. Serial port communication failure, major alarm. Board not in position alarm, major alarm.
Page 70
Page 71
SCC Unit
NESTATE_INSTALL
Probable Causes:
The NE is under installation. Clearing Procedure:
Step 1 Action Correct the configuration data and re-send the data.
Page 72
SCC Unit
WRG_BD_TYPE
Introduction: WRG_BD_TYPE alarm indicates wrong inserted board type, which is a minor alarm.
Probable Causes:
A wrong board is inserted. There are errors in the board configuration.
Step 1 2
Page 73
SCC Unit
Other Alarms
Description The HARD_BAD alarm indicates hardware fails, critical alarm. Lost of one nesoft, critical alarm. Multiplex section node ID mismatch, Major alarm. Power is abnormal, major alarm Power failure, major alarm Serial port communication failure, major alarm. Board not in position alarm, major alarm.
Page 74
Exercise
Case of 2 fiber SNCP ring with no protection chain. NE1, NE2, NE4, NE5 is
NE1
NE2
1#-16#VC12
NE4
T11-16
NE2
W E
T11-16 W2 W
17#-32# VC12
NE3
E
SNCP
NE1
W
NE5
T21-16
33#-48#VC12
T11-16
NE4
T21-16
49#-63# VC12
T21-16
E
T11-15
T31-15
Page 75
Exercise
If the Tx fiber between NE2 and NE3 is broken, please fill in the blank. If no
Card\NE E
NE1
-
NE2
MS_RDI
-
NE3
R_LOS
NE4
MS_AIS
NE5
-
W
PQ1 (NE1)
Page 76
Summary
Generation of Alarm& Performance Alarm& Performance Event Clearing Case of Ring with Chain
Page 77
Thank You
www.huawei.com