What is new in iPASO iPASO Series Product ?
Latest NEC Radio Product iPASO 1000
Hybrid ( Native Ethernet & TDM) Packet Radio (PWE Inside) VLAN QoS
QoS/Diffserve Policer/Shaper
All IP Clock Synch. OAM
PWE(E1) Sync Ether IEEE1588V2 Ethernet OAM Hot Standby(1+1) RF Link Aggregation
Link Protection
E1 SNCP RSTP Ethernet Ring(G.8032)
iPASO 400
iPASO 200
NEO HP
Hub, Bridge & Switches
Ethernet Frame and MAC Address The Ethernet is the most popular LAN technology, technology, and represents the protocol pr otocol itself as well. Developed by DEC, Intel and Xerox corporations, the Ethernet is standardized by the IEEE 802.3. The most important technologies on the Ethernet are: Layer 2 based protocol and standards IEEE 802.3 standard 48 bits MAC is used to identified the nodes Commonly known as the CSMA/CD protocol. Currently 4 data rates are defined for operation over optical fiber and twisted-pair cables:
10Base-T Ethernet (10 Mbps) Fast Ethernet (100 Mbps) Gigabit Ethernet (1000 Mbps) 10 Gigabit Ethernet (10,000 Mbps)
Terminal “A” MAC=111
DA: Destination Address SA: Origination Address
Ethernet Equipments (HUB / Switch / Bridge)
Ethernet Frame SA DA Data MAC=111 MAC=222
DA SA MAC=111 MAC=222
Data
Terminal “B” MAC=222
Collision Domain
HUB HUB
Host A
Host B
Host C
Host n
Collision Domain
Collision Domain A HUB
Bridge / Switch / Router
Collision Domain B
What is L2 Switch?
L2 Switch performs the frame forwarding based on Ethernet MAC address of the L2 frame.
Each port of the L2 switch act like a bridge.
Each port of a L2 switch is a collision domain. L2 Switch Hub 1 2 34 5 6 7 8
Hub 1 2 3 4 5 6 7 8 9 10 11 12
Hub
Hub
12 3 4 5 6 7 8
1 2 34 5 6 7 8
1 2 34 5 6 7 8
Ethernet Frame and MAC Address
Ethernet Frame Format Preamble (7B)
SFD (1B)
DA (6B)
SA (6B)
Usual untagged Ethernet Frame: Normal PC Max. MTU 1518 Byte
Length (2B)
Data (46 to 1500B)
FCS SFD: Start of Frame Delimiter DA: Destination address SA: Source Address FCS: Frame Check Sequence
MAC Address Format 1bit
1bit
3~24bit
25~48bit
Uni-cast (0) / Multi-cast (1) address Universal (0) / Local (1) address Vender ID Serial Number Broadcast Address: “all 1”, these frames sent out through all ports Multicast Address: these frames goes to some or all ports Unicast Address: these frames goes to only one port
Basic Ethernet Switching Procedure Frame transmission on Ethernet switch is realized by MAC address learning MAC Address Table Forwarding Data Table (FDB) FDB of iPASOLINK is 32K
Port
MAC address
Default FDB Aging Time 300 sec
1
00-00-00-00-00-01
2
3
1
A
00-00-00-00-00-01
4
D
00-00-00-00-00-04
4
00-00-00-00-00-04
What is VLAN?
Advantages of VLAN (Virtual LAN) Enables to make virtual group in LAN – But communication between different VLAN group can be processed by router Enables to divide broadcast domain Broadcast frame is transmitted to all port except port where broadcast frame was – received when VLAN is not used – Broadcast frame is not transmitted to differ ent VLAN group
VLAN setting
Broadcast frame is transmitted to all port except received port
Broadcast frame is not transmitted to different VLAN group
VLAN Architecture Features of VLAN
Traffic Control In a network where no VLAN is introduced, large amount of broadcast data are delivered to all network devices regardless of their necessity, which easily causes network congestion. Introducing VLANs allows to create small broadcast domains, which can limit communications among devices concerned, thus resulting in higher efficiency of the network bandwidth usage.
Improvement of Security Performance A device that belongs to a certain VLAN can communicate only with devices belonging to the same VLAN. For example, communication between the VLAN of a marketing division and that of a commercial division must go through a router. Since direct communication is not possible between these two divisions, the security performance of the system can be enhanced a great deal.
Easily Replacing and Moving Network Devices Conventional networks require a lot of network administrator’s manpower for replacing and moving network devices. When a user moves to another subnet, it is necessary to reset all addresses of the user’s terminal devices. Introducing VLANs can exempt administrators from this kind of troublesome work for resetting. For example, when moving a terminal in the VLAN of a marketing division to another network port and maintaining the subnet setting, it is sufficient only to change the setting of t he port so as to belong to the VLAN of the marketing division.
VLAN Architecture - 1 The VLAN (Virtual LAN) is a technology to construct a virtual network independent of physical network structure. The conventional LANs centering around hubs and routers take a lot of time and cost because of their physical restrictions encountered during the initial designing or expansion stages. Introducing VLAN m akes it possible to construct or modify the network more easily and flexibly. VLAN2 (Department B)
HUB
VLAN3 (Department C)
VLAN Switch
2nd Floor (Department B)
HUB
2nd Floor
VLAN Switch
VLAN-1(Department A)
1st Floor (Department A)
1st Floor
Just change setting, not physical connections
Need to change physical connections Router
Conventional LAN
Router/L3 Switch
VLAN
Port Based VLAN and Tag Based VLAN Port Based VLAN 1
2 3
4 5
6
7
8 9 10 11 12
VLAN Switch iPASO200 named it as Access VLAN type
VLAN 1
iPASO200 named it as Trunk VLAN type
Tag Based VLAN
(VLAN ID 10)
VLAN SW
(VLAN ID 20)
VLAN 3
VLAN 2
VLAN SW
1 2
1 2
3 4 5 6
3 4 5 6
Tag 10
Tag 20
(VLAN ID 10)
(VLAN ID 20)
Why Jumbo Frame Support is necessary ? Efficient Through-put for application which supports jumbo MTU size (e.g. IP-SAN) Support Ethernet Expansion Frames like VLAN tag, QinQ, MPLS Label etc.. iPASO200 supports frame size of FE ports to 2000 Byte and GbE port to 9600 Byte
Ethernet Header 18Bytes Usual Ethernet Frame
802.1q Ethernet Frame
Q in Q Ethernet Frame
Max 1518 Bytes 1500
Max MTU Size = 1500bytes (Ethernet Standard) Max Frame Size = 1518bytes
18
Max 1522 Bytes 1500
4
Max MTU Size = MTU1500bytes + 4 bytes VLAN Tag Max Frame Size = 1522 Bytes
18
Max 1526 Bytes 1500
4
4
18
Max MTU Size = MTU1500bytes + (2 x 4 bytes VLAN Tag) Max Frame Size = 1526 Bytes
Extended VLAN ( Q in Q) Extended VLAN is standardized by IEEE802.1ad VLAN tag (4byte) is stacked to Ethernet frame iPASO200 named the extended VLAN as Tunnel VLAN Company A VLAN100 Data
VLAN100
100
Data
Data
Company B
Data
100 200 Common Network
Data
100 VLAN100
Company A
100
100 300
Data VLAN100
Company B
100
Ethernet Packet Format Tag VLAN is standardized by IEEE802.1q VLAN tag (4byte) is inserted to Ethernet frame
IFG
Preamble
12 Byte
8 Byte
Destination MAC address
Source MAC address
(DA)
6byte
VLAN tag
Length / type
4byte
2byte
(SA)
Data
FCS
46 - 1500byte
4byte
6byte
Example: traffic assignment 7 (High)
Traffic management
6
Voice
5
Video
4
Control signal
3
Excellent effort
2
Best effort
1
Reserved
0 (Low)
Background
802.1q tag type
TCI field
2byte
2byte
Range: 1 - 4094 (0, 4095 reserved)
Priority
CFI
VLAN-ID
3bit
1bit
12bit
CoS value IFG: Inter Frame Gap CFI: Canonical Format Indicator FCS: Frame Check Sequence TCI: Tag Control Information TOS: Type Of Service
QoS Bit Assignment in Ethernet Frame CFI: Canonical Format Indicator FCS: Frame Check Sequence TCI: Tag Control Information TOS: Type Of Service COS: Class Of Service
802.1q Q-in-Q To MAC Address
Fm MAC Address
TPID
TCI
2Bytes VLAN Tag To MAC Address
VLAN Tag-2(outer)
Fm MAC Address
TCI
Priority bit
8100
IP Header
IP data
FCS
2Bytes Priority bit
8100
TPID
Type
DSCP: Differentiated Services Code Point TPID: Tag Protocol Identifier
TPID
CFI
CFI
VLAN ID
TCI
Type
VLAN ID
8100
Type
IP Header
IP Header
Priority bit
CFI
IP data
VLAN ID
FCS
VLAN Tag-1 (inner)
802.1ad Q-in-Q To MAC Address
Fm MAC Address
TPID
TCI
2Bytes VLAN Tag To MAC Address
VLAN Tag-2(outer)
Fm MAC Address
88a8
TPID
Priority bit
FCS
2Bytes Priority bit
8100
IP data
TCI
TPID
CFI
VLAN ID
CFI
VLAN ID
TCI
Type
8100
Priority bit
IP Header
CFI
IP data
VLAN ID
FCS
VLAN Tag-1 (inner)
Overall view of iPASOLINK L2 Switch Main Board 1.Access
FE1/GbE FE1/GbE
2.Trunk
3.Tunnel
Modem1
L2 SW
FE1/GbE
MC-A4
In-band
Modem2
1. Access Trunk VLAN
2. Trunk
FE1/GbE /GbE
Mod(slot1)
L2 SW
GbE
FE1/GbE
3.Tunnel
Trunk VLAN
Mod (slot N) NMS NE
NMS NE
GbE
iPASOLINK 200 , 802.1q
Main Board
2.Trunk
Modem1
L2 SW
GbE
iPASOLINK 400/1000 , 802.1q
In-band
FE1/GbE FE1/GbE
3.Tunnel
Mod (slot2) Mod (slot3)
GbE
1.Access
In-band
FE1/GbE
iPASOLINK 400/1000 , 802.1ad
Trunk VLAN
MC-A4
In-band
FE1/GbE
GbE
1. C-Access NMS
iPASOLINK 100E , 802.1q
2. S-Trunk
FE1/GbE /GbE
Mod(slot1)
L2 SW
GbE
Mod (slot2) Mod (slot3)
3.C-Bridge Mod (slot N) NMS NE
iPASOLINK 200 , 802.1ad not available
S-Trunk VLAN
VLAN Modes VLAN MODE
Port Type
Direction Ingress
Add C-VID to untagged frames (drop tagged frames)
Egress
Remove C-Tag (outer Tag) from the frame matching the Access port VID
Trunk
Ingress
Transparent for the assigned VLAN IDs (Drop untagged frames)
(Without Untagged Frame assignment)
Egress
Transparent for the assigned VLAN IDs
Ingress
Transparent for the assigned VLAN IDs (Drop untagged frames). Add CVID to untagged frames
Access
IEEE 802.1q
Trunk (With Untagged Frame assignment)
Tunnel
C-Access IEEE 802.1ad
Action
S-Trunk C-Bridge
Ingress Egress
Egress
Transparent for the assigned VLAN IDs Remove C-Tag (outer tag) matching the Access port VID
Ingress
Add C-VID to C-Tag or untagged frames as outer tag
Egress
Remove the C-tag (outer tag) matching the C-VID assigned to the tunnel port
Ingress
Add the S-VID to Untagged and C-tagged frames (as outer tag)
Egress
Remove the S-tag (outer tag) matching the S-VID assigned to C-Access port
Ingress
Transparent for the assigned S-VLAN IDs. (drop untag, c-tag frames)
Egress
Transparent for the assigned S-VLAN IDs
Ingress
Adds S-VID to defined C-Tagged frames
Egress
Remove the S-VID from defined C-Tagged frames
Egress Ether Port
Modem Port
Ingress
Modem ports always Trunk (802.1q) or S-Trunk (802.1ad)
VLAN Setting (1) – Types of VLAN setting at ports Types of VLAN port supported in iPASO200 are named Access, Trunk and Tunnel How to create Access type (port base) VLAN? 1. FE Port set to access port type VLAN
2. Modem port set to trunk type VLAN Default VLAN is 1 , here we set to 10 as example
Send with VLAN 10
Data
Data
10
iPASO200 Data
100
FE Port 1: Access VLAN 10
Modem 1: Trunk VLAN 10
Drop Recommendation: To be used for base station w ith un-tag traffic
VLAN Setting (2) – Types of VLAN setting at ports How to create tag base type (802.1q) VLAN and also supported with un-tag traffic? 1. FE port set to trunk port type VLAN (802.1q) and un-tag frame to be access 2. Modem port set to trunk port VLAN
Data Data
Data
20
100
Data
2
Data
20
FE Port 2: iPASO200 Access LAN 2 Trunk VLAN 20
Send with VLAN 2
Set for Un-tag packet
Send with VLAN 20
Modem 1: Trunk VLAN 2, 20
Drop Recommendation: To be used for base station with VLAN tag interface
VLAN Setting (3) – Types of VLAN setting at ports How to create tunnel type ( Q in Q ) VLAN? FE port set to tunnel port type VLAN (almost 802.1ad or Radio Hop Q in Q) Modem port set to trunk port VLAN
All packets will be sent transparently with additional tag added on
Data Data
20
No packets will be drooped
Data
30
Data
20 30
iPASO200
FE Port3: Tunnel VLAN 30
Add on tag VLAN30 Add on tag VLAN 30
Modem 1: Trunk VLAN 30
Recommendation: To be used when required Q in Q features
VLAN Setting (4) – Setting methods at Modem ports Modem port parameter setting methods
Data
Data
2
Data
2
Data
30
Data
30
Data
20
Data
20
Data
10
Data
10
40
Drop
iPASO200
Modem 1: Trunk VLAN 2,10,20,30
VLAN Mode 802.1ad- Example of C-Access Port 802.1ad
Only Untagged frames and all C-tag frames are processed on Port 1, and these frames are assumed to belong to S-VLAN ID = 200 any incoming S-VLAN tag frames are dropped
FM- To A B
C-VLAN any
MSG
FM- To- S-VLAN A B 200
FM- To- MSG A B
C-VLAN Y
FM- To- S-VLAN MSG A B 200
P1 (FE) FM- To- S-VLAN A B any
C-VLAN any
MSG
Modem port Type: S -Trunk S -VL AN : 100, 200,300
MSG
VLAN Mode 802.1ad- Example of S-Trunk Port 802.1ad
A t port 1, Fr ames without a S -Tag will have S-VL AN ID 200 and for warded (both untag g ed and with any C-tag ) Frames with S-VLA N IDs 100,200,300 are only passed. Any othe S-VL AN ID wi ll be dr opped FM- To A B
C-VLAN any
MSG
FM- To- S-VLAN A B 200
C-VLAN any
MSG
FM- To- MSG A B
FM- To- S-VLAN MSG A B 200
FM- To- S-VLAN A B 100
C-VLAN any
MSG
FM- To- S-VLAN A B 100
C-VLAN any
MSG
FM- To- S-VLAN A B 300
C-VLAN any
MSG
FM- To- S-VLAN A B 300
C-VLAN any
MSG
P1 (FE) FM- To- S-VLAN A B other
C-VLAN any
MSG
Modem port Type: S -Trun k S -VL AN : 100, 200,300
VLAN Mode 802.1ad- Example of C-Bridge Port In the example s hown:
802.1ad
Only frames with C -VLA N IDs , defined will pass at port1 wi th cor res pondi ng S -VL A N ins erted: C-V LA N 10, 20 will be inserted with S-VL AN 100 and for warded C-V LA N 25, 30 will be inserted with S -VLA N 200 and for warded A ll the other C -VL A Ns are dropped A ny S -VLA Ns are dropped
FM- To A B
C-VLAN 25,30
MSG
FM- To- S-VLAN A B 200
C-VLAN 25,30
MSG
FM- To A B
C-VLAN 10,20
MSG
FM- To- S-VLAN A B 100
C-VLAN 10,20
MSG
FM- To A B
C-VLAN other
MSG
S -VL A N: 100, 200,300 Modem port Type: S -Trun k
FM- To- S-VLAN A B 200
C-VLAN 25,30
MSG
C-VLAN 10,20
MSG
FM- To- S-VLAN A B 200
C-VLAN 25,30
MSG
FM- To- S-VLAN A B 100
C-VLAN any
MSG
FM- To- S-VLAN A B 100
C-VLAN 10,20
MSG
FM- To- S-VLAN A B 300 FM- To- MSG A B
P1 (FE)
Quality of Service
Summary of locations for Policing and Shaping Default Setting Shaping: 4XSP Default Setting of Policing : Nil
Classify/Policing
Scheduling/Shaping
Classify/Policing
Classify/Policing
Scheduling/Shaping Classify/Policing
FE Port
Scheduling/Shaping
Modem Port
Ingress Egress
Scheduling/Shaping
Modem Port
FE Port
QoS Bit Assignment in Ethernet Frame
1) IP Packet
ToS(3bit) DSCP/Diffserve(6bit)
Version
IP ECN
Header Length
TOS
Explicit Congestion Notification
IP address etc.
8bits
To MAC Address
Fm MAC Address
Type
TCI
Type
IP Header
IP data
FCS
2Bytes Priority bit (CoS)
VLAN Tag
CFI
CFI: Canonical Format Indicator FCS: Frame Check Sequence TCI: Tag Control Information TOS: Type Of Service COS: Class Of Service DSCP: Differentiated Services Code Point
VLAN ID
3bits (802.1q CoS)
2) MPLS Packet MPLS Label
MPLS Label
IP Header
IP data
3bits Label
Exp
S
TTL
EXP : experimental bits ( iPASO200 will supports in future)
Ether Functions
Protected
TDM
Packet
TDM Radio Capacity
Radio Capacity
Packet Policing/Shaping according to QoS
TDM
Port Ingress Setting Classification Determine equipment internal priority
Ether
VLAN CoS IPv4 precedence IPv4/v6 DSCP MPLS EXP
Eg ress Queue
Port Egress Setting TDM +
Ingress Policer
Packe
Token
Token
Internal Priority Queuing Policy per ingress Port
Class 3 queue
Sent frames
Packet
Class 2 queue Token bucket
t
QoS
Token bucket
Class 1 queue Two-Rate, (CIR & EIR) Three-Color Metering
Class 0 queue
S cheduling & S haping
User can define TDM bandwidth for each radio modulation
Color B lind metering WTD: Weighted Tail Drop, WRED: Weighted Random Early Detection, SP: Strict Priority, DWRR: Deficit Weighted Round Robin,
iPASOLINK QoS overview iPASOLINK has two QoS mapping profiles. One is classification the other is mapping to egress class queue Both mapping are for the selected ingress port
MODEM Port-1
ETH Port 1
Egress Port
Egress Class Queues
Egress Class Queues Egress Port
Ingress Port
Ingress Policer
Classification
Input frame priority (CoS, DSCP, EXP, etc) CoS 0 CoS 1 CoS 2 : :
Internal Priority (0-7) Internal 0 Internal 1 Internal 2 Internal 3 Internal 4 Internal 5 Internal 6 Internal 7
In Equipment base QoS, uses one profile per equipment. In Port base QoS, enables to prepare mapping profile per port.
MODEM Port-2
Egress Classify
Internal Priority (0-7) Internal 0 Internal 1 Internal 2 Internal 3 Internal 4 Internal 5 Internal 6 Internal 7
Egress Class Queues Class queue (0-3)
Egress Port
Class 0 Class 1 Class 2 Class 3
Enables to prepare total three mapping profiles. Sets profile from three profiles per output port (ETH, MODEM).
Summary of iPASOLINK QoS Functions and Features
•
iPASOLINK series supports fully functioned QoS control
•
Supported classification methods: CoS/IP Precedence/DSCP/EXP
•
Internal Classification: 8 classes (8 classes mapped to 4 classes (default) / 8 classes (option) for Egress Queue)
•
Internal Priority to CoS Mapping
•
Ingress policing: CIR, EIR (Two-Rate Three-Color Marking)
•
Profile based QoS management is supported
•
Scheduling: SP, SP+3DWRR, 4DWRR (default) / SP+7DWRR, 2SP+6DWRR (option)
•
Congestion Avoidance: Weighted Tail Drop / WRED
•
Egress hierarchical shaping (Port + each QoS Class) 31
Classification Modes •
Equipment Based QoS Mode –
•
Profile Based ( one profile for the equipment) Port Based QoS Mode
–
Port (Default Priority for each port can be set)
–
CoS (C-Tag) ( use Port priority or CoS)
–
DSCP IPv4/v6 (set DSCP to internal Priority)
Frame
Classification Mode & Internal Priority Port
Untag
Tagged
CoS (C-Tag)
DSCP IPv4/v6
IP packet
Default Port Priority
Default Port Priority
DSCP IPv4/v6
Non-IP packet
Default Port Priority
Default Port Priority
Default Port Priority
IP packet
Default Port Priority
CoS
DSCP IPv4/v6
Non-IP packet
Default Port Priority
CoS
Default Port Priority
32
Classification Classification –process of distinguishing one kind of traffic from another by examining the Layer 2 through Layer and QoS fields in the packet
Determine equipment internal priority
VLAN CoS IPv4 precedence IPv4/v6 DSCP MPLS EXP
Profile No.0
(ex) Profile No.1
(ex) Profile No.2
VLAN CoS
Internal priority
IP Precedence
Internal priority
DSCP
Internal priority
7
7
7
7
63
7
6
6
6
6
:
:
5
5
5
5
47
5
4
4
4
4
:
:
3
3
3
3
31
3
2
2
2
2
:
:
1
1
1
1
15
1
0
0
0
0
0
0
Classification profile is configurable.
Equipment based QoS Mode
iPASOLINK Modem (trunk)
Add tag 10 IP packet / Non-IP packet
SA
DA
Port 1
IP packet /
(Access) VLAN-10
Non-IP packet
VLAN 10 CoS X
SA
DA
X=Other setting for non IP frame X= IP Precedence for IP frame
IP packet /
VLAN 20
Non-IP packet
CoS Y
SA
DA
Port 2
(Trunk) VLAN-20
IP packet / Non-IP packet
VLAN 20 Cos Y
SA
DA
Pass with the incoming VLAN tag
IP packet /
VLAN 50
Non-IP packet
CoS Y
SA
DA
Port 3
IP packet /
(Tunnel)
Non-IP packt
VLAN 40 IP packet / Non-IP packet
SA
DA
Inner VLAN 50 CoS Y
IP packet / Non-IP packet
Outer VLAN 40 CoS Y
SA
DA
VLAN 40 CoS X
SA
DA
Add outer tag 40 to incoming frame X=Other setting for non IP frame X= IP Precedence for IP frame
Port Based QoS classification – Port Mode (1/3) •
Classifies according to ingress physical port
iPASOLINK Modem
Port type
Internal priority
Policing
Access
DPP-7
DPP-7
Trunk
DPP-6
CoS-0
Tunnel
DPP-5
DPP-0
(trunk) Port mode
IP packet / Non-IP packet
IP packet /
VLAN Tag
Non-IP packt
(CoS0)
IP packet /
VLAN Tag
Non-IP packt
(CoS0)
SA
SA
SA
DA
DA
DA
IP packet /
Port 1
(Access)
Port No.
Default Port priority
1
7
2
6
3
5
Port 2
4
4
(Trunk)
MODEM 1
3
MODEM 2
2
MODEM 3
1
MODEM 4
0
Non-IP packet
VLAN Tag
SA
DA
(C oS 7 ) Update CoS value to Default port priority value
IP packet / Non-IP packet
VLAN Tag
SA
DA
( C oS6 ) Update CoS value to Default port priority value
Port 3
IP packet /
(Tunnel)
Non-IP packt
Inner VLAN Tag (CoS0)
Outer VLAN Tag
SA
DA
( C oS5 )
Use Default port priority value as CoS value
Port Based QoS classification – CoS Mode (2/3) •
Classifies according to CoS value
Port type
Internal priority
Policing
Access
DPP-1
DPP-1
Trunk
CoS-0
CoS-0
Tunnel
CoS-5
CoS-5
iPASOLINK Modem (trunk) CoS (C-Tag) mode
Default Port priority = 1 IP packet / Non-IP packet
SA
DA
Port 1
IP packet /
(Access)
Non-IP packet
VLAN Tag ( CoS1 )
SA
DA
Update CoS value to Default port priority value
IP packet / Non-IP packet
VLAN Tag (CoS0)
SA
DA
Port 2
IP packet /
(Trunk)
Non-IP packet
VLAN Tag ( CoS0 )
SA
DA
No update CoS value
IP packet / Non-IP packet
VLAN Tag (CoS5)
SA
DA
Port 3
IP packet /
(Tunnel)
Non-IP packet
Inner VLAN Tag (CoS5)
Outer VLAN Tag ( CoS5 )
SA
DA
Use input CoS value
Port Based QoS classification - DSCP Mode(3/3) •
Classifies according to DSCP value even if the frame is VLAN tagged frame
Update CoS value to internal priority value of DSCP classification mapping Modem
iPASOLINK IP packet
IP packet
IP header ( DSCP63 )
IP header ( DSCP47 )
VLAN Tag (CoS7)
SA
SA
DA
(Access)
(Trunk)
IP header ( DSCP31 )
VLAN Tag (CoS7)
SA
Non-IP packet
Non-IP packet
Non-IP packet
VLAN Tag (CoS7) VLAN Tag (CoS7)
SA
SA
DA
DA
SA
DA
Inner VLAN Tag (CoS7)
Outer VLAN Tag ( CoS3 )
SA
DA
Non-IP packet
VLAN Tag ( CoS1 )
SA
DA
Non-IP packet
VLAN Tag ( CoS1 )
SA
DA
Outer VLAN Tag ( CoS1 )
SA
DA
IP header (DSCP63)
IP header
Internal priority
63
7
(Tunnel)
:
:
47
5
:
:
Port 1
31
3
(Access)
:
:
15
1
0
0
Classifies by this value
(DSCP47)
VLAN Tag ( CoS5 )
IP packet
DSCP Classification Mapping
Port 3
DA
DA
DSCP IPv4/v6 mode
DSCP IP packet
SA
IP packet
Port 2
DA
VLAN Tag ( CoS7 )
(trunk)
Port 1
Port 2
IP packet
IP header (DSCP31)
(Trunk)
SA
DA
Port 3
(Tunnel)
D
Default Port priority = 1
Non-IP packet
Inner VLAN Tag (CoS7)
Use default port priority value as CoS value
VLAN ID Based QoS Mode (1/2) •
Determines Internal Priority according to VLAN ID
•
Uses Default Priority value when VLAN ID is not registered to mapping table Port type
iPASOLINK
Modem
Internal priority
Policing
Access
7
7
Trunk
5
0
Tunnel
3
0
(trunk) VLAN ID Based QoS mode
(VID10,20,30)
Default Priority = 1 IP packet / Non-IP packet
SA
DA
Port 1
Ac ces s ) ( ( V ID10 )
IP packet / Non-IP packet
VLAN 20 (CoS0)
SA
DA
Port 2 ( T runk )
IP packet / VLAN ID
Internal priority
10
7
20
5
30
3
40
1
Non-IP packet
VLAN 10 ( CoS7 )
Non-IP packet
VLAN 20 (CoS0)
IP packet / Non-IP packet
VLAN 20 ( CoS0 )
IP packet / Non-IP packet
DA
Port 3 ( Tunnel ) ( V ID30 )
SA
DA
SA
DA
No update CoS value IP packet /
SA
DA
Use internal priority value for outer VLAN ID(*)
( V ID20 )
IP packet /
SA
Non-IP packet
Inner VLAN 20 (CoS0)
IP packet / Non-IP packet
(*) If outer VLAN ID which is added is not registered to mapping table, Default Priority is used as internal priority and CoS value.
Outer VLAN 30 ( CoS3 )
SA
DA
Outer VLAN 30 ( CoS3 )
SA
DA
Use internal priority value for outer VLAN ID(*)
VLAN ID Based QoS Mode (2/2) •
Determines Internal Priority according to VLAN ID
•
Uses Default Priority value when VLAN ID is not registered to mapping table iPASOLINK
Modem
(trunk) VLAN ID Based QoS mode
(VID60,70,80)
Default Priority = 1 IP packet / Non-IP packet
SA
DA
Port 1 ( Ac ces s ) ( V ID60 )
IP packet / Non-IP packet
VLAN 70 (CoS0)
SA
DA
Port 2
(Trunk)
IP packet / VLAN ID
Internal priority
10
7
20
5
30
3
40
1
Non-IP packet
VLAN 60 ( CoS1 )
Non-IP packet
VLAN 70 (CoS0)
IP packet / Non-IP packet
VLAN 70 ( CoS0 )
IP packet / Non-IP packet
DA
Port 3
Non-IP packet
(Tunnel)
Inner VLAN 70 (CoS0)
( V ID80 ) SA
DA
SA
DA
No update CoS value
IP packet / SA
DA
Use Default Priority value
( V ID70 )
IP packet /
SA
IP packet / Non-IP packet
(*) If outer VLAN ID which is added is not registered to mapping table, Default Priority is used as internal priority and CoS value.
Outer VLAN 80 ( CoS0 )
SA
DA
Outer VLAN 80 ( CoS1 )
SA
DA
Use Default Priority value
What is CIR, EIR? CIR (Committed Information Rate) -
Minimum BW guaranteed for an Ethernet service. Policing is enforcement of CIR Zero CIR means Best effort (no BW is guaranteed)
CIR Conformant Traffic ≤ CIR
EIR (Exceeded Information Rate) Service frames colored yellow may be
delivered but with no performance commitment.
EIR Conformant PIR (Peak Information Rate) -
Traffic ≥ CIR
Maximum rate at which packets are allowed to be forwarded. PIR = CIR + EIR (greater or equal to the CIR) Service frames exceeding PIR are red packets and
are unconditionally dropped
No traffic Traffic ≥ PIR
Note: Color Blind and Color Aware Rate Metering ( iPASO200 is color blind system)
Dual Token bucket (TRTCM) Dual rate token bucket with a programmable CIR and EIR, as well as CBS and EBS. It also named as Two rate ,Three-Colour Metering Example: consider the extreme case One bucket is used: CIR=2Mbps, CBS=2KB, EIR=0,EBS=0 Case 1: Two 1518 byte frames coming back to back First frame take 2000-1518 token remain 482 byte, the second frame is immediately Discarded Case 2: One frame 1518 is sent, 8 ms later, another 1518 byte arrive, since token bucket Refill with CIR/8=250Kb/s The token bucket is full again and able to sent the second frame out with green color.
Our Recommendations:
CBS/EBS should be set depend on traffic type 1. Bursty TCP-based traffic 2. UDP based type such as VoIP
Note: Color Blind and Color Aware Rate Metering ( iPASO200 is color blind system)
Ingress Policing Discard Violating Frames
PIR
Exceeding Frames ] c i f f a r T f o t n u o m A [
EIR
Complying Frames
CIR
[Time]
Ingress Policing (per port / per VLAN/priority) Conforming Frames Marking to Green
Rate Check Committed Rate Token Bucket
< Rate Check
> Exceeded Rate Token Bucket High priority Middle priority Low priority
> Drop
Exceeding Frames Marking to Yellow
Yellow
Green
Green
Green
< Violating Frames Marking to Red, and discard
Meters rate of packet stream (CIR and EIR), and marks three colors (green, yellow or red)
Service Provider Business Oriented Parameter in iPASO Business Package:
30 Mb
PIR
30Mbps PIR 20 Mb
15Mbps CIR 15Mbps EIR
Recognize the service according to DSCP/TOS/IP and prioritize it.
EIR 10 Mb CIR 0 Mb
VLAN 20 iPASO400
Video Conf.
Voice
Data / VPN
iPASO200
iPASO400
Scheduling or Queuing Methods
Methods of Scheduling FIFO
Strict Priority
WFQ(WRR)
Elements of QoS - Scheduling /Queuing
Control the output sequence and bandwidth of frames from each queue according to Output condition defined by Marker/Priority M arker/Priority Determination. Strict Priority Queuing (SPQ), Weighted Control (WRR) can be used as queuing method.
ETC System Electronic Toll Collection System
Deficit Round Robin 50
100
75
50 50 50
75
50 50 50
75
150 50
T i m e 50
75
100
75
50 50
25
50 50
25
150
75
100
Credits
150
50 50
100
50 50
100
150
150
7 5 75 75 75
Credits 50 50
Credits
50
100 50 50 50 50 150
Credits
Credit counter: Initially the counter start or reset from zero. For this example, it was set to size value of 75 for all the queue. When W hen the queue is not serve to send any packet, the credit counter will be increased with another 75 1st round: The first and fourth queue packet size is bigger than credit counter value, these two queue will hold back and not sending any packets, but second and third t hird queue sent out 50 packets. And their credit counter reduce to 25. 2nd round: The first and fourth queue counter credit increase to 150 byte The result is Q1 send 150 byte Q2 send 100 byte Q3 send 100 byte Q4 send 150 byte 3rd round: All credit counter with with value 75 byte
Egress Scheduling and Shaping (4 Class queue)
Clas Clas s ify (Ma (Mapping pping ) for Eg ress Queue with internal priority
Class 3
S chedulin ch edulingg and Shaping Sh aping Shaper
Class 2
SP
Shaper
Class 1
Class 0
Shaper
DWRR Shaper
Shaper
Divided throughput by weighted condition
Class 3 absolute priority
Mapping table is Configurable. WTD/WRED discard based on color (Green/Yellow)
“SP” or “1SP + 3 DWRR” or “4 DWRR”
Egress Scheduling and Shaping ( 8 class queue)
Clas Clas s ify (Ma (Mapping pping ) for Eg ress Queue with internal priority
Class 5
S chedulin ch edulingg and Shaping Sh aping
Class 7 Class 6
Shaper
Class 5 Class 4 Class 3 Class 2
Shaper
DWRR Shaper
Shaper
Class 1
Mapping table is Configurable.
SP
Shaper
Class 0
WTD/WRED discard based on color (Green/Yellow)
Divided throughput by weighted condition
Class 7 absolute priority
“1SP + 7 DWRR” or “2SP + 6 DWRR”
Scheduling – How it works? Strict Priority Scheduling :The queue with the highest priority that contains packets is always served (packet from that queue are de-queued and transmitted). Packets within a lower priority queue will not transmit until all the higher-priority queues become empty CoS=7 100Mbps CoS=5 100Mbps CoS=3 100Mbps CoS=0 100Mbps
1000M
Classification CoS 7 Pri 7 Class 3 CoS 6 Pri 6 Class 3 CoS 5 Pri 5 Class 2 CoS 4 Pri 4 Class 2 CoS 3 Pri 3 Class 1 CoS2 Pri 2 Class 1 CoS 1 Pri 1 Class 0 CoS 0 Pri 0 Class 0
250M
CoS=7 100Mbps CoS=5 100Mbps CoS=3 50Mbps CoS=0 0Mbps
4SP
Weighted Round Robin uses a number that indicates the importance (weight) of each queues. W RR scheduling prevents the low-priority queues from being completely neglected during periods of high-priority traffic. The WRR scheduler transmits some packets from each queue in turn. The number of packets it transmits corresponds to the relative importance of the queue. CoS=7 100Mbps CoS=5 100Mbps CoS=3 100Mbps
1000M
Classification CoS 7 Pri 7 Class 3 CoS 6 Pri 6 Class 3 CoS 5 Pri 5 Class 2 CoS 4 Pri 4 Class 2 CoS 3 Pri 3 Class 1 CoS2 Pri 2 Class 1 CoS 1 Pri 1 Class 0 CoS 0 Pri 0 Class 0
DRR Weight Class 3: Class 2: 4 Class 1: 2 Class 0: 1
CoS=7 100Mbps
CoS=3 100Mbps CoS=0 100Mbps
240M
1000M
Classification CoS 7 Pri 7 Class 3 CoS 6 Pri 6 Class 3 CoS 5 Pri 5 Class 2 CoS 4 Pri 4 Class 2 CoS 3 Pri 3 Class 1 CoS2 Pri 2 Class 1 CoS 1 Pri 1 Class 0 CoS 0 Pri 0 Class 0
DRR Weight Class 3: 4 Class 2: 3 Class 1: 2 Class 0: 1
CoS=5 80Mbps = (240-100)*4/(1+2+4) CoS=3 40Mbps = (240-100)*2/(1+2+4) CoS=0 20Mbps = (240-100)*1/(1+2+4)
1SP+3DWRR
CoS=0 100Mbps
CoS=5 100Mbps
CoS=7 100Mbps
SP class is absolute priority traffic. The remaining bandwidth is distributed in other classes according to DRR weight. (e.g. remaining BW = 240-100=140Mbps) CoS=7 80Mbps = 200*4/(1+2+3+4)
200M
CoS=5 60Mbps = 200*3/(1+2+3+4) CoS=3 40Mbps = 200)*2/(1+2+3+4) CoS=0 20Mbps = 200*1/(1+2+3+4)
4DWRR
The port bandwidth is distributed in all classes according to DRR weight.
Elements of QoS ( Discard Control) Determines whether the current frame to be queued or discarded, depending on the packet priority and the state of the queue.
Too Late!!
Comfortable!!
Little slow..
Not connecte d well…
Traffic Concentration h t d i w d n a B
Early detect and restrain Window Size decrease globally Average Utilization Time
h t d i w d n a B
Average Utilization
Time Effective Window size variation
Congestion Avoidance ( Discard Control) iPASO200 support Weight Tail Drop at Release 1.07and later with WRED Congestion avoidance techniques on the egress queues. Both techniques will drop packets when preconfigured thresholds on the egress queues have been reached.
Threshold2 (75%) Threshold3 Threshold1 (100%) (50%)
Weighted Tail Drop (WTD), with thresholds Setting on each queue, for congestion avoidance
Queuing Priority1: 0% discard Queuing Priority2: 0 % discard Queuing Priority3: 0% discard Queueing Priority1:100%discard Queuing Priority2: 0 % discard Queuing Priority3: 0% discard Queueing Priority1:100%discard Queuing Priority2: 100 % discard Queuing Priority3: 0% discard
Operation Administration & Maintenance (OAM)
Ethernet OAM To maintain the service availability and quality for the packet networks, powerful OAM toolset is required. Provide Fault management by Ethernet OAM (ITU-T Y.1731 and CFM or IEEE 802.1ag). Fault Management – CC (Continuity Check) – LB (Loop Back) → It corresponds to “ping” in IP. – LT (Link Trace) → It corresponds to “trace route” in IP.
BTS/Node-B
Provider X Operator A Operator B
BSC/RNC
CC LB LT
Y.1731 Performance Management not yet supported By iPASO200
Ethernet OAM
Function Connectivity Fault Management
Performance Monitor
Y.1731
802.1ag
Fault Detection
Mechanism CCM
Fault verification-Loop back
LBM / LBR
Fault isolation
LTM / LTR
Discovery
LTM / LTR
Fault Notification
-
AIS RDI
Frame Loss
-
CCM, LTM, LTR
Frame Delay
-
DM(1 way) DMM, DMR
Delay Variation
-
DM(1 way) DMM, DMR
CCM : Continuity Check Message LBM: Loopback Message LBR: Loopback Reply LTM: Link Trace Message LTR: Link Trace Reply DM: Delay Measurement DMM: Delay Measurement Message DMR: Delay Measurement Reply
Example of the hierarchical Ethernet OAM Customer Level (MEG level:5-7)
: MEP : MIP
Provider Level (MEG level:3-4) Operator Level (MEG level:0-2)
MEG
Operator Level (MEG level:0-2)
Operator Level (MEG level:0-2)
Operator Level (MEG level:0-2)
Provider X Customer 1
Operator A 2
3
Operator C
Operator B
4
5
6
8
7
9
LB
11
LB
(MEG level:0)
CC
10
Customer
(MEG level:0)
(MEG level:2)
LT
LB
(MEG level:2)
(MEG level:2)
CC
CC
(MEG level:4)
(MEG level:7)
Several level can be managed at same time in the same network
Example of Maintenance Entities
Provider X Customer 1
Operator A 2
3
Customer
Operator B 4
5
6
8
9
Customer Level (5-7) Service Provider Level (3-5) Operator Level (0-2) Maintenance Entity Points Maintenance Intermediate Points
Maintenance Entities
ETH-CC (Fault Detection)
1
2
3
4
Legend
: MEP : CCM : CCM
Objectives To Establish OAM connections on the Ethernet-based networks. To understand fault detection by sending and receiving ETH-CC frames between MEPs periodically
Operations Each MEP transmits ETH-CC frames periodically If MEP does not receive any ETH-CC frames for 3.5 times of the ETH-CC frame transmission interval, it provide alarm indication (loss of connectivity)
ETH-LB (Fault Verification) 1
2
3
4
Legend : : : :
MEP MIP LBM LBR
Objectives To verify the connectivity between multiple equipments Unicast ETH-LB : verification between the designated 2 equipments Multicast ETH-LB: verification the existence of the nodes in the same MEG
Operations MEP#1 sends a Unicast ETH-LBM frame to MEP#4 MIP(#2,3) forwards the ETH-LBM frame to the far -end MEP#4 terminates the ETH-LBM frame and reply a ETH-LBR frame MEP#1 receive the ETH-LBR frame
ETH-LT (Fault Isolation) 1
2
TTL=n
3
TTL=n-1
4
TTL=n-2
TTL=n TTL=n-1 TTL=n-2
Legend : MEP : MIP : LTM : LTR
Objectives To verify the route status and localization of the fault
Operations MEP#1 sends a ETH-LTM frame to MEP#4 Each MIP (#2,#3) sends a reply ETH-LTR to MEP#1, and forwards the ETH-LTM frame with the decreased TTL value to the far-end MEP#4 terminates the ETH-LTM frame and reply a ETH-LTR frame MEP#1 receives the ETH-LTR frames which have the different TTL value.
Ethernet OAM functions DOWN MEP/MIP
DOWN MEP/MIP
L2SW
L2SW
UP MEP/MIP
UP MEP/MIP
UP MEP/MIP sends messages in to the Node DOWN MEP/MIP sends messages out of the Node
ETH-CC/LB/LT
LAN
L2SW
MODEM
Reply frame OK Reply frame NG
MODEM
Reply frame NG
supports only Down MEP/MIP Ether OAM reply frame from Switch to LAN/MODEM port outward direction is okay But from LAN/MODEM toward Switch directional is not s upported For this application, ETH-CC/LB/LT reply frame only at MODEM port The MEP should be set only at Modem port
LAN
ETH-CC/LB/LT
ETH OAM Setting Maintenance Domain Name: NEC Short MA name: NEC Meg Level: 7 CCM: Enable ETH CC period : 3.3 ms CCM Priority : 7
iPaso400-F
iPASOLINK200 supports only Down MEP/MIP Ether OAM reply frame from Switch t o LAN/MODEM port outward direction is okay But from LAN/MODEM toward Switch directional is not supported
iPaso200-D
iPaso200-E
H M1
L
ODU-Back 23G Hz 22484 / 21252
ME P1
M1
M2
M2
iPaso400-F
M1
Mep1 Mep3
H
L M1
P2 MIP
L
ODU-Back 23G Hz 22484 / 21252
M1
M2
M2
P1
iPaso200-D
M1
M1
P2 MIP
M2
iPaso1000-C
H
L
M1
ODU-3 7GHz
MIP
iPaso200-E
H
M1
ODU-1 23GH z 22030 / 23038
P1
iPaso400-B
iPaso200-A
ME P2
MIP
iPaso200-A
H
7310/7156
L M1
M2
iPaso400-B
M2
Mep2
ODU-1 23G Hz 22030 / 23038
P1
P2 MIP
MIP
M2 ODU-4 7GHz 7310/ 71560
iPaso1000-C
M2 Mep4
LINK OAM Alarm & Status Discovery Msg (Active)
A flag in the OAMPDUs allows local device to convey failure event to its peer. Link OAM Down :signals that the PHY has determined a fault occurring in the receive direction of the local device iPASOLINK supports only receiving of this message.
Discovery Response (Passive)
Link Fault Msg
Dying Gasp Msg
e.g. CPU restart e.g. Loss of Signal
Cri tical Event Msg
Cr itical Event Msg e.g. Radio link failure
e.g. Module failure
Loopback
Loopback control Ms g
Equipment which is able to monitor Link Event
Event Notification Msg
Ether Ring Protection
G.8032 Ethernet Ring Protection Switching • • • •
Utilizing widely-deployed Ethernet (802.1,3) with OAM (802.1ag/Y.1731) Loop-free protection mechanism Protection Switching Time <50ms Scalable topologies – Single ring, interconnected rings, and logical rings – No. of nodes per ring: no limitation in theory(?) • Administrative operation – Forced switching – Manual switching – Revertive/ Non-revertive
Client #1 Signal Traffic separation with VLAN Tag
ETH-CC
RP L (Ring Protection Link) B locked port
Client #2 Signal
RP L (R ing P rotection Link) B locked port
G.8032 Ethernet Ring Protection
G.8032 is an ITU Recommendation
Defines the APS (Automatic Protection Switching ) protocol and protection switching mechanisms for ETH layer ring topologies.
Use of standard 802 MAC and OAM frames around the ring
Uses standard 802.1Q , but with xSTP disabled.
Prevents loops within the ring by blocking one of the links
Monitoring of the ETH layer f or discovery and identification of Signal Failure (SF) conditions.
Protection and recovery switching within 50 ms for typical rings.
Unblock blocking Port
Blocking Port
Client Traffic
1) Normal Condition
Submission of FDB Flush, Unblock blocking Port
2) Failure Event
3) Switchover Condition
Failure monitoring •
G.8032 utilizes the following monitoring functions to detect link / node f ailures certainly. –
Physical layer : Link down detected by Ethernet PHY (Optical/Electrical), etc.
–
Link layer
: ETH-CC (Continuity Check) defined on Y.1731/802.1ag between adjacent ring nodes. Messaging interval: 3.33msec at minimum
–
cc
Failure Detection time = 3.33 msec * 3.5 = 11.7msec Unblock blocking Port
MEP-2
cc
MEP-2
MEP-4
MEP-3
MEP-1 LOC
MEP-5 MEP-6
cc
MEP-8
cc
cc cc
MEP-5
MEP-7
LOC
1) Normal Condition
cc
MEP-4
MEP-8 MEP-7
Submission of FDB Flush, Unblock blocking Port
cc
MEP-3
MEP-1
cc
Client Traffic
MEP-6
cc
2) Failure Event
ETH-CC enables to detect failures on several conditions which physical layer monitoring can’t do.
LOC cc
cc
LOC 3) Switchover Condition
Unidirectional link failure
Partial failure in equipment
Decline of signal level (less than Loss of Signal)
In case if no ability to detect a failure is on physical layer
Multiple instances (2/3)
• Flexible placement of RPL – The shortest path per user traffic can be selected in normal condition.
Special reuse for the ring bandwidth can be achieved.
User B User A
•The double capacity can be obtained in normal condition, and the higher prioritized traffic are protected even in case of a failure.
1GbE 1GbE
1GbE Failure
2GbE Double capacity
GbE Ring
1GbE
1GbE
QoS discarding
GbE Ring
Principal benefit of Ethernet Ring Protection • Reduction of the number of link between NEs compared with mesh configuration • Load balancing by multi instance • Provides reliable protection mechanism – protection switching time < 50msec • Minimizes service influence with Manual/Forced switching and administrative reversion when adding NE
blocked port
Failure
blocked port
Multiple instances (2/3) • Multiple instances per physical ring – Logical rings can be configured on a physical ring. – Each logical ring has a group of user VLANs (instances) and a dedicated APS channel. – APS protocol runs independently. • RPL can be placed at a different point respectively • FDB flush operation is performed per logical ring • All logical rings shares the monitoring information of ETH-CC (link layer) and Link Failure (physical layer).
User VLAN group #1 APS channel #1 (Link Monitoring)ETH-CC-1
Physical Instance #1
User VLAN group #2 APS channel #2 (Link Monitoring)ETH-CC-2
Instance #2
User VLAN group #3 APS channel #3 (Link Monitoring) ETH-CC-3
Instance #3
Ring Types
Scenario A - Normal to Protection RPL
Node-A
Node-B
Node-C
Node-D
Node-E
Node-G
RPL Owner
Node-F
1 NORMAL S TA TE
failure
2 3 4
Flush SF
PROTECTION S TA TE
5 6 7
SF Flush
SF SF
Flush
SF
1 . Normal S tate Node-G i s the R PL Owner 2 . Failur e Occurs 3 . Node D and Node C d etect local s ig nal fail condition. After waiting for the Hold-Off timer to end block the failed ports 4 . While the SF condition continues Node C and Node D periodic ally s end S F (s ig nal Fail) Mes s ages on both ring ports 5 . Each node performs a FDB flus h operation after receiving the S F messag e
SF
SF Flush
Flush
SF Flush
Flush
SF
SF
SF
6 . When the R PL owner receives the S F mess age it unblock the RP L link 7 . S table State – S F messag es on the ring . Further S F mes s ag es does not tri g g er fur ther acti on
Message source Client ch block R-APS ch block
5 0 m s
Scenario B recovery Node-A
Node-B
Node-C
Node-D
Node-E
Node-F
Node-G RPL Owner
failure
8
SF SF
9 PROTECTION S TA TE
10 11
SF
SF
SF
SF
recovery NR
NR NR
NR
NR
NR
12
C o n f i r m a t i o n t i m e
13
14 NORMAL S TA TE
NR, RPL Blocked
NR, RPL Blocked Flush
m s
Flush
Flush Flush
15
Flush
NR, RPL Blocked 5 0
NR, RPL Blocked
9 . In Stable S F condition Node C and D continue to send SF mess ages every 5sec. 10 . R ecovery of failure 11 . Node C and D detects clearing of S F condition and start the g uard timer and ini tiate periodic al trans mis s ion of NR mess ag es on both ring ports (g uard timer prevents reception of R -APS mess ag es 12. When R PL owner receives the NR mess age, it starts the Wait to R estore Timer (WTR )
Flush
Flush NR, RPL Blocked
NR, NR Blocked RPL
14. When the Guard timer at Node C and D expire they may s tart receivi ng new R-APS messages 15. At the expiration of WTR timer, R PL owner blocks its end of of the RP L link, sends NR RB mess age 16. Each node after re3ceivng the NR R B mess ag e flushes i ts FD B . 17. When Node c and D receive the NR R B mes s age, they remove the block on their blocked ports 18 . S table normal conditio n all nodes g o to Idle state
Protection Switching Trigger Condition Protection switching trigger conditions: •
Fault C onditions – S ig nal Failure (S F):
local signal failure (local SF) will be submitted to protection trigger module once a failure is detected at endpoint.
– S ig nal Deg rade (S D): local signal degrade (local SD) will be submitted to protection trigger module once a signal degrade is detected
External commands – Manual s witch (MS ):
Maintenance command for temporarily switching normal traffic to working transport entity or protection transport entity, unless a higher priority switch request (i.e., FS, or SF) is in effect .
– Forced s witch (FS ): Maintenance command for temporarily switching normal traffic from working transport entity to protection transport entity, unless a higher priority switch request is in effect .
– Clear: This maintenance command clears all of the externally initiated switch commands listed above clearing the Maintenance command.
Revertive / Non-Revertive operation Non-revertive vs . R evertive Protection Operation Types : • Non-revertive operation – The normal traffic will not be switched back to the working transport entity even after a protection switching cause has cleared. •
R evertive Operation – The normal traffic is restored to the working transport entity after the condition (s) causing the protection switching has cleared. – In the case of clearing a command (e.g., Forced Switch), this happens immediately. – In the case of clearing of a defect, this generally happens after the expiry of a "Wait- to-Restore (WTR)" timer, which is used to avoid chattering of selectors in the case of intermittent defects. WTR (Wait to Res tore) Timer – In the revertive mode of operation, to prevent frequent operation of the protection switch due to an intermittent defect, a failed working transport entity must become stable in a fault -free state. After the failed working transport entity meets this criterion, a fixed period of time shall elapse before traffic channel uses it again. This period is called the wait-to-restore (WTR) period, (1 to 12 Min) In the revertive mode, when the protection is no longer requested, i.e., the failure condition has been cleared, a wait-to-restore state will be activated on the RPL owner node. This state shall normally time out and become a no request state. The wait-to-restore timer is deactivated when any request of higher priority pre-empts this state. In short, This is the number of seconds the RPL owner waits from receiving indication that topology has returned to its pre-failure state untill it actually operates according to that indication, i.e. blocks the RPL-port.
Protection Operation timers G uard Timer – R-APS messages are transmitted continuously. This, combined with the R-APS messages forwarding method, in which messages are copied and forwarded at every ring node around the ring, can result in a message corresponding to an old request, which is no longer relevant, being received by ring nodes. The reception of messages with outdated information could result in erroneous interpretation of the existing requests in the ring and lead to erroneous protection switching decisions The guard timer is used to prevent ring nodes from receiving outdated R-APS messages. During the duration of the guard timer, all received R-APS messages are ignored by the ring protection control process. This allows that old messages still circulating on the ring may be ignored. This, however, has the side effect that, during the period of the guard timer, a node will be unaware of new or existing ring requests transmitted from other nodes. The period of the guard timer may be configured by the operator in 10 ms steps between 10 ms and 2 seconds, with a default value of 500 ms. This time should be greater than the maximum expected forwarding delay for which one R-APS message circles around the ring.
Synchronization in iPASOLINK
Type of Synchronization Timing signalof system A
Frequency Synchronization :all nodes align in both clock and radio channel frequencies generated by the same frequency source.
T A=1/f A t Timing signalof systemB TB=1/f B
Phase Synchronization : all nodes have access to a reference timing signal whose rising edges occur at the same instant in time. This process is also referred to as relative-time synchronization or “adaptive frame alignment” in 3GPP mobile system. In phased 1PPS (pulse per second) signal is applied for phase synchronization of 3GPP2(cdmaOne/cdma2000)and WiMAX.
t Timing signalof system A
t Timing signalof systemB
Time Synchronization : Timing signal of system A 00:00:00 00:00:01
t 00:00:03 00:00:04
System A t Timing signal of system B 00:00:00 00:00:01
00:00:03 00:00:04
System B t
all nodes have access to the information on the reference time. The time synchronization is also referred to as time-of-day synchronization or wall-clock synchronization, where the clocks in question are traceable to a time-base such as UTC. Usually, this can be used as an alternate of phase synch. ToD( time of day) signals are applied for this synch..
Synchronous Ethernet Concept Uses the PHY clock – Generates the clock signal from “bit stream” – Similar to traditional SONET/SDH/PDH PLLs Each node in the Packet Network recovers the clock Performance is independent of network loading
There are four quality levels for clocks in SDH: Primary Reference Clock G.811 SSU Slave clock (local node) G.812
SSU Slave clock (transit node) G.812 SDH network element clock (SEC) G.813
IEEE1588v2 End-to-End Synchronization Concept (1) Boundary Clock (BC) Sync S
Sync
Sync S
M
S
M
PRC (Primary Reference Clock)
Sync S
M
M
CX2200
CX2600
All intermediate node terminates messages link-by-link.
(2) Transparent Clock (TC)
M
:Time synchronization Master
S
:Time synchronization Slave
Defined on version 2
PRC
Sync S
M
CX2200
CX2600 C t 3 = t 2 – t C Forwarding delay = t C
t 2 = t 1 – t B
B
Forwarding delay = t B
t 1 = t – t A
A
Forwarding delay = t A
t Clock (P DU Information) Timestamp = t
Intermediate node doesn’t terminate messages but add delay information node-by-node.
(3) Slave Clock (SC)
Defined on version 2 M
CX2200
CX2600 C S
B
A
PTP Server
Ethernet Cables
Ethernet Specification 10BASE-T 10BASE2 10BASE5 100BASE-X 100BASE-T
100BASE-FX 100BASE-TX
100BASE-T4 100BASE-T2
1000BASE- 1000BASE-LX 1000BASE-X FX 1000BASE-SX 1000BASE-CX 1000BASE-T 10GBASE-X
Speed 10M 10M 10M 100M 100M 100M 100M
Cable Type UTP cable (CAT3) Coaxial cable (50 ohms, diameter of 5mm) Coaxial cable (50 ohms, diameter of 10mm) Fiber optic cable (1300nm MMF) UTP cable (CAT5) UTP cable (CAT3) UTP cable (CAT3)
1000M Fiber optic cable (1300nm MMF) 1000M Fiber optic cable (1300nm SMF) 1000M Fiber optic cable (850nm MMF) 1000M Coaxial cable 1000M UTP cable (CAT5 e/CAT6)
10GBASE-TX1
10GBASE-SR 10GBASE-R 10GBASE-LR 10GBASE-ER 10GBASE-SW 10GBASE-LW 10GBASE-W 10GBASE-EW 10GBASE-LW4
Distance 100m 185m 500m 2000m 100m 100m 100m 550m 5000m 550m 25m 100m
10G Fiber optic cable (1310nm MMF)
300m
10G Fiber optic cable (1310nm SMF)
10km
10G 10G 10G 10G 10G 10G 10G
65m 10km 40km 65m 10km 40km 10km
Fiber optic cable (850nm MMF) Fiber optic cable (1310nm SMF) Fiber optic cable (1550nm SMF) Fiber optic cable (850nm MMF) Fiber optic cable (1310nm SMF) Fiber optic cable (1550nm SMF) Fiber optic cable (1310nm SMF)
Ethernet - 2 Ethernet Standards The standardization of LAN is conducted by the I EEE(Institute of Electrical and Electronics Engineers). It has already standardized many LAN-related technologies that we are familiar with in everyday life. They includes IEEE802.3, standards on the Ethernet, and IEEE802.11a/b/g, standards on the Wireless LAN. Standard
Layer 7 Application Layer Layer 6 Presentation Layer Layer 5 Session Layer
IEEE802.1
Layer 4 Transport Layer
Layer 3 Network Layer LLC
IEEE802.2
Layer 2 Data Link Layer MAC IEEE802.3 Layer 1 Physical Layer
..
Working Group
IEEE802.1
Higher Layer LAN Protocols
IEEE802.2
Logical Link Control
IEEE802.3
Ethernet
IEEE802.4
Token Bus
IEEE802.5
Token Ring
IEEE802.6
Metropolitan Area Network
IEEE802.7
Broadband
IEEE802.8
Fiber Optic
IEEE802.9
Isochronous LAN
IEEE802.10
Security
IEEE802.11
Wireless LAN
IEEE802.12
Demand Priority
IEEE802.14
Cable Modem
IEEE802.15
Wireless Personal Area Network (WPAN)
IEEE802.16
Broadband Wireless Access (W iMAX)
IEEE802.17
Resilient Packet Ring
IEEE802.18
Radio Regulatory
IEEE802.19
Coexistence
IEEE802.20
Mobile Broadband Wireless Access (MBWA)