H3C MSR Routers Configuration Examples-6W100

HomeSupportResource CenterConfigure & DeployConfiguration ExamplesH3C MSR Routers Configuration Examples-6W100
02-H3C MSR Routers Ethernet Link Aggregation Configuration Examples (Comware V7)

H3C MSR Routers Ethernet Link Aggregation Configuration Examples (Comware V7)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Copyright © 2017 New H3C Technologies Co., Ltd. All rights reserved.

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.



Introduction

This document provides Ethernet link aggregation configuration examples.

Prerequisites

This document applies to Comware V7-based MSR routers. Procedures and information in the examples might be slightly different depending on the software or hardware version of the router.

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 3 link aggregation

Network requirements

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

·     Configure a Layer 3 dynamic aggregation group on both Device A and Device B.

·     Configure IP addresses and subnet masks for the corresponding Layer 3 aggregate interfaces.

Figure 1 Network diagram

 

Software version used

This configuration example was created and verified on R0106.

Configuration restrictions and guidelines

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.

Configuration procedures

1.     Configure Device A:

# Create Layer 3 aggregate interface Route-Aggregation 1. Use one of the following methods as needed.

¡     Use the static aggregation mode to create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

¡     Use the dynamic aggregation mode to create Layer 3 aggregate interface Route-Aggregation 1.

<DeviceA> system-view

[DeviceA] interface route-aggregation 1

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

# Configure an IP address and subnet mask for Layer 3 aggregate interface Route-Aggregation 1.

[DeviceA-Route-Aggregation1] ip address 192.168.1.1 24

[DeviceA-Route-Aggregation1] quit

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

[DeviceA] interface range gigabitethernet 2/1/1 to gigabitethernet 2/1/3

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

[DeviceA-if-range] 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

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

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

        G -- Defaulted, H -- Expired

 

Aggregate Interface: Route-Aggregation1

Aggregation Mode: Static

Loadsharing Type: Shar

  Port             Status  Priority Oper-Key

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

  GE2/1/1          S       32768    1

  GE2/1/2          S       32768    1

  GE2/1/3          S       32768    1

The output shows that all member ports in the local aggregation group are in 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

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

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

        G -- Defaulted, H -- Expired

 

Aggregate Interface: Route-Aggregation1

Aggregation Mode: Dynamic

Loadsharing Type: Shar

System ID: 0x8000, 000f-e267-6c6a

Local:

  Port             Status  Priority Oper-Key  Flag

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

  GE2/1/1          S       32768    1         {ACDEF}

  GE2/1/2          S       32768    1         {ACDEF}

  GE2/1/3          S       32768    1         {ACDEF}

Remote:

  Actor            Partner Priority Oper-Key  SystemID               Flag

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

  GE2/1/1          1       32768    1         0x8000, 000f-e267-57ad {ACDEF}

  GE2/1/2          2       32768    1         0x8000, 000f-e267-57ad {ACDEF}

  GE2/1/3          3       32768    1         0x8000, 000f-e267-57ad {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:

#

¡     In the static aggregation mode:

#

interface route-aggregation1

 ip address 192.168.1.1 255.255.255.0

#

¡     In the dynamic aggregation mode:

#

interface route-aggregation1

 ip address 192.168.1.1 255.255.255.0

 link-aggregation mode dynamic

#

interface GigabitEthernet2/1/1

 port link-mode route

port link-aggregation group 1

#

interface GigabitEthernet2/1/2

 port link-mode route

port link-aggregation group 1

#

interface GigabitEthernet2/1/3

 port link-mode route

port link-aggregation group 1

#

·     Device B:

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

Related documentation

·     H3C MSR Series Routers Layer 2—LAN Switching Command Reference (V7)

·     H3C MSR Series Routers Layer 2—LAN Switching Configuration Guide (V7)

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网