H3C S5830V2 series Manuel utilisateur

H3C S5830V2 & S5820V2 Switch Series

IRF Configuration Guide

Hangzhou H3C Technologies Co., Ltd.

http://www.h3c.com

Software version: Release2108

Document version: 6W101-20120531

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

written consent of Hangzhou H3C Technologies Co., Ltd.

Trademarks

H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,

SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,

XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co.,

Ltd.

All other trademarks that may be mentioned in this manual are the property of their respective owners

Notice

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.

Preface

The H3C S5830V2 & S5820V2 documentation set includes 10 configuration guides, which describe the

software features for the H3C S5830V2 & S5820V2 Switch Series and guide you through the software

configuration procedures. These configuration guides also provide configuration examples to help you

apply software features to different network scenarios.

The IRF Configuration Guide describes how to use multiple switches to create an IRF fabric based on the

IRF technology. It covers planning the switch roles in the IRF fabric, connecting the IRF link, and detecting

and maintaining the IRF fabric.

This preface includes:

•Audience

•Conventions

•About the H3C S5830V2 & S5820V2 documentation set

•Obtaining documentation

•Technical support

•Documentation feedback

Audience

This documentation is intended for:

•Network planners

•Field technical support and servicing engineers

•Network administrators working with the S5830V2 & S5820V2 series

Conventions

This section describes the conventions used in this documentation set.

Command conventions

Convention Descri

tion

Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.

{ x | y | ... }

Braces enclose a set of required syntax choices separated by vertical bars, from which

you select one.

[ x | y | ... ]

Square brackets enclose a set of optional syntax choices separated by vertical bars, from

which you select one or none.

{ x | y | ... } *

Asterisk marked braces enclose a set of required syntax choices separated by vertical

bars, from which you select at least one.

[ x | y | ... ] *

Asterisk marked square brackets enclose optional syntax choices separated by vertical

bars, from which you select one choice, multiple choices, or none.

&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can

be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Descri

tion

< > Button names are inside angle brackets. For example, click <OK>.

[ ] Window names, menu items, data table and field names are inside square brackets. For

example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

Symbols

Convention Descri

tion

WARNING An alert that calls attention to important information that if not understood or followed can

result in personal injury.

CAUTION An alert that calls attention to important information that if not understood or followed can

result in data loss, data corruption, or damage to hardware or software.

IMPORTANT An alert that calls attention to essential information.

NOTE An alert that contains additional or supplementary information.

TIP An alert that provides helpful information.

Network topology icons

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports

Layer 2 forwarding and other Layer 2 features.

About the H3C S5830V2 & S5820V2

documentation set

The H3C S5830V2&S5820V2 documentation set includes:

Cate

Documents

Pur

oses

Hardware specifications

and installation

Compliance and safety

manual

Provides regulatory information and the safety

instructions that must be followed during installation.

Installation quick start Provides basic installation instructions.

Installation guide Provides a complete guide to hardware installation

and hardware specifications.

Fan assemblies

installation manual

Describes the appearance, specifications, and

installation and removal of hot-swappable fan

assemblies.

Power modules user

manual

Describes the appearance, specifications, and

installation and removal of hot-swappable power

modules.

Software configuration

Configuration guides Describe software features and configuration

procedures.

Command references Provide a quick reference to all available

commands.

Obtaining documentation

You can access the most up-to-date H3C product documentation on the World Wide Web

at http://www.h3c.com.

Click the links on the top navigation bar to obtain different categories of product documentation:

[Technical Support & Documents > Technical Documents] – Provides hardware installation, software

upgrading, and software feature configuration and maintenance documentation.

[Products & Solutions] – Provides information about products and technologies.

[Technical Support & Documents > Software Download] – Provides the documentation released with the

software version.

Technical support

servi[email protected]

http://www.h3c.com

Documentation feedback

You can e-mail your comments about product documentation to inf[email protected].

We appreciate your comments.

Contents

IRF overview ································································································································································· 1

Hardware compatibility····················································································································································1

IRF benefits·········································································································································································1

Application scenario·························································································································································1

Basic concepts···································································································································································2

IRF member roles ······················································································································································2

IRF member ID···························································································································································2

IRF port ······································································································································································2

Physical IRF port ·······················································································································································3

IRF domain ID ···························································································································································3

IRF split ······································································································································································4

IRF merge ··································································································································································4

Member priority························································································································································4

Interface naming conventions ··········································································································································4

File system naming conventions·······································································································································5

Configuration synchronization mechanism ····················································································································6

Master election··································································································································································6

IRF multi-active detection ··················································································································································7

Multi-active handling procedure ·····························································································································7

LACP MAD ································································································································································7

ARP MAD ··································································································································································8

ND MAD ···································································································································································9

Configuring IRF···························································································································································11

General restrictions and configuration guidelines······································································································ 11

Software requirements ·········································································································································· 11

IRF physical port restrictions and binding requirements···················································································· 11

IRF link redundancy··············································································································································· 11

MAD ······································································································································································· 11

Other configuration guidelines ···························································································································· 11

Setup and configuration task list ·································································································································· 12

Planning the IRF fabric setup········································································································································· 13

Assigning a member ID to each IRF member device ································································································· 13

Specifying a priority for each member device············································································································ 14

Connecting physical IRF ports······································································································································· 15

Binding physical ports to IRF ports ······························································································································· 15

Accessing the IRF fabric ················································································································································ 17

Configuring a member device description·················································································································· 17

Configuring IRF link load sharing mode······················································································································ 18

Configuring the global load sharing mode········································································································ 18

Configuring a port-specific load sharing mode ································································································· 18

Configuring IRF bridge MAC persistence···················································································································· 19

Enabling software auto-update for software image synchronization ······································································· 20

Setting the IRF link down report delay ························································································································· 20

Configuring MAD··························································································································································· 21

Configuring LACP MAD········································································································································ 21

Configuring ARP MAD·········································································································································· 22

Configuring ND MAD··········································································································································· 23

Excluding a port from the shutdown action upon detection of multi-active collision······································ 24

Recovering an IRF fabric ··············································································································································· 25

Displaying and maintaining an IRF fabric··················································································································· 26

Configuration examples ················································································································································ 27

LACP MAD-enabled IRF configuration example································································································· 27

ARP MAD-enabled IRF configuration example··································································································· 31

ND MAD-enabled IRF configuration example···································································································· 36

Index ···········································································································································································41

IRF overview

H3C Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple devices to

provide data center class availability and scalability. IRF virtualization technology offers processing

power, interaction, unified management, and uninterrupted maintenance of multiple devices.

This book describes IRF concepts and guides you through the IRF setup procedure.

Hardware compatibility

You can establish an IRF fabric that only comprises H3C S5820V2 series switches or S5830V2 series

switches, or establish a heterogeneous IRF fabric that comprises both H3C S5820V2 and S5830V2

switches.

IRF benefits

IRF delivers the following benefits:

•Simplified topology and easy management—An IRF fabric appears as one node and is accessible

at a single IP address on the network. You can use this IP address to log in at any member device

to manage all the members of the IRF fabric. In addition, you do not need to run the spanning tree

feature among the IRF members.

•1:N redundancy—In an IRF fabric, one member works as the master to manage and control the

entire IRF fabric, and all other members process services while backing up the master. When the

master fails, all the other member devices elect a new master from among them to take over without

interrupting services.

•IRF link aggregation—You can assign several physical links between neighboring members to their

IRF ports to create a load-balanced aggregate IRF connection with redundancy.

•Multichassis link aggregation—You can use the Ethernet link aggregation feature to aggregate the

physical links between the IRF fabric and its upstream or downstream devices across the IRF

members.

•Network scalability and resiliency—Processing capacity of an IRF fabric equals the total

processing capacities of all the members. You can increase ports, network bandwidth, and

processing capacity of an IRF fabric simply by adding member devices without changing the

network topology.

Application scenario

Figure 1 shows an IRF fabric that comprises two devices, which appear as a single node to the upper and

lower layer devices.

Figure 1 IRF application scenario

Basic concepts

This section describes the basic concepts that you might encounter when working with IRF.

IRF member roles

IRF uses two member roles: master and slave (called "subordinate" throughout the documentation).

When devices form an IRF fabric, they elect a master to manage and control the IRF fabric, and all the

other devices back up the master. When the master device fails, the other devices automatically elect a

new master from among them to take over. For more information about master election, see "Master

election."

IRF member ID

An IRF fabric uses member IDs to uniquely identify and manage its members. This member ID information

is included as the first part of interface numbers and file paths to uniquely identify interfaces and files in

an IRF fabric. For more information about interface and file path naming, see "Interface naming

conventions" and "File system naming conventions."

If two devices have the same IRF member ID, they cannot form an IRF fabric. If the IRF member ID of a

device has been used in an IRF fabric, the device cannot join the fabric.

IRF port

An IRF port is a logical interface for the connection between IRF member devices. Every IRF-capable

device supports two IRF ports. The IRF ports are named IRF-port n/1 and IRF-port n/2, where nis the

member ID of the switch. The two IRF ports are referred to as "IRF-port 1" and "IRF-port 2" in this book

for simplicity.

To use an IRF port, you must bind at least one physical port to it. The physical ports assigned to an IRF

port automatically form an aggregate IRF link. An IRF port goes down only if all its physical IRF ports are

down.

Physical IRF port

Physical IRF ports connect IRF member devices and must be bound to an IRF port. They forward the IRF

protocol packets between IRF member devices and the data packets that must travel across IRF member

devices.

For more information about physical ports that can be used for IRF links, see "IRF physical port restrictions

and binding requirements."

IRF domain ID

One IRF fabric forms one IRF domain. IRF uses IRF domain IDs to uniquely identify IRF fabrics and prevent

IRF fabrics from interfering with one another.

As shown in Figure 2, Device A and Device B form IRF fabric 1, and Device C and Device D form IRF

fabric 2. The fabrics have LACP MAD links between them. When a member device in one IRF fabric

receives an extended LACP packet for MAD detection, it looks at the domain ID in the packet to see

whether the packet is from the local IRF fabric or from a different IRF fabric. Then, the device can handle

the packet correctly.

Figure 2 A network that comprises two IRF domains

Device A Device B

IRF 1 (domain 10)

IRF link

Core network

IRF 2 (domain 20)

IRF link

Device C Device D

Access network

Autres manuels pour S5830V2 series

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels H3C Changer

H3C

H3C S9500E Series Manuel utilisateur

H3C

H3C S3100-8TP-SI Manuel utilisateur

H3C

H3C S6850 Series Manuel utilisateur

H3C

H3C S6520-EI Series Manuel utilisateur

H3C

H3C H3C S3600 Series Manuel utilisateur

H3C

H3C S5130-EI Series Manuel utilisateur

H3C

H3C S1850V2-EI Series Manuel utilisateur

H3C

H3C S10500X Series Manuel utilisateur

H3C

H3C S5500-EI series Manuel utilisateur

H3C

H3C S6850-56HF Manuel d'utilisation et d'entretien

H3C

H3C S6890-30HF Manuel d'utilisation et d'entretien

H3C

H3C 6W101 Manuel d'utilisation et d'entretien

H3C

H3C LS-S5600-26C-OVS Manuel utilisateur

H3C

H3C s5820x series Manuel utilisateur

H3C

H3C S6805 Series Manuel utilisateur

H3C

H3C s5820x series Manuel utilisateur

H3C

H3C S9500 Series Manuel utilisateur

H3C

H3C S9820-64H Manuel d'utilisation et d'entretien

H3C

H3C S12500 Series Manuel utilisateur

H3C

H3C S7500X-G Series Manuel utilisateur

H3C

H3C S9500 Series Manuel utilisateur

H3C

H3C S5800-EI Series Manuel utilisateur

H3C

H3C PSR600-54A-B Manuel utilisateur

H3C

H3C S5120-HI Series Manuel utilisateur

Manuels Changer populaires d'autres marques

URC

URC Total Control MFS-8 Manuel utilisateur

Azbil

Azbil HPQ-D11 Manuel utilisateur

Sony

Sony DFS-900M Manuel utilisateur

SICK

SICK i17S Manuel utilisateur

F&F

F&F SZR-277 Manuel utilisateur

Shure

Shure UAMS/BK Manuel utilisateur

Dräger

Dräger X-zone Switch Off Manuel utilisateur

Asco

Asco Joucomatic 349 Series Manuel utilisateur

BT Mini Hub Manuel utilisateur

D-Link

D-Link DES-1226G Manuel utilisateur

Johnson Controls

Johnson Controls FS80-C Manuel utilisateur

Alcatel-Lucent

Alcatel-Lucent 7450 ESS-12 Manuel utilisateur

MicroNet

MicroNet SP1200A Manuel utilisateur

Ruijie

Ruijie RG-PF2920 Series Manuel d'installation et d'exploitation

Altinex

Altinex DA1914SX Manuel utilisateur

MiLAN

MiLAN MIL-SM2401M Manuel utilisateur

RJM

RJM MASTERMIND PBC/6X Manuel utilisateur

Atlas

Atlas MMK-KVM8 Manuel utilisateur