Link Aggregation Link Aggregation Configuration

Link Aggregation Link Aggregation Configuration

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 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 Configuration Guide – Link Aggregation 4 Configure Configuration Example – Link-Aggregation of 802.1q trunk ports with LACP Network diagram Figure 1 Link aggregation with LACP on two Ten-Gigabit Ethernet links Configuration steps To configure Link Aggregation of 802.1q trunk ports with Link Aggregation Control Protocol, LACP, follow these steps: Create a logical Bridge-Aggregation interface. Enable Link Aggregation Control Protocol. Assign physical interfaces to the logical Bridge-Aggregation interface. Configure the Bridge-Aggregate interface as a trunk port. Permit desired VLANs on the Bridge-Aggregate interface. Step 1 – Create a logical Bridge-Aggregation interface Create a logical Bridge-Aggregation interface. Choose an interfacee 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. # Switch-A interface bridge-aggregation 3 # Switch-B interface bridge-aggregation 1 Step 2 – Enable the Link Aggregation Control Protocol Enable LACP on the Bridge-Aggregation interface of both switchess. LACP must be configured prior to assigning physical interfaces to the Bridge Grouup (Step 3). # Switch-A interface bridge-aggregation 3 link-aggregation mode dynamic Technical Configuration Guide – Link Aggregation 5 # Switch-B interface bridge-aggregation 1 link-aggregation mode dynamic 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. # Switch-A interface Ten-GigabitEthernet1/0/25 link-aggregation group-member 3 interface Ten-GigabitEthernet1/0/26 link-aggregation group-member 3 # Switch-B interface Ten-GigabitEthernet1/0/27 link-aggregation group-member 1 interface Ten-GigabitEthernet1/0/28 link-aggregation group-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

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    19 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us