Page 2
, H3CS, H3CIE, H3CNE, Aolynk, Care, , IRF, NetPilot, Netflow, SecEngine, SecPath, SecCenter, SecBlade, Comware, ITCMM and HUASAN are trademarks of New H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners Notice The information in this document is subject to change without notice.
Page 3
Preface This configuration guide describes how to set up an IRF fabric of multiple S5150-EI switches, including: • Plan the switch roles in the IRF fabric. • Connect the IRF links. • Detect IRF splits and maintain the IRF fabric. This preface includes the following topics about the documentation: •...
Page 4
GUI conventions Convention Description Window names, button names, field names, and menu items are in Boldface. For Boldface example, the New User window opens; click OK. Multi-level menus are separated by angle brackets. For example, File > Create > > Folder.
Page 5
Obtaining documentation To access the most up-to-date H3C product documentation, go to the H3C website at http://www.h3c.com.hk/ To obtain information about installation, configuration, and maintenance, click http://www.h3c.com.hk/Technical_Documents...
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.
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.
Page 9
Figure 2 A network that contains two IRF domains Core network IRF fabric 1 (domain 10) Device A Device B IRF link IRF fabric 2 Device D Device C (domain 20) IRF link Access network 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.
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-id/slot-number/port-index format. •...
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.
Compare the member IDs of the masters if all IRF fabrics have the same number of members. Set all fabrics to the Recovery state except the one that has the lowest numbered master. Shut down all physical network ports in the Recovery-state fabrics except for the following ports: IRF physical interfaces.
Page 14
Advantages Disadvantages Application scenario mechanism to each other. geographically • close to one If an intermediate another. device is used, every IRF member must have For information about a BFD MAD link to the BFD, see High intermediate device. Availability Configuration Guide.
Page 15
Figure 5 LACP MAD scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation fabric 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 scenario that uses an intermediate device.
Page 16
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 set up ARP MAD links between neighbor IRF member devices, or between each IRF member device and an intermediate device (see Figure...
Page 17
Figure 8 ARP MAD scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) fabric IRF link Subordinate Master Internet Common traffic path Extended ARP traffic path ND MAD ND MAD detects multi-active collisions by using NS packets to transmit the IRF domain ID and the active ID.
Figure 9 ND MAD scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) fabric IRF link Subordinate Master Internet Common traffic path Extended ND traffic path Hardware compatibility An S5150-EI 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...
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 transceiver modules and DAC cables, contact your H3C sales representative. 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.
Tasks at a glance Remarks the master election result. (Required.) Connecting IRF physical interfaces Perform this task on each member device. When you complete IRF port (Required.) Binding physical interfaces to IRF ports binding and activation on all IRF member devices, the IRF fabric is formed.
For more information about hardware and cabling, see the device installation guide. Assigning a member ID to each IRF member device CAUTION: In an IRF fabric, changing IRF member IDs might cause undesirable configuration changes and data loss. Before you do that, back up the configuration, and make sure you fully understand the impact on your network.
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.
Page 23
On a physical interface bound to an IRF port, you can execute only the description, flow-interval, and shutdown commands. For more information about these commands, see Layer 2—LAN Switching Command Reference. To bind physical interfaces to IRF ports: Step Command Remarks Enter system view.
Step Command Remarks Bring up the physical undo shutdown interfaces. 10. Return to system view. quit Activating IRF port configurations causes IRF merge and reboot. To avoid 11. Save the configuration. save data loss, save the running configuration to the startup configuration file before you perform the operation.
As a best practice, use the interactive method if you are new to IRF. When you specify IRF physical interfaces for an IRF port, you must follow the IRF port binding restrictions in "IRF physical interface requirements." If you specify IRF physical interfaces by using the interactive method, you must also follow these restrictions and guidelines: •...
• 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.
• irf mac-address persistent timer—Bridge MAC address of the IRF fabric is retained for 6 minutes after the address owner leaves. If the address 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.
The software auto-update feature automatically synchronizes the current software images of the master to devices that are attempting to join the IRF fabric. 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.
• Make sure the IRF link down report delay is shorter than the heartbeat or hello timeout settings of upper-layer protocols (for example, CFD and OSPF). If the report delay is longer than the timeout setting of a protocol, unnecessary recalculations might occur. •...
Step Command Remarks Enter system view. system-view Assign a domain ID to the irf domain domain-id The default IRF domain ID is 0. IRF fabric. Create a Layer 2 aggregate interface bridge-aggregation Perform this step also on the interface and enter Layer 2 interface-number intermediate device.
Page 31
Category Restrictions and guidelines • 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. •...
Step Command Remarks view. By default, BFD MAD is Enable BFD MAD. mad bfd enable disabled. By default, no MAD IP addresses are configured on any VLAN interfaces. 10. Assign a MAD IP address to mad ip address ip-address { mask | a member device on the Repeat this step to assign a mask-length } member member-id...
Step Command Remarks Enter Ethernet interface interface interface-type view. interface-number • Assign the port to the VLAN as an access port: port access vlan vlan-id • The link type of ARP MAD ports Assign the port to the VLAN as a can be access, trunk, or hybrid.
Step Command Remarks Enter system view. system-view Assign a domain ID to the irf domain domain-id The default IRF domain ID is 0. IRF 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...
Step Command Remarks Enter system view. system-view By default, all network ports on a Configure a network port to Recovery-state IRF fabric are not shut down when the IRF mad exclude interface shut down, except for the IRF fabric transits to the interface-type interface-number physical interfaces and console Recovery state.
Figure 14 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 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...
Page 38
[Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/2 [Sysname-irf-port1/1] quit # Bind Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/4 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/3 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/4 [Sysname-irf-port1/2] quit # Bring up the physical interfaces and save the configuration. [Sysname] interface range ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4 [Sysname-if-range] undo shutdown [Sysname-if-range] quit...
Page 39
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>...
Page 40
[Sysname] irf-port 4/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/2 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/3 and Ten-GigabitEthernet 4/0/4 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/3 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/4 [Sysname-irf-port4/2] quit # Bring up the physical interfaces and save the configuration.
# 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 distribution layer of the enterprise network.
Page 42
# Bind Ten-GigabitEthernet 1/0/1 and Ten-GigabitEthernet 1/0/2 to IRF-port 1/1. [Sysname] irf-port 1/1 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/1 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/2 [Sysname-irf-port1/1] quit # Bind Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/4 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/3 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/4 [Sysname-irf-port1/2] quit...
Page 43
[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. Configure Device C: # Change the member ID of Device C to 3 and reboot the device to validate the change. <Sysname>...
Page 44
[Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 4/0/1 and Ten-GigabitEthernet 4/0/2 to IRF-port 4/1. [Sysname] irf-port 4/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/2 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/3 and Ten-GigabitEthernet 4/0/4 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/3 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/4...
# 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 46
[Sysname] irf-port 1/1 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/1 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/2 [Sysname-irf-port1/1] quit # Bind Ten-GigabitEthernet 1/0/3 and Ten-GigabitEthernet 1/0/4 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/3 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/4 [Sysname-irf-port1/2] quit # Bring up the physical interfaces and save the configuration.
Page 47
The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master. Configure Device C: # Change the member ID of Device C to 3 and reboot the device to validate the change. <Sysname>...
Page 48
# Bind Ten-GigabitEthernet 4/0/1 and Ten-GigabitEthernet 4/0/2 to IRF-port 4/1. [Sysname] irf-port 4/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/2 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/3 and Ten-GigabitEthernet 4/0/4 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/3 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/4 [Sysname-irf-port4/2] quit...
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.
Page 50
Figure 18 Network diagram Device E IP network XGE1/0/1-XGE1/0/4 XGE2/0/5 XGE1/0/5 Device A Device B XGE1/0/3 XGE2/0/1 XGE2/0/3 XGE1/0/1 XGE1/0/4 XGE2/0/2 XGE2/0/4 XGE1/0/2 (IRF-port1/2) (IRF-port2/1) (IRF-port2/2) (IRF-port1/1) XGE3/0/3 XGE4/0/1 XGE3/0/4 XGE4/0/2 (IRF-port3/2) (IRF-port4/1) XGE3/0/5 XGE4/0/5 XGE3/0/1 XGE4/0/3 XGE3/0/2 XGE4/0/4 Device C Device D (IRF-port3/1) (IRF-port4/2)
Page 51
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>...
Page 52
[Sysname] irf-port 3/1 [Sysname-irf-port3/1] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port3/1] port group interface ten-gigabitethernet 3/0/2 [Sysname-irf-port3/1] quit # Bind Ten-GigabitEthernet 3/0/3 and Ten-GigabitEthernet 3/0/4 to IRF-port 3/2. [Sysname] irf-port 3/2 [Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/3 [Sysname-irf-port3/2] port group interface ten-gigabitethernet 3/0/4 [Sysname-irf-port3/2] quit # Bring up the physical interfaces and save the configuration.
Page 53
[Sysname] irf-port-configuration active Device D reboots to join the IRF fabric. A four-chassis IRF fabric is formed. 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.
Page 54
[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 S5150-EI Series and is the answer not in the manual?
Questions and answers