HP GbE2c HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Gu - Page 37

Link Aggregation Control Protocol - lacp

Get HP GbE2c - Blc Layer 2/3 Fiber SFP Option PDF manuals and user guides
UPC - 808736802215
View all HP GbE2c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

Link Aggregation Control Protocol Link Aggregation Control Protocol (LACP) is an IEEE 802.3ad standard for grouping several physical ports into one logical port (known as a dynamic trunk group or Link Aggregation group) with any device that supports the standard. Refer to the IEEE 802.3ad-2002 for a full description of the standard. The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link Aggregation Control Protocol (LACP). Link aggregation is a method of grouping physical link segments of the same media type and speed in full duplex, and treating them as if they were part of a single, logical link segment. If a link in a LACP trunk group fails, traffic is reassigned dynamically to the remaining link(s) of the dynamic trunk group. NOTE: Currently, LACP implementation does not support the Churn machine, an option used to detect if the port is operable within a bounded time period between the actor and the partner. Only the Market Responder is implemented, and there is no marker protocol generator. A port's Link Aggregation Identifier (LAG ID) determines how the port can be aggregated. The Link Aggregation ID (LAG ID) is constructed mainly from the system ID and the port's admin key, as follows: IMPORTANT: System ID-The system ID is an integer value based on the switch's MAC address and the system priority assigned in the CLI. • Admin key-A port's Admin key is an integer value (1-65535) that you can configure in the CLI. Each GbE2c port that participates in the same LACP trunk group must have the same admin key value. The Admin key is local significant, which means the partner switch does not need to use the same Admin key value. For example, consider two switches, an Actor (the GbE2c) and a Partner (another switch), as shown in the following table: Table 8 Actor vs. partner LACP configuration Actor Switch Partner Switch 1 Partner Switch 2 Port 20 (admin key = 100) Port 21 (admin key = 100) Port 22 (admin key = 200) Port 23 (admin key = 200) Port 1 (admin key = 50) Port 2 (admin key = 50) Port 3 (admin key = 60) Port 4 (admin key = 60) In the configuration shown in the table above, Actor switch ports 20 and 21 aggregate to form an LACP trunk group with Partner switch ports 1 and 2. At the same time, Actor switch ports 22 and 23 form a different LACP trunk group with a different partner. LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the controlled addition and removal of physical links for the link aggregation. Each port in the GbE2c can have one of the following LACP modes. • off (default)-The user can configure this port in to a regular static trunk group. • active-The port is capable of forming an LACP trunk. This port sends LACPDU packets to partner system ports. • passive-The port is capable of forming an LACP trunk. This port only responds to the LACPDU packets sent from an LACP active port. Each active LACP port transmits LACP data units (LACPDUs), while each passive LACP port listens for LACPDUs. During LACP negotiation, the admin key is exchanged. The LACP trunk group is enabled as long as the information matches at both ends of the link. If the admin key value changes for a port at either end of the link, that port's association with the LACP trunk group is lost. When the system is initialized, all ports by default are in LACP off mode and are assigned unique admin keys. To make a group of ports aggregatable, you assign them all the same admin key. You must set the port's LACP mode to active to activate LACP negotiation. You can set other port's LACP mode to passive, to reduce the amount of LACPDU traffic at the initial trunk-forming stage. Use the /info/l2/trunk command or the /info/l2/lacp/dump command to check whether the ports are trunked. NOTE: If you configure LACP on ports with 802.1x network access control, make sure the ports on both sides of the connection are properly configured for both LACP and 802.1x. Ports and trunking 37

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
Ports and trunking 37
Link Aggregation Control Protocol
Link Aggregation Control Protocol (LACP) is an IEEE 802.3ad standard for grouping several physical ports into one
logical port (known as a dynamic trunk group or Link Aggregation group) with any device that supports the standard.
Refer to the IEEE 802.3ad-2002 for a full description of the standard.
The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link Aggregation Control
Protocol (LACP). Link aggregation is a method of grouping physical link segments of the same media type and speed
in full duplex, and treating them as if they were part of a single, logical link segment. If a link in a LACP trunk group
fails, traffic is reassigned dynamically to the remaining link(s) of the dynamic trunk group.
NOTE:
Currently, LACP implementation does not support the Churn machine, an option used to detect if the
port is operable within a bounded time period between the actor and the partner. Only the Market Responder
is implemented, and there is no marker protocol generator.
A port’s Link Aggregation Identifier (LAG ID) determines how the port can be aggregated. The Link Aggregation ID
(LAG ID) is constructed mainly from the
system ID
and the port’s
admin key
, as follows:
IMPORTANT:
System ID
—The system ID is an integer value based on the switch’s MAC address and the system
priority assigned in the CLI.
•
Admin key
—A port’s Admin key is an integer value (1-65535) that you can configure in the CLI. Each GbE2c
port that participates in the same LACP trunk group must have the same
admin key
value. The Admin key is
local significant
, which means the partner switch does not need to use the same Admin key value.
For example, consider two switches, an Actor (the GbE2c) and a Partner (another switch), as shown in the following
table:
Table 8
Actor vs. partner LACP configuration
Actor Switch
Partner Switch 1
Partner Switch 2
Port 20 (admin key = 100)
Port 1 (admin key = 50)
Port 21 (admin key = 100)
Port 2 (admin key = 50)
Port 22 (admin key = 200)
Port 3 (admin key = 60)
Port 23 (admin key = 200)
Port 4 (admin key = 60)
In the configuration shown in the table above, Actor switch ports 20 and 21 aggregate to form an LACP trunk group
with Partner switch ports 1 and 2. At the same time, Actor switch ports 22 and 23 form a different LACP trunk group
with a different partner.
LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the
controlled addition and removal of physical links for the link aggregation.
Each port in the GbE2c can have one of the following LACP modes.
•
off (default)—The user can configure this port in to a regular static trunk group.
•
active—The port is capable of forming an LACP trunk. This port sends LACPDU packets to partner system ports.
•
passive—The port is capable of forming an LACP trunk. This port only responds to the LACPDU packets sent
from an LACP
active
port.
Each active LACP port transmits LACP data units (LACPDUs), while each passive LACP port listens for LACPDUs.
During LACP negotiation, the admin key is exchanged. The LACP trunk group is enabled as long as the information
matches at both ends of the link. If the admin key value changes for a port at either end of the link, that port’s
association with the LACP trunk group is lost.
When the system is initialized, all ports by default are in LACP
off
mode and are assigned unique
admin keys
. To
make a group of ports aggregatable, you assign them all the same
admin key
. You must set the port’s LACP mode to
active
to activate LACP negotiation. You can set other port’s LACP mode to passive, to reduce the amount of LACPDU
traffic at the initial trunk-forming stage.
Use the
/info/l2/trunk
command or the
/info/l2/lacp/dump
command to check whether the ports are
trunked.
NOTE:
If you configure LACP on ports with 802.1x network access control, make sure the ports on both sides
of the connection are properly configured for both LACP and 802.1x.