STP (IEEE 802.1D)/ RSTP (IEEE 802.1w)/ MSTP (IEEE802.1s)
•
Layer2 based loop-free protection mechanism
–
Each device using STP/RSTP send BPDU frames, and root bridge, root port, designated port,
backup port and alternate port are decided by BPDU frame.
•
Widely used in the enterprise network
•
Protection Switching Time; STP < 60sec / RSTP < 2~3 sec
•
Topology is no limitation (Ring, Tree, etc…)
Root Bridge Blocking Forwarding Forwarding Forwarding Forwarding Forwarding Root Bridge Blocking àForwarding Forwarding Forwarding àBlocking Forwarding Forwarding Forwarding
Failure
Root Bridge Blocking For MSTI1 MSTI 1 VLAN: 101 - 200 MSTI 2 VLAN: 201 - 300 Blocking For MSTI2 Double capacity• Some topology (instance) can be treated with
same STP network
• The VLANs are divided into some groups
(instances), and blocking port is decided in the
each group (instance).
• MSTP is based on RSTP (IEEE 802.1w), and can
used RSTP independently in each VLAN
– Enables load balancing, over a large
number of VLANs
• The restructuring of each VLAN becomes
possible. As a result, the time required to
restructure can be shortened.
STP Parameter - Bridge ID & Path Cost
Path Cost is accumulated Cost between a Bridge to Root Bridge.
Root Bridge
100Base-Tx 1000Base-T
100Base-Tx
Link Speed
Cost
10Gbps
2
1Gbps
4
100Mbps
19
10MBps
100
Path Cost defined in IEEE802.1d
0+4=4
4+19 =23
0+19 =19
19+100 =119
10Base-T
*
Port Cost is manually configurableBridge ID is main Parameter for
Spanning Tree Algorithm,
The Bridge with lowest Bridge ID
is selected as “Root Bridge”
Bridge ID (STP, RSTP)
Bridge Priority
Bridge MAC Address
Bridge ID (8 Bytes)
2bytes
6bytes
Root Bridge
Bridge: A
Bridge ID 32768
MAC Address 00-00-00-00-00-01
Port 1 as
Root port
Non Root Bridge
Bridge: C
Bridge ID 32768
MAC Address 00-00-00-00-00-02
Port 1
Port 2
Port 2
Port 2
Spanning Tree Failure
The blocked port has gone into
Forwarding
Non Root Bridge
Bridge: B
Bridge ID 32768
MAC Address 00-00-00-00-00-03
Port 1 as
Root port
RP
RP
DP
DP
STP IEEE 802.1D - Theory background (6)
Forwarding
Was Blocked
Now forwarding
Forwarding
Forwarding
Forwarding
Summary of STP Port States
1. Blocking
2. Listening
3. Learning
4. Forwarding
5. Disabled
BPDU
DP
Difference between STP and RSTP
STP
RSTP
STABLE TOPOLOGY
ONLY THE ROOT SEND BPDU AND OTHERS RELAY THEM.
ALL BRIDGES SEND BPDU EVERY HELLO (2SEC) AS A KEEP ALIVE MECHANISM.
PORT ROLES ROOT (FORWARDING) DESIGNATED (FORWARDING) NON-DESIGNATED (BLOCKING) ROOT (FORWARDING) DESIGNATED (FORWARDING) ALTERNATE (DISCARDING) BACKUP ( DISCARDING)
PORT STATES DISABLED , BLOCKING, LISTENING,
LEARNING ,FORWARDING
DISCARDING (DISABLED, BLOCKING, LISTENING) LEARNING, FORWARDING
TOPOLOGY CHANGES
USE TIMERS FOR CONVERGENCE INFORMED FROM THE ROOT. HELLO (2SEC)
MAX AGE (20SEC)
FORWARDING DELAY TIME (15SEC)
PROPOSAL AND AGREEMENT PROCESS FOR SYNCHRONIZATION (LESS THAN 1 SEC)
HELLO, MAX AGE AND FORWARDING DELAY TIMERS USED ONLY FOR BACKWARD COMPATIBILITY WITH STP. ONLY RSTP PORT RECEIVING STP
TRANSITION
SLOW: (50SEC), BLOCKING (20SEC)=>
LISTENING (15 SEC) => LEARNING (15SEC) => FORWARDING.
FASTER: NO LEARNING STATES. DOESN’T WAIT TO BE
INFORMED BY OTHERS, INSTEAD, ACTIVELY LOOKS FOR POSSIBLE FAILURE BY A FEED BACK MECHANISM.
TOPOLOGY CHANGE
WHEN A BRIDGE DISCOVER A CHANGE IN THE NETWORK IT INFORM THE ROOT. THEN ROOT INFORMS THE OTHER BRIDGES BY SENDING BPDU AND INSTRUCT THE OTHERS TO CLEAR THE DB ENTRIES AFTER THE FORWARDING DELAY
EVERY BRIDGE CAN GENERATE TOPOLOGY CHANGE AND INFORM ITS NEIGHBORS WHEN IT IS AWARE OF
TOPOLOGY CHANGE AND IMMEDIATELY DELETE OLD DB
CHANGE ROOT
IF A BRIDGE (NON-ROOT) DOESN'T RECEIVE HELLO FOR 10X HELLO TIME, FROM THE ROOT, IT START CLAIMING THE ROOT ROLE BY GENERATING ITS OWN HELLO.
IF A BRIDGE DOESN’T RECEIVE 3X HELLOS FROM THE ROOT, IT START CLAIMING THE ROOT ROLE BY
MSTP Setting
iPaso200-D iPaso400-F iPaso200-E iPaso400-B M1 M2 M2 M1 M2 M1 P1 P1 P2 MSTP Region: ABC MSTP Region: NEC Revision:0 IDU No. 1 2 3Bridge Priority (MSTI1) 4096 8192 8192 Bridge Priority (MSTI2) 20480 12288 20480
Instance No. (MSTI1) 1 1 1 Instance No. (MSTI2) 2 2 2
MSTI1 MSTI2
MODEM1 MODEM 2 MODEM 1 MODEM 2 IDU 1
IDU 2 IDU 3
After Failure condition mark the status of each modem Forwarding or Discarding
MSTI1 MSTI2
MODEM1 MODEM 2 MODEM 1 MODEM 2 IDU 1
IDU 2 IDU 3
In Normal condition mark the status of each modem Forwarding or Discarding
MSTP Setting
Select RSTP/MSTP Setting from the ETH Function Setting Menu.
Click the Modify STP Mode icon on the ETH Function Setting –RSTP/MSTP
Setting display.
In the STP Mode Setting window click the STP Mode dropdown list and select MSTP and click Ok. Click OK again on
the Complete information window. RSTP/MSTP Setting display shows the
MSTP Setting
Click the Modify STP Port icon on the RSTP/MSTP Setting display. And set the parameters for MSTP. Select each tab IST, MSTPI1 to MSTI4 as required and set the parameters.
MSTP Setting
Enter the Revision Number (0 - 65535). Of the configuration. All members of the MSTP region must have the same Revision No. Enter the Region Name (32 Characters). This should be same on all
members of the MSTP Region.
BPDU Guard Timer Usage: to use this function, select the Used radio
Button. This function prevent external BPDUs from changing the topology.
If BPDU Guard Timer usage is selected as Use, then enter the Timer value in seconds ( 10 – 1000000). When unwanted BPDU is detected in the port, it will block the port for the timer period preventing the BPDU to pass.
If BPDU Guard Timer usage is selected as Use, then enter the Timer value in seconds ( 10 – 1000000). When unwanted BPDU is detected
in the port, it will block the port for the timer period preventing the BPDU to pass. iPaso200-D iPaso400-F iPaso200-E iPaso400-B M1 M2 M2 M1 M2 M1 P1 P1 P2 MSTP Region: ABC MSTP Region: NEC Revision:0
The MSTP revision level is the revision number of the configuration. All switches in an MSTP region must have the same revision level configured
CIST Setting
Every Region has a Common Internal Spanning Tree (CIST) that forms a single spanning tree instance including all the members in the region. CIST operates across the MSTP region and create a loop free topology across regions. In each region several MSTP Instances (up to 4) can be created with each instance catering for a group of VLANs. MSTP instance operates within the Region.
Select the tab IST to configure the CIST. Enable the ports that is makes the STP. If any port is an Edge port select Enable from the drop down list.
For each of the ports selected:
STP Port Path Cost: select Auto for automatically detect the path Cost or select
Manual and enter the Path cost value
STP Port Priority: select port priority value from the drop down list (default is 128)
BPDU Guard: select from the drop down list enable to enable BPDU Guard function
for the Port.
Root Guard: select from the drop down list enable to enable Root Guard function for
the Port.
MSTI Setting
Configure the MSTP instances in the selected region by clicking on the MSTI# tabs.
Select Enable radio button on the selected MSTI#. MSTI Regional Root Bridge Priority /ID will be automatically selected on the MAC address, Bridge Priority…
Enter the Instance number for the selected MSTP Instance.
Select the Bridge Priority (MSTI) from the drop down list. This selection can force the Bridge ID to be higher or lower to select as root Bridge for the selected instance.
Click on the Member VLAN and select the VLANs for the selected MSTI from the VLAN List and the radio buttons.
Select the port associated with MSTP in the region from the check boxes.
Select the STP Port Path Cost and STP Port Priority from the respective drop down lists.
MSTP Setting
Forwarding and disable status of ports for each Instance is shown under status column. Selected Root Bridge Priority/ ID for
CIST, CIST Regional, and each MSTI are shown.
Detail STP Parameter Setting
Item Parameter Description
STP Bridge Priority 0 to 61440 Change default STP priority of the bridge
STP Bridge MAX Age 6 to 40 s Set the expiration of the Configuration BPDU stored, Bridge will. notice that a topology change has occurred after the Max Age time elapses and the BPDU is aged out
STP Bridge Hello Time 1 s Set the period of sending Configuration BPDUs from Root Bridge.
2 s STP Bridge Forward
Delay
4 to 30 s Set the delay when the port is going to change the state from Listening to Learning.
STP TX Hold Count 1 to 10 Set the number of BPDU which can be sent per second. STP MAX Hop Count 1 to 40 See below
The MSTP maximum hop count value is the maximum number of hops in the region. The MSTI root bridge sends BPDUs with the hop count set to the maximum value. When a bridge receives this BPDU, it decrements the remaining hop count by one and propagates this hop count in the BPDUs it sends. When a bridge receives a BPDU with a hop count of zero, the bridge discards the BPDU
G.8032 Ethernet Ring Protection Switching
ETH-CC
Client #1
Signal
Client #2
Signal
Traffic
separation
with VLAN
Tag
RPL (Ring Protection Link)• 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
RPL (Ring Protection Link)
u
G.8032 is an ITU Recommendation
u
Defines the APS (Automatic Protection Switching ) protocol and protection switching
mechanisms for ETH layer ring topologies.
u
Use of standard 802 MAC and OAM frames around the ring
u
Uses standard 802.1Q , but with xSTP disabled.
u
Prevents loops within the ring by blocking one of the links
u
Monitoring of the ETH layer for discovery and identification of Signal Failure (SF)
conditions.
u
Protection and recovery switching within 50 ms for typical rings.
Submission of
FDB Flush,
Unblock blocking Port
Blocking
Port
Unblock
blocking Port
1) Normal Condition
2) Failure Event
3) Switchover Condition
Client Traffic
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 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
ETH-CC (Continuity Check) enables to detect failures on several
conditions which physical layer monitoring can’t do.
n
Unidirectional link failure
n
Partial failure in equipment
n
Decline of signal level (less than Loss of Signal)
n
In case if no ability to detect a failure is on physical layer
ETH-CC (Continuity Check) enables to detect failures on several
conditions which physical layer monitoring can’t do.
n
Unidirectional link failure
n
Partial failure in equipment
n
Decline of signal level (less than Loss of Signal)
n
In case if no ability to detect a failure is on physical layer
Submission of
FDB Flush,
Unblock blocking Port
Unblock blocking Port
1) Normal Condition
2) Failure Event
3) Switchover Condition
Client Traffic
MEP-1
MEP-8
MEP-7
MEP-6
MEP-5
MEP-4
MEP-3
MEP-2
cc
cc
cc
cc
MEP-1
MEP-2
cc
MEP-8
MEP-7
cc
MEP-6
MEP-5
cc
MEP-4
MEP-3
cc
LOC LOCcc
cc
cc
cc
LOC LOCMultiple instance
• Several logical rings can be configured in the physical ring
(G.8032V2)
• Each logical ring can have a group of user VLANs (instances)
and can place a block port at a different point respectively
• Load balancing can be achieved in normal condition, and the
higher priority traffic can be protected even in case of failure
High priority
block port for instance#1 Instance#2
(Middle & Low priority)
Instance#1 (High priority)
block port for instance#2 Double capacity Low priority traffic is dropped based on QoS
Failure
Middle priority Low priority High priority Unblocked for instance#1 Instance#2(Middle & Low priority)
Instance#1 (High priority)
block port for instance#2
Middle priority Low priority
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).
Instance #1
Instance #2
Instance #3
User VLAN group #1 APS channel #1
Physical
ETH-CC-1
User VLAN group #2 APS channel #2 ETH-CC-2
User VLAN group #3 APS channel #3 ETH-CC-3 (Link Monitoring)
(Link Monitoring)
RPL SF failure
R-APS ch block
Client ch block
SF SF1
Scenario A - Normal to Protection
RPL Owner
2
Message source
SF SF3
4
5
SF SF SF SF SF SF6
50 m s7
Flush Flush Flush Flush
Flush Flush Flush NORMAL STATE PROTECTION STATE
1 . Normal State Node-G is the RPL Owner 2 . Failure Occurs
Node-A Node-B Node-C Node-D Node-E Node-F
Node-G
3 . Node D and Node C detect local signal fail condition and block the failed ports
4 . While the SF condition continues Node C and Node D periodically send SF (signal Fail) Messages on both ring ports
5 . Each node performs a FDB flush operation after receiving the SF message
6 . When the RPL owner receives the SF message it unblock the RPL link
7 . Stable State – SF messages on the ring . Further SF messages does not trigger further action
recovery
Scenario B recovery
RPL Owner9
10
SF SF SF SF SF SF13
8
12
NR NR NR NR NR, RPL Blocked NR, RPL Blocked NR, RPL Blocked14
NRNR, RPL Blocked NR, RPL Blocked NR, RPL Blocked NR NR11
Flush Flush Flush Flush Flush Flush Flush 50 m s C on fir m at ion ti m e15
Node-G Node-A Node-B Node-C Node-D Node-E Node-Ffailure
NORMAL STATE PROTECTION
STATE
9 . In Stable SF condition Node C and D continue to send SF messages every 5sec.
10 . Recovery of failure
11 . Node C and D detects clearing of SF condition and start the guard timer and initiate periodical transmission of NR messages on both ring ports (guard timer prevents reception of R-APS messages
14. When the Guard timer at Node C and D expire they may start receiving new R-APS messages
12. When RPL owner receives the NR message, it starts the Wait to Restore Timer (WTR)
15. At the expiration of WTR timer, RPL owner blocks its end of of the RPL link, sends NR RB message
16. Each node after re3ceivng the NR RB message flushes its FDB. 17. When Node c and D receive the NR RB message, they remove the block on their blocked ports
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
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.
Sub Ring
• Flexible placement of RPL
– The shortest path per user traffic can be selected in normal
condition.
2
ERP
iPASO 200D iPASO 400F iPASO 200E
Item PORT1 M1 M1 M2 M1 ETH Port1
MEG / (MEG LEV)/ CC Period NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms
MEP (VLAN 100) 6 1 2 3 4 5
MEP (VLAN 200) 12 7 8 9 10 11
Peer MEP (VLAN100) 5 2 1 4 3 6
Peer MEP (VLAN 200) 11 8 7 10 9 12
Ring ID/Ring Name 1 / Ring-1 2 / Ring-2 1 / Ring-1 2 / Ring-2 1 / Ring-1 2 / Ring-2
ERP Ver 8032v2 8032v2 8032v2 8032v2 8032v2 8032v2
Ring Port-0 P1 P1 M1 M1 P1 P1
Ring Port-1 M1 M1 M2 M2 M1 M1
RPL Owner /RPL Port Enable / 0 Enable / 1 - - -
-Revertive/WTR Revertive/1 Revertive/1
Guard Time 500msec 500msec 500msec 500msec 500msec 500msec
Control VLAN 1001 1002 1001 1002 1001 1002
R-APS MSG Period 7 7 7 7 7 7
MEG Lev 7 7 7 7 7 7
Traffic VLAN 100/300 200/400 100/300 200/400 100/300 200/400
CTRL MAC Address :01 :02 :01 :02 :01 :02
LOC Det enable enable enable enable enable enable
Ring Port-0 Ring Port-1 M1 M1 M2 M1 P1 P1 200-D 200-E 400-F Tester P2 P1 100/200/300/400 RING1 RPL RING2 RPL 100/200/300/400 100/200/300/400 100/200/300/400
ERP
iPASO 200A iPASO 1000C iPASO 400B
Item PORT1 M1 M1 M2 M1 ETH Port1
MEG / (MEG LEV)/ CC Period NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms NEC /(7)/3.3ms
MEP (VLAN 100) 6 1 2 3 4 5
MEP (VLAN 200) 12 7 8 9 10 11
Peer MEP (VLAN100) 5 2 1 4 3 6
Peer MEP (VLAN 200) 11 8 7 10 9 12
Ring ID/Ring Name 1 / Ring-1 2 / Ring-2 1 / Ring-1 2 / Ring-2 1 / Ring-1 2 / Ring-2
ERP Ver 8032v2 8032v2 8032v2 8032v2 8032v2 8032v2
Ring Port-0 P1 P1 M1 M1 P1 P1
Ring Port-1 M1 M1 M2 M2 M1 M1
RPL Owner /RPL Port Enable / 0 Enable / 1 - - -
-Revertive /WTR Revertive/1 Revertive/1 - - -
-Guard Time 500msec 500msec 500msec 500msec 500msec 500msec
Control VLAN 1001 1002 1001 1002 1001 1002
R-APS MSG Period 7 7 7 7 7 7
MEG Lev 7 7 7 7 7 7
Traffic VLAN 100/300 200/400 100/300 200/400 100/300 200/400
CTRL MAC Address :01 :02 :01 :02 :01 :02
LOC Det enable enable enable enable enable enable
Ring Port-0 Ring Port-1 M1 M1 M2 M1 P1 P1 200-A 400-B 1000-C Tester P2 P1 100/200/300/400 100/200/300/400 RING1 RPL RING2 RPL 100/200/300/400 100/200/300/400 100/200/300/400
ETHER RING PROTECTION - OAM Setting
Traffic(Ring1) Traffic(Ring2) MEP1 MEP8 Blocking Port MEP2 MEP3 MEP4 MEP5 MEP6 MEP9 MEP10 MEP11 MEP12 MEP7 NE1 NE1 NE2 NE2 NE3 NE3OAM(Ring1)VLAN 15 OAM (Ring2) VLAN 14
Confirm that no LOC alarm appear in the current status screen
For each Ring create a set of MEPs as shown in the diagram below.
ETHER RING PROTECTION Setting (1 of 5)
Select the ERP Setting from the ETH Function
Setting MENU
Click the Modify ERP mode icon on the ERP setting screen and select the ERP Mode Enable radio button
Click the OK button. ERP setting progress bar indicate under execution
Click the OK button on the Complete dialog window
Confirm that the ERP mode is Enabled is indicated in the ERP Setting screen
ETHER RING PROTECTION Setting (2 of 5)
Click the Add ERP icon on the ERP Setting screen. Step-1 of the ERP Setting wizard opens.
Select the Ring ID from the drop down list (01 to 16) Enter the Ring Name (up to 32 characters)
Select the ERP Version radio button G.8032v1 or G.8032v2 as appropriate
Select the Ring Port 0 item (Interface /Modem) and the port from the drop down List Select the Ring Port 1 item (Interface /Modem) and the port from the drop down List Port name of the assigned port will appear if a name is given to the port.
In RPL Owner Setting select Enable radio button if one of the selected Ring’s port is going to be a RPL port. If not select the Disabled radio button
If selected Enable in the previous selection, select which port is going to be the RPL port for the ring. Port0 or Port 1 by selecting the appropriate radio button
Select protection switching is to be Revertive or Non-Revertive. Click the appropriate radio button
If Revertive is selected in the previous item, select the Wait-To-Restore (WTR) timer value from the drop down list (1 to 12 min)
Enter the Guard Timer value (10ms to 2000 ms)
Click the Next button to go to Step2 ERP VLAN Setting window ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ETHER RING PROTECTION Setting (3 of 5)
In the Control VLAN ID enter a VLAN ID that is not part of the traffic (not in the VLAN List) for the selected ring.
Select the Control MAC Address for the selected ring. Same MAC address can be used for different instances of the same physical ring. MAC address should be different fro multiple physical rings. Change the last two digits of the MAC address for each ring
Select the R-APS Message Priority (0 tom7 0 from the drop down List Select the R-APS Message MEG Level from the drop down List
Enable the Traffic VLAN IDs from the VLAN list by selecting the appropriate Check
boxes. If the required VLAN ID is not in the list click on the Add VLAN ID button and
enter the VLAN ID and the VLAN Service Name, VLAN ID will appear in the list, enable the check box to select it. The VLANs grayed out in the list are already assigned to a different ring and cannot be selected
Click the Next button to go to Step3 ERP LOC Detection MEP Index Setting window. ■ ■ ■ ■ ■ ■
ETHER RING PROTECTION Setting (4 of 5)
In the Step 3 ERP LOC Detection MEP Index Setting window, Click the Enable Radio button. Ring0 and Ring 1 selection area become active
Select the LOC Detection MEP Index for Ring Port0 and
Ring Port1 by clicking on the appropriate radio button
Click the Next button to go to Step-4 Setting
Confirmation Screen
■
■
ETHER RING PROTECTION Setting (5 of 5)
Click the Delete ERP icon to delete any created Ether Rings. Select the Ring ID to be deleted from the drop down list and click the OK button
Click the OK button on the Step-4
Setting Confirmation Screen. Apply
the setting and close the Add ERP Setting wizard
Confirm the added Ether Ring is listed in the ERP Setting screen.
ERP Status information
Select the Current Status menu and click on the IDU tab to see the ETH Ring Status information
ETH Ring Cause
Local NR: Status change caused by NR( No Request)
Manual control Locally
Local SF: Status change caused by SF( Signal Fail)
detection on local node
Remote NR: Status change caused by NR( No Request)
Manual Control from Remote
ETH Ring Status
Idle: State where only an RPL port has been blocked and
no fault has occurred at every link in the ring
Pending: State where one or more failures occurred at links
in the ring, or switchback has been performed after a fault recovery
ETH Ring Port status
RPL blocking: State where an RPL port has been blocked.
This state can be caused at a port that has been set as an RPL port.
Forwarding: State where user frames and R-APS control
frames can be transmitted.
WTR: State where a switchback to the steady state has
been performed after a link fault recovery. This sate can be caused at a port that has been set as an RPL port.
Recovery: State where a link fault has been recovered signal fail: State where a link fault was detected and the port
with the fault has been blocked.
Protection: State where only an RPL port has been blocked and no fault has occurred at every link in the ring
ERP Control-1
Select Maintenance Mode First
Select the ERP Control screen by clicking the ERP CTRL from the ERP Setting screen. You can switch between the two screens
Select the ERP Control screen by Selecting the ERP Control from the
Maintenance Protection Control Menu
Select the Ring to be Loop detection restart, by the appropriate check box(s) and clicking the OK button
iPASOLINK monitor the loop detection when it receives it’s own R-APS control frame.
When the node receives own R-APS control frame at 160frames/100msec, the node detects the loop.
Loop Detection Restart reset the receive counter of own
R-APS control frame.
No traffic loss occurs when Loop Detection Restart.
Select the Loop Detection Restart icon on the Protection Control
ERP Control-2
Maintenance Control-Protection Control – ERP Control screen
provides manual switching of the Ethernet Rings.
Click the Ring ID number of the ring to be manually switched. ERP Control (RING ID#) window opens for the selected ring.
Select the Manual control to applied from the drop down List.. Available Options are:
Forced SW: Manual SW:
Clear: Clear the Maintenance Control
Select the Blocked Port to be switched to forwarding, Ring Port 0 or
Ring Port 1,
Click the OK button to apply the maintenance control
Maintenance control is applied is indicated by the yellow highlighting of the controlled Ring ID number.
What’s Radio Aggregation?
What’s Radio Aggregation?
Radio Aggregation Group bundle several radio links to the same destination
providing increased Ethernet bandwidth and high reliability by combining them into
one logical link, and to provide redundancy in case, one of the links fail.
Why Radio Aggregation
?
Increased link capacity: the capacity of multiple Radio Links are combined into one logical link.
Higher link availability: If a link within a Radio Aggregation Group fails the traffic is not disrupted
and communication is maintained
Load sharing: Traffic is distributed across multiple Radio links, minimizing the probability that a
single link be overwhelmed.
Radio Aggregation uses Static Link Aggregation
Treat multiple switch ports as one switch port for high-bandwidth connections
A static LAG balances the traffic load across the links in the channel. If a physical link within the
static LAG fails, traffic over the failed link is moved to the remaining links.
The following parameters are considered for distribution of traffic among the bundled
radio links on iPASOLINK
l
L3 based
• Source IP Address
• Destination IP Address
• Source TCP Port Number
• Destination TCP Port Number
l
MPLS based
• MPLS label
l
L2 based
• Source MAC Address
• Destination MAC Address
• VLAN ID
• Ether Type
Radio Aggregation (iPASOLINK-400)
Aggregation Group1 Aggregation Group1 Aggregation Group1 Aggregation Group1 MODEM#1 MODEM#2 MODEM#1 MODEM#2 MODEM#3 MODEM#4 MODEM#3 MODEM#4 L2SW L2SW Port-1 Port-n Port-1 Port-n GRP1 GRP1Aggregation Group1 Aggregation Group1 Aggregation Group2 Aggregation Group2 MODEM#1 MODEM#2 MODEM#3 MODEM#4 L2SW Port-1 Port-n GRP1 GRP2
Distribution algorithm L2 Base
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte6 Byte5 Byte4 Byte3 Byte2 Byte1
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte2 Byte1
7 6 5 4 3 2 1 0
Byte1
Source MAC Address Destination MAC Address
VLAN ID Ether Type Port ID Bits 0 1 2 Byte1 Source MAC Address 8 9 10 Byte2 16 17 18 Byte3 24 25 26 Byte4 32 33 34 Byte5 40 41 42 Byte6 0 1 2 Byte1 Destination MAC Address 8 9 10 Byte2 16 17 18 Byte3 24 25 26 Byte4 32 33 34 Byte5 40 41 42 Byte6 0 1 2 Byte1 VLAN ID 8 9 10 Byte2 0 1 2 Byte1 Ether Type 8 9 10 Byte2
0 1 2 Byte1 Port No.
x x x Exclusive OR results
Distribution Results iPASO 400 Exclusive OR Results Two modems Three modems Four modems Output Modem # 0 (000) 1 1 1 1 (001) 2 2 2 2 (010) 1 3 3 3 (011) 2 1 4 4 (100) 1 2 1 5 (101) 2 3 2 6 (110) 1 1 3 7 (111) 2 2 4 MODEM#1 MODEM#2 MODEM#3 MODEM#4 Port1
LAG
The distribution algorithm is calculated by using certain bits of each
parameters. (first 3 bits of each byte) The source address, destination
address, VLAN ID, etc are different values between several streams, the
XOR result decide the link to be transmitted.
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte6 Byte5 Byte4 Byte3 Byte2 Byte1
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte2 Byte1
The distribution algorithm is calculated by using the
Distribution algorithm – L3 Base
127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
Byte16 Byte15 Byte14 Byte13
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte2 Byte1
Source IP Address
Destination IP Address
Source TCP Port No. Destination TCP Port No.
IPv4 Bits 0 1 2 Byte1 Source IP Address 8 9 10 Byte2 16 17 18 Byte3 24 25 26 Byte4 0 1 2 Byte1 Destination IP Address 8 9 10 Byte2 16 17 18 Byte3 24 25 26 Byte4 0 1 2 Byte1 TCP Source Port 8 9 10 Byte2 0 1 2 Byte1 TCP Destination port 8 9 10 Byte2 x x x Exclusive OR Results
Distribution Results iPASO 400 Exclusive OR
Results modemsTwo modemsThree modemsFour Output Modem # 0 (000) 1 1 1 1 (001) 2 2 2 2 (010) 1 3 3 3 (011) 2 1 4 4 (100) 1 2 1 5 (101) 2 3 2 6 (110) 1 1 3 7 (111) 2 2 4 MODEM#1 MODEM#2 MODEM#3 MODEM#4 Port1
LAG
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0Byte6 Byte5 Byte4 Byte3 Byte2 Byte1
95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47
Byte12 Byte11 Byte10 Byte9 Byte8 Byte7
127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
Byte16 Byte15 Byte14 Byte13
IPv4
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Byte6 Byte5 Byte4 Byte3 Byte2 Byte1
95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47
Byte12 Byte11 Byte10 Byte9 Byte8 Byte7
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Distribution algorithm L2 Base
00 00000000 000 Byte1 Source MAC Address 01 00000001 001 Byte2 02 00000010 010 Byte3 03 00000011 011 Byte4 04 00000100 100 Byte5 05 00000101 101 Byte6 00 00000000 000 Byte1 Destination MAC Address 05 00000101 101 Byte2 06 00000110 110 Byte3 07 00000111 111 Byte4 08 00001000 000 Byte5 09 00001001 001 Byte6 64H 01100100 100 Byte1 VLAN ID Byte2 0800H 00000000 000 Byte1 Ether Type 00001000 000 Byte21 00000001 001 Byte1 Port No.
001 Exclusive OR results Distribution Results iPASO 400
Exclusive OR Results Two modems Three modems Four modems Output Modem # 0 (000) 1 1 1 1 (001) 2 2 2 2 (010) 1 3 3 3 (011) 2 1 4 4 (100) 1 2 1 5 (101) 2 3 2 6 (110) 1 1 3 7 (111) 2 2 4 MODEM#1 MODEM#2 MODEM#3 MODEM#4 Port1
LAG
MAC SA= 00:01:02:03:04:05(hex) MAC DA= 00:05:06:07:08:09(hex) VLAN ID= 64(hex)
ethertype= 800(hex)
(1) Source MAC Address XOR Result = (000) XOR (001) XOR (010) XOR (011) XOR (100) XOR (101) = 001(bin)
(2) Destination MAC Address XOR Result = (000) XOR (101) XOR (110) XOR (111) XOR (000) XOR (001) = 101(bin)
(3) VLAN ID XOR Result = (100) = 100(bin)
(4) ethertype XOR Result = (000) XOR (000) = 000(bin) (5) Source Port Number = 001(bin)
Distribution algorithm L3 Base
192 11000000 000 Byte1 Source IP Address 168 10101000 000 Byte2 0 00000000 000 Byte3 100 01100100 100 Byte4 192 11000000 000 Byte1 Destinati on IP Address 168 10101000 000 Byte2 1 00000001 001 Byte3 200 11001000 000 Byte4 80 00000000 000 Byte1 TCP Source Port 00001000 000 Byte2 80 00000000 000 Byte1 TCP Destinati on port 00001000 000 Byte2 101 Exclusive OR Results Distribution Results iPASO 400Exclusive OR Results Two modems Three modems Four modems Output Modem # 0 (000) 1 1 1 1 (001) 2 2 2 2 (010) 1 3 3 3 (011) 2 1 4 4 (100) 1 2 1 5 (101) 2 3 2 6 (110) 1 1 3 7 (111) 2 2 4 MODEM#1 MODEM#2 MODEM#3 MODEM#4 Port1
LAG
IP SA= 192.168.0.100 IP DA= 192.168.1.200 TCP SRC= 80 TCP DST= 80(1) Source IP Address XOR Result = (000) XOR (000) XOR (000) XOR (100) = 100(bin) (2) Destination IP Address XOR Result = (000) XOR (000) XOR (001) XOR (000) = 001(bin) (3) SRC TCP Port XOR Result = (000) XOR (000)= 000(bin)
Distribution algorithm MPLS Base
MODEM#1 MODEM#2 MODEM#3 Port1LAG
Initial hash, hash_key[127:0] is defined below
Bits Corresponding Label 127:112 MPLS Top Label [15:0]
111:96 MPLS second Label [15:0] If top label BOS field=1, all “0”
95:0 All “0”
Apply CRC16 to the hash_key [127:0] and obtain 16 bit result Extract bits [7:0] of the CRC16 results and convert hexadecimal to decimal and divide by the number of LAG ports and note the remainder
The remainder corresponds to the Port ID of the LAG group
Remainder Port ID 0 0 1 1 2 2 3 3 Port ID 0 Port ID 1 Port ID 2
Label Example CRC output Low 8 bits Decimal Remainder 2 Modems 3Modems 0 F59c 9c 156 0 0 1 B6db Db 219 1 0 2 Ca3b 3b 59 1 2 3 897c 7c 124 0 1 4 3520 20 32 0 2 5 d667 67 103 1 1
Example of demonstration configuration (L2 based)
MODEM#1 MODEM#2 Port1 LAG (L2 based) MODEM#1 MODEM#2 Port1 Ethernet Tester Stream-1 Stream-2 StreamNo. Dst MAC Address Src MAC Address VLAN ID ethertype Stream-1 00:00:00:01:00:02 00:00:00:02:00:01 10 (hex:0A) 0800 Stream-2 00:00:00:01:00:02 00:00:00:01:00:01 10 (hex:0A) 0800
56MHz, 258QAM
Distribution
Result Output port 0 (000) MODEM#1 1 (001) MODEM#2 2 (010) MODEM#1 3 (011) MODEM#2 4 (100) MODEM#1 5 (101) MODEM#2 6 (110) MODEM#1 7 (111) MODEM#2
Stream-1:
Distribution Result = (011) XOR (011) XOR (010) XOR (000) XOR (001) = 011(bin) è 3(dec)
Stream-2:
Example of demonstration configuration (L3 based)
MODEM#1 MODEM#2 Port1 LAG (L3 based) MODEM#1 MODEM#2 Port1 Ethernet Tester Stream-1 Stream-2 StreamNo. Dst MAC Src MAC VLAN ID Dst IP Address Src IP Address Dst TCP port Src TCP port
Stream-1 Any Any Any 192.168.1.1 192.168.1.11 80 80
Stream-2 Any Any Any 192.168.1.1 192.168.1.12 80 80
56MHz, 256QAM
Distribution
Result Output port 0 (000) MODEM#1 1 (001) MODEM#2 2 (010) MODEM#1 3 (011) MODEM#2 4 (100) MODEM#1 5 (101) MODEM#2 6 (110) MODEM#1 7 (111) MODEM#2
Stream-1:
Distribution Result = (010) XOR (000) XOR (000) XOR (000) = 010(bin) è 2(dec)
Stream-2:
Example of demonstration configuration (MPLS based)
MODEM#1 MODEM#2 Port1 LAG (MPLS based) MODEM#1 MODEM#2 Port1 Ethernet Tester Stream-1 Stream-2Stream No. Dst MAC Src MAC EXP MPLS 1stLabel
Stream-1 Any Any Any 1 Distribute
Stream-2 Any Any Any 3 Distribute
Notes (1/2)
•
The distribution algorithm is calculated by using certain bits of
each parameters. Therefore, even if the source address,
destination address, VLAN ID, etc are different values between
several streams, the XOR result can becomes the same
•
The distribution algorithm uses the XOR result. Therefore, even
if the different values are used between several streams, the
XOR result might become the same.
Stream
No. Dst MAC Address Src MAC Address VLAN ID ethertype XOR result Stream-1 00:00:00:01:00:02 00:00:00:02:00:01 10
(hex:0A) 0800 3(dec) Stream-2 00:00:00:01:00:02 00:00:00:02:00:11 10
(hex:0A) 0800 3(dec)
(example)
These bits are tot used bits
Stream
No. Dst MAC Address Src MAC Address VLAN ID ethertype XOR result Stream-1 00:00:00:01:00:02 00:00:00:02:00:01 10
(hex:0A) 0800 3(dec) Stream-2 00:00:00:01:00:02 00:00:00:01:00:02 10
(hex:0A) 0800 3(dec)
Radio Traffic aggregation (PRTA) Physical Layer aggregation
• Radio Traffic Aggregation Physical
Layer (PRTA)
– Fragments the packet with
variable length, and distributes
the fragmented packets to two
radio links fairly with
round-robin algorithm
– Provides redundancy to the
radio link
the traffic can be transmitted
by the remaining links though
the bandwidth decreases when
the failure occurs.
– Enables single antenna high
capacity transport with using
PRTA and XPIC simultaneously
PRTA can use different rate links as
radio link group
And also, PRTA can be used with
hitless AMR
Link#1RTA
XPIC
V
H
1Gbps
515Mbps
515Mbps
56MHz/512QAM
Link#1 Link#2RTA
14MHz/128QAM
28MHz/128QAM
100Mbps 200Mbps300Mbps
1:2 Distribute rateRadio Traffic Aggregation Physical Layer (PRTA)
•
Ethernet packets are fragmented to variable lengths without adding
the padding data for less than 64 bytes length packets
.
–
In the case of fixed length fragmentation, the last fragmentation packet
might be less than 64 bytes due to input packet length. When the
fragmentation packet is less than 64 bytes length, its packet is added the
padding data to become 64 bytes length. The addition of padding data
would cause jitter.
•
The fragmented packets are distributed fairly and sequentially to two
radio links with round-robin algorithm.
•
Special Modem card is required.
Link#1
Link#2
Flexible efficient Fragmentation
Distributed fairly and sequentially with round-robin algorithm 1 2 6 3 5 7 4 MAC: a VLAN: a MAC: b VLAN: b MAC: c VLAN: c MAC: d VLAN: d 1 3 5 7 2 6 4
RTA
MODEM
MODEM
M
CA
4
Capacity A
Capacity
A
＋
B
M
CA
4
Capacity
A+B
RTA
Modem
Modem
RTAMODEM
Capacity B
MODEM
RTA
Modem
Modem
RTAPRTA operation
▌
PRTA needs special modem card. MODEM-A cannot be used at PRTA
▌
Maximum number of radio link supporting PRTA is two.
Modem-A -NWA-055300-102 (PRTA compatible modem) Modem-A -NWA-055300-001 (non PRTA modem)
MODEM
MODEM
M
C
A
4
（L
2
S
W
)
Capacity A
Capacity
A＋B
M
C
A
4(
L
2
S
W
)
Capacity
A+B
PRTA
Modem
Modem
PRTA
MODEM
Capacity B
MODEM
PRTA
Modem
Modem
PRTA
MODEM
Capacity C
MODEM
PRTA
Modem
Modem
PRTA
MODEM
Capacity D
MODEM
PRTA
Modem
Modem
PRTA
Capacity
C+D
Capacity
C+D
PRTA in aggregation link
RADIO AGGREGATION SETTING
Modem Slot1 Modem Slot2 Modem slot3 Modem slot4
Group1 Not used Not used
Group1 Not used
Group1
Group1 Group2
Radio Aggregation Setting
iPaso200-D iPaso400-B E1 Mod2 STM-1 Mod1 MSE 16E1 Mod2 STM-1 Mod1 MSE 16E1 Mod1 Mod2 P1 P1 P1 iPaso200-E Mod1 Mod2 P1 P1 Ethernet Tester P1 Ethernet Tester iPaso400-FRADIO CONFIGURATION (1 of 4)
Click the Equipment Setup Menu and select Radio Configuration to open the Equipment Setup – Radio configuration screen
Click the Setup Icon to open the Setup 1 Detailed MODEM Setting of SW/XPIC GRP or Slot Unit window.
Radio configuration window shows the existing radio configuration including the ODU frequency, parameters of radio channels. Configuration depend on the Equipment Configuration
1
2
RADIO CONFIGURATION (2 of 4)
Green border on the Set Position section modem configuration show the selected modem
Specification and information of the ODU connected to the selected Modem
Current setup of the selected modem ‘s radio configuration
Select the channel spacing of the radio signal
Select the reference Modulation of the radio signal
Show the available Ether bandwidth after E1 and STM-1 traffic mapping.
Select the TX Power Control Mode. ATPC or MTPC. Parameter setting for each mode is from provisioning menu
Enter the radio signal Frame ID (1 ~ 32) Enter TX/RX point frequency within the Start and Stop frequency of the ODU shown above.
Enter the radio parameters and TDM mapping for the Modem (Slot 01). 3
3
Select Radio Aggregation used or not used (up to 3 modems are mounted) When all four modems are
mounted in (1+0) configuration
Select the Radio Mode, High Capacity or High System Gain
Show the assignment of TDM and Ether capacities. TDM Channels are assigned from the AMR /Radio Mapping configuration Menu(Rel3)
Select whether the aggregation distribution Mode is based on Packet layer or Physical Layer. (Physical Layer require PRTA Modem)
RADIO CONFIGURATION (3 of 4)
Confirmation screen shows the changes in blue background. Confirm the setting and click OK
Repeat for Modems in Slot 3 and 4 if configured
Select the Channel spacing to be used from the drop down list Select the Reference or fixed modulation to be used from the drop down list
Select the maximum number of E1 to be used
Select whether STM-1 is to be used in the through mode Confirm the available Ether band width
After changing the setting for Modem 1 and click the Next button Set the TX & RX Frequency
Select the Frame ID to be used (1 ~ 32) TX Power control mode ATPC or MTPC 4
4
5
Enter the radio parameters and TDM mapping for each of the configured Modem slots, and click Next
RADIO CONFIGURATION (4 of 4 )
Modem radio configuration
Item Parameter DescriptionChannel Spacing 7/14/28/56 [MHz] Specify the radio channel spacing Reference
Modulation
QPSK
16/32/64/128/256[QAM]
Specify the reference modulation from the list
Radio Mode High Capacity High System Gain
E1 Mapping For High Capacity: 0 to 152 [CH] 56MHz 0 to 86 [CH] 28MHz For High System Gain : 0 to 152 [CH] 56MHz
0 to 77 [CH] 28MHz
Indicate the Mapped E1 channels E1 and STM-1 through mode channel mapping is carried out from
AMR/Radio Mapping Configuration Menu
STM-1 Mapping 0 to 2 [CH] Indicate the number of STM-1 CH mapped to the radio
ETH Bandwidth [Mbps] Display the bandwidth of the ether traffic after TDM mapping if any TX RF Frequency xxxxx.xxx [MHz] Enter transmit frequency
RX RF Frequency xxxxx.xxx [MHz] receive frequency (automatically)
Frame ID 1 - 32 Set frame ID
TX Power Control MTPC/ATPC Set transmit power control mode Radio Traffic
Aggregation
Not used/ Radio GRP 1~6 Radio aggregation usage Support Version Ver.1 Packet Layer
Ver. 2 Packet layer & Physical Layer Distribution Mode Packet Layer (L2 & L3)
Radio aggregation – VLAN setting
3 1
2
Click the OK button to go back to VLAN Setting screen.
4
3
Select VLAN setting from the Provisioning ETH Function Setting Menu Select the LAG Radio group1 and assign the VLANs to the
aggregation group as well as the ETH Ports to be used. 1
2
2
4 Confirm that the VLANs are assigned to the Radio Aggregation Group and the ETH port(s)
Radio Aggregation – LAG Setting
1
2 2
Click the OK button to apply the changes 4
3
Select Link Aggregation Setting from the Provisioning ETH Function Setting Menu
1
2
Link Aggregation Setting screen shows the Radio GRP1 in the Link aggregation Group section. Default Distribution rule is L2 Base
To assign a name to the LAG (optional) or change the distribution rule, click the Modify Link Aggregation icon. 3 Enter the Link aggregation Group name in the LAG Name
field. (32 Characters).
Click the Distribution Rule drop down list and select L2 Base or L3 Base or MPLS Base as the distribution rule. L2 Base uses the MAC address as the distribution criteria, L3 Base uses the IP address as the distribution criteria MPLS Base uses the MPLS label as the distribution criteria
4 Note: Radio LAG cannot be added or deleted from this window
Radio Aggregation – Alarm/Status
1
Radio Aggregation status is shown in Current Status under the Modem/ODU and IDU tabs.
When the Links in the aggregation loop are normal Radio Traffic aggregation Port Status indicate as Active, It shows as Standby the links that are down.
1
2
2
When at least one link in the Radio aggregation group is normal Radio Traffic Aggregation Link status is shown as Normal. If all the links in the radio aggregation Group are down then the Radio Traffic Aggregation
Link Aggregation Setting
iPaso200-D iPaso400-B Mod2 STM-1 Mod1 MSE 16E1 Mod2 STM-1 Mod1 MSE 16E1 Mod1 Mod2 P1 P1 P3 iPaso200-E Mod1 Mod2 P2 Ethernet Tester P1 Ethernet Tester iPaso400-F P3 P1 P2 P2 P3 P1 P2 P2 P3What’s & Why LAG?
What’s LAG?
Link Aggregation Groups (LAGs), provide increased bandwidth and high reliability by
combining several interfaces into one logical link, and to provide redundancy in case one of
the links fails.
Why LAG?
– Higher link availability: If a link within a LAG fails or is replaced, the traffic is not disrupted
and communication is maintained
– Increased link capacity: the capacity of multiple interfaces is combined into one logical link.
– Load sharing: Traffic is distributed across multiple links, minimizing the probability that a
How does LAG Work?
•
LAG implement ways:
– LAG N is the load sharing mode of LAG.
• The LAG N protocol automatically distributes and load balances the
traffic across the working links within a LAG
– LAG M:N provides the working/protection mode
• M: active links
• N: standby links.
• Total member: M+N=8
How does LAG work?
–
The standard states, “Link Aggregation allows one or more links to
be aggregated together to form a Link Aggregation Group, such that
a MAC client can treat the Link Aggregation Group as if it were a
single link”. This layer 2 transparency is achieved by the LAG using
a single MAC address for all the device’s ports in the LAG group
.
Static vs. Dynamic LAG (1)
•
Static Link Aggregation Groups (LAGs)
– Treat multiple switch ports as one switch port for high-bandwidth connections
– A static LAG balances the traffic load across the links in the channel. If a physical link within
the static LAG fails, traffic over the failed link is moved to the remaining links.
•
Dynamic Link Aggregation Groups (LAGs)
– Dynamic LAG uses a peer-to-peer protocol for control, called the Link Aggregate Control
Protocol (
LACP
), specified in the IEEE standard 802.3ad
– LACP Ensures smooth and steady traffic flow by automating the configuration,
reconfiguration and maintenance of aggregated links.
Dynamically exchanging information between two switches in
order to configure and maintain link aggregation groups
automatically.
– Load sharing is maintained and automatically readjusted
– LACP interface supports two modes of operation
• Passive: The interface does not initiate the LACP exchange,
but replies to the received LACP packet.
• Active: The interface issues LACP PDUs due to its own
reasons and may initiate LACP exchange with either a
passive or another active connected interface.
LINK AGGREGATION Setting
Select Link Aggregation Setting From the ETH Function Setting menu.
Link Aggregation Setting screen shows the current
Link aggregation groups and Link aggregation Ports Click the Add LAG icon to open the ADD LAG window 1
2
2 1
LINK AGGREGATION Setting
LAG Name: Enter a name for the LAG Group
TX Interval: The interval for LACP PDU
transmission select Short (1Sec)or Long (30Sec) radio button
Click the OK button on the Complete dialog window
Mode: Select the LAG mode, LACP-Active,
LACP-Passive or Static from the drop down list
Two sides of the aggregation link should be set to :
Static / Static
LACP-Active / LACP Active LACP-Passive / LACP Active
Revertive: If static mode is selected select
Revertive or non Revertive . For LACP Active or Passive mode always Revertive is selected
LINK AGGREGATION GROUP SETTING
LINK AGGREGATION PORT SETTING
Before setting the LAG Ports enable the ports to be used from the Ether Port Setting
Select the ETH GRP# from the LAG drop down list for the ports to be used in the aggregation group
Select the Port Role Active or Standby from the radio buttons. Select all ports Active for all links to be used for aggregation. Select any port as Standby for that port to be used in case of failure of an Active link.
6 3 5 3 4 4 5 7 6 7 8 8 9 9 Click the Distribution Rule drop down list and select L2
Base or L3 Base or MPLS Base as the distribution rule. L2 Base uses the MAC address as the distribution criteria, L3 Base uses the IP address as the distribution criteria MPLS Base uses the MPLS label as the distribution criteria
LINK AGGREGATION Setting
Click the Modify Link Aggregation icon on the Link Aggregation Setting screen..
Click the Delete LAG icon to open the Delete LAG window.
■
■
■
■
■ Select the LAG group to be modified from the LAG drop down list .
Modify the Link Aggregation parameters for the selected LAG and click OK
Select the top most check box to delete all created link aggregation groups
Select the individual check boxes to delete the selected link aggregation groups Click the OK button to delete the selected LAG groups.
