White Paper

Eclipse Packet Node Link Aggregation

Executive Summary
Link aggregation provides a solution where more traffic capacity is needed than can be
transported over one physical link. Two or more links are aggregated to provide one logical
link with a capacity that is the sum of the individual links. This feature is particularly useful for
wireless transmission systems where multiple radio links must be used in parallel to achieve
very high capacities of 1Gbit/s and above.
With both L1 and
Eclipse Packet Node uniquely supports two link aggregation options, implemented at Layer 2
L2 capabilities,
(L2), and now a new highly effective option using Layer 1 (L1). Both solutions have particular
Eclipse Packet benefits for different applications:
Node enables L2 link aggregation uses MAC address data to direct individual Ethernet traffic
optimum link sessions over one physical link or another within the link aggregated group.
aggregation L1 link aggregation splits all traffic between the links on a byte-by-byte basis, based on
solutions for NW the capacity of the links. Unlike L2, it is fully effective for just one active session, such
as between two routers, or where there are only a few concurrent sessions.
operators.
L1 also supports higher burst capacities throughput can burst to the aggregated total
capacity, whereas L2 throughput cannot burst beyond the capacity of individual links.
Both L2 and L1 link aggregation support redundancy data from a failed link is
directed onto the remaining link, or links.
L1 or L2 link aggregation can be used to aggregate Eclipse radio links, but L2 is
needed to aggregate Eclipse radio links with 3rd party radio, fiber or wireline links.
Consequently, L1 link aggregation with its perfect load balancing and higher burst capability
Eclipse Packet
is the preferred solution for aggregation of multiple Eclipse radio links. L2 link aggregation
Node L1 link must be used for aggregation with 3rd party links.
aggregation
always provides Introduction
optimum load The Eclipse DAC GE card is an advanced switch, providing transport of Fast and Gigabit
Ethernet traffic, and has been certified as both MEF 9 and MEF 14 compliant to support
balancing.
carrier-class Ethernet transport.
Industry standard
As well as L2 and L1 link aggregation, its features include extremely low latency,
L2 (802.3ad) does programmable switching fabric, comprehensive QoS policing and prioritization (802.1p,
not. DiffServ), VLAN tagging (802.1Q and 802.1Q-in-Q), RWPRTM enhanced RSTP (802.1d), flow
control, and comprehensive RMON and performance indicators.
A glossary of terms is provided at the end of this paper.

What Is Link Aggregation?

Headquarters
Link aggregation aggregates two or more physical data links so they appear as a single,
Harris Stratex Networks, Inc.
higher-bandwidth logical link. The resultant traffic capacity is the sum of the individual link
Research Triangle Park
capacities. Two link-aggregated links may be operated on the same frequency channel using
637 Davis Drive
Eclipse co-channel dual polarized (CCDP) options.
Morrisville,
North Carolina 27560 Aggregated links can be established using multiple Eclipse radio links or in combination with
United States other radio, fiber or wireline links. These aggregated links can then be used to provide
Tel: 919-767-3230
Fax: 919-767-3233

www.harrisstratex.com 3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 1 of 8

 White Paper

redundancy, so if one of the physical links fails, affected traffic is directed onto the remaining
link(s).
If the remaining link(s) do not have the capacity needed to avoid a traffic bottleneck, the
Eclipse DAC GE provides appropriate QoS settings that can be used to prioritize traffic to
Both L1 and L2 ensure that all high priority traffic continues to get through.
support traffic To provide a similar level of redundancy without aggregation, hot-standby or diversity
redundancy. protection is required, but with such protection the standby equipment cannot be used to
pass traffic. Using Link Aggregation, Eclipse enables what would normally be standby
Traffic on a failed
equipment to now carry traffic during the time when there is no fault condition, essentially
link is directed providing double the capacity, with redundancy, and without additional costs.
onto the
remaining link(s). Layer 2 Link Aggregation
L2 link aggregation (IEEE 802.3ad) uses MAC address data in the Ethernet frame MAC/LLC
header to direct traffic streams onto one physical link or another.

Aggregation Key
Traffic streams to transit the logical link are split between the physical links. This is based on
their source and destination MAC addresses and the 'aggregation key' allocated to each of
the physical links within the link aggregation group (LAG). Splitting prevents the occurrence
of an IP loop, even though all traffic is sent and received on a common LAN interface at each
end of the logical link.
The aggregation key process is a layer 2 function that sets the weighting (load balancing) of
traffic between the links in the LAG. The DAC GE switch incorporates 16 keys, and traffic is
allocated between them on a random (hash) basis using its source and destination MAC
address.
The number of keys assigned to each of these ports is based on the split of capacity between
the links. For example, if the aggregated group comprises two links of equal capacity, the
keys are assigned as 8/8. But for a 300 Mbit/s link aggregated with a 150 Mbit/s link, the
former is allocated 11 keys, and the latter 5 keys. The number of keys applied must always
total 16, and is user-configurable.

Load Balancing
L2 link aggregation provides good load balancing between the physical links under normal
traffic densities where multiple concurrent sessions (20+) exist between different MAC source
and destination addresses.
But where there is only a single MAC address in play, such as a connection between two
routers, L2 link aggregation is not effective. All traffic goes via one link - the other link(s) in
the aggregation group carry no traffic.
L2 supports Where there are just a handful of MAC source and destination addresses in play (less than
16), link load balancing may be less than optimum, particularly where just one or a few of the
aggregation of sessions have relatively high throughput demands.
links over
Burst speeds are limited to the bandwidth provided on the individual physical links.
different network
media; radio fiber Redundancy
or wireline. Redundancy (data recovery) is a feature of L2 link aggregation. If a link within the LAG fails,
all traffic from the failed link is directed to the remaining link(s). If directed to more than one
link, aggregation keying applies an equitable split between the links. Traffic on the remaining
link, or links, is not affected when traffic from the failed link is added - except in instances
3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 2 of 8
Copyright 2009 Harris Stratex Networks, all rights reserved.
 White Paper

where available bandwidth is contested (over-subscribed). To ensure only low priority data is
affected (dropped), QoS settings can be configured so that all high priority data continues to
get through.
When a failed link is returned to service, aggregation keying restores load sharing across all
links. Existing traffic is not affected.

Aggregation over Different Media

L2 link aggregation can aggregate physical links over the same or different media. The links
(up to four) can be provided over Eclipse radio and/or fiber links, or over Eclipse and 3rd party
radio, fiber or leased-line links on a service-provider network.

Layer 1 Link Aggregation

The new L1 (physical layer) link aggregation option is used to aggregate multiple Eclipse
L1 is needed for radio links to support very high link capacities to 1 Gbit/s by splitting ingressing data between
single-session the links on a byte-by-byte basis. This provides optimum payload balance, regardless of the
throughput demands of individual user connections.
connections
(between routers). Whether there is one, a few, or many concurrent sessions, traffic is always split precisely
between the links based on the configured capacity of the links.
It should also be
Redundancy is also a feature of Eclipse L1 link aggregation. If a link is lost, its traffic is
used where there directed onto the remaining link(s) within the LAG. All traffic is momentarily affected (~10 ms),
are just a few and when the failed link is restored to service, all traffic is again momentarily affected.
concurrent If the Ethernet bandwidth on the remaining link(s) is over-subscribed, traffic will be dropped,
sessions. though with appropriate QoS settings only low priority data will be affected - all high priority
data will continue to get through.
Eclipse L1 link aggregation is fully effective where there is just one source and destination
MAC address session in play, such as between two routers, or in connections where there
are just a few sessions in play, particularly so if one or two sessions tend to dominate the
available bandwidth.
Higher burst speeds are also a feature of L1 link aggregation, where session throughputs can
burst to the aggregated total.

L2 Versus L1 Link Aggregation

Table 1 compares the main operating characteristics of Eclipse L2 and L1 link aggregation.

Table 1. L2 Versus L1 Link Aggregation

Function L2 Aggregation L1 Aggregation
Number of links that Maximum 4. Maximum 4.
can be aggregated.
L1 aggregates
Maximum aggregated 1000 Mbit/s. 1000 Mbit/s.
Eclipse radio throughput.
links it is not for Physical link Individual Ethernet links within the Individual Ethernet links within the
use where one or bandwidths LAG can be of any capacity. Over LAG are configured in multiples of
Eclipse radio links bandwidth is 150 Mbit/s. An Nx2 Mbit/s and
more links are configured in Nx150 Mbit/s, Nx2 Nx1.5 Mbit/s capability is planned.
Mbit/s, or Nx1.5 Mbit/s steps.
over other media.
Load balancing Not effective where only one Fully effective from one through
source/destination MAC address is

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 3 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.
 White Paper

Function L2 Aggregation L1 Aggregation

in play, such as between two many concurrent traffic sessions.
routers. Ingressing traffic on the master DAC
Limited effectiveness where a few GE is simply split across all links in
concurrent sessions are in play, the LAG on a byte-by-byte basis,
especially so where one or two based on the path size (capacity) of
streams dominate throughput on each link within the LAG.
one link.
Effective for multiple (20+)
concurrent traffic sessions.
Traffic is assigned to a link using an
algorithm, which does a simple
placing based on the source and
destination MAC addresses for each
traffic stream.
Individual traffic streams cannot split
across links within the LAG.
Session burst capacity Individual session throughputs Throughputs can burst to the
cannot burst beyond the capacity combined capacity provided on the
Higher burst provided on the individual links in aggregated link group.
speeds are also a the link group.
feature of L1 link Traffic redundancy Yes. Traffic from a failed link is Yes. Traffic from a failed link is
directed onto the other link, or links. directed onto the remaining link, or
aggregation. Service restoration times are links.
typically less than 20 ms where links During re-direction all traffic is
are managed under Eclipse Rapid interrupted for ~10 ms.
Failure Detection.
Traffic priority options are used to
Traffic on the surviving link(s) is not ensure all high priority traffic
affected during the re-direction continues to get through on the
process, unless displaced by higher remaining link, or links, when
priority traffic from the failed link. available bandwidth is over-
Traffic priority options are used to subscribed.
ensure all high priority traffic
continues to get through on the
remaining link, or links, when
available bandwidth is over-
subscribed.
Recovery from a link When a failed link is returned to Traffic is restored end-to-end across
failure service traffic is re-assigned to it by the links.
the load sharing mechanism. All traffic is momentarily interrupted
Existing traffic is not interrupted. for ~10 ms when the failed link is
L1 is used to link- returned to service.
aggregate Eclipse Aggregation overhead Not significant. None.
radio links. Compatible with 3rd Yes. Supports link aggregation with No. All links within the LAG must be
L2 is used where party Ethernet one or more 3rd party Ethernet established over Eclipse radio links.
switches. network links. For example, one
links over other Eclipse radio or fiber link link-
media are aggregated with a service-provider
radio, fiber or wireline link.
included in the
Can be used with Yes. Yes.
LAG. Eclipse co-channel
XPIC links

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 4 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.
 White Paper

Figure 1 shows a network link between a video server and a DSLAM, and illustrates the
primary advantage of L1 link aggregation. L1 link aggregation is fully effective for network
connections between routers; L2 is not effective at all.
Similar applications exist between two IP/MPLS routers in a core network, or communication
between two routers in an Enterprise network. These are typical of the bandwidth intensive
connections where L1 link aggregation can provide a cost effective solution for more network
capacity.
Figure 1. Eclipse 760 Mbit/s (2x382 Mbit/s) CCDP Terminal

Typical Configurations
For link aggregation of Eclipse radio links, L1 link aggregation should always be used
because of its perfect load balancing and higher session burst capability. L2 link aggregation
must be used where an Eclipse link is aggregated with 3rd party radio, fiber, or wire links.
Two link-
Identical link capacities are normally configured, though this is not a requirement. For
aggregated radio
example, a 300 Mbit/s link can be link aggregated with a 150 Mbit/s link to support a 450
links can operate Mbit/s logical link.
on the same RF Figure 2 illustrates an Eclipse Packet Node 760 Mbit/s logical link comprising two 382 Mbit/s
channel using physical links. The links are configured on one 56 MHz RF channel using RAC 6X CCDP
(Co-channel Dual Polarized) operation. L1 link aggregation is used.
Eclipse CCDP
XPIC options. Note that the capacities used in these diagrams represent L2 throughputs before application
of IFG and Preamble suppression and L2 header compression (MAC address compression),
which support significant gains in effective throughput, depending on frame size.

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 5 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.
White Paper

Figure 2. Eclipse 760 Mbit/s (2x382 Mbit/s) CCDP Terminal

Figure 3 illustrates an Eclipse INUe configured as a 680 Mbit/s logical link where 28 MHz is
the maximum available channel size. Using CCDP, two 190 Mbit/s links are established on
one 28 MHz channel with RAC 6X cards, and two 150 Mbit/s radio links on a separate 28
MHz channel with RAC 40 cards. Combiners support connection to a single antenna. L2 link
aggregation is used.
A 760 Mbit/s logical link solution from one INUe can be configured by installing an additional
DAC GE card and using the RAC 6X on all four physical links. L1 link aggregation is used.
Figure 3. Eclipse 680 Mbit/s (2x190 + 2x150 Mbit/s) CCDP Terminal

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 6 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.
White Paper

Figure 4 illustrates a 320 Mbit/s logical link comprising an Eclipse Packet Node 190 Mbit/s 28
MHz link and an existing STM1 link transporting a 130 Mbit/s Ethernet over STM payload.
The mapping of Ethernet to STM1 is enabled by a DAC 155oM card in the Eclipse INU.
The DAC 155oM maps Ethernet to STM1 at 2.048 Mbit/s per VC12/E1 tributary. The
maximum 63xVC12 enables 130 (129.024) Mbit/s on the STM1 path.
A RAC 60 provides a front-plane 190 Mbit/s GigE connection to the DAC GE for L2
link aggregation with the 130 Mbit/s from the DAC 155oM. A 28 MHz RF channel is
used (256 QAM).
The RAC 60 link can be configured to provide a 382 Mbit/s GigE connection using a
56 MHz channel, for an aggregated total of 512 Mbit/s.
Figure 4. Aggregation of Eclipse Ethernet and Ethernet over STM1 Links

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 7 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.
 White Paper

Summary
With its L1 and L2 With capacity demands on wireless network infrastructure continuing to grow, link
aggregation provides a cost efficient option for higher throughputs. It is especially attractive
options, and with CCDP, where an existing RF channel is configured to support two radio links using both
physical link the vertical and horizontal polarizations.
capacities to 380 Similarly, where the wider 56 MHz RF channels needed to support a high link capacity are
Mbit/s, Eclipse not available, link aggregation of two links on one 28 MHz channel provides a solution.
Packet Node The fact that traffic redundancy is provided on the aggregated L1 or L2 links is a major plus.
To provide a similar level of redundancy without aggregation, hot-standby or diversity
provides the most
protection is required, but with such protection the standby equipment is not used to pass
bandwidth traffic.
efficient and cost With both L1 and L2 options, Eclipse provides effective link aggregation solutions for all
effective radio link network needs. With its perfect load balancing, L1 is used for aggregation of Eclipse radio
links. L2 is used where Eclipse links are aggregated with links transported over other media.
aggregation
With these and other intelligent options for Ethernet and TDM, Eclipse delivers unrivalled
solutions.
performance and flexibility for wireless network connections.

Glossary
CCDP Co-channel dual polarized.
GigE Gigabit Ethernet.
L1 Layer 1
L2 Layer 2
LAG Link aggregation group.
MAC Media-specific access control.
MEF Metro Ethernet Forum. The MEF is an industry focal point for Carrier Ethernet. It is a non-
profit organization with over 150 active members, representing all Carrier Ethernet industry
groups. Its mission is to accelerate worldwide adoption of carrier-class Ethernet.
QAM Quadrature amplitude modulation.
QoS Quality of service.
RMON Remote network monitoring.
RSTP Rapid spanning tree protocol.
TM
RWPR Resilient Wireless Packet Ring.
TDM Time division multiplex.
VLAN Virtual LAN.
XPIC Cross-polarized interference cancellation.

3/25/2009 Eclipse Packet Node Link Aggregation.doc Page 8 of 8

Copyright 2009 Harris Stratex Networks, all rights reserved.