H3C S6300 Switch Series
Ethernet Link Aggregation Configuration Examples

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Contents

Introduction· 1

Prerequisites· 1

Example: Configuring Layer 2 link aggregation· 1

Network requirements· 1

Requirements analysis· 1

Software version used· 2

Configuration restrictions and guidelines· 2

Configuration procedures· 2

Verifying the configuration· 3

Configuration files· 4

Example: Configuring Layer 2 link aggregation load sharing· 5

Network requirements· 5

Requirements analysis· 6

Software version used· 6

Configuration restrictions and guidelines· 6

Configuration procedures· 7

Verifying the configuration· 8

Configuration files· 9

Example: Configuring Layer 2 link aggregation in an IRF fabric· 9

Network requirements· 9

Software version used· 10

Configuration restrictions and guidelines· 10

Configuration procedures· 11

Verifying the configuration· 13

Configuration files· 14

Related documentation· 15

 

Introduction

This document provides Ethernet link aggregation configuration examples.

Prerequisites

The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of Ethernet link aggregation.

Example: Configuring Layer 2 link aggregation

Network requirements

As shown in Figure 1, both Device A and Device B forward traffic from VLAN 10 and VLAN 20.

Configure link aggregation on Device A and Device B to meet the following requirements:

·     VLAN 10 on Device A can communicate with VLAN 10 on Device B.

·     VLAN 20 on Device A can communicate with VLAN 20 on Device B.

Figure 1 Network diagram

 

Requirements analysis

To enable traffic from VLAN 10 and VLAN 20 to pass through Layer 2 aggregate interface Bridge-aggregation 1, perform the following tasks:

·     Configure Layer 2 aggregate interface Bridge-aggregation 1 as a trunk port.

·     Assign the aggregate interface to VLAN 10 and VLAN 20.

Software version used

This configuration example was created and verified on S6300-CMW710-R2310.

Configuration restrictions and guidelines

When you configure Layer 2 link aggregation, follow these restrictions and guidelines:

·     When you assign a port to an aggregation group, the recommended configuration procedure is as follows:

a.     Use the display this command in interface view to check the following attribute configurations of the port:

-     Port isolation.

-     QinQ.

-     VLAN.

-     VLAN mapping.

b.     If any of the above configurations exist, use the undo forms of the corresponding commands to remove these configurations. This enables the port to use the default attribute configurations.

c.     Assign the port to the aggregation group.

·     In a static aggregation group, the Selected state of a port is not affected by whether the peer port is added to an aggregation group and is Selected. As a result, the Selected state of a port might be different from the Selected state of the peer port. When both ends support static aggregation and dynamic aggregation, H3C recommends using dynamic aggregation.

·     You cannot assign a port to a Layer 2 aggregation group when MAC authentication, port security mode, or 802.1X is configured or enabled on the port.

Configuration procedures

1.     Configure Device A:

# Create VLAN 10, and assign port Ten-GigabitEthernet 1/0/4 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port ten-gigabitethernet 1/0/4

[DeviceA-vlan10] quit

# Create VLAN 20, and assign port Ten-GigabitEthernet 1/0/5 to VLAN 20.

[DeviceA] vlan 20

[DeviceA-vlan20] port ten-gigabitethernet 1/0/5

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-aggregation 1. Use one of the following methods as needed.

¡     Use the static aggregation mode to create Layer 2 aggregate interface Bridge-aggregation 1.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] quit

¡     Use the dynamic aggregation mode to create Layer 2 aggregate interface Bridge-aggregation 1.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic

[DeviceA-Bridge-Aggregation1] quit

# Assign ports Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/3 to aggregation group 1.

[DeviceA] interface ten-gigabitethernet 1/0/1

[DeviceA-Ten-GigabitEthernet1/0/1] port link-aggregation group 1

[DeviceA-Ten-GigabitEthernet1/0/1] quit

[DeviceA] interface ten-gigabitethernet 1/0/2

[DeviceA-Ten-GigabitEthernet1/0/2] port link-aggregation group 1

[DeviceA-Ten-GigabitEthernet1/0/2] quit

[DeviceA] interface ten-gigabitethernet 1/0/3

[DeviceA-Ten-GigabitEthernet1/0/3] port link-aggregation group 1

[DeviceA-Ten-GigabitEthernet1/0/3] quit

# Configure Layer 2 aggregate interface Bridge-aggregation 1 as a trunk port.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] port link-type trunk

Configuring Ten-GigabitEthernet1/0/1 done.

 Configuring Ten-GigabitEthernet1/0/2 done.

 Configuring Ten-GigabitEthernet1/0/3 done.

# Assign the aggregate interface to VLANs 10 and 20.

[DeviceA-Bridge-Aggregation1] port trunk permit vlan 10 20

 Configuring Ten-GigabitEthernet1/0/1 done.

 Configuring Ten-GigabitEthernet1/0/2 done.

 Configuring Ten-GigabitEthernet1/0/3 done.

[DeviceA-Bridge-Aggregation1] quit

2.     Configure Device B in the same way Device A is configured. (Details not shown.)

Verifying the configuration

# Display detailed information about the link aggregation groups on Device A.

·     Link aggregation configuration information when the static aggregation mode is used:

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

        D -- Synchronization, E -- Collecting, F -- Distributing,

        G -- Defaulted, H -- Expired

 

Aggregation Interface: Bridge-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

  Port             Status  Priority  Oper-Key

--------------------------------------------------------------------------------

  XGE1/0/1          S       32768     1

  XGE1/0/2          S       32768     1

  XGE1/0/3          S       32768     1

The output shows that all member ports in the local aggregation group are in the Selected state. The Selected states of the local member ports are not affected by the Selected states of the peer member ports.

·     Link aggregation configuration information when the dynamic aggregation mode is used:

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

        D -- Synchronization, E -- Collecting, F -- Distributing,

        G -- Defaulted, H -- Expired

 

Aggregation Interface: Bridge-Aggregation11

Aggregation Mode: Dynamic

Loadsharing Type: Shar

System ID: 0x8000, 000f-e234-5678

Local:

  Port             Status  Priority Oper-Key  Flag

--------------------------------------------------------------------------------

  XGE1/0/1          S       32768    1         {ACDEF}

  XGE1/0/2          S       32768    1         {ACDEF}

  XGE1/0/3          S       32768    1         {ACDEF}

Remote:

  Actor            Partner Priority Oper-Key  SystemID               Flag

--------------------------------------------------------------------------------

  XGE1/0/1          14      32768    1         0x8000, 0000-fc00-7506 {ACDEF}

  XGE1/0/2          15      32768    1         0x8000, 0000-fc00-7506 {ACDEF}

  XGE1/0/3          16      32768    1         0x8000, 0000-fc00-7506 {ACDEF}

The output shows that the local member ports and the corresponding peer member ports are all Selected. In the dynamic link aggregation mode, each local member port and its peer member port have the same Selected state through exchanging LACPDUs. The user data traffic can be forwarded correctly.

Configuration files

·     Device A:

#

vlan 10

#

interface Ten-GigabitEthernet1/0/4

 port access vlan 10

#

vlan 20

#

interface Ten-GigabitEthernet1/0/5

 port access vlan 20

¡     In the static aggregation mode:

#

interface Bridge-Aggregation1

port link-type trunk

port trunk permit vlan 10 20

¡     In the dynamic aggregation mode:

#

interface Bridge-Aggregation1

port link-type trunk

port trunk permit vlan 10 20

link-aggregation mode dynamic

#

interface Ten-GigabitEthernet1/0/1

port link-type trunk

port trunk permit vlan 10 20

port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/2

port link-type trunk

port trunk permit vlan 10 20

port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/3

port link-type trunk

port trunk permit vlan 10 20

port link-aggregation group 1

#

·     Device B:

The configuration file on Device B is the same as the configuration file on Device A.

Example: Configuring Layer 2 link aggregation load sharing

Network requirements

As shown in Figure 2, both Device A and Device B forward traffic from VLAN 10 and VLAN 20.

Configure link aggregation on Device A and Device B to meet the following requirements:

·     VLAN 10 on Device A can communicate with VLAN 10 on Device B. VLAN 20 on Device A can communicate with VLAN 20 on Device B.

·     The packets from VLAN 10 are load shared across the Selected ports of link aggregation group 1 by source MAC addresses. The packets from VLAN 20 are load shared across the Selected ports of link aggregation group 2 by destination MAC addresses.

Figure 2 Network diagram

 

Requirements analysis

To meet the network requirements, you must perform the following tasks:

·     To configure different load sharing modes for packets in different link aggregation groups, configure link aggregation load sharing modes in Layer 2 aggregate interface view.

·     To enable packets from VLAN 10 to pass through aggregate interface Bridge-aggregation 1, assign the aggregate interface to VLAN 10. To enable packets from VLAN 20 to pass through aggregate interface Bridge-aggregation 2, assign the aggregate interface to VLAN 20.

Software version used

This configuration example was created and verified on S6300-CMW710-R2310.

Configuration restrictions and guidelines

When you configure Layer 2 load sharing, follow these restrictions and guidelines:

·     When you assign a port to an aggregation group, the recommended configuration procedure is as follows:

a.     Use the display this command in interface view to check the following attribute configurations of the port:

-     Port isolation.

-     QinQ.

-     VLAN.

-     VLAN mapping.

b.     If any of the above configurations exist, use the undo forms of the corresponding commands to remove these configurations. This enables the port to use the default attribute configurations.

c.     Assign the port to the aggregation group.

·     You cannot assign a port to a Layer 2 aggregation group when MAC authentication, port security mode, or 802.1X is configured or enabled on the port.

Configuration procedures

1.     Configure Device A:

# Create VLAN 10, and assign port Ten-GigabitEthernet 1/0/5 to VLAN 10.

<DeviceA> system-view

[DeviceA] vlan 10

[DeviceA-vlan10] port ten-gigabitethernet 1/0/5

[DeviceA-vlan10] quit

# Create VLAN 20, and assign port Ten-GigabitEthernet 1/0/6 to VLAN 20.

[DeviceA] vlan 20

[DeviceA-vlan20] port ten-gigabitethernet 1/0/6

[DeviceA-vlan20] quit

# Create Layer 2 aggregate interface Bridge-aggregation 1.

[DeviceA] interface bridge-aggregation 1

# Configure Layer 2 aggregation group 1 to load share packets based on source MAC addresses.

[DeviceA-Bridge-Aggregation1] link-aggregation load-sharing mode source-mac

[DeviceA-Bridge-Aggregation1] quit

# Assign ports Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 to aggregation group 1.

[DeviceA] interface ten-gigabitethernet 1/0/1

[DeviceA-Ten-GigabitEthernet1/0/1] port link-aggregation group 1

[DeviceA-Ten-GigabitEthernet1/0/1] quit

[DeviceA] interface ten-gigabitethernet 1/0/2

[DeviceA-Ten-GigabitEthernet1/0/2] port link-aggregation group 1

[DeviceA-Ten-GigabitEthernet1/0/2] quit

# Assign Layer 2 aggregate interface Bridge-aggregation 1 to VLAN 10.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] port access vlan 10

Configuring Ten-GigabitEthernet1/0/1 done.

Configuring Ten-GigabitEthernet1/0/2 done.

[DeviceA-Bridge-Aggregation1] quit

# Create Layer 2 aggregate interface Bridge-aggregation 2.

[DeviceA] interface bridge-aggregation 2

# Configure Layer 2 aggregation group 2 to load share packets based on destination MAC addresses.

[DeviceA-Bridge-Aggregation2] link-aggregation load-sharing mode destination-mac

[DeviceA-Bridge-Aggregation2] quit

# Assign ports Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/4 to aggregation group 2.

[DeviceA] interface ten-gigabitethernet 1/0/3

[DeviceA-Ten-GigabitEthernet1/0/3] port link-aggregation group 2

[DeviceA-Ten-GigabitEthernet1/0/3] quit

[DeviceA] interface ten-gigabitethernet 1/0/4

[DeviceA-Ten-GigabitEthernet1/0/4] port link-aggregation group 2

[DeviceA-Ten-GigabitEthernet1/0/4] quit

# Assign Layer 2 aggregate interface Bridge-aggregation 2 to VLAN 20.

[DeviceA] interface bridge-aggregation 2

[DeviceA-Bridge-Aggregation2] port access vlan 20

Configuring Ten-GigabitEthernet1/0/3 done.

Configuring Ten-GigabitEthernet1/0/4 done.

[DeviceA-Bridge-Aggregation2] quit

2.     Configure Device B in the same way Device A is configured. (Details not shown.)

Verifying the configuration

# Display the information about Selected ports in link aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected , I -- Individual

Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

        D -- Synchronization, E -- Collecting, F -- Distributing,

        G -- Defaulted, H -- Expired

 

Aggregation Interface: Bridge-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

  Port             Status  Priority  Oper-Key

--------------------------------------------------------------------------------

  XGE1/0/1         S       32768     1

  XGE1/0/2         S       32768     1

 

Aggregation Interface: Bridge-Aggregation2

Aggregation Mode: Static

Loadsharing Type: Shar

  Port             Status  Priority  Oper-Key

--------------------------------------------------------------------------------

  XGE1/0/3         S       32768     2

  XGE1/0/4         S       32768     2

The output shows the following information:

·     Link aggregation groups 1 and 2 are both Layer 2 static aggregation groups.

·     Each aggregation group has two Selected ports for forwarding traffic.

# Display the link aggregation load sharing mode of Bridge-aggregation 1.

[DeviceA]display link-aggregation load-sharing mode interface Bridge-Aggregation 1

Bridge-Aggregation1 Load-Sharing Mode:

source-mac address

The output shows that link aggregation group 1 load shares packets based on source MAC addresses.

# Display the link aggregation load sharing mode of Bridge-aggregation 2.

[DeviceA]display link-aggregation load-sharing mode interface Bridge-Aggregation 2

Bridge-Aggregation2 Load-Sharing Mode:

destination-mac address

The output shows that link aggregation group 2 load shares packets based on destination MAC addresses.

Configuration files

·     Device A:

#

vlan 10

#

interface Ten-GigabitEthernet1/0/5

port access vlan 10

#

vlan 20

#

interface Ten-GigabitEthernet1/0/6

port access vlan 10

#

interface Bridge-Aggregation1

port access vlan 10

link-aggregation load-sharing mode source-mac

#

interface Ten-GigabitEthernet1/0/1

port access vlan 10

port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/2

port access vlan 10

port link-aggregation group 1

#

interface Bridge-Aggregation2

port access vlan 20

link-aggregation load-sharing mode destination-mac

#

interface Ten-GigabitEthernet1/0/3

port access vlan 20

port link-aggregation group 2

#

interface Ten-GigabitEthernet1/0/4

port access vlan 20

port link-aggregation group 2

·     Device B:

The configuration file on Device B is the same as the configuration file on Device A.

Example: Configuring Layer 2 link aggregation in an IRF fabric

Network requirements

On the network as shown in Figure 3, perform the following tasks:

·     Set up a two-chassis IRF fabric at the access layer and a two-chassis IRF fabric at the distribution layer of the enterprise network.

·     Configure link aggregation to improve the reliability of the links between the access-layer and distribution-layer IRF fabrics and implement load sharing.

·     Run LACP MAD on the two IRF fabrics to detect IRF split.

Figure 3 Network diagram

 

Software version used

This configuration example was created and verified on S6300-CMW710-R2310.

Configuration restrictions and guidelines

When you configure Layer 2 link aggregation in an IRF fabric, follow these restrictions and guidelines:

·     IRF physical ports must be set to the bridge mode.

·     When you bind physical ports to an IRF port, you must set all the physical ports to operate in either normal or enhanced mode.

·     The physical ports of two connected IRF ports must operate in the same mode: normal or enhanced. For more information about the binding mode of the IRF physical ports, see IRF Configuration Guide.

·     H3C S6300 switches must use a group of SFP+ ports as IRF physical ports. Before you bind an SFP+ port to an IRF port, you must shut down all the SFP+ ports in the same group. This example uses a group of Ten-GigabitEthernet interfaces on Device A, B, C, and D. Every four ports are organized into a group by their number. To simplify the configuration, this example bulk shuts down and brings up the IRF physical ports. For more information about bulk configuring interfaces, see H3C S6300 Switch Series Layer 2—LAN Switching Configuration Guide. For more information about IRF, see H3C S6300 Switch Series IRF Configuration Guide.

·     When you assign a port to an aggregation group, the recommended configuration procedure is as follows:

a.     Use the display this command in interface view to check the following attribute configurations of the port:

-     Port isolation.

-     QinQ.

-     VLAN.

-     VLAN mapping.

b.     If any of the above configurations exist, use the undo forms of the corresponding commands to remove these configurations. This enables the port to use the default attribute configurations.

c.     Assign the port to the aggregation group.

·     In a static aggregation group, the Selected state of a port is not affected by whether the peer port is added to an aggregation group and is Selected. As a result, the Selected state of a port might be different from the Selected state of the peer port. When both ends support static aggregation and dynamic aggregation, H3C recommends using dynamic aggregation.

·     You cannot assign a port to a Layer 2 aggregation group when MAC authentication, port security mode, or 802.1X is configured or enabled on the port.

Configuration procedures

1.     Configure IRF on Device A:

# Shut down ports Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/4.

<DeviceA> system-view

[DeviceA] interface range ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[DeviceA-if-range] shutdown

[DeviceA-if-range] quit

# Bind Ten-GigabitEthernet 1/0/1 through Ten-GigabitEthernet 1/0/4 to IRF port 1/1.

[DeviceA] irf-port 1/1

[DeviceA-irf-port1/1] port group interface ten-gigabitethernet 1/0/1

[DeviceA-irf-port1/1] port group interface ten-gigabitethernet 1/0/2

[DeviceA-irf-port1/1] port group interface ten-gigabitethernet 1/0/3

[DeviceA-irf-port1/1] port group interface ten-gigabitethernet 1/0/4

[DeviceA-irf-port1/1] quit

# Bring up Ten-GigabitEthernet1/0/1 through Ten-GigabitEthernet1/0/4, and save the configuration.

[DeviceA] interface range ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[DeviceA-if-range] undo shutdown

[DeviceA-if-range] quit

[DeviceA] save

# Activate the IRF port configuration.

[DeviceA] irf-port-configuration active

Configure IRF on Device B:

# Change the member ID of Device B to 2, and reboot the device to validate the change.

<DeviceB> system-view

[DeviceB] irf member 1 renumber 2

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[DeviceB] quit

<DeviceB> reboot

# Shut down Ten-Gigabitethernet 2/0/1 through Ten-Gigabitethernet 2/0/4.

<DeviceB> system-view

[DeviceB] interface range ten-gigabitethernet 2/0/1 to ten-gigabitethernet 2/0/4

[DeviceB-if-range] shutdown

[DeviceB-if-range] quit

# Bind Ten-GigabitEthernet 2/0/1 through Ten-GigabitEthernet 2/0/4 to IRF port 2/2.

[DeviceB] irf-port 2/2

[DeviceB-irf-port2/2] port group interface ten-gigabitethernet 2/0/1

[DeviceB-irf-port2/2] port group interface ten-gigabitethernet 2/0/2

[DeviceB-irf-port2/2] port group interface ten-gigabitethernet 2/0/3

[DeviceB-irf-port2/2] port group interface ten-gigabitethernet 2/0/4

[DeviceB-irf-port2/2] quit

# Bring up Ten-GigabitEthernet 2/0/1 through Ten-GigabitEthernet 2/0/4, and save the configuration.

[DeviceB] interface range ten-gigabitethernet 2/0/1 to ten-gigabitethernet 2/0/4

[DeviceB-if-range] undo shutdown

[DeviceB-if-range] quit

[DeviceB] save

# Activate the IRF port configuration.

[DeviceB] irf-port-configuration active

Device A and Device B perform master election, and the one that has lost the election reboots to form an IRF fabric with the master. In this example, Device B reboots.

Configure a Layer 2 aggregation group on Device A:

# Create Layer 2 aggregate interface Bridge-Aggregation 1, and configure the link aggregation mode as dynamic.

[DeviceA] interface bridge-aggregation 1

[DeviceA-Bridge-Aggregation1] link-aggregation mode dynamic

# Configure Layer 2 aggregation group 1 to load share packets based on source IP addresses.

[DeviceA-Bridge-Aggregation1] link-aggregation load-sharing mode source-ip

[DeviceA-Bridge-Aggregation1] quit

# Assign ports Ten-GigabitEthernet 1/0/9, Ten-GigabitEthernet1/0/10, Ten-GigabitEthernet 2/0/9, and Ten-GigabitEthernet 2/0/10 to link aggregation group 1.

[DeviceA] interface range ten-gigabitethernet 1/0/9 to ten-gigabitethernet 1/0/10

ten-gigabitethernet 2/0/9 to ten-gigabitethernet 2/0/10

[DeviceA-if-range] port link-aggregation group 1

[DeviceA-if-range] quit

[DeviceA]

Configure LACP MAD on the IRF fabric:

# Set the domain ID of the IRF fabric to 1.

[DeviceA] irf domain 1

# Enable LACP MAD on Bridge-Aggregation 1.

[DeviceA] interface Bridge-Aggregation 1

[DeviceA-Bridge-Aggregation1] mad enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 1]:

The assigned domain ID is: 1

MAD LACP only enable on dynamic aggregation interface.

2.     Configure IRF on Device C in the same way IRF is configured on Device A. (Details not shown.)

3.     Configure IRF on Device D in the same way IRF is configured on Device B. (Details not shown.)

Device C and Device D perform master election, and the one that has lost the election reboots to form an IRF fabric with the master. In this example, Device C reboots.

4.     Configure a Layer 2 dynamic aggregation group Bridge-Aggregation 1 on Device C in the same way Bridge-Aggregation 1 is configured on Device A. (Details not shown.)

5.     Configure LACP MAD on the IRF fabric:

# Set the domain ID of the IRF fabric to 2.

<DeviceC> system-view

[DeviceC] irf domain 2

# Enable LACP MAD on Bridge-Aggregation 1.

[DeviceC] interface Bridge-Aggregation 1

[DeviceC-Bridge-Aggregation1] mad enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 2]:

The assigned domain ID is: 2

MAD LACP only enable on dynamic aggregation interface.

Verifying the configuration

# Display the information about the link aggregation groups on Device A.

[DeviceA] display link-aggregation verbose

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Flags:  A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

        D -- Synchronization, E -- Collecting, F -- Distributing,

        G -- Defaulted, H -- Expired

 

Aggregate Interface: Bridge-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

System ID: 0x8000, 00a0-fc00-5800

Local:

  Port             Status  Priority Oper-Key  Flag

--------------------------------------------------------------------------------

  XGE1/0/9         S       32768    1         {ACDEF}

  XGE1/0/10        S       32768    1         {ACDEF}

  XGE2/0/9         S       32768    1         {ACDEF}

  XGE2/0/10        s       32768    1         {ACDEF}

Remote:

  Actor            Partner Priority Oper-Key  SystemID               Flag

--------------------------------------------------------------------------------

  XGE1/0/9         139     32768    1         0x8000, 0cda-414a-859b {ACDEF}

  XGE1/0/10        205     32768    1         0x8000, 0cda-414a-859b {ACDEF}

  XGE2/0/9         204     32768    1         0x8000, 0cda-414a-859b {ACDEF}

  XGE2/0/10        138     32768    1         0x8000, 0cda-414a-859b {ACDEF}

The output shows that the local member ports and the corresponding peer member ports are all Selected. In the dynamic link aggregation mode, each local member port and its peer member port have the same Selected state through exchanging LACPDUs. The user data traffic can be forwarded correctly.

# Display the load sharing mode of Layer 2 aggregation group 1 on Device A.

[DeviceA] display link-aggregation load-sharing mode interface Bridge-Aggregation 1

Bridge-Aggregation1 Load-Sharing Mode:

source-ip address

The output shows that Layer 2 aggregation group 1 load shares packets based on source IP addresses.

# Shut down physical IRF port Ten-GigabitEthernet 2/0/1 on Device B.

A log message appears on Device A.

[DeviceA]%Jan  1 03:12:43:397 2011 Transit STM/3/STM_LINK_STATUS_DOWN: IRF port 2 is down.

%Jan  1 03:12:43:410 2011 Transit DEV/3/BOARD_REMOVED: Board is removed from Slo

t 1, type is MAIN_BOARD_TYPE_52QF.

%Jan  1 03:12:44:385 2011 Transit IFNET/3/PHY_UPDOWN: Ten-GigabitEthernet2/0/1

link status is down.

%Jan  1 03:12:44:386 2011 Transit IFNET/5/LINK_UPDOWN: Line protocol on the inte

rface Ten-GigabitEthernet2/0/1 is down.

The output shows that IRF split occurs on the distribution layer because Ten-GigabitEthernet 2/0/1 that is bound to IRF port 2/2 is physically down.

Configuration files

·     Device A:

#

 irf domain 1

 irf mac-address persistent timer

 irf auto-update enable

 irf link-delay 0

 irf member 1 priority 1

 irf member 2 priority 1

#

irf-port 1/1

 port group interface Ten-GigabitEthernet1/0/1

 port group interface Ten-GigabitEthernet1/0/2

 port group interface Ten-GigabitEthernet1/0/3

 port group interface Ten-GigabitEthernet1/0/4

#

irf-port 2/2

 port group interface Ten-GigabitEthernet2/0/1

 port group interface Ten-GigabitEthernet2/0/2

 port group interface Ten-GigabitEthernet2/0/3

 port group interface Ten-GigabitEthernet2/0/4

#

 

interface Bridge-Aggregation1

 link-aggregation mode dynamic

 link-aggregation load-sharing mode source-ip

#

interface Ten-GigabitEthernet1/0/9

 port link-aggregation group 1

#

interface Ten-GigabitEthernet1/0/10

 port link-aggregation group 1

#

interface Ten-GigabitEthernet2/0/9

 port link-aggregation group 1

#

interface Ten-GigabitEthernet2/0/10

port link-aggregation group 1

#

Device C:

The configuration file on Device C is similar as the configuration file on Device A.

Related documentation

·     H3C S6300 Switch Series Layer 2—LAN Switching Configuration Guide-Release 23xx

·     H3C S6300 Switch Series Layer 2—LAN Switching Command Reference-Release 23xx