HP FlexFabric 11900 Switch Series IRF Configuration Guide Part number: 5998-5256 Software version: Release 2111 and later Document version: 6W100-20140110
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Contents IRF overview ································································································································································· 1 Hardware compatibility ···················································································································································· 1 IRF benefits ···········································································································································
Configuring a member device description ········································································································· 22 Configuring IRF link load sharing mode ············································································································· 23 Configuring IRF bridge MAC persistence ··········································································································· 24 Enabling software auto-update for system software image synch
IRF overview The HP Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple devices to provide data center class availability and scalability. IRF virtualization technology offers processing power, interaction, unified management, and uninterrupted maintenance of multiple devices. This book describes IRF concepts and guides you through the IRF setup procedure. Hardware compatibility An HP 11900 switch can form an IRF fabric only with devices in the same series.
Figure 1 IRF application scenario Network topologies 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 physical IRF ports." Basic concepts This section uses Figure 2 to describe the basic concepts that you might encounter when you work with IRF.
Figure 2 Two-chassis IRF fabric implementation schematic diagram In this figure, Device A and Device B form a two-chassis IRF fabric that has four MPUs (one active and three standbys) and two times the number of interface cards that a single device provides. The IRF fabric manages the physical and software resources of Device A and Device B in a centralized manner. Operating mode The device operates in one of the following modes: • Standalone mode—The device cannot form an IRF fabric with other devices.
IRF member ID An IRF fabric uses member IDs to uniquely identify and manage its members. 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. 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.
IRF physical port IRF physical ports 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. 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 3, Device A and Device B form IRF fabric 1, and Device C and Device D form IRF fabric 2.
Figure 4 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 5. Figure 5 IRF merge IRF 1 IRF IRF 2 + Device A XGE1/3/0/1 = Device B XGE2/3/0/1 IRF link Device A Device B 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. The default member priority is 1.
During an IRF merge, the devices of the IRF fabric that fails the master election must reboot to rejoin the IRF fabric that wins the election. The reboot can be performed automatically or manually, depending on the configuration. See "Enabling IRF auto merge." After a master election, all subordinate devices 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.
In contrast, BFD MAD does not compare the number of members in fabrics. BFD MAD handles a multi-active collision in the following process: 1. Sets the IRF fabric that has the lowest numbered master to the Detect state. 2. Sets all other fabrics to the Recovery state. 3. 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.
Figure 6 LACP MAD application scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation IRF LACP-enabled dynamic link aggregation IRF link Master Subordinate Internet Common traffic path LACP MAD traffic path BFD MAD BFD MAD can work with or without intermediate devices. Figure 7 shows a typical BFD MAD application scenario. To use BFD MAD: • Set up dedicated BFD MAD link between each pair of IRF members or between each IRF member and the intermediate device.
Figure 7 BFD MAD application scenario Customer premise network Device Link aggregation IRF BFD MAD link VLAN 2 192.168.1.2/24 VLAN 2 192.168.1.
Configuring IRF General restrictions and configuration guidelines To ensure a successful IRF setup, read the configuration restrictions and guidelines carefully before you connect and set up an IRF fabric. Software requirements All IRF member devices must run the same system software image version. IRF size An HP 11900 IRF fabric can have up to four chassis. IRF physical port restrictions You can use 10-GE or 40-GE ports for IRF connection.
• Bring up the ports after you complete the operation. 40-GE port restrictions When you use 40-GE port for IRF connection, follow these restrictions and guidelines: • You can use a 40-GE port as one IRF physical port. • You can use the using tengige command to split a 40-GE port into four 10-GE interfaces. The following restrictions apply to these 10-GE interfaces: { { { • You must use all or none of the four 10-GE interfaces as IRF physical ports.
Multichassis link aggregation For high availability, connect a downstream device to each IRF member device, and assign the links to one link aggregation group. Feature and IRF mode compatibility To form an IRF fabric: • All member devices in the IRF fabric must work in the same system operating mode. For more information about the system operating mode, see Fundamentals Configuration Guide. • All member devices in the IRF fabric must have the same setting for the maximum number of ECMP routes.
• If two IRF fabrics have the same bridge MAC address, they cannot merge. • Assign each member a unique IRF member ID to make sure they can merge. You must reboot the members to validate the IRF member ID settings. • Assign the highest member priority to the device you want to use as the master. • Save any configuration you have made to the startup configuration file before you reboot the IRF member devices.
• Member ID and priority assignment scheme • Fabric topology and cabling scheme For more information about hardware and cabling, see the installation guide for the device. Preconfiguring IRF member devices in standalone mode Perform the tasks in this section on every IRF member device. These settings take effect on each member device after their operating mode changes to IRF.
Binding physical ports to IRF ports To establish an IRF connection between two devices, you must bind at least one physical port to IRF-port 1 on one device and to IRF-port 2 on the other. For link redundancy and load sharing, bind multiple physical ports to one IRF port. Make sure the IRF physical ports are operating as Layer 2 interfaces. Layer 3 interfaces cannot be bound to IRF ports.
Connecting physical IRF ports When you connect two neighboring IRF members, connect the physical ports of IRF-port 1 on one member to the physical ports of IRF-port 2 on the other, as shown in Figure 8. For more information about IRF physical port connection restrictions, see "IRF physical port restrictions." IMPORTANT: No intermediate devices are allowed between neighboring members. Figure 8 Connecting IRF physical ports Connect the devices into a daisy-chain topology or a ring topology.
Before changing to IRF mode, use the display irf configuration command to verify that a member ID has been assigned to the device. If the MemberID field displays two hyphens (--), first assign a member ID to the device. To set the operating mode of a device to IRF mode: Step Command Remarks 1. Enter system view. system-view N/A 2. Set the operating mode to IRF mode. chassis convert mode irf The default operating mode is standalone mode.
One IRF fabric forms one IRF domain. IRF domain IDs prevent IRF fabrics from interfering with one another. In Figure 10, Device A and Device B form IRF fabric 1, and Device C and Device D form IRF fabric 2. These fabrics have LACP MAD links between them. When a member device in one IRF fabric receives an LACP MAD packet, it looks at the domain ID in the packet to see whether the packet is from the local IRF fabric or from a different IRF fabric. Then, the device can handle the packet correctly.
Changing the member ID of a device CAUTION: In IRF mode, an IRF member ID change can invalidate member ID-related settings and cause data loss. Be sure you fully understand its impact on your live network. For a successful IRF merge, you must place a device in standalone mode before renumbering it in one of the following situations: • The IRF physical ports of the device are 10-GE breakout ports that are divided from a 40-GE QSFP+ port. • You are exchanging the member IDs of two devices.
Adding physical ports to an IRF port An IRF port can have up to eight physical ports. In IRF mode, you can add more physical ports to an IRF port. This task does not affect the ongoing traffic on the IRF port. When you perform this task, follow the IRF physical port restrictions and configuration guidelines in "IRF physical port restrictions" and "Binding physical ports to IRF ports." To configure IRF ports: Step 1. Enter system view. Command Remarks system-view N/A • Enter interface range view: 2.
Step 11. Save the running configuration. 12. Activate the configuration on the IRF port. Command Remarks save Activating IRF port configurations can cause IRF merge and reboot. To avoid data loss, save the running configuration to the startup configuration file before you perform the operation. 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.
Configuring IRF link load sharing mode On an IRF port, traffic is balanced across its physical links. You can configure the IRF port to distribute traffic based on certain criteria, including IP addresses, MAC addresses, incoming ports, or a combination of the criteria. If a criteria combination is not supported, the system displays an error message.
Step Command Remarks The following are the default load sharing mode: • Non-IP traffic—Source and destination MAC addresses. Configure the port-specific load sharing mode. 3. • Non-TCP/-UDP IP irf-port load-sharing mode { destination-ip | destination-mac | ingress-port | source-ip | source-mac } * traffic—Source and destination IP addresses. • TCP/UDP IP traffic—Source and destination service ports. If you execute this command multiple times, the most recent configuration takes effect.
Step Command Remarks • Retain the bridge MAC address even if the master has changed: irf mac-address persistent always 2. Configure IRF bridge MAC persistence. • Preserve the bridge MAC address for 6 minutes after the master leaves: irf mac-address persistent timer By default, the IRF fabric's bridge MAC address is retained permanently even after the master leaves.
Configuration procedure To enable an IRF fabric to automatically synchronize software images of the master to the devices you are adding to the IRF fabric: Step Command Remarks 1. Enter system view. system-view N/A 2. Enable software auto-update. irf auto-update enable By default, this function is enabled. Setting the IRF link down report delay Link flapping causes frequent IRF splits and merges during a short time.
Table 1 A comparison of the MAD mechanisms MAD mechanism LACP MAD Advantages Disadvantages • Detection speed is fast. • Requires no MAD-dedicated physical ports or interfaces. Application scenario Requires an intermediate HP device that supports extended LACPDUs 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. • No special requirements for network scenarios.
Step Command Remarks interface bridge-aggregation interface-number Perform this step also on the intermediate device. Configure the aggregation group to operate in dynamic aggregation mode. link-aggregation mode dynamic By default, an aggregation group operates in static aggregation mode. 5. Enable LACP MAD. mad enable By default, LACP MAD is disabled. 6. Return to system view. quit N/A 3. 4. Create a Layer 2 aggregate interface and enter aggregate interface view.
Category Restrictions and guidelines • Do not use the BFD MAD VLAN for any purpose other than configuring BFD BFD MAD VLAN and feature compatibility MAD. Layer 2 or Layer 3 features, including ARP and LACP, cannot work on the BFD MAD-enabled VLAN interface or any port in the VLAN. If you configure any other feature on the VLAN, neither the configured feature nor the BFD MAD function will work correctly. • Disable the spanning tree feature on any Layer 2 Ethernet ports in the BFD MAD VLAN.
Step Command Remarks • Assign the port to the VLAN as an access port: port access vlan vlan-id Assign the port or the range of ports to the BFD MAD VLAN. 6. • Assign the port to the VLAN as a Choose one command depending on the port type. trunk port: port trunk permit vlan vlan-id BFD MAD has no requirements for link type of the detection port. • Assign the port to the VLAN as a The default link type of a port is access. hybrid port: port hybrid vlan vlan-id { tagged | untagged } 7.
Recovering an IRF fabric After the failed IRF link between two split IRF fabrics is recovered, log in to the inactive IRF fabric in Recovery state, and use the reboot command to reboot all its members. If the irf auto-merge enable command has been configured, the inactive IRF member devices automatically reboot after the failed link is recovered. After these member devices join the active IRF fabric as subordinates, IRF merge is complete, as shown in Figure 11.
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.
Figure 13 Network diagram Configuration procedure IMPORTANT: For two neighboring IRF members, IRF links must be bound to IRF-port 1 on one member and to IRF-port 2 on the other. 1. Configure Device A: # Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 3/0/1 to IRF-port 2. system-view [Sysname] irf member 1 Info: Member ID change will take effect after the member reboots and operates in IRF mode.
Device A reboots to form a single-chassis IRF fabric. 2. Configure Device B: # Assign member ID 2 to Device B, and bind Ten-GigabitEthernet 3/0/1 to IRF-port 1. system-view [Sysname] irf member 2 Info: Member ID change will take effect after the member reboots and operates in IRF mode. [Sysname] irf-port 1 [Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port1] quit # Save the configuration.
[Sysname] interface ten-gigabitethernet 2/4/0/2 [Sysname-Ten-GigabitEthernet2/4/0/2] port link-aggregation group 2 [Sysname-Ten-GigabitEthernet2/4/0/2] quit 4. Configure Device C as the intermediate device: CAUTION: If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split. # Create a dynamic aggregate interface.
Figure 14 Network diagram IRF Device A XGE2/3/0/1 Device B (IRF-port2/1) XGE1/3/0/1 (IRF-port1/2) XGE1/4/0/1 BFD MAD link XGE2/4/0/1 …… Configuration procedure 1. Configure IRF on Device A: # Assign member ID 1 to Device A. system-view [Sysname] irf member 1 Info: Member ID change will take effect after the member reboots and operates in IRF mode. # Enable IRF mode. [Sysname] chassis convert mode irf The device will switch to IRF mode and reboot.
[Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/3/0/1 [Sysname-irf-port1/2] quit [Sysname] interface ten-gigabitethernet 1/3/0/1 [Sysname-Ten-GigabitEthernet1/3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet1/3/0/1] quit # Save the running configuration to the startup configuration file. [Sysname] quit save 2. Configure IRF on Device B: # Assign member ID 2 to Device B.
system-view [Sysname] irf-port-configuration active # Log in to Device B. (Details not shown.) # Activate IRF port configuration on Device B. system-view [Sysname] irf-port-configuration active %Jul 9 09:04:48:279 2013 G2-16 STM/4/STM_MERGE_NEED_REBOOT: -MDC=1; IRF merge occurs and the IRF system needs a reboot. %Jul 9 14:03:06:855 2013 G2-16 STM/5/STM_MERGE: -MDC=1; IRF merge occurs and the IRF system does not need to reboot. # Reboot Device B.
Figure 15 Network diagram Configuration procedure 1. Identify the master. display irf MemberID Slot Role CPU-Mac Description *+1 0 Master Priority 1 00e0-fc0a-15e0 DeviceA 1 1 Standby 1 00e0-fc0f-8c02 DeviceA 2 0 Standby 1 00e0-fc0f-15e1 DeviceB 2 1 Standby 1 00e0-fc0f-15e2 DeviceB -------------------------------------------------* indicates the device is the master. + indicates the device through which the user logs in.
Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file. Please wait..................................... The current configuration is saved to the active main board successfully. Configuration is saved to device successfully. 5. Change the operating mode of Device A to standalone. [IRF] undo chassis convert mode The device will switch to stand-alone mode and reboot.
Figure 16 Network diagram before IRF deployment Figure 17 Network diagram after IRF deployment Configuration procedure IMPORTANT: Between two neighboring IRF members, IRF links must be bound to IRF-port 1 on one member and to IRF-port 2 on the other.
1. Configure Device A: # Assign member ID 1 and priority 12 to Device A. system-view [Sysname] irf member 1 [Sysname] irf priority 12 # Bind Ten-GigabitEthernet 3/0/2 and Ten-GigabitEthernet 3/0/1 to IRF-port 1 and IRF-port 2, respectively. [Sysname] irf-port 1 [Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/2 [Sysname-irf-port1] quit [Sysname] irf-port 2 [Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port2] quit # Save the configuration.
[Sysname] chassis convert mode irf The device will switch to IRF mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup. Continue? [Y/N]:y Do you want to convert the content of the next startup configuration file flash:/startup.cfg to make it available in IRF mode? [Y/N]:y Please wait... Saving the converted configuration file to the main board succeeded. Slot 1: Saving the converted configuration file succeeded.
# Bind Ten-GigabitEthernet 3/0/1 and Ten-GigabitEthernet 3/0/2 to IRF-port 1 and IRF-port 2, respectively. [Sysname] irf-port 1 [Sysname-irf-port1] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port1] quit [Sysname] irf-port 2 [Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/2 [Sysname-irf-port2] quit # Save the configuration. [Sysname] save # Connect Device D to Device A and Device C, as shown in Figure 17. # Log in to Device D. (Details not shown.) # Enable IRF mode.
Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
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. Italic Italic text represents arguments that you replace with actual values. [] Square brackets enclose syntax choices (keywords or arguments) that are optional. { x | y | ... } Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Network topology icons Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features. Represents an access controller, a unified wired-WLAN module, or the switching engine on a unified wired-WLAN switch. Represents an access point.
Index A IRF BFD MAD (IRF mode), 28 accessing IRF bridge MAC persistence (IRF mode), 24 IRF fabric, 32 IRF fabric, 18 IRF fabric (4-chassis), 40 active IRF global link load sharing mode, 23 IRF active MPU, 4 IRF LACP MAD, 32 adding IRF LACP MAD (IRF mode), 27 IRF physical ports (IRF mode), 21 IRF link load sharing mode (IRF mode), 23 application scenario IRF MAD (IRF mode), 26 IRF, 1 IRF member device (IRF mode), 18 IRF BFD MAD, 9 IRF member device description (IRF mode), 22 IRF LACP MAD,
IRF bridge MAC persistence (IRF mode), 24 I IRF collision handling, 7 ID IRF configuration, 11, 14, 32 IRF configuration (4-chassis), 40 IRF device member priority (standalone mode), 15 IRF domain, 5 Intelligent Resilient Framework.
member device ID assignment (standalone mode), 15 IRF global mode configuration, 23 member ID, 4 IRF port-specific load sharing mode (IRF mode), 23 member priority, 6 member priority change (IRF mode), 20 member roles, 3 merge, 6 merge restrictions, 13 MPU redundancy restrictions, 12 MPU restrictions, 11 IRF link load sharing mode (IRF mode), 23 local IRF fabric access local login, 18 M MAC addressing IRF bridge MAC persistence (IRF mode), 24 MAD BFD.
IRF standalone mode restoration, 38 planning IRF fabric setup, 14 IRF standalone operating mode, 3 multi-active detection.
displaying IRF fabric, 32 IRF link down report delay (IRF mode), 26 enabling IRF auto merge (IRF mode), 22 enabling IRF software auto-update (IRF mode), 25 excluding port from IRF shutdown action, 30 planning IRF fabric setup, 14 preconfiguring IRF member device (standalone mode), 15 recovering IRF fabric, 31 restoring IRF standalone mode, 38 saving IRF next startup configuration file (standalone mode), 16 IRF operating mode, 17 shutdown action (IRF), 30 shutting down IRF shutdown action, 30 software IRF
53
