H3C S5830V2 series User manual

H3C S5830V2 & S5820V2 Switch Series
IRF Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: Release2108
Document version: 6W101-20120531

Copyright © 2012, 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 S5830V2 & S5820V2 documentation set includes 10 configuration guides, which describe the
software features for the H3C S5830V2 & S5820V2 Switch Series and guide you through the software
configuration procedures. These configuration guides also provide configuration examples to help you
apply software features to different network scenarios.
The IRF Configuration Guide describes how to use multiple switches to create an IRF fabric based on the
IRF technology. It covers planning the switch roles in the IRF fabric, connecting the IRF link, and detecting
and maintaining the IRF fabric.
This preface includes:
•Audience
•Conventions
•About the H3C S5830V2 & S5820V2 documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the S5830V2 & S5820V2 series
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
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
< > 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.
About the H3C S5830V2 & S5820V2
documentation set
The H3C S5830V2&S5820V2 documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Hardware specifications
and installation
Compliance and safety
manual
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation quick start Provides basic installation instructions.
Installation guide Provides a complete guide to hardware installation

and hardware specifications.
Fan assemblies
installation manual
Describes the appearance, specifications, and
installation and removal of hot-swappable fan
assemblies.
Power modules user
manual
Describes the appearance, specifications, and
installation and removal of hot-swappable power
modules.
Software configuration
Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available
commands.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
servi[email protected]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to inf[email protected].
We appreciate your comments.

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 ······································································································································································4
IRF merge ··································································································································································4
Member priority························································································································································4
Interface naming conventions ··········································································································································4
File system naming conventions·······································································································································5
Configuration synchronization mechanism ····················································································································6
Master election··································································································································································6
IRF multi-active detection ··················································································································································7
Multi-active handling procedure ·····························································································································7
LACP MAD ································································································································································7
ARP MAD ··································································································································································8
ND MAD ···································································································································································9
Configuring IRF···························································································································································11
General restrictions and configuration guidelines······································································································ 11
Software requirements ·········································································································································· 11
IRF physical port restrictions and binding requirements···················································································· 11
IRF link redundancy··············································································································································· 11
MAD ······································································································································································· 11
Other configuration guidelines ···························································································································· 11
Setup and configuration task list ·································································································································· 12
Planning the IRF fabric setup········································································································································· 13
Assigning a member ID to each IRF member device ································································································· 13
Specifying a priority for each member device············································································································ 14
Connecting physical IRF ports······································································································································· 15
Binding physical ports to IRF ports ······························································································································· 15
Accessing the IRF fabric ················································································································································ 17
Configuring a member device description·················································································································· 17
Configuring IRF link load sharing mode······················································································································ 18
Configuring the global load sharing mode········································································································ 18
Configuring a port-specific load sharing mode ································································································· 18
Configuring IRF bridge MAC persistence···················································································································· 19
Enabling software auto-update for software image synchronization ······································································· 20
Setting the IRF link down report delay ························································································································· 20
Configuring MAD··························································································································································· 21
Configuring LACP MAD········································································································································ 21
Configuring ARP MAD·········································································································································· 22
Configuring ND MAD··········································································································································· 23
Excluding a port from the shutdown action upon detection of multi-active collision······································ 24

ii
Recovering an IRF fabric ··············································································································································· 25
Displaying and maintaining an IRF fabric··················································································································· 26
Configuration examples ················································································································································ 27
LACP MAD-enabled IRF configuration example································································································· 27
ARP MAD-enabled IRF configuration example··································································································· 31
ND MAD-enabled IRF configuration example···································································································· 36
Index ···········································································································································································41

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 that only comprises H3C S5820V2 series switches or S5830V2 series
switches, or establish a heterogeneous IRF fabric that comprises both H3C S5820V2 and S5830V2
switches.
IRF benefits
IRF delivers the following benefits:
•Simplified topology and easy management—An IRF fabric appears as one node and is accessible
at a single IP address on the network. You can use this IP address to log in at any member device
to manage all the members of the IRF fabric. In addition, you do not need to run the spanning tree
feature among the IRF members.
•1:N redundancy—In an IRF fabric, one member works as the master to manage and control the
entire IRF fabric, and all other members process services while backing up the master. When the
master fails, all the other member devices elect a new master from among them to take over without
interrupting services.
•IRF link aggregation—You can assign several physical links between neighboring members to their
IRF ports to create a load-balanced aggregate IRF connection with redundancy.
•Multichassis link aggregation—You can use the Ethernet link aggregation feature to aggregate the
physical links between the IRF fabric and its upstream or downstream devices across the IRF
members.
•Network scalability and resiliency—Processing capacity of an IRF fabric equals the total
processing capacities of all the members. You can increase ports, network bandwidth, and
processing capacity of an IRF fabric simply by adding member devices without changing the
network topology.
Application scenario
Figure 1 shows an IRF fabric that comprises two devices, which appear as a single node to the upper and
lower layer devices.

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 devices form an IRF fabric, they elect a master to manage and control the IRF fabric, and all the
other devices back up the master. When the master device fails, the other devices automatically elect a
new master from among them to take over. For more information about master election, see "Master
election."
IRF member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. This member ID information
is included as the first part of interface numbers and file paths to uniquely identify interfaces and files in
an IRF fabric. For more information about interface and file path naming, see "Interface naming
conventions" and "File system naming conventions."
If two devices have the same IRF member ID, they cannot form an IRF fabric. If the IRF member ID of a
device has been used in an IRF fabric, the device cannot join the fabric.
IRF port
An IRF port is a logical interface for the connection between IRF member devices. Every IRF-capable
device supports two IRF ports. The IRF ports are named IRF-port n/1 and IRF-port n/2, where nis the
member ID of the switch. The two IRF ports are referred to as "IRF-port 1" and "IRF-port 2" in this book
for simplicity.

3
To use an IRF port, you must bind at least one physical port to it. The physical ports assigned to an IRF
port automatically form an aggregate IRF link. An IRF port goes down only if all its physical IRF ports are
down.
Physical IRF port
Physical IRF ports connect IRF member devices and must be bound to an IRF port. They forward the IRF
protocol packets between IRF member devices and the data packets that must travel across IRF member
devices.
For more information about physical ports that can be used for IRF links, see "IRF physical port restrictions
and binding requirements."
IRF domain ID
One IRF fabric forms one IRF domain. IRF uses IRF domain IDs to uniquely identify IRF fabrics and prevent
IRF fabrics from interfering with one another.
As shown in Figure 2, Device A and Device B form IRF fabric 1, and Device C and Device D form IRF
fabric 2. The fabrics have LACP MAD links between them. When a member device in one IRF fabric
receives an extended LACP packet for MAD detection, it looks at the domain ID in the packet to see
whether the packet is from the local IRF fabric or from a different IRF fabric. Then, the device can handle
the packet correctly.
Figure 2 A network that comprises two IRF domains
Device A Device B
IRF 1 (domain 10)
IRF link
Core network
IRF 2 (domain 20)
IRF link
Device C Device D
Access network

4
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
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 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
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 chassis-id/slot-number/port-index format, where:
•chassis-id—IRF member ID of the switch. This argument defaults to 1.
•slot-number—Represents the slot number of the interface card. This argument always takes 0 on
S5820V2 and S5830V2 switches.
•port-index—Port index depends on the number of ports available on the device. To identify the
index of a port, look at its port index mark on the chassis.
For one example, on the standalone switch Sysname, Ten-GigabitEthernet 1/0/1 represents the first port
on the device. Set its link type to trunk, as follows:
<Sysname> system-view
[Sysname] interface ten-gigabitethernet 1/0/1
IRF link
Device A Device B
Device A Device B
IRF 1 IRF 2 IRF
+=

5
[Sysname-Ten-GigabitEthernet1/0/1] port link-type trunk
For another example, on the IRF fabric Master, Ten-GigabitEthernet 3/0/1 represents the first fixed port
on member device 3. Set its link type to trunk, as follows:
<Master> system-view
[Master] interface ten-gigabitethernet 3/0/1
[Master-Ten-GigabitEthernet3/0/1] port link-type trunk
File system naming conventions
On a standalone device, you can use its storage device name 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 device, 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> dir
Directory of flash:
0 -rw- 32841728 Jan 01 2011 00:35:36 5800-B23Feature.ipe
1 -rw- 39981056 Jan 01 2011 00:49:53 5800.ipe
2 -rw- 40442880 Jan 01 2011 07:11:59 5800b32.ipe
3 -rw- 32173056 Jan 01 2011 01:20:00 5800v1.ipe
4 -rw- 39080960 Jan 01 2011 01:57:39 S5820V2_5830V2-T2201.ipe
5 drw- - Jan 01 2011 00:00:30 diagfile
6 -rw- 218 Jan 01 2011 01:52:48 ifindex.dat
7 drw- - Jan 01 2000 02:34:20 logfile
8 -rw- 9119744 Jan 01 2011 00:37:47 s5820v2-r2108p02.bin
9 -rw- 30605312 Jan 01 2011 00:26:12 s5820v2-t2204.bin
10 drw- - Jan 01 2000 00:00:06 seclog
11 -rw- 4137 Jan 01 2011 07:16:32 startup.cfg
12 -rw- 4028 Jan 01 2011 01:52:17 startup.cfg_bak
13 -rw- 36912 Jan 01 2011 07:16:33 startup.mdb
14 drw- - Jan 01 2011 07:00:29 test
15 drw- - Jan 01 2011 00:01:01 versionInfo
524288 KB total (443044 KB free)
To create and access the test folder under the root directory of the Flash on member device 3:
<Master> mkdir slot3#flash:/test
Directory slot3#flash:/test created.
<Master> cd slot3#flash:/test
<Master> pwd
slot3#flash:/test
Or:
<Master> cd slot3#flash:/
<Master> mkdir test
Directory slot3#flash:/test created.
To copy the file test.ipe on the master to the root directory of the Flash on member device 3:

6
# Display the current working path. In this example, the current working path is the root directory of the
Flash on member device 3.
<Master> pwd
slot3#flash:
# Change the current working path to the root directory of the Flash on the master device:
<Master> cd flash:/
<Master> pwd
flash:
# Copy the file to member device 3.
<Master> copy test.ipe slot3#flash:/
Copy flash:/test.ipe to slot3#flash:/test.ipe?[Y/N]:y
Start to copy flash:/test.ipe to slot3#flash:/test.ipe...Done.
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.
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 members consider themselves as the master, and this rule
is skipped.
2. Member with higher priority.
3. Member with the longest system uptime.
Two members are considered starting up at the same time if the difference between their startup
times is equal to or less than 10 minutes. For these members, the next tiebreaker applies.
4. Member with the lowest bridge MAC address.
The IRF fabric is formed on election of the master.
During an IRF merge, the members of the IRF fabric that fails the master election must reboot to re-join the
IRF fabric that wins the election. The reboot can be automatically performed or manually performed.
After a master election, all subordinate members initialize and reboot with the configuration on the
master, and their original configuration, even if has been saved, is removed.

7
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.
Detection
The device's MAD implementation detects active IRF fabrics with the same Layer 3 global configuration
by extending the LACP, ARP, or IPv6 ND 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 but 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, enable the IRF fabric in Recovery state
to take over the active IRF fabric before recovering the failed IRF fabric and IRF link.
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. The intermediate device must be an H3C
device that supports extended LACP for MAD.
The IRF member devices 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 device 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 ports, IRF ports, and any ports you have specified

8
with the mad exclude interface command. The IRF fabric with lower active ID is still in Active state
and forwards traffic.
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 more commonly, 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.
Device
Master Subordinate
IRF
Internet
Customer
premise
network
IRF link
Common traffic path
LACP MAD traffic path
LACP-enabled dynamic
link aggregation
LACP-enabled dynamic
link aggregation

9
Figure 6 ARP MAD application scenario
Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its
domain ID and active ID:
•If the domain IDs are different, the extended 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.
ND MAD
ND MAD detects multi-active collisions by using the IPv6 ND protocol's NS packets that convey the IRF
domain ID and the active ID.
You can set up ND MAD links between neighbor IRF member devices or more commonly, between each
IRF member device and an intermediate device (see Figure 7). If an intermediate device is used, you must
also run the spanning tree protocol between the IRF fabric and the intermediate device.
Device
Master Subordinate
IRF
Internet
Customer
premise
network
IRF link
Common traffic path
Extended ARP traffic path
STP domain (all devices
must run the spanning
tree feature)

10
Figure 7 ND MAD application scenario
Each IRF member device compares the domain ID and the active ID in incoming NS packets with its
domain ID and active ID:
•If the domain IDs are different, the NS 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.
Device
Master Subordinate
IRF
Internet
Customer
premise
network
IRF link
Common traffic path
Extended ND traffic path
STP domain (all devices
must run the spanning
tree feature)

11
Configuring IRF
Read the configuration restrictions and guidelines carefully when you connect and set up an IRF fabric.
General restrictions and configuration guidelines
Software requirements
All IRF member switches must run the same software image version.
IRF physical port restrictions and binding requirements
All SFP+ and QSFP+ ports on the H3C S5820V2 switches and all SFP+ ports on the H3C S5830V2
switches can be used as IRF physical ports.
SFP+ ports provide 10-GE connections and 40-GE ports provide 40-GE connections.
SFP+ ports are grouped by their numbers in order, starting from the one numbered 1. Each group
contains four ports. Ports in the same group must be used for the same purpose. If you use one port in a
group as an IRF physical port, no other ports in the group can be used for any other purposes.
When you connect two neighboring IRF members, connect the physical ports of IRF-port 1 on one
member to the physical ports of IRF-port 2 on the other.
On a physical port bound to an IRF port, you can execute only the shutdown and description commands.
For more information about these commands, see Interface Command Reference.
IRF link redundancy
You can bind up to four physical ports to an IRF port for link redundancy.
MAD
•Configure at least one MAD mechanism for prompt detection and recovery of IRF partition.
•If LACP MAD, ARP MAD, or ND 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,
rather than using the undo shutdown command.
Other configuration guidelines
•If a subordinate device uses the same next-startup configuration file name as the master device, 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.

12
•Assign each member a unique IRF member ID to make sure that 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.
•Assign the IRF fabric a unique IRF domain ID in a multi-IRF network.
•Save any configuration you have made to the startup configuration file before you reboot the IRF
member devices.
Setup and configuration task list
H3C recommends the basic IRF setup procedure in Figure 8. Perform the tasks in this figure on each
member device. After the IRF fabric is set up, you can access the IRF fabric to manage its member devices
as if they were one device.
Figure 8 Basic IRF setup flow chart
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 device
Required.
Perform this task on each member
device.
3. Specifying a priority for each member device
Required.
Perform this task on each member
device.
4. Connecting physical IRF ports Required.
5. Binding physical ports to IRF ports
Required.
Perform this task on each member
switch.
When you complete IRF port
binding and activation on all IRF
member devices, the IRF fabric is
formed.

13
Task Remarks
6. Accessing the IRF fabric
Required.
When you log in to the IRF fabric,
you are placed at the master's CLI,
where you complete subsequent
IRF settings and configure other
features for the member devices as
if they were one device.
7. Configuring a member device description This task is required for ARP MAD
and LACP MAD.
8. Configuring IRF link load sharing mode:
{Configuring the global load sharing mode
{Configuring a port-specific load sharing mode
Optional.
9. Configuring IRF bridge MAC persistence Optional.
10. Enabling software auto-update for software image synchronization
Optional. H3C recommends
enabling software auto-update to
make sure system software image
synchronization
11. Setting the IRF link down report delay Optional.
12. Configuring MAD:
{Configuring LACP MAD
{Configuring ARP MAD
{Configuring ND MAD
{Excluding a port from the shutdown action upon detection of
multi-active collision
Required.
MAD mechanisms are
independent of one another. You
can configure at least one MAD
mechanism for an IRF fabric.
13. Recovering an IRF fabric Optional.
Planning the IRF fabric setup
Consider the following items when you plan an IRF fabric:
•Hardware compatibility and restrictions
•IRF fabric size
•Master switch
•IRF physical ports
•Member ID and priority assignment scheme
•Fabric topology and cabling scheme
For more information about hardware and cabling, see the switch installation guide.
Assigning a member ID to each IRF member device