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.

The IRF port numbering rules are as follows:

· 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.

For simplicity, 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 merge

IRF merge occurs when two split IRF fabrics reunite or when two independent IRF fabrics are united, as shown in Figure 3.

Figure 3 IRF merge

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 a minimum of one MAD mechanism (see "Configuring MAD").

Figure 4 IRF split

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 or ring topology. As shown in Figure 6, a ring topology is more reliable. In ring topology, the failure of one IRF link does not cause the IRF fabric to split as in daisy-chain topology. Rather, the IRF fabric changes to a daisy-chain topology without interrupting network services.

Figure 6 Daisy-chain topology vs. ring topology

You can connect two distant IRF member devices through Layer 2 relay devices (for example, Layer 2 switches). The following are the available deployment methods:

· Set the binding mode to enhanced or extended when you bind physical interfaces to IRF ports that connect the two member devices, as shown in Figure 7.

· Assign each IRF physical link a unique VLAN to send and receive IRF packets, as shown in Figure 8. The VLANs are called IRF packet VLANs.

Figure 7 Deployment method (binding mode-based)

‌

Figure 8 Deployment method (VLAN-based)

‌

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 format of slot-number/subslot-number/interface-index.

For example, set the link type of Ten-GigabitEthernet 3/1/1 to trunk, as follows:

<Sysname> system-view

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

[Sysname-Ten-GigabitEthernet3/1/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, Ten-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 ten-gigabitethernet 1/2/0/1

[Sysname-Ten-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 to ensure that multiple devices in an IRF fabric can operate as a single device. Failure of the global active MPU does not affect the correct operation of the entire IRF fabric.

IRF supports bulk configuration synchronization and real-time configuration synchronization.

· Bulk configuration synchronization—This type of configuration synchronization occurs in the following situations:

¡ When a new device is added to the IRF fabric, the new device reboots as a subordinate device. During the reboot, the new device synchronizes the running configuration on the global active MPU to the local active MPU. However, the new device retains the following command settings on the local device and synchronizes the settings to the global active MPU:

- irf member description

- irf member priority

- irf-port

The configuration files on the new device are retained, but the files do not take effect. The device uses its own startup configuration files on its local active MPU only after it is removed from the IRF fabric.

¡ When the entire IRF fabric reboots, all member devices in the IRF fabric reboot. All subordinate devices obtain and run the running configuration of the global active MPU.

· Real-time configuration synchronization—When the IRF fabric is operating, configuration changes are automatically propagated from the global active MPU to the remaining MPUs.

Configuration synchronization ensures that all MPUs in an IRF fabric run consistent settings. When the master device or global active MPU fails, the remaining member devices or MPUs can run correctly.

Use the save all command as needed. With this command, IRF saves the running configuration to the storage medium on all MPUs to avoid configuration loss caused by IRF fabric reboot.

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 detecting a multi-active collision, MAD disables all IRF fabrics except one from forwarding data traffic by placing them in Recovery state. The IRF fabrics placed in Recovery state are called inactive IRF fabrics. The IRF fabric that continues to forward traffic is called the active IRF fabric.

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

1. Compare the health states of split fabrics.

2. Set all fabrics to the Recovery state except the healthiest one.

3. Compare the number of members in each fabric if all IRF fabrics are in the same health state..

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

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

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

7. 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 9. 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 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 9 Recovering the IRF fabric

‌

If the active IRF fabric fails before the IRF link is recovered (see Figure 10), 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 10 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 scenario
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. · No intermediate device is required. · 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. · If no intermediate device is used, any two IRF members must have a BFD MAD link to each other. · If an intermediate device is used, every IRF member must have a BFD MAD link to the intermediate device.	· No special requirements for network scenarios. · If no intermediate device is used, this mechanism is only suitable for IRF fabrics that have a small number of members that are geographically close to one another.

MAD mechanism

Advantages

Disadvantages

Application scenario

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.

· No intermediate device is required.

· 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.

· If no intermediate device is used, any two IRF members must have a BFD MAD link to each other.

· If an intermediate device is used, every IRF member must have a BFD MAD link to the intermediate device.

· No special requirements for network scenarios.

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

‌

LACP MAD

As shown in Figure 11, 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 11 LACP MAD scenario

‌

BFD MAD

BFD MAD detects multi-active collisions by using BFD. You can use common Ethernet ports to establish BFD MAD links.

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 the same VLAN used for BFD MAD. Each member device is assigned a MAD IP address on the VLAN interface.

The BFD MAD links and BFD MAD VLAN must be dedicated. Do not use the BFD MAD links or BFD MAD VLAN for any other purposes.

NOTE:

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

‌

Figure 12 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 13 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 12 BFD MAD scenario with an intermediate device

‌

Figure 13 BFD MAD scenario without an intermediate device

‌

Restrictions and guidelines: IRF configuration

Hardware compatibility with IRF

To establish an IRF fabric successfully, make sure the member device models, their IRF physical interfaces, and switching fabric modules meet the compatibility requirements in Table 2. For more information about IRF physical interface configuration restrictions, see "IRF physical interface configuration restrictions and guidelines."

Table 2 Hardware compatibility matrix for IRF establishment

Hardware platform

IRF members

MPU requirements

IRF physical interfaces

Switching fabric module requirements

CR16006-F, CR16010-F, CR16014-F, CR16010H-F, CR16018-F

Same model routers.

All member devices must use same model MPUs.

10-GE, 40-GE, or 100-GE Ethernet fiber ports on the following cards:

CSPEX-1304X, CSPEX-1404X, CSPEX-1504X, CSPEX-1602X, CSPEX-1804X, CSPEX-1612X, CEPC-XP24LX, CEPC-XP48RX, CEPC-CP4RX-L

All member devices must use same model switching fabric modules.

NOTE:

Do not use the CSFC-08T-G/16T-G, CSFC-16T1, CEPC-CQ8L, CSPEX-1802X, CSPEX-1812X-E, CEPC-CQ8LA, CEPC-CQ8L1A, CSPEX-1802XA, CSPEX-2612XA, or CEPC-CQ16L card on an IRF fabric. They can operate only on devices in standalone mode.

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.

MPU requirements for IRF

To form an IRF fabric, two devices must use the same MPU model.

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.

· 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.

· For high availability, bind multiple physical interfaces to an IRF port.

Figure 14 Connecting IRF physical interfaces

IRF physical interface configuration restrictions and guidelines

Grouped port binding restrictions

You can only select ports from among the candidate IRF physical interfaces listed in "Hardware compatibility with IRF" as IRF physical interfaces.

All IRF physical interfaces must be the same speed.

You must reboot an IRF connection card (a card that contains physical IRF interfaces) in the following situations:

· The first time you bind ports on the card to an IRF port, you must reboot the card for the bindings to take effect.

· To use the card as a regular I/O module to forward traffic after you disconnect all its IRF physical links and remove all its IRF port bindings, you must reboot the card.

Do not install WAN interface subcards on the cards used as IRF connection cards.

After you place the device in IRF mode, all Ethernet ports on the IRF connection cards automatically change to bridge mode and operate as Layer 2 interfaces.

When you replace a subcard on an IRF connection card in IRF mode, make sure the replacement subcard is the same model as the replaced subcard.

If you use a card as an IRF connection card, do not configure the ports on it for any other purposes than IRF connection and BFD MAD services.

IMPORTANT:

You can use the using tengige command to split the 40-GE port on the MIC-QP1L interface card into four 10-GE breakout interfaces. However, you cannot use these breakout interfaces as IRF physical interfaces.

‌

Command configuration restrictions

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

· Interface commands:

¡ description.

¡ flow-interval.

¡ priority-flow-control.

¡ priority-flow-control no-drop dot1p.

¡ shutdown.

For more information about these commands, see Interface Command Reference.

· LLDP commands:

¡ 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.

· Synchronous Ethernet commands, including:

¡ esmc enable.

¡ synce state.

¡ synchronous mode.

For more information about these commands, see synchronous Ethernet in Network Management and Monitoring Command Reference.

· The port service-loopback group command, which assigns the physical interface to a service loopback group. For more information about this command, see Layer 2—LAN Switching Command Reference.

‌

IMPORTANT:

Do not execute the port service-loopback group command on an IRF physical interface if that interface is the only member interface of an IRF port. Doing so will split the IRF fabric, because this command also removes the binding of the physical interface and IRF port.

‌

· The mirroring-group reflector-port command, which specifies the physical interface as the reflector port for remote mirroring. For more information about this command, see Network Management and Monitoring Command Reference.

‌

IMPORTANT:

Do not execute the mirroring-group reflector-port command on an IRF physical interface if that interface is the only member interface of an IRF port. Doing so will split the IRF fabric, because this command also removes the binding of the physical interface and IRF port.

‌

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

To form an IRF fabric, all member devices must use the same VLAN mode (set by using the system-vlan-mode command). For more information about setting the VLAN mode, see VLAN configuration in Layer 2—LAN Switching 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 quick IRF link detection interval for a relayed IRF fabric

g. Setting the operating mode to IRF mode

h. 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 bridge MAC address settings

¡ Enabling software auto-update for software image synchronization

This feature automatically propagates the software images of the global active MPU to all other MPUs in the IRF fabric.

¡ Setting the IRF link down report delay

¡ Setting the quick IRF link detection interval for a relayed IRF fabric

4. (Optional.) Fast-restoring IRF configuration for a one-MPU member

This task helps you fast-restore IRF configuration for one-MPU members before an MPU replacement.

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

If you are deploying a VLAN-based relayed IRF fabric, use the following restrictions and guidelines:

· You must specify an IRF packet VLAN for the IRF physical interfaces at the two ends of each IRF link. When you do that, follow these restrictions and guidelines:

¡ Specify a unique VLAN for each IRF physical link. Do not use these VLANs for any other purposes than transmitting IRF protocol packets.

¡ Make sure the two ends of each IRF physical link use the same VLAN ID.

· On the Layer 2 relay devices, you must configure the interfaces in the path of each IRF physical link as follows:

¡ Disable the spanning tree feature on these interfaces.

¡ The link type of these interfaces cannot be access.

¡ If the link type of an interface is trunk, make sure the interface permits the traffic from the IRF packet VLAN to pass through and the IRF packet VLAN is not the PVID of the trunk interface.

¡ If the link type of an interface is hybrid, make sure the hybrid interface is a tagged member of the IRF packet VLAN.

You can bind a maximum of 16 physical interfaces to an IRF port. The physical interfaces bound to the same IRF port can be distributed on a maximum of eight cards.

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 ] [ vlan vlan-id ]

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. A 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 [ safely ] [ backup | main ] [ force ]

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 quick IRF link detection interval for a relayed IRF fabric

About quick IRF link detection

Quick IRF link failure detection helps eliminate packet loss when IRF connections are established over Layer 2 relay devices between remote IRF member devices.

The quick IRF link failure detection mechanism tests the IRF links at specified intervals. If a member device has not received detection packets from its neighbor over an IRF link for three detection intervals, the member device determines that the IRF link has failed. Then, it reports the link failure to the CPU and switches traffic over to available IRF links.

The quick IRF link failure detection mechanism operates independently of the regular link state change detection mechanism on a port. The link down report delay set by using the irf link-delay command applies to the regular link state change detection mechanism, but it does not apply to the quick IRF link failure detection mechanism. If both mechanisms detect that the link is down, the port reports only the link down event reported by the quicker one of the two mechanisms.

Restrictions and guidelines

For the quick IRF link failure detection mechanism to operate correctly, you must specify a unique IRF packet VLAN for the physical interfaces of each IRF link when you execute the port group interface command.

As a best practice, set the quick IRF link detection interval to 10 milliseconds if the following intervals are set to 100 milliseconds:

Command	Interval description
bfd min-echo-receive-interval	The minimum interval for receiving BFD echo packets.
bfd min-transmit-interval bfd min-receive-interval	The minimum intervals for sending and receiving BFD single-hop control packets, respectively.
bfd multi-hop min-transmit-interval bfd multi-hop min-receive-interval	The minimum interval for sending and receiving BFD multi-hop control packets.

For more information about BFD, see High Availability Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Set the IRF link detection interval.

irf link-detect-time interval

By default, the IRF link failure detection interval is 100 milliseconds.

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.

Restrictions and guidelines

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. ‌

Prerequisites

Before you change the operating mode, verify that a unique IRF member ID has been assigned to the device. If you do not assign an IRF member ID to the device, the default IRF member ID (1) applies.

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.

Configuring MAD

Restrictions and guidelines for MAD configuration

Assigning IRF domain IDs

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

Actions on interfaces shut down by MAD

To prevent an interface from being shut down when the IRF fabric transits to the Recovery state, use the mad exclude interface command.

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.

To bring up the interfaces shut down by a MAD mechanism 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. When you do this, make sure there is no risk of multi-active collision.

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.

Configure BFD MAD on a VLAN interface if you use common Ethernet ports for BFD MAD.

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 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. · Do not assign IRF physical interfaces to the BFD MAD VLAN or use the Layer 2 Ethernet interfaces in the BFD MAD VLAN as IRF physical interfaces. · If you are using a VLAN-based IRF deployment over Layer 2 relay devices, you must execute the mad bfd dedicated command to specify the physical interfaces assigned to the BFD MAD VLAN on the IRF member devices as dedicated BFD MAD ports. In addition, do not use the BFD MAD VLAN on the relay devices for any purposes other than BFD MAD. · On the IRF fabric, member ports of the BFD MAD VLAN can be located on IRF-connect cards or non-IRF-connect cards, but not both. · If you use ports on the IRF connection cards for BFD MAD, you can assign only one Layer 2 Ethernet interface from each IRF-connect card to the BFD MAD VLAN.
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.

‌

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.

Do not enable BFD MAD on VLAN-interface 1.

Perform this step also on the intermediate device (if any).

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.

Perform this step also on the intermediate device (if any).

7. Configure the ports as dedicated BFD MAD ports.

mad bfd dedicated

By default, a Layer 2 Ethernet port is not BFD MAD dedicated.

This command helps avoid loops in the BFD MAD VLAN. Do not use this command on any ports except the ports used for BFD MAD. A dedicated BFD MAD port processes only BFD MAD packets with all other packets dropped.

8. Return to system view.

quit

9. Enter VLAN interface view.

interface vlan-interface vlan-interface-id

10. Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

11. 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 a VLAN interface.

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

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.

· Interfaces used for BFD MAD.

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

You can exclude an 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

When you configure this feature, follow these 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.

· Do not exclude the following interfaces from the shutdown action:

¡ Aggregate interfaces used for MAD and their member ports.

¡ VLAN interfaces used for MAD and the Ethernet ports in the VLANs.

Procedure

1. Enter system view.

system-view

2. Configure an 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 interfaces automatically excluded by the system. The automatically excluded interfaces include IRF physical interfaces.

Recovering an IRF fabric

About this task

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 for traffic forwarding. 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. When you perform this task, 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 ports) 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.

3. Save the running configuration.

save [ safely ] [ force ]

4. Reboot the member device.

In standalone mode:

reboot [ slot slot-number ] [ force ]

In IRF mode:

reboot chassis chassis-number

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

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

If you are deploying a VLAN-based relayed IRF fabric, use the following restrictions and guidelines:

· You must specify an IRF packet VLAN for the IRF physical interfaces at the two ends of each IRF link. When you do that, follow these restrictions and guidelines:

¡ Specify a unique VLAN for each IRF physical link. Do not use these VLANs for any other purposes than transmitting IRF protocol packets.

¡ Make sure the two ends of each IRF physical link use the same VLAN ID.

· On the Layer 2 relay devices, you must configure the interfaces in the path of each IRF physical link as follows:

¡ Disable the spanning tree feature on these interfaces.

¡ The link type of these interfaces cannot be access.

¡ If the link type of an interface is trunk, make sure the interface permits the traffic from the IRF packet VLAN to pass through and the IRF packet VLAN is not the PVID of the trunk interface.

¡ If the link type of an interface is hybrid, make sure the hybrid interface is a tagged member of the IRF packet VLAN.

You can bind a maximum of 16 physical interfaces to an IRF port. The physical interfaces bound to the same IRF port can be distributed on a maximum of eight cards.

Procedure

1. Enter system view.

system-view

2. 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 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

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 ] [ vlan vlan-id ]

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 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> ]

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:

· 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.

· A member device reboots immediately after you specify a new member ID for it. Make sure you are aware of the impact 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 bridge MAC address settings

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.

In special occasions that require a fixed special IRF bridge MAC address, you can specify that MAC address as the IRF bridge MAC address. For example, when you replace an IRF fabric as a whole, you can configure the new IRF fabric with the IRF bridge MAC address of the existing IRF fabric before the replacement to minimize service interruption.

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 for IRF bridge MAC address configuration

CAUTION:

Bridge MAC address change will cause transient traffic disruption.

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

· If the IRF fabric has upstream or downstream BFD sessions, do not disable IRF bridge MAC persistence by using the undo irf mac-address persistent command. Use of this command might cause BFD session flapping after an active/standby switchover.

· 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 fabric.

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

Specifying a MAC address as the IRF bridge MAC address

1. Enter system view.

system-view

2. Specify a MAC address as the IRF bridge MAC address.

irf mac-address mac-address

By default, an IRF fabric uses the bridge MAC address of the master as the IRF bridge MAC address.

If an IRF fabric splits after you configure the IRF bridge MAC address, both the split IRF fabrics use the configured bridge MAC address as the IRF bridge MAC address.

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 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:

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 Boot 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

If BFD is used in the IRF fabric, make sure the delay interval is shorter than the BFD session lifetime. For more information about BFD, see High Availability Configuration Guide.

The link down report delay applies to the regular link state change detection mechanism, but it does not apply to the quick IRF link failure detection mechanism on a relayed IRF fabric. If both mechanisms detect that the link is down, the port reports only the link down event reported by the quicker one of the two mechanisms. Quick IRF link failure detection is configurable with the irf link-detect-time command.

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 0 seconds.

Setting the quick IRF link detection interval for a relayed IRF fabric

About quick IRF link detection

Quick IRF link failure detection helps eliminate packet loss when IRF connections are established over Layer 2 relay devices between remote IRF member devices.

Restrictions and guidelines

As a best practice, set the quick IRF link detection interval to 10 milliseconds if the following intervals are set to 100 milliseconds:

Command	Interval description
bfd min-echo-receive-interval	The minimum interval for receiving BFD echo packets.
bfd min-transmit-interval bfd min-receive-interval	The minimum intervals for sending and receiving BFD single-hop control packets, respectively.
bfd multi-hop min-transmit-interval bfd multi-hop min-receive-interval	The minimum interval for sending and receiving BFD multi-hop control packets.

For more information about BFD, see High Availability Configuration Guide.

Procedure

1. Enter system view.

system-view

2. Set the IRF link detection interval.

irf link-detect-time interval

By default, the IRF link failure detection interval is 100 milliseconds.

Fast-restoring IRF configuration for a one-MPU member

About fast IRF configuration restoration

If a member device has only one MPU, you must reconfigure the basic IRF settings for the device after its MPU is damaged. Fast IRF configuration restoration helps you quickly restore the IRF configuration on a one-MPU member device by using a correctly operating member device.

The member device that assists in restoration is called the restoration assistant.

Restrictions and guidelines for fast IRF configuration restoration

Perform this task only for fast-restoring IRF configuration. This task might cause unknown errors in other application scenarios.

As a best practice, perform fast IRF configuration restoration in IRF mode.

The recovery procedure differs depending on the availability of a two-MPU restoration assistant.

Prerequisites for fast IRF configuration restoration

Save the .cfg configuration file on all MPUs in the IRF fabric.

Fast-restoring IRF configuration by using a two-MPU restoration assistant

1. Save the running configuration to the configuration file used at the next startup.

save [ safely ] [ force ]

2. On the assistant, execute the following commands in sequence to change the assistant's member ID on the standby MPU to be the same as that of the failed member device:

a. Enter system view.

system-view

b. Change the member ID on the standby MPU.

In standalone mode:

irf slot slot-number member member-id

In IRF mode:

irf chassis chassis-number slot slot-number member member-id

CAUTION:

Use this command only for fast-restoring IRF configuration. This task might cause unknown issues in other scenarios.

3. Replace the damaged MPU with the assistant's standby MPU.

Fast-restoring IRF configuration by using a one-MPU restoration assistant

1. Save the running configuration to the configuration file used at the next startup.

save [ safely ] [ force ]

2. Insert a new MPU into the idle MPU slot of the assistant. The inserted MPU operates in standby mode on the assistant.

3. Copy the configuration file from the assistant's active MPU to its standby MPU.

copy fileurl-source fileurl-dest

4. Set the configuration file for next startup on the assistant.

startup saved-configuration cfgfile

5. On the assistant, execute the following commands in sequence to change the assistant's member ID on the standby MPU to be the same as that of the failed member device:

a. Enter system view.

system-view

b. Change the member ID on the standby MPU.

In standalone mode:

irf slot slot-number member member-id

In IRF mode:

irf chassis chassis-number slot slot-number member member-id

CAUTION:

Use this command only for fast-restoring IRF configuration. This task might cause unknown issues in other scenarios.

6. Replace the damaged MPU with the assistant's standby MPU.

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 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 IRF fabric

Network configuration

As shown in Figure 15, use Device A and Device B to set up a two-chassis IRF fabric at the access layer.

To quickly detect and remove multi-active collision, configure LACP MAD on the multichassis aggregation to Device C, which supports extended LACP for MAD.

Figure 15 Network diagram

Restrictions and guidelines

This example binds physical interfaces to IRF ports when the devices operate in standalone mode. If you place the devices in IRF mode before you bind physical interfaces to IRF ports, you must also perform the following steps after you do IRF port binding to have the IRF fabric established:

1. Save the configuration.

2. Execute the irf-port-configuration active command to activate the configuration on the IRF ports.

Procedure

1. Configure Device A for IRF fabric establishment:

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

<DeviceA> system-view

[DeviceA] irf member 1

[DeviceA] interface ten-gigabitethernet 3/1/1

[DeviceA-Ten-GigabitEthernet3/1/1] port link-mode bridge

[DeviceA-Ten-GigabitEthernet3/1/1] quit

[DeviceA] irf-port 2

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

[DeviceA-irf-port2] quit

# Save the configuration.

[DeviceA] quit

<DeviceA> save

# Enable IRF mode.

<DeviceA> system-view

[DeviceA] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device A forms a single-chassis IRF fabric after it reboots.

2. Configure Device B for IRF fabric establishment:

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

<DeviceB> system-view

[DeviceB] irf member 2

[DeviceB] interface ten-gigabitethernet 3/1/1

[DeviceB-Ten-GigabitEthernet3/1/1] port link-mode bridge

[DeviceB-Ten-GigabitEthernet3/1/1] quit

[DeviceB] irf-port 1

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

[DeviceB-irf-port1] quit

# Save the configuration.

[DeviceB] quit

<DeviceB> save

# Connect the two devices, as shown in Figure 15.

# Enable IRF mode on Device B.

<DeviceB> system-view

[DeviceB] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device B reboots to join the IRF fabric. A two-chassis IRF fabric is formed.

3. Configure LACP MAD on the IRF fabric:

# Assign domain ID 1 to the IRF fabric.

<DeviceA> system-view

[DeviceA] irf domain 1

# Create a dynamic aggregate interface and enable LACP MAD.

[DeviceA] interface bridge-aggregation 2

[DeviceA-Bridge-Aggregation2] link-aggregation mode dynamic

[DeviceA-Bridge-Aggregation2] mad enable

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

[Current domain is: 0]: 1

The assigned domain ID is: 1

[DeviceA-Bridge-Aggregation2] quit

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

[DeviceA] interface ten-gigabitethernet 1/3/1/2

[DeviceA-Ten-GigabitEthernet1/3/1/2] port link-mode bridge

[DeviceA-Ten-GigabitEthernet1/3/1/2] port link-aggregation group 2

[DeviceA-Ten-GigabitEthernet1/3/1/2] quit

[DeviceA] interface ten-gigabitethernet 2/3/1/2

[DeviceA-Ten-GigabitEthernet2/3/1/2] port link-mode bridge

[DeviceA-Ten-GigabitEthernet2/3/1/2] port link-aggregation group 2

4. Configure Device C as the intermediate device:

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. This interface connects to the aggregate interface that is enabled with LACP MAD on the IRF fabric.

<DeviceC> system-view

[DeviceC] interface bridge-aggregation 2

[DeviceC-Bridge-Aggregation2] link-aggregation mode dynamic

[DeviceC-Bridge-Aggregation2] quit

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

[DeviceC] interface ten-gigabitethernet 3/1/1

[DeviceC-Ten-GigabitEthernet3/1/1] port link-mode bridge

[DeviceC-Ten-GigabitEthernet3/1/1] port link-aggregation group 2

[DeviceC-Ten-GigabitEthernet3/1/1] quit

[DeviceC] interface ten-gigabitethernet 3/1/2

[DeviceC-Ten-GigabitEthernet3/1/2] port link-mode bridge

[DeviceC-Ten-GigabitEthernet3/1/2] port link-aggregation group 2

Example: Configuring a BFD MAD-enabled IRF fabric

Network configuration

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

To quickly detect and remove multi-active collision, configure BFD MAD on the IRF fabric. Because the number of IRF member devices is limited, this example sets up BFD MAD links between the member devices.

Figure 16 Network diagram

Restrictions and guidelines

1. Save the configuration.

2. Execute the irf-port-configuration active command to activate the configuration on the IRF ports.

Procedure

1. Configure Device A for IRF fabric establishment:

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

<DeviceA> system-view

[DeviceA] irf member 1

[DeviceA] interface ten-gigabitethernet 3/1/1

[DeviceA-Ten-GigabitEthernet3/1/1] port link-mode bridge

[DeviceA-Ten-GigabitEthernet3/1/1] quit

[DeviceA] irf-port 2

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

[DeviceA-irf-port2] quit

# Save the configuration.

[DeviceA] quit

<DeviceA> save

# Enable IRF mode.

<DeviceA> system-view

[DeviceA] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device A forms a single-chassis IRF fabric after it reboots.

2. Configure Device B for IRF fabric establishment:

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

<DeviceB> system-view

[DeviceB] irf member 2

[DeviceB] interface ten-gigabitethernet 3/1/3

[DeviceB-Ten-GigabitEthernet3/1/3] port link-mode bridge

[DeviceB-Ten-GigabitEthernet3/1/3] quit

[DeviceB] irf-port 1

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

[DeviceB-irf-port1] quit

# Save the configuration.

[DeviceB] quit

<DeviceB> save

# Connect the two devices, as shown in Figure 16.

# Enable IRF mode.

<DeviceB> system-view

[DeviceB] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device B reboots to join the IRF fabric. A two-chassis IRF fabric is formed.

3. Configure BFD MAD on the IRF fabric:

# Create VLAN 3, add Ten-GigabitEthernet 1/4/1/1 and Ten-GigabitEthernet 2/4/1/1 to VLAN 3, disable the spanning tree feature on the ports, and configure the ports as dedicated BFD MAD ports.

<DeviceA> system-view

[DeviceA] vlan 3

[DeviceA-vlan3] quit

[DeviceA] interface ten-gigabitethernet 1/4/1/1

[DeviceA-Ten-GigabitEthernet1/4/1/1] port link-mode bridge

[DeviceA-Ten-GigabitEthernet1/4/1/1] port link-type trunk

[DeviceA-Ten-GigabitEthernet1/4/1/1] undo port trunk permit vlan 1

[DeviceA-Ten-GigabitEthernet1/4/1/1] port trunk permit vlan 3

[DeviceA-Ten-GigabitEthernet1/4/1/1] undo stp enable

[DeviceA-Ten-GigabitEthernet1/4/1/1] mad bfd dedicated

The interface will drop all packets except BFD MAD packets. Are you sure you want

to continue? [Y/N]:y

[DeviceA-Ten-GigabitEthernet1/4/1/1] quit

[DeviceA] interface ten-gigabitethernet 2/4/1/1

[DeviceA-Ten-GigabitEthernet2/4/1/1] port link-mode bridge

[DeviceA-Ten-GigabitEthernet2/4/1/1] port link-type trunk

[DeviceA-Ten-GigabitEthernet2/4/1/1] undo port trunk permit vlan 1

[DeviceA-Ten-GigabitEthernet2/4/1/1] port trunk permit vlan 3

[DeviceA-Ten-GigabitEthernet2/4/1/1] undo stp enable

[DeviceA-Ten-GigabitEthernet2/4/1/1] mad bfd dedicated

The interface will drop all packets except BFD MAD packets. Are you sure you want

to continue? [Y/N]:y

[DeviceA-Ten-GigabitEthernet2/4/1/1] quit

# Create VLAN-interface 3 and assign a MAD IP address to each member device on the VLAN interface.

[DeviceA] interface vlan-interface 3

[DeviceA-Vlan-interface3] mad bfd enable

[DeviceA-Vlan-interface3] mad ip address 192.168.2.1 24 member 1

[DeviceA-Vlan-interface3] mad ip address 192.168.2.2 24 member 2

[DeviceA-Vlan-interface3] quit

Example: Configuring a relayed IRF fabric

As shown in Figure 17, set up an IRF fabric of remote member devices (Device A and Device B) at the core layer. Use CEPC cards to connect the IRF member devices at Layer 2 through a relay device (Device C in this example).

To quickly detect and remove multi-active collision, configure BFD MAD on the IRF fabric. Because the number of member devices is limited, this example sets up BFD MAD links between the member devices.

Figure 17 Network diagram

Procedure

1. Configure Device A for IRF fabric establishment:

# Assign member ID 1 to Device A.

<DeviceA> system-view

[DeviceA] irf member 1

# Save the configuration.

[DeviceA] quit

<DeviceA> save

# Enable IRF mode.

<DeviceA> system-view

[DeviceA] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

Device A forms a single-chassis IRF fabric after it reboots.

# Bind Ten-GigabitEthernet 1/3/1/1 to IRF-port 1/2 and specify VLAN 10 as the IRF packet VLAN for the IRF link.

<DeviceA> system-view

[DeviceA] interface ten-gigabitEthernet 1/3/1/1

[DeviceA-Ten-GigabitEthernet1/3/1/1]port link-mode bridge

[DeviceA-Ten-GigabitEthernet1/3/1/1] shutdown

[DeviceA-Ten-GigabitEthernet1/3/1/1] quit

[DeviceA] irf-port 1/2

[DeviceA-irf-port1/2] port group interface ten-GigabitEthernet 1/3/1/1 vlan 10

[DeviceA-irf-port1/2] quit

# Bring up Ten-GigabitEthernet 1/3/1/1.

[DeviceA] interface ten-gigabitethernet 1/3/1/1

[DeviceA-Ten-GigabitEthernet1/3/1/1] undo shutdown

[DeviceA-Ten-GigabitEthernet1/3/1/1] quit

# Save the configuration.

[DeviceA] quit

<DeviceA> save

# Reboot the IRF connection card.

<DeviceA> reboot chassis 1 slot 3

This command will reboot the specified slot, Continue? [Y/N]:y

Now rebooting, please wait...

# Activate the IRF port configuration after the card changes to the normal state.

<DeviceA> system-view

[DeviceA] irf-port-configuration active

2. Configure Device B for IRF fabric establishment:

# Assign member ID 2 to Device B.

<DeviceB> system-view

[DeviceB] irf member 2

# Save the configuration.

[DeviceB] quit

<DeviceB> save

# Enable IRF mode.

<DeviceB> system-view

[DeviceB] chassis convert mode irf

The device will switch to IRF mode and reboot. Continue?[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/test.cfg]

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

cfa0:/test.cfg exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

test.cfg to make it available in IRF mode? [Y/N]:y

Now rebooting, please wait...

# Bind Ten-GigabitEthernet 2/3/1/1 to IRF-port 2/1 and specify VLAN 10 as the IRF packet VLAN for it. You must assign the physical interface to the same IRF packet VLAN as its peer interface.

<DeviceB> system-view

[DeviceB] interface Ten-GigabitEthernet 2/3/1/1

[DeviceB-Ten-GigabitEthernet2/3/1/1]port link-mode bridge

[DeviceB-Ten-GigabitEthernet2/3/1/1] shutdown

[DeviceB-Ten-GigabitEthernet2/3/1/1] quit

[DeviceB] irf-port 2/1

[DeviceB-irf-port2/1] port group interface Ten-GigabitEthernet 2/3/1/1 vlan 10

[DeviceB-irf-port2/1] quit

# Bring up Ten-GigabitEthernet 2/3/1/1.

[DeviceB] interface ten-gigabitethernet 2/3/1/1

[DeviceB-Ten-GigabitEthernet2/3/1/1] undo shutdown

[DeviceB-Ten-GigabitEthernet2/3/1/1] quit

# Save the configuration.

[DeviceB] quit

<DeviceB> save

# Reboot the IRF connection card.

<DeviceB> reboot chassis 2 slot 3

This command will reboot the specified slot, Continue? [Y/N]:y

Now rebooting, please wait...

# Activate the IRF port configuration after the card changes to the normal state.

<DeviceB> system-view

[DeviceB] irf-port-configuration active

3. Configure Device C as a relay device to provide Layer 2 connectivity between the remote IRF member devices:

# Create VLAN 10.

<DeviceC> system-view

[DeviceC] vlan 10

# Change the link mode of Ten-GigabitEthernet 4/1/1 and Ten-GigabitEthernet 4/1/2 to bridge, remove the ports from VLAN 1, assign them to VLAN 10, and disable the spanning tree feature on them.

[DeviceC] interface ten-gigabitethernet 4/1/1

[DeviceC-Ten-GigabitEthernet4/1/1] port link-mode bridge

[DeviceC-Ten-GigabitEthernet4/1/1] port link-type trunk

[DeviceC-Ten-GigabitEthernet4/1/1] undo port trunk permit vlan 1

[DeviceC-Ten-GigabitEthernet4/1/1] port trunk permit vlan 10

[DeviceC-Ten-GigabitEthernet4/1/1] undo stp enable

[DeviceC-Ten-GigabitEthernet4/1/1] quit

[DeviceC] int Ten-GigabitEthernet 4/1/2

[DeviceC-Ten-GigabitEthernet4/1/2] port link-mode bridge

[DeviceC-Ten-GigabitEthernet4/1/2] port link-type trunk

[DeviceC-Ten-GigabitEthernet4/1/2] undo port trunk permit vlan 1

[DeviceC-Ten-GigabitEthernet4/1/2] port trunk permit vlan 10

[DeviceC-Ten-GigabitEthernet4/1/2] undo stp enable

[DeviceC-Ten-GigabitEthernet4/1/2] quit

4. Configure BFD MAD on Device A and Device B:

# Create VLAN 20, add Ten-GigabitEthernet 1/3/1/2 on Device A and Ten-GigabitEthernet 2/3/1/2 on Device B to VLAN 20, disable the spanning tree feature on the ports, and configure the ports as dedicated BFD MAD ports.

<DeviceA> system-view

[DeviceA] vlan 20

[DeviceA-vlan20] quit

[DeviceA] interface ten-gigabitethernet 1/3/1/2

[DeviceA-Ten-GigabitEthernet1/3/1/2] port link-mode bridge

[DeviceA-Ten-GigabitEthernet1/3/1/2] port link-type trunk

[DeviceA-Ten-GigabitEthernet1/3/1/2] undo port trunk permit vlan 1

[DeviceA-Ten-GigabitEthernet1/3/1/2] port trunk permit vlan 20

[DeviceA-Ten-GigabitEthernet1/3/1/2] undo stp enable

[DeviceA-Ten-GigabitEthernet1/3/1/2] mad bfd dedicated

The interface will drop all packets except BFD MAD packets. Are you sure you want

to continue? [Y/N]:y

[DeviceA-Ten-GigabitEthernet1/3/1/2] quit

[DeviceA] interface ten-gigabitethernet 2/3/1/2

[DeviceA-Ten-GigabitEthernet2/3/1/2] port link-mode bridge

[DeviceA-Ten-GigabitEthernet2/3/1/2] port link-type trunk

[DeviceA-Ten-GigabitEthernet2/3/1/2] undo port trunk permit vlan 1

[DeviceA-Ten-GigabitEthernet2/3/1/2] port trunk permit vlan 20

[DeviceA-Ten-GigabitEthernet2/3/1/2] undo stp enable

[DeviceA-Ten-GigabitEthernet2/3/1/2] mad bfd dedicated

The interface will drop all packets except BFD MAD packets. Are you sure you want

to continue? [Y/N]:y

[DeviceA-Ten-GigabitEthernet1/3/1/2] quit

# Create VLAN-interface 20 and configure a MAD IP address for each member device on the VLAN interface.

[DeviceA] interface vlan-interface 20

[DeviceA-Vlan-interface3] mad bfd enable

[DeviceA-Vlan-interface3] mad ip address 192.168.2.1 24 member 1

[DeviceA-Vlan-interface3] mad ip address 192.168.2.2 24 member 2

[DeviceA-Vlan-interface3] quit

5. Configure Device C to assist in BFD MAD:

# Create VLAN 20.

<DeviceC> system-view

[DeviceC] vlan 20

# Set the link mode of Ten-GigabitEthernet 4/1/3 and Ten-GigabitEthernet 4/1/4 to bridge, remove the ports from VLAN 1, assign them to VLAN 20, and disable the spanning tree feature on them.

[DeviceC] interface ten-gigabitEthernet 4/1/3

[DeviceC-Ten-GigabitEthernet4/1/3] port link-mode bridge

[DeviceC-Ten-GigabitEthernet4/1/3] port link-type trunk

[DeviceC-Ten-GigabitEthernet4/1/3] undo port trunk permit vlan 1

[DeviceC-Ten-GigabitEthernet4/1/3] port trunk permit vlan 20

[DeviceC-Ten-GigabitEthernet4/1/3] undo stp enable

[DeviceC-Ten-GigabitEthernet4/1/3] quit

[DeviceC] interface ten-gigabitEthernet 4/1/4

[DeviceC-Ten-GigabitEthernet4/1/4] port link-mode bridge

[DeviceC-Ten-GigabitEthernet4/1/4] port link-type trunk

[DeviceC-Ten-GigabitEthernet4/1/4] undo port trunk permit vlan 1

[DeviceC-Ten-GigabitEthernet4/1/4] port trunk permit vlan 20

[DeviceC-Ten-GigabitEthernet4/1/4] undo stp enable

[DeviceC-Ten-GigabitEthernet4/1/4] quit

IRF merge occurs after Device A and Device B exchange IRF hello packets. The device that has failed master election automatically reboots to form an IRF fabric with the other device.

Example: Restoring standalone mode

Network configuration

Split the IRF fabric in Figure 18 and change the operating mode of Device A and Device B from IRF to standalone.

You can split an IRF fabric by removing the cables between all physical IRF interfaces or by shutting down the physical IRF interfaces from the CLI. This example uses the CLI-based method.

Figure 18 Network diagram

Analysis

You can split an IRF fabric by removing the cables between all physical IRF interfaces or by shutting down the physical IRF interfaces from the CLI. This example uses the CLI-based method.

Procedure

1. Identify the master.

<IRF> display irf

MemberID Slot Role Priority CPU-Mac Description

*+1 0 Master 1 00e0-fc0f-8c01 DeviceA

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

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

2 3 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: 0000-fc00-313e

Auto upgrade : no

Mac persistent : always

Domain ID : 1

Auto merge : no

The output shows that Device A is the master.

2. Identify the distribution of each VLAN interface's member ports on the member devices.

IMPORTANT:

If a VLAN interface has member ports on both member devices, change the IP address on one member device to be unique after you split the IRF fabric. This practice avoids the IP conflict that would occur if the devices were placed in standalone mode with their VLAN interfaces sharing the same IP address.

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

<IRF> system-view

[IRF] interface ten-gigabitethernet 1/3/1/1

[IRF-Ten-Gigabitethernet1/3/1/1] shutdown

[IRF-Ten-Gigabitethernet1/3/1/1] quit

4. Remove all IRF port bindings. In this example, remove Ten-GigabitEthernet 1/3/1/1 from IRF port 1/2.

[IRF] irf-port 1/2

[IRF-irf-port1/2] undo port group interface ten-gigabitethernet1/3/1/1

[IRF-irf-port1/2] quit

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. Continue?[Y/N]:

Before pressing ENTER you must choose 'YES' or 'NO'[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

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

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

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

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

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 remove all its IRF port bindings. In this example, shut down Ten-GigabitEthernet 2/3/1/1 and then remove it from IRF port 2/1.

<IRF> system-view

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

[IRF-Ten-Gigabitethernet2/3/1/1] shutdown

[IRF-Ten-Gigabitethernet2/3/1/1] quit

[IRF] irf-port 2/1

[IRF-irf-port2/1] undo port group interface ten-gigabitethernet2/3/1/1

[IRF-irf-port2/1] quit

7. Change the operating mode of Device B to standalone.

[IRF] undo chassis convert mode

The device will switch to stand-alone mode and reboot. Continue?[Y/N]:

Before pressing ENTER you must choose 'YES' or 'NO'[Y/N]:y

You are recommended to save the current running configuration and specify the co

nfiguration file for the next startup. Now save the running configuration to the

next-startup configuration file? [Y/N]:y

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

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

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

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

Do you want to convert the content of the next startup configuration file cfa0:/

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.

8. If Device A and Device B has VLAN interfaces with the same IP address, change the IP addresses of these VLAN interface to be unique.

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 merge

IRF split

MAD

IRF domain ID

Detection

Grouped port binding restrictions

Command configuration restrictions

Suppressing SNMP notifications of packet drops on IRF physical interfaces

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Connecting IRF physical interfaces

About quick IRF link detection

Procedure

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

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

Configuring IRF bridge MAC address settings

About this task

Restrictions and guidelines for IRF bridge MAC address configuration

Specifying a MAC address as the IRF bridge MAC address

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About quick IRF link detection

Restrictions and guidelines

Procedure

Display and maintenance commands for IRF

Network configuration

Restrictions and guidelines

Procedure

Example: Configuring a BFD MAD-enabled IRF fabric

Network configuration

Restrictions and guidelines

Procedure

Procedure

Example: Restoring standalone mode