HP FlexFabric 12900 Switch Series Configuration Guide Part number: 5998-7267a Software version: R103x Document version: 6W100-20160728...
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.
Contents Setting up an IRF fabric ··············································································································································· 3 Overview ············································································································································································ 3 Network topologies ·························································································································································· 4 Basic concepts ··································································································································································· 4 Operating mode ······················································································································································· 5 IRF member roles ······················································································································································ 5 IRF member ID ··························································································································································· 5 MPU roles ··································································································································································...
Page 4
BFD MAD-enabled IRF configuration example for a two-chassis IRF fabric ···················································· 35 Configuration example for restoring standalone mode ···················································································· 38 Support and other resources ····································································································································· 41 Contacting HP ································································································································································ 41 Subscription service ·············································································································································· 41 Related information ························································································································································ 41 ...
Setting up an IRF fabric Overview HP 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.
IRF fabric simply by adding member devices without changing the network topology. 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."...
Operating mode The device operates in one of the following modes: Standalone mode—The device cannot form an IRF fabric with other devices. • IRF mode—The device can form an IRF fabric with other devices. • 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.
In standalone mode, the IRF ports are named IRF-port 1 and IRF-port 2. In IRF mode, the IRF ports are named IRF-port n/1 and IRF-port n/2, where n is the member ID of the device. The two IRF ports are referred to as IRF-port 1 and IRF-port 2 in this book. To use an IRF port, you must bind a minimum of one physical interface to it.
Figure 3 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 4.
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. Configuration synchronization IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all devices obtain and run the running configuration of the master.
For the setup of 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. The reboot can be performed automatically or manually, depending on the IRF auto-merge configuration (see "Enabling IRF auto-merge").
6, LACP MAD has the following requirements: Every IRF member must have a link with an intermediate device. • 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 that convey 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. If the domain IDs and active IDs sent by all the member devices are the same, the IRF fabric is •...
For a successful IRF setup, follow the restrictions and guidelines in this section and the setup procedure "Setup and configuration task list." Hardware compatibility An HP 12900 switch can form an IRF fabric with devices of the same model. Software requirements All IRF member devices must run the same software image version.
Port split (the using tengige command) 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.
The persistence setting ensures that other devices in the TRILL network can maintain correct network topology after the bridge MAC address owner leaves the IRF fabric. 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.
You can use the backup file to restore the original configuration after removing the subordinate from the IRF fabric. Setup and configuration task list HP recommends the following IRF fabric setup and configuration procedure: Tasks at a glance Remarks (Required.)
Preconfiguring IRF member devices in standalone mode Perform the preconfiguration tasks on every IRF member device. These settings take effect on each member device after their operating mode changes to IRF. Assigning a member ID to each IRF member device A device by default operates in standalone mode without an IRF member ID.
Make sure the IRF physical interfaces are operating as Layer 2 interfaces. Layer 3 interfaces cannot be bound to IRF ports. To configure a physical interface as a Layer 2 or Layer 3 interface, use the port link-mode { bridge | route } command. For more information about this command, see Layer 2—LAN Switching Configuration Guide.
Task Command Save the running configuration to save [ safely ] [ backup | main ] [ force ] the next-startup configuration file. 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 When you connect fiber ports, connect the transmit port of the transceiver module at one end to the...
To set the operating mode of a device to IRF mode: Step Command Remarks Check the MemberID field. If the Verify that a unique IRF device does not have an IRF member ID has been display irf configuration member ID, the field displays two assigned to the device.
Assigning an IRF domain ID to the IRF fabric This task is required for running LACP MAD between two IRF fabrics. For BFD MAD, this task is optional. One IRF fabric forms one IRF domain. IRF domain IDs prevent IRF fabrics from interfering with one another.
A change to member priority can affect the master re-election result. However, it does not cause an immediate master re-election. To change the priority of a member device: Step Command Remarks Enter system view. system-view Specify a priority for a The default IRF member priority irf member member-id priority priority member of an IRF fabric.
Page 24
Step Command Remarks By default, no physical interfaces are bound to any IRF port. Repeat this step to assign multiple physical interfaces to port group interface interface-type the IRF port. Bind each physical interface interface-number [ mode { enhanced | to the IRF port.
Enabling IRF auto-merge When two IRF fabrics merge, you must reboot the member devices in the IRF fabric that fails in the master election. The auto-merge feature enables the IRF fabric to automatically reboot all its member devices to complete the merge. This feature works only when it is enabled on both IRF fabrics that are merging.
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. • MAC addresses. • Incoming ports.
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 permanently even if the owner has left the IRF 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 owner leaves bridge MAC address is retained persistence.
Page 29
Configuring LACP MAD When you use LACP MAD, follow these guidelines: The intermediate device must be an HP device that supports extended LACP for MAD. • If the intermediate device is also an IRF fabric, assign this fabric a different domain ID than the LACP •...
Page 30
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> aggregation group, enter Method 2: interface range view. Enter Ethernet interface view interface range name name or interface range view.
Page 31
Step Command Remarks Enter system view. system-view Assign a domain ID to the By default, the domain ID of an irf domain domain-id IRF fabric. IRF fabric is 0. Create a new VLAN The default VLAN on the device vlan vlan-id dedicated to BFD MAD.
Page 32
Excluding a port from the shutdown action upon detection of multi-active collision 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. By default, all ports except the console and IRF physical interfaces shut down automatically when the IRF fabric transits to the Recovery state.
Figure 11 Active IRF fabric fails before the IRF link is recovered IP network IP network IRF fabric 2 IRF fabric 2 fabric 1 (Recovery) (Active) IRF fabric (Active) 1 fails IRF fabric 1 Execute the mad because fails before the restore IRF link is command on...
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. Figure 12 Network diagram...
Page 35
[Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/4 [Sysname-irf-port2] quit # Save the configuration. [Sysname] quit <Sysname> save # Enable IRF mode. <Sysname> system-view [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.
Page 36
Slot 1: Saving the converted configuration file succeeded. Now rebooting, please wait... Device B and Device A form a two-chassis IRF fabric after Device B reboots. Configure LACP MAD: # Assign domain ID 1 to the IRF fabric. <Sysname> system-view [Sysname] irf domain 1 # Create a dynamic aggregate interface and enable LACP MAD.
BFD MAD-enabled IRF configuration example for a two-chassis IRF fabric Network requirements As shown in Figure 13, set up an IRF fabric at the distribution layer of the network. • Configure BFD MAD in the IRF fabric and set up BFD MAD links between the member devices. Disable the spanning tree feature on the ports used for BFD MAD, because the two features conflict •...
Page 38
Saving the converted configuration file to the main board succeeded. Slot 1: Saving the converted configuration file succeeded. Now rebooting, please wait... Device A reboots to form a single-chassis IRF fabric. # Shut down Ten-GigabitEthernet 1/3/0/1 through Ten-GigabitEthernet 1/3/0/4. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/3/0/1 to ten-gigabitethernet 1/3/0/4 [Sysname-if-range] shutdown [Sysname-if-range] quit...
Page 39
[Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 2/3/0/1 through Ten-GigabitEthernet 2/3/0/4 to IRF-port 2/1. [Sysname] irf-port 2/1 [Sysname-irf-port2/1] port group interface ten-gigabitethernet 2/3/0/1 [Sysname-irf-port2/1] port group interface ten-gigabitethernet 2/3/0/2 [Sysname-irf-port2/1] port group interface ten-gigabitethernet 2/3/0/3 [Sysname-irf-port2/1] port group interface ten-gigabitethernet 2/3/0/4 [Sysname-irf-port2/1] quit # Bring up the IRF physical interfaces.
[Sysname-Vlan-interface3] mad ip address 192.168.2.1 24 member 1 [Sysname-Vlan-interface3] mad ip address 192.168.2.2 24 member 2 [Sysname-Vlan-interface3] quit # Disable the spanning tree feature on Ten-GigabitEthernet 1/4/0/1 and Ten-GigabitEthernet 2/4/0/1. [Sysname] interface ten-gigabitethernet 1/4/0/1 [Sysname-Ten-GigabitEthernet1/4/0/1] undo stp enable [Sysname-Ten-GigabitEthernet1/4/0/1] quit [Sysname] interface ten-gigabitethernet 2/4/0/1 [Sysname-Ten-GigabitEthernet2/4/0/1] undo stp enable [Sysname-Ten-GigabitEthernet2/4/0/1] quit...
Page 41
The Bridge MAC of the IRF is: 000f-e26a-63ed Auto upgrade : no Mac persistent : always Domain ID The output shows that Device A is the master. Examine the configuration for VLAN interfaces. If a VLAN interface has member ports on different member devices, change the IP address for the interface on each device to be unique.
Page 42
Saving the converted configuration file succeeded. Now rebooting, please wait... Device B automatically reboots to complete the operating mode change.
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 45
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.