HP 10500 Switch Series Configuration Guide Part number: 5998-5224 Software version: Release 2111P01 and later Document version: 6W101-20140331...
Page 2
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Page 4
Configuration example for restoring standalone mode ···················································································· 38 Four-chassis IRF fabric configuration example ··································································································· 40 Support and other resources ····································································································································· 45 Contacting HP ································································································································································ 45 Subscription service ·············································································································································· 45 Related information ························································································································································ 45 Documents ······························································································································································ 45 ...
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.
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.
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.
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.
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 Figure 5 IRF merge IRF 1 IRF 2 XGE1/3/0/1 XGE2/3/0/1 IRF link Device A Device A Device B Device B...
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."...
Figure 6. In addition, the intermediate device must be an HP device that supports extended LACP for MAD. The IRF member devices send extended LACPDUs with TLVs that convey the domain ID and the active ID of the IRF fabric. The intermediate device transparently forwards the extended LACPDUs received from...
Figure 6 LACP MAD application scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation 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.
Page 14
Figure 7 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...
Software requirements All IRF member devices must run the same system software image version. IRF size An HP 10500 IRF fabric can have up to four chassis. IRF physical port restrictions You can use 10-GE or 40-GE ports for IRF connection.
Before binding a 10-GE port in a port group to an IRF port or removing it from the IRF port, you must • shut down all the other 10-GE ports in the same group. Bring up the ports after you complete the operation. •...
Physical ports bound to an IRF port can be located on different cards. • • HP recommends using multicard IRF links to prevent a card removal from causing an IRF split. Multichassis link aggregation For high availability, connect a downstream device to each IRF member device, and assign the links to one link aggregation group.
• Save any configuration you have made to the startup configuration file before you reboot the IRF member devices. Setup and configuration task list HP recommends the following IRF fabric setup and configuration procedure: Setup and configuration procedure Remarks (Required.) Planning the IRF fabric setup (Required.)
IRF physical ports • • 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.
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."...
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...
Page 23
One IRF fabric forms one IRF domain. IRF domain IDs prevent IRF fabrics from interfering with one another. 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.
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+ •...
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...
Step Command Remarks Activating IRF port configurations can cause IRF merge and reboot. To avoid Save the running save data loss, save the running configuration. 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...
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. • Non-TCP/-UDP IP Configure the traffic—Source and irf-port load-sharing mode { destination-ip port-specific load destination IP addresses. | destination-mac | ingress-port | sharing mode.
Step Command Remarks • Retain the bridge MAC address even if the master has changed: irf mac-address persistent always • Preserve the bridge MAC address By default, the IRF fabric's Configure IRF bridge MAC for 6 minutes after the master bridge MAC address is retained persistence.
Enter system view. system-view The default IRF link down report delay is 4000 milliseconds (4 seconds). HP recommends setting the delay to 0 seconds in one of the following situations: • The IRF fabric requires a quick Set the IRF link down report master/subordinate or IRF link switchover.
Page 31
Configuration Guide. Configuring LACP MAD When you use LACP MAD, follow these guidelines: The intermediate device must be an HP device that support 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.
Page 32
Step Command Remarks Create a Layer 2 aggregate interface bridge-aggregation Perform this step also on the interface and enter interface-number intermediate device. aggregate interface view. By default, an aggregation group operates in static Configure the aggregation aggregation mode. group to operate in dynamic link-aggregation mode dynamic aggregation mode.
Page 33
Category Restrictions and guidelines • Do not use the BFD MAD VLAN for any purpose other than configuring BFD 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.
Page 34
Step Command Remarks • Assign the port to the VLAN as an access port: Choose one command port access vlan vlan-id depending on the port type. • Assign the port to the VLAN as a Assign the port or the range trunk port: BFD MAD has no requirements of ports to the BFD MAD...
Page 35
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.
LACP MAD-enabled IRF configuration example for a two-chassis IRF fabric Network requirements Set up a two-chassis IRF fabric at the access layer of the enterprise network in Figure Configure LACP MAD on the multichassis aggregation to Device C, an HP device that supports extended LACP.
Page 37
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. Configure Device A: # Assign member ID 1 to Device A, and bind Ten-GigabitEthernet 3/0/1 to IRF-port 2. ...
Page 38
Device A reboots to form a single-chassis IRF fabric. 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] 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 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.
Page 40
Figure 14 Network diagram Device A Device B XGE1/3/0/1 XGE2/3/0/1 (IRF-port1/2) (IRF-port2/1) BFD MAD XGE1/4/0/1 XGE2/4/0/1 link …… Configuration procedure 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.
Page 41
[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 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;...
Page 43
Figure 15 Network diagram Configuration procedure Identify the master. display irf MemberID Slot Role Priority CPU-Mac Description Master 00e0-fc0a-15e0 DeviceA Standby 1 00e0-fc0f-8c02 DeviceA Standby 1 00e0-fc0f-15e1 DeviceB 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. Change the operating mode of Device A to standalone.
Page 45
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.
Page 46
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...
Page 47
[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...
Page 48
# 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...
Related information Documents To find related documents, browse to the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals For related documentation, navigate to the Networking section, and select a networking category. •...
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. Braces enclose a set of required syntax choices separated by vertical bars, from which { x | y | ...
Page 51
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.
Page 54
member device ID assignment (standalone IRF global mode configuration, mode), IRF link load sharing mode (IRF mode), member ID, IRF port-specific load sharing mode (IRF mode), member priority, local member priority change (IRF mode), IRF fabric access local login, member roles, merge, MAC addressing merge restrictions,...