HP FlexFabric 12900 Switch Series Configuration Guide Part number: 5998-6237 Software version: Release 1135 Document version:6W100-20150427...
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
BFD MAD-enabled IRF configuration example ··································································································· 36 Configuration example for restoring standalone mode ···················································································· 39 Support and other resources ····································································································································· 42 Contacting HP ································································································································································ 42 Subscription service ·············································································································································· 42 Related information ························································································································································ 42 Documents ······························································································································································ 42 ...
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 The HP 12900 IRF fabric only supports the daisy-chain topology. For information about connecting IRF member devices, see "Connecting IRF physical interfaces." Basic concepts This section uses Figure 2 to describe the basic concepts that you might encounter when you work with...
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 interface IRF physical interfaces 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 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.
Two members are considered to start up at the same time if their startup time difference is equal to or less than 10 minutes. For these members, the next tiebreaker applies. Member with the lowest member ID. For a new IRF fabric, the subordinate devices must reboot to complete the setup after the master election. For an IRF merge, devices must reboot if they are in the IRF fabric that fails the master election.
All the links form a dynamic link aggregation group. • The intermediate device must be an HP device that supports extended LACP for MAD. • The IRF member devices send extended LACPDUs with a domain ID and an active ID. The intermediate device transparently forwards the extended LACPDUs received from one member device to all the other member devices.
Figure 6 LACP MAD 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
When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect, and the • two masters can establish a BFD session. If you use the display bfd session command, the state of the BFD session between the two devices is Up. Figure 7 BFD MAD scenario Customer premise...
IRF size and member ID restrictions To ensure a successful IRF setup, follow these IRF size and member ID restrictions: An HP 12900 IRF fabric can have up to two chassis. • The member ID assigned to a member chassis must be 1 or 2.
Port split and combination (the using fortygige command) require a card reboot. To avoid topology • change, HP recommends that you complete these operations before you add the device to an IRF fabric. When you perform these operations in an IRF fabric, make sure you understand the impact on the IRF fabric topology.
If the IRF fabric splits, do not change the IRF settings on any IRF member devices before they reunite. Configuration backup HP recommends that you back up the next-startup configuration file on a device before adding the device to an IRF fabric as a subordinate.
Setup and configuration procedure Remarks (Optional.) Configuring IRF member devices in IRF mode: Assigning an IRF domain ID to the IRF fabric Adding physical interfaces to an IRF Changing the member ID of a device port is required if you did not Changing the priority of a member device preconfigure IRF port bindings.
Step Command Remarks Check the MemberID field. If the (Optional.) Verify the device does not have an IRF member ID assignment display irf configuration member ID, the field displays status. two hyphens (--). Enter system view. system-view By default, the device does not have an IRF member ID.
When you connect transceiver modules, connect the transmit port of the transceiver module at one end to the receive port of the transceiver module at the other end. IMPORTANT: No intermediate devices are allowed between neighboring members. Figure 8 Connecting IRF physical interfaces Connect the devices into a daisy-chain topology.
After you change the operating mode, the device automatically reboots for the change to take effect. During the reboot, you may choose to have the system automatically convert the startup configuration file. Automatic configuration conversion prevents slot- or interface-related settings from becoming invalid. For example, the system can convert the slot slot-number parameter set in standalone mode to the chassis chassis-number slot slot-number parameter in IRF mode.
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. • Make sure you fully understand its impact on your live network. • If you are exchanging the member IDs of member devices, you must place the member devices in standalone mode before renumbering them for a successful IRF merge.
Page 24
When you perform this task, follow the IRF physical interface restrictions and configuration guidelines in the following sections: IRF physical interface restrictions. • Binding physical interfaces to IRF ports. • To add physical interfaces to IRF ports: Step Command Remarks Enter system view.
Step Command Remarks • Enter interface range view: interface range { interface-type interface-number [ to interface-type Enter Ethernet interface view interface-number ] } &<1-24> or interface range view. • Enter interface view: interface interface-type interface-number Bring up the physical undo shutdown interfaces.
Configuring a member device description Step Command Remarks Enter system view. system-view Configure a description for a By default, no member device irf member member-id description text member device. description is configured. 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 any combination of the following criteria: IP addresses.
Step Command Remarks Enter system view. system-view Enter IRF port view. irf-port member-id/port-number By default, the global IRF link load sharing mode applies. Configure the irf-port load-sharing mode { destination-ip port-specific load | destination-mac | ingress-port | If you execute this command sharing mode.
Step Command Remarks • Retain the bridge MAC address permanently even if the address owner has left the fabric: irf mac-address persistent always • Retain the bridge MAC address for By default, the IRF fabric's Configure IRF bridge MAC 6 minutes after the address owner bridge MAC address is retained persistence.
Remarks 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 Set the IRF link down report in the following situations: irf link-delay interval delay. •...
Page 30
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 •...
Page 31
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 32
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 BFD MAD VLAN and feature the BFD MAD feature will work correctly.
Page 33
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.
Page 34
Recovering an IRF fabric After the failed IRF link between two split IRF fabrics is recovered, log in to the Recovery-state IRF fabric, 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 Network requirements As shown in Figure 12, set up a two-chassis IRF fabric at the access layer of the enterprise network. Configure LACP MAD on the multichassis aggregation to Device C, an HP device that supports extended LACP.
Page 36
Figure 12 Network diagram 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. Configure Device A: # Assign member ID 1 to Device A, and bind FortyGigE 1/0/2 to IRF-port 2. <Sysname>...
Page 37
Device A reboots to form a single-chassis IRF fabric. Configure Device B: # Assign member ID 2 to Device B, and bind FortyGigE 1/0/1 to IRF-port 1. <Sysname> system-view [Sysname] irf member 2 Info: Member ID change will take effect after the member reboots and operates in IRF mode.
[Sysname-FortyGigE2/1/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. <Sysname>...
Page 39
Figure 13 Network diagram Configuration procedure Configure IRF on Device A: # Assign member ID 1 to Device A. <Sysname> system-view [Sysname] irf member 1 Info: Member ID change will take effect after the member reboots and operates in IRF mode.
Page 40
[Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface fortygige 1/1/0/2 [Sysname-irf-port1/2] quit [Sysname] interface fortygige 1/1/0/2 [Sysname-FortyGigE1/1/0/2] undo shutdown [Sysname-FortyGigE1/1/0/2] quit # Save the running configuration to the startup configuration file. [Sysname] quit <Sysname> save Configure IRF on Device B: # Assign member ID 2 to Device B. <Sysname>...
<Sysname> system-view [Sysname] irf-port-configuration active # Log in to Device B. (Details not shown.) # Activate IRF port configuration on Device B. <Sysname> system-view [Sysname] irf-port-configuration active %Jul 9 09:04:48:279 2013 STM/4/STM_MERGE_NEED_REBOOT: IRF merge occurs and the IRF system needs a reboot. %Jul 9 14:03:06:855 2013 STM/5/STM_MERGE: IRF merge occurs and the IRF system does not need to reboot.
Page 42
Figure 14 Network diagram Configuration procedure Identify the master. <IRF> display irf MemberID Slot Role Priority CPU-Mac Description Master 00e0-fc0a-15e0 DeviceA Standby 00e0-fc0f-8c02 DeviceA Standby 00e0-fc0f-15e1 DeviceB Standby 00e0-fc0f-15e2 DeviceB -------------------------------------------------- * indicates the device is the master. + indicates the device through which the user logs in. The Bridge MAC of the IRF is: 000f-e26a-58ed Auto upgrade : no...
Page 43
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.
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 46
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.