Page 3
The H3C S5830V2 & S5820V2 documentation set includes 16 configuration guides. These guides describe the software features for the H3C S5830V2 & S5820V2 Switch Series and guide you through the software configuration procedures. These guides also provide configuration examples to help you apply software features to different network scenarios.
Page 4
Release 2310 does not contain any changes to IRF over Release 2307. Release 2307 does not contain any changes to IRF over Release 2210. Conventions This section describes the conventions used in this documentation set. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 5
Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your switch. About the H3C S5830V2 & S5820V2 documentation set The H3C S5830V2 & S5820V2 documentation set includes: Category Documents Purposes...
Page 6
Solutions]—Provides information about products and technologies, as well as solutions. [Technical Support & Documents > 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 You can establish an IRF fabric by using S5820V2 switches, S5830V2 switches, or switches from both 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.
<Sysname> system-view [Sysname] interface ten-gigabitethernet 1/0/1 [Sysname-Ten-GigabitEthernet1/0/1] port link-type trunk For another example, on the IRF fabric Master, Ten-GigabitEthernet 3/0/1 represents the first fixed 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 standalone device, you can use its storage device name to access its file system.
<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.
After a master election, all subordinate members reboot with the configuration on the master. The configuration files of the subordinate members are still retained, but these files do not take effect in the IRF fabric. IRF multi-active detection An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 configurations, including the same IP address.
Sets the IRF fabric that has the lowest numbered master to the Detect state. Sets all other fabrics to the Recovery state. Takes the same action on the network ports in Recovery-state fabrics as LACP MAD does. 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 •...
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 intermediate devices. 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: •...
IRF physical interface restrictions and binding requirements Use the following physical interfaces for IRF links: S5820V2 switch—10-GE, SFP+, and QSFP+ ports. • S5830V2 switch—SFP+ ports. • Selecting transceiver modules and cables When you select transceiver modules and cables, follow these restrictions and guidelines: Use 10-GE twisted pairs to connect 10-GE ports in a short distance.
When you use SFP+ ports as IRF physical interfaces on the S5820V2-52QF, S5820V2-52QF-U, S5820V2-48S, or S5830V2-24S switch, follow these restrictions and guidelines: The SFP+ ports are grouped by port number in order, starting from 1. Each group contains four ports.
Save any configuration you have made to the startup configuration file before you reboot the IRF 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.
Page 24
Figure 9 Basic IRF setup flow chart H3C recommends the following IRF fabric setup and configuration procedure: Setup and configuration procedure Remarks (Required.) Planning the IRF fabric setup Perform this task on each member (Required.) Assigning a member ID to each IRF member device device.
Setup and configuration procedure 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
Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-5> To shut down a range of IRF physical interfaces, enter Method 2: Enter interface view or interface range view. interface range name name interface range view.
Step Command Remarks Bring up the interface or the undo shutdown range of interfaces. Return to system view. quit Activating IRF port configurations 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.
Configuring IRF link load sharing mode On an IRF port, traffic is balanced 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 certain criteria, including IP addresses, MAC addresses, and any combination of the criteria.
Step Command Remarks Enter system view. system-view Enter IRF port view. irf-port member-id/port-number 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...
Step Command Remarks • Retain the bridge MAC address even if the address owner has left the fabric: irf mac-address persistent always • Retain the bridge MAC address for By default, the IRF bridge MAC Configure IRF bridge MAC 6 minutes after the address owner address remains unchanged for persistence.
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 menu to delete files. Configuration procedure To enable software auto-update: Step...
Page 34
LACP MAD. • • 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 •...
Step Command Remarks Multichassis link aggregation is Assign the Ethernet port or allowed. the range of Ethernet ports to port link-aggregation group number the specified aggregation Perform this step on the group. intermediate device as well. Configuring BFD MAD When you use BFD MAD, follow these guidelines: Category Restrictions and guidelines •...
Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type To assign a range of ports to the interface-number ] } &<1-5> BFD MAD VLAN, enter interface Method 2: range view. Enter interface view or interface range name name interface range view.
Create an ARP MAD VLAN and assign the ports on the ARP 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 ARP MAD: Step Command Remarks...
Do not configure ND MAD on VLAN-interface 1. • • On the intermediate device, create the ND MAD VLAN and assign the ports on the ND MAD links to the VLAN. To configure ND MAD: Step Command Remarks Enter system view. system-view Assign a domain ID to the IRF irf domain domain-id...
Exclude a VLAN interface and its Layer 2 ports from the shutdown action so you can log in through • the VLAN interface. CAUTION: Excluding a VLAN interface and its Layer 2 ports from the shutdown action introduces IP collision risks because the VLAN interface might be active on both the active and inactive IRF fabrics.
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
[Sysname] interface range name irf interface ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] 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.
Page 44
# Bring up the SFP+ ports and save the configuration. [Sysname] interface range name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] 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 45
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 14, and log in to Device D. # Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48.
[Sysname-Ten-GigabitEthernet1/0/2] quit [Sysname] interface ten-gigabitethernet 2/0/1 [Sysname-Ten-GigabitEthernet2/0/1] port link-aggregation group 2 [Sysname-Ten-GigabitEthernet2/0/1] quit [Sysname] interface ten-gigabitethernet 3/0/2 [Sysname-Ten-GigabitEthernet3/0/2] port link-aggregation group 2 [Sysname-Ten-GigabitEthernet3/0/2] quit [Sysname] interface ten-gigabitethernet 4/0/1 [Sysname-Ten-GigabitEthernet4/0/1] port link-aggregation group 2 [Sysname-Ten-GigabitEthernet4/0/1] quit 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.
Page 48
[Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] 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> system-view [Sysname] irf member 1 renumber 2 Renumbering the member ID may result in configuration change or loss.
Page 49
# Connect Device C to Device A as shown in Figure 15, and log in to Device C. # Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48. <Sysname>...
Page 50
# 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 name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] quit [Sysname] save...
# 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...
Page 52
[Sysname] interface range name irf interface ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] 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.
Page 53
# Bring up the SFP+ ports and save the configuration. [Sysname] interface range name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] 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
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. # Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48.
[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: CAUTION: If the intermediate device is also in an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection.
Page 56
Figure 17 Network diagram Configuration procedure 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. <Sysname> system-view [Sysname] interface range name irf interface ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] quit...
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
# Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48. <Sysname> system-view [Sysname] interface range name irf interface ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] quit # Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1.
Page 59
[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 name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] quit [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active Device D reboots to join the IRF fabric.
Page 60
[DeviceE-vlan3] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4 [DeviceE-vlan3] quit...
Need help?
Do you have a question about the S5830V2 and is the answer not in the manual?
Questions and answers