The Intelligent Resilient Framework (IRF) technology virtualizes multiple physical devices at the same layer into one virtual fabric to provide data center class availability and scalability. IRF virtualization technology offers processing power, interaction, unified management, and uninterrupted maintenance of multiple devices.

IRF network model

Figure 1 shows an IRF fabric that has two devices, which appear as a single node to the upper-layer and lower-layer devices.

Figure 1 IRF application scenario

As shown in Figure 2, 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.

Figure 2 Two-chassis IRF fabric implementation schematic diagram

‌

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 the other members process services while backing up the master. When the master fails, all the other member devices elect a new master from among them to take over without interrupting services.

· IRF link aggregation—You can assign several physical links between neighboring members to their IRF ports to create a load-balanced aggregate IRF connection with redundancy.

· Multichassis link aggregation—You can use the Ethernet link aggregation feature to aggregate the physical links between the IRF fabric and its upstream or downstream devices across the IRF members.

· Network scalability and resiliency—Processing capacity of an IRF fabric equals the total processing capacities of all the members. You can increase ports, network bandwidth, and processing capacity of an IRF fabric simply by adding member devices without changing the network topology.

Basic concepts

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 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. 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. Two devices cannot form an IRF fabric if they use the same member ID. A device cannot join an IRF fabric if its member ID has been used in the fabric.

MPU roles

Each IRF member device has one or two MPUs. The following are MPU roles:

Role	Description
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 tasks: · Manages the local device, including synchronizing configuration with the local standby MPU, processing protocol packets, and creating and maintaining route entries. · Processes 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.

‌

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.

IRF port

An IRF port is a logical interface that connects IRF member devices. Every IRF-capable device has 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 n is the member ID of the device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2.

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 when all its IRF physical interfaces are down.

IRF physical interface

IRF physical interfaces connect IRF member devices and must be bound to an IRF port. They forward traffic between member devices, including IRF protocol packets and data packets that must travel across IRF member devices.

IRF split

IRF split occurs when an IRF fabric breaks up into multiple IRF fabrics because of IRF link failures, as shown in Figure 3. 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 a minimum of one MAD mechanism (see "Configuring MAD").

Figure 3 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 4.

Figure 4 IRF merge

‌

MAD

An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 settings, 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.

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 5, 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 determine whether the packet is from the local IRF fabric. Then, the member device can handle the packet correctly.

Figure 5 A network that contains two IRF domains

‌

IRF network topology

An IRF fabric can use a daisy-chain topology, as shown in Figure 6.

IMPORTANT:

No relay devices are allowed between IRF member devices.

‌

Figure 6 Daisy-chain topology

‌

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 split IRF fabrics merge. For information about the master device of the merged IRF fabric, see "Failure recovery."

‌

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 members consider themselves as the master. This rule is skipped.

2. Member with higher priority.

3. Member with the longest system uptime.

Two members are considered to start 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 CPU MAC address.

For the setup of 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.

Interface naming conventions

In standalone mode:

A physical interface is numbered in the slot-number/subslot-number/interface-index format.

For example, set the link type of GigabitEthernet 2/0/1 to trunk, as follows:

<Sysname> system-view

[Sysname] interface gigabitethernet 2/0/1

[Sysname-GigabitEthernet2/0/1] port link-type trunk

In IRF mode:

A physical interface is numbered in the chassis-number/slot-number/subslot-number/interface-index format. The chassis-number argument represents the IRF member ID.

For example, GigabitEthernet 1/2/0/1 represents the first port in slot 2 on member device 1. Set its link type to trunk, as follows:

<Sysname> system-view

[Sysname] interface gigabitethernet 1/2/0/1

[Sysname-GigabitEthernet1/2/0/1] port link-type trunk

File system naming conventions

In standalone mode, you can use the storage device name to access the file system of the active MPU. To access the file system of the standby MPU, use the name in the slotslot-number#storage-device-name format.

On a multichassis IRF fabric, you can use the storage device name to access the file system of the global active MPU. To access the file system of a global standby MPU, use the name in the chassismember-ID#slotslot-number#storage-device-name format.

For more information about storage device naming conventions, see Fundamentals Configuration Guide.

For example:

· To create and access the test folder under the root directory of the flash memory on the global active MPU:

<Master> mkdir test

Creating directory flash:/test... Done.

<Master> cd test

<Master> dir

Directory of flash:/test

The directory is empty.

524288 KB total (29832 KB free)

· To create and access the test folder under the root directory of the flash memory in slot 0 on member device 1:

<Master> mkdir chassis1#slot0#flash:/test

Creating directory chassis1#slot0#flash:/test... Done.

<Master> cd chassis1#slot0#flash:/test

<Master> dir

Directory of chassis1#slot0#flash:/test

The directory is empty.

524288 KB total (128812 KB free)

Configuration synchronization

IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all MPUs obtain and run the running configuration of the global active MPU. Configuration changes are automatically propagated from the global active MPU to the remaining MPUs. The configuration files of these MPUs are retained, but the files do not take effect. The subordinate devices use their own startup configuration files on their respective local active MPU only after these devices are removed from the IRF fabric.

As a best practice, 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.

For more information about configuration management, see Fundamentals Configuration Guide.

Multi-active handling procedure

The multi-active handling procedure includes detection, collision handling, and failure recovery.

Detection

IRF provides MAD mechanisms by extending LACP and BFD to detect multi-active collisions. As a best practice, configure a minimum of one MAD mechanism on an IRF fabric. For more information about the MAD mechanisms and their application scenarios, see "MAD mechanisms."

For information about LACP, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide. For information about BFD, see High Availability Configuration Guide.

Collision handling

When MAD detects a multi-active collision, it sets all IRF fabrics except one to the Recovery state. The fabric that is not placed in Recovery state can continue to forward traffic. The Recovery-state IRF fabrics are inactive and cannot forward traffic.

LACP MAD and BFD MAD use the following process to handle a multi-active collision:

1. Compare the number of members in each fabric.

2. Set all fabrics to the Recovery state except the one that has the most members.

3. Compare the member IDs of the masters if all IRF fabrics have the same number of members.

4. Set all fabrics to the Recovery state except the one that has the lowest numbered master.

5. Shut down all common network interfaces in the Recovery-state fabrics except for the following interfaces:

¡ Interfaces automatically excluded from being shut down by the system.

¡ Interfaces specified by using 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.

After the failed IRF link between two split IRF fabrics is recovered, log in to the inactive IRF fabric to reboot its member devices if the system requires you to do so. After these member devices join the active IRF fabric as subordinate devices, the IRF merge is complete, as shown in Figure 7. The network interfaces that have been shut down by MAD automatically restore their original state.

‌

CAUTION:

If you inadvertently reboot the active IRF fabric after the failed IRF link recovers, its member devices will join the inactive IRF fabric with their network interfaces being shut down by MAD. To restore the original states of the network interfaces in the merged IRF fabric, use the mad restore command.

‌

NOTE:

If the IRF auto-merge feature is enabled, the inactive IRF member devices will automatically reboot after the failed IRF link recovers and a manual reboot is typically not required.

‌

Figure 7 Recovering the IRF fabric

If the active IRF fabric fails before the IRF link is recovered (see Figure 8), use the mad restore command on the inactive IRF fabric to recover the inactive IRF fabric. This command brings up all network interfaces that were shut down by MAD. After the IRF link is repaired, merge the two parts into a unified IRF fabric.

Figure 8 Active IRF fabric fails before the IRF link is recovered

‌

MAD mechanisms

IRF provides MAD mechanisms by extending LACP and BFD.

Table 1 compares the MAD mechanisms and their application scenarios.

Table 1 Comparison of MAD mechanisms

MAD mechanism	Advantages	Disadvantages	Application scenarios
LACP MAD	· Detection speed is fast. · Runs on existing aggregate links without requiring MAD-dedicated physical links or Layer 3 interfaces.	Requires an intermediate device that supports extended LACP for MAD.	Link aggregation is used between the IRF fabric and its upstream or downstream device.
BFD MAD	· Detection speed is fast. · Intermediate device, if used, can come from any vendor.	Requires MAD dedicated physical links and Layer 3 interfaces, which cannot be used for transmitting user traffic.	· No special requirements for network scenarios. · If no intermediate device is used, this mechanism is only suitable for IRF fabrics that have only two members that are geographically close to one another.

MAD mechanism

Advantages

Disadvantages

Application scenarios

LACP MAD

· Detection speed is fast.

· Runs on existing aggregate links without requiring MAD-dedicated physical links or Layer 3 interfaces.

Requires an intermediate device that supports extended LACP for MAD.

Link aggregation is used between the IRF fabric and its upstream or downstream device.

BFD MAD

· Detection speed is fast.

· Intermediate device, if used, can come from any vendor.

Requires MAD dedicated physical links and Layer 3 interfaces, which cannot be used for transmitting user traffic.

· No special requirements for network scenarios.

· If no intermediate device is used, this mechanism is only suitable for IRF fabrics that have only two members that are geographically close to one another.

‌

LACP MAD

As shown in Figure 9, 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 a device that supports extended LACP for MAD.

The IRF member devices send extended LACPDUs that convey a domain ID and an active ID (the member ID of the master). The intermediate device transparently forwards the extended LACPDUs received from one member device to all the other member devices.

· If the domain IDs and active IDs 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."

Figure 9 LACP MAD scenario

‌

BFD MAD

BFD MAD detects multi-active collisions by using BFD.

You can use common or management Ethernet ports for BFD MAD.

If management Ethernet ports are used, BFD MAD has the following requirements:

· An intermediate device is required and each IRF member device must have a BFD MAD link to the intermediate device.

· Each member device is assigned a MAD IP address on the master's management Ethernet port.

If common Ethernet ports are used, BFD MAD has the following requirements:

· If an intermediate device is used, each member device must have a BFD MAD link to the intermediate device. If no intermediate device is used, all member devices must have a BFD MAD link to each other. As a best practice, use an intermediate device to connect IRF member devices if the IRF fabric has more than two member devices. A full mesh of IRF members might cause broadcast loops.

· Ports on BFD MAD links are assigned to a VLAN (or Layer 3 aggregate interface) used for BFD MAD. Each member device is assigned a MAD IP address on the VLAN interface (or Layer 3 aggregate interface).

The BFD MAD links and BFD MAD VLAN (or Layer 3 aggregate interface) must be dedicated. Do not use BFD MAD links or BFD MAD VLAN (or Layer 3 aggregate interface) for any other purposes.

When you use a Layer 3 aggregate interface for BFD MAD, make sure its member ports do not exceed the maximum number of Selected ports allowed for an aggregation group. If the number of member ports exceeds the maximum number of Selected ports, some member ports cannot become Selected. BFD MAD will be unable to work correctly and its state will change to Faulty. For more information about setting the maximum number of Selected ports for an aggregation group, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide.

NOTE:

· The MAD addresses identify the member devices and must belong to the same subnet.

· Of all management Ethernet ports on an IRF fabric, only the master's management Ethernet port is accessible.

Figure 10 shows a typical BFD MAD scenario that uses an intermediate device. On the intermediate device, assign the ports on the BFD MAD links to the same VLAN.

Figure 11 shows a typical BFD MAD scenario that does not use an intermediate device.

With BFD MAD, the master attempts to establish BFD sessions with 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 takes effect. 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.

· When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect. The masters can establish a BFD session. If you execute the display bfd session command, the state of the BFD session between the two devices is Up.

Figure 10 BFD MAD scenario with an intermediate device

Figure 11 BFD MAD scenario without an intermediate device

‌

Restrictions and guidelines: IRF configuration

Hardware compatibility with IRF

The device can form an IRF fabric only with devices of the same model. The cards in the slots numbered the same between member chassis must be the same type.

Software requirements for IRF

All IRF member devices must run the same software image version. Make sure the software auto-update feature is enabled on all member devices.

IRF fabric size

An IRF fabric can contain a maximum of two member devices.

Candidate IRF physical interfaces

IMPORTANT:

· The physical interfaces bound to one IRF port must be located on the same module and operate at the same rate.

· The physical interfaces at the two ends of an IRF link must operate at the same rate.

‌

Use Table 2 to identify which fixed ports on a service module can act as IRF physical interfaces. If a service module supports subcards or does not have fixed ports, use Table 3 to identify the subcards that provide IRF physical interfaces.

Table 2 Candidate IRF physical interfaces on service modules

Module	Candidate IRF physical interfaces
FIP-240	All fixed ports.
FIP-260	No fixed ports.
FIP-300	All fixed ports.
FIP-310	All fixed ports.
FIP-380	All fixed ports.
FIP-600	No fixed ports.
FIP-660	No fixed ports.
FIP-680	The four fixed SFP+ ports.
SAP-20GE2XP	GE 16 through GE 19. The two fixed SFP+ fiber ports.
SAP-28GE	GE 16 through GE 27.
SAP-XP4GE32	All fixed ports.

Table 3 Candidate IRF physical interfaces on subcards

Module	Candidate IRF physical interfaces
MIC-X-GP8	All ports.
MIC-X-GP10	All ports.
MIC-X-GT8	All ports.
MIC-X-GP4GT4	All ports.
MIC-X-XP2	All ports.
MIC-X-XP4	All ports.
MIC-X-XP4W	All ports.
MIC-X-SP4	Not supported.
MIC-X-SP8	Not supported.
MIC-X-ET16	Not supported.
MIC-X-CLP4	Not supported.
MIC-X-CLP2	Not supported.

IMPORTANT:

· If the device contains a FIP-600 module, you can use only the physical interfaces on SAP-4EXP modules for IRF links.

· If you use ports on an SAP-4EXP module as IRF physical interfaces on one member device, you must use ports on the same type of module as IRF physical interfaces on the neighboring member device.

· For more information about the service module and subcard compatibility, see H3C SR6600_SR6600-X Routers Interface Module Guide.

‌

Transceiver modules and cables selection for IRF

When you select transceiver modules and cables, follow these restrictions and guidelines:

· Use Ethernet network cables to connect copper Ethernet ports for a short-distance connection.

· Use transceiver modules and fibers to connect fiber Ethernet ports for a long-distance connection.

· The transceiver modules at the two ends of an IRF link must be the same type.

For more information about the transceiver modules and DAC cables, see the device installation guide and H3C Transceiver Modules User Guide.

NOTE:

The transceiver modules and DAC cables available for the device are subject to change over time. For the most up-to-date list of transceiver modules and DAC cables, contact your H3C sales representative.

‌

IRF port connection

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.

· For high availability, bind multiple physical interfaces to an IRF port. For information about the maximum number of physical interfaces that can be bound to an IRF port, see the command reference.

Figure 12 Connecting IRF physical interfaces

‌

IRF physical interface configuration restrictions and guidelines

Command configuration restrictions

On a physical interface bound to an IRF port, you can execute only the following commands:

· Interface commands, including:

¡ description.

¡ flow-interval.

¡ shutdown.

For more information about these commands, see Ethernet interface configuration in Interface Command Reference.

· LLDP commands, including:

¡ lldp admin-status.

¡ lldp check-change-interval.

¡ lldp enable.

¡ lldp encapsulation snap.

¡ lldp notification remote-change enable.

¡ lldp tlv-enable.

For more information about these commands, see Layer 2—LAN Switching Command Reference.

Suppressing SNMP notifications of packet drops on IRF physical interfaces

Before an IRF member device forwards a packet, it examines its forwarding path in the IRF fabric for a loop. If a loop exists, the device discards the packet on the source interface of the looped path. This loop elimination mechanism will drop a large number of broadcast packets on the IRF physical interfaces.

To suppress SNMP notifications of packet drops that do not require attention, do not monitor packet forwarding on the IRF physical interfaces.

Feature compatibility and configuration restrictions with IRF

MDC

Make sure IRF physical interfaces and MAD VLANs belong to the default MDC. Assign physical interfaces to MDCs and then configure MAD.

If the IRF fabric splits, do not change the MDC settings on any IRF member devices before they reunite.

Before you use the undo mdc command to delete an MDC, remove IRF port bindings for the physical interfaces on the MDC and save the configuration. To identify physical interfaces bound to IRF ports, use the display irf link command.

Except for the commands in Table 4, all IRF commands are available only on the default context.

Table 4 IRF commands available on both default and non-default contexts

Command category	Commands
Display commands	display irf link display mad
MAD commands	mad arp enable mad enable mad nd enable mad exclude interface

Command category

Commands

Display commands

display irf link

display mad

MAD commands

mad arp enable

mad enable

mad nd enable

mad exclude interface

‌

For more information about contexts, see "Configuring contexts."

Licensing requirements for IRF

For a license-based feature to run correctly on an IRF fabric, make sure the licenses installed for the feature on all member devices are the same. For more information about feature licensing, see Fundamentals Configuration Guide.

Configuration rollback restrictions

The configuration rollback feature cannot roll back the following IRF settings:

· Member device description (set by using the irf member description command).

· Member device priority (set by using the irf member priority command).

· IRF physical interface and IRF port bindings (set by using the port group interface command).

For more information about the configuration rollback feature, see configuration file management in Fundamentals Configuration Guide.

IRF tasks at a glance

To configure IRF, perform the following tasks:

1. Setting up an IRF fabric

a. Assigning a member ID to each IRF member device

b. (Optional.) Specifying a priority for each member device

c. Binding physical interfaces to IRF ports

d. Saving configuration to the next-startup configuration file

e. Connecting IRF physical interfaces

f. Setting the operating mode to IRF mode

g. Accessing the IRF fabric

2. Configuring MAD

Configure a minimum of one MAD mechanism on an IRF fabric.

¡ Configuring LACP MAD

¡ Configuring BFD MAD

¡ Excluding interfaces from the shutdown action upon detection of multi-active collision

This feature excludes an interface from the shutdown action for management or other special purposes when an IRF fabric transits to the Recovery state.

¡ Recovering an IRF fabric

3. (Optional.) Optimizing IRF settings for an IRF fabric

¡ Changing the member ID of a member device

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.

¡ Changing the priority of a member device

¡ Adding physical interfaces to an IRF port

¡ Bulk-configuring basic IRF settings for a member device

You can configure member IDs, priorities, domain ID, IRF physical interfaces separately or in bulk.

¡ Enabling IRF auto-merge

When two IRF fabrics merge, this feature enables the IRF fabric that failed the master election to automatically reboot all its member devices to complete the merge.

¡ Configuring a member device description

¡ Configuring IRF link load sharing mode

¡ Configuring the IRF bridge MAC address

¡ Enabling software auto-update for software image synchronization

This feature automatically synchronizes the current software images of the global active MPU to devices or MPUs that are attempting to join the IRF fabric.

¡ Setting the IRF link down report delay

Planning the IRF fabric setup

Consider the following items when you plan an IRF fabric:

· Hardware compatibility and restrictions.

· IRF fabric size.

· Master device.

· Member ID and priority assignment scheme.

· Fabric topology and cabling scheme.

· IRF physical interfaces.

Setting up an IRF fabric

Assigning a member ID to each IRF member device

About this task

Assign a unique IRF member ID to a device before changing the device's operating mode to IRF. If you do not assign a member ID to the device, the device automatically uses the member ID of 1 after the mode changes to IRF.

The member ID assigned to the device is saved in both active and standby MPUs. The standby MPU might store a different member ID than the active MPU after an MPU replacement. For consistency, the system updates the member ID in the active MPU automatically to the standby MPU when the difference is detected.

Procedure

1. Enter system view.

system-view

2. Assign an IRF member ID to the device.

irf member member-id

By default, the device operates in standalone mode and does not have an IRF member ID.

Specifying a priority for each member device

About this task

IRF member priority represents the possibility for a device to be elected the master in an IRF fabric. A larger priority value indicates a higher priority.

Procedure

1. Enter system view.

system-view

2. Specify a priority for the device in standalone mode.

irf priority priority

The default IRF member priority is 1.

Binding physical interfaces to IRF ports

About this task

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 physical interface.

Restrictions and guidelines

Make sure the IRF physical interfaces of an IRF port use the same binding mode. In IRF mode, IRF physical interfaces of an IRF port cannot be configured to use different binding modes. In standalone mode, you can configure the IRF physical interfaces of an IRF port to use different binding modes. However, only one binding mode takes effect after the operating mode changes from standalone to IRF. The binding mode of the first IRF physical interface in the configuration file has the highest priority.

Procedure

1. Enter system view.

system-view

2. Enter IRF port view in standalone mode.

irf-port irf-port-number

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 an IRF port.

Repeat this step to assign multiple physical interfaces to the IRF port.

Saving configuration to the next-startup configuration file

About this task

Save the running configuration before converting to the IRF mode. The mode change requires a reboot, which causes all unsaved settings to be lost.

Procedure

To save the running configuration to the next-startup configuration file, execute the following command in any view:

save

For more information about this command, see configuration file management in Fundamentals Command Reference.

Connecting IRF physical interfaces

Follow the restrictions in "IRF port connection" to connect IRF physical interfaces as well as based on the topology and cabling scheme.

Setting the operating mode to IRF mode

About this task

By default, the device operates in standalone mode. To assign the device to an IRF fabric, you must change its operating mode to IRF mode.

After you change the operating mode, the device automatically reboots for the change to take effect.

During the reboot, you may choose to have the system automatically convert the startup configuration file. Automatic configuration conversion prevents slot- or interface-related settings from becoming invalid. For example, the system adds member ID information to interface numbers and file paths in IRF mode.

Restrictions and guidelines

Upon an operating mode change, the system automatically converts interface names by adding or deleting the first number segment (the member ID) in the interface number. When performing this task, the system converts every string in a valid interface name format without identifying whether or not they are interface names. To avoid undesirable configuration changes that result from false modification, do not name any objects except interfaces in a valid interface name format.

The following are valid interface name formats:

· interface-type interface-number, which has a space between the two arguments.

· interface-typeinterface-number, which does not have a space between the two arguments.

The system uses the space-separated format to match CPOS E1, E3, T1, and T3 interfaces and uses the non-space format to match other types of physical interfaces.

If a string (except the string configured by using the description command) matches a valid interface name, the system converts that string. For example, if a VLAN exists with a name of GigabitEthernet2/0/7 in standalone mode, the VLAN name will change to GigabitEthernetn/2/0/7 in IRF mode. The n argument represents the IRF member ID.

Prerequisites

Before you change the operating mode, verify that a unique IRF member ID has been assigned to the device.

Procedure

1. Enter system view.

system-view

2. Set the operating mode to IRF mode.

chassis convert mode irf

The default operating mode is standalone mode.

IRF generates packets on a device in IRF mode even if the device does not form an IRF fabric with any other devices. To conserve system resources, set a device to standalone mode after removing it from an IRF fabric. To restore the standalone mode, use the undo chassis convert mode command.

Accessing the IRF fabric

The following methods are available for accessing an IRF fabric:

· Local login—Log in through the console port of any member device.

· Remote login—Log in at a Layer 3 interface on any member device by using methods including Telnet and SNMP.

The IRF fabric appears as one device after it is formed. When you log in to an IRF fabric, you are placed at the CLI of the global active MPU, regardless of at which member device you are logged in. You configure and manage all IRF members at the CLI of the global active MPU. All settings you have made are automatically propagated to the IRF members.

For more information, see login configuration in Fundamentals Configuration Guide.

Configuring MAD

Restrictions and guidelines for MAD configuration

Assigning IRF domain IDs

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 the commands overwrite each other.

If you change the IRF domain ID in one MDC, the IRF domain IDs in all other MDCs change automatically. The irf domain command is available only on the default MDC. The mad enable, mad arp enable, and mad nd enable commands are available on any MDCs.

If LACP MAD runs between two IRF fabrics, assign each fabric a unique IRF domain ID. (For BFD MAD, this task is optional.)

Actions on interfaces shut down by MAD

To prevent a multi-active collision from causing network issues, avoid using the undo shutdown command to bring up the interfaces shut down by a MAD mechanism on a Recovery-state IRF fabric.

Configuring LACP MAD

1. Enter system view.

system-view

2. Assign a domain ID to the IRF fabric.

irf domain domain-id

The default IRF domain ID is 0.

CAUTION:

Changing the IRF domain ID of an IRF member device will remove that member device from the IRF fabric. This member device will be unable to exchange IRF protocol packets with the remaining member devices in the IRF fabric.

3. Create an aggregate interface and enter aggregate interface view.

¡ Enter Layer 2 aggregate interface view.

interface bridge-aggregation interface-number

¡ Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

Perform this step also on the intermediate device.

4. Configure the aggregation group to operate in dynamic aggregation mode.

link-aggregation mode dynamic

By default, an aggregation group operates in static aggregation mode.

LACP MAD takes effect only on dynamic aggregate interfaces.

Perform this step also on the intermediate device.

5. Enable LACP MAD.

mad enable

By default, LACP MAD is disabled.

6. Return to system view.

quit

7. Enter Ethernet interface view or interface range view.

¡ Enter Ethernet interface view.

interface interface-type interface-number

¡ Enter interface range view. Choose one of the following commands:

interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ]

To assign a range of ports to the aggregation group, enter interface range view.

To assign one port to the aggregation group, enter Ethernet interface view.

8. Assign the Ethernet port or the range of Ethernet ports to the specified aggregation group.

port link-aggregation group group-id

Multichassis link aggregation is allowed.

Perform this step also on the intermediate device.

Configuring BFD MAD

Restrictions and guidelines for configuring BFD MAD

As a best practice, use the following procedure to set up BFD MAD:

1. Choose a BFD MAD link scheme as described in "BFD MAD."

2. Configure BFD MAD.

3. Connect the BFD MAD links.

When you configure BFD MAD on a VLAN interface, follow these restrictions and guidelines:

Category	Restrictions and guidelines
BFD MAD VLAN	· Do not enable BFD MAD on VLAN-interface 1. · If you are using an intermediate device, perform the following tasks: ¡ On the IRF fabric and the intermediate device, create a VLAN for BFD MAD. ¡ On the IRF fabric and the intermediate device, assign the ports of BFD MAD links to the BFD MAD VLAN. ¡ On the IRF fabric, create a VLAN interface for the BFD MAD VLAN. · Make sure the IRF fabrics on the network use different BFD MAD VLANs. · Make sure the BFD MAD VLAN contains only ports on the BFD MAD links. Exclude a port from the BFD MAD VLAN if that port is not on a BFD MAD link. If you have assigned that port to all VLANs by using the port trunk permit vlan all command, use the undo port trunk permit command to exclude that port from the BFD MAD VLAN.
BFD MAD VLAN and feature compatibility	Do not use the BFD MAD VLAN and its member ports for any purpose other than configuring BFD MAD. · Use only the mad bfd enable and mad ip address commands on the BFD MAD-enabled VLAN interface. If you configure other features, both BFD MAD and other features on the interface might run incorrectly. · Disable the spanning tree feature on any Layer 2 Ethernet ports in the BFD MAD VLAN. The MAD feature is mutually exclusive with the spanning tree feature.
MAD IP address	· To avoid network issues, only use the mad ip address command to configure IP addresses on the BFD MAD-enabled VLAN interface. Do not configure an IP address by using the ip address command or configure a VRRP virtual address on the BFD MAD-enabled VLAN interface. · Make sure all the MAD IP addresses are on the same subnet.

‌

When you configure BFD MAD on a Layer 3 aggregate interface, follow these restrictions and guidelines:

Category	Restrictions and guidelines
BFD MAD-enabled Layer 3 aggregate interface	· Make sure the Layer 3 aggregate interface operates in static aggregation mode. · Make sure the member ports in the aggregation group do not exceed the maximum number of Selected ports allowed for an aggregation group. If the number of member ports exceeds the maximum number of Selected ports, some member ports cannot become Selected. BFD MAD will be unable to work correctly and its state will change to Faulty.
BFD MAD VLAN	· On the intermediate device (if any), assign the ports on the BFD MAD links to the same VLAN. Do not assign the ports to an aggregate interface. If the ports are hybrid ports, make sure these ports are untagged members of their PVIDs. · If the intermediate device acts as a BFD MAD intermediate device for multiple IRF fabrics, assign different BFD MAD VLANs to the IRF fabrics. · Do not use the BFD MAD VLAN on the intermediate device for any purposes other than BFD MAD. · Make sure the BFD MAD VLAN on the intermediate device contains only ports on the BFD MAD links. Exclude a port from the BFD MAD VLAN if that port is not on a BFD MAD link. If you have assigned that port to all VLANs by using the port trunk permit vlan all command, use the undo port trunk permit command to exclude that port from the BFD MAD VLAN.
BFD MAD-enabled Layer 3 aggregate interface and feature compatibility	Use only the mad bfd enable and mad ip address commands on the BFD MAD-enabled interface. If you configure other features, both BFD MAD and other features on the interface might run incorrectly.
MAD IP address	· To avoid network issues, only use the mad ip address command to configure IP addresses on the BFD MAD-enabled interface. Do not configure an IP address by using the ip address command or configure a VRRP virtual address on the BFD MAD-enabled interface. · Make sure all the MAD IP addresses are on the same subnet.

‌

When you configure BFD MAD on a management Ethernet port, follow these restrictions and guidelines:

Category	Restrictions and guidelines
Management Ethernet ports for BFD MAD	Connect a management Ethernet port on each IRF member device to the common Ethernet ports on the intermediate device. To avoid BFD MAD failure caused by an active/standby MPU switchover, connect the management Ethernet ports on each MPU to the intermediate device.
BFD MAD VLAN	· On the intermediate device, create a VLAN for BFD MAD, and assign the ports used for BFD MAD to the VLAN. On the IRF fabric, you do not need to assign the management Ethernet ports to the VLAN. · Make sure the IRF fabrics on the network use different BFD MAD VLANs. · Make sure the BFD MAD VLAN on the intermediate device contains only ports on the BFD MAD links.
MAD IP address	· Use the mad ip address command instead of the ip address command to configure MAD IP addresses on the BFD MAD-enabled management Ethernet ports. · Make sure all the MAD IP addresses are on the same subnet.

‌

Configuring BFD MAD on a VLAN interface

1. Enter system view.

system-view

2. (Optional.) Assign a domain ID to the IRF fabric.

irf domain domain-id

By default, the domain ID of an IRF fabric is 0.

CAUTION:

3. Create a VLAN dedicated to BFD MAD.

vlan vlan-id

By default, only VLAN 1 exists.

4. Return to system view.

quit

5. Enter Ethernet interface view or interface range view.

¡ Enter Ethernet interface view.

interface interface-type interface-number

¡ Enter interface range view. Choose one of the following commands:

interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ]

To assign a range of ports to the BFD MAD VLAN, enter interface range view.

To assign one port to the BFD MAD VLAN, enter Ethernet interface view.

6. Assign the port or the range of ports to the BFD MAD VLAN.

¡ Assign the ports to the VLAN as access ports.

port access vlan vlan-id

¡ Assign the ports to the VLAN as trunk ports.

port trunk permit vlan vlan-id

¡ Assign the ports to the VLAN as hybrid ports.

port hybrid vlan vlan-id { tagged | untagged }

The link type of BFD MAD ports can be access, trunk, or hybrid.

The default link type of a port is access.

7. Return to system view.

quit

8. Enter VLAN interface view.

interface vlan-interface vlan-interface-id

9. Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

10. Assign a MAD IP address to a member device on the VLAN interface.

mad ip address ip-address { mask | mask-length } member member-id

By default, no MAD IP addresses are configured on any VLAN interfaces.

Repeat this step to assign a MAD IP address to each member device on the VLAN interface.

Configuring BFD MAD on a Layer 3 aggregate interface

1. Enter system view.

system-view

2. (Optional.) Assign a domain ID to the IRF fabric.

irf domain domain-id

By default, the domain ID of an IRF fabric is 0.

CAUTION:

3. Create a Layer 3 aggregate interface for BFD MAD.

interface route-aggregation interface-number

4. Return to system view.

quit

5. Enter interface view or interface range view.

¡ Enter Ethernet interface view.

interface interface-type interface-number

¡ Enter interface range view. Choose one of the following commands:

interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ]

To assign a range of ports to the aggregation group for the aggregate interface, enter interface range view.

To assign one port to the aggregation group for the aggregate interface, enter Ethernet interface view.

6. Assign the port or the range of ports to the aggregation group for the aggregate interface.

port link-aggregation group number

7. Return to system view.

quit

8. Enter Layer 3 aggregate interface view.

interface route-aggregation interface-number

9. Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

10. Assign a MAD IP address to a member device on the Layer 3 aggregate interface.

mad ip address ip-address { mask | mask-length } member member-id

By default, no MAD IP addresses are configured on aggregate interfaces.

Repeat this step to assign a MAD IP address to each member device on the aggregate interface.

Configuring BFD MAD on a management Ethernet port

1. Enter system view.

system-view

2. (Optional.) Assign a domain ID to the IRF fabric.

irf domain domain-id

By default, the domain ID of an IRF fabric is 0.

CAUTION:

3. Enter management Ethernet interface view.

interface m-gigabitethernet interface-number

Of all management Ethernet ports on an IRF fabric, only the master's management Ethernet port is accessible.

4. Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

5. Assign a MAD IP address to each member device.

mad ip address ip-address { mask | mask-length } member member-id

By default, no MAD IP addresses are configured.

Excluding interfaces from the shutdown action upon detection of multi-active collision

About this task

When an IRF fabric transits to the Recovery state, the system automatically excludes the following network interfaces from being shut down:

· IRF physical interfaces.

· Member interfaces of an aggregate interface if the aggregate interface is excluded from being shut down.

You can exclude a network interface from the shutdown action for management or other special purposes. For example:

· Exclude a port from the shutdown action so you can Telnet to the port for managing the device.

· Exclude a VLAN interface and its Layer 2 ports from the shutdown action so you can log in through the VLAN interface.

Restrictions and guidelines

If the Layer 2 ports of a VLAN interface are distributed on multiple member devices, the exclusion operation might introduce IP collision risks. The VLAN interface might be up on both active and inactive IRF fabrics.

Procedure

1. Enter system view.

system-view

2. Configure a network interface to not shut down when the IRF fabric transits to the Recovery state.

mad exclude interface interface-type interface-number

By default, all network interfaces on a Recovery-state IRF fabric are shut down, except for the network interfaces automatically excluded by the system.

Recovering an IRF fabric

About this task

For split IRF fabrics, if the active IRF fabric fails before the IRF link is recovered, perform this task on the inactive IRF fabric to recover the inactive IRF fabric. The manual recovery operation brings up all interfaces that were shut down by MAD on the inactive IRF fabric.

Procedure

1. Enter system view.

system-view

2. Recover the inactive IRF fabric.

mad restore

Optimizing IRF settings for an IRF fabric

Changing the member ID of a member device

Restrictions and guidelines

CAUTION:

In IRF mode, an IRF member ID change can invalidate member ID-related settings and cause data loss. Make sure you fully understand its impact on your live network.

‌

The new member ID takes effect at reboot. After the device reboots, the settings on all member ID-related physical resources (including common physical network interfaces) are removed, regardless of whether you have saved the configuration.

Procedure

1. Enter system view.

system-view

2. Change the member ID of a member device.

irf member member-id renumber new-member-id

By default, the device uses the member ID that is set in standalone mode.

CAUTION:

In IRF mode, an IRF member ID change can invalidate member ID-related settings and cause data loss. Make sure you fully understand its impact on your live network.

‌

3. Save the running configuration.

save [ safely ] [ force ]

4. Return to user view.

quit

5. Reboot the member device.

reboot chassis chassis-number

The chassis-number must be the same as the member-id specified in the irf member member-id renumber new-member-id command.

Changing the priority of a member device

About this task

You can change the priority of a member device so it can be elected the master in the next master election.

A change to member priority can affect the master re-election result. However, it does not cause an immediate master re-election.

Procedure

1. Enter system view.

system-view

2. Specify a priority for a member of an IRF fabric.

irf member member-id priority priority

The default IRF member priority is 1.

Adding physical interfaces to an IRF port

Restrictions and guidelines

Make sure the IRF physical interfaces of an IRF port use the same binding mode. In IRF mode, IRF physical interfaces of an IRF port cannot be configured to use different binding modes.

Procedure

1. Enter system view.

system-view

2. Enter the interface view or interface range view of an IRF physical interface or a range of IRF physical interfaces, respectively.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter interface range view. Choose one of the following commands:

interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ]

To shut down one IRF physical interface, enter its interface view.

To shut down a range of IRF physical interfaces, enter interface range view.

3. Shut down the physical interfaces.

shutdown

By default, a physical interface is not administratively down.

If you cannot shut down a physical interface, follow the system instruction to shut down its peer interface.

4. Return to system view.

quit

5. Enter IRF port view.

irf-port member-id/irf-port-number

6. Bind each physical interface to the IRF port.

port group interface interface-type interface-number [ mode enhanced ]

By default, no physical interfaces are bound to an IRF port.

Repeat this step to assign multiple physical interfaces to the IRF port.

7. Return to system view.

quit

8. Enter the interface view or interface range view of an IRF physical interface or a range of IRF physical interfaces, respectively.

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

¡ Enter interface range view. Choose one of the following commands:

interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ]

9. Bring up the physical interfaces.

undo shutdown

10. Return to system view.

quit

11. Save the running configuration.

save

Activating IRF port settings causes IRF merge and reboot. To avoid data loss, save the running configuration to the startup configuration file before you perform the operation.

12. Activate the configuration on the IRF port.

irf-port-configuration active

After this step is performed, the state of the IRF port changes to UP. The member devices elect a master, and the subordinate device reboots automatically.

After the IRF fabric is formed, you can add physical interfaces to an IRF port (in UP state) without repeating this step.

Bulk-configuring basic IRF settings for a member device

About this task

Use the easy IRF feature to bulk-configure basic IRF settings for a device in IRF mode, including the member ID, domain ID, priority, and IRF port bindings.

The easy IRF feature provides the following configuration methods:

· Interactive method—Enter the easy-irf command without parameters. The system will guide you to set the parameters step by step.

· Non-interactive method—Enter the easy-irf command with parameters.

As a best practice, use the interactive method if you are new to IRF.

Restrictions and guidelines

CAUTION:

· Use caution when you change the member ID of an IRF member device. An IRF member ID uniquely identifies a device in an IRF fabric. An IRF member ID change can invalidate member ID-related settings, including interface and file path settings, and cause data loss. Make sure you fully understand its impact on the live network.

· The member device reboots immediately after you specify a new member ID for it. Make sure you are aware of the impact of this operation on the network.

If you execute the easy-irf command multiple times, the following settings take effect:

· The most recent settings for the member ID, domain ID, and priority.

· IRF port bindings added through repeated executions of the command. To remove an IRF physical interface from an IRF port, you must use the undo port group interface command in IRF port view.

If you specify IRF physical interfaces by using the interactive method, you must also follow these restrictions and guidelines:

· Do not enter spaces between the interface type and interface number.

· Use a comma (,) to separate two physical interfaces. No spaces are allowed between interfaces.

Procedure

1. Enter system view.

system-view

2. Bulk-configure basic IRF settings for the device.

easy-irf [ member member-id [ renumber new-member-id ] domain domain-id [ priority priority ] [ irf-port1 interface-list1 ] [ irf-port2 interface-list2 ] ]

Make sure the new member ID is unique in the IRF fabric to which the device will be added.

Enabling IRF auto-merge

About this task

When two IRF fabrics merge, you must reboot the member devices in the IRF fabric that fails in the master election. The auto-merge feature enables the IRF fabric to automatically reboot all its member devices to complete the merge.

If this feature is disabled, you must manually reboot the devices that failed the master election to complete the merge.

Procedure

1. Enter system view.

system-view

2. Enable IRF auto-merge.

irf auto-merge enable

By default, this feature is enabled.

Configuring a member device description

1. Enter system view.

system-view

2. Configure a description for a member device.

irf member member-id description text

By default, no member device description is configured.

Configuring IRF link load sharing mode

About IRF link load sharing mode

On an IRF port, traffic is balanced across its physical links.

You can configure the IRF port to distribute traffic based on any combination of the following criteria:

· IP addresses.

· MAC addresses.

· Incoming port.

The system displays an error message if a criteria combination is not supported.

The criteria can also be packet types, such as Layer 2, IPv4, and IPv6.

Restrictions and guidelines for configuring IRF link load sharing mode

Configure the IRF link load sharing mode for IRF links in system view or IRF port view:

· In system view, the configuration is global and takes effect on all IRF ports.

· In IRF port view, the configuration is port specific and takes effect only on the specified IRF port.

An IRF port preferentially uses the port-specific load sharing mode. If no port-specific load sharing mode is available, the IRF port uses the global load sharing mode.

Before you configure a port-specific load sharing mode, make sure you have bound a minimum of one physical interface to the IRF port.

Configuring the global load sharing mode

1. Enter system view.

system-view

2. Configure the global IRF link load sharing mode.

irf-port global load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } *

The following are the default criteria for distributing different types of packets across IRF links:

¡ Non-TCP/-UDP IP traffic—Source and destination IP addresses.

¡ TCP/UDP IP traffic—Source and destination TCP/UDP port numbers.

If you execute this command multiple times, the most recent configuration takes effect.

Configuring a port-specific load sharing mode

1. Enter system view.

system-view

2. Enter IRF port view.

irf-port member-id/irf-port-number

3. Configure the port-specific load sharing mode.

irf-port load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } *

The following are the default criteria for distributing different types of packets across IRF links:

¡ Non-TCP/-UDP IP traffic—Source and destination IP addresses.

¡ TCP/UDP IP traffic—Source and destination TCP/UDP port numbers.

If you execute this command multiple times, the most recent configuration takes effect.

Configuring the IRF bridge MAC address

About this task

The bridge MAC address of a system must be unique on a switched LAN. IRF bridge MAC address identifies an IRF fabric by Layer 2 protocols (for example, LACP) on a switched LAN.

By default, an IRF fabric uses the bridge MAC address of the master as the IRF bridge MAC address. After the master leaves, the IRF bridge MAC address persists for a period of time or permanently depending on the IRF bridge MAC persistence setting. When the IRF bridge MAC persistence timer expires, the IRF fabric uses the bridge MAC address of the current master as the IRF bridge MAC address.

If IRF fabric merge occurs, IRF determines the IRF bridge MAC address of the merged IRF fabric as follows:

1. When IRF fabrics merge, IRF ignores the IRF bridge MAC addresses and checks the bridge MAC address of each member device in the IRF fabrics. IRF merge fails if any two member devices have the same bridge MAC address.

2. After IRF fabrics merge, the merged IRF fabric uses the bridge MAC address of the merging IRF fabric that won the master election as the IRF bridge MAC address.

Restrictions and guidelines

CAUTION:

The bridge MAC address change causes transient traffic disruption.

When you configure IRF bridge MAC persistence, follow these restrictions and guidelines:

· If the IRF fabric has multichassis aggregate links, do not use the undo irf mac-address persistent command. Use of this command might cause traffic disruption.

Configuring IRF bridge MAC persistence

1. Enter system view.

system-view

2. Configure IRF bridge MAC persistence.

¡ Retain the bridge MAC address permanently even if the address owner has left the fabric.

irf mac-address persistent always

¡ Retain the bridge MAC address for 6 minutes after the address owner leaves the fabric.

irf mac-address persistent timer

¡ Change the bridge MAC address as soon as the address owner leaves the fabric.

undo irf mac-address persistent

By default, the IRF bridge MAC address does not change after the address owner leaves.

The irf mac-address persistent timer command avoids unnecessary bridge MAC address changes caused by device reboot, transient link failure, or purposeful link disconnection.

Enabling software auto-update for software image synchronization

About this task

The software auto-update feature automatically propagates the software images of the global active MPU to all other MPUs (including new devices) in the IRF fabric.

To join an IRF fabric, an MPU must use the same software images as the global active MPU in the fabric.

When you add an MPU to the IRF fabric, software auto-update compares the startup software images of the MPU with the current software images of the IRF global active MPU. If the two sets of images are different, the MPU automatically performs the following operations:

1. Downloads the current software images of the global active MPU.

2. Sets the downloaded images as the main startup software images.

3. Reboots with the new software images to rejoin the IRF fabric.

You must manually update the new MPU with the software images running on the IRF fabric if software auto-update is disabled.

NOTE:

Use this feature in IRF mode. To synchronize software from the active MPU to the standby MPU in standalone mode, use the undo version check ignore and version auto-update enable commands. For more information about these commands, see Fundamentals Configuration Guide.

‌

Restrictions and guidelines

To ensure a successful software auto-update in a multi-user environment, prevent anyone from rebooting or swapping member devices or MPUs during the auto-update process. To inform administrators of the auto-update status, configure the information center to output the status messages to configuration terminals (see Network Management and Monitoring Configuration Guide).

Make sure the MPU you are adding to the IRF fabric has sufficient storage space for the new software images.

If sufficient storage space is not available, the MPU automatically deletes the current software images. If the reclaimed space is still insufficient, the MPU cannot complete the auto-update. You must reboot the device that holds the MPU, and then access the BootWare menu to delete files.

Procedure

1. Enter system view.

system-view

2. Enable software auto-update.

irf auto-update enable

By default, software auto-update is enabled.

Setting the IRF link down report delay

About this task

To prevent frequent IRF splits and merges during link flapping, configure the IRF ports to delay reporting link down events.

An IRF port does not report a link down event to the IRF fabric immediately after its link changes from up to down. If the IRF link state is still down when the delay is reached, the port reports the change to the IRF fabric.

IRF ports do not delay link up events. They report the link up event immediately after the IRF link comes up.

Restrictions and guidelines

Make sure the IRF link down report delay is shorter than the heartbeat or hello timeout settings of upper-layer protocols (for example, CFD and OSPF). If the report delay is longer than the timeout setting of a protocol, unnecessary recalculations might occur.

Set the delay to 0 seconds in the following situations:

· The IRF fabric requires a fast master/subordinate or IRF link switchover.

· The BFD or GR feature is used.

· You want to shut down an IRF physical interface or reboot an IRF member device. (After you complete the operation, reconfigure the delay depending on the network condition.)

Procedure

1. Enter system view.

system-view

2. Set the IRF link down report delay.

irf link-delay interval

By default, the IRF link down report delay is 1000 milliseconds.

Display and maintenance commands for IRF

Execute display commands in any view.

Task	Command
Display information about all IRF members.	display irf
Display the IRF fabric topology.	display irf topology
Display IRF link information.	display irf link
Display IRF configuration.	display irf configuration
Display the load sharing mode for IRF links.	display irf-port load-sharing mode [ irf-port [ member-id/irf-port-number ] ]
Display MAD configuration.	display mad [ verbose ]

‌

IRF configuration examples

The IRF configuration examples show how to set up IRF fabrics that use different MAD mechanisms.

Example: Configuring an LACP MAD-enabled two-chassis IRF fabric

Network configuration

As shown in Figure 13, set up a two-chassis IRF fabric at the access layer of the enterprise network.

Configure LACP MAD on the multichassis aggregation to Device C, which supports extended LACP.

Figure 13 Network diagram

‌

Analysis

To reduce the device reboot times when you set up an IRF fabric, use the following steps:

1. In standalone mode, complete IRF port configuration and other settings required for IRF setup.

2. Change the operating mode to IRF. Before the devices finish reboot, connect IRF physical interfaces. After the devices finish reboot, the IRF fabric is set up.

3. Configure MAD settings.

Restrictions and guidelines

If you change the operating mode to IRF before binding IRF physical interfaces to IRF ports, use the following steps to ensure successful IRF setup:

1. Configure IRF port settings and other required settings.

2. Execute the save command to save the running configuration.

3. Execute the irf-port-configuration active command to activate the IRF port settings.

Procedure

1. Set up IRF on Device A:

# Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 2.

<Sysname> system-view

[Sysname] irf member 1

[Sysname] irf-port 2

[Sysname-irf-port2] port group interface ten-gigabitethernet 2/0/1

[Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/1

[Sysname-irf-port2] quit

# Save the configuration.

[Sysname] quit

<Sysname> save

# Enable IRF mode.

<Sysname> system-view

[Sysname] chassis convert mode irf

The device will switch to IRF mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

2. Set up IRF on Device B:

# Assign member ID 2 to Device B, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 1.

<Sysname> system-view

[Sysname] irf member 2

[Sysname] irf-port 1

[Sysname-irf-port1] port group interface ten-gigabitethernet 2/0/1

[Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/1

[Sysname-irf-port1] quit

# Save the configuration.

[Sysname] quit

<Sysname> save

# Connect the two devices as shown in Figure 13.

# Log in to Device B. (Details not shown.)

# Enable IRF mode.

<Sysname> system-view

[Sysname] chassis convert mode irf

The device will switch to IRF mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device B and Device A form an IRF fabric after Device B reboots.

3. Configure LACP MAD on the IRF fabric:

# Assign domain ID 1 to the IRF fabric.

<Sysname> system-view

[Sysname] irf domain 1

# Create a dynamic aggregate interface and enable LACP MAD.

[Sysname] interface route-aggregation 2

[Sysname-Route-Aggregation2] link-aggregation mode dynamic

[Sysname-Route-Aggregation2] mad enable

You need to assign a domain ID (range: 0-4294967295)

[Current domain is: 1]:

The assigned domain ID is: 1

MAD LACP only enable on dynamic aggregation interface.

[Sysname-Route-Aggregation2] quit

# Assign Ten-GigabitEthernet 1/2/0/2 and Ten-GigabitEthernet 2/2/0/2 to the aggregate interface.

[Sysname] interface ten-gigabitethernet 1/2/0/2

[Sysname-Ten-GigabitEthernet1/2/0/2] port link-aggregation group 2

[Sysname-Ten-GigabitEthernet1/2/0/2] quit

[Sysname] interface ten-gigabitethernet 2/2/0/2

[Sysname-Ten-GigabitEthernet2/2/0/2] port link-aggregation group 2

4. Configure Device C as the intermediate device for LACP MAD:

CAUTION:

If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split.

# Create a dynamic aggregate interface.

<Sysname> system-view

[Sysname] interface route-aggregation 2

[Sysname-Route-Aggregation2] link-aggregation mode dynamic

[Sysname-Route-Aggregation2] quit

# Assign Ten-GigabitEthernet1/0/1 and Ten-GigabitEthernet1/0/2 to the aggregate interface.

[Sysname] interface ten-gigabitethernet 1/0/1

[Sysname-Ten-GigabitEthernet1/0/1] port link-aggregation group 2

[Sysname-Ten-GigabitEthernet1/0/1] quit

[Sysname] interface ten-gigabitethernet 1/0/2

[Sysname-Ten-GigabitEthernet1/0/2] port link-aggregation group 2

Example: Configuring a BFD MAD-enabled two-chassis IRF fabric

Network configuration

As shown in Figure 14, set up an IRF fabric at the distribution layer of the network.

· Configure BFD MAD in the IRF fabric and set up BFD MAD links between the member devices.

· Disable the spanning tree feature on the ports used for BFD MAD, because the two features conflict with each other.

· Assign the highest member priority to Device A so it can be elected the master.

Figure 14 Network diagram

‌

Analysis

To reduce the device reboot times when you set up an IRF fabric, use the following steps:

1. In standalone mode, complete IRF port configuration and other settings required for IRF setup.

2. Change the operating mode to IRF. Before the devices finish reboot, connect IRF physical interfaces. After the devices finish reboot, the IRF fabric is set up.

3. Configure MAD settings.

Restrictions and guidelines

If you change the operating mode to IRF before binding IRF physical interfaces to IRF ports, use the following steps to ensure successful IRF setup:

1. Configure IRF port settings and other required settings.

2. Execute the save command to save the running configuration.

3. Execute the irf-port-configuration active command to activate the IRF port settings.

Procedure

1. Set up IRF on Device A:

# Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 2.

<Sysname> system-view

[Sysname] irf member 1

[Sysname] irf-port 2

[Sysname-irf-port2] port group interface ten-gigabitethernet 2/0/1

[Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/1

[Sysname-irf-port2] quit

# Specify the priority of Device A as 10 to make sure it is elected as the master when the IRF fabric is established.

[DeviceA] irf priority 10

# Save the configuration.

[Sysname] quit

<Sysname> save

# Enable IRF mode.

<Sysname> system-view

[Sysname] chassis convert mode irf

The device will switch to IRF mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

2. Set up IRF on Device B:

# Assign member ID 2 to Device B, and bind Ten-GigabitEthernet 2/0/1 and Ten-GigabitEthernet 3/0/1 to IRF-port 1.

<Sysname> system-view

[Sysname] irf member 2

[Sysname] irf-port 1

[Sysname-irf-port1] port group interface ten-gigabitethernet 2/0/1

[Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/1

[Sysname-irf-port1] quit

# Save the configuration.

[Sysname] quit

<Sysname> save

# Connect the two devices as shown in Figure 14.

# Log in to Device B. (Details not shown.)

# Enable IRF mode.

<Sysname> system-view

[Sysname] chassis convert mode irf

The device will switch to IRF mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device B and Device A form an IRF after Device B reboots.

3. Configure BFD MAD on the IRF fabric:

# Create Route-Aggregation 1.

<Sysname> system-view

[Sysname] interface route-aggregation 1

[Sysname-Route-Aggregation1] quit

# Add Ten-GigabitEthernet 1/2/0/2 and Ten-GigabitEthernet 2/2/0/2 to the aggregation group.

[Sysname] interface ten-gigabitethernet 1/2/0/2

[Sysname-Ten-GigabitEthernet1/2/0/2] port link-aggregation group 1

[Sysname-Ten-GigabitEthernet1/2/0/2] quit

[Sysname] interface ten-gigabitethernet 2/2/0/2

[Sysname-Ten-GigabitEthernet2/2/0/2] port link-aggregation group 1

[Sysname-Ten-GigabitEthernet2/2/0/2] quit

# Assign a MAD IP address to each member device on the aggregate interface.

[Sysname] interface route-aggregation 1

[Sysname-Route-Aggregation1] mad bfd enable

[Sysname-Route-Aggregation1] mad ip address 192.168.2.1 24 member 1

[Sysname-Route-Aggregation1] mad ip address 192.168.2.2 24 member 2

[Sysname-Route-Aggregation1] quit

Example: Restoring standalone mode

Network configuration

Break the IRF fabric in Figure 15, and change the operating mode of Device A and Device B from IRF to standalone.

Figure 15 Network diagram

‌

Procedure

1. Identify the master.

<IRF> display irf

MemberID Slot Role Priority CPU-Mac Description

*+1 0 Master 1 00e0-fc0a-15e0 DeviceA

1 1 Standby 1 00e0-fc0f-8c02 DeviceA

2 0 Standby 1 00e0-fc0f-15e1 DeviceB

2 1 Standby 1 00e0-fc0f-15e2 DeviceB

--------------------------------------------------

* indicates the device is the master.

+ indicates the device through which the user logs in.

The Bridge MAC of the IRF is: 000f-e26a-58ed

Auto upgrade : no

Mac persistent : always

Domain ID : 0

The output shows that Device A is the master.

2. Examine the configuration for VLAN interfaces.

If a VLAN interface has member ports on different member devices, change the IP address for the interface on each device to be unique.

3. Shut down IRF physical interfaces to disconnect all IRF links. In this example, shut down Ten-Gigabitethernet 1/2/0/1 and Ten-GigabitEthernet 1/3/0/1.

<IRF> system-view

[IRF] interface range ten-gigabitethernet 1/2/0/1 ten-gigabitethernet 1/3/0/1

[IRF-if-range] shutdown

[IRF-if-range] quit

4. Save the configuration.

[IRF] save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait.....................................

The current configuration is saved to the active main board successfully.

Configuration is saved to device successfully.

5. Change the operating mode of Device A to standalone.

[IRF] undo chassis convert mode

The device will switch to stand-alone mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in stand-alone mode? [Y/N]:y

Now rebooting, please wait...

Device A automatically reboots to complete the operating mode change.

6. Log in to Device B and change its operating mode to standalone.

<IRF> system-view

[IRF] undo chassis convert mode

The device will switch to stand-alone mode and reboot.

You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

flash:/startup.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Slot 1:

Save next configuration file successfully.

Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in stand-alone mode? [Y/N]:y

Now rebooting, please wait...

Device B automatically reboots to complete the operating mode change.

02-Virtual Technologies Configuration Guide

Configuring an IRF fabric

Operating mode

IRF member roles

IRF member ID

MPU roles

Member priority

IRF port

IRF physical interface

IRF split

IRF merge

MAD

IRF domain ID

Detection

Command configuration restrictions

Suppressing SNMP notifications of packet drops on IRF physical interfaces

MDC

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Connecting IRF physical interfaces

About this task

Restrictions and guidelines

Prerequisites

Procedure

Assigning IRF domain IDs

Actions on interfaces shut down by MAD

Restrictions and guidelines for configuring BFD MAD

Configuring BFD MAD on a VLAN interface

Configuring BFD MAD on a Layer 3 aggregate interface

Configuring BFD MAD on a management Ethernet port

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Optimizing IRF settings for an IRF fabric

Restrictions and guidelines

Procedure

Changing the priority of a member device

About this task

Procedure

Adding physical interfaces to an IRF port

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Enabling IRF auto-merge

About this task

Procedure

About IRF link load sharing mode

Restrictions and guidelines for configuring IRF link load sharing mode

Configuring the global load sharing mode

Configuring a port-specific load sharing mode

About this task

Restrictions and guidelines

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Display and maintenance commands for IRF

Network configuration

Analysis

Restrictions and guidelines

Procedure

Network configuration

Analysis

Restrictions and guidelines

Procedure

Network configuration

Procedure