Page 3
Preface This configuration guide describes how to set up an IRF fabric of multiple H3C S5130-EI switches, including: • Plan the switch roles in the IRF fabric. Connect the IRF links. • Detect IRF splits and maintain the IRF fabric.
Page 4
Convention Description The argument or keyword and argument combination before the ampersand (&) sign can &<1-n> be entered 1 to n times. A line that starts with a pound (#) sign is comments. GUI conventions Convention Description Window names, button names, field names, and menu items are in Boldface. For Boldface example, the New User window appears;...
Page 5
Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. About the H3C S5130-EI documentation set The H3C S5130-EI documentation set includes the following categories of documents: Category Documents...
Page 6
[Products & Solutions]—Provides information about products and technologies, as well as solutions. [Software Download]—Provides the documentation released with the software version. Technical support service@h3c.com http://www.h3c.com Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
This book describes IRF concepts and guides you through the IRF setup procedure. Hardware compatibility An H3C S5130-EI switch can form an IRF fabric only with devices in the same series. IRF benefits IRF provides the following benefits: Simplified topology and easy management—An IRF fabric appears as one node and is accessible...
Figure 1 IRF application scenario Basic concepts This section describes the basic concepts you might encounter when you work with IRF. 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.
To use an IRF port, you must bind a minimum of one physical interface to it. The physical interfaces assigned to an IRF port form an aggregate IRF link automatically. An IRF port goes down only if all its IRF physical interfaces are down.
IRF split IRF split occurs when an IRF fabric breaks up into two or more IRF fabrics because of IRF link failures, as shown in Figure 3. The split IRF fabrics operate with the same IP address and cause routing and forwarding problems on the network.
On the standalone switch Sysname, GigabitEthernet 1/0/1 represents the first port on the device. • Set its link type to trunk, as follows: <Sysname> system-view [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] port link-type trunk • On the IRF fabric Master, GigabitEthernet 3/0/1 represents the first fixed port on member device 3.
<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.
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. 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.
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: Compare the member IDs of the masters in the IRF fabrics. Set all fabrics to the Recovery state except the one that has the lowest numbered master.
Figure 5 LACP MAD application scenario Customer premise network Device LACP-enabled dynamic link aggregation LACP-enabled dynamic link aggregation IRF link Subordinate Master Internet Common traffic path LACP MAD traffic path BFD MAD BFD MAD can work with or without an intermediate device. Figure 6 shows a typical BFD MAD application scenario.
Figure 6 BFD MAD application scenario Customer premise network Device Link aggregation BFD MAD link VLAN 2 VLAN 2 192.168.1.2/24 192.168.1.3/24 IRF link Subordinate Master Internet ARP MAD ARP MAD detects multi-active collisions by using extended ARP packets that convey the IRF domain ID and the active ID.
Figure 7 ARP MAD application scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) IRF link Subordinate Master Internet Common traffic path Extended ARP traffic path Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID: •...
Page 20
Figure 8 ND MAD application scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) IRF link Subordinate Master Internet Common traffic path Extended ND traffic path Each IRF member device compares the domain ID and the active ID in incoming NS packets with its domain ID and active ID: •...
The transceiver modules at the two ends of an IRF link must be the same type. • For more information about the SFP+ ports, SFP+ DAC cables, and SFP+ transceiver modules, see the switch installation guide. For detailed information about the SFP+ transceiver modules, see H3C Low End Series Ethernet Switches Pluggable Modules Manual. NOTE: The SFP+ modules and SFP+ DAC cables available for the switch are subject to change over time.
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. IRF link redundancy Switch model Maximum number of physical interfaces/IRF port S5130-28F-EI S5130-28S-EI S5130-28S-PWR-EI S5130-28S-HPWR-EI S5130-28TP-EI...
• member devices. Setup and configuration task list H3C recommends the basic IRF setup procedure in Figure 9. Perform the tasks in this figure on each member device. After the IRF fabric is set up, you can access the IRF fabric to manage its member devices...
Page 24
Subordinate devices Activate IRF ports IRF fabric is set up configuration automatically reboot H3C recommends the following IRF fabric setup and configuration procedure: Tasks at a glance Remarks (Required.) Planning the IRF fabric setup Perform this task on each member (Required.)
Tasks at a glance Remarks (Required.) Configuring MAD: Configuring LACP MAD MAD mechanisms are Configuring BFD MAD independent of one another. You Configuring ARP MAD can configure multiple MAD Configuring ND MAD mechanisms for an IRF fabric. Excluding a port from the shutdown action upon detection of multi-active collision (Optional.) Recovering an IRF fabric...
Step Command Remarks If you have bound physical interfaces to IRF ports or assigned member priority, save (Optional.) Save the save the configuration before configuration. rebooting the device so these settings can continue to take effect after the reboot. Reboot the device. reboot [ slot slot-number ] [ force ] 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.
Connect the devices into a daisy-chain topology or a ring topology. A ring topology is more reliable (see Figure 1 1). In ring topology, the failure of one IRF link does not cause the IRF fabric to split as in daisy-chain topology.
Page 28
Software version Available commands Remarks • Basic Ethernet interface commands, including: description flow-interval shutdown For more information about these • LLDP commands, including: Release 3109P05 and later commands, see Layer 2—LAN versions lldp admin-status Switching Configuration Guide. lldp check-change-interval lldp enable lldp notification remote-change enable lldp tlv-enable...
Step Command Remarks Activating IRF port settings causes IRF merge and reboot. To avoid data loss, save the running Save the configuration. save configuration to the startup configuration file before you perform the operation. After this step is performed, the state of the IRF port changes to UP, the member devices elect a master automatically, and the...
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.
Step Command Remarks By default, packets are distributed automatically across IRF member links based on irf-port load-sharing mode Configure the port-specific packet types. { destination-ip | destination-mac | load sharing mode. source-ip | source-mac } * If you execute this command multiple times, the most recent configuration takes effect.
Step Command Remarks Enter system view. system-view • Retain the bridge MAC address By default, the IRF bridge MAC even if the address owner has left address remains unchanged for the fabric: 6 minutes after the address irf mac-address persistent always owner leaves.
Configuration procedure To enable an IRF fabric to synchronize software images of the master automatically to the devices you are adding to the IRF fabric: Step Command Remarks Enter system view. system-view Enable software By default, software auto-update irf auto-update enable auto-update.
Page 34
BFD MAD. • • ARP MAD. ND MAD. • LACP MAD handles collisions differently than BFD MAD, ARP MAD, and ND MAD. To avoid conflicts, do not enable LACP MAD together with any of those mechanisms in an IRF fabric. However, you can use BFD MAD, ARP MAD, and ND MAD together.
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 •...
Page 36
Category Restrictions and guidelines • Do not enable BFD MAD on VLAN-interface 1. • If you are using an intermediate device, assign the ports of BFD MAD links to the BFD MAD VLAN on the device. • Make sure the IRF fabrics on the network use different BFD MAD VLANs. BFD MAD VLAN •...
Step Command Remarks • Assign the port to the VLAN as an access port: port access vlan vlan-id The link type of BFD MAD ports • Assign the port to the VLAN as a Assign the port or the range can be access, trunk, or hybrid.
Step Command Remarks Configure the IRF bridge By default, the IRF bridge MAC MAC address to change as address remains unchanged for undo irf mac-address persistent soon as the address owner 6 minutes after the address leaves. owner leaves. Create a VLAN dedicated to The default VLAN on the device vlan vlan-id ARP MAD.
Step Command Remarks Enter system view. system-view Assign a domain ID to the IRF irf domain domain-id The default IRF domain ID is 0. fabric. Configure the IRF bridge By default, the IRF bridge MAC MAC address to change as address remains unchanged for undo irf mac-address persistent soon as the address owner...
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. To configure a port to not shut down when the IRF fabric transits to the Recovery state: Step Command...
Figure 13 Active IRF fabric fails before the IRF link is recovered To manually recover an inactive IRF fabric: Step Command Enter system view. system-view 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.
As shown in Figure 14, 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 14 Network diagram...
Page 43
Configuration procedure Configure Device A: # Shut down the physical interfaces used for IRF connection. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/25 to Ten-GigabitEthernet 1/0/28 for IRF connection. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/0/25 to ten-gigabitethernet 1/0/28 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 1/0/25 and Ten-GigabitEthernet 1/0/26 to IRF-port 1/1.
Page 44
# Bind Ten-GigabitEthernet 2/0/25 and Ten-GigabitEthernet 2/0/26 to IRF-port 2/2. [Sysname] irf-port 2/2 [Sysname-irf-port2/2] port group interface ten-gigabitethernet 2/0/25 [Sysname-irf-port2/2] port group interface ten-gigabitethernet 2/0/26 [Sysname-irf-port2/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 2/0/25 to ten-gigabitethernet 2/0/28 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...
Page 45
Device C reboots to join the IRF fabric. 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>...
[Sysname-Bridge-Aggregation2] quit # Assign GigabitEthernet 1/0/2, GigabitEthernet 2/0/1, GigabitEthernet 3/0/2, and GigabitEthernet 4/0/1 to the aggregate interface. [Sysname] interface gigabitethernet 1/0/2 [Sysname-GigabitEthernet1/0/2] port link-aggregation group 2 [Sysname-GigabitEthernet1/0/2] quit [Sysname] interface gigabitethernet 2/0/1 [Sysname-GigabitEthernet2/0/1] port link-aggregation group 2 [Sysname-GigabitEthernet2/0/1] quit [Sysname] interface gigabitethernet 3/0/2 [Sysname-GigabitEthernet3/0/2] port link-aggregation group 2 [Sysname-GigabitEthernet3/0/2] quit [Sysname] interface gigabitethernet 4/0/1...
Page 47
Disable the spanning tree feature on the ports used for BFD MAD, because the two features conflict with each other. Figure 15 Network diagram Device E GE1/0/1 GE1/0/2 GE1/0/4 GE1/0/3 Device B Device A GE1/0/1 GE2/0/1 XGE1/0/27 XGE2/0/27 XGE2/0/25 XGE1/0/25 XGE1/0/28 XGE2/0/28 XGE2/0/26...
Page 48
# Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 1/0/25 to ten-gigabitethernet 1/0/28 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active Configure Device B: # Change the member ID of Device B to 2 and reboot the device to validate the change. <Sysname>...
Page 49
[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/25 to Ten-GigabitEthernet 3/0/28 for IRF connection. # Shut down the physical interfaces. <Sysname>...
Page 50
[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/26 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/27 and Ten-GigabitEthernet 4/0/28 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/27 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/28 [Sysname-irf-port4/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 4/0/25 to ten-gigabitethernet 4/0/28 [Sysname-if-range] undo shutdown [Sysname-if-range] quit...
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 GigabitEthernet 1/0/1, GigabitEthernet 1/0/2, GigabitEthernet 1/0/3, and GigabitEthernet 1/0/4 to VLAN 3 for forwarding BFD MAD packets. <DeviceE>...
Page 52
# Shut down the physical interfaces used for IRF connection. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/25 to Ten-GigabitEthernet 1/0/28 for IRF connection. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/0/25 to ten-gigabitethernet 1/0/28 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 1/0/25 and Ten-GigabitEthernet 1/0/26 to IRF-port 1/1.
Page 53
[Sysname-irf-port2/2] port group interface ten-gigabitethernet 2/0/25 [Sysname-irf-port2/2] port group interface ten-gigabitethernet 2/0/26 [Sysname-irf-port2/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 2/0/25 to ten-gigabitethernet 2/0/28 [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.
Page 54
# 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>...
# 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 Configure Device E as the intermediate device:...
Page 56
Figure 17 Network diagram Device E IP network GE1/0/1~GE1/0/4 GE2/0/1 GE1/0/2 Device A Device B XGE1/0/27 XGE2/0/27 XGE2/0/25 XGE1/0/25 XGE1/0/28 XGE2/0/28 XGE2/0/26 XGE1/0/26 (IRF-port1/2) (IRF-port2/1) (IRF-port2/2) (IRF-port1/1) XGE3/0/25 XGE4/0/25 XGE3/0/26 XGE4/0/26 (IRF-port3/2) (IRF-port4/1) GE3/0/2 GE4/0/1 XGE3/0/27 XGE4/0/27 XGE3/0/28 XGE4/0/28 Device C Device D (IRF-port3/1) (IRF-port4/2)
Page 57
[Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active 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.
Page 58
# 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/25 to Ten-GigabitEthernet 3/0/28 for IRF connection. # Shut down the physical interfaces. <Sysname>...
Page 59
# Bind Ten-GigabitEthernet 4/0/27 and Ten-GigabitEthernet 4/0/28 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/27 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/28 [Sysname-irf-port4/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 4/0/25 to ten-gigabitethernet 4/0/28 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...
Page 60
[DeviceE-vlan3] port gigabitethernet 1/0/1 to gigabitethernet 1/0/4 [DeviceE-vlan3] quit...