New in iPASO Series Product and Ethernet Fundamentals

iPasolink O&M Training PAGE 0
What is new in iPASO Series Product ?
Latest NEC Radio Product

iPASO iPASO iPASO
NEO HP
1000 400 200
Hybrid ( Native Ethernet & TDM)

Packet Radio (PWE Inside)
VLAN
QoS QoS/Diffserve
Policer/Shaper
All IP PWE(E1)
Sync Ether
Clock Synch.
IEEE1588V2
OAM
Ethernet OAM
Hot Standby(1+1)
RF Link Aggregation
Link Protection E1 SNCP
RSTP
Ethernet Ring(G.8032)

Hub, Bridge & Switches

Ethernet Frame and MAC Address
The Ethernet is the most popular LAN technology, and represents the protocol 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) Ethernet Equipments
(HUB / Switch / Bridge)
Terminal B
Terminal A
Ethernet Frame MAC=222
MAC=111
SA DA
Data
MAC=111 MAC=222
DA SA
DA: Destination Address Data
MAC=111 MAC=222
SA: Origination Address

Collision Domain
HUB
HUB
Host C Host n
Host A Host B
Collision Domain
Collision Domain A Bridge / Switch / Router

Collision Domain B
HUB

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 Hub
1 234 5 6 7 8 1 2 3 4 5 6 7 8 9 10 11 12 1 234 56 7 8
Hub Hub
PCA PCB PCC PCA PCB PCC
12 3 4 5 6 7 8 1 234 5 6 7 8
PCA PCB PCC PCA PCB PCC

Ethernet Frame and MAC Address
Usual untagged Ethernet Frame: Normal PC
Max. MTU 1518 Byte
Ethernet Frame Format
Preamble SFD DA SA Length Data

FCS
(7B) (1B) (6B) (6B) (2B) (46 to 1500B)
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 A 00-00-00-00-00-01
4 D 00-00-00-00-00-04
1 2 3 4
Dst MAC: D Dst MAC: A

Src MAC: A Src MAC: D
MAC A
MAC B MAC C MAC D 00-00-00-00-00-04
00-00-00-00-00-01

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 different VLAN group
VLAN setting
Broadcast frame is
Broadcast frame is not
transmitted to all port
transmitted to different
except received port
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 administrators manpower for replacing and
moving network devices. When a user moves to another subnet, it is necessary to reset all
addresses of the users 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 the 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 makes it possible to construct or
modify the network more easily and flexibly.
VLAN2 VLAN3
(Department B) (Department C)
HUB VLAN Switch
2nd Floor (Department B) 2nd Floor
HUB VLAN Switch
VLAN-1(Department A)
1st Floor (Department A) 1st Floor
Need to change Just change setting, not

physical connections physical connections
Router Router/L3 Switch
Conventional LAN 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 VLAN 2 VLAN 3
iPASO200 named
Tag Based VLAN it as Trunk VLAN type
(VLAN ID 10)
VLAN SW VLAN SW
1 1 (VLAN ID 10)
2 2
3 3
(VLAN ID 20) 4 4
5 5
6 6 (VLAN ID 20)
Tag 10
Tag 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
Max 1518 Bytes

Usual
Ethernet Max MTU Size = 1500bytes (Ethernet Standard)
1500 18 Max Frame Size = 1518bytes
Frame
802.1q Max 1522 Bytes

Ethernet
Max MTU Size = MTU1500bytes + 4 bytes VLAN Tag
Frame 1500 4 18 Max Frame Size = 1522 Bytes
Q in Q Max 1526 Bytes Max MTU Size = MTU1500bytes + (2 x 4 bytes VLAN

Ethernet Tag)
Frame 1500 4 4 18 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 Company B
VLAN100 VLAN100
Data 100 Data 100
Data 100 300

Data 100 200 Common Network
Data 100 Data 100

VLAN100 VLAN100
Company A Company B

Ethernet Packet Format
Tag VLAN is standardized by IEEE802.1q

VLAN tag (4byte) is inserted to Ethernet frame
IFG Preamble Destination Source MAC VLAN Length Data FCS

MAC address tag / type
12 Byte 8 Byte address (SA) 46 - 1500byte 4byte
(DA) 6byte 4byte 2byte
6byte
802.1q tag type TCI field

Example: traffic assignment 2byte 2byte Range: 1 - 4094
7 (High) Traffic management (0, 4095 reserved)
6 Voice
5 Video
Priority CFI VLAN-ID
4 Control signal
3bit 1bit 12bit
3 Excellent effort
CoS value
2 Best effort
1 Reserved
IFG: Inter Frame Gap
0 (Low) Background CFI: Canonical Format Indicator
TCI: Tag Control Information
TOS: Type Of Service

QoS Bit Assignment in Ethernet Frame
CFI: Canonical Format Indicator
DSCP: Differentiated Services Code Point
TCI: Tag Control Information TPID: Tag Protocol Identifier
802.1q Q-in-Q COS: Class Of Service
To MAC Fm MAC TPID TCI Type IP Header IP data FCS

Address Address
2Bytes 2Bytes
Priority CFI VLAN
VLAN Tag 8100 bit ID
To MAC Fm MAC TPID TCI TPID TCI Type IP Header IP data FCS
Address Address
Priority CFI VLAN Priority CFI VLAN

VLAN Tag-2(outer) 8100 bit ID 8100 bit ID VLAN Tag-1 (inner)
802.1ad Q-in-Q
To MAC Fm MAC TPID TCI Type IP Header IP data FCS
Address Address
2Bytes 2Bytes
Priority CFI VLAN
VLAN Tag 8100 bit ID
To MAC Fm MAC TPID TCI TPID TCI Type IP Header IP data FCS
Address Address
Priority CFI VLAN Priority CFI VLAN

VLAN Tag-2(outer) 88a8 bit ID 8100 bit ID VLAN Tag-1 (inner)

Overall view of iPASOLINK L2 Switch
MC-A4
Main Board In-band In-band
1.Access FE1/GbE FE1/GbE
FE1/GbE 1. Access FE1/GbE

Modem1 Mod(slot1)
2.Trunk Trunk
FE1/GbE L2 SW Modem2 VLAN 2. Trunk
/GbE
L2 SW Mod (slot2)
Trunk
3.Tunnel FE1/GbE GbE Mod (slot3) VLAN
3.Tunnel
GbE Mod (slot N)
NMS NE
NMS NE
GbE
iPASOLINK 200 , 802.1q iPASOLINK 400/1000 , 802.1q
Main Board In-band

1.Access FE1/GbE
FE1/GbE
Modem1 iPASOLINK 400/1000 , 802.1ad
2.Trunk Trunk
GbE L2 SW VLAN
MC-A4 In-band
3.Tunnel GbE FE1/GbE
1. C-Access FE1/GbE
Mod(slot1)
NMS /GbE
2. S-Trunk L2 SW Mod (slot2)
S-Trunk
GbE Mod (slot3) VLAN
iPASOLINK 100E , 802.1q 3.C-Bridge
Mod (slot N)
NMS NE
iPASOLINK 200 , 802.1ad

not available

VLAN Modes
VLAN MODE Port Type Direction Action

Ingress Add C-VID to untagged frames (drop tagged frames)
Access
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
Transparent for the assigned VLAN IDs (Drop untagged frames). Add C-
IEEE 802.1q Trunk Ingress
VID to untagged frames
(With Untagged Frame
assignment)
Transparent for the assigned VLAN IDs
Egress
Remove C-Tag (outer tag) matching the Access port VID
Ingress Add C-VID to C-Tag or untagged frames as outer tag
Tunnel Remove the C-tag (outer tag) matching the C-VID assigned to the tunnel
Egress
port
Ingress Add the S-VID to Untagged and C-tagged frames (as outer tag)
C-Access Remove the S-tag (outer tag) matching the S-VID assigned to C-Access
Egress
port
IEEE 802.1ad Ingress Transparent for the assigned S-VLAN IDs. (drop untag, c-tag frames)
S-Trunk
Egress Transparent for the assigned S-VLAN IDs
Ingress Adds S-VID to defined C-Tagged frames
C-Bridge
Egress Remove the S-VID from defined C-Tagged frames
Egress
Ingress Ether Modem Modem ports always Trunk
Port Port Ingress (802.1q) or S-Trunk (802.1ad)
Egress

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: Modem 1:
Access Trunk
VLAN 10 VLAN 10
Drop
Recommendation: To be used for base station with un-tag traffic

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 2 Send with VLAN 2 Set for Un-tag packet
Data 20 20 Send with VLAN 20

Data
FE Port 2: iPASO200 Modem 1:

Data 100 Access LAN 2 Trunk VLAN 2, 20
Trunk VLAN 20
Drop
Recommendation: To be used for base station with VLAN tag interface

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 30 Add on tag VLAN30
Data 20 Data 20 30 Add on tag VLAN 30
No packets will iPASO200 Modem 1:

FE Port3:
be drooped Trunk VLAN 30
Tunnel 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 2 Data 2
Data 30 Data 30
Data 20 Data 20 Modem 1:

Data 40 Trunk
Data 10 Data 10 VLAN 2,10,20,30
Drop
iPASO200

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- C-VLAN MSG FM- To- S-VLAN C-VLAN MSG

A B any A B 200 Y
FM- To- MSG FM- To- S-VLAN MSG

A B A B 200
P1 (FE)
FM- To- S-VLAN C-VLAN MSG

A B any any Modem port Type: S-Trunk
S-VLAN: 100, 200,300

VLAN Mode 802.1ad- Example of S-Trunk Port
802.1ad
At port 1, Frames without a S-Tag

will have S-VLAN ID 200 and
forwarded (both untagged and
with any C-tag)
Frames with S-VLAN IDs
100,200,300 are only passed. Any
othe S-VLAN ID will be dr opped

A B any A B 200 any
FM- To- MSG FM- To- S-VLAN MSG
A B A B 200
FM- To- S-VLAN C-VLAN MSG FM- To- S-VLAN C-VLAN MSG
A B 100 any A B 100 any
FM- To- S-VLAN C-VLAN MSG FM- To- S-VLAN C-VLAN MSG
A B 300 any A B 300 any
P1 (FE)
Modem port Type: S-Trunk
A B other any
S-VLAN: 100, 200,300

VLAN Mode 802.1ad- Example of C-Bridge Port
In the example shown: 802.1ad
Only frames with C-VLAN IDs, defined will pass at
port1 with corresponding S-VLAN inserted:
C-VLAN 10, 20 will be inserted with S-VLAN 100 and
forwarded
C-VLAN 25, 30 will be inserted with S-VLAN 200 and
forwarded
All the other C-VLANs are dropped
Any S-VLANs are dropped

A B 25,30 A B 200 25,30
A B 10,20 A B 100 10,20
FM- To- C-VLAN MSG
A B other S-VLAN: 100, 200,300
Modem port Type: S-Trunk
A B 200 25,30 P1 (FE)
FM- To- S-VLAN C-VLAN MSG A B 200 25,30
A B 100 10,20
FM- To- S-VLAN C-VLAN MSG A B 100 10,20
A B 300 any
FM- To- MSG
A B

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 Scheduling/Shaping
Classify/Policing
Scheduling/Shaping
Classify/Policing Scheduling/Shaping
FE Port Modem Port Modem Port FE Port
Ingress
Egress

QoS Bit Assignment in Ethernet Frame
1) IP Packet ToS(3bit)
DSCP/Diffserve(6bit) IP ECN Explicit Congestion Notification
Version Header TOS IP address etc.

Length
8bits
To MAC Fm MAC Type TCI Type IP Header IP data FCS

Address Address
2Bytes
CFI: Canonical Format Indicator
VLAN Tag Priority CFI VLAN
bit (CoS) ID TCI: Tag Control Information
3bits COS: Class Of Service
(802.1q CoS) DSCP: Differentiated Services Code Point
2) MPLS Packet
MPLS MPLS IP Header IP data

Label Label
3bits
Label Exp S TTL
EXP : experimental bits ( iPASO200 will supports in future)

Ether Functions
Protected
TDM TDM Radio
Radio Capacity
Packet
Capacity
Packet Policing/Shaping
according to QoS
TDM
Port Ingress Setting Port Egress Setting

Egress Queue
Classification TDM
Determine
Ingress Policer +
equipment Packe
internal priority Token Token Internal Priority Queuing Class 3 queue Sent t
Policy per ingress Port
frames QoS
VLAN CoS
IPv4 precedence Packet
Class 2 queue
IPv4/v6 DSCP
MPLS EXP Token
Ether Token
bucket bucket
Class 1 queue Scheduling &
Two-Rate, (CIR & EIR) Shaping User can define TDM
Three-Color Metering
Class 0 queue bandwidth for each
radio modulation
Color Blind 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
Egress Port ETH Port 1 MODEM Port-1
Egress Class Egress Class

Queues Queues
Egress Port
Ingress Port
Ingress Egress MODEM Port-2

Classification
Policer Classify
Egress Class
Queues
Egress Port
Input frame priority Internal Priority (0-7) Internal Priority (0-7) Class queue (0-3)
(CoS, DSCP, EXP, etc)
Internal 0 Class 0
CoS 0 Internal 0 Internal 1
CoS 1 Internal 1 Internal 2 Class 1
CoS 2 Internal 2 Internal 3
: Internal 3 Internal 4 Class 2
: Internal 4 Internal 5
Internal 5 Internal 6 Class 3
Internal 6 Internal 7
Internal 7
In Equipment base QoS, uses one profile per Enables to prepare total three mapping profiles.
equipment. In Port base QoS, enables to Sets profile from three profiles per output port (ETH, MODEM).
prepare mapping profile per port.

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)
iPasolink O&M Training PAGE 31 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 CoS (C-Tag) DSCP IPv4/v6
Untag IP packet Default Port Priority Default Port Priority DSCP IPv4/v6
Non-IP packet Default Port Priority Default Port Priority Default Port Priority
Tagged IP packet Default Port Priority CoS DSCP IPv4/v6
Non-IP packet Default Port Priority CoS Default Port Priority
iPasolink O&M Training PAGE 32 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 Profile No.0 (ex) Profile No.1 (ex) Profile No.2
precedence
IPv4/v6 DSCP Internal IP Internal Internal
VLAN CoS DSCP
priority Precedence priority priority
MPLS EXP
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 / Port 1 IP packet / VLAN 10

SA DA SA DA
Non-IP packet (Access) Non-IP packet CoS X
VLAN-10
X=Other setting for non IP frame
X= IP Precedence for IP frame
IP packet / VLAN 20 IP packet / VLAN

SA DA Port 2 20 SA DA
Non-IP packet CoS Y Non-IP packet Cos Y
(Trunk)
VLAN-20
Pass with the incoming VLAN tag
IP packet / VLAN 50 Inner Outer

SA DA Port 3 IP packet / VLAN VLAN
Non-IP packet CoS Y SA DA
(Tunnel) Non-IP packt 50 40
CoS Y CoS Y
VLAN 40
IP packet / VLAN
SA DA IP packet /
Non-IP packet 40 SA DA
Non-IP packet CoS X
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
Port type Internal priority Policing

Access DPP-7 DPP-7
Trunk DPP-6 CoS-0
iPASOLINK
Modem Tunnel DPP-5 DPP-0
(trunk)
Port mode
IP packet / Port 1 IP packet / VLAN

SA DA Tag SA DA
Non-IP packet (Access) Default Port Non-IP packet (CoS7)
Port No.
priority
Update CoS value to
1 7 Default port priority value
2 6
3 5
IP packet / VLAN Tag IP packet / VLAN
SA DA Port 2 4 4 Tag SA DA
Non-IP packt (CoS0) Non-IP packet (CoS6)
(Trunk) MODEM 1 3
MODEM 2 2 Update CoS value to
Default port priority value
MODEM 3 1
MODEM 4 0
IP packet / VLAN Tag Inner Outer

SA DA Port 3 IP packet / VLAN VLAN
Non-IP packt (CoS0) SA DA
(Tunnel) Non-IP packt Tag Tag
(CoS0) (CoS5)
Use Default port priority value as CoS value

Port Based QoS classification CoS Mode (2/3)
Classifies according to CoS value

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

SA DA Tag SA DA
Non-IP packet (Access) Non-IP packet (CoS1)
Update CoS value to Default
port priority value
IP packet / VLAN IP packet / VLAN

Tag SA DA Port 2 Tag SA DA
Non-IP packet (CoS0) (Trunk) Non-IP packet (CoS0)
No update CoS value
Inner Outer
IP packet / VLAN IP packet /
Port 3 VLAN VLAN
Tag SA DA SA DA
Non-IP packet Non-IP packet Tag Tag
(CoS5) (Tunnel)
(CoS5) (CoS5)
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
iPASOLINK Modem
IP header Port 1 (trunk) IP header VLAN
IP packet SA DA IP packet Tag SA DA
(DSCP63) (Access) (DSCP63) (CoS7)
DSCP IPv4/v6 mode
IP header VLAN Port 2 IP header VLAN

IP packet Tag SA DA DSCP Classification Mapping IP packet Tag SA DA
(DSCP47) (CoS7) (Trunk) (DSCP47) (CoS5)
Internal
DSCP
priority Inner
VLAN Outer
IP header Port 3 IP header
IP packet Tag SA DA 63 7 VLAN VLAN
IP packet SA DA
(DSCP31) (CoS7) (DSCP31) Tag Tag
(Tunnel) : : (CoS7) (CoS3)
Classifies by this value 47 5
: :
31 3 VLAN
Non-IP packet SA DA Port 1 Non-IP packet Tag SA DA
(Access) : : (CoS1)
15 1
0 0 VLAN
VLAN Non-IP packet Tag SA DA
Non-IP packet Tag SA DA Port 2
(CoS1)
(CoS7) (Trunk)
Inner Outer
VLAN VLAN VLAN
D Non-IP packet SA DA
Non-IP packet Tag SA DA Port 3 Tag Tag
(CoS7) Default Port priority = 1 (CoS7) (CoS1)
(Tunnel)
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
Access 7 7
iPASOLINK Trunk 5 0
Modem
Tunnel 3 0
<Case1: VLAN ID is registered> (trunk)
VLAN ID Based QoS mode (VID10,20,30)
Default Priority = 1
SA DA Internal 10 SA DA
Non-IP packet (Access) VLAN ID Non-IP packet (CoS7)
priority
(VID10)
10 7 Use internal priority value
for outer VLAN ID(*)
20 5
30 3
IP packet / VLAN Port 2 IP packet / VLAN
20 SA DA 40 1 20 SA DA
(VID20)
No update CoS value
Inner Outer
VLAN IP packet / VLAN VLAN
IP packet / SA DA
20 SA DA Port 3 Non-IP packet 20 30
Non-IP packet (CoS0) (CoS0) (CoS3)
(Tunnel)
(VID30) Outer
IP packet / IP packet / VLAN
SA DA SA DA
Non-IP packet Non-IP packet 30
(CoS3)
Use internal priority value

(*) If outer VLAN ID which is added is not registered to mapping table, Default Priority is used as internal priority and CoS 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
<Case2: VLAN ID is not registered> (trunk)

VLAN ID Based QoS mode (VID60,70,80)
Default Priority = 1
SA DA Internal 60 SA DA
Non-IP packet (Access) VLAN ID Non-IP packet (CoS1)
priority
(VID60)
10 7 Use Default Priority value
20 5
30 3
IP packet / VLAN Port 2 IP packet / VLAN
70 SA DA 40 1 70 SA DA
(VID70)
No update CoS value
Inner Outer
IP packet / VLAN IP packet / VLAN VLAN
70 SA DA Port 3 SA DA
Non-IP packet 70 80
Non-IP packet (CoS0)
(Tunnel) (CoS0) (CoS0)
IP packet / (VID80)
Outer
SA DA IP packet /
Non-IP packet VLAN
SA DA
Non-IP packet 80
(CoS1)
(*) If outer VLAN ID which is added is not registered to mapping table, Default Priority is used as internal priority and CoS value. 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.
CBS/EBS should be set depend on traffic

Our Recommendations: 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
EIR
[Amount of Traffic] Complying Frames CIR
[Time]
Ingress Policing (per port / per VLAN/priority) Yellow Green
Rate Check Conforming Frames

Marking to Green
Green
Committed <
Rate Token
Bucket Rate Check Exceeding Frames Green
> Marking to Yellow
Exceeded
Rate Token
<
Bucket
High priority
> Violating Frames
Middle priority
Marking to Red,
Drop and discard
Low priority
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
15Mbps CIR 20 Mb
EIR
Recognize the
15Mbps EIR service according to
DSCP/TOS/IP and 10 Mb
prioritize it. CIR
0 Mb
VLAN 20
Video Conf. iPASO400
iPASO200
Voice
Data / VPN 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 Determination.
Strict Priority Queuing (SPQ), Weighted Control (WRR) can be used as queuing method.
High Priority Round Robin (RR)
Police Car ETC Car
ETC Car
ETC System
Electronic Toll Collection System

Deficit Round Robin
75 Credits
50 100 Credit counter:
50 50 50 75 Initially the counter start or reset from zero.
For this example, it was set to size value
50 50 50 75
of 75 for all the queue. When the queue is
150 75 not serve to send any packet, the credit
counter will be increased with another 75
50 100 75 Credits 1st round:
The first and fourth queue packet size is
50 50 25 50 50 bigger than credit counter value, these
50 50 25 two queue will hold back and not sending
Time
any packets, but second and third queue

150 75
sent out 50 packets. And their credit
150 Credits counter reduce to 25.
50 100 50 100
50 50 100 2nd round:
50 50 The first and fourth queue counter credit
50 50 100 increase to 150 byte
50 50
150 150 The result is Q1 send 150 byte
150 Q2 send 100 byte
Q3 send 100 byte
7 Credits Q4 send 150 byte
5
75 3rd round:
75 All credit counter with value 75 byte
75

Egress Scheduling and Shaping (4 Class queue)
Classify (Mapping) for Egress Class 3 Scheduling and Shaping

Queue with internal priority
Shaper
Class 2
Shaper SP Shaper
Class 1 DWRR
Shaper
Shaper Class 3 absolute priority

Class 0 Divided throughput
by weighted condition
Mapping table is
Configurable.
SP or 1SP + 3 DWRR or 4 DWRR
WTD/WRED discard based on color
(Green/Yellow)

Egress Scheduling and Shaping ( 8 class queue)
Classify (Mapping) for Egress Class 5

Scheduling and Shaping
Queue with internal priority
Class 7
Shaper
Class 6
Class 5
Shaper SP Shaper
Class 4
DWRR
Class 3 Shaper
Class 2 Class 7 absolute priority

Shaper
Divided throughput
Class 1
by weighted condition
Class 0
Mapping table is
Configurable.
1SP + 7 DWRR or 2SP + 6 DWRR
WTD/WRED discard based on color
(Green/Yellow)

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 Classification
CoS 7 Pri 7 Class 3 CoS=7 100Mbps
100Mbps
CoS 6 Pri 6 Class 3 CoS=5 100Mbps
CoS=5 CoS 5 Pri 5 Class 2 250M CoS=3 50Mbps
100Mbps CoS 4 Pri 4 Class 2
CoS=3
1000M CoS 3 Pri 3 Class 1 CoS=0 0Mbps
CoS2 Pri 2 Class 1
CoS=0 CoS 0 Pri 0 Class 0 4SP
100Mbps
Weighted Round Robin uses a number that indicates the importance (weight) of each queues. WRR 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.
Classification
CoS 7 Pri 7 Class 3
CoS=7
CoS 6 Pri 6 Class 3 DRR Weight CoS=7 100Mbps
100Mbps
CoS 5 Pri 5 Class 2 Class 3: - CoS=5 80Mbps = (240-100)*4/(1+2+4)
CoS=5 CoS 4 Pri 4 Class 2
CoS 3 Pri 3 Class 1
Class 2: 4 240M CoS=3 40Mbps = (240-100)*2/(1+2+4)
100Mbps Class 1: 2
1000M CoS2 Pri 2 Class 1 Class 0: 1 CoS=0 20Mbps = (240-100)*1/(1+2+4)
SP class is absolute priority traffic.
CoS=0 1SP+3DWRR The remaining bandwidth is distributed in
100Mbps
other classes according to DRR weight.
(e.g. remaining BW = 240-100=140Mbps)
Classification
CoS 7 Pri 7 Class 3
CoS=7
CoS 6 Pri 6 Class 3 DRR Weight CoS=7 80Mbps = 200*4/(1+2+3+4)
100Mbps
CoS 5 Pri 5 Class 2 Class 3: 4 CoS=5 60Mbps = 200*3/(1+2+3+4)
CoS 3 Pri 3 Class 1
Class 2: 3 200M CoS=3 40Mbps = 200)*2/(1+2+3+4)
100Mbps Class 1: 2
1000M CoS2 Pri 2 Class 1 Class 0: 1 CoS=0 20Mbps = 200*1/(1+2+3+4)
The port bandwidth is distributed in all
CoS=0 4DWRR classes according to DRR weight.
100Mbps

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
Not slow..
connecte
d well
Traffic Early detect and

Concentration restrain
Bandwidth
Bandwidth
Window Size decrease globally Average Utilization

Average Utilization
Time
Time
Effective Window size variation

Congestion Avoidance ( Discard Control)
iPASO200 support Weight Tail Drop at Release Threshold2

1.07and later with WRED (75%)
Congestion avoidance techniques on the Threshold3 Threshold1
egress queues. (100%) (50%)
Both techniques will drop packets when pre-
configured thresholds on the egress queues
have been reached.
Weighted Tail Drop (WTD), with thresholds

Setting on each queue, for congestion
avoidance
Queuing Priority1: 0% discard

Queuing Priority2: 0 discard
Queueing Priority1:100%discard
Queueing Priority1:100%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.
Provider X
BTS/Node-B Operator A Operator B BSC/RNC
CC
LB
LT
Y.1731 Performance Management not yet supported

By iPASO200

Ethernet OAM
Function Y.1731 802.1ag Mechanism

Connectivity Fault
Management
Fault Detection
CCM
Fault verification-Loop back

LBM / LBR
Fault isolation
LTM / LTR
Discovery
LTM / LTR
Fault Notification
- AIS RDI
Performance
Monitor
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)
Provider Level (MEG level:3-4) : MEP

Operator Level (MEG level:0-2) : MIP
MEG Operator Level (MEG level:0-2) Operator Level (MEG level:0-2)
Operator Level (MEG level:0-2)
Provider X
Customer Operator A Operator B Operator C Customer
1 2 3 4 5 6 7 8 9 10 11
LB LB
(MEG level:0) (MEG level:0)
CC LT LB
(MEG level:2) (MEG level:2)
(MEG level:2)
CC
(MEG level:4)
CC
(MEG level:7)
Several level can be managed at same time in the same network

Example of Maintenance Entities
Provider X
Customer Operator A Operator B Customer
1 2 3 4 5 6 8 9
Customer
Level (5-7)
Service
Provider
Level (3-5)
Operator
Level (0-2)
Maintenance Entity Points

Maintenance Entities
Maintenance Intermediate Points

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 3 4
TTL=n TTL=n-1 TTL=n-2

Legend
TTL=n : MEP
TTL=n-1 : MIP
TTL=n-2
: 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 DOWN
MEP/MIP 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
MODEM
L2SW MODEM LAN
LAN
Reply frame OK
Reply frame NG Reply frame NG ETH-CC/LB/LT
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 supported

For this application, ETH-CC/LB/LT reply frame only at MODEM port
The MEP should be set only at Modem port
ETH OAM Setting
Maintenance Domain Name: NEC
iPASOLINK200 supports only Down MEP/MIP
Short MA name: NEC
Meg Level: 7 Ether OAM reply frame from Switch to LAN/MODEM port outward direction is okay
CCM: Enable
But from LAN/MODEM toward Switch directional is not supported
ETH CC period : 3.3 ms
CCM Priority : 7
iPaso400-B iPaso1000-C
iPaso200-D iPaso200-A
iPaso400-F iPaso200-E M2 M1 M1
M2 M1 H L M1 M2 H L
H L M1 M2
M1 ODU-1 ODU-3
ODU-Back 23GHz 7GHz
23GHz
22030 / 23038 7310/7156
22484 / 21252 P1 P2
P1 P2
MEP1 MEP2
MIP MIP
MIP MIP
iPaso200-D iPaso200-A iPaso400-B

iPaso400-F iPaso200-E M2
M1 H L M1 M2 Mep2
H L M1 M2
M1 ODU-1
ODU-Back 23GHz
23GHz
22030 / 23038
22484 / 21252
P1 P2
Mep1
Mep3 MIP MIP
M2
ODU-4
7GHz iPaso1000-C
7310/ 71560 M2 Mep4

LINK OAM Alarm & Status
A flag in the OAMPDUs allows local device to convey failure
Discovery Msg event to its peer.
(Active)
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
Critical Event Msg Critical Event Msg
e.g. Radio link failure

e.g. Module failure
Equipment which is
able to monitor Link
Loopback control Msg
Loopback 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
ETH-CC Traffic separation
with VLAN Tag
RPL (Ring Protection Link)

Blocked port
Client #2
Signal
RPL (Ring Protection Link)

Blocked 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 for discovery and identification of Signal Failure (SF) conditions.
Protection and recovery switching within 50 ms for typical rings.
Blocking Unblock
Port blocking Port
Client Traffic Submission of

FDB Flush,
Unblock blocking Port
1) Normal Condition 2) Failure Event 3) Switchover Condition

Failure monitoring
G.8032 utilizes the following monitoring functions to detect link / node failures 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
Failure Detection time = 3.33 msec * 3.5 = 11.7msec Client Traffic
cc
MEP-2 cc
Submission of
MEP-3 FDB Flush,
MEP-1 cc
MEP-2 MEP-3
cc
MEP-4
MEP-1
MEP-4
MEP-8
MEP-5 LOC cc
cc MEP-7 MEP-8
cc
MEP-6 cc
MEP-5
cc MEP-7
LOC
1) Normal Condition MEP-6 cc
2) Failure Event LOC
ETH-CC enables to detect failures on several conditions which cc

cc
physical layer monitoring cant do. 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
User B can be achieved.
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
Failure
1GbE 1GbE
2GbE 1GbE
Double QoS
discarding
capacity
GbE Ring
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).
Physical
User VLAN group #1
APS channel #1 Instance #1
(Link Monitoring) ETH-CC-1
User VLAN group #2

(Link Monitoring)ETH-CC-2
User VLAN group #3

(Link Monitoring) ETH-CC-3

Ring Types

Scenario A - Normal to Protection
RPL
Node-G
Node-A Node-B Node-C Node-D Node-E Node-F RPL Owner

1
NORMAL 2 failure
STATE
3
4
Flush SF SF SF
50 ms
SF SF
Flush Flush Flush Flush
Flush Flush
PROTECTION 5
STATE
6
SF SF
SF SF SF
SF
7
1 . Normal State Node-G is the RPL Owner 6 . When the RPL owner receives the SF message it
unblock the RPL link
2 . Failure Occurs
7 . Stable State SF messages on the ring . Further
3 . Node D and Node C detect local signal fail SF messages does not trigger further action
condition. After waiting for the Hold-Off timer to
end block the failed ports
4 . While the SF condition continues Node C and Message source
Node D periodically send SF (signal Fail) Messages Client ch block
on both ring ports
R-APS ch block
5 . Each node performs a FDB flush operation after
receiving the SF message

Scenario B recovery
Node-A Node-B Node-C Node-D Node-E Node-F Node-G
RPL Owner
failure
8
SF SF
SF SF
SF SF
9 recovery
PROTECTION 10 NR
Confirmation time
STATE NR
NR NR NR
NR
11
12
13
NR,
NR, RPL Blocked
50 ms
NR, RPL Blocked
RPL Blocked Flush
14 Flush Flush
Flush
NORMAL Flush
STATE Flush Flush
15 NR,
NR Blocked
RPL
NR, NR,
RPL Blocked RPL Blocked
9 . In Stable SF condition Node C and D continue to send SF 14. When the Guard timer at Node C and D expire they may start receiving
messages every 5sec. new R-APS messages
10 . Recovery of failure 15. At the expiration of WTR timer, RPL owner blocks its end of of the
11 . Node C and D detects clearing of SF condition and start the RPL link, sends NR RB message
guard timer and initiate periodical transmission of NR messages on 16. Each node after re3ceivng the NR RB message flushes its FDB.
both ring ports (guard timer prevents reception of R-APS messages 17. When Node c and D receive the NR RB message, they remove the
12. When RPL owner receives the NR message, it starts the Wait to block on their blocked ports
Restore Timer (WTR) 18 . Stable normal condition all nodes go to Idle state
Protection Switching Trigger Condition
Protection switching trigger conditions:

Fault Conditions
Signal Failure (SF): local signal failure (local SF) will be submitted to protection trigger
module once a failure is detected at endpoint.
Signal Degrade (SD): local signal degrade (local SD) will be submitted to protection trigger
module once a signal degrade is detected
External commands
Manual switch (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 switch (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. Revertive 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.
Revertive 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 Restore) 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
Guard 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

TA=1/fA clock and radio channel frequencies generated by
the same frequency source.
t
Timing signalof systemB
TB=1/fB
Phase Synchronization all nodes have access to a
reference timing signal whose rising edges occur at the
t
same instant in time. This process is also referred to as
Timing signalof systemA
relative-time synchronization or adaptive frame
alignment in 3GPP mobile system. In phased 1PPS
(pulse per second) signal is applied for phase
t synchronization of 3GPP2(cdmaOne/cdma2000and
Timing signalof systemB WiMAX.
Time Synchronization
Timing signal of system A t all nodes have access to the information on
the reference time. The time synchronization is
00:00:00 00:00:01 00:00:03 00:00:04 also referred to as time-of-day synchronization
System A or wall-clock synchronization, where the clocks
t in question are traceable to a time-base such
Timing signal of system B as UTC. Usually, this can be used as an
alternate of phase synch. ToD( time of day)
00:00:00 00:00:01 00:00:03 00:00:04 signals are applied for this synch..
System B
t
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 (transit node) G.812
SSU Slave clock (local node) G.812 SDH network element clock (SEC) G.813
IEEE1588v2 End-to-End Synchronization Concept
(1) Boundary Clock (BC) PRC (Primary Reference
Clock)
Sync Sync Sync Sync
S M S M S M S M
CX2200 CX2600
All intermediate node terminates messages link-by-link. M :Time synchronization Master
S :Time synchronization Slave
(2) Transparent Clock (TC) Defined on version 2

PRC
Sync
S M
CX2200 CX2600
t3 = t 2 tC C t2 = t 1 tB B t1 = t tA A t
Forwarding Forwarding Forwarding Clock (PDU Information)
delay = tC delay = tB delay = tA Timestamp = t
Intermediate node doesnt terminate messages but add delay information node-by-node.
(3) Slave Clock (SC) Defined on version 2

M
PTP Server
CX2200 CX2600
C B A
S

Ethernet Cables
Ethernet Specification Speed Cable Type Distance

10BASE-T 10M UTP cable (CAT3) 100m
10BASE2 10M Coaxial cable (50 ohms, diameter of 5mm) 185m
10BASE5 10M Coaxial cable (50 ohms, diameter of 10mm) 500m
100BASE-FX 100M Fiber optic cable (1300nm MMF) 2000m
100BASE-X
100BASE-TX 100M UTP cable (CAT5) 100m
100BASE-T
100BASE-T4 100M UTP cable (CAT3) 100m
100BASE-T2 100M UTP cable (CAT3) 100m
1000M Fiber optic cable (1300nm MMF) 550m
1000BASE- 1000BASE-LX
1000M Fiber optic cable (1300nm SMF) 5000m
1000BASE-X FX
1000BASE-SX 1000M Fiber optic cable (850nm MMF) 550m
1000BASE-CX 1000M Coaxial cable 25m
1000BASE-T 1000M UTP cable (CAT5 e/CAT6) 100m
10G Fiber optic cable (1310nm MMF) 300m
10GBASE-X 10GBASE-TX1
10G Fiber optic cable (1310nm SMF) 10km
10GBASE-SR 10G Fiber optic cable (850nm MMF) 65m
10GBASE-R 10GBASE-LR 10G Fiber optic cable (1310nm SMF) 10km
10GBASE-ER 10G Fiber optic cable (1550nm SMF) 40km
10GBASE-SW 10G Fiber optic cable (850nm MMF) 65m
10GBASE-LW 10G Fiber optic cable (1310nm SMF) 10km
10GBASE-W
10GBASE-EW 10G Fiber optic cable (1550nm SMF) 40km
10GBASE-LW4 10G Fiber optic cable (1310nm SMF) 10km

Ethernet - 2
Ethernet Standards
The standardization of LAN is conducted by the IEEEInstitute 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 Working Group
IEEE802.1 Higher Layer LAN Protocols
Layer 7 Application Layer
IEEE802.2 Logical Link Control
IEEE802.3 Ethernet
Layer 6 Presentation Layer
IEEE802.4 Token Bus
IEEE802.5 Token Ring
Layer 5 Session Layer
IEEE802.1 IEEE802.6 Metropolitan Area Network
IEEE802.7 Broadband
Layer 4 Transport Layer
IEEE802.8 Fiber Optic
IEEE802.9 Isochronous LAN
Layer 3 Network Layer IEEE802.10 Security
IEEE802.11 Wireless LAN
LLC IEEE802.2 IEEE802.12 Demand Priority
Layer 2 Data Link Layer IEEE802.14 Cable Modem
MAC
IEEE802.15 Wireless Personal Area Network (WPAN)
IEEE802.3 ..
IEEE802.16 Broadband Wireless Access (WiMAX)
Layer 1 Physical Layer
IEEE802.17 Resilient Packet Ring
IEEE802.18 Radio Regulatory
IEEE802.19 Coexistence
IEEE802.20 Mobile Broadband Wireless Access (MBWA)

Thank you
This training document describes the current version of the equipment.

The specifications or configuration contained in this document are subject to change
without notice.

New in iPASO Series Product and Ethernet Fundamentals

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

New in iPASO Series Product and Ethernet Fundamentals

Uploaded by

Copyright:

Available Formats

iPasolink O&M Training PAGE 0

What is new in iPASO Series Product ?

Latest NEC Radio Product

Hybrid ( Native Ethernet & TDM)

iPasolink O&M Training PAGE 1

iPasolink O&M Training PAGE 2

iPasolink O&M Training PAGE 3

Collision Domain A Bridge / Switch / Router

iPasolink O&M Training PAGE 4

L2 Switch performs the frame forwarding based on Ethernet MAC

PCA PCB PCC PCA PCB PCC

Preamble SFD DA SA Length Data

MAC Address Format

Uni-cast (0) / Multi-cast (1) address

Frame transmission on Ethernet switch is realized by MAC address learning

MAC Address Table

Dst MAC: D Dst MAC: A

iPasolink O&M Training PAGE 7

iPasolink O&M Training PAGE 8

Enables to divide broadcast domain

iPasolink O&M Training PAGE 9

Easily Replacing and Moving Network Devices

iPasolink O&M Training PAGE 10

HUB VLAN Switch

2nd Floor (Department B) 2nd Floor

HUB VLAN Switch

Need to change Just change setting, not

iPasolink O&M Training PAGE 11

Port Based VLAN

VLAN 1 VLAN 2 VLAN 3

iPasolink O&M Training PAGE 12

Ethernet Header 18Bytes

Max 1518 Bytes

802.1q Max 1522 Bytes

Q in Q Max 1526 Bytes Max MTU Size = MTU1500bytes + (2 x 4 bytes VLAN

iPasolink O&M Training PAGE 13

Extended VLAN is standardized by IEEE802.1ad

Data 100 300

Data 100 Data 100

iPasolink O&M Training PAGE 14

Tag VLAN is standardized by IEEE802.1q

IFG Preamble Destination Source MAC VLAN Length Data FCS

802.1q tag type TCI field

iPasolink O&M Training PAGE 15

To MAC Fm MAC TPID TCI Type IP Header IP data FCS

Priority CFI VLAN Priority CFI VLAN

Priority CFI VLAN Priority CFI VLAN

iPasolink O&M Training PAGE 16

FE1/GbE 1. Access FE1/GbE

iPASOLINK 200 , 802.1q iPASOLINK 400/1000 , 802.1q

Main Board In-band

iPASOLINK 200 , 802.1ad

iPasolink O&M Training PAGE 17

VLAN MODE Port Type Direction Action

iPasolink O&M Training PAGE 18

Send with VLAN 10

iPasolink O&M Training PAGE 19

Data Data 2 Send with VLAN 2 Set for Un-tag packet

Data 20 20 Send with VLAN 20

FE Port 2: iPASO200 Modem 1:

Recommendation: To be used for base station with VLAN tag interface

iPasolink O&M Training PAGE 20

How to create tunnel type ( Q in Q ) VLAN?