Sie sind auf Seite 1von 20

Traffic Protection

 Traffic protection is a mechanism to


enhance the dependability of a transport
service.
 OME6500 supports line level traffic
protection and restoration schemes.
 OME6500 Release 1.2 also supports
UPSR/SNCP path level protection
BLSR Configuration
 A 2-Fiber bidirectional line-switched ring
(BLSR)/multiplex section shared protection ring
(MS-SPRing) is a ring network of nodes
interconnected by a pair of optical fibers.

 BLSR/MS-SPRing traffic protection provides 100%


restoration of restorable traffic for single failures by
reserving 50% of the ring’s capacity for protection.
As a result, a 2-Fiber OC-48/STM-16 or OC-
192/STM-64 ring effectively has a span capacity of
STS-24/STM-8 and STS-96/STM-32 respectively.
Provisioning a 2-Fiber BLSR/MS-SPRing
traffic protection……

 Protection group provisioning


 Ring map provisioning
 Cross-connect provisioning
 RTRV-FFP-OC192:[tid]:aid[,protAid]:ctag;

 ENT-FFP-
OC192:[tid]:workAid,protAid:ctag:::[PSDIRN=Domain][,PS=Domain]
[,WR=Domain][,RVRTV=Domain][,REMSTANDARD=Domain][,RD=Domain
];

 RTRV-BLSRMAP:[tid]:oddaid,evenaid:ctag;

 ENT-BLSRMAP:[tid]:oddaid,evenaid:ctag::Map[:LABEL=Domain];

 ED-BLSRMAP-LABEL:[tid]:oddaid,evenaid:ctag:::LABEL=Domain;

 RTRV-PROTNSW-OC192:[tid]:aid:ctag;
Protection TL1 Commands
 User Commands:
 Set up FFP
 ENT-FFP-OC48
 ED-FFP-OC48 (use this to modify WTR time)
 DLT-FFP-OC48

 User initiated switch (manual, forced, LOW, LOP)


 OPR-PROTNSW-OC48
 RLS-PROTNSW-OC48
 Ex: OPR-PROTNSW-OC192:[tid]:aid:ctag::[sc];
 Exerciser
 EX-SW-OC48 (will be run on both optics successively)
 ALW-OC48
 INH-EX-OC48
BLSR Ring protection
APS K-Byte (K1, K2)

 BLSR uses APS protocols (K1/K2 of the


SONET/SDH section overhead) to initiate
and signal automatic or user protection
switch requests to the appropriate nodes on
the ring.

 Bytes K1 and K2 in the Line Overhead of


the first STS-1 signal are used to carry the
protocol that coordinates the protection
switching.
APS bytes (K1, K2) – ring protection
K1 Byte K2 Byte

1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8

Switch Destination Source Status


Preemption Node ID Node ID 111 Line AIS
Priority 110 Line RDI
101 reserved
1111 Lockout of Protection 100 reserved
1110 Forced Switch - Span 011 Extra Traffic
1101 Forced Switch - Ring 010 Bridged and Switched Status
1100 Signal Fail - Span 001 Bridged Status
1011 Signal Fail - Ring 000 Idle
1010 Signal Degrade - Protection
1001 Signal Degrade - Span 0 Short Path Code
1000 Signal Degrade - Ring 1 Long Path Code
0111 Manual Switch - Span
0110 Manual Switch - Ring
0101 Wait-to-Restore
0100 Exercisor - Span
0011 Exercisor - Ring
0010 Reverse Request - Span
0001 Reverse Request - Ring
0000 No Request
BLSR/MS-SPRing protection switch
criteria

 BLSR switching is 1:1 revertive.


 BLSR/MS-SPRing protection switch
requests can occur automatically by the
system or by user initiated actions.
 Automatic switch
 User-initiated switches
 Manual switch
 Forced switch
 Lockout of Working
 Lockout of Protection
BLSR/MS-SPRing protection Switching
Priority
Wait to Restore (WTR)

 System must remain stable (good signal on


working channel) for the duration of WTR
time before protection channels will revert
back to working channels
 WTR is 2nd lowest in Protection hierarchy
(all user-initiated and auto switches will
override WTR)
BLSR Ring Switching

 Ring switching Ring switching reroutes


traffic away from the point of failure.
 A ring switch occurs when:
- an entire node fails
- one optical fiber fails
- or a user makes a request
Protection Switch Example:
STS #1

1 2

• Traffic is added and


dropped at NEs #1 and
#4
• STS #1 is carrying
traffic

3 4
Prot Switch Exp: (Cont’d)
(1)
Unidirectional X STS #1

Fiber Break 1 2 (2)


(3) LOS
SF-R, SRC=2,
DST=1, Short, RDI

SF-R, SRC=2,
• (1) Fiber is cut from NE DST=1, Long, Idle
#1 to NE #2
• (2) NE #2 detects a line (3)
condition (LOS)
• (3) NE #2 transmits a
bridge request for
Signal Fail - Ring (SF-
R) to NE #1 via K-bytes
on both short and long
path (4)
• (4) NEs #4 & #3 receive (4)
this request and enter 3 4
bi-directional full pass- Bi-directional Bi-directional
Full Pass-thru Full Pass-thru
thru mode
• Stop sending Uneq,
pass traffic through
Prot Switch Exp: (Cont’d)
Responding to X STS #1

Bridge 1 2
Request SF-R, SRC=2,
(5) DST=1, Short, RDI

RR-R, SRC=1,
(6) DST=2, Short, Idle SF-R, SRC=2,
• (5) NE #1 receives SF-R DST=1, Long, Idle
on short path SF-R, SRC=1,
DST=2, Long, Idle
• (6) Replies with Reverse
(7)
Request (RR-R) on
short path
• (7) Also sends SF-R on
long path

3 4
Bi-directional Bi-directional
Full Pass-thru Full Pass-thru
Prot Switch Exp: (Cont’d)
Bridging traffic X STS #1

1 2
• (8) NE #1 receives SF-R SF-R, SRC=2,
on long path DST=1, Short, RDI

• (9) Bridges traffic to RR-R, SRC=1,


STS #25-48 on long path DST=2, Short, Idle SF-R, SRC=2,
• (10) Sends new K-byte (8) DST=1, Long, Br

message to NE #2 via SF-R, SRC=1,


DST=2, Long, Br
(13)
(11)
long path indicating
traffic is bridged (SF-R, (10)
(9) (12)
state = Br)
STS STS
• (11) NE #2 receives SF- #25 #25
R on long path
• (12) Bridges traffic to
STS #25-48 on long path
• (13) Sends new K-byte SF-R, SRC=1,
message to NE #1 via 3 DST=2, Long, Idle
4
long path indicating
Bi-directional Bi-directional
traffic is bridged (SF-R, Full Pass-thru
SF-R, SRC=2,
Full Pass-thru
DST=1, Long, Idle
state = Br)
Prot Switch Exp: (Cont’d)
Switching Traffic X STS #1

1 2
• (14) NE #1 receives (15) (18)
SF-R, SRC=2,
Bridged status on long DST=1, Short, RDI
path
• (15) Switches traffic to RR-R, SRC=1,
DST=2, Short, Idle SF-R, SRC=2,
listen to STS #25-48 on (14) DST=1, Long, Br&Sw
long path SF-R, SRC=1,
(17) (19)
• (16) Sends new K-byte DST=2, Long, Br&Sw

message to NE #2 via (16)


long path indicating
traffic is switched (SF- STS
R, state = Br&Sw) #25
• (17) NE #2 receives
Bridged status on long
path
• (18) Switches traffic to SF-R, SRC=1,
DST=2, Long, Br
listen to STS #25-48 on 3 4
long path Bi-directional
SF-R, SRC=2,
Bi-directional
Full Pass-thru Full Pass-thru
• (19) Sends new K-byte DST=1, Long, Br

message to NE #1 via
long path indicating
traffic is switched (SF-
R, state = Br&Sw)
Prot Switch Exp: (Cont’d)
Final State X STS #1

1 2
SF-R, SRC=2,
DST=1, Short, RDI

RR-R, SRC=1,
DST=2, Short, Idle SF-R, SRC=2,
• (20) NE #1 sending K- DST=1, Long, Br&Sw
byte message to NE #2 SF-R, SRC=1, (21)
via long path indicating DST=2, Long, Br&Sw

traffic is switched (SF- (20)


R, state = Br&Sw)
• (21) NE #2 sending K- STS
byte message to NE #1 #25
via long path indicating
traffic is switched (SF-
R, state = Br&Sw)
3 4
Bi-directional Bi-directional
Full Pass-thru Full Pass-thru
BLSR Node Isolation
Squelching Example:
Node Isolation. X
• Starting with the final AIS-P on
Chan 25
switch state of the previous
example. 1 2
• (1) Cause a second failure
between NE #1 and NE# 3.
• (2) NE #1 detects LOS (SF)
and send a Short request
SF-R to NE #3 (NE#1 now
X RR-R, SRC=1,
DST=2, Short, Idle
SF-R, SRC=2,
DST=1, Short, RDI

SF-R, SRC=2,
DST=1, Long, Br&Sw

drops its switches – Idle) SF-R, SRC=1,


(3) STS #1
(1)
• (3) NE #2 and NE#3 both X DST=3, Short, Idle
STS
receive switch requests on (2) #25
the long path with different STS
STS
Source APSIDs. Using the #25
#25
Ring Map they determine AIS-P on
what node(s) is isolated and Chan 25
squelch the appropriate
traffic (based on connection (3)
provisioning using A and Z 3 SF-R, SRC=3, 4
DST=1, Long, Br&Sw
End APSids). NOW a switching Bi-directional
• NOTE if the AIS-P was not NODE STS Full Pass-thru
injected traffic would have #25 STS
been misconnected #25

STS #1
Thank You