H3C S9500E Series User manual

H3C S9500E Series Routing Switches
IRF Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S9500E-CMW520-R1725
Document version: 6W170-20111118

Copyright © 2011, 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, , 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 S9500E documentation set includes 14 configuration guides, which describe the software
features for the H3C S9500E Series Routing Switches 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 the Intelligent Resilient Framework (IRF) technology developed by
H3C. It covers the basic concepts and working process of an IRF, and describes how to configure and
access an IRF virtual device.
This preface includes:
•Audience
•Conventions
•About the H3C S9500E 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 S9500E series
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.

Convention Descri
p
tion
[ 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 S9500E documentation set
The H3C S9500E documentation set includes:
Cate
g
or
y
Documents
Pur
p
oses
Product description and Marketing brochures Describe product specifications and benefits.

Cate
g
or
y
Documents
Pur
p
oses
specifications
Technology white papers
Provide an in-depth description of software features
and technologies.
Card datasheets Describe card specifications, features, and
standards.
Hardware specifications
and installation
Regulatory compliance
and safety information
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
H3C N68 Cabinet
Installation and Remodel
Introduction
Guides you through installing and remodeling H3C
N68 cabinets.
H3C Pluggable SFP
[SFP+][XFP] Transceiver
Modules Installation
Guide
Guides you through installing SFP/SFP+/XFP
transceiver modules.
H3C High-End Network
Products Hot-Swappable
Module Manual
Describes the hot-swappable modules available for
the H3C high-end network products, their external
views, and specifications.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Operations and
maintenance
System log messages Explains the system log messages.
Trap messages Explains the trap messages.
MIB Companion Describes the MIBs for the software release.
Release notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
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, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.

Technical support
cu[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

Contents
Configuring IRF····························································································································································· 1
IRF overview·······································································································································································1
Benefits ······································································································································································1
Application scenario················································································································································1
Basic concepts···································································································································································2
Establishment, operation, and maintenance of an IRF fabric·······················································································4
Connecting the IRF member switches·····················································································································5
Topology collection ··················································································································································6
Master election ·························································································································································7
IRF fabric management and maintenance ·············································································································7
IRF fabric configuration task list·······································································································································8
Configuration prerequisites ·····································································································································9
Pre-configuration·······················································································································································9
Non pre-configuration··········································································································································· 10
Pre-configuring an IRF member switch in standalone mode······················································································ 11
Binding a physical port to an IRF port ················································································································ 12
Setting a member ID for the switch······················································································································ 13
Specifying a priority for the switch······················································································································ 13
Enabling enhanced IRF mode······································································································································· 13
Configuration guidelines ······································································································································ 13
Configuration procedure ······································································································································ 14
Saving the running configuration to the configuration file to be used at the next system startup ························· 14
Switching operating mode············································································································································ 14
IRF modes······························································································································································· 14
Configuration file auto-conversion······················································································································· 15
Switching the operating mode to IRF mode ······································································································· 15
Accessing an IRF fabric ················································································································································· 15
Accessing the active MPU of an IRF fabric········································································································· 15
Accessing a standby MPU of an IRF fabric ········································································································ 15
Configuring IRF member switches in IRF mode··········································································································· 16
Specifying an IRF domain ID for an IRF fabric··································································································· 16
Configuring IRF ports ············································································································································ 17
Setting a member ID for a switch ························································································································ 19
Specifying a priority for a member switch ········································································································· 19
Configuring a description for a member switch ································································································ 19
Specifying the preservation time of the bridge MAC address ········································································· 20
Enabling auto reboot for IRF fabric merge ········································································································· 21
Enabling automatic boot file updating················································································································ 21
Setting the IRF link down report delay ················································································································ 22
Enabling IRF link failure detection and auto-recovery ······················································································· 23
Configuring MAD detection ································································································································· 23
Performing IRF configuration fast recovery·················································································································· 33
Configuration prerequisites ·································································································································· 33
Configuration procedures····································································································································· 33
Displaying and maintaining an IRF fabric··················································································································· 34
IRF fabric configuration examples································································································································ 34
LACP MAD detection-enabled configuration example (non pre-configuration mode)··································· 35
BFD MAD detection-enabled IRF configuration example (pre-configuration mode)······································· 38
ARP MAD detection-enabled IRF configuration example (pre-configuration mode)······································· 40
i

ii
Switching the operating mode of IRF member switches from IRF to standalone ············································ 43
Enhanced IRF mode configuration example (four switches forming an IRF fabric) ········································ 45
Index ············································································································································································· 1

1
Configuring IRF
IRF overview
You can use the H3C Intelligent Resilient Framework (IRF) technology to connect and virtualize multiple
switches into a virtual switch called an “IRF fabric” to provide data center class availability and
scalability. IRF virtualization technology offers processing power, interaction, unified management, and
uninterrupted maintenance of multiple switches.
NOTE:
Up to four switches of the same series can form an IRF fabric.
Benefits
IRF delivers the following benefits:
•Simplified topology and streamlined management. An IRF fabric appears as one node on the
network. You can log in at any member switch to manage all members of the IRF fabric.
•Network scalability and resiliency. You can increase ports and network bandwidth of an IRF fabric
simply by adding member switches.
•High availability and reliability. The member switches in an IRF fabric work in redundant mode.
One member switch works as the master to manage and maintain the entire IRF fabric, and other
member switches process services and provide backup. If the master fails, another member switch
is elected as the new master to prevent service interruption. You can perform link aggregation not
only for IRF links but also for physical links between the IRF fabric and its upper or lower layer
devices for link redundancy.
Application scenario
Figure 1 shows an IRF fabric that comprises two switches, which appear as a single node to the upper
and lower layer switches.

2
Figure 1 IRF application scenario
Basic concepts
Figure 2 IRF implementation schematic diagram
IRF link
After an IRF is
formed.
Suppose
Device A is the
master.
Master
(MemberID=1)
Slave
(MemberID=2)
Active MPU of the
member
Device A
(MemberID=1) Device B
(MemberID=2)
XGE1/3/0/1
Physical IRF
port
XGE2/3/0/1
Physical IRF
port
IRF-Port2 IRF-Port1
Service
interface
Service
interface
IRF
Standby MPU of the
member
Active MPU of the
member
Standby MPU of the
member
Active MPU of the IRF
Standby MPU of the
IRF
Standby MPU of the
IRF
Standby MPU of the
IRF

3
Device A and Device B in Figure 2 form an IRF fabric which has four MPUs (one active and three standby)
and two interface cards. The IRF fabric manages both the physical and software resources of Device A
and Device B.
This section uses Figure 2 to explain the concepts that you might encounter when working with IRF.
Operating mode
A switch can operate in either of the following two modes:
•Standalone mode—The switch cannot form an IRF fabric with other switches.
•IRF mode—The switch can connect with other switches to form an IRF fabric.
You can change the operating mode of a switch at the command line interface (CLI).
IRF member switch roles
IRF uses two member switch roles: master and slave.
When switches form an IRF fabric, they elect a master to manage the IRF fabric, and the other switches
back up the master. When the master switch fails, another switch is elect as the new master to avoid
service interruption. For more information about master election, see “Master election.”
Roles of MPUs
Each member switch in an IRF fabric has one or two MPUs (also called the supervision engines) and they
play different roles, as follows:
Role Description
Local active main processing unit (MPU) The supervisor engine that manages the local switch.
Local standby MPU The supervisor engine backs up the local active MPU,
and takes over when the local active MPU fails.
Global active MPU
The active MPU of the master switch. You configure and
manage the entire IRF at the command line of the global
active MPU.
Global standby MPU All MPUs except the active MPU of the master switch are
global standby MPUs.
IRF member ID
You assign the active MPU of each member switch a unique ID to identify the switch in the IRF fabric. This
ID is called the “IRF member ID” of the switch. By default, the standby MPU of a switch is automatically
assigned the same ID as the active MPU. You can change the standby MPU ID of a member switch to
quickly recover IRF configuration for a switch that has only one MPU as described in “Performing IRF
configuration fast recovery.”
IRF port
An IRF port is a logical interface for the internal connection between IRF member switches. Each IRF
member switch has two IRF ports: IRF-port 1 and IRF-port 2. An IRF port is activated when you bind a
physical port to it.
NOTE:
In standalone mode, the IRF ports are named IRF-port1 and IRF-port2. In IRF mode, the IRF ports are
named IRF-port
n /1 and IRF-port n /2, where n is the member ID of the switch. In this manual, IRF-port1
and IRF-port2 are used.

4
Physical IRF port
Physical IRF ports are physical ports bound to an IRF port. They connect IRF member switches and
forward IRF protocol packets and data packets between IRF member switches.
Physical IRF ports can be electrical ports or optical ports.
IRF partition
IRF partition occurs when an IRF fabric splits into two or more IRF fabrics because of IRF link failures, as
shown in Figure 3. The partitioned IRF fabrics operate with the same IP address and cause routing and
forwarding problems on the network.
Figure 3 IRF partition
NOTE:
W
hen you unplug the card where a physical IRF port resides, IRF partition might occur. Therefore, when
you unplug this kind of card, make sure that there are at least two physical IRF ports in UP state, and they
are not on the same card.
IRF merge
IRF merge occurs when two partitioned IRF fabrics re-unite or when you configure and connect two
independent IRF fabrics to be one IRF fabric, as shown in Figure 4.
Figure 4 IRF merge
IRF link
XGE1/3/0/1 XGE2/3/0/1
Device A Device B
Device A Device B
IRF 1 IRF 2 IRF
+=
Member priority
Member priority determines the role of a member switch during the master election process. A member
with a higher priority is more likely to be a master.
The priority of a switch defaults to 1. You can modify the priority at the CLI.
Establishment, operation, and maintenance of an
IRF fabric
IRF fabric management involves these stages: Connecting the IRF member switches, Topology
collection, Master election, and IRF fabric management and maintenance.

5
Connecting the IRF member switches
Connection medium
To establish an IRF fabric, physically connect the physical IRF ports of member switches. The connection
medium depends on the physical IRF ports supported by the switch.
•If you use electrical interfaces as physical IRF ports, use network cables (cross-over or
straight-through) to connect them. This connection mode improves the usage of the available
resources (electrical interfaces are used to forward data traffic when not bound to any IRF port, and
used to forward packets between member switches when bound to IRF ports), and saves the cost as
well (without the need to purchase optical module used for IRF connection).
•If you use optical ports as physical IRF ports, use fibers to connect them. This connection mode
connects physical switches located very far at a distance and provides flexible application.
NOTE:
A
g
ood practice is to use 10G optical Ethernet interfaces as physical IRF ports.
Connecting requirements
As shown in Figure 5, connect the physical ports bound to IRF-Port1 on one switch to the physical ports
bound to the IRF-Port2 on its neighbor switch.
Figure 5 IRF fabric physical connection
NOTE:
A
n IRF port can be bound to a maximum of 12 physical ports to increase the bandwidth and reliability of
the IRF port.
IRF topologies
IRF member switches typically adopt a daisy chain topology or ring topology, as shown in Figure 6.
•The daisy chain topology is mainly used in a network where member switches are distributedly
located.
•The ring topology is more reliable than the daisy chain topology. In a daisy chained IRF fabric, the
failure of one link can cause the IRF fabric to partition into two independent IRF fabrics; the failure
of a link in a ring topology result in a daisy chain connection, not affecting IRF services.
If two IRF member switches are far away from each other (for example, if they are in different cities), you
can use a relay device to connect them, as shown in Figure 7.

6
Figure 6 IRF connections
Figure 7 IRF connections
Topology collection
Each member exchanges IRF hello packets with neighbors to collect the topology data, including IRF port
connection states, member IDs, priorities, and bridge MAC addresses.
Each member is managed by its active MPU, which records its known topology information locally. At the
startup of a member switch, the active MPU of the member switch records topology information of the
member switch. When an IRF port of the member switch is up, the active MPU of the switch performs the
following operations:
1. Periodically sends its known topology information from this port.
2. When receiving the topology information from the directly connected neighbor, it updates the
local topology information.
3. If a standby MPU is available on the member switch, the active MPU synchronizes its recorded
topology information to the standby MPU to ensure consistent topology information on both
boards.

7
After all member switches have obtained topology information (known as topology convergence), the
IRF fabric enters the role election stage.
Master election
Master election is held each time the topology changes, for example, when the IRF fabric is established,
a new member switch is plugged in, the master switch fails or is removed, or the partitioned IRF fabrics
merge.
The master is elected based on the following rules in descending order:
•The current master, even if a new member has a higher priority. (When an IRF fabric is being
formed, all member switches consider themselves as the master, and this rule is skipped)
•The switch with a higher priority.
•The switch with the longest system up-time. (The member switches exchange system up-time in the
IRF hello packets)
•The switch with the lowest bridge MAC address.
The IRF fabric is formed on election of the master.
NOTE:
•During an IRF merge, an IRF election is held, the switches of the IRF fabric that fails the master election
must reboot to re-join the IRF fabric that wins the election. Then, the switch reboots with the execution of
a command.
•After a master election, all slave member switches initialize and reboot with the configuration on the
master, and their original configuration, even if has been saved, will be lost.
IRF fabric management and maintenance
After the IRF fabric is established, you can access the master from any member switch to manage all the
resources of the member switches.
Member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. For example, if an interface
on a switch that operates in standalone mode is named GigabitEthernet 3/0/1. After the switch joins an
IRF fabric, it receives a member ID of 2. The name of the interface changes to GigabitEthernet 2/3/0/1.
Member ID is also used in file management. For example, when the switch operates in standalone mode,
the path of a file was slot1#flash:/test.cfg. After the switch joins an IRF fabric, the path changes to
chassis1#slot1#flash:/test.cfg, which indicates that the file is saved on the board in slot 1 of member
switch 1. Therefore, member IDs must be unique.
NOTE:
Member IDs and priorities are confi
g
ured per switch. If you set the member ID or priority for a member
switch, the configuration is first saved on the active MPU of the member switch, and then synchronized to
the standby MPU. If the active MPU and standby MPU of a member switch keep different member IDs, the
member ID kept by the active MPU is applied. For example, if the switch with the member ID of 2 has onl
y
one active MPU, after you plug in a standby MPU that keeps a member ID of 1, the member ID of the
switch is still 2 and the member ID kept on the standby MPU is synchronized to 2.

8
IRF fabric topology maintenance
As soon as a member switch is down or an IRF link is down, its neighbor switches broadcast the leaving
of the switch to other members. When a member switch receives the leave message, it looks up its IRF
topology database to determine whether the leaving switch is the master. If yes, the member switch starts
a master election and updates its IRF topology database. If the leaving switch is not a master, the member
switch directly updates its IRF topology database.
NOTE:
A
n IRF port
g
oes down only when all its physical IRF ports are down.
IRF multi-active detection
An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3
configurations, such as the same IP address. To avoid IP address collisions and network problems, IRF
uses the multi-active detection (MAD) mechanism to detect the presence of multiple identical IRF fabrics
and handle collisions. MAD provides the following functions:
1. Detection
MAD detects multiple identical active IRF devices with the same global configuration by extending the
Link Aggregation Control Protocol (LACP), the Bidirectional Forwarding Detection (BFD) protocol, or the
Gratuitous Address Resolution (ARP) protocol. For more information, see ”Configuring MAD detection.”
2. Collision handling
If multiple identical active IRF fabrics are detected, only the IRF fabric that has the lowest master ID can
operate in active state and forward traffic normally. MAD sets all other IRF fabrics in recovery state
(disabled) and shuts down all physical ports but the console and physical IRF ports and other ports you
have specified with the mad exclude interface command.
3. Failure recovery
An IRF link failure triggers IRF fabric partition and causes multi-active collision. In this case, repair the
failed IRF link to make the collided IRF fabrics merge into one and recover the failure. If the IRF fabric in
recovery state fails before the failure is recovered, repair both the failed IRF fabric and the failed IRF link,
and then the collided IRF fabrics can merge into one and the failure is recovered. If the IRF fabric in active
state fails before the failure is recovered, enable the IRF fabric in recovery state at the CLI to make it take
over the active IRF fabric and protect the services from being affected. Then, recover the MAD failure.
NOTE:
For information about LACP, see
Layer 2—LAN Switching Configuration Guide . For information about
BFD, see
High Availability Configuration Guide . For information about gratuitous ARP, see Layer 3—IP
Services Configuration Guide .
IRF fabric configuration task list
There are two IRF fabric configuration methods, pre-configuration and non pre-configuration. The
pre-configuration method is recommended because only one switch reboot is needed to complete the
configuration.

9
Configuration prerequisites
•Configure a higher priority for a member switch that features good performance and rich functions
so that the switch can be elected as the master when two switches form an IRF fabric for the first
time.
•If you use a physical port of a switch as a physical IRF port when the switch operates in standalone
mode, the services configured on the port will become ineffective after the switch switches to IRF
mode. Make preparations in advance to ensure services are not affected.
•Before establishing an IRF fabric, make sure that the system working mode of the member switches
is the same. If not, the IRF fabric cannot be established. For more information about the system
working mode, see Fundamentals Configuration Guide.
•The member switches of an IRF fabric must work in the same rule match mode. This means that you
must configure the acl ipv6 enable command, or the acl ipv6 disable command on the switches. For
more information about the acl ipv6 command, see ACL and QoS Configuration Guide.
•The member switches of an IRF fabric must be configured with the same VPN label processing mode.
This means that you must configure the vpn popgo command or the undo vpn popgo command on
the switches. For more information about the vpn popgo command, see ACL and MPLS
Configuration Guide.
•Before establishing an IRF fabric, check that enhanced IRF mode is enabled on all member switches
or disabled on all member switches. If enhanced IRF mode is enabled on some member switches
but disabled on the others, the IRF fabric cannot be established. For more information about
enhanced IRF mode, see “Enabling enhanced IRF mode.”
Pre-configuration
Pre-configuration allows you to configure IRF ports, member IDs, and member priority on a switch
operating in standalone mode. These configurations do not affect the running of the switch, and take
effect only when the switch switches to IRF mode. Adopt this method to configure an IRF fabric before
establishing it. To enable switches operating in standalone mode to form an IRF fabric, you must
pre-configure their member IDs and switch their operating modes. If you configure the priority for a
switch as the greatest value when the switch operates in standalone mode, this switch can win the master
election and become the master after multiple switches form an IRF fabric for the first time. If you
configure IRF ports for member switches operating in standalone mode, they can directly form an IRF
fabric with other switches after their operating mode is switched to IRF. Pre-configurations enable the
member switches to reboot only once to establish an IRF fabric.
Complete these tasks to configure an IRF fabric in pre-configuration mode:
Task Remarks
Pre-configuring an
IRF member switch
in standalone mode
Binding a physical port to an IRF
port Required
Setting a member ID for the switch
Required
Specifying a priority for the switch
Optional
Enabling enhanced IRF mode
Optional
Perform this task to use three or four switches to
form an IRF fabric.
Saving the running configuration to the configuration file
to be used at the next system startup Required

10
Task Remarks
Physically connecting two switches operating in
standalone mode
Required
Optical Ethernet interfaces and electrical Ethernet
interfaces (except combo ports) can be used as
physical IRF ports.
Be sure to connect the switches according to the
requirements described in the section “Connecting
requirements” Otherwise, they cannot form an IRF
fabric.
Switching operating mode Required
Activating the physical IRF ports of the member switches
by using the undo shutdown command Required
Accessing an IRF
fabric
Accessing the active MPU of an
IRF fabric Required
Accessing a standby MPU of an
IRF fabric Optional
Configuring IRF
member switches in
IRF mode
Configuring a description for a
member switch Optional
Specifying the preservation time
of the bridge MAC address Optional
Enabling auto reboot for IRF
fabric merge Optional
Enabling automatic boot file
updating Optional
Setting the IRF link down report
delay Optional
Enabling IRF link failure detection
and auto-recovery Optional
Configuring MAD detection Optional
Performing IRF configuration fast
recovery Optional
Non pre-configuration
Non pre-configuration allows you to configure the member ID for a switch operating in standalone mode,
switch the operating mode to IRF mode, and then configure parameters such as a new member ID and
member priority (during the whole process, the member switches may reboot for multiple times). Use this
method when you need to modify the running configuration. For example,
•Change the member ID of a switch to a specified value.
NOTE:
Changing member ID might cause ineffectiveness of some member ID-related configurations.
•Modify the priority of a member switch to make sure it is elected as the master in the next master
election.

11
•Modify the binding between an IRF port and physical IRF ports (such as deleting a binding or
adding a new binding), and the configuration of IRF ports may affect the operation of the switch
(for example, causing IRF partition, or IRF merge).
Complete these tasks to configure an IRF fabric in non pre-configuration mode:
Task Remarks
Setting a member ID for the switch Required
Enabling enhanced IRF mode
Optional
Perform this task to use three or four
switches to form an IRF fabric.
Saving the running configuration to the configuration file to be used
at the next system startup Required
Switching operating mode Required
Accessing an IRF
fabric
Accessing the active MPU of an IRF fabric Required
Accessing a standby MPU of an IRF fabric Optional
Configuring IRF
member switches in
IRF mode
Configuring IRF ports Required
Setting a member ID for the switch Optional
Specifying a priority for a member switch Optional
Physically connecting two switches
operating in standalone mode
Required
Be sure to connect the switches
according to the requirements
described in the section “Connecting
requirements.” Otherwise, they cannot
form an IRF fabric.
Configuring a description for a member
switch Required
Specifying the preservation time of the
bridge MAC address Optional
Enabling auto reboot for IRF fabric merge Optional
Enabling automatic boot file updating Optional
Setting the IRF link down report delay Optional
Enabling IRF link failure detection and
auto-recovery Optional
Configuring MAD detection Optional
Performing IRF configuration fast recovery Optional
Pre-configuring an IRF member switch in standalone
mode
You can configure the IRF ports, member ID, and member priority for the switch when it is operating in
standalone mode. Configurations take effect when the operating mode of the switch switches to IRF.

12
Binding a physical port to an IRF port
To establish IRF connection, you must assign the physical ports that connect IRF member switches to IRF
ports.
An IRF port can be bound to a maximum of 12 physical ports and is known as an aggregate IRF port,
which can be realized by repeatedly executing the port group interface command. This allows two
switches to be connected through 12 Ethernet cables or fibers to increase the bandwidth and reliability
of the IRF port.
To bind a physical port to an IRF port:
To do… Use the command… Remarks
Enter system view system-view —
Enter physical IRF port view interface interface-type
interface-number —
Shut down the port shutdown
Required when two member
switches have more than one
pair of physical IRF ports
connected.
Return to system view quit —
Create an IRF port and enter IRF
port view when the switch
operates in standalone mode (if
the IRF port is already created,
this command enters IRF port
view)
irf-port port-number
Required
By default, no IRF port is created
on the switch.
Bind a physical IRF port to the IRF
port
port group interface interface-type
interface-number
Required
By default, an IRF port is not
bound to any physical IRF port.
Verify the binding configuration
display irf configuration [ |{ begin |
exclude | include }
regular-expression ]
Optional
Make sure that the binding is as
expected. If the binding is
incorrect, IRF cabling errors may
occur, resulting in IRF
establishment failure.
CAUTION:
•A combo port cannot be bound to an IRF port. For information about combo ports, see
Interface
Configuration Guide.
•Save the configurations to the startup configuration file so that the configurations can take effect when
the switch is switched to IRF mode.
•In standalone mode, binding a physical port to an IRF port does not affect the running configuration of
the port. However, when the operating mode changes to IRF mode, the default configuration of the
physical IRF port restores, and you can only execute the shutdown and description commands on the
physical port. For more information about the shutdown and description commands, see Interface
Command Reference
.