02-IRF Configuration Guide

HomeSupportResource CenterSwitchesH3C S6300 Switch SeriesH3C S6300 Switch SeriesTechnical DocumentsConfigureConfiguration GuidesH3C S6300 Switch Series Configuration Guides-Release 243x-6W10002-IRF Configuration Guide
Table of Contents
Related Documents
01-IRF configuration
Title Size Download
01-IRF configuration 722.32 KB

Contents

Setting up an IRF fabric· 1

Overview· 1

Network topology· 2

Basic concepts· 2

Interface naming conventions· 4

File system naming conventions· 4

Configuration synchronization· 5

Master election· 5

Loop elimination mechanism·· 6

Multi-active handling procedure· 6

MAD mechanisms· 7

Hardware compatibility· 12

General restrictions and configuration guidelines· 12

Software requirements· 12

IRF physical interface requirements· 12

Connecting IRF ports· 14

Feature compatibility and configuration restrictions· 14

Licensing requirements· 14

Configuration backup· 14

Setup and configuration task list 14

Planning the IRF fabric setup· 15

Assigning a member ID to each IRF member device· 16

Specifying a priority for each member device· 16

Connecting IRF physical interfaces· 17

Binding physical interfaces to IRF ports· 17

Accessing the IRF fabric· 19

Configuring a member device description· 19

Configuring IRF link load sharing mode· 19

Configuration restrictions and guidelines· 20

Configuring the global load sharing mode· 20

Configuring a port-specific load sharing mode· 20

Configuring the IRF bridge MAC address· 21

Configuration restrictions and guidelines· 21

Specifying a MAC address as the IRF bridge MAC address· 22

Configuring IRF bridge MAC persistence· 22

Enabling software auto-update for software image synchronization· 23

Configuration prerequisites· 23

Configuration procedure· 23

Setting the IRF link down report delay· 23

Configuring MAD·· 24

Configuring LACP MAD·· 24

Configuring BFD MAD·· 25

Configuring ARP MAD·· 27

Configuring ND MAD·· 29

Excluding a port from the shutdown action upon detection of multi-active collision· 31

Recovering an IRF fabric· 31

Displaying and maintaining an IRF fabric· 32

Configuration examples· 33

LACP MAD-enabled IRF configuration example· 33

BFD MAD-enabled IRF configuration example· 37

ARP MAD-enabled IRF configuration example· 41

ND MAD-enabled IRF configuration example· 45

Setting up an IRF 3 system·· 51

Overview· 51

Basic concepts· 53

IRF 3 operating mechanisms· 54

Hardware compatibility· 55

Configuration restrictions and guidelines· 56

PEX physical interface requirements· 56

PEX cabling requirements· 56

Configuring the operating mode of the device· 56

Configuring the device as a PEX· 57

Configuring the device as an independent switch· 57

 

 


Setting up an IRF fabric

Overview

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.

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

 

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.

Network topology

An IRF fabric can use a daisy-chain or ring topology. IRF does not support the full mesh topology. For information about connecting IRF member devices, see "Connecting IRF physical interfaces."

Basic concepts

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. For more information about interface and file path naming, see "Interface naming conventions" and "File system naming conventions."

If two devices have the same IRF member ID, they cannot form an IRF fabric. If the IRF member ID of a device has been used in an IRF fabric, the device cannot join the fabric.

IRF port

An IRF port is a logical interface that connects IRF member devices. Every IRF-capable device supports two IRF ports. The IRF ports are named IRF-port n/1 and IRF-port n/2, where n is the member ID of the device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book.

To use an IRF port, you must bind a minimum of one physical interface to it. The physical interfaces assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down only if all its IRF physical interfaces are down.

IRF physical interface

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

For more information about physical interfaces that can be used for IRF links, see "IRF physical interface requirements."

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 2, IRF fabric 1 contains Device A and Device B, and IRF fabric 2 contains Device C and Device D. Both fabrics use the LACP aggregate links between them for MAD. When a member device receives an extended LACPDU for MAD, it checks the domain ID to see whether the packet is from the local IRF fabric. Then, the device can handle the packet correctly.

Figure 2 A network that contains two IRF domains

 

IRF split

IRF split occurs when an IRF fabric breaks up into multiple IRF fabrics because of IRF link failures, as shown in Figure 3. The split IRF fabrics operate with the same IP address. IRF split causes routing and forwarding problems on the network. To quickly detect a multi-active collision, configure a minimum of one MAD mechanism (see "Configuring MAD").

Figure 3 IRF split

 

IRF merge

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

Figure 4 IRF merge

 

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.

Interface naming conventions

An interface is named in the chassis-number/slot-number/port-index format.

·           chassis-number—IRF member ID of the switch. This argument defaults to 1. The IRF member ID always takes effect, whether or not the device has formed an IRF fabric with other devices. If the device is alone, the device is considered to be a one-chassis IRF fabric.

·           slot-numberSlot number of the front panel. This argument is fixed at 0.

·           port-index—Index of the port on the device. Port index depends on the number of ports available on the device. To identify the index of a port, examine its port index mark on the chassis.

For example:

·           On the single-chassis IRF fabric Sysname, Ten-GigabitEthernet 1/0/1 represents the first port on the device. Set its link type to trunk, as follows:

<Sysname> system-view

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

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

·           On the multichassis IRF fabric Master, Ten-GigabitEthernet 3/0/1 represents the first port on member device 3. Set its link type to trunk, as follows:

<Master> system-view

[Master] interface ten-gigabitethernet 3/0/1

[Master-Ten-GigabitEthernet3/0/1] port link-type trunk

File system naming conventions

On a single-chassis fabric, you can use its storage device name to access its file system.

On a multichassis IRF fabric, you can use the storage device name to access the file system of the master. To access the file system of a subordinate device, use the name in the slotmember-ID#storage-device-name format.

For example:

To access the test folder under the root directory of the flash memory on the master device:

<Master> mkdir test

Creating directory flash:/test... Done.

<Master> dir

Directory of flash:

   0 -rw-    43548660 Jan 01 2011 08:21:29   system.ipe

   1 drw-           - Jan 01 2011 00:00:30   diagfile

   2 -rw-         567 Jan 02 2011 01:41:54   dsakey

   3 -rw-         735 Jan 02 2011 01:42:03   hostkey

   4 -rw-          36 Jan 01 2011 00:07:52   ifindex.dat

   5 -rw-           0 Jan 01 2011 00:53:09   lauth.dat

   6 drw-           - Jan 01 2011 06:33:55   license

   7 drw-           - Jan 02 2000 00:00:07   logfile

   8 -rw-    23724032 Jan 01 2011 00:49:47   switch-cmw710-system.bin

   9 drw-           - Jan 01 2000 00:00:07   seclog

  10 -rw-         591 Jan 02 2011 01:42:03   serverkey

  11 -rw-        4609 Jan 01 2011 00:07:53   startup.cfg

  12 -rw-        3626 Jan 01 2011 01:51:56   startup.cfg_bak

  13 -rw-       78833 Jan 01 2011 00:07:53   startup.mdb

  14 drw-           - Jan 01 2011 00:15:48   test

  25 drw-           - Jan 01 2011 04:16:53   versionInfo

 

524288 KB total (365292 KB free)

To create and access the test folder under the root directory of the flash memory on member device 3:

<Master> mkdir slot3#flash:/test

Creating directory slot3#flash:/test... Done.

<Master> cd slot3#flash:/test

<Master> pwd

slot3#flash:/test

Or:

<Master> cd slot3#flash:/

<Master> mkdir test

Creating directory slot3#flash:/test... Done.

To copy the file test.ipe on the master to the root directory of the flash memory on member device 3:

# Display the current working path. In this example, the current working path is the root directory of the flash on member device 3.

<Master> pwd

slot3#flash:

# Change the current working path to the root directory of the flash memory on the master device.

<Master> cd flash:/

<Master> pwd

flash:

# Copy the file to member device 3.

<Master> copy test.ipe slot3#flash:/

Copy flash:/test.ipe to slot3#flash:/test.ipe?[Y/N]:y     

Copying file flash:/test.ipe to slot3#flash:/test.ipe... Done.

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

Configuration synchronization

IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all devices obtain and run the running configuration of the master. Any configuration change is automatically propagated from the master to the remaining devices. The configuration files of these devices are retained, but the files do not take effect. The devices use their own startup configuration files only after they are removed from the IRF fabric.

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

Master election

Master election occurs each time the IRF fabric topology changes in the following situations:

·           The IRF fabric is established.

·           The master device fails or is removed.

·           The IRF fabric splits.

·           Independent IRF fabrics merge.

 

 

NOTE:

Master election does not occur when two split IRF fabrics merge.

 

Master election selects a master in descending order:

1.      Current master, even if a new member has higher priority.

When an IRF fabric is being formed, all members consider themselves as the master. This rule is skipped.

2.      Member with higher priority. If all members have the same priority, this rule is skipped.

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.

Loop elimination mechanism

Loop control protocols such as the spanning tree protocols cannot be configured on IRF physical interfaces. However, IRF has its own mechanism to eliminate loops. Before an IRF member device forwards a packet, it identifies whether loops exist on the forwarding path based on the source and destination physical interfaces and the IRF topology. 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. When you use SNMP tools, do not monitor packet forwarding on the IRF physical interfaces to reduce SNMP notifications of packet drops.

Multi-active handling procedure

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

Detection

MAD identifies each IRF fabric with a domain ID and an active ID (the member ID of the master). If multiple active IDs are detected in a domain, MAD determines that an IRF collision or split has occurred.

For more information about the MAD mechanisms and their application scenarios, see "MAD mechanisms."

Collision handling

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

LACP MAD uses the following process to handle a multi-active collision:

1.      Compares the number of members in each fabric.

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

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

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

5.      Shuts down all physical network ports in the Recovery-state fabrics except for the following ports:

?  IRF physical interfaces.

?  Ports you have specified with the mad exclude interface command.

In contrast, BFD MAD, ARP MAD, and ND MAD do not compare the number of members in fabrics. These MAD mechanisms use the following process to hand a multi-active collision:

1.      Compare the member IDs of the masters in the IRF fabrics.

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

3.      Take the same action on the network ports in Recovery-state fabrics as LACP MAD.

Failure recovery

To merge two split IRF fabrics, first repair the failed IRF link and remove the IRF link failure.

·           If the IRF fabric in Recovery state fails before the failure is recovered, repair the failed IRF fabric and the failed IRF link.

·           If the active IRF fabric fails before the failure is recovered, enable the inactive IRF fabric to take over the active IRF fabric. Then, recover the MAD failure.

MAD mechanisms

IRF provides MAD mechanisms by extending LACP, BFD, ARP, and IPv6 ND. You can configure multiple MAD mechanisms on an IRF fabric.

·           Do not configure LACP MAD together with BFD MAD, ARP MAD, or ND MAD, because LACP MAD handles collisions differently than these MAD mechanisms.

·           Do not configure BFD MAD together with ARP MAD or ND MAD if common Ethernet ports are used for MAD. BFD MAD is mutually exclusive with the spanning tree feature, but ARP MAD and ND MAD require the spanning tree feature.

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.

·          Does not require 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.

For information about LACP, see Layer 2—LAN Switching Configuration Guide.

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.

For information about BFD, see High Availability Configuration Guide.

ARP MAD

·          No intermediate device is required.

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

·          Does not require MAD dedicated ports.

·          Detection speed is slower than BFD MAD and LACP MAD.

·          The spanning tree feature must be enabled if common Ethernet ports are used for ARP MAD links.

If common Ethernet ports are used, this MAD mechanism is applicable only to the spanning tree-enabled non-link aggregation IPv4 network scenario.

For information about ARP, see Layer 3—IP Services Configuration Guide.

ND MAD

·          No intermediate device is required.

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

·          Does not require MAD dedicated ports.

·          Detection speed is slower than BFD MAD and LACP MAD.

·          The spanning tree feature must be enabled.

Spanning tree-enabled non-link aggregation IPv6 network scenario.

 

LACP MAD

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

 

BFD MAD

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

·           If management Ethernet ports are used, BFD MAD must work with an intermediate device. Make sure the following requirements are met:

?  Each IRF member device has a BFD MAD link to the intermediate device.

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

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

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

?  Each member device is assigned a MAD IP address on a VLAN interface.

The BFD MAD links must be dedicated. Do not use BFD MAD links for any other purposes.

 

 

NOTE:

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

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

 

Figure 6 shows a typical BFD MAD scenario that uses an intermediate device. Figure 7 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 6 BFD MAD scenario with an intermediate device

 

Figure 7 BFD MAD scenario without an intermediate device

 

ARP MAD

ARP MAD detects multi-active collisions by using extended ARP packets that convey the IRF domain ID and the active ID.

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

·           If management Ethernet ports are used, ARP MAD must work with an intermediate device. Make sure the following requirements are met:

?  Connect the management Ethernet port on each member device to the intermediate device.

?  On the intermediate device, you must assign the ports used for ARP MAD to the same VLAN.

·           If common Ethernet ports are used, ARP MAD can work with or without an intermediate device. Make sure the following requirements are met:

?  If an intermediate device is used, connect each IRF member device to the intermediate device. Run the spanning tree feature between the IRF fabric and the intermediate device. In this situation, data links can be used.

?  If an intermediate device is not used, connect each IRF member device to all other member devices. In this situation, IRF links cannot be used for ARP MAD.

Figure 8 shows a typical ARP MAD scenario that uses an intermediate device.

Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID.

·           If the domain IDs are different, the extended ARP packet is from a different IRF fabric. The device does not continue to process the packet with the MAD mechanism.

·           If the domain IDs are the same, the device compares the active IDs.

?  If the active IDs are different, the IRF fabric has split.

?  If the active IDs are the same, the IRF fabric is integrated.

Figure 8 ARP MAD scenario

 

ND MAD

ND MAD detects multi-active collisions by using NS packets to transmit the IRF domain ID and the active ID.

You can set up ND MAD links between neighbor IRF member devices or between each IRF member device and an intermediate device (see Figure 9). If an intermediate device is used, you must also run the spanning tree protocol between the IRF fabric and the intermediate device.

Each IRF member device compares the domain ID and the active ID in incoming NS packets with its domain ID and active ID.

·           If the domain IDs are different, the NS packet is from a different IRF fabric. The device does not continue to process the packet with the MAD mechanism.

·           If the domain IDs are the same, the device compares the active IDs.

?  If the active IDs are different, the IRF fabric has split.

?  If the active IDs are the same, the IRF fabric is integrated.

Figure 9 ND MAD scenario

 

Hardware compatibility

An H3C S6300 switch can form an IRF fabric only with devices in the same series.

General restrictions and configuration guidelines

For a successful IRF setup, follow the restrictions and guidelines in this section and the setup procedure in "Setup and configuration task list."

Software requirements

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

IRF physical interface requirements

Use the following ports as IRF physical interfaces:

·           10GBase-T Ethernet ports.

·           SFP+ ports.

·           QSFP+ ports.

Selecting transceiver modules and cables

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

·           Use Category 6A (or above) twisted-pair cables to connect 10GBase-T Ethernet ports in a short distance.

·           Use SFP+, QSFP+, or QSFP+ to SFP+ DAC cables to connect SFP+ or QSFP+ ports in a short distance.

·           Use SFP+ or QSFP+ transceiver modules and fibers to connect SFP+ or QSFP+ ports in a long distance.

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

For more information about the SFP+ and QSFP+ transceiver modules, see the switch installation guide and H3C Transceiver Modules User Guide.

 

 

NOTE:

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

 

10GBase-T Ethernet port restrictions for the S6300-42QT switch

When you use the 10GBase-T Ethernet ports on the S6300-42QT switch as IRF physical interfaces, follow these restrictions and guidelines:

·           The 10GBase-T Ethernet ports are grouped by port number in order, starting from 1. Each group contains four ports. If you use one port in a group for IRF links, you must also use all the other ports in the group for IRF links. However, you can bind the ports to different IRF ports.

·           Before you bind a 10GBase-T Ethernet port to an IRF port or remove it from the IRF port, you must shut down all the 10GBase-T Ethernet ports in the same group.

·           Bring up the ports after you complete the operation.

QSFP+ port restrictions for the S6300 switch

You can use a QSFP+ port as an IRF physical interface, or use the breakout SFP+ ports of the QSFP+ port as IRF physical interfaces. To use the breakout SFP+ ports, you must use the using tengige command to split the QSFP+ port into four 10-GE breakout interfaces.

When you use the breakout interfaces of a 40-GE port for IRF links, follow these restrictions and guidelines:

·           You must use all or none of the four 10-GE breakout interfaces as IRF physical interfaces. The four breakout interfaces can be bound to different IRF ports.

·           Before you bind one 10-GE breakout interface to an IRF port or remove it from the IRF port, you must shut down all the other 10-GE breakout interfaces. If any of the breakout interfaces are in up state, the bind or remove action will fail.

·           Bring up the breakout interfaces after you complete the operation.

SFP+ port restrictions for the S6300-42QF, S6300-48S, and S6300-52QF switches

When you use the SFP+ ports on the S6300-42QF, S6300-48S, or S6300-52QF switch as IRF physical interfaces, follow these restrictions and guidelines:

·           The SFP+ ports are grouped by port number in order, starting from 1. Each group contains four ports. If you use one port in a group for IRF links, you must also use all the other ports in the group for IRF links. However, you can bind the ports to different IRF ports.

·           Before you bind an SFP+ port to an IRF port or remove it from the IRF port, you must shut down all the SFP+ ports in the same group.

·           Bring up the ports after you complete the operation.

Connecting IRF ports

When you connect two neighboring IRF members, connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of IRF-port 2 on the other.

Feature compatibility and configuration restrictions

Make sure all member devices use the same system operating mode set by using the system-working-mode command. For more information about system operating modes, see Fundamentals Configuration Guide.

Licensing requirements

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

Configuration backup

Back up the next-startup configuration file on a device before adding the device to an IRF fabric as a subordinate device.

A subordinate device's next-startup configuration file might be overwritten if the master and the subordinate use the same file name for their next-startup configuration files. You can use the backup file to restore the original configuration after removing the subordinate from the IRF fabric.

Setup and configuration task list

As a best practice, use the basic IRF setup procedure in Figure 10. Perform the tasks in this figure on each member device.

Figure 10 Basic IRF setup flow chart

 

To set up an IRF fabric, perform the following tasks:

 

Tasks at a glance

Remarks

1.      (Required.) Planning the IRF fabric setup

N/A

2.      (Required.) Assigning a member ID to each IRF member device

Perform this task on each member device.

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

Perform this task on one or multiple member devices to affect the master election result.

4.      (Required.) Connecting IRF physical interfaces

N/A

5.      (Required.) Binding physical interfaces to IRF ports

Perform this task on each member device.

When you complete IRF port binding and activation on all IRF member devices, the IRF fabric is formed.

6.      (Required.) Accessing the IRF fabric

When you log in to the IRF fabric, you are placed at the master's CLI, where you complete subsequent IRF settings and configure other features for the member devices as if they were one device.

7.      (Optional.) Configuring a member device description

N/A

8.      (Optional.) Configuring IRF link load sharing mode:

?  Configuring the global load sharing mode

?  Configuring a port-specific load sharing mode

N/A

9.      (Optional.) Configuring the IRF bridge MAC address

?  Specifying a MAC address as the IRF bridge MAC address

?  Configuring IRF bridge MAC persistence

N/A

10.   (Optional.) Enabling software auto-update for software image synchronization

As a best practice, enable software auto-update to ensure system software image synchronization.

11.   (Optional.) Setting the IRF link down report delay

N/A

12.   (Required.) Configuring MAD:

?  Configuring LACP MAD

?  Configuring BFD MAD

?  Configuring ARP MAD

?  Configuring ND MAD

?  Excluding a port from the shutdown action upon detection of multi-active collision

MAD mechanisms are independent of one another. You can configure multiple MAD mechanisms for an IRF fabric.

13.   (Optional.) Recovering an IRF fabric

N/A

 

Planning the IRF fabric setup

Consider the following items when you plan an IRF fabric:

·           Hardware compatibility and restrictions.

·           IRF fabric size.

·           Master device.

·           IRF physical interfaces.

·           Member ID and priority assignment scheme.

·           Fabric topology and cabling scheme.

For more information about hardware and cabling, see the switch installation guide.

Assigning a member ID to each IRF member device

CAUTION

CAUTION:

In an IRF fabric, changing IRF member IDs might cause undesirable configuration changes and even data loss. Before you do that, back up the configuration and make sure you fully understand the impact on your network. For example, all member devices in an IRF fabric are the same model. If you swapped the IDs of any two members, their interface settings would also be swapped.

 

To create an IRF fabric, you must assign a unique IRF member ID to each member device.

To prevent any undesirable configuration change or data loss, avoid changing member IDs after the IRF fabric is formed.

The new member ID takes effect at a 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.

To assign a member ID to a device:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Assign a member ID to a member device.

irf member member-id renumber new-member-id

The default IRF member ID is 1.

3.      (Optional.) Save the configuration.

save

If you have bound physical interfaces to IRF ports or assigned member priority, save the configuration before rebooting the device so these settings can continue to take effect after the reboot.

4.      Reboot the device.

reboot [ slot slot-number ] [ force ]

N/A

 

Specifying a priority for each member device

IRF member priority represents the possibility for a device to be elected the master in an IRF fabric. The higher the priority, the higher the possibility.

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

To specify a priority for a member device:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Specify a priority for the device.

irf member member-id priority priority

The default IRF member priority is 1.

 

Connecting IRF physical interfaces

When you connect two neighboring IRF members, connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of IRF-port 2 on the other (see Figure 11).

For example, you have four chassis: A, B, C, and D. IRF-port 1 and IRF-port 2 are represented by A1 and A2 on chassis A, represented by B1 and B2 on chassis B, and so on. To connect the four chassis into a ring topology of A-B-C-D(A), the IRF link cabling scheme must be one of the following:

·           A1-B2, B1-C2, C1-D2, and D1-A2.

·           A2-B1, B2-C1, C2-D1, and D2-A1.

 

IMPORTANT

IMPORTANT:

No intermediate devices are allowed between neighboring members.

 

Figure 11 Connecting IRF physical interfaces

 

Connect the devices into a daisy-chain topology or a ring topology. A ring topology is more reliable (see Figure 12). 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 12 Daisy-chain topology vs. ring topology

 

Binding physical interfaces to IRF ports

When you bind physical interfaces to IRF ports, follow these guidelines:

·           Follow the restrictions in "IRF physical interface requirements."

·           You must always shut down a physical interface before binding it to an IRF port or removing the binding. Start the shutdown operation on the master, and then the member device that has the fewest number of hops from the master.

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

·           Interface commands:

?  description.

?  flow-interval.

?  priority-flow-control.

?  shutdown.

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

To bind physical interfaces to IRF ports:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter interface view or interface range view.

·          Enter interface range view:
interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

·          Enter interface view:
interface interface-type interface-number

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

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

3.      Shut down the interface or the range of interfaces.

shutdown

By default, all interfaces are up.

4.      Return to system view.

quit

N/A

5.      Enter IRF port view.

irf-port member-id/port-number

N/A

6.      Bind each physical interface to the IRF port.

port group interface interface-type interface-number

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

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

You can bind up to eight physical interfaces to an IRF port.

7.      Return to system view.

quit

N/A

8.      Enter interface view or interface range view.

·          Enter interface range view:
interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

·          Enter interface view:
interface interface-type interface-number

N/A

9.      Bring up the interface or the range of interfaces.

undo shutdown

N/A

10.   Return to system view.

quit

N/A

11.   Save the 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 IRF port settings.

irf-port-configuration active

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

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

 

Accessing the IRF fabric

The IRF fabric appears as one device after it is formed. You configure and manage all IRF members at the CLI of the master. All settings you have made are automatically propagated to the IRF members.

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.

When you log in to an IRF fabric, you are placed at the CLI of the master, regardless of at which member device you are logged in.

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

Configuring a member device description

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Configure a description for a member device.

irf member member-id description text

By default, no member device description is configured.

 

Configuring IRF link load sharing mode

An IRF port distributes traffic across its physical links.

By default, traffic is distributed automatically based on packet types, including Layer 2, IPv4, and IPv6. You can configure the IRF port to distribute traffic based on criteria including IP addresses, MAC addresses, and the combination of IP and MAC addresses. If the device does not support a criterion combination, the system displays an error message.

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

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

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

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

The IRF link load sharing mode takes effect on all types of packets, including unicast, multicast, and broadcast.

Configuration restrictions and guidelines

To distribute traffic based on TCP/UDP ports, use one of the following methods:

·           Use the default setting for both global and port-specific IRF link load sharing modes.

·           Set the IRF link load sharing mode and the global load sharing mode for Ethernet link aggregation as follows:

?  Set the IRF link load sharing mode to distribute traffic based on source IP, destination IP, or both source and destination IP addresses. The command syntax is irf-port load-sharing mode { destination-ip | source-ip } *.

?  Set the global load sharing mode for Ethernet link aggregation to distribute traffic based on source service port, destination service port, or both source and destination service ports. The command syntax is link-aggregation global load-sharing mode { destination-port | source-port } *. For more information about Ethernet link aggregation load sharing, see Layer 2—LAN Switching Configuration Guide.

Configuring the global load sharing mode

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Configure the global IRF link load sharing mode.

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

By default, packets are distributed automatically across IRF member links based on packet types.

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

 

Configuring a port-specific load sharing mode

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

To configure a port-specific load sharing mode for an IRF port:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enter IRF port view.

irf-port member-id/port-number

N/A

3.      Configure the port-specific load sharing mode.

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

By default, packets are distributed automatically across IRF member links based on packet types.

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

 

Configuring the IRF bridge MAC address

CAUTION

CAUTION:

The bridge MAC address change causes transient traffic disruption.

 

Use this feature to configure the bridge MAC address of an IRF fabric. Layer 2 protocols, such as LACP, use the IRF bridge MAC address to identify an IRF fabric. On a switched LAN, the bridge MAC address must be unique.

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

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

The following methods are available to configure the IRF bridge MAC address for an IRF fabric:

·           Specifying a MAC address as the IRF bridge MAC address.

The IRF fabric always uses the specified IRF bridge MAC address unless you specify another IRF bridge MAC address or IRF bridge MAC persistence takes effect.

·           Configuring IRF bridge MAC persistence.

This feature specifies the amount of time an IRF fabric can continue using a MAC address as the IRF bridge MAC address after the address owner leaves. By default, the bridge MAC address of the master device becomes the IRF bridge MAC address upon the setup of the IRF fabric.

Configuration restrictions and guidelines

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

·           The IRF bridge MAC persistence feature does not take effect if you specify the IRF bridge MAC address by using the irf mac-address mac-address command.

·           If ARP MAD or ND MAD is used, you must disable IRF bridge MAC persistence by using the undo irf mac-address persistent command. In addition, do not specify a MAC address as the IRF bridge MAC address..

·           Configure the irf mac-address persistent always command or the irf mac-address mac-address command in the following situations:

?  TRILL is used. The bridge MAC address setting avoids unnecessary traffic disruption caused by IRF bridge MAC address changes on the TRILL network.

?  The IRF fabric uses a daisy-chain topology, and it has aggregate links with upstream or downstream devices. The bridge MAC address setting prevents transmission delay or packet loss after the address owner leaves.

Specifying a MAC address as the IRF bridge MAC address

You can specify the bridge MAC address of an existing IRF fabric for a new IRF fabric to replace the existing IRF fabric with transient packet loss.

To specify a MAC address as the IRF bridge MAC address:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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

 

Configuring IRF bridge MAC persistence

Depending on the network condition, enable the IRF fabric to retain or change its bridge MAC address after the address owner leaves. Available options include:

·           irf mac-address persistent timerBridge MAC address of the IRF fabric remains unchanged for 6 minutes after the address owner leaves. If the owner does not return before the timer expires, the IRF fabric uses the bridge MAC address of the current master as its bridge MAC address. This option avoids unnecessary bridge MAC address changes caused by device reboot, transient link failure, or purposeful link disconnection.

·           irf mac-address persistent alwaysBridge MAC address of the IRF fabric does not change after the address owner leaves.

·           undo irf mac-address persistent—Bridge MAC address of the current master replaces the original one as soon as the owner of the original bridge MAC leaves.

To configure the IRF bridge MAC persistence setting:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Configure IRF bridge MAC persistence.

·          Retain the bridge MAC address permanently even if the owner has left the IRF fabric:
irf mac-address persistent always

·          Retain the bridge MAC address for 6 minutes after the owner leaves the fabric:
irf mac-address persistent timer

·          Change the bridge MAC address as soon as the owner leaves the fabric:
undo irf mac-address persistent

By default, the IRF bridge MAC address remains unchanged for 6 minutes after the address owner leaves the fabric.

 

Enabling software auto-update for software image synchronization

IMPORTANT

IMPORTANT:

To ensure a successful software auto-update in a multi-user environment, prevent anyone from rebooting member devices 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).

 

The software auto-update feature synchronizes the current software images of the master in an IRF fabric to all its members automatically.

To join an IRF fabric, a device must use the same software images as the master in the fabric.

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

1.      Downloads the current software images of the master.

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

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

You must manually update the new device with the software images running on the IRF fabric in the following situations:

·           Software auto-update is disabled.

·           Software auto-update fails to update software. This situation might occur if the IRF fabric cannot identify the software version used on the new device.

Configuration prerequisites

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

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

Configuration procedure

To enable software image synchronization:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Enable software auto-update.

irf auto-update enable

By default, software auto-update is enabled.

 

Setting the IRF link down report delay

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.

When you configure the IRF link down report delay, follow these restrictions and guidelines:

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

·           Set the delay to 0 seconds in the following situations:

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

?  The BFD or GR feature is used.

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

To set the IRF link down report delay:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Set the IRF link down report delay.

irf link-delay interval

The default IRF link down report delay is 4 seconds.

 

Configuring MAD

When you configure MAD, follow these restrictions and guidelines:

·           You can configure multiple MAD mechanisms on an IRF fabric for prompt IRF split detection.

?  Do not configure LACP MAD together with BFD MAD, ARP MAD, or ND MAD, because they handle collisions differently.

?  Do not configure BFD MAD together with ARP MAD or ND MAD if common Ethernet ports are used for MAD. BFD MAD is mutually exclusive with the spanning tree feature, but ARP MAD and ND MAD require the spanning tree feature.

·           If LACP MAD, ARP MAD, or ND 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 following commands: irf domain, mad enable, mad arp enable, or mad nd enable. The IRF domain IDs configured by using these commands overwrite each other.

·           To prevent a port from being shut down when the IRF fabric transits to the Recovery state, use the mad exclude interface command. To bring up ports in a Recovery-state IRF fabric, use the mad restore command instead of the undo shutdown command. The mad restore command activates the Recovery-state IRF fabric.

Configuring LACP MAD

When you use LACP MAD, follow these guidelines:

·           The intermediate device must be a device that supports extended LACP for MAD.

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

·           Use dynamic link aggregation mode. MAD is LACP dependent. Even though LACP MAD can be configured on both static and dynamic aggregate interfaces, it takes effect only on dynamic aggregate interfaces.

·           Configure link aggregation settings on the intermediate device.

To configure LACP MAD:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Assign a domain ID to the IRF fabric.

irf domain domain-id

The default IRF domain ID is 0.

3.      Create a Layer 2 aggregate interface and enter Layer 2 aggregate interface view.

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

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

N/A

7.      Enter Ethernet interface view or interface range view.

·          Enter interface range view:
interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

·          Enter Ethernet interface view:
interface interface-type interface-number

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 number

Multichassis link aggregation is allowed.

Also perform this step on the intermediate device.

 

Configuring BFD MAD

Before you configure BFD MAD, choose a BFD MAD link scheme as described in "BFD MAD."

As a best practice, connect the BFD MAD links after you finish the BFD MAD configuration.

Configuring BFD MAD that uses common Ethernet ports

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

When you use 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 both the IRF fabric and the intermediate device:

?  Create a VLAN and VLAN interface for BFD MAD.

?  Assign the ports of BFD MAD links to 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 the port is not on the BFD MAD link. For example, if you have assigned the port to all VLANs by using the port trunk permit vlan all command, use the undo port trunk permit command to exclude the 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.

·          Configure only the mad bfd enable and mad ip address commands on the VLAN interface used for BFD MAD. If you configure other features, both BFD MAD and other features on the interface might run incorrectly.

·          Disable the spanning tree feature on all Layer 2 Ethernet ports in the BFD MAD VLAN. The MAD feature is mutually exclusive with the spanning tree feature.

MAD IP address

·          Use the mad ip address command instead of the ip address command to configure MAD IP addresses on the BFD MAD-enabled VLAN interface.

·          Make sure all the MAD IP addresses are on the same subnet.

 

To configure BFD MAD that uses common Ethernet ports:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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.

3.      Create a VLAN dedicated to BFD MAD.

vlan vlan-id

The default VLAN on the device is VLAN 1.

4.      Return to system view.

quit

N/A

5.      Enter interface view or interface range view.

·          Enter interface range view:
interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24>

·          Enter interface view:
interface interface-type interface-number

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 port to the VLAN as an access port:
port access vlan vlan-id

·          Assign the port to the VLAN as a trunk port:
port trunk permit vlan
vlan-id

·          Assign the port to the VLAN as a hybrid port:
port hybrid vlan
vlan-id { tagged | untagged }

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

The default link type of a port is access.

7.      Return to system view.

quit

N/A

8.      Create the VLAN interface and enter VLAN interface view.

interface vlan-interface vlan-interface-id

N/A

9.      Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

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

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

By default, no MAD IP address is configured for an IRF member device on a VLAN interface.

 

Configuring BFD MAD that uses management Ethernet ports

When you configure BFD MAD that uses management Ethernet ports, follow these restrictions and guidelines:

 

Category

Restrictions and guidelines

Ports on the intermediate device for BFD MAD

Use common Ethernet ports on the intermediate device to connect to the BFD MAD-enabled management Ethernet ports on the IRF fabric.

BFD MAD VLAN

·          On the intermediate device, create a VLAN for BFD MAD, and assign the ports used for BFD MAD to the VLAN. On the IRF fabric, you do not need to assign the BFD MAD-enabled management Ethernet ports to the VLAN.

·          Make sure the IRF fabrics on the network use different BFD MAD VLANs.

·          Make sure the BFD MAD VLAN on the intermediate device contains only ports on the BFD MAD links. Exclude a port from the BFD MAD VLAN if the port is not on the BFD MAD link. For example, if you have assigned the port to all VLANs by using the port trunk permit vlan all command, use the undo port trunk permit command to exclude the port from the BFD MAD VLAN.

MAD IP address

·          Use the mad ip address command instead of the ip address command to configure MAD IP addresses on the BFD MAD-enabled management Ethernet ports.

·          Make sure all the MAD IP addresses are on the same subnet.

 

To configure BFD MAD that uses management Ethernet ports:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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.

3.      Enter management Ethernet interface view.

interface m-gigabitethernet interface-number

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

4.      Enable BFD MAD.

mad bfd enable

By default, BFD MAD is disabled.

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

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

By default, no MAD IP address is configured for an IRF member device.

 

Configuring ARP MAD

Before you configure ARP MAD, choose an ARP MAD link scheme as described in "ARP MAD."

As a best practice, connect the ARP MAD links after you finish the ARP MAD configuration if you are not using existing data links as ARP MAD links.

Configuring ARP MAD that uses common Ethernet ports

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

When you configure ARP MAD that uses common Ethernet ports, follow these restrictions and guidelines:

 

Category

Restrictions and guidelines

ARP MAD VLAN

·          Do not enable ARP MAD on VLAN-interface 1.

·          If you are using an intermediate device, perform the following tasks on both the IRF fabric and the intermediate device:

?  Create a VLAN and VLAN interface for ARP MAD.

?  Assign the ports of ARP MAD links to the ARP MAD VLAN.

·          Do not use the ARP MAD VLAN for any other purposes.

ARP MAD and feature configuration

If an intermediate device is used, make sure the following requirements are met:

·          Run the spanning tree feature between the IRF fabric and the intermediate device to ensure that there is only one ARP MAD link in forwarding state. For more information about the spanning tree feature and its configuration, see Layer 2—LAN Switching Configuration Guide.

·          Enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

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

 

To configure ARP MAD that uses common Ethernet ports:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Assign a domain ID to the IRF fabric.

irf domain domain-id

The default IRF domain ID is 0.

3.      Configure the IRF bridge MAC address to change as soon as the address owner leaves.

undo irf mac-address persistent

By default, the IRF bridge MAC address remains unchanged for 6 minutes after the address owner leaves.

4.      Create a VLAN dedicated to ARP MAD.

vlan vlan-id

The default VLAN on the device is VLAN 1.

5.      Return to system view.

quit

N/A

6.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

7.      Assign the port to the ARP MAD VLAN.

·          Assign the port to the VLAN as an access port:
port access vlan vlan-id

·          Assign the port to the VLAN as a trunk port:
port trunk permit vlan
vlan-id

·          Assign the port to the VLAN as a hybrid port:
port hybrid vlan
vlan-id { tagged | untagged }

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

The default link type of a port is access.

8.      Return to system view.

quit

N/A

9.      Create the VLAN interface and enter VLAN interface view.

interface vlan-interface vlan-interface-id

N/A

10.   Assign the interface an IP address.

ip address ip-address { mask | mask-length }

By default, no IP address is assigned to a VLAN interface.

11.   Enable ARP MAD.

mad arp enable

By default, ARP MAD is disabled.

 

Configuring ARP MAD that uses management Ethernet ports

When you configure ARP MAD that uses management Ethernet ports, follow these restrictions and guidelines:

 

Category

Restrictions and guidelines

Ports on the intermediate device for ARP MAD

Use common Ethernet ports on the intermediate device to connect the management Ethernet ports on the IRF fabric.

ARP MAD VLAN

On the intermediate device, create a VLAN for ARP MAD, and assign the ports used for ARP MAD to the VLAN. On the IRF fabric, you do not need to assign the management Ethernet ports to the VLAN.

ARP MAD and feature configuration

·          Enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

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

 

To configure ARP MAD that uses management Ethernet ports:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Assign a domain ID to the IRF fabric.

irf domain domain-id

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

3.      Configure the IRF bridge MAC address to change as soon as the address owner leaves.

undo irf mac-address persistent

By default, the IRF bridge MAC address remains unchanged for 6 minutes after the address owner leaves.

4.      Enter management Ethernet interface view.

interface m-gigabitethernet interface-number

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

5.      Assign an IP address to the management Ethernet ports.

ip address ip-address { mask | mask-length }

By default, no IP addresses are configured.

6.      Enable ARP MAD.

mad arp enable

By default, ARP MAD is disabled.

 

Configuring ND MAD

When you use ND MAD, follow these guidelines:

·           Do not configure ND MAD on VLAN-interface 1.

·           Do not use the VLAN configured for ND MAD for any other purpose.

·           If an intermediate device is used, you can use common data links as ND MAD links. If no intermediate device is used, set up dedicated ND MAD links between IRF member devices.

·           If an intermediate device is used, make sure the following requirements are met:

?  Run the spanning tree feature between the IRF fabric and the intermediate device. Make sure there is only one ND MAD link in forwarding state. For more information about the spanning tree feature and its configuration, see Layer 2—LAN Switching Configuration Guide.

?  Enable the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

?  Create an ND MAD VLAN and assign the ports on the ND MAD links to the VLAN.

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

To configure ND MAD:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Assign a domain ID to the IRF fabric.

irf domain domain-id

The default IRF domain ID is 0.

3.      Configure the IRF bridge MAC address to change as soon as the address owner leaves.

undo irf mac-address persistent

By default, the IRF bridge MAC address remains unchanged for 6 minutes after the address owner leaves.

4.      Create a VLAN dedicated to ND MAD.

vlan vlan-id

The default VLAN on the device is VLAN 1.

5.      Return to system view.

quit

N/A

6.      Enter Ethernet interface view.

interface interface-type interface-number

N/A

7.      Assign the port to the ND MAD VLAN.

·          Assign the port to the VLAN as an access port:
port access vlan vlan-id

·          Assign the port to the VLAN as a trunk port:
port trunk permit vlan
vlan-id

·          Assign the port to the VLAN as a hybrid port:
port hybrid vlan
vlan-id { tagged | untagged }

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

The default link type of a port is access.

8.      Return to system view.

quit

N/A

9.      Create the VLAN interface and enter VLAN interface view.

interface vlan-interface vlan-interface-id

N/A

10.   Assign the interface an IP address.

ipv6 address { ipv6-address/pre-length | ipv6 address pre-length }

By default, no IPv6 address is assigned to a VLAN interface.

11.   Enable ND MAD.

mad nd enable

By default, ND MAD is disabled.

 

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

CAUTION

CAUTION:

Do not exclude a VLAN interface and its Layer 2 ports from the shutdown action if the Layer 2 ports are distributed on multiple member devices. The exclusion introduces IP collision risks because the VLAN interface might be up on both active and inactive IRF fabrics.

 

By default, all ports (except for the console and IRF physical interfaces) shut down automatically when the IRF fabric transits to the Recovery state.

You can exclude a network port 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.

To configure a port to not shut down when the IRF fabric transits to the Recovery state:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

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

mad exclude interface interface-type interface-number

By default, all ports on a Recovery-state IRF fabric are shut down, except for the IRF physical interfaces and console port.

 

Recovering an IRF fabric

When the failed IRF link between two split IRF fabrics is recovered, all member devices in the inactive IRF fabric automatically join the active IRF fabric as subordinate members. The network ports that have been shut down by MAD automatically restore their original physical state, as shown in Figure 13.

Figure 13 Recovering the IRF fabric

 

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

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

 

To manually recover an inactive IRF fabric:

 

Step

Command

1.      Enter system view.

system-view

2.      Recover the inactive IRF fabric.

mad restore

 

After the IRF fabric is recovered, all ports that have been shut down by MAD come up automatically.

Displaying and maintaining an IRF fabric

Execute display commands in any view.

 

Task

Command

Display information about all IRF members.

display irf

Display the IRF fabric topology.

display irf topology

Display IRF link information.

display irf link

Display IRF configuration.

display irf configuration

Display the load sharing mode for IRF links.

display irf-port load-sharing mode [ irf-port [ member-id/port-number ] ]

Display MAD configuration.

display mad [ verbose ]

 

Configuration examples

This section provides IRF configuration examples for IRF fabrics that use different MAD mechanisms.

LACP MAD-enabled IRF configuration example

Network requirements

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

Configure LACP MAD on the multichassis aggregation to Device E, an H3C device that supports extended LACP.

Figure 15 Network diagram

 

Configuration procedure

1.      Configure Device A:

# Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.

[Sysname] irf-port 1/1

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

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

[Sysname-irf-port1/1] quit

# Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF-port 1/2.

[Sysname] irf-port 1/2

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

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

[Sysname-irf-port1/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

2.      Configure Device B:

# Change the member ID of Device B to 2 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 2

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device B to Device A as shown in Figure 15, and log in to Device B. This example uses the SFP+ group that contains Ten-GigabitEthernet 2/0/45 to Ten-GigabitEthernet 2/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 2/0/47 and Ten-GigabitEthernet 2/0/48 to IRF-port 2/1.

[Sysname] irf-port 2/1

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

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

[Sysname-irf-port2/1] quit

# Bind Ten-GigabitEthernet 2/0/45 and Ten-GigabitEthernet 2/0/46 to IRF-port 2/2.

[Sysname] irf-port 2/2

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

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

[Sysname-irf-port2/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master.

3.      Configure Device C:

# Change the member ID of Device C to 3 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 3

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device C to Device A as shown in Figure 15, and log in to Device C. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1.

[Sysname] irf-port 3/1

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

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

[Sysname-irf-port3/1] quit

# Bind Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to IRF-port 3/2.

[Sysname] irf-port 3/2

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/45

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/46

[Sysname-irf-port3/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device C reboots to join the IRF fabric.

4.      Configure Device D:

# Change the member ID of Device D to 4 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 4

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device D to Device B and Device C as shown in Figure 15, and log in to Device D. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 4/0/45 and Ten-GigabitEthernet 4/0/46 to IRF-port 4/1.

[Sysname] irf-port 4/1

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/45

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46

[Sysname-irf-port4/1] quit

# Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2.

[Sysname] irf-port 4/2

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48

[Sysname-irf-port4/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device D reboots to join the IRF fabric. A four-chassis IRF fabric is formed.

5.      Configure LACP MAD on the IRF fabric:

# Set the domain ID of the IRF fabric to 1.

<Sysname> system-view

[Sysname] irf domain 1

# Create a dynamic aggregate interface and enable LACP MAD.

[Sysname] interface bridge-aggregation 2

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

[Sysname-Bridge-Aggregation2] mad enable

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

[Current domain is: 1]:

 The assigned  domain ID is: 1

 Info: MAD LACP only enable on dynamic aggregation interface.

[Sysname-Bridge-Aggregation2] quit

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

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

[Sysname-if-range] port link-aggregation group 2

[Sysname-if-range] quit

6.      Configure Device E 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.

<Sysname> system-view

[Sysname] interface bridge-aggregation 2

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

[Sysname-Bridge-Aggregation2] quit

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

[Sysname] interface range ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[Sysname-if-range] port link-aggregation group 2

[Sysname-if-range] quit

BFD MAD-enabled IRF configuration example

Network requirements

As shown in Figure 16, set up a four-chassis IRF fabric at the core layer of the enterprise network.

·           Configure BFD MAD in the IRF fabric and set up BFD MAD links between each member device and the intermediate device.

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

Figure 16 Network diagram

 

 

Configuration procedure

1.      Configure Device A:

# Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.

[Sysname] irf-port 1/1

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

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

[Sysname-irf-port1/1] quit

# Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF-port 1/2.

[Sysname] irf-port 1/2

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

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

[Sysname-irf-port1/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

2.      Configure Device B:

# Change the member ID of Device B to 2 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 2

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device B to Device A as shown in Figure 16, and log in to Device B. This example uses the SFP+ group that contains Ten-GigabitEthernet 2/0/45 to Ten-GigabitEthernet 2/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 2/0/47 and Ten-GigabitEthernet 2/0/48 to IRF-port 2/1.

[Sysname] irf-port 2/1

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

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

[Sysname-irf-port2/1] quit

# Bind Ten-GigabitEthernet 2/0/45 and Ten-GigabitEthernet 2/0/46 to IRF-port 2/2.

[Sysname] irf-port 2/2

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

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

[Sysname-irf-port2/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master.

3.      Configure Device C:

# Change the member ID of Device C to 3 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 3

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device C to Device A as shown in Figure 16, and log in to Device C. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1.

[Sysname] irf-port 3/1

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

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

[Sysname-irf-port3/1] quit

# Bind Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to IRF-port 3/2.

[Sysname] irf-port 3/2

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/45

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/46

[Sysname-irf-port3/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device C reboots to join the IRF fabric.

4.      Configure Device D:

# Change the member ID of Device D to 4 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 4

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device D to Device B and Device C as shown in Figure 16, and log in to Device D. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 4/0/45 and Ten-GigabitEthernet 4/0/46 to IRF-port 4/1.

[Sysname] irf-port 4/1

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/45

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46

[Sysname-irf-port4/1] quit

# Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2.

[Sysname] irf-port 4/2

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48

[Sysname-irf-port4/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device D reboots to join the IRF fabric. A four-chassis IRF fabric is formed.

5.      Configure BFD MAD on the IRF fabric:

# Create VLAN 3, and add Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 2/0/1, Ten-GigabitEthernet 3/0/1, and Ten-GigabitEthernet 4/0/1 to VLAN 3.

[Sysname] vlan 3

[Sysname-vlan3] port ten-gigabitethernet 1/0/1 ten-gigabitethernet 2/0/1 ten-gigabitethernet 3/0/1 ten-gigabitethernet 4/0/1

[Sysname-vlan3] quit

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

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] mad bfd enable

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

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

[Sysname-Vlan-interface3] mad ip address 192.168.2.3 24 member 3

[Sysname-Vlan-interface3] mad ip address 192.168.2.4 24 member 4

[Sysname-Vlan-interface3] quit

# Disable the spanning tree feature on Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 2/0/1, Ten-GigabitEthernet 3/0/1, and Ten-GigabitEthernet 4/0/1.

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

[Sysname-if-range] undo stp enable

[Sysname-if-range] quit

6.      Configure Device E as the intermediate device:

 

CAUTION

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 VLAN 3, and assign Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 1/0/3, and Ten-GigabitEthernet 1/0/4 to VLAN 3 for forwarding BFD MAD packets.

<DeviceE> system-view

[DeviceE] vlan 3

[DeviceE-vlan3] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[DeviceE-vlan3] quit

ARP MAD-enabled IRF configuration example

Network requirements

As shown in Figure 17, set up a four-chassis IRF fabric in the enterprise network.

·           Configure ARP MAD in the IRF fabric and use the links connected to Device E for transmitting ARP MAD packets.

·           To prevent loops, run the spanning tree feature between Device E and the IRF fabric.

Figure 17 Network diagram

 

Configuration procedure

1.      Configure Device A:

# Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.

[Sysname] irf-port 1/1

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

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

[Sysname-irf-port1/1] quit

# Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF-port 1/2.

[Sysname] irf-port 1/2

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

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

[Sysname-irf-port1/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

2.      Configure Device B:

# Change the member ID of Device B to 2 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 2

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device B to Device A as shown in Figure 17, and log in to Device B. This example uses the SFP+ group that contains Ten-GigabitEthernet 2/0/45 to Ten-GigabitEthernet 2/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 2/0/47 and Ten-GigabitEthernet 2/0/48 to IRF-port 2/1.

[Sysname] irf-port 2/1

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

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

[Sysname-irf-port2/1] quit

# Bind Ten-GigabitEthernet 2/0/45 and Ten-GigabitEthernet 2/0/46 to IRF-port 2/2.

[Sysname] irf-port 2/2

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

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

[Sysname-irf-port2/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master.

3.      Configure Device C:

# Change the member ID of Device C to 3 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 3

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device C to Device A as shown in Figure 17, and log in to Device C. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1.

[Sysname] irf-port 3/1

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

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

[Sysname-irf-port3/1] quit

# Bind Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to IRF-port 3/2.

[Sysname] irf-port 3/2

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/45

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/46

[Sysname-irf-port3/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device C reboots to join the IRF fabric.

4.      Configure Device D:

# Change the member ID of Device D to 4 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 4

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device D to Device B and Device C as shown in Figure 17, and log in to Device D. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 4/0/45 and Ten-GigabitEthernet 4/0/46 to IRF-port 4/1.

[Sysname] irf-port 4/1

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/45

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46

[Sysname-irf-port4/1] quit

# Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2.

[Sysname] irf-port 4/2

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48

[Sysname-irf-port4/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device D reboots to join the IRF fabric. A four-chassis IRF fabric is formed.

5.      Configure ARP MAD on the IRF fabric:

# Enable the spanning tree feature globally. Map the ARP MAD VLAN to MSTI 1 in the MST region.

<Sysname> system-view

[Sysname] stp global enable

[Sysname] stp region-configuration

[Sysname-mst-region] region-name arpmad

[Sysname-mst-region] instance 1 vlan 3

[Sysname-mst-region] active region-configuration

[Sysname-mst-region] quit

# Configure the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

[Sysname] undo irf mac-address persistent

# Set the domain ID of the IRF fabric to 1.

[Sysname] irf domain 1

# Create VLAN 3, and assign Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 2/0/1, Ten-GigabitEthernet 3/0/2, and Ten-GigabitEthernet 4/0/1 to VLAN 3.

[Sysname] vlan 3

[Sysname-vlan3] port ten-gigabitethernet 1/0/2 ten-gigabitethernet 2/0/1 ten-gigabitethernet 3/0/2 ten-gigabitethernet 4/0/1

[Sysname-vlan3] quit

# Create VLAN-interface 3, assign it an IP address, and enable ARP MAD on the interface.

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] ip address 192.168.2.1 24

[Sysname-Vlan-interface3] mad arp enable

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

 [Current domain is: 1]:

 The assigned  domain ID is: 1

6.      Configure Device E as the intermediate device:

 

CAUTION:

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

 

# Enable the spanning tree feature globally. Map the ARP MAD VLAN to MSTI 1 in the MST region.

<DeviceE> system-view

[DeviceE] stp global enable

[DeviceC] stp region-configuration

[DeviceC-mst-region] region-name arpmad

[DeviceC-mst-region] instance 1 vlan 3

[DeviceC-mst-region] active region-configuration

[DeviceC-mst-region] quit

# Create VLAN 3, and assign ports Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 1/0/3, and Ten-GigabitEthernet 1/0/4 to VLAN 3 for forwarding ARP MAD packets.

[DeviceE] vlan 3

[DeviceE-vlan3] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[DeviceE-vlan3] quit

ND MAD-enabled IRF configuration example

Network requirements

As shown in Figure 18, set up a four-chassis IRF fabric in the IPv6 enterprise network.

·           Configure ND MAD in the IRF fabric and use the links connected to Device E for transmitting ND MAD packets.

·           To prevent loops, run the spanning tree feature between Device E and the IRF fabric.

Figure 18 Network diagram

 

Configuration procedure

1.      Configure Device A:

# Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.

[Sysname] irf-port 1/1

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

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

[Sysname-irf-port1/1] quit

# Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF-port 1/2.

[Sysname] irf-port 1/2

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

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

[Sysname-irf-port1/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

2.      Configure Device B:

# Change the member ID of Device B to 2 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 2

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device B to Device A as shown in Figure 18, and log in to Device B. This example uses the SFP+ group that contains Ten-GigabitEthernet 2/0/45 to Ten-GigabitEthernet 2/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 2/0/47 and Ten-GigabitEthernet 2/0/48 to IRF-port 2/1.

[Sysname] irf-port 2/1

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

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

[Sysname-irf-port2/1] quit

# Bind Ten-GigabitEthernet 2/0/45 and Ten-GigabitEthernet 2/0/46 to IRF-port 2/2.

[Sysname] irf-port 2/2

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

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

[Sysname-irf-port2/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 2/0/45 to ten-gigabitethernet 2/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master.

3.      Configure Device C:

# Change the member ID of Device C to 3 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 3

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device C to Device A as shown in Figure 18, and log in to Device C. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1.

[Sysname] irf-port 3/1

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

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

[Sysname-irf-port3/1] quit

# Bind Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to IRF-port 3/2.

[Sysname] irf-port 3/2

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/45

[Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/46

[Sysname-irf-port3/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device C reboots to join the IRF fabric.

4.      Configure Device D:

# Change the member ID of Device D to 4 and reboot the device to validate the change.

<Sysname> system-view

[Sysname] irf member 1 renumber 4

Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y

[Sysname] quit

<Sysname> reboot

# Connect Device D to Device B and Device C as shown in Figure 18, and log in to Device D. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 for IRF links.

# Shut down the physical interfaces.

<Sysname> system-view

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] shutdown

[Sysname-if-range] quit

# Bind Ten-GigabitEthernet 4/0/45 and Ten-GigabitEthernet 4/0/46 to IRF-port 4/1.

[Sysname] irf-port 4/1

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/45

[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46

[Sysname-irf-port4/1] quit

# Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2.

[Sysname] irf-port 4/2

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47

[Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48

[Sysname-irf-port4/2] quit

# Bring up the SFP+ ports and save the configuration.

[Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48

[Sysname-if-range] undo shutdown

[Sysname-if-range] quit

[Sysname] save

# Activate the IRF port configuration.

[Sysname] irf-port-configuration active

Device D reboots to join the IRF fabric. A four-chassis IRF fabric is formed.

5.      Configure ND MAD on the IRF fabric:

# Enable the spanning tree feature globally. Map the ND MAD VLAN to MSTI 1 in the MST region.

<Sysname> system-view

[Sysname] stp global enable

[Sysname] stp region-configuration

[Sysname-mst-region] region-name ndmad

[Sysname-mst-region] instance 1 vlan 3

[Sysname-mst-region] active region-configuration

[Sysname-mst-region] quit

# Configure the IRF fabric to change its bridge MAC address as soon as the address owner leaves.

[Sysname] undo irf mac-address persistent

# Set the domain ID of the IRF fabric to 1.

[Sysname] irf domain 1

# Create VLAN 3, and add Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 2/0/1, Ten-GigabitEthernet 3/0/2, and Ten-GigabitEthernet 4/0/1 to VLAN 3.

[Sysname] vlan 3

[Sysname-vlan3] port ten-gigabitethernet 1/0/2 ten-gigabitethernet 2/0/1 ten-gigabitethernet 3/0/2 ten-gigabitethernet 4/0/1

[Sysname-vlan3] quit

# Create VLAN-interface 3, assign it an IPv6 address, and enable ND MAD on the interface.

[Sysname] interface vlan-interface 3

[Sysname-Vlan-interface3] ipv6 address 2001::1 64

[Sysname-Vlan-interface3] mad nd enable

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

 [Current domain is: 1]:

 The assigned  domain ID is: 1

6.      Configure Device E as the intermediate device:

 

CAUTION:

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

 

# Enable the spanning tree feature globally. Map the ND MAD VLAN to MSTI 1 in the MST region.

<DeviceE> system-view

[DeviceE] stp global enable

[DeviceC] stp region-configuration

[DeviceC-mst-region] region-name ndmad

[DeviceC-mst-region] instance 1 vlan 3

[DeviceC-mst-region] active region-configuration

[DeviceC-mst-region] quit

# Create VLAN 3, and add ports Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 1/0/3, and Ten-GigabitEthernet 1/0/4 to VLAN 3 for forwarding ND MAD packets.

[DeviceE] vlan 3

[DeviceE-vlan3] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4

[DeviceE-vlan3] quit


Setting up an IRF 3 system

Overview

IRF 3 integrates multiple lower-layer devices with a higher-layer IRF fabric to provide high-density, low-cost connectivity at the access layer.

In an IRF 3 system, the higher-layer IRF fabric is called the parent fabric and the lower-layer devices are called port extenders (PEXs). You can manage and configure the PEXs from the parent fabric as if they were interface cards on the parent fabric.

Typically, IRF 3 works at the access layer of data centers. As shown in Figure 19, the access layer of a network is virtualized into an IRF 3 system. The system contains one parent fabric (a two-chassis IRF fabric) and multiple PEXs to provide connectivity for servers and hosts.

Figure 19 IRF 3 application scenario

 

IRF 3 provides the following benefits:

·           Simplified topologyDevices in an IRF 3 system appear as one node. For redundancy and load balancing, a downstream or upstream device can connect to the IRF 3 system through multichassis link aggregation. Together with link aggregation, IRF 3 creates a loop-free Layer 2 network. The spanning tree feature is not needed among devices in the IRF 3 system or on the link aggregations. IRF 3 also simplifies the Layer 3 network topology because it reduces the number of routing peers. The network topology does not change when a device is added to or removed from the IRF 3 system.

·           Single point of managementAn IRF 3 system is accessible at a single IP address on the network. You can use this IP address to log in through any network port to manage all the devices in the system. For an SNMP NMS, an IRF 3 system is one managed network node.

·           Network scalability and resiliency—You can increase the number of ports in an IRF 3 system by adding PEXs without changing network topology.

·           High availability—Each PEX has multiple high-speed physical ports for uplink connectivity to the parent fabric. The links on these ports are aggregated and load balanced automatically.

·           Decreased TCO—IRF 3 decreases hardware investments and management costs. In an IRF 3 system, the parent fabric performs all the management and routing functions, and the PEXs only forwards traffic. You can add low-performance devices as PEXs to an IRF 3 system for network scalability. In addition, PEXs can load software and synchronize configuration from the parent fabric without administrative intervention.

Basic concepts

IRF 3 includes IRF concepts and adds the concepts in this section.

IRF 3 roles

The devices in an IRF 3 system have the following roles:

·           Parent fabric—Higher-layer single-chassis or multichassis IRF fabric that controls the entire IRF 3 system, including PEXs. Each IRF 3 system has one parent fabric.

·           Parent deviceMember devices in the parent fabric.

·           Master deviceControls and manages the entire IRF 3 system, including all parent devices and PEXs. The master device in the IRF fabric is also the master device for the IRF 3 system. You configure all devices (including PEXs and parent devices) from the master device.

·           PEX—Operates as I/O modules of the parent fabric to receive and transmit traffic. All forwarding decisions are made on the parent fabric. Table 2 shows the operating states of PEXs.

Table 2 PEX operating states

State

Description

Loading

The PEX is starting up. To avoid problems, do not reboot a PEX while it is in Loading state.

Online

The PEX has started up and registered with the parent fabric. You can configure and manage the PEX from the parent fabric.

Offline

Any of the following conditions exist:

·          The PEX has not started up.

·          The PEX has lost its uplink connectivity to the parent fabric.

·          The PEX configuration on the parent fabric is incomplete.

 

PEX port

A PEX port is a logical port created on the parent fabric for managing a PEX. For each PEX, you must create a unique PEX port, and assign all physical interfaces connected to the PEX to the PEX port.

PEX physical interface

PEX physical interfaces connect PEXs and the parent fabric.

You can set up multiple PEX links between the parent fabric and a PEX. These links aggregate automatically for backup and load balancing.

On the parent fabric, you must assign the PEX physical interfaces for one PEX to the same PEX port. On a PEX, you must connect all its PEX physical interfaces to the physical interfaces in the same PEX port.

Table 3 describes the states of PEX physical interfaces.

Table 3 PEX physical interface states

State

Description

Forwarding

The PEX physical interface is operating correctly and can forward data traffic.

Down

The physical link is disconnected. The PEX physical interface cannot forward any packets.

Blocked

The PEX physical interface cannot forward any packets except for IRF 3 packets. The Blocked state is a transitional state between Forwarding and Down. A PEX physical interface changes to the Blocked state in the following situations:

·          Incorrect physical connection:

?  The PEX has PEX links to more than one PEX port on the parent fabric.

?  The PEX port on the parent fabric contains physical links to more than one PEX.

·          The data link is forced to the Blocked state. In the startup phase, the PEX blocks a PEX physical interface if the interface's physical link is up, but it is not used for loading startup software.

·          The physical state of the interface is up, but the PEX link to the parent fabric has been disconnected. The PEX and the parent fabric cannot receive IRF 3 heartbeat packets from each other.

 

Virtual slot number

Each PEX is identified by a unique virtual slot number in an IRF 3 system.

After a PEX joins an IRF 3 system, the first segment in its interface numbers changes to the virtual slot number assigned to the PEX. For example, a PEX has an interface numbered 1/0/1 before it is added to an IRF 3 system. After it is added to an IRF 3 system as slot 100, the interface number changes to 100/0/1.

IRF 3 operating mechanisms

IRF 3 membership establishment

After you complete PEX configuration for a PEX, the master device monitors the PEX physical interfaces for the slot number request from the PEX. The PEX uses the following process to join the IRF 3 system:

1.      Virtual slot assignment:

a.    At startup, the PEX sends a slot number request to the master device.

b.    The master device assigns the user-configured slot number to the PEX.

2.      Software loading and PEX registration:

a.    The PEX checks the local storage medium for valid startup images.

b.    If the local startup images are valid, the PEX verifies their compatibility with the running software images on the master device:

-       If all the images are compatible, the PEX starts up with the local startup images.

-       If any incompatibility exists, the PEX goes to step c.

 

 

NOTE:

For the switch to start up, you must make sure it has valid local startup images.

 

c.    The PEX sends a startup software request to the master device.

d.    The master device provides the correct Boot ROM and startup software images to the PEX.

e.    The PEX downloads the software images to the local storage medium, and then automatically reboots to register with the master device.

3.      Configuration synchronization:

a.    The parent device issues its running configuration to the PEX.

b.    The PEX runs with the configuration received from the master device instead of reading the configuration from its local startup configuration file.

4.      PEX link maintenance:

The master device and the PEX send heartbeat packets on the PEX links to detect link failure. You can determine whether a PEX link is available by checking the state of its physical interfaces.

Configuration management

An IRF 3 system manages all its settings (including settings for PEXs) on the master device. You can configure and manage PEXs only from the master device. The running configuration on the master device has all settings in the IRF 3 system, including settings for PEXs. When a PEX reboots or is added, the master device issues its running configuration to the PEX.

Data forwarding

By default, the PEXs do not have local forwarding capability.

The PEXs send any incoming traffic to the parent fabric. The parent fabric makes the forwarding decisions and sends the traffic to the outgoing interfaces. Figure 20 shows the data forwarding model.

Figure 20 Data forwarding model

 

Hardware compatibility

The S6300 switches can operate only as PEXs to the following devices:

·           S5820V2 switches.

·           S10500 switches.

·           S12500-X switches.

For information about IRF 3 configuration on the parent devices, see the configuration guides for the parent devices.

Configuration restrictions and guidelines

For a successful IRF 3 system setup, read the configuration restrictions and guidelines carefully before you connect and set up a PEX.

PEX physical interface requirements

Use Table 4 to identify physical interfaces for PEX links.

Table 4 Candidate PEX physical interfaces

Switch model

Candidate PEX physical interfaces

S6300-48S

SFP+ ports 45 through 48 on the front panel.

Other S6300 switches

·       The highest-numbered four SFP+ ports on the front panel.

·       QSFP+ ports on the front panel.

NOTE:

Do not use both SFP+ and QSFP+ ports for PEX links.

 

PEX cabling requirements

When you connect the parent fabric and PEXs, follow these cabling restrictions and guidelines:

·           On the parent fabric, connect a PEX port's all physical interfaces to the same PEX.

·           On a PEX, connect all its PEX physical interfaces to the physical interfaces in the same PEX port.

·           Do not connect PEXs to each other.

·           IRF 3 only supports one layer of PEXs. You cannot attach a lower-layer PEX to a higher-layer PEX.

Configuring the operating mode of the device

An IRF 3-capable device can operate in the following modes:

·           Auto—The device automatically changes to the PEX mode to join an IRF 3 system when it detects any PEX links in up state. Before that, the device operates as an independently node and is configurable from its CLI.

 

 

NOTE:

·       The auto mode does not take effect if IRF port settings are configured on the device. For the auto mode to take effect, you must remove the IRF port settings.

·       The auto mode runs only for 24 hours. The auto mode stops monitoring PEX links if the device fails to join an IRF 3 system before the timer expires. To add the device to an IRF 3 system, you must manually change its mode to PEX mode.

 

·           PEX—The device can only be managed from the parent fabric in an IRF 3 system. You cannot manage the device from the CLI of the device. If no PEX links are available to the parent fabric, you can only access the device from the Boot menus.

·           Switch—The device operates independently as a node. It is not part of an IRF 3 system, whether or not it has connections to the parent fabric.

Configuring the device as a PEX

To add the device to an IRF 3 system as a PEX, you must change its operating mode to auto or PEX.

To configure the device as a PEX:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Change the operating mode to auto or PEX.

pex working-mode { auto | pex } { all | slot slot-number1 [ to slot-number2 ] }

By default, the device operates in auto mode.

To cancel the change, configure the pex working-mode { auto | switch } { all | slot slot-number1 [ to slot-number2 ] } command before the reboot.

3.      Return to user view.

quit

N/A

4.      Save the running configuration.

save

N/A

5.      Reboot the device.

reboot

The change takes effect at reboot.

If PEX mode is used, you will be unable to access the CLI of the device. To change the operating mode of the PEX, you must perform the task from its Boot menus or the parent fabric.

 

Configuring the device as an independent switch

You can set the device to switch mode from its CLI when the device is operating in auto mode.

To configure the device as an independent switch from its CLI:

 

Step

Command

Remarks

1.      Enter system view.

system-view

N/A

2.      Change the operating mode to switch.

pex working-mode switch { all | slot slot-number1 [ to slot-number2 ] }

By default, the device operates in auto mode.

To cancel the change, configure the pex working-mode { auto | pex } { all | slot slot-number1 [ to slot-number2 ] } command before the reboot.

3.      Return to user view.

quit

N/A

4.      Save the running configuration.

save

N/A

5.      Reboot the device.

reboot

The change takes effect at reboot.