H3C S5120-EI Series User manual

H3C S5120-EI Switch Series
IRF Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release 2220
Document version: 6W100-20130810

Copyright © 2013, 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 S5120-EI documentation set includes 10 configuration guides, which describe the software
features for the H3C S5120-EI Switch Series Release 2220, 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
•Added and modified features
•Conventions
•About the S5120-EI 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 S5120-EI series
Added and modified features
None
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.

Convention Descri
p
tion
[ 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.
Convention Descri
p
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
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 device.
About the S5120-EI documentation set
The H3C S5120-EI documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications
Marketing brochure Describe product specifications and benefits.
Technology white papers
Provide an in-depth description of software features
and technologies.
Hardware specifications
and installation
Compliance and safety
manual
CE DOCs
Provide regulatory information and the safety
instructions that must be followed during installation.
Quick start Guides you through initial installation and setup
procedures to help you quickly set up your device.
Installation guide Provides a complete guide to switch installation and
specifications.
RPS Ordering Information
for H3C Low-End Ethernet
Switches
Helps you order RPSs for switches that can work with
an RPS.
User manuals for RPSs Describe the specifications, installation, and
replacement of RPSs.
User manuals for interface
cards
Describe the specifications, installation, and
replacement of expansion interface cards.
H3C Low End Series
Ethernet Switches
Pluggable Modules
Manual
Describes the specifications of pluggable transceiver
modules.
Pluggable SFP[SFP+][XFP]
Transceiver Modules
Installation Guide
Describe the installation, and replacement of
SFP/SFP+/XFP transceiver modules.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Operations and
maintenance 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
servi[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [email protected].
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
Physical IRF port ·······················································································································································3
IRF domain ID ···························································································································································3
IRF split ······································································································································································3
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 ··················································································································································6
Multi-active handling procedure ·····························································································································6
LACP MAD ································································································································································7
ARP MAD ··································································································································································8
Configuring IRF···························································································································································10
General restrictions and configuration guidelines······································································································ 10
Software requirements ·········································································································································· 10
IRF link redundancy··············································································································································· 10
IRF physical port restrictions and cabling requirements ···················································································· 10
IRF port binding restrictions·································································································································· 10
MAD ······································································································································································· 11
FIPS mode requirement ········································································································································· 11
Other configuration guidelines ···························································································································· 11
Setup and configuration task list ·································································································································· 11
Planning the IRF fabric setup········································································································································· 12
Assigning a member ID to each IRF member switch ·································································································· 13
Specifying a priority for each member switch ············································································································ 13
Connecting physical IRF ports······································································································································· 14
Binding physical ports to IRF ports ······························································································································· 15
Accessing the IRF fabric ················································································································································ 16
Accessing the CLI of the master switch ··············································································································· 16
Accessing the CLI of a subordinate switch ········································································································· 17
Assigning an IRF domain ID to the IRF fabric·············································································································· 17
Configuring a member switch 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 system software image synchronization··························································· 19
Setting the IRF link down report delay ························································································································· 20
Configuring MAD··························································································································································· 21

ii
Configuring LACP MAD········································································································································ 21
Configuring ARP MAD·········································································································································· 22
Excluding a port from the shutdown action upon detection of multi-active collision······································ 23
Recovering an IRF fabric······································································································································· 24
Displaying and maintaining an IRF fabric··················································································································· 25
Configuration examples ················································································································································ 26
LACP MAD-enabled IRF configuration example································································································· 26
ARP MAD-enabled IRF configuration example··································································································· 28
Index ···········································································································································································31

1
IRF overview
The H3C Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple switches
to provide data center class availability and scalability. IRF virtualization technology offers processing
power, interaction, unified management, and uninterrupted maintenance of multiple switches.
This book describes IRF concepts and guides you through the IRF setup procedure.
Hardware compatibility
Among the S5120-EI switches, S5120-28C-EI, S5120-52C-EI, S5120-28C-PWR-EI, and
S5120-52C-PWR-EI support IRF. You can establish an IRF fabric among these S5120-EI switches, but must
purchase at least one 10-GE interface card listed in "IRF physical port restrictions and cabling
requirements."
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, and 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.
•Multiple-chassis 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 is formed by two switches, which appear as a single node to the upper
and lower layer devices.

2
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 switches form an IRF fabric, they elect a master to manage the IRF fabric, and all other switches
back up the master. When the master switch fails, the other switches 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 switches have the same IRF member ID, they cannot form an IRF 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.
IP network
IRF
IP network
IRF link Equal to
Master Subordinate

3
For two neighboring devices, their IRF physical links must be bound to IRF-port 1 on one device and to
IRF-port 2 on the other.
Physical IRF port
Physical IRF ports connect IRF member devices and must be bound to an IRF port. They forward IRF
protocol packets between IRF member devices and data packets that must travel across IRF member
devices.
For more information about physical ports that can be used for IRF links, see "General restrictions and
configuration guidelines."
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, Switch A and Switch B form IRF fabric 1, and Switch C and Switch D form IRF fabric
2. The fabrics have LACP MAD detection links between them. When a member switch 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 switch can handle
the packet correctly.
Figure 2 A network that comprises two IRF domains
IRF split
IRF split occurs when an IRF fabric breaks up into two or more IRF fabrics because of IRF link failures, as
shown in Figure 3. The split IRF fabrics operate with the same IP address and cause routing and

4
forwarding problems on the network. To quickly detect a multi-active collision, configure at least one
MAD mechanisms (see "IRF multi-active detection").
Figure 3 IRF split
IRF merge
IRF merge occurs when two split IRF fabrics reunite or when you configure and connect two independent
IRF fabrics to be one IRF fabric, as shown in Figure 4.
Figure 4 IRF merge
Member priority
Member priority determines the possibility of a member device to be elected the master. A member with
higher priority is more likely to be elected the master.
The default member priority is 1. You can change the member priority of a member device to affect the
master election result.
Interface naming conventions
An interface is named in the format of chassis-id/slot-number/port-index, where:
•slot-number—Represents the slot number of the interface card. This argument takes 0 for the fixed
ports on the front panel, and takes 1 and 2 for the two interface cards (from left to right) on the rear
panel.
•port-index—Port index depends on the number of ports available on the switch. To identify the
index of a port, look at its port index mark on the chassis.
For one example, on the standalone switch Sysname, GigabitEthernet 1/0/1 represents the first fixed
port on the front panel. Set its link type to trunk, as follows:
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port link-type trunk
For another example, on the IRF fabric Master, GigabitEthernet 3/0/1 represents the first fixed port on
the front panel of member switch 3. Set its link type to trunk, as follows:
<Master> system-view
IRF link
Device A Device B
Device A Device B
IRF 1 IRF 2 IRF
+=

5
[Master] interface gigabitethernet 3/0/1
[Master-GigabitEthernet3/0/1] port link-type trunk
File system naming conventions
On a standalone switch, you can use the name of storage device to access its file system. For more
information about storage device naming conventions, see Fundamentals Configuration Guide.
On an IRF fabric, you can use the name of storage device to access the file system of the master. To
access the file system of any other member switch, use the name in the
slotmember-ID#storage-device-name format. For example:
To access the test folder under the root directory of the Flash on the master switch:
<Master> mkdir test
...
%Created dir flash:/test.
<Master> dir
Directory of flash:/
0 -rw- 10105088 Apr 26 2000 13:44:57 test.app
1 -rw- 2445 Apr 26 2000 15:18:19 config.cfg
2 drw- - Jul 14 2008 15:20:35 test
30861 KB total (20961 KB free)
To create and access the test folder under the root directory of the Flash on member switch 3:
<Master> mkdir slot3#flash:/test
%Created dir slot3#flash:/test.
<Master> cd slot3#flash:/test
<Master> pwd
slot3#flash:/test
Or:
<Master> cd slot3#flash:/
<Master> mkdir test
%Created dir slot3#flash:/test.
To copy the file test.app on the master to the root directory of the Flash on member switch 3:
# Display the current working path. In this example, the current working path is the root directory of the
Flash on member switch 3.
<Master> pwd
slot3#flash:
# Change the current working path to the root directory of the Flash on the master switch.
<Master> cd flash:/
<Master> pwd
flash:
# Copy the file to member switch 3.
<Master> copy test.app slot3#flash:/
Copy flash:/test.app to slot3#flash:/test.app?[Y/N]:y
%Copy file flash:/test.app to slot3#flash:/test.app...Done.

6
Configuration synchronization mechanism
IRF uses a strict running-configuration synchronization mechanism so all chassis in an IRF fabric can work
as a single node, and after the master fails, other members can operate normally.
In an IRF fabric, all chassis get and run the running configuration of the master. Any configuration you
have made is propagated to all members.
When you execute the save [ safely ] [ backup | main ] [ force ] command or the save file-url all
command, the system saves the running configuration, as follows:
•If the configuration auto-update function (the slave auto-update config command) is enabled, saves
the configuration as the startup configuration on all member switches for the next startup.
•If the configuration auto-update function is disabled, saves the configuration as the startup
configuration on the master for the next startup.
By default, configuration auto-update is enabled.
For more information about configuration management, see Fundamentals Configuration Guide.
Master election
Master election is held each time the IRF fabric topology changes, for example, when the IRF fabric is
established, a new member device is plugged in, the master device fails or is removed, the IRF fabric
splits, or IRF fabrics merge.
Master election uses the following rules in descending order:
1. Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all member switches consider themselves as the master, and
this rule is skipped
2. Member with higher priority.
3. Member with the longest system uptime.
4. Member with the lowest bridge MAC address.
The IRF fabric is formed on election of the master.
During an IRF merge, the switches of the IRF fabric that fails the master election must reboot to re-join the
IRF fabric that wins the election.
After a master election, all subordinate switches reboot with the configuration on the master. Their
configuration files do not take effect.
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, including the same IP address. To avoid IP address collision and network problems, IRF
uses multi-active detection (MAD) mechanisms to detect the presence of multiple identical IRF fabrics,
handle collisions, and recover from faults.
Multi-active handling procedure
The multi-active handling procedure includes detection, collision handling and failure recovery.

7
Detection
The MAD implementation of the switch detects active IRF fabrics with the same Layer 3 global
configuration by extending the LACP or gratuitous ARP protocol.
These MAD mechanisms identify each IRF fabric with a domain ID and an active ID (the member ID of
the master). If multiple active IDs are detected in a domain, MAD determines that an IRF collision or split
has occurred.
You can use at least one of these mechanisms in an IRF fabric, depending on your network topology. For
a comparison of these MAD mechanisms, see "Configuring MAD."
Collision handling
When multiple identical active IRF fabrics are detected, MAD compares the member IDs of their masters.
If the master in one IRF fabric has the lowest member ID among all the masters, the members in the fabric
continue to operate in Active state and forward traffic. MAD sets all the other IRF fabrics in Recovery
(disabled) state and shuts down all their physical ports except the console ports, physical IRF ports, and
any ports you have specified with the mad exclude interface command.
Failure recovery
To merge two split IRF fabrics, first repair the failed IRF link and remove the IRF link failure.
If the IRF fabric in Recovery state fails before the failure is recovered, repair the failed IRF fabric and the
failed IRF link.
If the IRF fabric in Active state fails before the failure is recovered, first enable the IRF fabric in Recovery
state to take over the active IRF fabric and protect the services from being affected. After that, recover the
MAD failure.
LACP MAD
LACP MAD requires that every IRF member have a link with an intermediate device, and all these links
form a dynamic link aggregation group, as shown in Figure 5. In addition, the intermediate device must
be an H3C device that supports extended LACP for MAD.
The IRF member switches send extended LACPDUs with TLVs that convey the domain ID and the active ID
of the IRF fabric. The intermediate device transparently forwards the extended LACPDUs received from
one member switch to all the other member switches:
•If the domain IDs and the active IDs in the extended LACPDUs sent by all the member devices are
the same, the IRF fabric is integrated.
•If the extended LACPDUs convey the same domain ID but different active IDs, a split has occurred.
To handle this situation, LACP MAD sets the IRF fabric with higher active ID in Recovery state, and
shuts down all its physical ports but the console port, IRF ports, and any ports you have specified
with the mad exclude interface command. The IRF fabric with lower active ID is still in Active state
and forwards traffic.

8
Figure 5 LACP MAD application scenario
ARP MAD
ARP MAD detects multi-active collisions by using extended gratuitous ARP packets that convey the IRF
domain ID and the active ID.
You can set up ARP MAD links between neighbor IRF member devices, or between each IRF member
device and an intermediate device (see Figure 6). If an intermediate device is used, you must also run the
spanning tree feature between the IRF fabric and the intermediate device.

9
Figure 6 ARP MAD application scenario
Each IRF member compares the domain ID and the active ID in incoming extended gratuitous ARP
packets with its domain ID and active ID:
•If the domain IDs are different, the extended gratuitous ARP packet is from a different IRF fabric, and
the device does not continue to process the packet with the MAD mechanism.
•If the domain IDs are the same, the device compares the active IDs:
{If the active IDs are different, the IRF fabric has split.
{If the active IDs are the same, the IRF fabric is integrated.

10
Configuring IRF
Read the configuration restrictions and guidelines carefully when you connect and set up an IRF fabric.
General restrictions and configuration guidelines
This section describes the restrictions and configuration guidelines you must follow.
Software requirements
All IRF member switches must run the same system software image version.
IRF link redundancy
The switch supports up to two physical ports for an IRF port, and these two ports must be located on the
same interface card.
IRF physical port restrictions and cabling requirements
Candidate IRF physical ports include 10-GE ports on expansion interface cards. To use IRF, purchase at
least one interface card. The following are the interface cards available for IRF connections:
•1-port 10 GE XFP interface card
•2-port 10 GE XFP interface card
•Short-haul 2-port 10 GE CX4 interface card
•2-port 10 GE SFP+ interface card
•2-port 10 GE Ethernet interface card (LSPM1XGT2P)
For long-distance IRF connections, use XFP or SFP+ transceiver modules and fibers. For short-distance IRF
connections, use 10 GE Ethernet twisted pairs, CX4 or SFP+ cables. For more information about
transceiver modules available for an interface card, see the interface card user guide.
For more information about transceiver modules, see H3C Low End Series Ethernet Switches Pluggable
Modules Manual.
The SFP+ modules and SFP+ cables available for the switch are subject to change over time. For the most
up-to-date list of SFP+ modules and cables, consult your H3C sales representative or technical support
engineer.
IRF port binding restrictions
Facing the rear panel, make sure the physical ports bound to IRF port 1 is on the left of the physical ports
bound to IRF port 2.
Physical ports of an IRF port must be on the same interface card.

11
MAD
•Configure at least one MAD mechanism for prompt IRF split detection and IRF fabric recovery.
•If LACP MAD or ARP MAD runs between two IRF fabrics, assign each fabric a unique IRF domain
ID.
•To exclude a port from the shutdown action that is executed when an IRF fabric transits to the
Recovery state, use the mad exclude interface command. To bring up a port after the IRF fabric
transits to the Recovery state, you must use the mad restore command to activate the entire IRF fabric,
and not the undo shutdown command.
FIPS mode requirement
To form an IRF fabric, all member devices must use the same FIPS mode setting (configurable with the fips
mode enable command). For more information about FIPS mode, see Security Configuration Guide.
Other configuration guidelines
•Strictly follow the IRF fabric setup procedure described in "Setup and configuration task list" to plan
the IRF fabric, identify IRF physical ports, connect IRF member switches, and configure basic
settings.
•Assign each member a unique IRF member ID to make sure they can merge. You must reboot the
members to validate the IRF member ID settings.
•Assign the highest member priority to the device you want to use as the master.
•Before removing an interface card that has physical IRF ports in an IRF fabric, remove the IRF
connection cables, or use the shutdown command to shut down the IRF physical ports.
•If a subordinate switch uses the same next-startup configuration file name as the master switch, the
file might be overwritten depending on your configuration file management settings. To continue to
use the configuration file after removing the switch from the IRF fabric, back up the file before setting
up the IRF fabric.
•Save any configuration you have made to the startup configuration file before rebooting the IRF
member devices.
Setup and configuration task list
H3C recommends the basic IRF setup procedure in Figure 7. Perform the tasks in this figure on each
member switch. After the IRF fabric is set up, you can access the IRF fabric to manage its member
switches as if they were one switch.
Figure 7 Basic IRF setup flow chart

12
H3C recommends the following IRF fabric setup and configuration procedure:
Task Remarks
1. Planning the IRF fabric setup Required.
2. Assigning a member ID to each IRF member switch
Required.
Perform this task on each member
switch.
3. Specifying a priority for each member switch
Required.
Perform this task on each member
switch.
4. Connecting physical IRF ports Required.
5. Binding physical ports to IRF ports
Required.
Perform this task on each member
switch.
6. Accessing the IRF fabric:
{Accessing the CLI of the master switch
{Accessing the CLI of a subordinate switch
Login to the master's CLI is
required. You configure all
member switches at the master's
CLI.
From the master's CLI, you can log
in to any other member switch's
CLI to execute a limited set of
maintenance commands.
7. Assigning an IRF domain ID to the IRF fabric This task is required for ARP MAD
and LACP MAD.
8. Configuring a member switch description Optional.
9. Configuring IRF link load sharing mode:
{Configuring the global load sharing mode
{Configuring a port-specific load sharing mode
Optional.
10. Configuring IRF bridge MAC persistence Optional.
11. Enabling software auto-update for system software image
synchronization
Optional.
H3C recommends enabling
software auto-update to make sure
system software image
synchronization
12. Setting the IRF link down report delay Optional.
13. Configuring MAD:
{Configuring LACP MAD
{Configuring ARP MAD
{Excluding a port from the shutdown action upon detection of
multi-active collision
{Recovering an IRF fabric
Required.
MAD mechanisms are
independent of one another. You
can configure at least one MAD
mechanism for an IRF fabric.
Planning the IRF fabric setup
Consider the following items when you plan an IRF fabric: