Ceragon IP 10 - LAG

Proprietary and Confidential

Lin

k A

gg

reg

ati

on

(IE

EE

80

2.3

ad

)


Definition

Advantages

Feature Review

Applications

Load Balance Example

Ag

en

da

Agenda

2


IEEE Definition:

•Link Aggregation allows one or more links to be aggregated

together to form

a Link Aggregation Group, such that a M

AC

Client can treat the Link Aggregation Group as if it were a

single link

•The Link Aggregation Group is consisting of N parallel

instances of full duplex point-to-point links operating at the

same data rate

•Traffic sent to the ports in such a group is distributed through

a load balancing function

Introduction to Link Aggregation

3

N

Ad

va

nta

ge

s


Benefits of using Link Aggregation

51. Increased aggregate bandwidth

Link Aggregation allows the establishment of full duplex point-to-point links

that have a higher aggregate bandwidth than the individual links that form

the

aggregation.

The capacity of the m

ultiple links is combined into one logical link.

100 M

bps



62. Im

proved Resiliency

In case of a failed link, remaining links take over utilization of new available BW

Traffic via LAG is distributed according to user’s policy –

improved reliability



73. Reduced Complexity & Administration

When m

ultiple ports are allocated between two ETH switches, broadcast storm

s are

created due to physical loops. STP is required to elim

inate loops by blocking the redundant

port.

When m

ultiple ports are allocated between 2 Routers, Routing Protocols are required to

control traffic paths.

With LA –

STP or routing protocols are not needed, therefore, less processing is involved.

STP requires blocking and

path cost calculations



84. Reduced Cost

Instead of utilizing an expensive GbEport(s) to transport 200Mbps –

>> we trunk N x FE ports



95. Im

proved Netw

ork Efficiency / Security

For sites with limited IP address space that nevertheless require large amounts of

bandwidth, you need only one IP address for a large aggregation of interfaces.

For sites that need to hide the existence of internal interfaces, the IP address of

the aggregation hides its interfaces from external applications.

(These examples refer to using L2 topologies as well)

Customer

Network

Public

Network

Multiple

Interfaces

Single

Interface

Fe

atu

re R

evie

w


LAG Distribution Policy

11Traffic sent to ports in a group is distributed through a load balancing function.

Two m

ethods are available for Link Aggregation Group traffic distribution:

1. Sim

ple XOR:

In this m

ethod the 3 LSBs of DA and SA are XORedand the result is used to select

one of the ports in the group.

This m

ethod can be used for testing & debugging.

2. Hash (default):

In this m

ethod the hash function (used by the traffic switch for address table lookups)

is used to select one of the ports in the group.

This provides better statistical load balancing.


LAG Distribution: Simple XOR

12We can easily demo balanced traffic distribution using the XOR m

ethod –

(Configure your Traffic Generator with the following MACs)

Str

ea

m

MA

C (

HE

X)

Last

3b

its

XO

R r

esu

ltA

ssig

ne

d L

AG

Po

rt

SA

->

->

DA

00

:20

:8f:

0a

:02

:01

00

:20

:8f:

0a

:01

:01

00

1

00

10

00

(0

)Li

nk

#1

SA

->

->

DA

00

:20

:8f:

0a

:02

:02

00

:20

:8f:

0a

:01

:02

01

0

01

00

00

(0)

Lin

k #

1

SA

->

->

DA

00

:20

:8f:

0a

:02

:03

00

:20

:8f:

0a

:01

:03

01

1

01

10

00

(0)

Lin

k #

1

SA

->

->

DA

00

:20

:8f:

0b

:e1

:03

00

:20

:8f:

0a

:e1

:04

01

1

01

00

01

(1

)Li

nk

#2

SA

->

->

DA

00

:20

:8f:

0b

:e1

:03

00

:20

:8f:

0a

:e1

:01

01

0

10

10

10

(2)

Lin

k #

3

SA

->

->

DA

00

:20

:8f:

0b

:e1

:07

00

:20

:8f:

0a

:e1

:04

11

1

10

00

11

(3

)Li

nk

#4


Static LAG guidelines

131.Only traffic ports (including radio port) can belong to a LAG

2.Management ports / W

SC ports cannot be grouped in a LAG

3.LAG is supported in IDUs configured as M

anaged or Metro switch

4.LAG is not supported in a Single Pipe m

ode

5.All ports in a LAG must be in the same IDU (same switch)

6.There may be up to 3 LAGs per IDU

7.A LAG m

ay contain from 1 to 5 physical ports


8. LAGs are virtual ports that do not perm

anently exist in the system

9. When a LAG is created, it will automatically inherit all the ports’

characteristics, except for the following:

•xSTProle (edge, non-edge)

•path cost

10. The LAG will initially receive default values for these parameters

11. Dynamic Link Aggregation (LACP) is not supported

Static LAG guidelines (continued)

14


Grouping ports in LAG

15Ports 1-2 (GBE ports) and ports 3-7 (FE only ports) cannot be in the same LAG

group even if the GBE ports are configured as 100Mbps.

12

34

56

78

FE

12

34

56

78

FE

Gb

EG

bE

IP-10 IDU

IP-10 IDU


Grouping ports in LAG

16Radio port (port 8) may be in a LAG with the GBE ports only

12

34

56

78

FE

12

34

56

78

FE

Gb

EG

bE

IP-10 IDU

IP-10 IDU

Ap

pli

cati

on

s


Introduction to Link Aggregation

18Multiple PHYs are grouped together to support a higher capacity PHY.

Grouped ports are known as LAG –

Link Aggregation Group.

Multiple FE

ports as a LAG

Stackable

(Nodal) Site

12

34

56

78

12

34

56

78

GbE

PHY

12

34

56

78

GbE

PHY

Multiple Radio System

implemented with LAG

Standalone Site

Port #2 and Radio

form

a LAG

Single Pipe


1+0 LAG

19•Dual (redundant) GbE interfaces facing the Switch/Router

•Static Link Aggregation Group (or equivalent) configured on the Switch/Router

interfaces connected to the IP-10

•Any failure in the local GbE interfaces will be handled by the link aggregation m

echanism

12

34

56

78

3rdparty

Switch or Router

Static LAG


1+1 HSB W

/O LAG

20•

Single GE interfacing a 3

rdparty Switch/Router

•Optical splitter/combiner is used to connect to each of the IP-10 GbEinterfaces in

(1+1) protected configuration

•STBY IP-10 GbEinterface is disabled

•MW Radio link switchovers are transparent to Switch/Router

(traffic interruption <50mSecs)

12

34

56

78

12

34

56

78

3rdparty

Switch or Router

1+1 HSB or

2+0 “Multi-Radio”

No need for LAG


1+1 HSB W

ith LAG

21•Dual (redundant) GE interfaces facing the 3rdparty Switch/Router

•Static Link Aggregation Group (or equivalent) is configured on the Switch/Router

interfaces connected to the IP-10 units

•STBY IP-10 disables its Ethernet interface towards the Switch/Router

•As a result, the Switch/Router sends all traffic over the Ethernet interface connected to

the “active” IP-10

•Any failure detected in radio link or Ethernet interface will trigger a switch-over to the

“back-up” unit with <50msecs traffic interruption on the radio link

•The Switch/Router detects the switch-over and start sending traffic over the interface

connected to the new “active” unit only

12

34

56

78

12

34

56

78

3rdparty

Switch or Router

Static LAG

1+1 HSB or


No need for LAG


1+1 HSB W

ith dual GbE + LAG

22•Dual (redundant) GE interface to the Switch/Router

•Static Link Aggregation Group (or equivalent) is configured on the Switch/Router

interfaces connected to the IP-10s

•Static Link Aggregation Group (or equivalent) is configured on the IP-10

•2 optical splitter/combiners are used to connect each of the 2 interfaces on the

Switch/Router to each of the corresponding interfaces on the IP-10s

12

34

56

78

12

34

56

78

3rdparty

Switch or Router

Static LAG

Static LAG

Static LAG

1+1 HSB or



1+1 HSB W

ith dual GbE + LAG (cont.)

23•STBY IP-10 disables its Ethernet interface towards the Switch/Router

•Any failure detected in radio link or equipment will trigger switch-over to the “back-up”

IP-10 unit with <50msecs traffic interruption on the radio link

•Any failure in the local GbE interfaces will be handled by the link aggregation

mechanism without triggering switch-over to the “back-up” IP-10 unit!

12

34

56

78

12

34

56

78

3rdparty

Switch or Router

Static LAG

Static LAG

Static LAG

1+1 HSB or


Loa

d B

ala

nce

Exa

mp

le


Load balance example

25

IDU #2 is configured as Single Pipe

IDU #1 is configured as M

anaged Switch to support LAG

Traffic injected via GbE port #1 is distributed evenly between Port #2 & Port #8

Port #2 is linked to a Pipe IDU, hence, a M

ulti-Radio system is achieved:

12

34

56

78

12

34

56

78

GbE

PHY

P S

Port #2 and Radio

form

a LAG

50%

50%

GbE port #1 = (50% via Radio #1) + (50% via Radio #2)



26

1)Radio #2 encounters a signal degradation

2)Since ASP is enabled, the alarm

is propagated to port #1

3)IDU #1 detects the alarm

s and shuts down port #2

4)Port #2 is not part of the LAG

5)Radio #1 takes full control (100%) of traffic

Enable Automatic State Propagation on both IDUs

12

34

56

78

12

34

56

78

GbE

PHY

P S

100%

50%

X

1) Link

Degradation

2) Alarm

is

propagated

4) Port 2 is out

of the LAG

3) Port 1 is

shut down

5) Radio 1

takes 100%



27To improve system resiliency, Automatic State Propagation can shut down the

LAG interface when ACM degrades below a pre-determ

ined profile.

12

34

56

78

12

34

56

78

GbE

PHY

P S

100%

50%

X

256QAM

64QAM

Shut down

100%


Th

an

k Y

ou

!

tra

inin

g@

cera

go

n.c

om

28

Ceragon IP 10 - LAG

Documents

Transcript of Ceragon IP 10 - LAG