Sdh/Sonet: Alarms & Performance Monitoring

SDH/SONET
ALARMS & PERFORMANCE MONITORING
1 www.mapyourtech.com
Contents
• Standards
• Alarms Introductions and Examples
• Performance Monitoring Parameters
• FAQs
Standards
Bell Communications Research (Bellcore, BCR)

prepares equipment standards for North American community
ANSI Committee T1
prepares telecommunications standards (rates and formats)
creator of SONET
ANSI (American National Standards Institute) accredited
sponsored by ATIS (Alliance for Telecommunications Industry Solutions)
ITU-T G.826,G.783
Alarms Introductions and Examples
Alarm Overview
  1. RS
2. MS
3. HP
 4. AU
5. TU
  6. LP
7. PPI
SDH Frame
V1 V5 
5 www.mapyourtech.com V2 
The SDH Frame
VC-4 POH
R A1 A1 A1 A2 A2 A2 J0
S
B1 E1 F1 J1 Lower order
O
H VC-n POH
D1 D2 D3 B3
AU H1 H1 H1 H2 H2 H2 H3 H3 H3 C2
Pointer
B2 B2 B2 K1 K2 G1 VC-11 VC-12 VC-2
D4 D5 D6 F2 V5 V5 V5
M
D7 D8 D9 H4 25 34 106
S
O
D10 D11 D12 F3 N2 N2 N2
H
S1 Z1 Z1 Z2 Z2 M1 E2 K3 25 34 106
N1 K4 K4 K4
25 34 106
Number of bytes of
6 www.mapyourtech.com data separating fields.
RSOH [Regenerator Section Overhead]
A1, A2 RS-LOF Provides a frame alignment pattern [A1 =11110110, A2 = 00101000]. The frame alignment word of an
STM-n frame is 3 X n A1 bytes followed by 3 X n A2 bytes.
J0 RS-TIM Regenerator section trace. [16 byte frame including CRC7 (1st byte.) Supports continuity testing
between transmitting and receiving device on each regenerator section.
Z0 Spare. Reserved for future international standardisation.
B1 RS-EXC Provides regenerator section monitoring. The regenerator section BIP-8 provides end-to-end error
RS-DEG performance monitoring across an individual regenerator section and is calculated over all bits of the
previous STM-n frame after scrambling. Computed value is placed in B1 byte before scrambling
E1 Provides local orderwire channel for voice communications between regenerators, hubs and remote
terminal locations.
F1 Allocated to user’s purpose [e.g. temporary data/voice channel connection for special maintenance
applications]
D1-D3 COMMS 192 kb/s message based data communications channel providing administration, monitor, alarm and
maintenance functions between regenerator section termination equipment
B1 – Is not supported in OM4000 NE’s due to redundancy and

this NE is primarily used as an ADM
SDH Frame
MSOH [Multiplex Section Overhead]
B2 MS-EXC Provides multiplex section error monitoring. The BIP-n X 24, of an STM-n frame, provides end-
MS-DEG to-end error performance monitoring across an individual multiplex section and is calculated over
all bits of the previous STM-n frame except for the first three rows of SOH. Computed value is
placed in B2 byte before scrambling.
K1, K2 MS-AIS Two bytes allocated for APS signalling for multiplex section protection.
MS-RDI K2 [b6-b8] contains MS-RDI and MS-AIS status information.
D4-D12 COMMS Provides 576 kb/s data communication channel between multiplex section termination
equipment. Used to carry network administration and maintenance information.
S1 Synchronisation status messages. S1 [b5-b8] indicates which of the four levels of

synchronisation is being used at the transmit end of a multiplex section.
M1 MS-REI Multiplex section remote error indication [MS-REI]. Conveys the number of B2 errors detected
by downstream equipment.
E2 Provides express orderwire channel for voice communications between multiplex section
terminating equipment
H1-H3 AU-AIS AU pointer bytes are associated with, but not part of, the MSOH. The pointer contained in H1
TU-AIS [TU-3] and H2 points to the location where the VC-n begins. The last ten bits [b7-b16] of H1, H2 carry
the pointer value [0 to 782]. The H3 bytes are ‘pointer action’ bytes and carry ‘live’ information
AU-LOP
from a VC4, during the STM-n frame in which negative pointer adjustment occurs
TU-LOP [TU-3]
MSP Protocol Bytes K1 [b1-4] – SDH Frame

8 type of request [b5-8] – channel number
www.mapyourtech.com K2 [b1-4] –
channel bridging [b5] – protection architecture
HO-POH [Higher order path Overhead]
J1 HP-TIM [VC-4] The first byte in the virtual container. Its location is indicated by the AU pointer [H1,H2
LP-TIM [VC-3] bytes]. Provides a higher order trail trace identifier [64-byte free format string or 16-byte
frame including CRC7. Supports end-to-end monitoring of a higher order path.
B3 HP-EXC Provides higher order path error monitoring. The BIP-8 is calculated over all bits of
HP-DEG previous VC-n. Computed value is placed in B3 byte before scrambling.
LP-EXC+DEG [VC-3]
C2 HP-AIS High order signal label. Indicates composition or the maintenance status of the associated
LP-AIS [VC-3] container.
HP-UNEQ+PLM
LP-UNEQ+PLM [VC-3]
G1 HP-REI + RDI Higher order path status. Send status and performance monitoring information from
LP-REI + RDI [VC-3] receiving path terminating equipment to originating equipment. Allows status and
performance of two-way path to be monitored at either end. G1 REI [b1-b4] RDI [b5]
F2 Higher order path user channel. Allocated for network operator communications between
path terminations.
H4 HP-LOM Position indicator. Multiframe phase indication for TU structured payloads. H4 [b7-b8]
F3 Higher order path user channel. Allocated for network operator communications between
path terminations
K3 Higher order path automatic protection switching [b1-b4]. The rest of the bits [b5-b8] are
allocated for future use.
N1 Higher order tandem connection monitoring. There are two possible implementations
described in Annex C and Annex D of ITU-T G.707. In Annex C, the N1 byte provides a
tandem connection incoming error count [IEC] and the remaining four bits provide an end-
to-end data link
SDH Frame
LO-POH [Lower order path Overhead]
V5 [VC-12] Provides BIP-2 error checking, signal label and path status information.
LP-AIS [b5-b7]
LP-REI [b3]
LP-RDI [b8]
LP-EXC [b1-b2]
LP-UNEQ [b5-b7]
LP-PLM [b5-b7]
J2 LP-TIM [VC-12] Lower order trail trace identifier [16 byte frame including CRC7]. Supports end-to-
end monitoring of a lower order path
N2 Lower order tandem connection monitoring. Contains BIP-2 error checking, AIS,
tandem connection REI [TC-REI], outgoing error indication [OEI] and a 76-byte
multiframe containing a tandem connection access point identifier [TC-APid].
K4 Lower order path automatic protection switching [b1-b4] and enhanced remote
defect indication [b5-b7].
SDH Frame
Anomalies, defects and alarms
 Alarm
 A human observable indication that draws attention to a failure usually giving an indication of
the severity of the fail
 The report to the user of a defect
 Anomaly
 The smallest discrepancy which can be observed between the actual and desired
characteristics of an item. The occurrence of a single anomaly does not constitute an
interruption in the ability to perform a required function. Anomalies are used as the input for
the Performance Monitoring [PM] process and for the detection of defects
 A single occurrence of, or commencement of a pre-defined condition
 Defect
 The density of anomalies has reached a level where the ability to perform a required function
has been interrupted. Defects are used as input for PM, the control of consequent actions, and
the determination of faults cause
 The persistent or repeated occurrence of an anomaly for a pre-defined duration or
number of repetitions
Defect naming
 The origin of defect naming can be confusing.
 The following points should help when dealing with the nomenclature
 Defects derived from path overheads begin: LP, HP, LPOM or HPOM.
 Defects derived from section overheads begin: RS or MS.
 Defects related to conditions affecting a whole VC and its pointer begin: AU or TU. AU is used for VC-4s.
TU is used for TU-3s, TU-2s and TU-12s. Defect types beginning TU are not distinguishable.
 When distinguishing LP and LPOM remember that LPs will be present when traffic is terminated and
LPOMs when traffic is un-terminated.
 A defect type (e.g. LP-EXC) has two parts:

 Part 1 is a "function point“
 Part 2 is an "alarm category".
 Example: LP-EXC. This defect is detected at the LP function point - the "low order path termination"
function point. The category of the defect is "EXC" - EXCessive bit errors.
 Excessive bit errors in a VC-3 will give an LP-EXC defect, as will excessive bit errors in a
VC-12. The two defects share their type but they have distinct instances. When the corresponding alarm is
reported to the user the type and instance will be reported.
Defect Correlation
 If a defect is subject to correlation

 it will NOT be raised if another alarm is present.
 Aim of defect correlation
 The aim of correlation is to present to the operator only the alarm closest to the source cause of a
set of related defects. This reduces the amount of fault analysis required of the operator and the
traffic on communication channels.
 Example:
 If EXC is present it will hide the presentation of TIM, PLM, UNEQ etc.
 More specifically EXC will ‘mask’ TIM, PLM and UNEQ alarms.
HP-EXC A
A masks B
HP-TIM HP-PLM HP-UNEQ B
Plug In Unit Defect Correlation
• Plug In Unit [PIU] related defects

– For a given instance of PIU in a slot
– All defects present within that PIU will be masked
Card Fail Card Fault Wrong Card Unexpected Card
= ‘A masks B’
Alarm raised on the card/slot instance

B
PDH Traffic Defect Correlation
PPI LOS PPI UNEXP SGNL
= ‘A masks B’ PPI EXC
B
PPI DEG PPI AIS INT LP IP BUFFER INT HP IP BUFFER
PPI LOF
PPI LOM
SDH traffic DEFECT correlation
RS LOS RS UNEXPECTED SIGNAL
A
ES CMI
= ‘A masks B’
B
RS LOF
A
QECC COMMS FAIL RS TIM MS RDI

= ‘A masks B, dependent
on AIS consequent
MS AIS MS RDI action configuration of A
B
MS EXC
MS DEG AU LOP
AU AIS
HPOM EXC
HPOM TIM HPOM PLM HPOM UNEQ
HP EXC
INT HP OP BUFF HP DEG HP LOM HP TIM HP PLM HP UNEQ HP RDI
PPI LOF HP REI

TU LOP
TU AIS
A
INT TU LOP LPOM EXC
= "A masks B if B's TU

type is TU-12"
B INT TU AIS LPOM TIM LPOM PLM LPOM UNEQ
LP EXC
INT LP OP BUFFER LP DEG LP TIM LP PLM LP UNEQ LP RDI
17 www.mapyourtech.com LP REI
What is a path?
 A path is an end to end circuit
 The ends of a LO path are where traffic is brought into SDH or removed from SDH
 Paths carry VCs
 LO VCs are
 generated where traffic is brought into SDH
 and terminated where it is removed
 HO VCs are
 Generated / terminated where traffic is brought into SDH or when LO VCs are brought into / removed from a
HO VC
Low Order Path
High Order Path
Multiplexer
Regenerator
Carrying a 2 Meg circuit in a STM frame
 2M example where
 High order paths are
 encased in STM frames when they pass between nodes
 Low order paths are
 threaded through high order paths
RS 2M trib
MS
HO path STM-1 tributary with a LO
connection
LO path
19 www.mapyourtech.com 2M PDH Multiplexor Regenerator
SONET Layers
Path Section Line Path Path
Terminating Terminating Terminating Terminating Terminating
Equipment Equipment Equipment Equipment Equipment
(PTE) (STE) (LTE) (PTE) (PTE)
DS1 DS1
VT Path VT Path
DS3
STS Path STS Path STS Path
DS3
Line Line Line Line
Section Section Section Section Section
Photonic Photonic Photonic Photonic Photonic
Section Section Section Section

Line Line Line
STS Path STS Path

VT Path
SDH Section Hierarchy
 There are four sections – Regenerator Section (RS), Multiplex Section (MS), Higher
Order Path Section (HP), and Lower Order Path Section (LP)
 RS is a part (section) of the optical fibre network, within which RSOH part of SDH frame
is NOT opened
 MS is a part (section) of the optical fibre network, within which MSOH part of SDH frame
is NOT opened
 HP is a part (section) of the optical fibre network, within which higher order VC part of
SDH frame is NOT opened (it may be opened only for interpreting HOPOH)
 LP is a part (section) of the optical fibre network, within which lower order VC part of
SDH frame is NOT opened (it may be opened only for interpreting LOPOH)
Downlink signal flow & High order part
High order part
SDH SDH
Interface cross-connect Interface
unit
PDH interface
Downlink signal
flow
Uplink signal flow & Low order part
SDH SDH
Interface cross-connect Interface
unit
PDH interface
Uplink signal flow

Low order part
Two Common Alarms
AIS (Alarm Indication Signal)
Inserts the all “1”s signal into the Low 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.
Alarms & Performance of High Order Part
SDH Interface to Cross-connect Unit
Uplink signal Flow
A B C D E F G
STM-N SPI RST MST MSP MSA HPT Cross-connect

Unit
Downlink signal Flow
Diagram of Alarm Generation
Frame synchronizer& RS MS overhead processor Pointer processor& HP
overhead processor overhead processor
(RST) (MST) (MSA, HPT)
STM-N LOS “1” AIS “1” AIS
Optical
Signal
LOF MS_AIS AU_AIS
A1,A2 K2 H1,H2
B2 Err AU_LOP
B1 Err B2 H1,H2
B1 HP_TIM
MS_REI J1 X
M1 HP_UNEQ “1”
C2 C
MS_RDI HP_SLM S
K2 C2
HP_LOM
H4
B3 Err
B3
HP_REI
G1
HP_RDI
G1
Downlink signal flow Alarm report or return
Signal transfer point (Insert down all "1"s Alarm termination point (Report
signal) to SCC unit)
Downlink Signal Flow
Frame synchronizer and RS overhead processor
 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
MS overhead processor
 K1 and K2 bytes detecting

 SF and SD detection
 Process D4–D12, S1 and E2 bytes
 MSP protection function
 MS_AIS, MS_RDI
 B2 byte detecting
 BIP-8 computing to check bit error (B2_SD and B2_OVER)
 M1 bytes (MS_REI)
Pointer processor and HP overhead processor
 H1 and H2 bytes detecting

 Frequency and phase alignment
 Locate each VC-4 and send it to High 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)
Uplink Signal Flow
Pointer processor and HP overhead processor
 Generates N High order path overhead bytes

 J1, C2, B3, G1, F2, F3 and N1 Bytes
 Return alarm to the remote end

 HP_RDI (G1)
 HP_REI (G1)
 AU-4 pointers generating

 Pointer processor generates N AU-4 pointers
Uplink Signal Flow
MS overhead processor
 Set multiplex section overhead (MSOH) Bytes
 K1, K2, D4-D12, S1, M1, E2 and B2 Bytes
 Return alarm to the remote end
 MS_RDI (K2)
 MS_REI (M1)
Uplink Signal Flow
Frame synchronizer and RS overhead processor
 Set regenerator section overhead (RSOH) Bytes

 A1, A2, J0, E1, F1, D1-D3 and B1 Bytes
 Frame synchronizer and scrambler scrambles STM-N electrical signals
 E/O
Alarms & Performance of Low Order
Part
PDH Interface to Cross-connect Unit
Uplink signal Flow
G H I J K
Cross-connect HPA LPT LPA PPI PDH Interface
Unit
Downlink signal Flow
Part
Diagram of Alarm Generation
High Order Path Adaptation& Low Low Order Path Adaptation PDH Physical Interface
Order Path Termination
(HPA, LPT) (LPA) (PPI)
X E1_AIS All “1” T_ALOS

C E1
S LP_SLM Interface
V5
LP_UNEQ
V5
LP_TIM
J2 LP_TFIFO
V1,V2 TU_LOP
V1,V2 TU_AIS
HP_LOM
H4
LP_RDI
V5
X E1_AIS All “1”
C E1
S BIP 2 Interface
V5
LP_REI LP_RFIFO
Downlink signal flow Alarm report or return
Signal transfer point (Insert down all "1"s Alarm termination point (Report
signal) to SCC unit)
Alarms & Performance of Low Order Part
High Order Path Adaptation& Low Order Path Termination
 V1, V2 and V3 bytes detecting

 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
Alarms & Performance of Low Order Part
Low Order Path Adaptation& PDH Physical Interface
 Low Order Path Adaptation

 Recover data stream and the related clock reference signals
 Detect LP_RFIFO alarm
 PDH Physical Interface

 Forming a 2048 kbit/s signal
Part
Uplink Signal Flow
Low Order Path Adaptation& PDH Physical Interface
 Low Order Path Adaptation

 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
Part
Uplink Signal Flow
High Order Path Adaptation& Low Order Path
 Low Order Path Termination

 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)
 High Order Path Adaptation

 Adapt VC-12 into TU-12
 Map TU-12 into High order VC-4
Suppression Correlation between SDH
Alarms
 Suppression R_LOS
Relationship R_LOF
A1, A2 Bytes
R_OOF
RSOH, J0_MM MS_AIS B1_EXEC B2_EXEC MS_RDI
MSOH
(Except AU_AIS AU_LOP B1_SD B2_SD
A1,A2)
B3_EXEC HP_TIM HP_SLM HP_LOM HP_UNEQ HP_RDI
B3_SD TU_AIS TU_LOP BIP_EXEC
LP_UNEQ LP_TIM LP_SLM BIP_SD LP_RDI
A B A suppress B
More on Alarms
Alarm Understanding Rules
Rule 1
Alarms reported are alarms received

Alarm reported
FC 1
ex. a
ADM 1 ADM 2
Alarm reported
FC 1
ex. b
ADM 1 ADM 2
Rule 2
Alarms are reported on SDH Objects

Alarm Understanding Rules (…contd.)
Rule 3
3a. No Object => No Alarms reported

NO TU12
ex. (1-1-1)
FC on TU12 (1-1-1) Note:
ADM 1 ADM 2 These two
NO Alarm reported for FC examples are
on TU12 (1-1-1)
not possible
3b. Object Mismatch => No Alarms reported for AU object
WHY?
TU11
ex. (1-1-1) See slide 9
FC on TU12 (1-1-1)
ADM 1 ADM 2
NO Alarm reported for FC
on TU12 (1-1-1)
Rule 4
4a. No PT XC => No Alarms pass-through
NO VC4
ex. a
PT (1)
FC on AU4 (1)
ADM 1 NO Alarm pass-through ADM 2 ADM 3

Alarm reported for FC
on AU4 (1)
NO VC12
ex. b
PT (1-1-1)
FC on TU12 (1-1-1)
ADM 1 NO Alarm pass-through ADM 2 ADM 3

NO Alarm reported for
FC on TU12 (1-1-1)
4b. Bigger PT XC => No Alarms reported & Alarm pass-through
STM-1
ex. a VC4
links
FC on TU12 (1-1-1)
ADM 1 Alarm pass-through for ADM 2 ADM 3

FC on TU12 (1-1-1) NO Alarm reported
for FC on TU12 (1-1-1)
4c. Smaller PT XC => No Alarms reported (always ??) &

Alarm pass-through but on smaller object
STM-1
ex. b VC12
links
(1-1-1) FC on TU3 (1)
ADM 1 Alarm pass-through for ADM 2 ADM 3

FC on TU12 (1-1-1) NO Alarm reported
for FC on TU3 (1)
What ifwww.mapyourtech.com
44
Same size PT XC ?
Guide Lines
 Alarms reported are alarms received

 Object---- No Object
---- Object Mismatch
 Privilege of the NE
 Upstream / Downstream
RS Alarms
RS alarms are those, which can be reported even by a pure Regenerator

(who has privilege of opening (interpreting & rewriting) only RSOH)
LOS (Loss of Signal) RSOH bytes

based on whole RSOH
LOF (Loss of Frame)

A1 A2 J0
based on A1, A2 bytes
B1 E1 F1
TIM (Trace Identifier Mismatch)
based on J0 byte D1 D2 D3
SF (Signal Fail)
based on B1 byte
SD (Signal Degrade) Note: The order in which the alarms are written is important,
based on B1 byte as we will see later while discussing Alarm masking
Description of Alarms
LOS
Received power is less than Laser receiver sensitivity (All bits interpreted as ‘0’)
Tx off / misconnectivity Rx off / misconnectivity LOS
Fiber Cut
Tx Rx
ex.
Rx Tx
Received power is less than
Laser receiver sensitivity
ADM 1 (Low power transmitted, Span is longer than ADM 2
specified, Fiber gets deformed etc. etc.)
LOS clears when 2 consecutive framing patterns are received & no new LOS condition is detected
LOF
Anything other than “F6 28 (Hex)” in any (?) of the A1 A2 bytes (within a STM frame)
-- for consecutive 5 frames (625 µs)  OOF (Out of Frame)  clearing 2 frames
-- for consecutive 24 frames (3 ms)  LOF  clearing 24 frames
Note: Prolonged LOS => LOF, but not always LOF => LOS
47 (this fact will be used as one of the Alarm Masking logic later)
www.mapyourtech.com
Description of Alarms (…contd.)
TIM (J0)
Received J0 trace (1/16 byte(s)) != Expected J0 trace (1/16 byte(s))
Exp trace = A to B
P1 Rx trace = C to B
Tx trace = A to B P2
A Exp trace = C to B B Tx trace = C to B C

Rx trace = A to B
SF (B1/B2/B3/V5)
3 4 5
Equivalent BER exceeds alarm generation threshold ( 1 in 10 / 1 in 10 / 1 in 10 )
SD (B1/B2/B3/V5)
5 9
Equivalent BER exceeds alarm generation threshold ( 1 in 10 to 1 in 10 )
Note: For both SF & SD, alarm clearing threshold is 1 decade lower than generation
threshold, e.g., Gen. Thr. is 1 in 1000 or higher => Clg. Thr. is 1 in 10000 or lower
MS Alarms
MS alarms are those, which can be reported by a Add-Drop Multiplexer, irrespective of

cross-connect configuration
(who has privilege of opening (interpreting & rewriting) RSOH, MSOH, AU pointers plus
opening HOPOH(s) / TU Pointers / LOPOH(s) depending upon cross-connect configuration)
MSOH bytes
AIS (Alarm Indication Signal)
reported based on K2 byte -- bits 6,7,8
B2 K1 K2
SF (Signal Fail)
based on B2 bytes D4 D5 D6
SD (Signal Degrade) D7 D8 D9
based on B2 bytes
D10 D11 D12
RDI (Remote Defect Indication)
based on K2 byte -- bits 6,7,8 S1 M1 E2
Note 1: The order in which the alarms are written is important, we will see later while discussing Alarm masking
Note 2: MS-AIS is also called Line-AIS or AIS on STM port
49 MS-RDI is also called Line-RDI or RDI on STM port

www.mapyourtech.com
Description of Alarms (…contd.)
Example of generation of AIS, RDI

MS-AIS (Gen)
AU-AIS
TU-AIS (Gen)
Any traffic affecting LP
RS Alarm
HP Alarm or
orTU-AIS
MS-AIS
AU-AIS(Rx)
(Rx)
ADM
MS-RDI
HP-RDI
LP-RDI
Example of reception of TU-AIS, LP-RDI

TU-AIS (Rx)
Any traffic affecting RS/HP/LP Alarm
VC12 VC12 VC12

E1 E1
ADM 1 ADM 2 ADM 3
LP-RDI (Rx)
HP / LP Alarms
HP / LP alarms are those, which can be reported by a Add-Drop Multiplexer, having

HO / HO & LO object (LO object => LO cross-connect)
(who has privilege of “opening (interpreting & rewriting) RSOH, MSOH, AU Pointers plus
at least interpreting HOPOH(s)” / “opening (interpreting & rewriting) RSOH, MSOH, AU
Pointers, HOPOH(s), TU Pointers plus at least interpreting LOPOH(s)”
depending upon cross-connect configuration)
J1
H
HP-AIS reported based on H1, H2 bytes B3
H1, H2, H3 – AU O
Pointer bytes P
HP-LOP (Loss of Pointer) based on H1, H2 bytes C2 O
Note 1: Same as before HP-UNEQ (unequipped) based on C2 byte G1 H
Note 2: HP-Alarm is also
HP-TIM based on J1 byte F2 b
called AU-Alarm y
or Alarm on AU HP-SF based on B3 byte H4 t
e
LP-Alarm is also HP-SD based on B3 byte F3 s
called TU-Alarm K3
HP-RDI based on G1 byte -- bit 5
www.mapyourtech.com
51 or Alarm on TU N1
HP / LP Alarms (…contd.)
Note 1: Same as before

LP-AIS reported based on V1, V2 bytes
Note 2: Whole of this slide assumes
LP-LOP based on V1, V2 bytes TU2/TU12/TU11 for LP. If there
is TU3 with AU4 mapping, then
LOM (Loss of Multiframe) based on H4 byte – bits 7,8
also it is LP but Pointers & POH
HP-PLM / SLM (Payload / Signal Label Mismatch) bytes will be like HO
based on C2 byte
LP-UNEQ based on V5 byte – bits 5,6,7
LOPOH bytes LP-TIM based on J2 byte
V5 LP-SF based on V5 byte – bits 1,2

V1, V2, V3 – TU
Pointer bytes J2 LP-SD based on V5 byte – bits 1,2
N2 LP-RDI based on V5 byte -- bit 8
K4 LP-PLM / SLM based on V5 byte – bits 5,6,7

SONET/SDN Terminology Translation
SDH SONET
VC-11 (virtual container) VT-1.5 SPE
VC-12
VT-2 SPE
VC-2 VT-6 SPE
VC-3 STS-1 SPE
VC-4 STS-3c SPE
TU-11 (tributary unit) VT-1.5 (Virtual Tributary size 1.5)
TU-12 VT-2
TU-2 VT-6
TU-3 no SONET equivalent (like a 50 Mbit/s VT)
TUG-2 (TU group) VT Group
TUG-3 No SONET equivalent
AU-3 = VC-3 + Ptr STS-1 SPE + STS-1 Pointer
AU-4 = VC-4 + Ptr STS-3c SPE + STS-3c Pointer
AUG = 1 x AU-4, logical entity (not defined)
or 3 x AU-3s
STS-3
STM-1 = AUG + SOH
STS-3N
STM-N = N AUGs + SOH
Section Layer
Regenerator Section
Line Layer
Multiplex Section
53 www.mapyourtech.com 14
Alarm Propagation Examples
For every example,

 Assumption(s) is/are stated
 Root Cause(s) is/are stated
 Diagrammatic representation is made (OFCs are shown in cyan)
 Alarm(s) generated / condition(s) generated for reporting alarms is/are

shown in black
 Alarm(s) existing at a port is/are shown in red
 Alarm(s) masked at a port is/are covered with
 Alarm(s) reported at secondary supprressed alarm page is/are shown

in pink, italicised
 Note(s), whenever required is/are mentioned in green
www.mapyourtech.com
54
Alarm Propagation Examples (…contd.)
Example 1
Assumption: AU-4 Mapping on both ports Root Cause: NO XConnect on both ports
AU4 Signal Label Unequipped
HP-RDI
HP- UNEQ
HP-RDI
HP- UNEQ
A HP-RDI B
HP-RDI
Note: 1) if AU-3 mapping, then what happens?

2) In newer version of Tejas software, UNEQ is not reported for this root cause
Example 2
Assumption: AU-4 Mapping on both ports, Root Cause: NO XConnect on the port of B
HP-SLM default action is “report
SLM, no downstream AIS”
Signal Label TUG-structure

HP-RDI
LP-RDI
HP-RDI
HP-SLM
VC12
E1 HP- UNEQ
A TU-LOP B
Invalid TU Pointer value
Note: LP-RDI is not reported on B (See Rule 3a)

Example 3
Assumption: AU-4 Mapping on both ports of A & C
Root Cause: Fiber cut in the link from A to B
MS-AIS
AIS
AU-AIS
LOS TU-AIS
VC-12 VC-12
E1 MS-RDI E1
A HP-RDI B C
(Reg.)
LP-RDI MS-RDI
HP-RDI
LP-RDI
Note: The Reg. can not generate any RDI
Actually at C, AU-AIS & TU-AIS conditions are also received
Example 4
Assumption: AU-4 Mapping on all ports Root Cause: Fiber cut in the link from A to B
ADM B  VC-12 PT
MS-AIS
LOS TU AIS
VC-12 VC-12 VC-12

E1 MS-RDI LP RDI E1
A HP-RDI B C
LP RDI MS-RDI LP RDI
HP-RDI
Note: Only TU-AIS is reported on Node C (See Rule 4c)

LP-RDI on B is SSA
Example 5
Assumption: AU-4 Mapping on all ports Root Cause: Fiber cut in the link from A to B
ADM B  VC-4 PT
MS-AIS
AU AIS
LOS TU AIS
VC-12 VC-4 VC-12

E1 MS-RDI E1
A HP-RDI B C
LP RDI MS-RDI LP RDI
HP-RDI
Note: Only AU-AIS is reported on Node C (See Rule 4c)

LP-RDI on B is not reported (See Rule 3b)
Example 6
Assumption: AU-4 Mapping on all ports Root cause: NO XConnect on B, C & D for (1-1-2)
E1 (1) E1 (1)
VC-12 (1-1-1)
LP RDI (1-
1-2)
E1 VC-12 (1-1-2)
(2) TU-LOP (1-

1-2)
A B C D
Invalid TU Pointers (1-
1-2)
Note: Why E1(1) is shown?

LP-RDI is not reported on B (See Rule 3a)
www.mapyourtech.com
60
Example 7
Assumption: AU-4 Mapping on all ports Root cause: NO XConnect on C & D for (1-1-2)
E1 (1) E1 (1)
VC-12 (1-1-1)
LP RDI (1- LP RDI (1-

1-2) 1-2)
LP-RDI
(1-1-2)
E1 VC-12 (1-1-2) VC-12 (1-1-2)
(2) TU-AIS TU-LOP (1-

(1-1-2) 1-2)
A B C D
TU AIS (1-1-2) Invalid TU Pointers (1-
1-2)
Note: LP-RDI at node B is secondary suppressed
TU-AIS at node A is reported as terminating alarm
www.mapyourtech.com
61
Example 8
Assumption: AU-4 Mapping on all ports Root cause: NO XConnect on C for (1-1-2)
E1 (1) E1 (1)
VC-12 (1-1-1)
LP RDI (1- LP RDI (1- Invalid TU Pointers

1-2) 1-2) (1-1-2)
LP-RDI TU-LOP (1-
(1-1-2) 1-2)
E1 VC-12 (1-1-2) VC-12 (1-1-2) VC12(1-1-2) E1

(2) TU-AIS TU-LOP (1- (2)
(1-1-2) 1-2)
A B C D
TU AIS (1-1-2) Invalid TU Pointers (1- LP RDI (1-1-2)
1-2)
Note: K-L-M value need not remain same throughout a particular LP, alarms will
be reported accordingly on different objects
www.mapyourtech.com
62
Example 9
Assumption: AU-4 Mapping on all ports, Root cause: NO XConnect on C for (1-1-1)
VC4 PT at node B,
For each port, HP-SLM default action is “ignore SLM”
LP-RDI
(1-1-1)
VC-12(1-1-1)
VC-4 VC-12(1-1-2)
E1 (1) VC-12(1-1-2)
E1(2)
TU-LOP
E1 (2)
(1-1-1)
A B C
Invalid TU Pointers
(1-1-1)
Note: LP-RDI from A is not reported on B (See Rule 3b).
63 Why assumption on SLM?
www.mapyourtech.com
Example 10 (with SNCP)

Assumption: AU-4 Mapping on all ports Root cause: Fiber-cut in the link from A to B
W  A-B-C, P  A-D-C MS-AIS
LOS TU AIS
E1 VC-12 VC-12 VC-12 E1
MS-RDI LP RDI
HP-RDI LP RDI
A B C
LP RDI MS-RDI
HP-RDI
Note: SNCP is always

uni-directional & for VC-12
Tejas, it is 1+1
64 www.mapyourtech.com D
Alarms: Animated Description
SDH Alarms and Consequent Actions
SPI
LOS
RST
LOF RS-TIM RS-BIP
MST MSA
MS-AIS MS-EXC MS-DEG MS-RDI MS-REI MS-BIP AU-AIS AU-LOP
HPOM / HPT HPOM HPA
HP-TIM HP-EXC HP-DEG HP-RDI HP-REI HP-BIP HP- HP- HP- TU-AIS TU-LOP
UNEQ PLM LOM
LPOM / LPT LPOM LPA
LP-TIM LP-EXC LP-DEG LP-RDI LP-REI LP-BIP LP- LP-PLM

UNEQ
INTERRUPTION,
LOS
HW TROUBLE,
ATTENUATION
LOS AU/TU-AIS
NE LINE LINE NE
MS-RDI
TRIB
K2=XXXXX110
PDH-AIS
PDH
XXX = DETECTED XXX = SENT BACK
XXX = GENERATED XXX = MONITORED
AI = SIGNAL PASSED THROUGH

S
LOF
PROBLEM ON FRAME
A1,A2
ALIGNMENT WORD
LOF AU/TU-AIS
NE LINE LINE NE
MS-RDI
TRIB
K2=XXXXX110
PDH-AIS
XXX = DETECTED XXX = SENT BACK PDH


S
RS-TIM
RECEIVED REGENERATOR
SECTION TRACE JO
IDENTIFIER MISMATCH
RS-TIM AU/TU-AIS
NE LINE LINE NE
MS-RDI
TRIB
K2=XXXXX110
PDH-AIS


S
RS-BIP
NEAR END
ERRORED SIGNAL
B1
PERFORMANCE
COLLECTION
RS-BIP
NE LINE LINE NE
TRIB


S
MS-AIS
TROUBLE ON THE
RECEIVED SIGNAL K2=XXXXX111
(LOS, LOF, RS-TIM)
MS-AIS MS-AIS AU/TU-AIS
LINE LINE NE
MS-RDI
TRIB
K2=XXXXX110
PDH-AIS
PDH

S
MS-EXC
NEAR END
PERFORMANCE
EXCESSIVE BIT B2
ERROR RATE COLLECTION
( 1X10 E -3)
MS-EXC AU/TU-AIS
NE LINE LINE NE
MS-RDI
TRIB
K2=XXXXX110
PDH-AIS


S
MS-BIP
NEAR END
ERRORED SIGNAL B2
PERFORMANCE
COLLECTION
MS-BIP
NE LINE LINE NE
MS-REI
TRIB
M1


S
MS-RDI
TROUBLE ON THE K2=XXXXX110
RX SIDE
(LOS, LOF. RS-TIM,
MS-AIS, MS-EXC,
MS-RDI MS-RDI
NE LINE LINE NE
TRIB
PDH

S
MS-REI
FAR END
M1
PERFORMANCE
COLLECTION
MS-REI MS-REI
NE LINE LINE NE
TRIB
ERRORED SIGNAL

S
MS-DEG
NEAR END
PERFORMANCE
DEGRADATION
B2
(1X10 E -5    1X10 E -9 ) COLLECTION
MS-
DEG
NE LINE LINE NE
MS-REI
TRIB
M1


S
AU-AIS
TROUBLE ON THE
RX SIDE
(LOS, LOF, RS-TIM,
MS-AIS, MS-EXC,
AU-4 XC
AU/TU-AIS
AU-AIS AU-AIS
AIS
NE LINE LINE NE
HP-RDI
TRIB
G1 =XXXX100X
PDH-AIS
XXX = GENERATED XXX = MONITORED PDH

S
AU-LOP
TROUBLE ON THE
AU POINTER VALUE
(WRONG SETTING
SDH/SONET, DEG,
H1,H2
HW FAILURE)
AU/TU-AIS
AU-LOP
NE LINE LINE NE
HP-RDI
TRIB
G1 =XXXX100X
PDH-AIS

S
HP-UNEQ
AU-4 CHANNEL
NOT CONNETTED C2 = 00000000
HP-UNEQ
NE LINE LINE NE
TRIB

S
HP-TIM
RECEIVED HIGHER PATH TRACE
IDENTIFIER MISMATCH
J1
HP-TIM
NE LINE LINE NE
HP-RDI
TRIB HP-TIM
G1 =XXXX100X
PDH-AIS

140M
S
HP-BIP
ERRORED SIGNAL NEAR END
B3 PERFORMANCE
COLLECTION
HP-BIP
NE LINE LINE NE
HP-REI
TRIB
HP-BIP
G1 (1,2,3,4)

140M

S
HP-RDI
TROUBLE ON THE G1 =XXXX100X
RECEIVED HP
(AU-AIS, AU-LOP, HP-TIM,
HP-PLM, HP-EXC)
HP-RDI HP-RDI
NE LINE LINE NE
TRIB HP-RDI
PDH
XXX = DETECTED XXX = SENT BACK 140M

S
HP-REI
FAR END
G1 (1, 2, 3, 4) PERFORMANCE
COLLECTION
HP-REI
HP-REI
NE LINE LINE NE
TRIB HP-REI
ERRORED SIGNAL

140M

S
HP-DEG
DEGRADATION
NEAR END
(1X10 E -5    1X10 E -9 )
B3 PERFORMANCE
COLLECTION
HP-DEG
NE LINE LINE NE
HP-REI
TRIB
HP-DEG
G1 (1,2,3,4)

140M

S
HP-EXC
EXCESSIVE BIT NEAR END
ERROR RATE B3 PERFORMANCE
( 1X10 E -3)
COLLECTION
HP-EXC
NE LINE LINE NE
HP-RDI
TRIB
HP-EXC
G1 =XXXX100X

140M

S
HP-PLM
UNEXPECTED HIGHER
PATH PAYLOD LABEL
C2
HP-PLM TU-AIS
NE LINE LINE NE
HP-RDI
TRIB
G1 =XXXX100X
PDH-AIS

PDH

S
TU-AIS
TROUBLE ON THE
RX SIDE
(AU-AIS, AU-LOP,
HP-TIM, HP-PLM)
TU XC
TU-AIS TU-AIS
AIS
NE LINE LINE NE
LP-RDI
TRIB AIS
V5 = XXXXXXX1
PDH-AIS
PDH
1.5-2-34-45M

S
TU-LOP
TROUBLE ON THE
TU POINTER VALUE
(DEGRADATION, V1, V2
HW FAILURE)
TU-LOP TU-AIS
NE LINE LINE NE
LP-RDI
TRIB AIS
V5 = XXXXXXX1
PDH-AIS

PDH
1.5-2-34-45M
S
LP-TIM
RECEIVED LOWER PATH TRACE
IDENTIFIER MISMATCH
J2
LP-TIM
NE LINE LINE NE
LP-RDI
TRIB LP-TIM
V5 = XXXXXXX1
PDH-AIS

PDH
1.5-2-34-
45M
S
LP-BIP
ERRORED SIGNAL NEAR END
V5 (1, 2) PERFORMANCE
COLLECTION
LP-BIP
NE LINE LINE NE
LP-REI
TRIB
LP-BIP
V5 (3)
= DETECTED = SENT BACK PDH

XXX XXX
1.5-2-34-45M

S
LP-RDI
TROUBLE ON THE V5 = XXXXXXX1
RECEIVED LP
(TU-AIS, TU-LOP, LP-TIM,
LP-PLM, LP-EXC)
LP-RDI LP-RDI
NE LINE LINE NE
TRIB LP-RDI
PDH
XXX = DETECTED XXX = SENT BACK 1.5-2-34-45M

S
LP-REI
FAR END
V5 (3) PERFORMANCE
COLLECTION
LP-REI
LP-REI
NE LINE LINE NE
TRIB LP-REI
ERRORED SIGNAL

1.5-2-34-45M

S
LP-DEG
DEGRADATION
NEAR END
(1X10 E -5    1X10 E -9 )
V5 (1, 2) PERFORMANCE
COLLECTION
LP-DEG
NE LINE LINE NE
LP-REI
TRIB
LP-DEG
V5 (3)
= DETECTED = SENT BACK PDH

XXX XXX
1.5-2-34-45M

S
LP-EXC
EXCESSIVE BIT NEAR END
ERROR RATE V5 (1, 2) PERFORMANCE
( 1X10 E -3)
COLLECTION
LP-EXC
NE LINE LINE NE
LP-RDI
TRIB LP-EXC
V5 = XXXXXXX1
XXX = GENERATED XXX = MONITORED 1.5-2-34-45M

S
LP-PLM
UNEXPECTED LOWER
PATH PAYLOD LABEL
NE LINE LINE NE
LP-RDI
TRIB LP-PLM
V5 = XXXXXXX1
PDH-AIS

PDH
1.5-2-34-45M
S
LP-UNEQ
TU CHANNEL
NOT CONNETTED V5 (5, 6, 7) = 000
LP-UNEQ
NE LINE LINE NE
TRIB

S
HP-LOM
TROUBLE ON THE
MULTIFRAME ALIGNMENT
WORD H4
HP- TU-AIS
LOM
NE LINE LINE NE
LP-RDI
TRIB AIS
V5 = XXXXXXX1
PDH-AIS

PDH
1.5-2M
S

A1/A2
Regenerator Section
LOS
LOF
Multiplex Section
AIS
Higher Order Path Lower Order Path
J0 RS-TIM
RS-BIP Error indicator alarm sent upstream

B1
MS-AIS
K2 Alarm indicator sent upstream
MS-BIP
B2 Error/alarm detection
MS-REI
M1 AIS
MS-RDI
K2
AU-AIS
AIS
AU-LOP
HP-UNEQ
C2 HP-TIM
J1 HP-BIP
B3 HP-REI AIS
G1 HP-RDI
G1 TU-AIS
TU-LOP
AIS
TU-LOM
HP-PLM
H4
LP-UNEQ
C2
LP-TIM
V5 AIS
LP-BIP
J2
LP-REI
V5
LP-RDI
V5
LP-PLM
V5
V5
98 www.mapyourtech.com AIS
Performance Monitoring
Overhead Termination
STM-n Unit or STM-n Unit or

2M, 34M Unit 140M Unit STM-n Unit STM-n Unit 140M Unit 2M, 34M Unit
LPT HPT MST RST RST MST HPT LPT

RSOH
MSOH
VC-4 POH
VC-12, VC-3 POH
LPT: Lower-order Path termination MST: Multiplex Section Termination

HPT: High-order Path termination RST: Regenerator Section Termination
www.mapyourtech.com 100
Overhead Termination
STM-N unit TSI unit 2M or 34M unit
Crossconnect
Level
STM-N RST MST HPT VC-12 or VC-3
LPT 2M or 34M
STM-N unit TSI unit 140M unit

Crossconnect
Level
STM-N RST MST VC-4
HPT 140M
STM-N unit TSI unit STM-N unit

Crossconnect
Level
STM-N RST MST HPT VC-12 or VC-3
HPT MST RST STM-N
STM-N unit TSI unit STM-N unit

Crossconnect
Level
STM-N RST MST VC-4
MST RST STM-N
Performance Monitoring Point
• Physical Layer
• Section Layer
• Adaptation
• High/Low-order Path Termination
-Physical Layer-
• Optical Interface
LDBC : Laser Diode Bias Current
• PDH Interface
CV-L : Code Rule Violation
ES-L : Errored Second
SES-L : Severely Errored Second
• External Clock Interface
CV-＊ : Code Rule Violation
ES-＊ : Errored Second)
SES-＊ : Severely Errored Second
＊ : L or P
-Section Layer-
• Regenerator (RS) and Multiplex (MS) Section

ES-＊＊ : Errored Second
SES-＊＊ : Severely Errored Seconds
BBE-＊＊ : Background Block Error
UAS-＊＊ : Unavailable Seconds
OFS-＊＊ : Out of Frame Seconds (OOF)
• Multiplex Section Far-end
ES-MSFE : Errored Second
SES-MSFE : Severely Errored Seconds
BBE-MSFE : Background Block Error
UAS-MSFE : Unavailable Seconds
• Multiplex Section
PSC : Protection Switching Count
PSD : Protection Switching Duration
＊＊ : RS or MS
-Adaptation-
• AU-4 Pointer
PJE (positive) : Pointer Justification Event (positive)
PJE (negative) : Pointer Justification Event (negative)
-Path Termination-
• High/Low-order Path (receiving direction)

ES-＊＊ : Errored Second
SES-＊＊ : Severely Errored Seconds
BBE-＊＊ : Background Block Error
UAS-＊＊ : Unavailable Seconds
• High/Low-order Path (transmitting direction)
ES-＊＊FE : Errored Second
SES-＊＊FE : Severely Errored Seconds
BBE-＊＊FE : Background Block Error
UAS-＊＊FE : Unavailable Seconds
＊＊ : HO or LO
Terms and Definitions
(used by error performance)
EDC : Error Detection Code

Block : block
EB : Errored Block
Defect : defect
ES : Errored Second
SES : Severely Errored Second
BBE : Background Block Error
CV : Code Violation
UAS : Unavailable Second
BIP-8 of VC-4
1 2 3 26 1 1 1 2 3 4 5 6 7 8
26 2 26 3 2 1 2 3 4 5 6 7 8
Gro up o f 8 bits
BIP-8 check sequence
VC-4
23 4 8 1 2 3 4 5 6 7 8
234 8 23 4 9 23 4 9 1 2 3 4 5 6 7 8
B lo c k ( 1 8 7 9 2 b i t s / b l o c k ) B3

Block : block
EB : Errored Block
Defect : defect
ES : Errored Second
CV : Code Violation

Block : block
EB : Errored Block
Defect : defect
ES : Errored Second
CV : Code Violation
Generation and Detection of SDH
Performance
Bit Error Generation Mechanism
Mechanism: Bit interleaved parity (BIP)

Transmit end: The result of BIP is placed in the relevant bytes of the
next frame
Receive end: Compare the result of BIP with the bytes of the 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
Notice: The Sequence of descramble& BIP

Generation and Detection of SDH Performance
Error Detection and Report
LPT HPT MST RST RST MST HPT LPT
B1
B2
B3
V5
Errors occurring in Low order path will not be detected in High order
path, High order bit errors will trigger Low order errors.
Terms
Term Description
BE Errored block, in which one or more bits are in error.
Background block error, it is an errored block occurring outside of the period
BBE
of UAT and SES.
FEBBE 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
ES
detected.
FEES 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
SES 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.
Terms
Term Description
Far end severely errored second, in which an SES event detected at the
FESES
remote end.
Consecutive severely errored second, in which the SES events

CSES
consecutively occur, but last less than 10 seconds.
Far end consecutive severely errored second, in which a CSES event

FECSES
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
UAS
transmission directions of a transmission system is inferior to 10-3 . These
ten seconds are considered to be part of unavailable time.
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
Administrative unit pointer (AU_PTR)

Tributary unit pointer (TU_PTR)
Generation Mechanism of AU Pointer Justification
 Locatio
9
n:
H1 Y Y H2 F F H3 H3 H3 VC4
1 9
row
 Causation: 10………270 Column
− Network is out of synchronization
 Pointer justification state:

Byte numbering and content of the fourth row in STM-1
Name frame Rate relation
7 8 9 10 11 12
Zero H3 H3 H3 Info Info Info Information = container
Positive H3 H3 H3 Stuffing Stuffing Stuffing Information< container
Negative Info Info Info Info Info Info Information> container
Generation Mechanism of TU Pointer Justification
 Causation:
− Transformed from AU pointer justification
− The system clock is not consistent with the received clock
− Pointer justification occurs at the upstream NE where the service
passes
Detection and Reporting of Pointer Justification
Remote detection:
Occur at the local station, report at the remote station
Local detection:
Generate at the local station, report locally
Relationship between Alarms and Performance
 Relationship
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 Performance Event Alarm Event
Local end Remote end Local end Remote end
RS RSBBE - B1_OVER -
MS MSBBE MSFEBBE B2_OVER MS_REI
HP HPBBE HPFEBBE B3_OVER HP_REI
LP LPBBE LPFEBBE BIP_OVER LP_REI
Relation between ES, SES and BBE
ES
SES
Blocks in 1sec. period
30 %
1 sec. nonEB } EB BBE

Block : block
EB : Errored Block
Defect : defect
ES : Errored Second
CV : Code Violation
Unavailable Second
10 sec. < 10 sec. 10 sec.
Unavailability detected Availability detected
Unavailable period Available period
Severely errored second Errored second

Error-free second
SES ES
Storage of PM data
15 minute accumulation
TCA (Threshold Crossing Alert)
32 periods with zero suppression

(32) (2) (1)
15 min.
Current 15 min.
hh : 15n hh : 15(n+1)
data update : every 1 min.
Zero Suppression
past time future
1 day accumulation item a 0 * 0 0 0 0 0
item b * 0 0 0 0 △ 0
TCA (Threshold Crossing Alert) item x
* * 0 0 0 0 *
item y 0 0 0 0 0 0 *
(Yesterday)
Zero Suppression
PM items of one facility
1 day
0 : 00 0 : 00 item a 0 * 0 0 0
Current 1 day (Today) item b * 0 0 △ 0
data update : every 1 min. item x
* * 0 0 *
item y 0 0 0 0 *
old memory new
all zero data with time stamp of △ occurrence
Bit error defects family
 EXC = EXCessively errored signal
 DEG = DEGraded signal
 CMI = Code Mark Inversion
 All members of the [large] family of bit error defects have a common origin
 errors in the transmission/reception of a signal.
 SDH calculates a parity check and places the results in the overhead.
 Occurs in both Tx and Rx. A difference indicates a bit error in transmission/reception
 Another detection mechanism is for electrical signals
 An invalid sequence is a code violation
 PPI-EXC and ES-CMI defect originate from code violations.
 SDH paths and sections may have EXC and DEG defects [Different degrees of errors]
 EXC represent an ‘EXCessive’ number of bit errors – the signal is so badly errored as to be unusable
EXC defects represent a bit error ratio of 10-3 or 10-4.
EXC results in a protection switch at the closure point of a sub-network connection and may be configured
to insert AIS and RDI.
 DEG defects represent a bit error ratio of 10-5 or less
 DEG does not result in a protection switch or raising of any consequent action.
What is Performance Monitoring
 Performance monitoring is used to measure Traffic Quality

 How? – By counting anomalies and defects.
 Why are they needed?

 To diagnose faults in a network OR detect occurrence of dribbling errors.
 Measure a networks performance and its service capability.
 At the edge of the network
 Within the network
 Check service level agreements for end customers and find out whether they have been
satisfied or breached.
 Reporting performance monitoring

 NE collects and logs PMs continuously for all connections.
 EC-1 collects PMs from all NEs in span of control.
 INM collects PMs from the complete network.
Performance Monitoring Points
 Performance Monitoring Points [PMPs]
 are points at which software collects performance monitoring [PM] data. The PM data
is a measure of the quality of the transmission path at that point.
LP_NE V5, B3 TU_PJE

LP_FE V5, G1
PDH
Vc-12 End User
PDH
End User
Vc-12
PPI_CV HP_FE G1
Vc-4 Vc-4 HP_NE B3
AU_PJE
NE1
RS-OOF A1, A2 MS_NE B2 NE2
STM-N
RS-NE B1 MS_FE M1
Optical Link via Network
Table of PM points
 PMs count will occur at the same points as where alarms will occur
 FE[Far End] PMs are associated with the RDI defect category.
 The destination you are sending to has received your signal in a defective state.
PMP-Type Byte Defects

RS-OOF A1, A2
RS-NE B1 RS-LOS, RS-LOF
MS_NE B2 All RS defects, MS-AIS, MS-EXC
MS_FE M1 MS-RDI
AU_PJE N/A N/A
HP_NE, HPOM_NE B3 All RS, MS defects, AU-AIS, AU-LOP, HP-LOM, HP-TIM, HP-PLM, HP-EXC
HP_FE, HPOM_FE G1 HP-RDI
TU_PJE N/A N/A
LP_FE G1[VC-3] HP-RDI, LP-RDI
LPOM_FE V5(b3[VC-12]
LP_NE B3[VC-3] All RS, MS, AU, HP defects, TU-AIS, TU-LOP, LP-TIM, LP-PLM, LP-EXC,
INT-LO-BUFFER
LPOM_NE V5(b1-b2[VC-12]
ES-CV N/A ES-LOS
PPI-CV N/A PPI-LOS
BIP Errors vs Block Errors
 B1 is an 8 bit parity byte, calculated across the complete SDH frame [2430
bytes for an STM-1 signal].
 B1 byte is generated/terminated at every NE.
 ANSI specifies BIP
 ETSI/ITU specifies Block Errors
 The B1 Byte is treated as 1 block
 The B1 Byte is treated as BIP-8 [since it has 8 bits]
Example
Transmitted Received
0 1 0 1 0 1 0 1 0 1 1 1 0 1 0 1 = 1 Block Error, = 1 BIP Error
0 1 1 1 0 0 0 1 = 1 Block Error, = 2 BIP Errors

= Bit Error
Definition of BBE, ES, SES, UAS
 Background Block Error [BBE]
 A Background Block Error [BBE] is a single errored Block in the SDH frame, not occurring
as part of an SES or a UAS.
 Errored Second [ES]
 An Errored Second [ES] is a second during which at least one anomaly or one defect
occurs, but not occurring as part of a UAS.
 Severely Errored Second [SES]
 A Severely Errored Second [SES] is a second during which at least ‘X’ anomalies or one
defect occurs, but not occurring as part of a UAS. By definition an SES is always an ES.
 Unavailable Second [UAS]
 An Unavailable Second is a second during which the signal is unavailable. It becomes
unavailable at the onset of 10 consecutive seconds that qualify as SES, and continue to be
unavailable until the onset of 10 consecutive seconds that do not qualify as SES.
How to interrupt SES and UAS
 The difference between SES and UAS is conceptually difficult to understand.
 Therefore it is better clarified through the use of a diagram.
 Unavailable periods/detection and available periods/detection are indicated.
<10secs 10secs <10secs 10secs
Unavailability Availability
Detected Detected
Available Period Unavailable Period Available Period
= SES = Non SES
Processing of B1 byte
 This can be broken down into activities performed in hardware and software.
15-minute
BBE, ES, SES, UAS
15-Minute PM Counts
TIME BBE ES SES UAS

Calculate B1 00:00 3 3 1 0
00:15 5 4 0 0
block errors 00:30 1 1 0 0
15-Minute
Frame B1
SDH Frame Filter
errors
1- Second 1- second
BBE, ES, SES, UAS
Filter
SDH Frame Frame RS 24-Hour Filter

defects, LOS,
LOF
24-Hour PM Counts
Determine RS
BBE ES SES UAS
defects 40 33 0 0
34 16 20 20
24-hour 21 4 2 0
130 www.mapyourtech.com BBE, ES, SES, UAS
Calculating B1 block errors.
 The calculation of B1 block errors occurs in hardware.
 Conceptually this can be understood via a diagram.
Frame X Frame X+1 Frame X+2

}
Actual B1 byte
Calculate
expected B1
byte
Compare
B1 errors
Expected B1 byte actual with
www.mapyourtech.com
expected B1
131
byte
1- Second Filter
1-Second Filter
Frame B1 errors
B1 Errors (x) BBE ES SES UAS
x = 0 0 0 0 0
1- second 0 < x < 2400 x 1 0 0
BBE, ES, SES, UAS x >= 2400 (< 10 secs) 0 1 1 0
1-Second
x >= 2400 (> 10 secs) 0 0 0 1
filter
Defects BBE ES SES UAS

No Defects 0 0 0 0
Frame RS defect, LOS, LOF (< 10 secs) 0 1 1 0
LOS, LOF LOS, LOF (> 10 secs) 0 0 0 1
SDH Frame B1 Errors/Defects
DATE TIME FRAME

B1 Errors Defects
}
01/01/2000 00:00:00 0001 0 -
01/01/2000 00:00:00 0002 0 -
01/01/2000 00:00:00 0003 1 -
1-Second PM Counts
“ “ “ . .
“ “ “ . .
DATE TIME BBE ES SES UAS
“ “ “ . .
01/01/2000 00:00:00 1 1 0 0
01/01/2000 00:00:00 7998 0 -
01/01/2000 00:00:01 x x x x
01/01/2000 00:00:00 7999 0 -
01/01/2000 00:00:02 x x x x
01/01/2000 00:00:00 8000 0 -
----
TOTAL B1 Errors (x) = 0001
15-Minute Filter
1- second 15-Minute
BBE, ES, SES, UAS BBE, ES, SES, UAS
15-Minute
Filter
1-Second PM Counts
15-Minute PM Counts
DATE TIME BBE ES SES UAS
01/01/2000 00:00:00 1 1 0 0 DATE TIME BBE ES SES UAS
}
01/01/2000 00:00:01 0 0 0 0 01/01/2000 00:00 3 3 1 0
01/01/2000 00:00:02 0 1 1 0 01/01/2000 00:15 x x x x
“ “ . . . . 01/01/2000 00:30 x x x x
“ “ . . . .
“ “ . . . .
01/01/2000 00:14:57 2 1 0 0
01/01/2000 00:14:58 0 0 0 0
01/01/2000 00:14:59 0 0 0 0
24 Hour Filter
1- second 24-Hour
BBE, ES, SES, UAS BBE, ES, SES, UAS
24-Hour
Filter
1-Second PM Counts
DATE TIME BBE ES SES UAS 24-Hour PM Counts

01/01/2000 00:00:00 1 1 0 0
DATE BBE ES SES UAS
}
01/01/2000 00:00:01 0 0 0 0
01/01/2000 00:00:02 0 1 1 0 01/01/2000 40 33 3 0
“ “ 30 . . . 02/01/2000 x x x x
“ “ . 30 1 . 03/01/2000 x x x x
“ “ 4 . . . “ . . . .
01/01/2000 23:59:57 0 0 1 0 “ . . . .
01/01/2000 23:59:58 5 1 0 0 “ . . . .
01/01/2000 23:59:59 0 0 0 0
Accumulation of PMs over time
TIME B1 Errors Defects B1 errors

1 5 - BBE= 5 ES= 1 SES= UAS= 5000 > 2400 [<10 secs]
2 50 - BBE= 50 ES= 1 SES= UAS=
3 500 - BBE= 500 ES= 1 SES= UAS=
4 5000 - BBE= ES= 1 SES= 1 UAS=
5 0 LOS BBE= ES= 1 SES= 1 UAS=
Defects
8 4000 LOS BBE= ES= 1 SES= 1 UAS= LOS, LOF (< 10 secs)
2 Seconds 9 2500 LOF BBE= ES= 1 SES= 1 UAS=
that qualify 10 2700 - BBE= ES= 1 SES= 1 UAS=
as SES 11 3000 - BBE= ES= 1 SES= 1 UAS= Unavailability
12 4000 - BBE= ES= 1 SES= 1 UAS=
13 5000 - BBE= ES= 1 SES= 1 UAS= Detected
14 6000 - BBE= ES= SES= UAS= 1
15 7000 - BBE= ES= SES= UAS= 1 B1 errors
16 0 - BBE= ES= SES= UAS= 1 X > 2400 [>10 secs]
17 50 - BBE= ES= SES= UAS= 1 AND / OR
18 0 - BBE= ES= SES= UAS= 1
19 100 - BBE= ES= SES= UAS= 1
Defects
20 0 - BBE= ES= SES= UAS= 1 LOS, LOF [>10secs]
21 30 - BBE= ES= SES= UAS= 1
22 0 - BBE= ES= SES= UAS= 1 Unavailable
23 35 - BBE= ES= SES= UAS= 1 Period
10 Second 26 0 - BBE= ES= SES= UAS= Availability
27 40 - BBE= 40 ES= 1 SES= UAS=
Period Detected
28 0 LOF BBE= ES= 1 SES= 1 UAS=
29 0 - BBE= ES= SES= UAS= B1 errors
X < 2400 [>10secs]
TOTAL BBE= 595 ES= 15 SES= 11 UAS= 12 AND / OR
135 www.mapyourtech.com Defects
No Defects [>10secs]
FAQs
Question and Answers
 What is the difference between an anomaly and a defect?
 Anomaly is a single occurrence of, or commencement of a condition
 Defect is a persistent or repeated occurrence of an anomaly
 What is the main difference between a POM alarm and a LO or HO alarm?
 LPs / HPs are present on termination
 POMs are present when traffic is un-terminated
 What is the main principle behind masking?
 Present alarm closet to source
 Reduce the amount of fault analysis and alarm presentation
 A car fail alarm is raised on a PIU, What should you do?
 This alarm needs to be cleared first because it will mask all other alarms raised on the card/slot
instance
 What is the difference between a regenerator and a multiplexer?
 Regenerator terminates the RSOH, MSOH + payload continue, regenerator generates new OH
 Multiplexer fulfils the same function of a regenerator and also terminates / generates a MSOH
 What alarms does the Multiplex Section Termination give?
 Provides pointer processing and gives AU alarms
 Where are the Low Path Termination points?
 On PDH tributaries
 If an unprotected limb has two POMs present which one is active the Rx or the Tx?
 Rx is active
 In a protected connection is a limb has a HPT or LPT present can HPOM/LPOM also be
active?
 Yes
 Which bytes are responsible for the reporting of a LOF alarm, what section overhead are
they found?
 A1 and A2 –In RSOH
 Where is AIS reported in relation to a defect?
 AIS is reported downstream from a defect, a user would look upstream to resolve the
issue
 Why is there no RS-AIS alarm?
 Possibly redundancy [Like the TIM alarms which only has RS-TIM]
 Could also be that RS alarms on regenerators are passive and operate as a pass through.
Multiplexers drop traffic and are better therefore to address issue
 How many consequent actions are there and what are they?
 AIS, RDI/REI and protection switches
 Which alarm is more serious, RDI or REI?
 RDI is more serious
 What type of cards produce CMI alarms?
 Electrical cards [comes from Code Mark Inversion line coding]
 What consequent actions does a DEG alarm produce?
 It doesn’t
 What type of payload would you expect on the raising of a UNEQ alarm?
 0
 What bytes carry PM information and where are they calculated?
 B1, B2 and B3. Calculated in hardware
References
• Various presentation collected from Internet {Huawei,Tejas,Nortel & Marconi) available free of cost
• www.mapyourtech.com
• www.google.com
For further queries do reach on www.mapyourtech.com
Thank You!

Sdh/Sonet: Alarms & Performance Monitoring

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sdh/Sonet: Alarms & Performance Monitoring

Uploaded by

Copyright:

Available Formats

SDH/SONET

ALARMS & PERFORMANCE MONITORING

Bell Communications Research (Bellcore, BCR)

Z0 Spare. Reserved for future international standardisation.

B1 – Is not supported in OM4000 NE’s due to redundancy and

S1 Synchronisation status messages. S1 [b5-b8] indicates which of the four levels of

MSP Protocol Bytes K1 [b1-4] – SDH Frame

 A defect type (e.g. LP-EXC) has two parts:

 If a defect is subject to correlation

HP-TIM HP-PLM HP-UNEQ B

• Plug In Unit [PIU] related defects

Card Fail Card Fault Wrong Card Unexpected Card

Alarm raised on the card/slot instance

PPI LOS PPI UNEXP SGNL

= ‘A masks B’ PPI EXC

QECC COMMS FAIL RS TIM MS RDI

INT HP OP BUFF HP DEG HP LOM HP TIM HP PLM HP UNEQ HP RDI

PPI LOF HP REI

= "A masks B if B's TU

INT LP OP BUFFER LP DEG LP TIM LP PLM LP UNEQ LP RDI

Low Order Path

High Order Path

Section Section Section Section

STS Path STS Path

High order part

Uplink signal flow

RDI (Remote Defect Indication)

Uplink signal Flow

STM-N SPI RST MST MSP MSA HPT Cross-connect

Downlink signal Flow

Downlink signal flow Alarm report or return

 K1 and K2 bytes detecting

 H1 and H2 bytes detecting

 J1, C2, B3 and G1 bytes detecting

 Generates N High order path overhead bytes

 Return alarm to the remote end

 AU-4 pointers generating

 Set multiplex section overhead (MSOH) Bytes

 K1, K2, D4-D12, S1, M1, E2 and B2 Bytes

 Return alarm to the remote end

Frame synchronizer and RS overhead processor

 Set regenerator section overhead (RSOH) Bytes

Uplink signal Flow

Downlink signal Flow

X E1_AIS All “1” T_ALOS

Downlink signal flow Alarm report or return

 V1, V2 and V3 bytes detecting

Low Order Path Adaptation& PDH Physical Interface

 Low Order Path Adaptation

 PDH Physical Interface

Low Order Path Adaptation& PDH Physical Interface

 Low Order Path Adaptation

 PDH Physical Interface

High Order Path Adaptation& Low Order Path

 Low Order Path Termination

 High Order Path Adaptation

RSOH, J0_MM MS_AIS B1_EXEC B2_EXEC MS_RDI

B3_EXEC HP_TIM HP_SLM HP_LOM HP_UNEQ HP_RDI

B3_SD TU_AIS TU_LOP BIP_EXEC

LP_UNEQ LP_TIM LP_SLM BIP_SD LP_RDI

Alarms reported are alarms received

Alarms are reported on SDH Objects

3a. No Object => No Alarms reported