H3C S5830V2 series User manual

H3C S5830V2 & S5820V2 Switch Series
IRF Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 23xx
Document version: 6W102-20150315

Copyright © 2014-2015, Hangzhou H3C Technologies Co., Ltd. and its licensors
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 Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , H3CS, H3CIE, H3CNE, Aolynk, , H3Care, , IRF, NetPilot, Netflow,
SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM 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 16 configuration guides. These guides
describe the software features for the H3C S5830V2 & S5820V2 Switch Series and guide you through
the software configuration procedures. These guides also provide configuration examples to help you
apply software features to different network scenarios.
The IRF Configuration Guide describes how to set up an IRF fabric of multiple switches, including:
•Plan the switch roles in the IRF fabric.
•Connect the IRF links.
•Detect IRF splits and maintain the IRF fabric.
This preface includes:
•Audience
•Added and modified features
•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.
Added and modified features
Release 2311P05 contains the following changes to IRF over Release 2311P04:
Confi
g
uration
g
uide Added and modified features
IRF Added features: Configuring BFD MAD on management Ethernet
ports.
Release 2311P04 contains the following changes to IRF over Release 2310:
Confi
g
uration
g
uide Added and modified features
IRF Modified features: The maximum number of IRF physical interfaces was
increased from four to eight for an IRF port.

Release 2310 does not contain any changes to IRF over Release 2307.
Release 2307 does not contain any changes to IRF over Release 2210.
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
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
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
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.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your switch.
About the H3C S5830V2 & S5820V2
documentation set
The H3C S5830V2 & S5820V2 documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications Marketing brochures Describe product specifications and benefits.
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.
H3C LSWM1HFANSC &
LSWM1HFANSCB Fan
Assemblies Installation
Provides the physical views, specifications, and
installation procedures, and removal procedures for
hot-swappable fan assemblies.
H3C LSVM1FANSC &
LSVM1FANSCB Fan
Assemblies Installation
Provides physical views, specifications, and
installation procedures, and removal procedures for
hot-swappable fan assemblies.
H3C SFP/SFP+/XFP
Transceiver Modules
Installation Guide
Describes the installation and replacement
procedures for SFP/SFP+/XFP transceiver modules.
H3C LSVM1AC650 &
LSVM1DC650 Power
Modules User Manual
Provides the physical views, specifications, and
installation procedures, and removal procedures for
the LSVM1AC650 and LSVM1DC650 power
modules.
H3C LSVM1AC300 &
LSVM1DC300 Power
Modules User Manual
Provides the physical views, specifications,
installation procedures, and removal procedures for
the LSVM1AC300 and LSVM1DC300 power
modules.

Cate
g
or
y
Documents Pur
p
oses
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Operations and
maintenance
MIB Companion Describes the MIBs for the software release.
Release notes Provide information about the product release and
software upgrading.
Obtaining documentation
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, as well as solutions.
[Technical Support & Documents > Software Download]—Provides the documentation released with the
software version.
Technical support
servic[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
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
IRF physical interface ···············································································································································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 ································································································································································8
BFD MAD ··································································································································································9
ARP MAD ······························································································································································· 10
ND MAD ································································································································································ 11
Configuring IRF···························································································································································13
General restrictions and configuration guidelines······································································································ 13
Software requirements ·········································································································································· 13
IRF physical interface restrictions and binding requirements············································································ 13
IRF link redundancy··············································································································································· 14
Multichassis link aggregation ······························································································································ 14
MAD and IRF domain restrictions························································································································ 14
Licensing requirements·········································································································································· 15
Other configuration guidelines ···························································································································· 15
Setup and configuration task list ·································································································································· 15
Planning the IRF fabric setup········································································································································· 17
Assigning a member ID to each IRF member device ································································································· 17
Specifying a priority for each member device············································································································ 18
Connecting IRF physical interfaces······························································································································· 18
Binding physical interfaces to IRF ports ······················································································································· 19
Accessing the IRF fabric ················································································································································ 21
Configuring a member device description·················································································································· 21
Configuring IRF link load sharing mode······················································································································ 22
Configuring the global load sharing mode········································································································ 22
Configuring a port-specific load sharing mode ································································································· 22
Configuring IRF bridge MAC persistence···················································································································· 23
Enabling software auto-update for software image synchronization ······································································· 24
Configuration prerequisites ·································································································································· 24
Configuration procedure ······································································································································ 25
Setting the IRF link down report delay ························································································································· 25

ii
Configuring MAD··························································································································································· 25
Configuring LACP MAD········································································································································ 27
Configuring BFD MAD·········································································································································· 28
Configuring ARP MAD·········································································································································· 29
Configuring ND MAD··········································································································································· 30
Excluding a port from the shutdown action upon detection of multi-active collision······································ 31
Recovering an IRF fabric ··············································································································································· 32
Displaying and maintaining an IRF fabric··················································································································· 33
Configuration examples ················································································································································ 34
LACP MAD-enabled IRF configuration example································································································· 34
BFD MAD-enabled IRF configuration example··································································································· 38
ARP MAD-enabled IRF configuration example··································································································· 43
ND MAD-enabled IRF configuration example···································································································· 47
Index ···········································································································································································123H53

1
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 by using S5820V2 switches, S5830V2 switches, or switches from both
series.
IRF benefits
IRF provides 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. All the 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 has two devices, which appear as a single node to the upper-layer and
lower-layer devices.

2
Figure 1 IRF application scenario
Basic concepts
This section describes the basic concepts you might encounter when you work with IRF.
IRF member roles
IRF uses two member roles: master and standby (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 elect a new master
automatically. 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 device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book.