1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. 6127XLG
  6. Irf configuration manual

HPE 6127XLG Irf Configuration Manual

Blade switch series
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
HPE 6127XLG Blade Switch Series
IRF

Configuration Guide

Part number: 797703-002
Software version: Release 24xx
Document version: 6W101-20170705

Advertisement

Table of Contents
loading

Related Manuals for HPE 6127XLG

Summary of Contents for HPE 6127XLG

  • Page 1: Configuration Guide

    HPE 6127XLG Blade Switch Series Configuration Guide Part number: 797703-002 Software version: Release 24xx Document version: 6W101-20170705...
  • Page 2 © Copyright 2017 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

  • Page 3: Table Of Contents

    Contents Setting up an IRF fabric ·····································································1 Overview ···································································································································· 1 Network topology ·················································································································· 2 Basic concepts ····················································································································· 2 Interface naming conventions ·································································································· 4 File system naming conventions ······························································································· 4 Configuration synchronization ·································································································· 6 Master election ····················································································································· 6 Multi-active handling procedure ································································································ 6 MAD mechanisms ·················································································································...
  • Page 4 Remote support ·················································································································· 47 Documentation feedback ······································································································ 47 Index ··························································································· 48...

  • Page 5: Setting Up An Irf Fabric

    IRF fabric that has two member devices, which appear as a single node to the upper-layer and lower-layer devices. NOTE: IRF member devices in this document are HPE 6127XLG switch modules. Figure 1 IRF application scenario IP network...

  • Page 6: Network Topology

    processing capacity of an IRF fabric simply by adding member devices without changing the network topology. 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."...
  • Page 7 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.

  • Page 8: Interface Naming Conventions

    To identify the port index, see Figure Figure 5 Port indexes External uplink port QSFP+ port SFP+ port 6127XLG 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Backplane Internal downlink port...
  • Page 9 On a multi-member IRF fabric, you can use the storage device name to access the file system of the master. To access the file system of any other member device, use the name in the slotmember-ID#storage-device-name format. For example: To access the test folder under the root directory of the flash memory on the master device: <Master>...

  • Page 10: Configuration Synchronization

    # Copy the file to member device 3. <Master> copy test.ipe slot3#flash:/ Copy flash:/test.ipe to slot3#flash:/test.ipe?[Y/N]:y Copying file flash:/test.ipe to slot3#flash:/test.ipe... Done. For more information about storage device naming conventions, see Fundamentals Configuration Guide. Configuration synchronization IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all member devices get and run the running configuration of the master.

  • Page 11: Mad Mechanisms

    For more information about the MAD mechanisms and their application scenarios, see "MAD mechanisms." Collision handling When MAD detects a multi-active collision, it sets all IRF fabrics except one to the Recovery state. The fabric that is not placed in Recovery state can continue to forward traffic. The Recovery-state IRF fabrics are inactive and cannot forward traffic.
  • Page 12 Advantages Disadvantages Application scenario mechanism • No special • Requires MAD dedicated requirements for physical links and Layer 3 network scenarios. interfaces, which cannot be • • Detection speed is If no intermediate used for transmitting user fast. device is used, this traffic.
  • Page 13 Figure 6 LACP MAD scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation IRF 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 intermediate devices. Figure 7 shows a typical BFD MAD scenario that uses an intermediate device.
  • Page 14 • When the IRF fabric splits, the IP addresses of the masters in the split IRF fabrics take effect. The masters can establish a BFD session. If you execute the display bfd session command, the state of the BFD session between the two devices is Up. Figure 7 BFD MAD scenario with intermediate device Device IRF fabric...
  • Page 15 Figure 9 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.

  • Page 16: Hardware Compatibility

    Common traffic path Extended ND traffic path Hardware compatibility An HPE 6127XLG switch module can form an IRF fabric only with switch modules 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 "Setup and configuration task...

  • Page 17: Connecting Irf Ports

    These ports are invisible to users and do not require physical cabling. The HP 6127XLG or HP 6127XLG TAA switch module has four crosslink ports, which are numbered 17, 18, 19, and 20. By default, the four ports are shut down to avoid loops.

  • Page 18: Configuration Backup

    Configuration backup As a best practice, back up the next-startup configuration file on a device before adding the device to an IRF fabric as a subordinate device. A subordinate device's next-startup configuration file might be overwritten if the master and the subordinate use the same file name for their next-startup configuration files.

  • Page 19: Planning The Irf Fabric Setup

    Tasks at a glance Remarks Configuring ARP MAD  Configuring ND MAD  Excluding a port from the shutdown action upon detection of  multi-active collision 13. (Optional.) Recovering an IRF fabric Planning the IRF fabric setup Consider the following items when you plan an IRF fabric: •...

  • Page 20: Specifying A Priority For Each Member Device

    Step Command Remarks effect after the reboot. Reboot the device. reboot [ slot slot-number ] [ force ] Specifying a priority for each member device IRF member priority represents the possibility for a device to be elected the master in an IRF fabric. The higher the priority, the higher the possibility.

  • Page 21: Binding Physical Interfaces To Irf Ports

    Figure 12 Connecting IRF member devices by using crosslink ports Inter-switch Crosslink IRF-port2 IRF-port1 6127XLG 6127XLG You can connect the devices into a daisy-chain topology or a ring topology. A ring topology is more reliable (see Figure 13). In ring topology, the failure of one IRF link does not cause the IRF fabric to split as in daisy-chain topology.
  • Page 22 To bind physical interfaces to IRF ports: Step Command Remarks Enter system view. system-view • Enter interface range view: interface range { interface-type To shut down a range of IRF interface-number [ to physical interfaces, enter interface-type Enter interface view or interface range view.

  • Page 23: Accessing The Irf Fabric

    Accessing the IRF fabric The IRF fabric appears as one device after it is formed. You configure and manage all IRF members at the CLI of the master. All settings you have made are automatically propagated to the IRF members. The following methods are available for accessing an IRF fabric: •...

  • Page 24: Configuring The Global Load Sharing Mode

    Set the global load sharing mode for Ethernet link aggregation to distribute traffic based on  source service port, destination service port, or both source and destination service ports. The command syntax is link-aggregation global load-sharing mode { destination-port | source-port } *.

  • Page 25: Enabling Software Auto-Update For Software Image Synchronization

    • irf mac-address persistent always—Bridge MAC address of the IRF fabric does not change after the address owner leaves. NOTE: IRF fabrics that have the same bridge MAC address cannot merge. If you use the removed bridge MAC owner as the master device in a new fabric, the bridge MAC of the new fabric is the same as the old fabric.

  • Page 26: Configuration Prerequisites

    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. If the two sets of images are different, the device automatically performs the following operations: Downloads the current software images of the master.

  • Page 27: Configuring Mad

    You want to shut down an IRF physical interface or reboot an IRF member device. (After  you complete the operation, reconfigure the delay depending on the network condition.) To set the IRF link down report delay: Step Command Remarks Enter system view.

  • Page 28: Configuring Bfd Mad

    Step Command Remarks interface-number By default, an aggregation group operates in static Configure the aggregation aggregation mode. group to operate in dynamic link-aggregation mode dynamic aggregation mode. Perform this step also on the intermediate device. By default, LACP MAD is Enable LACP MAD.

  • Page 29: Configuring Arp Mad

    Category Restrictions and guidelines interface. • Make sure all the MAD IP addresses are on the same subnet. To configure BFD MAD: Step Command Remarks Enter system view. system-view (Optional.) Assign a domain By default, the domain ID of an irf domain domain-id ID to the IRF fabric.
  • Page 30 Category Restrictions and guidelines • Do not enable ARP MAD on VLAN-interface 1. • If you are using an intermediate device, perform the following tasks on both the IRF fabric and the intermediate device: ARP MAD VLAN Create a VLAN and VLAN interface for ARP MAD. ...

  • Page 31: Configuring Nd Mad

    Step Command Remarks disabled. Configuring ND MAD ND MAD can use only common Ethernet ports. When you use ND MAD, follow these restrictions and guidelines: • Do not configure ND MAD on VLAN-interface 1. • Do not use the VLAN configured for ND MAD for any other purposes. •...

  • Page 32: Excluding A Port From The Shutdown Action Upon Detection Of Multi-Active Collision

    Step Command Remarks and enter VLAN interface vlan-interface-id view. ipv6 address By default, no IPv6 addresses 10. Assign the interface an IP { ipv6-address/pre-length | ipv6 are assigned to any VLAN address. address pre-length } interfaces. 11. Enable ND MAD. mad nd enable By default, ND MAD is disabled.
  • Page 33 Figure 14 Recovering the IRF fabric IP network IP network IP network IRF fabric 2 IRF fabric 2 IRF fabric 1 IRF fabric 1 (Recovery) (Recovery) (Active) (Active) fabric After the IRF link IRF merge is recovered IP network IP network IP network If the active IRF fabric fails before the IRF link is recovered (see Figure...

  • Page 34: Displaying And Maintaining An Irf Fabric

    Network requirements As shown in Figure 16, set up a two-member IRF fabric. Configure LACP MAD on the multi-member aggregation to Device E, an HPE device that supports extended LACP. Figure 16 Network diagram Device E FGE1/0/1 FGE1/0/2...
  • Page 35 Configuration procedure Configure Device A: # Shut down the physical interfaces used for IRF links. This example uses the crosslink ports Ten-GigabitEthernet 1/0/17 to Ten-GigabitEthernet 1/0/20. By default, the four ports are shut down to avoid loops. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/0/17 to ten-gigabitethernet 1/0/20 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 1/0/17 to Ten-GigabitEthernet 1/0/20 to IRF-port 1/1.

  • Page 36: Bfd Mad-Enabled Irf Configuration Example (Using Crosslink Ports)

    [Sysname-if-range] quit [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active The two devices perform master election, and the one that has failed the election reboots to form an IRF fabric with the master. Configure LACP MAD on the IRF fabric: # Set the domain ID of the IRF fabric to 1.
  • Page 37 Figure 17 Network diagram Device E FGE1/0/1 FGE1/0/2 FGE1/1/1 (IRF-port2/2) FGE2/1/1 XGE2/0/17-XGE2/0/20 Device A Device B XGE1/0/17-XGE1/0/20 (IRF-port1/1) IRF link BFD MAD link Data link Configuration procedure Configure Device A: # Shut down the physical interfaces used for IRF links. This example uses the crosslink ports Ten-GigabitEthernet 1/0/17 to Ten-GigabitEthernet 1/0/20.
  • Page 38 Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y [Sysname] quit <Sysname> reboot # Log into Device B. (Details not shown.) # Shut down the physical interfaces used for IRF links. This example uses the crosslink ports Ten-GigabitEthernet 2/0/17 to Ten-GigabitEthernet 2/0/20.

  • Page 39: Arp Mad-Enabled Irf Configuration Example (Using Uplink Ports)

    # Create VLAN 3, and assign FortyGigE 1/0/1 and FortyGigE 1/0/2 to VLAN 3 for forwarding BFD MAD packets. <DeviceE> system-view [DeviceE] vlan 3 [DeviceE-vlan3] port fortygige 1/0/1 to fortygige 1/0/2 [DeviceE-vlan3] quit ARP MAD-enabled IRF configuration example (using uplink ports) Network requirements As shown in...
  • Page 40 [Sysname] irf-port 1/1 [Sysname-irf-port1/1] port group interface fortygige 1/1/1 [Sysname-irf-port1/1] quit # Bind FortyGigE 1/1/2 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface fortygige 1/1/2 [Sysname-irf-port1/2] quit # Bring up the physical interfaces and save the configuration. [Sysname] interface range fortygige 1/1/1 to fortygige 1/1/2 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...
  • Page 41 <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> reboot # Connect Device C to Device A as shown in Figure 18, and log in to Device C. (Details not shown.) # Shut down the physical interfaces used for IRF links.
  • Page 42 [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface fortygige 4/1/2 [Sysname-irf-port4/2] quit # Bring up the physical interfaces and save the configuration. [Sysname] interface range fortygige 4/1/1 to fortygige 4/1/2 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active Device D reboots to join the IRF fabric.

  • Page 43: Nd Mad-Enabled Irf Configuration Example (Using Uplink Ports)

    [DeviceC-mst-region] region-name arpmad [DeviceC-mst-region] instance 1 vlan 3 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Create VLAN 3, and assign ports FortyGigE 1/0/1 through FortyGigE 1/0/4 to VLAN 3 for forwarding ARP MAD packets. [DeviceE] vlan 3 [DeviceE-vlan3] port fortygige 1/0/1 to fortygige 1/0/4 [DeviceE-vlan3] quit ND MAD-enabled IRF configuration example (using uplink ports)
  • Page 44 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind FortyGigE 1/1/1 to IRF-port 1/1. [Sysname] irf-port 1/1 [Sysname-irf-port1/1] port group interface fortygige 1/1/1 [Sysname-irf-port1/1] quit # Bind FortyGigE 1/1/2 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface fortygige 1/1/2 [Sysname-irf-port1/2] quit # Bring up the physical interfaces and save the configuration.
  • Page 45 The two devices perform master election, and the one that has failed 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 46 [Sysname-irf-port4/1] port group interface fortygige 4/1/1 [Sysname-irf-port4/1] quit # Bind FortyGigE 4/1/2 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface fortygige 4/1/2 [Sysname-irf-port4/2] quit # Bring up the physical interfaces and save the configuration. [Sysname] interface range fortygige 4/1/1 to fortygige 4/1/2 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...
  • Page 47 <DeviceE> system-view [DeviceE] stp global enable [DeviceC] stp region-configuration [DeviceC-mst-region] region-name ndmad [DeviceC-mst-region] instance 1 vlan 3 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Create VLAN 3, and add ports FortyGigE 1/0/1 through FortyGigE 1/0/4 to VLAN 3 for forwarding ND MAD packets. [DeviceE] vlan 3 [DeviceE-vlan3] port fortygige 1/0/1 to fortygige 1/0/4 [DeviceE-vlan3] quit...

  • Page 48: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.

  • Page 49: Network Topology Icons

    Convention Description An alert that provides helpful information. TIP: Network topology icons Convention Description 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 50: Support And Other Resources

    Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: www.hpe.com/support/hpesc Information to collect •...

  • Page 51: Websites

    Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
  • Page 52 Index IRF fabric ND MAD (uplink port), IRF LACP MAD, accessing IRF link load sharing mode, IRF fabric, IRF link load sharing mode (global), application IRF link load sharing mode (port-specific), IRF ARP MAD application scenario, IRF MAD, IRF BFD MAD application scenario, IRF member device description, IRF LACP MAD application scenario, IRF ND MAD,...
  • Page 53 IRF fabric LACP MAD configuration (crosslink fabric LACP MAD configuration (crosslink port), port), IRF fabric ND MAD configuration (uplink port), fabric ND MAD configuration (uplink port), fabric recovery, IRF fabric recovery, fabric setup, 1, 15 IRF fabric setup, failure recovery, IRF failure recovery, hardware compatibility, IRF hardware compatibility,...
  • Page 54 IRF mode configuration, IRF fabric ARP MAD configuration (uplink port), local IRF fabric BFD MAD configuration (crosslink IRF fabric access local login, port), IRF fabric configuration, MAC addressing IRF fabric LACP MAD configuration (crosslink port), IRF bridge MAC persistence, IRF fabric ND MAD configuration (uplink port), IRF fabric recovery, ARP.
  • Page 55 binding IRF physical interface+port, IRF fabric, configuring IRF ARP MAD, shutting down configuring IRF BFD MAD, IRF port shutdown exclusion, configuring IRF bridge MAC persistence, software configuring IRF fabric, IRF software auto-update, configuring IRF fabric ARP MAD (uplink port), specifying IRF device member priority, configuring IRF fabric BFD MAD (crosslink splitting...
  • Page 56 IRF fabric BFD MAD configuration (crosslink port), IRF fabric configuration, IRF fabric display, IRF fabric LACP MAD configuration (crosslink port), IRF fabric ND MAD configuration (uplink port), IRF fabric recovery, IRF fabric setup, 1, 15 IRF hardware compatibility, IRF LACP MAD, IRF LACP MAD configuration, IRF link down report delay, IRF link load sharing mode,...

Table of Contents