Technical Configuration Guide

Link Aggregation
Link Aggregation Configuration


Table of Contents
Table of Contents ................................................................................................................................... 2
Introduction ............................................................................................................................................ 4
Background Information ........................................................................................................................ 4
Requirements ..................................................................................................................................... 4
Configure ................................................................................................................................................ 5
Configuration Example Link-Aggregation of 802.1q trunk ports with LACP .................................. 5
Network diagram ............................................................................................................................ 5
Configuration steps ........................................................................................................................ 5
Step 1 Create a logical Bridge-Aggregation interface ................................................................ 5
Step 2 Enable the Link Aggregation Control Protocol ................................................................ 5
Step 3 Assign physical interfaces to the Bridge Aggregation Group .......................................... 6
Step 4 Configure the Bridge-Aggregation interface as a trunk port .......................................... 6
Step 5 Permit the desired VLANs on the Bridge-Aggregation interface ..................................... 6
Verify Link-Aggregation of Trunk Ports with LACP ........................................................................ 6
Configuration Example Static Link-Aggregation of 802.1q trunk ports (without LACP) ................ 9
Network diagram ............................................................................................................................ 9
Configuration steps ........................................................................................................................ 9
Step 1 Create a logical Bridge-Aggregation interface .............................................................. 10
Step 2 Assign physical interfaces to the Bridge Aggregation Group ........................................ 10
Step 3 Configure the Bridge-Aggregation interface as a trunk port ........................................ 10
Step 4 Permit the desired VLANs on the Bridge-Aggregation interface ................................... 10
Verify Static Link-Aggregation ..................................................................................................... 11
Configuration Example Link-Aggregation of multiple access ports with LACP ............................ 13
Network Diagram ......................................................................................................................... 13
Configuration steps ...................................................................................................................... 13
Step 1 Create a logical Bridge-Aggregation interface .............................................................. 13
Step 2 Enable the Link Aggregation Control Protocol .............................................................. 13
Step 3 Assign physical interfaces to the Bridge Aggregation Group ........................................ 13
Step 4 Configure the Bridge-Aggregation interface as an access port in the desired VLAN. ... 14
Verify Link-Aggregation with Access Ports .................................................................................. 14
Additional Information ......................................................................................................................... 15
Configuration steps .......................................................................................................................... 15
Create a logical Bridge-Aggregation interface ............................................................................ 15
Enable the Link Aggregation Control Protocol (optional) ............................................................ 16
Assign physical interfaces to the Bridge Aggregation Group ...................................................... 16
Configure the link-mode and VLANs on the Bridge-Aggregation interface ................................ 16
Troubleshoot ........................................................................................................................................ 16
Common Misconfigurations ............................................................................................................. 17
Problem: No Member Ports Selected ........................................................................................... 17
Problem: LACP mismatch ............................................................................................................. 18
For more information ........................................................................................................................... 19



Technical Configuration Guide Link Aggregation 4

Introduction
This Technical Configuration Guide (TCG) describes how to configure Link Aggregation under Comware OS. The
intended audience is HP solution architects and technical consultants.
What is Link Aggregation?
When two or more Ethernet links are directly connected between two switches, the Multiple Spanning Tree
Protocol (MSTP) blocks all but one of the links in each MSTP instance to avoid loops. The full bandwidth potential
of the multiple links may not be achieved.
Link Aggregation binds multiple Ethernet links into one aggregate link and shares the traffic load onto the
multiple links in a manner that avoids looping. MSTP is unaware of the components of the aggregate link and
treats the aggregate link as a single spanning tree link with a cost representative of the aggregate link.
The configuration of Link Aggregation consists of creating a logical interface that represents the aggregate link
and then binding the physical interfaces to the logical interface. Finally, the desired characteristics of the link are
configured on the logical interface.
Background Information
This section provides some background information related to this TCG.
Requirements
Readers of this document should be familiar with the basic Comware data-link layer configuration commands
including Virtual Local Area Networks (VLANs), access ports, and trunk ports.
Considerations:
Link Aggregation is configured on two switches. Both switches must be configured.
All physical interfaces that are part of the Link Aggregation must function at the same speed.
Link Aggregation is designed for point-to-point Ethernet links.
All physical interfaces that are part of the Link Aggregation will be configured similarly.
The following hardware is required:
Manageable switches or routers with bridged interfaces under Comware OS.
The following software is required:
Comware 5.20


Technical C

Config
Configu
Network
Configur
To configu
steps:
Cr
En
As
Co
Pe
Step 1
Create a lo
as part of a
The Bridge
Bridge-Agg
# Swi t
i nt er f

# Swi t
i nt er f
Step 2
Enable LAC
LACP must
# Swi t
i nt er f
l i

Configuration
gure
uration Ex
k diagram
Fig
ration step
ure Link Aggreg
reate a logical
nable Link Agg
ssign physical
onfigure the B
ermit desired V
Create a lo
ogical Bridge-A
any other Link
e-Aggregation
gregation grou
t ch- A
f ace br i dge
t ch- B
f ace br i dge
Enable the
CP on the Bridg
t be configured
t ch- A
f ace br i dge
i nk- aggr eg
Guide Link A
xample L
gure 1 Link agg
s
gation of 802.1
Bridge-Aggreg
gregation Cont
interfaces to t
ridge-Aggrega
VLANs on the B
ogical Bridg
Aggregation int
k Aggregation.
group number
up number on
e- aggr egat
e- aggr egat
e Link Aggre
ge-Aggregatio
d prior to assig
e- aggr egat
gat i on mode
ggregation
Link-Aggr
gregation with
1q trunk ports
gation interfac
rol Protocol.
the logical Brid
ate interface as
Bridge-Aggreg
ge-Aggrega
terface. Choos

r is locally sign
the connecting
t i on 3
t i on 1
egation Con
n interface of
gning physical
t i on 3
e dynami c
regation o
h LACP on two T
with Link Agg
ce.
dge-Aggregati
s a trunk port.
gate interface.
ation interfa
se an interface
nificant to a sw
g switch.
ntrol Proto
both switches
interfaces to t
of 802.1q
Ten-Gigabit Et
regation Contr
on interface.


ace
e number that i
witch. This num
col
s.
the Bridge Grou
trunk por
thernet links
rol Protocol, L
is not already
mber does not
up (Step 3).

rts with LA
ACP, follow th
in use on the s
need to match
5
ACP

ese
switch
h the

Technical Configuration Guide Link Aggregation 6

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1
l i nk- aggr egat i on mode dynami c
Step 3 Assign physical interfaces to the Bridge Aggregation Group
Assign the physical interfaces that are to be part of this link aggregation to the Bridge Aggregation group. The
group-member number used in this step must match the Bridge Aggregation number used in the previous step.
# Swi t ch- A
i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 25
l i nk- aggr egat i on gr oup- member 3

i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 26
l i nk- aggr egat i on gr oup- member 3

# Swi t ch- B
i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 27
l i nk- aggr egat i on gr oup- member 1

i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 28
l i nk- aggr egat i on gr oup- member 1
Step 4 Configure the Bridge-Aggregation interface as a trunk port
Configure the Bridge-Aggregate interface as an 802.1q trunk interface.
Do not configure trunk commands on the physical interfaces. The trunk configuration will be placed on the
physical link interfaces automatically.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3
por t l i nk- t ype t r unk

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1
por t l i nk- t ype t r unk
Step 5 Permit the desired VLANs on the Bridge-Aggregation interface
By default an 802.1q trunk interface permits only VLAN 1. Permit any additional VLANs required on the aggregate
link and select the PVID if necessary.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3
por t t r unk per mi t vl an al l

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1
por t t r unk per mi t vl an al l
Verify Link-Aggregation of Trunk Ports with LACP
To verify the configuration of Link-Aggregation of 802.1q trunk ports with LACP, follow these steps:
Verify that the Bridge-Aggregation interface has selected all of the physical interfaces.

Technical Configuration Guide Link Aggregation 7


Figure 2 Verification with the display link aggregation summary command

ITEM DESCRIPTION
1. Dynamic mode indicates LACP is enabled
2. Both member ports are selected


<SwitchA> display link-aggregation summary
Aggregation Interface Type:
BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, 3ce5-a6cf-1219
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
--------------------------------------------------------------------------
BAGG3 D 0x8000, 3ce5-a680-9cb6 2 0 Shar
2.
Bridge-Aggregation
interface
LAG-01
1.

Technical Configuration Guide Link Aggregation 8

Verify that LACP is active, collecting, and distributing.
Verify that the physical cables connect to the same peer.

Figure 3 Verification with display link aggregation verbose command

ITEM DESCRIPTION
1. Both member ports are selected
2. LACP confirms that member ports connect to the same peer
3. MAC address of peer for each link


<SwitchA> display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregation Interface: Bridge-Aggregation3
Aggregation Mode: Dynamic
Loadsharing Type: Share
System ID: 0x8000, 3ce5-a6cf-1219
Local:
Port Status Priority Oper-Key Flag
-----------------------------------------------------------------------------
XGE1/0/25 S 32768 1 {ACDEF}
XGE1/0/26 S 32768 1 {ACDEF}
Remote:
Actor Partner Priority Oper-Key SystemID Flag
-----------------------------------------------------------------------------
XGE1/0/25 83 32768 1 0x8000, 3ce5-a680-9cb6 {ACDEF}
XGE1/0/26 84 32768 1 0x8000, 3ce5-a680-9cb6 {ACDEF}
2.
1.
3.
LAG-02

Technical C

Ve
Ve

Configu
(withou
Network
The netwo
Configur
To configu
Cr
As
Co
Pe
1.
Configuration
erify that the B
erify the aggre
Figu
ITEM
1.
uration Ex
ut LACP)
k diagram
ork diagram be
Figure 5
ration step
ure Link Aggreg
reate a logical
ssign physical
onfigure the B
ermit desired V
<Switch-A>
Bridge-Ag
IP Packet
Descripti
20Gbps-sp
Link spee
PVID: 1
Port link
VLAN pas
VLAN per
Trunk po
Guide Link A
Bridge-Aggreg
egate bandwid
ure 4 Verificati
DESCRIPTION
Aggregate ban
xample S
elow illustrates
Link Aggregati
s
gation of 802.1
Bridge-Aggreg
interfaces to t
ridge-Aggrega
VLANs on the B
> display i
ggregation3
t Frame Typ
ion: Bridge
peed mode,
ed type is
k-type: tru
ssing : 1(
rmitted: 1(
ort encapsu
ggregation
gation interface
dth represents
ion with displa
ndwidth
Static Link
s the connectiv
ion with two 8
1q trunk ports
gation interfac
the logical Brid
ate interface as
Bridge-Aggreg
interface B
3 current s
pe: PKTFMT_
e-Aggregati
full-duple
autonegoti
unk
(default vl
(default vl
ulation: IE
e is an 802.1q
the aggregate
ay interface bri
k-Aggrega
vity for this con
02.1q Ten-Gig
, follow these
ce.
dge-Aggregati
s a trunk port.
gate interface.
Bridge-Aggre
state: UP
_ETHNT_2, Ha
ion3 Interfa
ex mode
iation, link
lan), 2-100
lan), 2-4094
EEE 802.1q
trunk port.
e bandwidth of
idge aggregati
ation of 8
nfiguration ex
gabit Ethernet
steps:
on interface.


egation 3
ardware Add
ace
k duplex ty
4
80
f all links.
ion command
02.1q tru
xample.
links without L
dress: 000f
ype is auto
02.1q trunk

nk ports
LACP
f-e207-f2e0
onegotiatio
LAG-03
9


0
on
3

Technical Configuration Guide Link Aggregation 10

Step 1 Create a logical Bridge-Aggregation interface
Create a logical Bridge-Aggregation interface. Choose an interface number that is not already in use on the switch
as part of any other Link Aggregation.
The Bridge-Aggregation group number is locally significant to a switch. This number does not need to match the
Bridge-Aggregation group number on the connecting switch.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1
Step 2 Assign physical interfaces to the Bridge Aggregation Group
Assign the physical interfaces that are to be part of this link aggregation to the Bridge Aggregation group. The
group-member number used in this step must match the Bridge Aggregation number used in the previous step.
# Swi t ch- A
i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 25
l i nk- aggr egat i on gr oup- member 3

i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 26
l i nk- aggr egat i on gr oup- member 3

# Swi t ch- B
i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 27
l i nk- aggr egat i on gr oup- member 1

i nt er f ace Ten- Gi gabi t Et her net 1/ 0/ 28
l i nk- aggr egat i on gr oup- member 1
Step 3 Configure the Bridge-Aggregation interface as a trunk port
Configure the Bridge-Aggregate interface as an 802.1q trunk interface.
Do not configure trunk commands on the physical interfaces. The trunk configuration will be placed on the
physical link interfaces automatically.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3
por t l i nk- t ype t r unk

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1
por t l i nk- t ype t r unk
Step 4 Permit the desired VLANs on the Bridge-Aggregation interface
By default an 802.1q trunk interface permits only VLAN 1. Permit any additional VLANs required on the aggregate
link and select the PVID if necessary.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3
por t t r unk per mi t vl an al l

# Swi t ch- B
i nt er f ace br i dge- aggr egat i on 1

Technical Configuration Guide Link Aggregation 11

por t t r unk per mi t vl an al l
Verify Static Link-Aggregation
To verify the configuration of static Link-Aggregation of 802.1q trunk ports, follow these steps:
Verify that the Bridge-Aggregation interface has selected all of the physical interfaces.

Figure 6 Verification with the display link aggregation summary command
ITEM DESCRIPTION
1. Static mode indicates LACP is not enabled
2. Partner MAC address is unknown without LACP
3. Both member ports are selected


<SwitchA> display link-aggregation summary
Aggregation Interface Type:
BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, 3ce5-a6cf-1219
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
-------------------------------------------------------------------------
BAGG3 S none 2 0 Shar
1. 2.
3.
Bridge-Aggregation
interface
LACP-04

Technical Configuration Guide Link Aggregation 12

Verify link aggregation mode is static.

Figure 7 Verification with the display link aggregation verbose command
ITEM DESCRIPTION
1. Static indicates LACP is not enabled
2. Both member ports are selected


<SwitchA> display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregation Interface: Bridge-Aggregation3
Aggregation Mode: Static
Loadsharing Type: Shar
Port Status Priority Oper-Key
------------------------------------------------------------------
XGE1/0/25 S 32768 1
XGE1/0/26 S 32768 1
1.
2.
LACP-05

Technical C

Configu
LACP
Network
The netwo
Configur
To configu
Cr
En
As
Co
Step 1
Create a lo
as part of a
# Swi t
i nt er f
Step 2
Enable LAC
LACP must
# Swi t
i nt er f
l i
Step 3
Assign the
group-mem
# Swi t
i nt er f
l i
Configuration
uration Ex
k Diagram
ork diagram be
Figure 8
ration step
ure Link Aggreg
reate a logical
nable the Link
ssign physical
onfigure the B
Create a lo
ogical Bridge-A
any other Link
t ch- A
f ace br i dge
Enable the
CP on the Bridg
t be configured
t ch- A
f ace br i dge
i nk- aggr eg
Assign phy
physical inter
mber number
t ch- A
f ace Gi gabi
i nk- aggr eg
Guide Link A
xample L
elow illustrates
8 Link aggrega
s
gation of acces
Bridge-Aggreg
Aggregation C
interfaces to t
ridge-Aggrega
ogical Bridg
Aggregation int
k Aggregation.
e- aggr egat
e Link Aggre
ge-Aggregatio
d prior to assig
e- aggr egat
gat i on mode
ysical interf
rfaces that are
used in this ste
i t Et her net
gat i on gr ou
ggregation
Link-Aggr
s the connectiv
ation of two Gi
ss ports with L
gation interfac
Control Protoco
the logical Brid
ate interface as
ge-Aggrega
terface. Choos

t i on 3
egation Con
n interface of
gning physical
t i on 3
e dynami c
faces to the
to be part of t
ep must match
t 1/ 0/ 14
up- member
regation o
vity for this con
gabit Ethernet
LACP, follow th
ce.
ol.
dge-Aggregati
s an access po
ation interfa
se an interface
ntrol Proto
the switch.
interfaces to t
e Bridge Ag
this link aggreg
h the Bridge Ag
3
of multiple
nfiguration ex
t links access
hese steps:
on interface.
ort in the appro
ace
e number that i
col
the Bridge Grou
ggregation G
gation to the B
ggregation num
e access p
xample.
s ports with LA
opriate VLAN.
is not already
up (Step 3).
Group
Bridge Aggrega
mber used in t

ports with

ACP
in use on the s
ation group. Th
the previous st
13
h
switch
he
tep.

Technical Configuration Guide Link Aggregation 14


i nt er f ace Gi gabi t Et her net 2/ 0/ 14
l i nk- aggr egat i on gr oup- member 3
Step 4 Configure the Bridge-Aggregation interface as an access port in the desired
VLAN.
Configure the Bridge-Aggregate interface as an access port and place the Bridge Aggregate interface into the
desired VLAN.
Do not configure access port commands or VLAN commands on the physical interfaces. These commands will be
placed on the physical interfaces automatically.
If any physical interfaces were previously configured as trunk ports, they will be changed to access ports
automatically.
# Swi t ch- A
i nt er f ace br i dge- aggr egat i on 3
por t l i nk- t ype access
por t access vl an 100
Verify Link-Aggregation with Access Ports
To verify the configuration of Link-Aggregation of access ports with LACP, follow these steps:
Verify that the Bridge-Aggregation interface has selected all of the physical interfaces.

Figure 9 Verification with the display link aggregation summary command
ITEM DESCRIPTION
1. Dynamic mode indicates LACP is enabled
2. Both member ports are selected


<SwitchA> display link-aggregation summary
Aggregation Interface Type:
BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
Aggregation Mode: S -- Static, D -- Dynamic
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Actor System ID: 0x8000, 3ce5-a6cf-1219
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
--------------------------------------------------------------------------
BAGG3 D 0x8000, 3ce5-a680-9cb6 2 0 Shar
2.
Bridge-Aggregation
interface
LAG-01
1.

Technical Configuration Guide Link Aggregation 15

Verify that the Bridge-Aggregation interface is an access port in the proper VLAN.

Figure 10 Verification with the display interface bridge-aggregation command
ITEM DESCRIPTION
1. Aggregate bandwidth
2. Primary VLAN ID
3. Port link-type is an access port

Additional Information
Configuration steps
This section provides additional information on each of the steps to configure Link Aggregation.
Create a logical Bridge-Aggregation interface
Link-Aggregation consists of bundling several physical interfaces together. The bundle of interfaces is
represented logically by a Bridge-Aggregation interface.
The first step to configure Link Aggregation is to create a Bridge-Aggregation interface.
Since a switch may have more than one aggregate link, each logical Bridge-Aggregation interface is assigned an
interface number that uniquely represents a specific bundle of physical interfaces on the switch. This Bridge-
Aggregation interface number is also referred to as a bridge-aggregation group number.
The Bridge-Aggregation group number is locally significant to a switch. This number does not need to match the
Bridge-Aggregation group number on the connecting switch.
All interfaces that are to be part of the same bundle are assigned to the same Bridge Aggregation group.
This new interface can be configured similarly to a physical interface. Changes made to the logical interface will
be propagated to the physical interfaces, ensuring a consistent configuration of the member ports.
<SwitchA> display interface Bridge-Aggregation 3
Bridge-Aggregation3 current state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 000f-e207-f2e0
Description: Bridge-Aggregation3 Interface
2Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
PVID: 100
Port link-type: access
Tagged VLAN ID : none
Untagged VLAN ID : 100
1.
2.
3.
LACP-06

Technical Configuration Guide Link Aggregation 16

Enable the Link Aggregation Control Protocol (optional)
The Link Aggregation Control Protocol, LACP, allows a standardized mechanism by which switches can transition
to and from link aggregation status in an orderly fashion. LACP is a standard protocol defined by 802.1ax
(formerly 802.3ad) and is interoperable with other vendors who support this standard.
The second step to configure Link Aggregation is to enable the LACP protocol if desired.
The use of LACP is optional. However, if one end of the aggregate link enables LACP, the other end must enable
LACP too. LACP is not required for the formation of an aggregate link, but the use of LACP can make the
conversion less problematic. For example, by using LACP, a switch can refrain from converting to an aggregate
link if the partner switch is not properly configured.
LACP can also simplify troubleshooting cabling problems. Should there be a mistake in cabling, the administrator
can inspect the status of the LACP link and observe the bridge ID of the neighbor to verify proper connectivity; this
can be very useful when remotely administering equipment. Without LACP the switch does not detect the error,
and despite having a correct configuration, Link Aggregation does not function because the cables are incorrectly
connected. Identifying and troubleshooting these types of issues is easier with LACP.
If you choose to use LACP, it must be configured prior to assigning physical interfaces to the Bridge Aggregation
Group. Once the physical interfaces are assigned, LACP cannot be enabled or disabled on the Bridge-Aggregation
interface until the physical interfaces are removed from the logical Bridge-Aggregation interface.
In Comware, LACP functions in the active role.
Assign physical interfaces to the Bridge Aggregation Group
The third step to configure Link Aggregation is to assign the physical interfaces that are to participate in a specific
link aggregation to the logical Bridge Aggregation Group.
All interfaces that are to be part of the same bundle are assigned to the same Bridge Aggregation group.
Configure the link-mode and VLANs on the Bridge-Aggregation interface
The final step to configure link aggregation is to configure the desired characteristics of the link on the logical
Bridge-Aggregation interface.
The logical Bridge-Aggregation interface represents the aggregate link. Commands to change the configuration
of the logical interface should be entered in the Bridge-Aggregation interface instead of the physical components.
If the aggregate link is to function as an 802.1q trunk port, configure the necessary link-mode trunk command on
the Bridge-Aggregate interface.
If the aggregate link is to function as an access port, configure the necessary link-mode and VLAN commands on
the Bridge-Aggregate interface.
There is no need to configure trunk, access, or VLAN commands on the physical interfaces. These configurations
will be placed on the physical link interfaces automatically.
Avoid configuring trunk, access, or VLAN commands on the individual component interfaces. Doing so risks
creating an inconsistency in the link-mode status among the participating interfaces causing the aggregate link to
exclude certain physical interfaces from the aggregate. Only interfaces with a configuration consistent with the
parent Bridge-Aggregation interface are considered for inclusion in the aggregate link.
The configurations of the physical interfaces must remain consistent among all members of the aggregate link as
well as remain consistent with the parent Bridge-Aggregate interface.
Troubleshoot
If the configuration cannot be verified, follow these steps to troubleshoot:

Technical Configuration Guide Link Aggregation 17

Common Misconfigurations
The following are examples of several common misconfigurations of Link-Aggregation. The invalid configuration
is shown followed by the necessary steps to correct the problem.
Problem: No Member Ports Selected
In this example, no member ports are selected as part of the Link-Aggregation interface because the link-type of
the member ports does not match the link-type of the Bridge-Aggregation interface.
The link-type of the Bridge-Aggregation interface must match the link-type of the member ports.

Figure 11 Misconfiguration no member ports selected
ITEM DESCRIPTION
1. Bridge-aggregation interface is an access port
2. Member ports are 802.1q trunk ports
3. No member ports are selected
To correct this problem, configure the link-type of the Bridge-Aggregation interface.
If the Link-Aggregation is to be an 802.1q trunk port, configure the Bridge-Aggregation interface as a trunk port.
If the Link-Aggregation is to be an access port, reconfigure the Bridge-Aggregation interface as an access port.
<SwitchA>
interface Bridge-Aggregation2
link-aggregation mode dynamic
interface Ten-GigabitEthernet4/0/1
port link-type trunk
port trunk permit vlan all
port link-aggregation group 2
interface Ten-GigabitEthernet4/0/2
port link-type trunk
port trunk permit vlan all
port link-aggregation group 2
<SwitchA> display link-aggregation summary
Actor System ID: 0x8000, 3ce5-a680-9cb6
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
-----------------------------------------------------------------------
BAGG2 D 0x8000, 0000-0000-0000 0 2 Shar
1.
2.
3.
LACP-07

Technical Configuration Guide Link Aggregation 18

Problem: LACP mismatch
In this example, LACP is configured on one switch but not the other switch. If LACP is to be used, it must be
configured on both switches.

Figure 12 Misconfiguration LACP mismatch
ITEM DESCRIPTION
1. LACP is not enabled on Switch-A
2. LACP is enabled on Switch-B
To correct this problem, either configure LACP on Switch-A, or remove the LACP configuration from Switch-B.

<Switch-A>
interface Bridge-Aggregation2
port link-type trunk
port trunk permit vlan all
<Switch-B>
interface Bridge-Aggregation2
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
<Switch-A> display link-aggregation summary
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
-----------------------------------------------------------------------
BAGG2 S none 2 0 Shar
<Switch-B> display link-aggregation summary
AGG AGG Partner ID Select Unselect Share
Interface Mode Ports Ports Type
-----------------------------------------------------------------------
BAGG2 D 0x8000, 0000-0000-0000 1 1 Shar
1.
2.
LACP-08

Technical Configuration Guide Link Aggregation 19

For more information
To read more about HP Networking Products, go to http://www.hp.com/go/networking




















Get connected
hp.com/go/getconnected
Current HP driver, support, and security alerts
delivered directly to your desktop

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is
subject to change without notice. The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
Trademark acknowledgments, if needed.
Version 1, Created June 2012, Updated August 2012