Configuration Guide - LAN(V200R002C00_02)

8/12/2019 Configuration Guide - LAN(V200R002C00_02)

1/254

Huawei AR1200-S Series Enterprise Routers

V200R002C00

Configuration Guide - LAN

Issue 02

Date 2012-03-30

HUAWEI TECHNOLOGIES CO., LTD.


2/254

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2012-03-30) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/254

About This Document

Intended Audience

This document describes how to configure the components for LAN services, including link

aggregation groups, VLANs, voice VLANs, MAC address tables, transparent bridging, as well

as GVRP, STP/RSTP, and MSTP protocols.

This document provides procedures and examples to illustrate the methods and application

scenarios for the service configurations.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

DANGER

Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,

performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save

time.

NOTE Provides additional information to emphasize or supplement

important points of the main text.


Configuration Guide - LAN About This Document



ii


4/254

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by vertical

bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by vertical

bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated by verticalbars. A minimum of one item or a maximum of all items can be

selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by vertical

bars. Several items or no item can be selected.

& The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Interface Numbering Conventions

Interface numbers used in this manual are examples. In device configuration, use the existing

interface numbers on devices.

Change History

Changes between document issues are cumulative. Therefore, the latest document version

contains all updates made to previous versions.

Changes in Issue 02 (2012-03-30)

Based on issue 01 (2011-12-30), the document is updated as follows:

The following information is modified:

l 3.8.2 Example for Configuring Communication Between VLANs Using VLANIF

Interfaces

Changes in Issue 01 (2011-12-30)

Initial commercial release.


Configuration Guide - LAN About This Document



iii


5/254

Contents

About This Document.....................................................................................................................ii

1 Link Aggregation Configuration................................................................................................1

1.1 Introduction to Link Aggregation.......................................................................................................................2

1.2 Link Aggregation Supported by the AR1200-S.................................................................................................21.3 Configuring Link Aggregation in Manual Load Balancing Mode.....................................................................3

1.3.1 Establishing the Configuration Task.................................................................... .....................................3

1.3.2 Creatingan Eth-Trunk Interface................................................................................................................4

1.3.3 Configuring an Eth-Trunk to Work in Manual Load Balancing Mode.....................................................5

1.3.4 Adding Member Interfaces to an Eth-Trunk.............................................................................................6

1.3.5 (Optional) Limiting the Number of Active Interfaces...............................................................................7

1.3.6 Checking the Configuration.......................................................................................................................8

1.4 Configuring Link Aggregation in Static LACP Mode.......................................................................................9

1.4.1 Establishing the Configuration Task.........................................................................................................9

1.4.2 Creatingan Eth-Trunk Interface..............................................................................................................10

1.4.3 Configuring an Eth-Trunk to Work in Static LACP Mode.....................................................................11

1.4.4 Adding Member Interfaces to an Eth-Trunk...........................................................................................11

1.4.5 (Optional) Limiting the Number of Active Interfaces.............................................................................13

1.4.6 (Optional) Setting the LACP Priority of the System...............................................................................14

1.4.7 (Optional) Setting the LACP Priority for an Interface............................................................................14

1.4.8 (Optional) Enabling LACP Preemption and Setting the Preemption Delay...........................................15

1.4.9 (Optional) Setting the Timeout Interval for Receiving LACP Packets...................................................16

1.4.10 Checking the Configuration...................................................................................................................16

1.5 Maintaining Link Aggregation.........................................................................................................................17

1.5.1 Clearing Statistics of LACP Packets.......................................................................................................17

1.5.2 Debugging the Link Aggregation Group.................................................................................................18

1.5.3 Monitoring the Operating Status of the Link Aggregation Group..........................................................18

1.6 Configuration Examples...................................................................................................................................19

1.6.1 Example for Configuring Link Aggregation in Manual Load Balancing Mode.....................................19

1.6.2 Example for Configuring Link Aggregation in Static LACP Mode.......................................................21

1.6.3 Example for Configuring Layer 3 Link Aggregation..............................................................................24

2 Transparent Bridging Configuration.......................................................................................28

2.1 Overview of Transparent Bridging...................................................................................................................29


Configuration Guide - LAN Contents



iv


6/254

2.2 Transparent Bridging Supported by the AR1200-S.........................................................................................32

2.3 Configuring Local Bridging.............................................................................................................................33

2.3.1 Establishing the Configuration Task.......................................................................................................33

2.3.2 Creating a Bridge Group..........................................................................................................................34

2.3.3 Adding Local Interfaces to a Bridge Group............................................................................................35

2.3.4 (Optional) Disabling a Bridge Group from Bridging Specified Protocol Packets..................................36

2.3.5 Checking the Configuration.....................................................................................................................36

2.4 Configuring Local Bridging Integrated with IP Routing..................................................................................37


2.4.2 Creatinga Bridge Group..........................................................................................................................38

2.4.3 Adding Local Interfaces to a Bridge Group............................................................................................39

2.4.4 Configuring a Bridge-if Interface for a Bridge Group.............................................................................41

2.4.5 Enabling IP Routing for a Bridge Group.................................................................................................41



2.5 Configuring Remote Bridging..........................................................................................................................43



2.5.3 Adding User-side Interfaces to a Bridge Group......................................................................................45

2.5.4 AddingNetwork-side Interfaces to a Bridge Group................................................................................46


2.5.6 (Optional) Configuring VLAN ID Transparent Transmission................................................................49

2.5.7 Checking the Configuration.....................................................................................................................492.6 Configuring Remote Bridging Integrated with IP Routing..............................................................................50



2.6.3 Adding User-side Interfaces to a Bridge Group......................................................................................52

2.6.4 AddingNetwork-side Interfaces to a Bridge Group................................................................................53

2.6.5 Configuring a Bridge-if Interface for a Bridge Group.............................................................................55

2.6.6 Enabling IP Routing for a Bridge Group.................................................................................................56



2.7 Maintaining Transparent Bridging...................................................................................................................58

2.7.1 Monitoring the Operation of Bridge Groups...........................................................................................58

2.7.2 Clearingthe Traffic Statistics of a Bridge Group....................................................................................59

2.7.3 Clearingthe Traffic Statistics on the Bridge-if Interface of a Bridge Group..........................................59

2.8 ConfigurationExample.....................................................................................................................................60

2.8.1 Examplefor Configuring Local Bridging...............................................................................................60

2.8.2 Examplefor Configuring Local Bridging with IP Routing.....................................................................63

2.8.3 Example for Configuring Remote Bridging............................................................................................65

2.8.4 Examplefor Configuring Remote Bridging with IP Routing..................................................................68

2.8.5 Examplefor Configuring Remote Bridging with VLAN ID Transparent Transmission........................71





v


7/254

3 VLAN Configuration..................................................................................................................76

3.1 Introduction to VLAN......................................................................................................................................77

3.2 VLAN Features Supported by the AR1200-S..................................................................................................77

3.3 Creating VLANs...............................................................................................................................................79


3.3.2 Creating a VLAN.....................................................................................................................................79

3.3.3 (Optional) Creating VLANs in a Batch...................................................................................................80

3.3.4 (Optional) Configuring the Priority for a VLAN....................................................................................80


3.4 Adding Interfaces to a VLAN..........................................................................................................................81


3.4.2 Adding an Access Interface to a VLAN..................................................................................................82

3.4.3 Adding a Trunk Interface to a VLAN......................................................................................................83

3.4.4 Adding a Hybrid Interface to a VLAN....................................................................................................84

3.4.5 (Optional) Specifying the Default VLAN for a Trunk Interface.............................................................84

3.4.6 (Optional) Specifying the Default VLAN for a Hybrid Interface...........................................................85


3.5 Configuring VLANIF Interfaces to Implement Layer-3 Communication.......................................................87


3.5.2 Creatinga VLANIF Interface..................................................................................................................88

3.5.3 Assigning an IP Address to a VLANIF Interface....................................................................................88

3.5.4 (Optional) Setting the MTU of a VLANIF Interface...............................................................................88

3.5.5 (Optional) Configuring VLAN Damping................................................................................................893.5.6 Checking the Configuration.....................................................................................................................90

3.6 Configuring VLAN Aggregation......................................................................................................................90


3.6.2 Configuring Sub-VLANs........................................................................................................................91

3.6.3 Creatinga Super-VLAN..........................................................................................................................92

3.6.4 Assigning an IP Address to the VLANIF Interface of the Super-VLAN................................................93

3.6.5 Configuring Proxy ARP for the Super-VLAN........................................................................................93


3.7 Configuring aManagement VLAN..................................................................................................................95


3.7.2 Configuring Management VLAN Functions...........................................................................................95


3.8 ConfigurationExamples...................................................................................................................................96

3.8.1 Examplefor Configuring Interface-based VLAN Assignment...............................................................96

3.8.2 Example for Configuring Communication Between VLANs Using VLANIF Interfaces......................99

3.8.3 Examplefor Configuring VLAN Damping...........................................................................................101

3.8.4 Examplefor Configuring VLAN Aggregation......................................................................................103

3.8.5 Examplefor Configuring Communication Across a Layer 3 Network Using VLANIF Interfaces......106

4 Voice VLAN Configuration.....................................................................................................111





vi


8/254


9/254

6.4.6 (Optional) Setting the Aging Time for Secure Dynamic MAC Addresses on an Interface..................147


6.5 Configuring Limitation on MAC Address Learning......................................................................................148

6.5.1 Establishing the Configuration Task.....................................................................................................148

6.5.2 Limiting MAC Address Learning on an Interface.................................................................................148


6.6 Configuring MAC Address Flapping Detecting Function.............................................................................150


6.6.2 Configuring MAC Address Flapping Detection....................................................................................150

6.6.3 Unblocking an Interface or a MAC Address.........................................................................................151


6.7 Configuring the Router to Discard Packets with an Invalid All-0 MAC Address.........................................152


6.7.2 Configuring the Router to Discarding Packets with All-0 MAC Addresses.........................................152

6.7.3 Triggering an Alarm for Packets with All-0 MAC Addresses..............................................................153


6.8 Maintaining the MAC Address Table............................................................................................................154

6.8.1 Debugging the MAC Address Table.....................................................................................................154

6.9 ConfigurationExamples.................................................................................................................................154

6.9.1 Examplefor Configuring the MAC Address Table...............................................................................154

6.9.2 Examplefor Configuring Port Security.................................................................................................157

6.9.3 Example for Configuring MAC Address Limiting Rules on Interfaces................................................159

7 STP/RSTP Configuration.........................................................................................................1617.1 STP/RSTP Overview......................................................................................................................................162

7.2 STP/RSTP Features Supported by the AR1200-S..........................................................................................166

7.3 Configuring Basic STP/RSTP Functions.......................................................................................................168


7.3.2 Configuring the STP/RSTP Mode.........................................................................................................170

7.3.3 (Optional) Configuring Switching Device Priorities.............................................................................170

7.3.4 (Optional) Configuring the Path Cost for a Port....................................................................................171

7.3.5 (Optional) Configuring Port Priorities...................................................................................................172

7.3.6 Enabling STP/RSTP..............................................................................................................................1737.3.7 Checking the Configuration...................................................................................................................173

7.4 Configuring STP/RSTP Parameters on an Interface......................................................................................174


7.4.2 Configuring System Parameters............................................................................................................177

7.4.3 Configuring Port Parameters.................................................................................................................179


7.5 Configuring RSTP Protection Functions........................................................................................................182


7.5.2 Configuring BPDU Protection on a Switching Device.........................................................................184

7.5.3 Configuring TC Protection on a Switching Device...............................................................................184





viii


10/254

7.5.4 Configuring Root Protection on a Port..................................................................................................185

7.5.5 Configuring Loop Protection on a Port.................................................................................................186


7.6 Maintaining STP/RSTP..................................................................................................................................187

7.6.1 Clearing STP/RSTP Statistics...............................................................................................................188

7.7 Configuration Examples.................................................................................................................................188

7.7.1 Example for Configuring Basic STP Functions....................................................................................188

7.7.2 Examplefor Configuring Basic RSTP Functions..................................................................................192

8 MSTP Configuration.................................................................................................................198

8.1 MSTP Introduction.........................................................................................................................................200

8.2 MSTP Features Supported by the AR1200-S.................................................................................................207

8.3 Configuring Basic MSTP Functions...............................................................................................................209


8.3.2 Configuring the MSTP Mode................................................................................................................212

8.3.3 Configuring and Activating an MST Region........................................................................................212

8.3.4 (Optional) Configuring a Priority for a Switching Device in an MSTI.................................................214

8.3.5 (Optional) Configuring a Path Cost of a Port in an MSTI.....................................................................215

8.3.6 (Optional) Configuring a Port Priority in an MSTI...............................................................................216

8.3.7 Enabling MSTP.....................................................................................................................................217


8.4 Configuring MSTP Parameters on an Interface.............................................................................................218


8.4.2 Configuring System Parameters............................................................................................................219

8.4.3 Configuring Port Parameters.................................................................................................................221


8.5 Configuring MSTP Protection Functions.......................................................................................................224


8.5.2 Configuring BPDU Protection on a Switching Device.........................................................................226

8.5.3 Configuring TC Protection on a Switching Device...............................................................................227

8.5.4 Configuring Root Protection on an Interface........................................................................................228

8.5.5 Configuring Loop Protection on an Interface........................................................................................229

8.5.6 Checking the Configuration...................................................................................................................2298.6 Configuring MSTP Interoperability Between Huawei Devices and Non-Huawei Devices...........................230


8.6.2 Configuring a Proposal/Agreement Mechanism...................................................................................231

8.6.3 Configuring the MSTP Protocol Packet Format on an Interface...........................................................232

8.6.4 Enabling the Digest Snooping Function................................................................................................233


8.7 Maintaining MSTP.........................................................................................................................................234

8.7.1 ClearingMSTP Statistics.......................................................................................................................234

8.8 ConfigurationExamples.................................................................................................................................235





ix


11/254


12/254

1Link Aggregation ConfigurationAbout This Chapter

This chapter describes link aggregation concepts and how to configure link aggregation groups

while also providing configuration examples.

1.1 Introduction to Link Aggregation

This section describes the concept of link aggregation.

1.2 Link Aggregation Supported by the AR1200-S

This section describes the link aggregation features supported by the AR1200-S.

1.3 Configuring Link Aggregation in Manual Load Balancing ModeThis section describes how to configure link aggregation in manual load balancing mode.

1.4 Configuring Link Aggregation in Static LACP Mode

This section describes how to configure link aggregation in static LACP mode.

1.5 Maintaining Link Aggregation

This section describes how to clear the statistics of received and sent LACP packets, debug the

link aggregation group, and monitor the running status of the link aggregation group.

1.6 Configuration Examples

This section provides configuration examples of link aggregation in manual load balancing mode

and in static LACP mode.


Configuration Guide - LAN 1 Link Aggregation Configuration



1


13/254

1.1 Introduction to Link Aggregation

This section describes the concept of link aggregation.

Link aggregation refers to a method of bundling a group of physical interfaces into a logical

interface to increase bandwidth and improve reliability. These types of groupings are also called

multi-interface load sharing groups or link aggregation groups (LAGs). For details, refer to

IEEE802.3ad.

Link aggregation provides redundancy protection for communication channels among between

devices without upgrading the hardware to higher capacities.

1.2 Link Aggregation Supported by the AR1200-S

This section describes the link aggregation features supported by the AR1200-S.

Manual Load Balancing Mode

In load balancing mode, you can manually add member interfaces to a link aggregation group

(LAG). All the interfaces configured with load balancing are in forwarding state. The AR1200-

S can perform load balancing based on Exclusive-Or of source and destination MAC addresses,

or Exclusive-Or of source and destination IP addresses.

The manual load balancing mode does not use the Link Aggregation Control Protocol (LACP).

The AR1200-S can use this mode if the peer device does not support LACP.

Static LACP Mode

In static LACP mode, devices at two ends of a link negotiate aggregation parameters by

exchanging LACP packets. After the negotiation is complete, the two devices determine the

active interface and the inactive interface. In this mode, you need to manually create an Eth-

Trunk and add members to it. LACP negotiation determines which interfaces are active and

which ones are inactive.

The static LACP mode is also called the M:N mode. In this mode, links load balance traffic and

provide redundancy backup at the same time. In an LAG, M links are active and they forward

data in load balancing mode. N links are inactive and they function as backup links. The backup

links do not forward data. If an active link fails, data forwarding is switched to the backup link

with the highest priority, and the status of the backup link changes to active.

In static LACP mode, some links function as backup links. In manual load balancing mode, all

member interfaces work in forwarding state to share the traffic. This is the main difference

between the two modes.

Active and Inactive Interfaces

Active interfaces refer to the interfaces in active state that forward data. The interfaces that do

not forward data and are in inactive state are called inactive interfaces. Depending on the link

aggregation mode the interfaces use, active and inactive interfaces are classified as follows:

l

Manual load balancing mode: Generally, all member interfaces are active interfaces unlessa fault occurs.





2


14/254

l Static LACP mode: The interfaces connected to M links are active interfaces that forward

data; the interfaces connected to N links are inactive interfaces that are used for redundancy

backup.

Actor and Partner

In static LACP mode, the device in the link aggregation group with a higher LACP priorityis

the Actor and the device with a lower LACP priority is the Partner.

If the two devices have the same LACP priority, the Actor is selected based on the MAC

addresses of the devices. The device with a smaller MAC address becomes the Actor.

Differentiating the Actor and the Partner keeps the active interfaces at both ends consistent. If

both ends select active interfaces according to the priorities of their own interfaces, the active

interfaces may be different at two ends. To prevent this problem, devices at two ends determine

the Actor first, and the Partner selects active interfaces according to priorities of the interfaces

on the Actor. Figure 1-1shows the process of selecting active interfaces.

Figure 1-1Determining the active links in static LACP mode

RouterA RouterB

RouterBRouterA

The Actor determines

the active link

Device with high

priority

Device with low

priority

Active interface selected by RouterA

Active interface selected by RouterB

1.3 Configuring Link Aggregation in Manual Load

Balancing ModeThis section describes how to configure link aggregation in manual load balancing mode.

1.3.1 Establishing the Configuration Task

Applicable Environment

When the bandwidth or the reliability of two devices should be increased and either of the two

devices does not support LACP, create an Eth-Trunk in manual load balancing mode on thedevices and add member interfaces to the Eth-Trunk, as shown in Figure 1-2.





3


15/254

Figure 1-2Network diagram of link aggregation in manual load balancing mode

RouterA RouterBEth-Trunk 1 Eth-Trunk 1

Eth-Trunk

Pre-configuration Tasks

Before configuring an Eth-Trunk in manual load balancing mode, complete the following tasks:

l Powering on the AR1200-S

l Creating an Eth-Trunk

Data PreparationTo configure an Eth-Trunk in manual load balancing mode, you need the following data.

No. Data

1 Number of the Eth-Trunk in manual load balancing mode

2 Types and numbers of the member interfaces

1.3.2 Creating an Eth-Trunk Interface

Context

Eth-Trunk interfaces increase bandwidth and improve transmission reliability. You can

configure Layer 2 and Layer 3 Eth-Trunk interfaces for different applications on a network.

Procedure

l Creating a Layer 2 Eth-Trunk interface

1. Run:

system-view

The system view is displayed.

2. Run:

interface eth-trunktrunk-id

A Layer 2 Eth-Trunk interface is created.

By default, an Eth-Trunk interface works in Layer 2 mode.

l Creating a Layer 3 Eth-Trunk interface

1. Run:

system-view






4


16/254

2. Run:


A Layer 2 Eth-Trunk interface is created.

3. Run:

undo portswitch

The Eth-Trunk interface is configured to work in Layer 3 mode.

4. Run:

ip addressip-address{ mask| mask-length} [ sub]

An IP address is configured for the Layer 3 Eth-Trunk interface.

5. (Optional) Run:

mtumtu

The maximum transmission unit (MTU) of the Eth-Trunk interface is set.

The default MTU of an interface is 1500 bytes.

CAUTION

l The mtucommand cannot be used on Layer 2 Eth-Trunk interfaces.

l Directly connected interfaces must use the same MTU. If you change the MTU of

an interface, you must use the mtucommand to change the MTU of the peer

interface to the same value; otherwise, services may be interrupted.

l After changing the MTU on an interface, run the shutdowncommand and then

the undo shutdowncommand on the interface to make the setting take effect.

----End

1.3.3 Configuring an Eth-Trunk to Work in Manual Load BalancingMode

Context

Perform the following steps on the AR1200-S to configure an Eth-Trunk in manual loadbalancing mode.

NOTE

Check whether the Eth-Trunk contains member interfaces before you configure the operation mode of the

Eth-Trunk. If the Eth-Trunk contains member interfaces, the operation mode of the Eth-Trunk cannot be

changed. To delete member interfaces from the Eth-Trunk, run the undo eth-trunkcommand in the

interface view or run the undo trunkportinterface-type { interface-number1 [ tointerface-number2 ] }

& command in the Eth-Trunk view.

Procedure

Step 1 Run:system-view





5


17/254


Step 2 Run:interface eth-trunktrunk-id

The Eth-Trunk interface view is displayed.

Step 3 Run:mode manual load-balance

The operation mode of the Eth-Trunk is set to manual load balancing.

By default, an Eth-Trunk works in manual load balancing mode.

If the local device is configured with an Eth-Trunk in manual load balancing mode, configure

the Eth-Trunk in manual load balancing mode on the peer device.

----End

1.3.4 Adding Member Interfaces to an Eth-Trunk

Context

Perform the following steps on the AR1200-S to configure member interfaces of an Eth-Trunk.

Procedure

l Configuration in the Eth-Trunk interface view

1. Run:

system-view


2. Run:



3. Run:

trunkportinterface-type{ interface-number1[ tointerface-number2] }

&

Member interfaces are added to the Eth-Trunk.

l Configuration in the member interface view

1. Run:

system-view


2. Run:

interfaceinterface-typeinterface-number

The interface view is displayed.

3. Run:

eth-trunktrunk-id

The interface is added to the Eth-Trunk.

When adding an interface to an Eth-Trunk, pay attention to the following points:





6


18/254

Member interfaces of a Layer 2 Eth-Trunk must be Layer 2 interfaces, and member

interfaces of a Layer 3 Eth-Trunk must be Layer 3 interfaces.

An Eth-Trunk supports a maximum of eight member interfaces.

A member interface cannot have any service or static MAC address configured.

Ensure that interfaces added to an Eth-Trunk are hybrid interfaces (the default interface

type).

An Eth-Trunk interface cannot have other Eth-Trunk interfaces as member interfaces.

An Ethernet interface can be added to only one Eth-trunk interface. To add the Ethernet

interface to another Eth-trunk, delete the Ethernet interface from the current Eth-Trunk

first.

Member interfaces of an Eth-trunk must be the same type. For example, an FE interface

and a GE interface cannot be added to the same Eth-trunk interface.

Ethernet interfaces on different LPUs can be added to the same Eth-Trunk.

The peer interface directly connected to a member interface of the local Eth-Trunk mustalso be added to an Eth-Trunk; otherwise, the two ends cannot communicate.

When member interfaces have different rates, the interfaces with lower rates may

become congested and packet loss may occur.

After an interface is added to an Eth-Trunk, MAC address learning is performed by the

Eth-Trunk rather than the member interfaces.

G.SHDSL interfaces that work in PTM mode cannot be added to an Eth-Trunk.

----End

1.3.5 (Optional) Limiting the Number of Active Interfaces

Context

Perform the following steps on the AR1200-S to limit the number of active interfaces.

Procedure

l Setting the maximum number of interfaces that determine bandwidth for an Eth-Trunk

1. Run:

system-view


2. Run:



3. Run:

max bandwidth-affected-linknumberlink-number

The maximum number of interfaces that determine bandwidth for the Eth-Trunk is

set.

By default, the maximum number of interfaces that determine bandwidth for an Eth-Trunk is 8.





7


19/254

NOTE

l The maximum number of interfaces that determine bandwidth for an Eth-Trunk on the local

AR1200-S and that on the remote AR1200-S can be different. If the values of this setting at the

two ends are different, the smaller value is used.

l Setting the minimum number of active interfaces1. Run:

system-view


2. Run:



3. Run:

least active-linknumberlink-number

The minimum number of active interfaces is set.

By default, the minimum number of active interfaces is 1.

In manual load balancing mode, you can determine the minimum number of active

interfaces in the Eth-Trunk. If the number of active interfaces is smaller than the minimum

value, the status of the Eth-Trunk becomes Down.

NOTE

l The minimum number of active interfaces on the local AR1200-S and that on the remote AR1200-

S can be different. If the values of this setting at the two ends are different, the larger value is

used.

----End

1.3.6 Checking the Configuration

Procedure

l Run the display trunkmembership eth-trunktrunk-idcommand to display the member

interfaces of the Eth-Trunk.

l Run the display eth-trunk[ trunk-id] command to display the load balancing status of the

Eth-Trunk.

----End

Example

Run the display trunkmembership eth-trunkcommand to view the operation mode, total

number of member interfaces, number of member interfaces in Up state, and information about

the member interfaces.

display trunkmembership eth-trunk 1

Trunk ID: 1

Used status: VALIDTYPE: ethernet

Working Mode :Normal

Number Of Ports in Trunk = 2

Number Of Up Ports in Trunk = 0Operate status: down





8


20/254

Interface Ethernet0/0/1, valid, operate down, weight=1


Run the display eth-trunkcommand to check the load balancing mode of the Eth-Trunk. By

default, the load balancing mode of the Layer 2 Eth-Trunk is displayed as "SA-XOR-DA" in the

output information.

display eth-trunk 1Eth-Trunk1's state information is:

WorkingMode: NORMAL Hash arithmetic: According to SA-XOR-DA

Least Active-linknumber: 1 Max Bandwidth-affected-linknumber: 8Operate status: down Number Of Up Port In Trunk: 0

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

PortName Status WeightEthernet0/0/1 Down 1

Ethernet0/0/2 Down 1

1.4 Configuring Link Aggregation in Static LACP ModeThis section describes how to configure link aggregation in static LACP mode.

1.4.1 Establishing the Configuration Task

Applicable Environment

To increase the bandwidth and improve the connection reliability, you can configure a link

aggregation group on two directly connected routers. The requirements are as follows:

l The links between two devices can implement redundancy backup. When a fault occurs onone or more links, the backup links replace the faulty ones to help ensure uninterrupted

data transmission.

l The active links have the load balancing capability.

Figure 1-3Networking of link aggregation in static LACP mode

RouterB

Eth-Trunk 1

RouterA

Eth-Trunk 1

Eth-TrunkActive link

Standby link

Pre-configuration Tasks

Before configuring an Eth-Trunk in static LACP mode, complete the following tasks:

l Powering on the AR1200-S

l Creating an Eth-Trunk

Data Preparation

To configure an Eth-Trunk in static LACP mode, you need the following data.





9


21/254


22/254

CAUTION

l The mtucommand cannot be used on Layer 2 Eth-Trunk interfaces.

l Directly connected interfaces must use the same MTU. If you change the MTU ofan interface, you must use the mtucommand to change the MTU of the peer

interface to the same value; otherwise, services may be interrupted.

l After changing the MTU on an interface, run the shutdowncommand and then

the undo shutdowncommand on the interface to make the setting take effect.

----End

1.4.3 Configuring an Eth-Trunk to Work in Static LACP Mode

ContextNOTE

Check whether the Eth-Trunk contains member interfaces before you configure the operation mode of the

Eth-Trunk. If the Eth-Trunk contains member interfaces, the operation mode of the Eth-Trunk cannot be

changed. To delete member interfaces from the Eth-Trunk, run the undo eth-trunkcommand in the

interface view or run the undo trunkportinterface-type { interface-number1 [ tointerface-number2 ] }

& command in the Eth-Trunk view.

Perform the following steps on the AR1200-S.

Procedure





Step 3 Run:mode lacp-static

The Eth-Trunk is configured to work in static LACP mode.

By default, an Eth-Trunk works in manual load balancing mode.

If the local device is configured with an Eth-Trunk in static LACP mode, configure the Eth-

Trunk in static LACP mode on the peer device.

----End

1.4.4 Adding Member Interfaces to an Eth-Trunk

Context






11


23/254

Procedure

l Configuration in the Eth-Trunk interface view

1. Run:

system-view


2. Run:



3. Run:

trunkportinterface-type{ interface-number1[ tointerface-number2] }

&

Member interfaces are added to the Eth-Trunk.

l Configuration in the member interface view

1. Run:

system-view


2. Run:

interfaceinterface-typeinterface-number


3. Run:

eth-trunktrunk-id

The interface is added to the Eth-Trunk.

When adding an interface to an Eth-Trunk, pay attention to the following points:

Member interfaces of a Layer 2 Eth-Trunk must be Layer 2 interfaces, and member

interfaces of a Layer 3 Eth-Trunk must be Layer 3 interfaces.

An Eth-Trunk contains a maximum of eight member interfaces.

A member interface cannot be configured with any service or static MAC address.

Ensure that interfaces added to an Eth-Trunk are hybrid interfaces (the default interface

type).

An Eth-Trunk interface cannot have other Eth-Trunk interfaces as member interfaces.

An Ethernet interface can be added to only one Eth-trunk interface. To add the Ethernet

interface to another Eth-trunk, delete the Ethernet interface from the current Eth-Trunk

first.

The member interfaces of an Eth-trunk must be the same type, that is, an FE interface

and a GE interface cannot be added to the same Eth-trunk.

Ethernet interfaces on different LPUs can be added to the same Eth-Trunk.

The peer interface directly connected to a member interface of the local Eth-Trunk must

also be added to an Eth-Trunk; otherwise, the two ends cannot communicate.

When member interfaces have different rates, the interfaces with lower rates maybecome congested and packet loss may occur.





12


24/254

After an interface is added to an Eth-Trunk, MAC address learning is performed by the

Eth-Trunk rather than the member interfaces.

----End

1.4.5 (Optional) Limiting the Number of Active Interfaces

Context

Perform the following steps on the AR1200-S to limit the number of active interfaces.

Procedure

l Setting the maximum number of active interfaces

1. Run:

system-view


2. Run:



3. Run:

max active-linknumberlink-number

The maximum number of active interfaces is set.

In static LACP mode, you can limit the maximum number (M) of active interfaces in the

Eth-Trunk. The other member interfaces function as backups.

If the maximum number of active interfaces is not set, up to eight interfaces in the Eth-

Trunk can be active.

NOTE

l The maximum number of active interfaces must be larger than or equal to the minimum number

of active interfaces.

l The maximum number of active interfaces on the local AR1200-S and that on the remote

AR1200-S can be different. If the values of this setting at the two ends are different, the smaller

value is used.

l Setting the minimum number of active interfaces

1. Run:system-view


2. Run:



3. Run:

least active-linknumberlink-number

The minimum number of active interfaces is set.

By default, the minimum number of active interfaces is 1.





13


25/254

In static LACP mode, you can determine the minimum number of active interfaces in the

Eth-Trunk. If the number of active interfaces is smaller than the minimum value, the status

of the Eth-Trunk becomes Down.

NOTE

l The minimum number of active interfaces must be smaller than or equal to the maximum number

of active interfaces.

l The minimum number of active interfaces on the local AR1200-S and that on the remote AR1200-

S can be different. If the values of this setting at the two ends are different, the larger value is

used.

----End

1.4.6 (Optional) Setting the LACP Priority of the System

ContextPerform the following steps on the AR1200-S to set the LACP priority of the system.

Procedure



Step 2 Run:lacp prioritypriority

The system LACP priority is set for the AR1200-S.

A smaller LACP priority value indicates a higher priority. By default, the LACP priority of the

system is 32768.

The end with smaller priority value functions as the Actor. If the two ends have the same priority,

the end with a smaller MAC address functions as the Actor.

----End

1.4.7 (Optional) Setting the LACP Priority for an Interface

Context

Perform the following steps on the AR1200-S to set the LACP priority for an interface.

Procedure



Step 2 Run:interfaceinterface-typeinterface-number





14


26/254


Step 3 Run:lacp prioritypriority

The LACP priority is set for the interface.

By default, the LACP priority of an interface is 32768.

----End

1.4.8 (Optional) Enabling LACP Preemption and Setting thePreemption Delay

Context


Procedure





Step 3 Run:lacp preempt enable

The LACP preemption function is enabled on the Eth-Trunk interface.

By default, the LACP preemption function is disabled.

NOTE

To ensure normal running of an Eth-Trunk, it is recommended that you enable or disable LACP preemption

on both ends of the Eth-Trunk.

Step 4 Run:lacp preempt delaydelay-time

The preemption delay is set for the Eth-Trunk.

By default, the preemption delay is 30 seconds.

LACP preemption function ensures that the interface with the highest LACP priority serves as

an active interface. If this function is enabled, the interface with the highest priority automatically

becomes an active interface after recovering from a failure. If this function is enabled, the

interface cannot automatically become an active interface again after it goes Down due to a

failure.

The delay for LACP preemption refers to the period in which an inactive interface of the Eth-

Trunk in static LACP mode waits before it becomes active.

----End





15


27/254

1.4.9 (Optional) Setting the Timeout Interval for Receiving LACPPackets

ContextPerform the following steps on the AR1200-S to set the timeout interval for receiving LACP

packets.

Procedure



Step 2 Run:



Step 3 Run:lacp timeout{ fast| slow}

The timeout interval for receiving LACP protocol packets is set on the Eth-Trunk.

NOTE

l After the lacp timeoutcommand is configured, the local end informs the peer end of the configured

timeout interval through LACP packets. The peer end then sends LACP packets at the specified interval.

If the fastkeyword is used, the peer end sends LACP packets at an interval of 1 second. If the slow

keyword is used, the peer end sends LACP packets at an interval of 30 seconds.

l The timeout interval for receiving LACP packets on the local end is three times the interval at which

the peer end sends LACP packets. That is, when the fastkeyword is used, the timeout interval for

receiving LACP packets is 3s; when the slowkeyword is used, the timeout interval for receiving LACP

packets is 90s.

l You can select different keywords on the two ends. However, it is recommended that you select the

same keyword on both ends to facilitate maintenance.

----End

1.4.10 Checking the Configuration

Procedurel Run the display trunkmembership eth-trunktrunk-idcommand to display the member


l Run the display eth-trunk[ trunk-id[interfaceinterface-typeinterface-number] ]

command to display information about the Eth-Trunk and member interfaces.

----End

Example

Run the display trunkmembership eth-trunkcommand to view the operation mode, total

number of member interfaces, number of member interfaces in Up state, and information aboutmember interfaces of an Eth-Trunk.





16


28/254

display trunkmembership eth-trunk 1

Trunk ID: 1

Used status: VALIDTYPE: ethernet

Working Mode : Static

Number Of Ports in Trunk = 3

Number Of UP Ports in Trunk = 0operate status: down




Run the display eth-trunkcommand to view information about an Eth-Trunk. The following

information shows that the Eth-Trunk work in static LACP mode.

display eth-trunk 1Eth-Trunk1's state information is:

Local:LAG ID: 1 WorkingMode: STATICPreempt Delay: Disabled Hash arithmetic: According to SIP-XOR-DIP

System Priority: 50 System ID: 000b-09d3-dc62

Least Active-linknumber: 3 Max Active-linknumber: 8Operate status: down Number Of Up Port In Trunk: 0

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

ActorPortName Status PortType PortPri PortNo PortKey PortState Weight

Ethernet0/0/1 Unselect 100M 10 1547 561 11100000 1Ethernet0/0/2 Unselect 100M 32768 1548 561 11100010 1

Ethernet0/0/3 Unselect 100M 32768 1549 561 11100010 1

Partner:

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

ActorPortName SysPri SystemID PortPri PortNo PortKey PortState

Ethernet0/0/1 0 0000-0000-0000 0 0 0 11100000Ethernet0/0/2 0 0000-0000-0000 0 0 0 11100011

Ethernet0/0/3 0 0000-0000-0000 0 0 0 11100011

1.5 Maintaining Link Aggregation

This section describes how to clear the statistics of received and sent LACP packets, debug the

link aggregation group, and monitor the running status of the link aggregation group.

1.5.1 Clearing Statistics of LACP Packets

Context

CAUTION

The statistics of LACP packets cannot be restored after being cleared.

Procedure

Step 1 Run the reset lacp statistics eth-trunk[ trunk-id[ interfaceinterface-type interface-number] ] command in the user view to clear statistics of received and sent LACP packets.

----End





17


29/254

1.5.2 Debugging the Link Aggregation Group

Context

CAUTION

Debugging affects system performance. Run the undo debugging allcommand immediately

after debugging is completed.

When a running fault occurs in the link aggregation group, run the following debugging

commands in the user view to check the debugging information, and locate and analyze the fault.

Procedurel Run the debugging trunk error command to enable the debugging of Eth-Trunk errors.

l Run the debugging trunk event command to enable the debugging of Eth-Trunk events.

l Run the debugging trunk lacp-pdu command to enable the debugging of LACP packets.

l Run the debugging trunk lagmsg command to enable the debugging of LACP protocol

messages.

l Run the debugging trunk msg command to enable the debugging of Eth-Trunk messages.

l Run the debugging trunk state-machine command to enable the debugging of Eth-Trunk

status machine.

l Run the debugging trunk updown command to enable the debugging of Eth-Trunk Upand Down messages.

l Run the debugging trunk command to enable the debugging of Eth-Trunk messages.

----End

1.5.3 Monitoring the Operating Status of the Link AggregationGroup

Context

During the routine maintenance, you can run the following commands in any view to check the

operating status of the link aggregation group.

Procedure

l Run the display eth-trunkcommand to display the status of the link aggregation group.

l Run the display lacp statistics eth-trunk[ trunk-id[ interfaceinterface-typeinterface-

number] ] command to display the statistics of sent and received LACP packets.

l Run the display trunkmembership eth-trunktrunk-idcommand to display the member


----End





18


30/254

1.6 Configuration Examples

This section provides configuration examples of link aggregation in manual load balancing mode

and in static LACP mode.

1.6.1 Example for Configuring Link Aggregation in Manual LoadBalancing Mode

Networking Requirements

As shown in Figure 1-4, the Router is connected to the broadband remote access server (BRAS)

through an Eth-Trunk. The link between the Router and BRAS must ensure high reliability, and

data traffic needs to be load balanced among the LPUs of the Router. To meet this requirement,

you need to configure an Eth-Trunk on the Router.

Figure 1-4Network diagram of link aggregation in manual load balancing mode

BRAS

Router

Eth-Trunk 1

DSLAM DSLAM

Eth0/0/1

VLAN 100-150

Eth

-Tr

unk

Eth-Trunk 1

Eth0/0/4Eth0/0/3

Eth0/0/2

VLAN 151-200

Configuration Roadmap

The configuration roadmap is as follows:

1. Create an Eth-Trunk.

2. Add member interfaces to the Eth-Trunk.





19


31/254

Data Preparation

To complete the configuration, you need the following data:

l Number of the Eth-Trunk

l Types and numbers of the member interfaces in the Eth-Trunk

Procedure

Step 1 Create an Eth-Trunk.

# Create Eth-Trunk 1.

system-view

[Huawei] sysname Router

[Router] interface eth-trunk 1[Router-Eth-Trunk1] quit

Step 2 Add member interfaces to the Eth-Trunk.# Add Ethernet 0/0/3 to Eth-Trunk 1.

[Router] interface ethernet 0/0/3[Router-Ethernet0/0/3] eth-trunk 1[Router-Ethernet0/0/3] quit

# Add Ethernet 0/0/4 to Eth-Trunk 1.

[Router] interface ethernet 0/0/4[Router-Ethernet0/0/4] eth-trunk 1

[Router-Ethernet0/0/4] quit

Step 3 Configure Eth-Trunk 1.

# Configure Eth-Trunk 1 to allow packets of VLANs 100 to 200 to pass through.

[Router] interface eth-trunk 1

[Router-Eth-Trunk1]port link-type trunk

[Router-Eth-Trunk1]port trunk allow-pass vlan 100 to 200[Router-Eth-Trunk1] quit

Step 4 Verify the configuration.

Run the display trunkmembership eth-trunktrunk-idcommand in any view to check whether

Eth-Trunk 1 is created and whether member interfaces are added.

[Router] display trunkmembership eth-trunk 1

Trunk ID: 1Used status: VALID

TYPE: ethernetWorking Mode :Normal

Number Of Ports in Trunk = 2Number Of UP Ports in Trunk = 2operate status: up

Interface Ethernet0/0/3, valid, operate up, weight=1,

Interface Ethernet0/0/4, valid, operate up, weight=1,

# Display the configuration of Eth-Trunk 1.

[Router] display eth-trunk 1

Eth-Trunk1's state information is:WorkingMode:NORMAL Hash arithmetic: According to SA-XOR-DA

Least Active-linknumber: 1 Max Bandwidth-affected-linknumber: 8

Operate status: up Number Of Up Port In Trunk: 2

--------------------------------------------------------------------------------PortName Status Weight





20


32/254

Ethernet0/0/3 Up 1

Ethernet0/0/4 Up 1

The preceding information indicates that Eth-Trunk 1 consists of member interfaces Ethernet

0/0/3 and Ethernet 0/0/4. The member interfaces are both in Up state.

----End

Configuration Files

Configuration file of the Router

#

sysname Router

#

interface Eth-Trunk1port link-type trunk

port trunk allow-pass vlan 100 to 200

#

interface Ethernet0/0/3

eth-trunk 1#

interface Ethernet0/0/4eth-trunk 1

#

return

1.6.2 Example for Configuring Link Aggregation in Static LACPMode


To increase the bandwidth and improve the connection reliability, you can configure a link

aggregation group on two directly connected routers, as shown in Figure 1-5. The requirements

are as follows:

l The link aggregation group contains three member links. Two links function as active links

to implement load balancing, and the other link functions as the backup link.

l When a fault occurs on an active link, the backup link replaces the faulty one to help ensure

uninterrupted data.

Figure 1-5Network diagram of link aggregation in static LACP mode

RouterA RouterBEth-Trunk 1 Eth-Trunk 1

Eth-Trunk

Eth 0/0/1Eth 0/0/2Eth 0/0/3

Eth 0/0/1Eth 0/0/2Eth 0/0/3

Active link

Backup link



1. Create an Eth-Trunk on each Router and configure the Eth-Trunk to work in static LACPmode.





21


33/254

2. Add member interfaces to the Eth-Trunk.

3. Set the system priority and determine the Actor.

4. Set the maximum number of active interfaces in the Eth-Trunk.

5. Set the priority of the interface and determine the active link.

Data Preparation


l Number of the link aggregation group

l System priority of RouterA

l Maximum number of active interfaces in the Eth-Trunk

l LACP priorities of the active interfaces

Procedure

Step 1 Create Eth-Trunk 1 and set the load balancing mode of the Eth-Trunk to static LACP mode.

# Configure RouterA.

system-view

[Huawei] sysname RouterA

[RouterA] interface eth-trunk 1[RouterA-Eth-Trunk1]mode lacp-static[RouterA-Eth-Trunk1] quit

# Configure RouterB.

system-view

[Huawei] sysname RouterB[RouterB] interface eth-trunk 1[RouterB-Eth-Trunk1]mode lacp-static[RouterB-Eth-Trunk1] quit

Step 2 Add member interfaces to the Eth-Trunk.

# Configure RouterA.

[RouterA] interface ethernet 0/0/1[RouterA-Ethernet0/0/1] eth-trunk 1

[RouterA-Ethernet0/0/1] quit

[RouterA] interface ethernet 0/0/2[RouterA-Ethernet0/0/2] eth-trunk 1[RouterA-Ethernet0/0/2] quit

[RouterA] interface ethernet 0/0/3[RouterA-Ethernet0/0/3] eth-trunk 1[RouterA-Ethernet0/0/3] quit

# Configure RouterB.

[RouterB] interface ethernet 0/0/1[RouterB-Ethernet0/0/1] eth-trunk 1

[RouterB-Ethernet0/0/1] quit

[RouterB] interface ethernet 0/0/2[RouterB-Ethernet0/0/2] eth-trunk 1[RouterB-Ethernet0/0/2] quit

[RouterB] interface ethernet 0/0/3

[RouterB-Ethernet0/0/3] eth-trunk 1[RouterB-Ethernet0/0/3] quit

Step 3 Set the system priority on RouterA to 100 so that RouterA becomes the Actor.





22


34/254

[RouterA] lacp priority 100

Step 4 Set maximum number of active interfaces in the Eth-Trunk on RouterA to 2.[RouterA] interface eth-trunk 1

[RouterA-Eth-Trunk1]max active-linknumber 2[RouterA-Eth-Trunk1] quit

Step 5 Set the priority of the interface and determine active links on RouterA.[RouterA] interface ethernet 0/0/1

[RouterA-Ethernet0/0/1] lacp priority 100

[RouterA-Ethernet0/0/1] quit[RouterA] interface ethernet 0/0/2[RouterA-Ethernet0/0/2] lacp priority 100

[RouterA-Ethernet0/0/2] quit


# Check information about the Eth-Trunk of the Routers and check whether the negotiation is

successful on the link.

[RouterA] display eth-trunk 1

Eth-Trunk1's state information is:

Local:LAG ID: 1 WorkingMode: STATICPreempt Delay: Disabled Hash arithmetic: According to SA-XOR-DA

System Priority: 100 System ID: 00e0-fca8-0417

Least Active-linknumber: 1 Max Active-linknumber: 2Operate status: Up Number Of Up Port In Trunk: 2

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

ActorPortName Status PortType PortPri PortNo PortKey PortStateWeight

Ethernet0/0/1 Selected 100M 100 6145 2865 11111100

1


Ethernet0/0/3 Unselect 100M 32768 6147 2865 11100000

1

Partner:

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

PartnerPortName SysPri SystemID PortPri PortNo PortKey PortState

Ethernet0/0/1 32768 00e0-fca6-7f85 32768 6145 2609 11111100Ethernet0/0/2 32768 00e0-fca6-7f85 32768 6146 2609 11111100

Ethernet0/0/3 32768 00e0-fca6-7f85 32768 6147 2609 11110000

[RouterB] display eth-trunk 1Eth-Trunk1's state information is:

Local:

LAG ID: 1 WorkingMode: STATICPreempt Delay: Disabled Hash arithmetic: According to SA-XOR-DA

System Priority: 32768 System ID: 00e0-fca6-7f85

Least Active-linknumber: 1 Max Active-linknumber: 8

Operate status: Up Number Of Up Port In Trunk: 2 ------------------------------------------------------------------------------

ActorPortName Status PortType PortPri PortNo PortKey PortState

Weight



1Ethernet0/0/3 Unselect 100M 32768 6147 2609 11100000

1

Partner: ------------------------------------------------------------------------------

PartnerPortName SysPri SystemID PortPri PortNo PortKey

PortState

Ethernet0/0/1 100 00e0-fca8-0417 100 6145 286511111100





23


35/254

Ethernet0/0/2 100 00e0-fca8-0417 100 6146 2865

11111100

Ethernet0/0/3 100 00e0-fca8-0417 32768 6147 286511110000

The preceding information shows that the system priority of RouterA is 100, which is higher

than the system priority of RouterB. Member interfaces Ethernet0/0/1 and Ethernet0/0/2 are

active interfaces and are in Selected state. Interface Ethernet0/0/3 is in Unselect state.

----End

Configuration Files

l Configuration file of RouterA

#

sysname RouterA

#

lacp priority 100

#interface Eth-Trunk1

mode lacp-staticmax active-linknumber 2

#


eth-trunk 1lacp priority 100

#


eth-trunk 1lacp priority 100

#


eth-trunk 1#

return

l Configuration file of RouterB

#sysname RouterB

#

interface Eth-Trunk1mode lacp-static

#


eth-trunk 1#


eth-trunk 1

#

interface Ethernet0/0/3eth-trunk 1

#return

1.6.3 Example for Configuring Layer 3 Link Aggregation


RouterA and RouterB are connected by two pairs of Layer 3 GE interfaces. To increase link

bandwidth and improve reliability, you can create an Eth-Trunk interface on each router and add

the Layer 3 GE interfaces to the Eth-Trunk interface.





24


36/254

Figure 1-6Network diagram of Layer 3 link aggregation

RouterA RouterBGE1/0/0

GE2/0/0

GE1/0/0

GE2/0/0

Eth-Trunk1

Eth-Trunk1

100.1.1.1/24

100.1.1.2/24



1. Create a Layer 3 Eth-Trunk interface on each device and configure an IP addresses for each

Eth-Trunk interface.

2. Add GE interfaces to the Eth-Trunk.

Data Preparation


l Numbers of Layer 3 GE interfaces between RouterA and RouterB

l IP address of the Eth-Trunk interface on RouterA

l IP address of the Eth-Trunk interface on RouterB

Procedure

Step 1 Configure RouterA. system-view[Huawei] sysname RouterA

# Create a Layer 3 Eth-Trunk interface (Eth-Trunk 1) and configure an IP addresses for the Eth-

Trunk interface.

[RouterA] interface eth-trunk 1[RouterA-Eth-Trunk1] undo portswitch[RouterA-Eth-Trunk1] ip address 100.1.1.1 24

[RouterA-Eth-Trunk1] quit

# Add GE1/0/0 and GE2/0/0 to Eth-Trunk 1.

[RouterA] interface gigabitethernet 1/0/0[RouterA-GigabitEthernet1/0/0] eth-trunk 1[RouterA-GigabitEthernet1/0/0] quit[RouterA] interface gigabitethernet 2/0/0

[RouterA-GigabitEthernet2/0/0] eth-trunk 1

[RouterA-GigabitEthernet2/0/0] quit

Step 2 Configure RouterB. system-view[Huawei] sysname RouterB

# Create a Layer 3 Eth-Trunk interface Eth-Trunk 1 and configure an IP addresses for the Eth-

Trunk interface.

[RouterB] interface eth-trunk 1

[RouterB-Eth-Trunk1] undo portswitch[RouterB-Eth-Trunk1] ip address 100.1.1.2 24





25


37/254

[RouterB-Eth-Trunk1] quit

# Add GE1/0/0 and GE2/0/0 to Eth-Trunk 1.

[RouterB] interface gigabitethernet 1/0/0[RouterB-GigabitEthernet1/0/0] eth-trunk 1

[RouterB-GigabitEthernet1/0/0] quit[RouterB] interface gigabitethernet 2/0/0

[RouterB-GigabitEthernet2/0/0] eth-trunk 1[RouterB-GigabitEthernet2/0/0] quit


Run the display interface eth-trunkcommand on RouterA or RouterB to verify that the Eth-

Trunk is in Up state.

Take the display on Router A as an example.

[RouterA] display interface eth-trunk 1Eth-Trunk1 current state : UP

Line protocol current state : UP

Description:HUAWEI, AR Series, Eth-Trunk1 InterfaceRoute Port, Hash arithmetic : According to SIP-XOR-DIP,The Maximum Transmit Unit

is 1500

Internet Address is 100.1.1.1/24

IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 00e0-fc09-9722Current system time: 2011-4-14 14:51:01

Input bandwidth utilization : 0.00%

Output bandwidth utilization : 0.00%

-----------------------------------------------------PortName Status Weight

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

GigabitEthernet1/0/0 UP 1

GigabitEthernet2/0/0 UP 1-----------------------------------------------------

The Number of Ports in Trunk : 2

The Number of UP Ports in Trunk : 2

The Eth-Trunk interfaces on RouterA and RouterB can ping each other.

[RouterA]ping -a 100.1.1.1 100.1.1.2 PING 100.1.1.2: 56 data bytes, press CTRL_C to break

Reply from 100.1.1.2: bytes=56 Sequence=1 ttl=255 time=31 ms Reply from 100.1.1.2: bytes=56 Sequence=2 ttl=255 time=31 ms

Reply from 100.1.1.2: bytes=56 Sequence=3 ttl=255 time=62 ms

Reply from 100.1.1.2: bytes=56 Sequence=4 ttl=255 time=62 ms

Reply from 100.1.1.2: bytes=56 Sequence=5 ttl=255 time=62 ms --- 100.1.1.2 pi

Configuration Guide - LAN(V200R002C00_02)

Documents

Transcript of Configuration Guide - LAN(V200R002C00_02)