Login
- Table of Contents
-
- H3C S9500 Operation Manual-Release2132[V2.03]-01 Access Volume
- 00-1Cover
- 01-Ethernet Interface Configuration
- 02-POS Interface Configuration
- 03-GVRP Configuration
- 04-Link Aggregation Configuration
- 05-Port Mirroring Configuration
- 06-RPR Configuration
- 07-Ethernet OAM Configuration
- 08-MSTP Configuration
- 09-VLAN Configuration
- 10-QinQ Configuration
- 11-BPDU Tunneling Configuration
- 12-Port Isolation Configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 04-Link Aggregation Configuration | 88.55 KB |
Chapter 1 Link Aggregation Overview
1.1.2 Consistency Considerations for Ports in an Aggregation Group
1.2 Approaches to Link Aggregation
1.2.2 Static LACP link aggregation
1.3 Load Sharing in a Link Aggregation Group
1.5 Link Aggregation Port Group
Chapter 2 Link Aggregation Configuration
2.1 Configuring Link Aggregation
2.1.1 Configuring a Manual Link Aggregation Group
2.1.2 Configuring a Static LACP Link Aggregation Group
2.1.3 Configuring an Name for a Link Aggregation Group
2.1.4 Configuring a Service Loop Group
2.1.5 Entering Aggregation Port Group View
2.2 Displaying and Maintaining Link Aggregation
2.3 Link Aggregation Configuration Example
Chapter 1 Link Aggregation Overview
When configuring link aggregation, go to these sections for information you are interesting in:
l Approaches to Link Aggregation
l Load Sharing in a Link Aggregation Group
1.1 Link Aggregation
Link aggregation aggregates multiple physical Ethernet ports into one logical link, also called a logical group, to increase reliability and bandwidth. Link aggregation allows you to increase bandwidth by distributing traffic on the member ports in an aggregation group. In addition, it provides reliable connectivity because these member ports can dynamically back up each other.
This section covers these topics:
l LACP
l Consistency Considerations for Ports in an Aggregation
& Note:
Note the following when employing link aggregation on an S9500 routing switch:
l Up to 31 link aggregation groups are supported on a switch.
l Up to 31 link aggregation groups are supported on XP4B boards. However, ports on boards of this type cannot be added to aggregation groups.
l Up to seven link aggregation groups are supported on XP4CA boards. However, ports on boards of this type cannot be added to aggregation groups.
l Up to 7 link aggregation groups are supported on boards with their models suffixed with “C”, “CA”, “CB”, and boards that are of 100 Mbps and of class B.
l For boards other than the above mentioned, up to 31 link aggregation groups are supported.
l To enable load being properly shared among ports in an aggregation group, make sure the number of the aggregation groups created on a board is not larger than that the board can accommodate.
1.1.1 LACP
The link aggregation control protocol (LACP) is defined in IEEE 802.3ad. LACP interacts with its peer by sending link aggregation control protocol data units (LACPDUs).
Adding a port to a static LACP aggregation group enables LACP on the port. Then, the port sends LACPDUs to notify the remote system of its system LACP priority, system MAC address, port LACP priority, port number, and operational key. Upon receipt of an LACPDU, the remote system compares the received information with the information received on other ports to determine the ports that can operate as selected ports. This allows the two systems to reach an agreement on the states of the related ports.
When aggregating ports, link aggregation control automatically assigns each port an operational key based on its rate, duplex mode, and other basic configurations. In a manual or static LACP aggregation, the selected ports share the same operational key.
1.1.2 Consistency Considerations for Ports in an Aggregation Group
To participate in load sharing, member ports in an aggregation group must use the same configurations with respect to STP, QoS, GVRP, QinQ, BPDU tunnel, VLAN, port attributes, MAC address learning, and so on, as shown in the following table. These configurations are referred to as aggregation-related configurations throughout this manual.
Table 1-1 Consistency considerations for ports in an aggregation
|
Category |
Considerations |
|
STP |
l State of port-level STP (enabled or disabled) l Attribute of the link (point-to-point or otherwise) connected to the port l Port path cost l STP priority l Maximum transmission rate l Loop protection l Root protection l Port type (whether the port is an edge port) |
|
QoS |
l Traffic policing l Traffic shaping l Congestion avoidance l Strict priority (SP) queuing l Port priority l Port priority trust mode l Policy setting on the port l Flow template |
|
GVRP |
l GVRP state on ports (enabled or disabled) l GVRP registration type l GARP timers |
|
QinQ |
l State of QinQ (enabled or disabled) l Added outer VLAN tag |
|
BPDU tunnel |
l BPDU tunnel state on ports (enabled or disabled) l BPDU tunnel state for STP on ports (enabled or disabled) |
|
VLAN |
l VLANs permitted to pass through the port l Default VLAN ID of the port l Link type of the port, which can be trunk, hybrid, or access l Protocol VLAN configuration l Whether packets of a VLAN carry the VLAN tag |
|
Port attribute |
l Port rate l Duplex mode l Up/down state of the link l Isolation group membership of the port |
|
MAC address learning |
l MAC address learning capability l Setting of maximum number of MAC addresses that can be learned on the port l Forwarding of frames with unknown destination MAC addresses after the upper limit of the MAC address table is reached |
1.2 Approaches to Link Aggregation
Two ways are available for implementing link aggregation, as described in Manual Link Aggregation, and Static LACP link aggregation.
1.2.1 Manual Link Aggregation
I. Overview
You can configure manual link aggregation by manually assigning ports to a LACP-disabled aggregation group. LACP is disabled on all ports in a manual aggregation group.
II. Port states in a manual aggregation group
In a manual aggregation group, ports are either selected or unselected. Selected ports can receive and transmit data frames whereas unselected ones cannot. Among all selected ports, the one with the lowest port number is the master port and others are member ports.
When setting the state of ports in a manual aggregation group, the system considers the following:
l Select a port from the ports in up state, if any, in the order of full duplex/high speed, full duplex/low speed, half duplex/high speed, and half duplex/low speed, with the full duplex/high speed being the most preferred. If two ports with the same duplex mode/speed pair are present, the one with the lower port number wins out. Then, place those ports in up state with the same speed/duplex pair, link state and basic configuration in selected state and all others in unselected state.
l When all ports in the group are down, select the port with the lowest port number as the master port and set all ports (including the master) in unselected state.
l Place the ports that cannot aggregate with the master in unselected state, for example, as the result of hardware restriction.
Manual aggregation limits the number of selected ports in an aggregation group. When the limit is exceeded, the system changes the state of selected ports with greater port numbers to unselected until the number of selected ports drops under the limit.
In addition, unless the master port should be selected, a port that joins the group after the limit is reached will not be placed in selected state even if it should be in normal cases. This is to prevent the ongoing service on selected ports from being interrupted. You need to avoid the situation however as the selected/unselected state of a port may become different after a reboot.
& Note:
Currently, the number of the selected ports in a manual aggregation group created on an S9500 routing switch can be up to eight.
III. Port Configuration Considerations in manual aggregation
As mentioned above, in a manual aggregation group, only ports with configurations consistent with those of the master port can become selected. These configurations include port rate, duplex mode, link state and other basic configurations described in Consistency Considerations for Ports in an Aggregation.
You need to maintain the basic configurations of these ports manually to ensure consistency. As one configuration change may involve multiple ports, this can become troublesome if you need to do that port by port. As a solution, you can configure the link aggregation port group corresponding to the link aggregation group. A link aggregation port group is created upon creation of a link aggregation group to include all the ports in the link aggregation group. The configuration made on a link aggregation port group applies to all the ports in the group. For more information about link aggregation port groups, refer to Link Aggregation Port Group.
& Note:
Because changing an aggregation-related configuration setting on a port may cause the selected-state change of other ports and thus affects services, you are recommended to do that with caution.
1.2.2 Static LACP link aggregation
I. Overview
You can configure static LACP aggregation by manually assigning ports to a LACP-enabled aggregation group. As soon as a port is assigned to a static LACP aggregation group, LACP is enabled on the port.
II. Port states in static aggregation
In a static aggregation group, ports can be selected or unselected, where both can receive and transmit LACPDUs but only selected ports can receive and transmit data frames. The selected port with the lowest port number is the master port and all others are member ports.
All member ports that cannot aggregate with the master are placed in unselected state. These ports include those using the basic configurations different from the master port or those located on a board different from the master port because of hardware restriction.
Member ports in up state can be selected if they have the configuration same as that of the master port. The number of selected ports however, is limited in a static aggregation group. When the limit is exceeded, the local and remote systems negotiate the state of their ports as follows:
1) Compare the actor and partner system IDs that each comprises a system LACP priority plus a system MAC address as follow:
l First compare the system LACP priorities. The system with lower system LACP priority wins out.
l If they are the same, compare the system MAC addresses. The system with the smaller ID has higher priority. (the lower the LACP priority, the smaller the MAC address, and the smaller the device ID)
2) Compare the port IDs that each comprises a port LACP priority and a port number on the system with higher ID as follows:
l Compare the port LACP priorities. The port with lower port LACP priority wins out.
l If two ports with the same port LACP priority are present, compare their port numbers. The state of the ports with lower IDs then change to selected and the state of the ports with higher IDs to unselected, so does the state of their corresponding remote ports. (the lower the LACP priority, the smaller the port number, and the smaller the port ID)
& Note:
Currently, the number of the selected ports in a static LACP aggregation group created on an S9500 routing switch can be up to eight.
III. Port configuration considerations in static aggregation
Like in a manual aggregation group, in a static LACP aggregation group, only ports with configurations consistent with those of the master port can become selected. These configurations include port rate, duplex mode, link state and other basic configurations described in section Consistency Considerations for Ports in an Aggregation.
You need to maintain the basic configurations of these ports manually to ensure consistency. As one configuration change may involve multiple ports, this can become troublesome if you need to do that port by port. As a solution, you may add the ports into an aggregation port group where you can make configuration for all member ports.
When the configuration of a port in a static aggregation group changes, the system does not remove the aggregation; instead, it re-sets the selected/unselected state of the member ports and re-selects a master port.
1.3 Load Sharing in a Link Aggregation Group
Link aggregation groups fall into load sharing aggregation groups and non-load sharing aggregation groups.
If a link aggregation group contains more than one selected port upon its creation, it performs load sharing automatically; if it contains only one selected port, it does not perform load sharing.
Caution:
Once a load sharing link aggregation group is created, its load sharing attribute will not change even after the number of selected ports in it decreases to one due to port removal for example.
1.4 Service Loop Group
As the S9500 series support service card intermixing, you need to create service loop ports to redirect services between service cards. Thus, when a service card receives traffic not intended for it, the card can redirect the traffic to the intended destination. To increase the redirect throughput, you may create service-loop groups.
You can create a service loop group by creating a manual aggregation group of service-loop ports first and then specifying which service can be redirected for the group. At present, you may specify to redirect four types of services, IPv6 (IPv6 unicast), IPv6mc (IPv6 multicast), tunnel, and MPLS.
When adding a port to a service loop group, make sure that the port supports the service specified for the service loop group and meets the following requirements:
l The port is configured only with the physical configuration (such as the speed and duplex mode), QoS, and ACL. Other conflicting configurations, such as STP, are not configured.
l The port belongs to VLAN 1.
For ports that are already in a service loop group, you can perform configurations that do not conflict with the service loop group for them, such as QoS.
& Note:
Currently, for the S9500 series, the boards with their models suffixed with DA, DB, or DC support IPv6 unicast/multicast and tunnel service loop groups; those with their models suffixed with C or CA support MPLS service loop groups.
1.5 Link Aggregation Port Group
As mentioned earlier, in a manual or static aggregation group, a port can be selected only when its configuration is the same as that of the master port in terms of duplex/speed pair, link state, and other basic configurations. Their configuration consistency requires administrative maintenance, which is troublesome after you change some configuration.
To simplify configuration, port-groups are provided allowing you to configure for all ports in individual groups at one time. Aggregation port groups are an example of port groups.
Upon creation or removal of a link aggregation group, an aggregation port-group which cannot be administratively created or removed is automatically created or removed. In addition, you can only assign/remove a member port to/from an aggregation port-group by assigning/removing it from the corresponding link aggregation group.
Chapter 2 Link Aggregation Configuration
When performing link aggregation configuration, go to these sections for information you are interesting in:
l Configuring Link Aggregation
l Displaying and Maintaining Link Aggregation
l Link Aggregation Configuration Example
2.1 Configuring Link Aggregation
When configuring a link aggregation group, go to these sections for information you are interested in:
l Configuring a Manual Link Aggregation Group
l Configuring a Static LACP Link Aggregation Group
l Configuring an Name for a Link Aggregation Group
l Configuring a Service Loop Group
l Entering Aggregation Port Group View
2.1.1 Configuring a Manual Link Aggregation Group
Follow these steps to configure a manual aggregation group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Create a manual aggregation group |
link-aggregation group agg-id mode manual |
Required |
|
Enter Ethernet interface view |
interface interface-type interface-number |
–– |
|
Assign the Ethernet port to the aggregation group |
port link-aggregation group agg-id |
Required |
Note that:
l You may create a manual aggregation group by changing the type of a static aggregation group that has existed. If the specified group contains ports, its group type changes to manual with LACP disabled on its member ports; if not, its group type directly changes to manual.
l An aggregation group cannot include ports with static MAC addresses, 802.1x-enabled ports, MAC address authentication-enabled ports, or POS interfaces. Besides, ports operating as upstream ports of isolation groups cannot be added to manual or static aggregation groups.
l You can remove all ports in a manual aggregation group by removing the group. If this group contains only one port, you can remove the port only by removing the group.
l To guarantee a successful aggregation, ensure that the ports at the two ends of each link to be aggregated are consistent in selected/unselected state.
2.1.2 Configuring a Static LACP Link Aggregation Group
Follow these steps to configure a static aggregation group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Configure the system LACP priority |
lacp system-priority system-priority |
Optional 32768 by default. |
|
Create a static LACP aggregation group |
link-aggregation group agg-id mode static |
Required |
|
Enter Ethernet interface view |
interface interface-type interface-number |
–– |
|
Configure the port LACP priority |
lacp port-priority port-priority-value |
Optional 32768 by default. |
|
Assign the Ethernet port to the aggregation group |
port link-aggregation group agg-id |
Required |
Note that:
l Adding a port to a static LACP aggregation group enables LACP on the port automatically.
l You can create a static aggregation group by changing the type of an existing empty manual link aggregation group.
l An aggregation group cannot include ports with static MAC addresses, 802.1x-enabled ports, MAC address authentication-enabled ports, or POS interfaces. Besides, ports operating as uplink ports of isolation groups cannot be added to manual or static aggregation groups.
l You can remove all members of a static LACP aggregation group by removing the group. Doing so disables LACP on the ports automatically.
l If a static LACP aggregation group contains only one port, you can remove the port only by removing the group.
& Note:
When making configuration, be aware that after a load-balancing aggregation group changes to a non-load balancing group due to resources exhaustion, either of the following may happen:
l Forwarding anomaly resulted from inconsistency of the two ends in the number of selected ports.
l Some protocols such as GVRP malfunction because the state of the remote port connected to the master port is unselected.
2.1.3 Configuring an Name for a Link Aggregation Group
Follow these steps to configure a name for an aggregation group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Configure a name for a link aggregation group |
link-aggregation group agg-id description agg-name |
Required Not configured by default. |
Caution:
When configuring a name for a link aggregation group, make sure the ID of the link aggregation group is available. You can obtain the ID of a link aggregation group using the display link-aggregation summary command or the display link-aggregation interface command.
2.1.4 Configuring a Service Loop Group
Follow these steps to configure a service loop group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Create a manual aggregation group |
link-aggregation group agg-id mode manual |
Required |
|
Specify the aggregation group as a service loop group |
link-aggregation group agg-id service-type { ipv6 | ipv6mc | mpls | tunnel } |
Required |
|
Enter Ethernet interface view |
interface interface-type interface-number |
–– |
|
Assign the Ethernet port to the service loop group |
port link-aggregation group agg-id |
Required |
& Note:
l You can define only one service loop group for each service loop group type.
l Only one service type can be specified for a service loop group.
l There can only be up to eight Ethernet ports valid for each service loop group type.
l An Ethernet port can be added to a service loop group only when STP is not enabled on it.
l You can change the type of an existing service loop group. The operation fails if it is currently referenced by a module or the service loop group contains ports whose attributes conflict with the intended service type.
l You can use the undo link-aggregation group command to remove a service loop group. The operation fails if it is currently referenced by a module.
l For a service loop group containing only one port, you can remove the port from the service loop group only by removing the service loop group.
2.1.5 Entering Aggregation Port Group View
In aggregation port group view, you can make configuration for all the member ports in a link aggregation group at one time.
Follow these steps to enter aggregation port group view:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
–– |
|
Enter aggregation port group view |
port-group aggregation agg-id |
–– |
Caution:
In aggregation port group view, you can configure aggregation related settings such as STP, VLAN, QoS, GVRP, QinQ, BPDU tunnel, MAC address learning, but cannot add or remove member ports.
2.2 Displaying and Maintaining Link Aggregation
|
To do… |
Use the command… |
Remarks |
|
Display the local system ID |
display lacp system-id |
Available in any view |
|
Display detailed information about link aggregation for the specified port or ports |
display link-aggregation interface interface-type interface-number [ to interface-type interface-number ] |
Available in any view |
|
Display information about the specified or all service loop groups |
display link-aggregation service-type [ agg-id ] |
Available in any view |
|
Display summaries for all link aggregation groups |
display link-aggregation summary |
Available in any view |
|
Display detailed information about specified or all link aggregation groups |
display link-aggregation verbose [ agg-id ] |
Available in any view |
|
Clear the statistics about LACP for specified or all ports |
reset lacp statistics [ interface interface-type interface-number [ to interface-type interface-number ] ] |
Available in user view |
2.3 Link Aggregation Configuration Example
I. Network requirements
Switch A aggregates ports Ethernet 1/1/1 through Ethernet 1/1/3 to form one link connected to Switch B and performs load sharing among these ports.
II. Network diagram
Figure 2-1 Network diagram for link aggregation
III. Configuration procedure
& Note:
l This example only describes how to configure link aggregation on Switch A. To achieve link aggregation, do the same on Switch B.
l Both manual aggregation and static LACP aggregation can be used for the purpose of this example.
1) In manual aggregation approach
# Create manual aggregation group 1.
<SwitchA> system-view
[SwitchA] link-aggregation group 1 mode manual
# Add ports Ethernet 1/1/1 through Ethernet 1/1/3 to the aggregation group.
[SwitchA] interface ethernet 1/1/1
[SwitchA-Ethernet1/1/1] port link-aggregation group 1
[SwitchA-Ethernet1/1/1] quit
[SwitchA] interface ethernet 1/1/2
[SwitchA-Ethernet1/1/2] port link-aggregation group 1
[SwitchA-Ethernet1/1/2] quit
[SwitchA] interface ethernet 1/1/3
[SwitchA-Ethernet1/1/3] port link-aggregation group 1
2) In static aggregation approach
# Create static aggregation group 1.
<SwitchA> system-view
[SwitchA] link-aggregation group 1 mode static
# Add ports Ethernet 1/1/1 through Ethernet 1/1/3 to the aggregation group.
[SwitchA] interface ethernet 1/1/1
[SwitchA-Ethernet1/1/1] port link-aggregation group 1
[SwitchA-Ethernet1/1/1] quit
[SwitchA] interface ethernet 1/1/2
[SwitchA-Ethernet1/1/2] port link-aggregation group 1
[SwitchA-Ethernet1/1/2] quit
[SwitchA] interface ethernet 1/1/3
[SwitchA-Ethernet1/1/3] port link-aggregation group 1
