HP FlexFabric 12900 series User manual

HP FlexFabric 12900 Switch Series
IRF
Configuration Guide
Part number: 5998-6237
Software version: Release 1135
Document version:6W100-20150427

Legal and notice information
© Copyright 2015 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.

1
Contents
IRF overview ································································································································································· 3
Hardware compatibility····················································································································································3
IRF benefits·········································································································································································3
Application scenario·························································································································································3
Network topologies ··························································································································································4
Basic concepts···································································································································································4
Operating mode·······················································································································································5
IRF member roles ······················································································································································5
IRF member ID···························································································································································6
MPU roles··································································································································································6
IRF port ······································································································································································6
IRF physical interface ···············································································································································7
IRF domain ID ···························································································································································7
IRF split ······································································································································································7
IRF merge ··································································································································································8
Member priority························································································································································8
Master election··································································································································································8
IRF connection error notification······································································································································9
IRF multi-active detection ··················································································································································9
Multi-active handling procedure ·····························································································································9
LACP MAD ····························································································································································· 10
BFD MAD ······························································································································································· 11
Configuring IRF···························································································································································13
General restrictions and configuration guidelines······································································································ 13
Software requirements ·········································································································································· 13
IRF size and member ID restrictions ···················································································································· 13
MPU requirements ················································································································································· 13
IRF physical interface restrictions························································································································· 13
Connecting IRF ports ············································································································································· 14
IRF link redundancy··············································································································································· 14
Multichassis link aggregation ······························································································································ 14
Feature and IRF mode compatibility···················································································································· 14
MAD and IRF domain restrictions························································································································ 15
IRF merge restrictions ············································································································································ 15
Configuration backup ··········································································································································· 15
Setup and configuration task list ·································································································································· 15
Planning the IRF fabric setup········································································································································· 16
Preconfiguring IRF member devices in standalone mode ·························································································· 16
Assigning a member ID to each IRF member device························································································· 16
Specifying a priority for each member device··································································································· 17
Binding physical interfaces to IRF ports ·············································································································· 17
Saving configuration to the next-startup configuration file ························································································ 18
Connecting IRF physical interfaces······························································································································· 18
Setting the operating mode to IRF mode ····················································································································· 19
Accessing the IRF fabric ················································································································································ 20
Configuring IRF member devices in IRF mode ············································································································ 20
Assigning an IRF domain ID to the IRF fabric····································································································· 20
Changing the member ID of a device················································································································· 21

2
Changing the priority of a member device ········································································································ 21
Adding physical interfaces to an IRF port··········································································································· 21
Enabling IRF auto-merge······································································································································· 23
Configuring a member device description ········································································································· 24
Configuring IRF link load sharing mode ············································································································· 24
Configuring IRF bridge MAC persistence··········································································································· 25
Enabling software auto-update for system software image synchronization ·················································· 26
Setting the IRF link down report delay ················································································································ 27
Configuring MAD·················································································································································· 27
Displaying and maintaining an IRF fabric··················································································································· 33
Configuration examples ················································································································································ 33
LACP MAD-enabled IRF configuration example································································································· 33
BFD MAD-enabled IRF configuration example··································································································· 36
Configuration example for restoring standalone mode ···················································································· 39
Support and other resources ·····································································································································42
Contacting HP ································································································································································ 42
Subscription service ·············································································································································· 42
Related information························································································································································ 42
Documents······························································································································································ 42
Websites································································································································································· 42
Conventions ···································································································································································· 43
Index ···········································································································································································45

3
IRF overview
The HP 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
An HP 12900 switch can form an IRF fabric only with devices of the same model.
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 acts as the master to manage and control the entire
IRF fabric. 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.
•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 has two devices, which appear as a single node to the upper-layer and
lower-layer devices.

4
Figure 1 IRF application scenario
Network topologies
The HP 12900 IRF fabric only supports the daisy-chain topology. For information about connecting IRF
member devices, see "Connecting IRF physical interfaces."
Basic concepts
This section uses Figure 2 to describe the basic concepts that you might encounter when you work with
IRF.

5
Figure 2 Two-chassis IRF fabric implementation schematic diagram
In this figure, Device A and Device B form a two-chassis IRF fabric. The fabric has four MPUs (one active
and three standbys), and two times the number of interface cards that a single device provides. The IRF
fabric manages the physical and software resources of Device A and Device B in a centralized manner.
Operating mode
The device operates in one of the following modes:
•Standalone mode—The device cannot form an IRF fabric with other devices.
•IRF mode—The device can form an IRF fabric with other devices.
IRF member roles
IRF uses two member roles: master and standby (called subordinate throughout the documentation).
When devices form an IRF fabric, they elect a master to manage the IRF fabric, and all other devices back
up the master. When the master device fails, the other devices automatically elect a new master. For more
information about master election, see "Master election."
IRF link
An IRF
fabric is
formed.
Master
(Member ID=1)
Subordinate
(Member ID=2)
Active MPU
Device A
(Member ID=1) Device B
(Member ID=2)
IRF physical
interfaces IRF physical
interfaces
IRF-port 2 IRF-port 1
Network
interfaces
Network
interfaces
IRF
Standby MPU
Active MPU
Standby MPU
IRF’s master MPU
IRF’s standby MPU
IRF’s standby MPU
IRF’s standby MPU

6
IRF member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. 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.
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 example, after you assign a device with member ID 2 to an IRF
fabric, the name of interface FortyGigE 3/0/1 changes to FortyGigE 2/3/0/1. The file path changes
from slot16#flash:/test.cfg to chassis1#slot16#flash:/test.cfg.
MPU roles
Each IRF member device has one or two MPUs. The following are MPU roles:
Role Descri
p
tion
Master MPU Active MPU of the master device. It is also called the global active MPU. You
configure and manage the entire IRF fabric at the CLI of the global active MPU.
Active MPU
Active MPU on each member device. An active MPU performs the following
operations:
•Manages the local device, including synchronizing configuration with the
local standby MPU, processing protocol packets, and creating and
maintaining route entries.
•Handles IRF-related events, such as master election and topology collection.
Standby MPU
For the master MPU, all other MPUs are standby MPUs, including active MPUs
on subordinate devices.
If a member device has two MPUs, the MPU backing up the local active MPU is
the local standby MPU from the perspective of the member device.
IRF port
An IRF port is a logical interface for the connection between IRF member devices. Every IRF-capable
device supports two IRF ports.
In standalone mode, the IRF ports are named IRF-port 1 and IRF-port 2.
In IRF mode, the IRF ports are named IRF-port n/1 and IRF-port n/2, where nis the member ID of the
device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book.
To use an IRF port, you must bind a minimum of one physical interface to it. The physical interfaces
assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down only if all its IRF
physical interfaces are down.
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.

7
IRF physical interface
IRF physical interfaces 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.
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 3, IRF fabric 1 contains Device A and Device B, and IRF fabric 2 contains Device C
and Device D. Both fabrics use the LACP aggregate links between them for MAD. When a member
device receives an extended LACPDU for MAD, it checks the domain ID to see whether the packet is from
the local IRF fabric. Then, the device can handle the packet correctly.
Figure 3 A network that contains two IRF domains
IRF split
IRF split occurs when an IRF fabric breaks up into multiple IRF fabrics because of IRF link failures, as
shown in Figure 4. The split IRF fabrics operate with the same IP address. IRF split causes routing and
forwarding problems on the network. To quickly detect a multi-active collision, configure one of the MAD
mechanisms (see "IRF multi-active detection").
Device A Device B
IRF 1 (domain 10)
IRF link
Core network
IRF 2 (domain 20)
IRF link
Device C Device D
Access network

8
Figure 4 IRF split
IRF merge
IRF merge occurs when two split IRF fabrics reunite or when two independent IRF fabrics are united, as
shown in Figure 5.
Figure 5 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.
Master election
Master election occurs each time the IRF fabric topology changes in the following situations:
•The IRF fabric is established.
•The master device fails or is removed.
•The IRF fabric splits.
•Independent IRF fabrics merge.
NOTE:
Master election does not occur when two split IRF fabrics merge.
Master election selects a master in descending order:
1. Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all member devices consider themselves as the master. This
rule is skipped.
2. Member with higher priority.
3. Member with the longest system uptime.

9
Two members are considered to start up at the same time if their startup time difference is equal to
or less than 10 minutes. For these members, the next tiebreaker applies.
4. Member with the lowest member ID.
For a new IRF fabric, the subordinate devices must reboot to complete the setup after the master election.
For an IRF merge, devices must reboot if they are in the IRF fabric that fails the master election. The reboot
can be performed automatically or manually (see "Enabling IRF auto-merge").
After a master election, all subordinate devices reboot with the configuration on the master. The
configuration files of the subordinate members are retained, but the files do not take effect in the IRF
fabric. A subordinate member uses its own startup configuration file only after it is removed from the IRF
fabric.
IRF connection error notification
The device generates error messages when its IRF physical interfaces are connected to non-IRF physical
interfaces. The error messages use the form of "The port port can't receive irf pkt and has been changed
to inactive status, please check." The port argument represents the interface name of an IRF physical
interface that connects to a non-IRF physical interface.
The messages help you identify incorrect IRF connections to avoid issues including cross-chassis packet
loss and IRF split.
The error messages might be falsely generated when the IRF fabric is unstable. For example, the
messages might occur during an IRF setup, reboot, or IRF port binding modification process. If the IRF
connections are correct, the messages will not occur after the IRF fabric completes the process.
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 MAD implementation of this device detects active IRF fabrics with the same Layer 3 global
configuration by extending the LACP or BFD 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.
IMPORTANT:
LACP MAD handles collisions differently than BFD MAD. To avoid conflicts, do not enable LACP MAD
together with BFD MAD.

10
For a comparison of the MAD mechanisms, see "Configuring MAD."
Collision handling
When MAD detects a multi-active collision, it allows one IRF fabric to forward traffic and sets all the other
IRF fabrics to the Recovery state. The Recovery-state IRF fabrics are inactive and cannot forward traffic.
LACP MAD uses the following process to handle a multi-active collision:
1. Compares the number of members in each fabric.
2. Allows the fabric that has the most members to forward traffic, and sets all other fabrics to the
Recovery state.
3. Compares the member IDs of their masters if all IRF fabrics have the same number of members.
4. Allows the IRF fabric that has the lowest numbered master to forward traffic, and sets all other
fabrics to the Recovery (inactive) state.
5. Shuts down all physical network ports in the Recovery-state fabrics except for the following ports:
{IRF physical interfaces.
{Ports you have specified with the mad exclude interface command.
In contrast, BFD MAD does not compare the number of members in fabrics. BFD MAD uses the following
process to handle a multi-active collision:
1. Allows the IRF fabric that has the lowest numbered master to forward traffic.
2. Sets all other fabrics to the Recovery state.
3. Takes the same action on the network ports in Recovery-state fabrics as LACP MAD.
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 active IRF fabric fails before the failure is recovered, enable the inactive IRF fabric to take over
the active IRF fabric. Then, recover the MAD failure.
LACP MAD
As shown in Figure 6, LACP MAD has the following requirements:
•Every IRF member must have a link with an intermediate device.
•All the links form a dynamic link aggregation group.
•The intermediate device must be an HP device that supports extended LACP for MAD.
The IRF member devices send extended LACPDUs with a domain ID and an active ID. The intermediate
device transparently forwards the extended LACPDUs received from one member device to all the other
member devices.
•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.
LACP MAD handles this situation as described in "Collision handling."

11
Figure 6 LACP MAD scenario
BFD MAD
BFD MAD can work with or without intermediate devices. Figure 7 shows a typical BFD MAD application
scenario.
To use BFD MAD:
•Set up dedicated BFD MAD link between each pair of IRF members or between each IRF member
and the intermediate device. Do not use the BFD MAD links for any other purpose.
•Assign the ports connected by BFD MAD links to the same VLAN.
•Create a VLAN interface for the VLAN, and assign a MAD IP address to each member on the VLAN
interface.
NOTE:
The MAD IP addresses identify the member devices and must belong to the same subnet.
With BFD MAD, the master tries to establish BFD sessions with the other member devices by using its
MAD IP address as the source IP address.
•If the IRF fabric is integrated, only the MAD IP address of the master is effective, and the master
cannot establish a BFD session with any other member. If you execute the display bfd session
command, the state of the BFD sessions is Down.
Intermediate device
Master
IRF
Internet
Customer
premise
network
IRF link
Common traffic path
LACP MAD traffic path
LACP-enabled dynamic
link aggregation
Subordinate
LACP-enabled dynamic
link aggregation

12
•When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect, and the
two masters can establish a BFD session. If you use the display bfd session command, the state of
the BFD session between the two devices is Up.
Figure 7 BFD MAD scenario
Device
Master Subordinate
IRF
Internet
Customer
premise
network
IRF link
Link aggregation
BFD MAD link
VLAN 2
192.168.1.2/24 VLAN 2
192.168.1.3/24

13
Configuring IRF
General restrictions and configuration guidelines
For a successful IRF setup, follow the restrictions and guidelines in this section and the setup procedure
in "Setup and configuration task list."
Software requirements
All IRF member devices must run the same system software image version.
IRF size and member ID restrictions
To ensure a successful IRF setup, follow these IRF size and member ID restrictions:
•An HP 12900 IRF fabric can have up to two chassis.
•The member ID assigned to a member chassis must be 1 or 2.
MPU requirements
Each IRF member device must have a minimum of one MPU.
IRF physical interface restrictions
Use the following physical interfaces for IRF links:
•10 -GE p or ts.
•40-GE ports.
•100 - GE por ts.
Selecting transceiver modules and cables
When you select transceiver modules and cables, follow these restrictions and guidelines:
•Use SFP+, QSFP+, or CXP transceiver modules and fibers for a long-distance connection.
•Use SFP+, QSFP+, or CXP DAC cables to connect 10-GE, 40-GE, or 100-GE ports for a
short-distance connection.
•The transceiver modules at the two ends of an IRF link must be the same type. For more information
about transceiver modules, see the device installation guide.
40-GE port restrictions
You can use a 40-GE QSFP+ port as an IRF physical interface, or use the using tengige command to split
a QSFP+ port into four 10-GE breakout interfaces.
When you use the 10-GE breakout interfaces of a QSFP+ port for IRF links, follow these restrictions and
guidelines:

14
•The 10-GE breakout interfaces of a 40-GE port are operating independently. You do not need to
use all of them for IRF links.
•Port split and combination (the using fortygige command) require a card reboot. To avoid topology
change, HP recommends that you complete these operations before you add the device to an IRF
fabric. When you perform these operations in an IRF fabric, make sure you understand the impact
on the IRF fabric topology. For more information about 40-GE port split and combination
operations, see Layer 2—LAN Switching Configuration Guide.
Physical interface binding requirements
When you bind an IRF physical interface to an IRF port, follow these guidelines:
•In IRF mode, use the shutdown command to shut down the physical interface before you bind it to
or remove it from the IRF port. Use the undo shutdown command to bring up the physical interface
after a binding or binding removal operation.
•In standalone mode, the shutdown and undo shutdown operations are not required.
Connecting IRF ports
When you connect two neighboring IRF members, follow these restrictions and guidelines:
•You must connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of
IRF-port 2 on the other.
•Do not connect physical interfaces of both IRF ports on one member device to the physical
interfaces of both IRF ports on the other device.
IRF link redundancy
When you configure an IRF fabric, follow these link redundancy guidelines:
•For link redundancy and load sharing, bind up to eight physical interfaces to one IRF port.
•Physical interfaces bound to an IRF port can be located on different cards.
•HP recommends using multicard IRF links to prevent a card removal from causing an IRF split.
Multichassis link aggregation
For high availability, connect a downstream device to each IRF member device, and assign the links to
one link aggregation group.
Feature and IRF mode compatibility
To form an IRF fabric:
•All member devices in the IRF fabric must work in the same system operating mode. For more
information about the system operating mode, see Fundamentals Configuration Guide.
•All member devices in the IRF fabric must have the same setting for the maximum number of ECMP
routes. For more information about configuring ECMP, see Layer 3—IP Routing Configuration
Guide.

15
MAD and IRF domain restrictions
When you configure MAD, follow these restrictions and guidelines:
•If LACP MAD runs between two IRF fabrics, assign each fabric a unique IRF domain ID. (For BFD
MAD, this task is optional.)
•An IRF fabric has only one IRF domain ID. You can change the IRF domain ID by using the irf
domain or mad enable command. The IRF domain IDs configured by using these commands
overwrite each other.
•LACP MAD handles collisions differently than BFD MAD. To avoid conflicts, do not enable LACP
MAD together with BFD MAD in an IRF fabric.
•To prevent a port from being shut down when the IRF fabric transits to the Recovery state, use the
mad exclude interface command. To bring up ports in a Recovery-state IRF fabric, use the mad
restore command instead of the undo shutdown command. The mad restore command activates
the Recovery-state IRF fabric.
IRF merge restrictions
If the IRF fabric splits, do not change the IRF settings on any IRF member devices before they reunite.
Configuration backup
HP recommends that you back up the next-startup configuration file on a device before adding the device
to an IRF fabric as a subordinate.
A subordinate device's next-startup configuration file might be overwritten if the master and the
subordinate use the same file name for their next-startup configuration files. You can use the backup file
to restore the original configuration after removing the subordinate from the IRF fabric.
Setup and configuration task list
HP recommends the following IRF fabric setup and configuration procedure:
Setu
p
and confi
g
uration
p
rocedure Remarks
1. (Required.) Planning the IRF fabric setup N/A
2. (Required.) Preconfiguring IRF member devices in standalone mode:
{Assigning a member ID to each IRF member device
{Specifying a priority for each member device
{Binding physical interfaces to IRF ports
Perform this task on each member
device before IRF mode is enabled.
3. (Required.) Saving configuration to the next-startup configuration file
N/A
4. (Required.) Connecting IRF physical interfaces Make sure that they are
interoperable.
5. (Required.) Setting the operating mode to IRF mode N/A
6. (Required.) Accessing the IRF fabric N/A

16
Setu
p
and confi
g
uration
p
rocedure Remarks
7. (Optional.) Configuring IRF member devices in IRF mode:
{Assigning an IRF domain ID to the IRF fabric
{Changing the member ID of a device
{Changing the priority of a member device
{Adding physical interfaces to an IRF port
{Enabling IRF auto-merge
{Configuring a member device description
{Configuring IRF link load sharing mode
{Configuring IRF bridge MAC persistence
{Enabling software auto-update for system software image
synchronization
{Setting the IRF link down report delay
{Configuring MAD
Adding physical interfaces to an IRF
port is required if you did not
preconfigure IRF port bindings.
CAUTION:
Changing member IDs in an IRF
fabric can void member ID-related
configuration and cause
unexpected problems. Make sure
you understand the impact on your
live network before you change
member IDs.
Planning the IRF fabric setup
Consider the following items when you plan an IRF fabric:
•Hardware compatibility and restrictions.
•IRF fabric size.
•Master device.
•IRF physical interfaces.
•Member ID and priority assignment scheme.
•Fabric topology and cabling scheme.
For more information about hardware and cabling, see the installation guide for the device.
Preconfiguring IRF member devices in standalone
mode
Perform the preconfiguration tasks on every IRF member device. These settings take effect on each
member device after their operating mode changes to IRF.
Assigning a member ID to each IRF member device
By default, a device operates in standalone mode without an IRF member ID. You must assign it a unique
IRF member ID before changing its operating mode to IRF.
The member ID assigned to a device is saved in both active and standby MPUs of the device. The standby
MPU might store a different member ID than the active MPU after an MPU replacement. For consistency,
the system automatically updates the member ID in the active MPU to the standby MPU when the
difference is detected.
To set a member ID for the device in standalone mode:

17
Ste
p
Command Remarks
1. (Optional.) Verify the
member ID assignment
status.
display irf configuration
Check the MemberID field. If the
device does not have an IRF
member ID, the field displays
two hyphens (--).
2. Enter system view. system-view N/A
3. Assign an IRF member ID to
the device. irf member member-id
By default, the device does not
have an IRF member ID.
The assigned member ID must be
1 or 2. If you use other member
IDs, the IRF fabric cannot be set
up.
Specifying a priority for each member device
IRF member priority represents the possibility for a device to be elected the master in an IRF fabric. The
higher the priority, the higher the possibility.
To specify a priority for the device in standalone mode:
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Specify a priority for the
device. irf priority priority The default IRF member priority
is 1.
Binding physical interfaces to IRF ports
To establish an IRF connection between two devices, you must bind a minimum of one physical interface
to IRF-port 1 on one device and to IRF-port 2 on the other. For link redundancy and load sharing, bind
multiple physical interfaces to one IRF port.
Make sure the IRF physical interfaces are operating as Layer 2 interfaces. Layer 3 interfaces cannot be
bound to IRF ports. To configure a physical interface as a Layer 2 interface, use the port link-mode bridge
command. For more information about this command, see Layer 2—LAN Switching Configuration
Guide.
In standalone mode, IRF port binding operations do not affect the current configuration of the interface.
However, when the operating mode changes to IRF mode, the default configuration is restored on the IRF
physical interface. You can only execute the following commands on the physical interface:
Command cate
g
or
y
Commands Remarks
Basic Ethernet interface
commands
•description
•flow-interval
•shutdown
See Layer 2—LAN Switching
Configuration Guide.

18
Command cate
g
or
y
Commands Remarks
LLDP commands
•lldp admin-status
•lldp check-change-interval
•lldp enable
•lldp notification remote-change
enable
•lldp tlv-enable
See Layer 2—LAN Switching
Configuration Guide.
To bind physical interfaces to IRF ports:
Ste
p
Command Remarks
1. Enter system view. system-view N/A
2. Enter IRF port view. irf-port port-number N/A
3. Bind a physical interface to
the IRF port.
port group interface interface-type
interface-number [ mode enhanced ]
By default, no physical interfaces
are bound to any IRF port.
Repeat this step to assign
multiple physical interfaces to the
IRF port.
Each IRF port can have a
maximum of eight physical
interfaces.
An IRF physical interface
operates in enhanced mode
after the IRF binding takes effect,
regardless of whether you have
specified the mode enhanced
keywords.
Saving configuration to the next-startup
configuration file
Save the running configuration before converting to the IRF mode. The mode change requires a reboot,
which causes all unsaved settings to be lost.
Perform the following task in any view:
Task Command
Save the running configuration to
the next-startup configuration file. save [ safely ] [ backup | main ] [ force ]
Connecting IRF physical interfaces
When you connect two neighboring IRF members, connect the physical interfaces of IRF-port 1 on one
member to the physical interfaces of IRF-port 2 on the other (see Figure 8).