HPE FlexNetwork HSR6800 Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Network Router
  5. FlexNetwork HSR6800 series
  6. Configuration manual
HPE FlexNetwork HSR6800 Configuration Manual

HPE FlexNetwork HSR6800 Configuration Manual

Irf configuration guide
Hide thumbs Also See for FlexNetwork HSR6800:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual
HPE FlexNetwork HSR6800 Routers
IRF Configuration Guide
Part number: 5998-4487R
Software version: HSR6800-CMW520-R3303P25
Document version: 6W105-20151231

Advertisement

Table of Contents
loading

Related Manuals for HPE FlexNetwork HSR6800

Summary of Contents for HPE FlexNetwork HSR6800

  • Page 1 HPE FlexNetwork HSR6800 Routers IRF Configuration Guide Part number: 5998-4487R Software version: HSR6800-CMW520-R3303P25 Document version: 6W105-20151231...
  • Page 2 © Copyright 2015 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 IRF overview ··································································································· 1 Hardware compatibility ······································································································································· 1 Chassis compatibility ·································································································································· 1 Card compatibility ······································································································································· 1 IRF benefits ························································································································································ 1 Application scenario ··········································································································································· 2 Basic concepts ··················································································································································· 2 Operating mode ········································································································································· 3 IRF member roles ······································································································································ 3 IRF member ID ··········································································································································· 4 MPU roles ··················································································································································...
  • Page 4 BFD MAD-enabled IRF configuration example ························································································ 32 ARP MAD-enabled IRF configuration example ························································································ 34 Restoring standalone mode ····················································································································· 37 Document conventions and icons ································································· 40 Conventions ····················································································································································· 40 Network topology icons ···································································································································· 41 Support and other resources ········································································ 42 Accessing Hewlett Packard Enterprise Support ······························································································ 42 Accessing updates ···········································································································································...

  • Page 5: Irf Overview

    IRF overview The Intelligent Resilient Framework (IRF) technology is proprietary to Hewlett Packard Enterprise. This 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.

  • Page 6: Application Scenario

    Application scenario Figure 1 shows an IRF fabric that has two devices, which appears as a single node to the upper and lower layer devices. Figure 1 IRF application scenario Basic concepts This section uses Figure 2 to describe the basic concepts that you might encounter when you work with IRF.

  • Page 7: Operating Mode

    Figure 2 Two-chassis IRF fabric implementation schematic diagram Device A Device B (MemberID=1) (MemberID=2) Active MPU Active MPU Standby MPU Standby MPU IRF-port 2 IRF-port 1 IRF link XGE1/3/0/1 Service XGE2/3/0/1 Service Physical IRF interface Physical IRF interface port port An IRF fabric is formed.

  • Page 8: Irf Member Id

    IRF member ID An IRF fabric uses member IDs to uniquely identify and manage its members. This 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. For example, after you assign a device with member ID 2 to an IRF fabric, the name of interface GigabitEthernet 3/0/1 changes to GigabitEthernet 2/3/0/1, and the file path slot1#cfa0:/test.cfg changes to chassis2#slot1#cfa0:/test.cfg.

  • Page 9: Irf Domain Id

    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 Router A and Router B form IRF fabric 2.

  • Page 10: Irf Merge

    IRF merge IRF merge occurs when two split IRF fabrics reunite or when you configure and connect two independent IRF fabrics to be one, 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...

  • Page 11: Multi-Active Handling Procedure

    Figure 6. In addition, the intermediate device must be an HPE 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 one member device to all the other member devices: •...

  • Page 12: Bfd Mad

    Figure 6 LACP MAD application scenario 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.

  • Page 13: Arp Mad

    Figure 7 BFD MAD application scenario Customer premises 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 ARP MAD ARP MAD detects multi-active collisions by using extended gratuitous ARP packets that convey the IRF domain ID and the active ID.
  • Page 14 Figure 8 ARP MAD application scenario Customer premises network STP Domain To avoid loops, all devices Device in the domain must run the spanning tree feature. IRF link Subordinate Master Internet Common traffic path Extended gratuitous ARP traffic path Each IRF member compares the domain ID and the active ID in incoming extended gratuitous ARP packets with its domain ID and active ID: •...

  • Page 15: Configuring Irf

    Configuring IRF To ensure a successful IRF setup, read the configuration restrictions and guidelines carefully before you connect and set up an IRF fabric. General restrictions and configuration guidelines Software requirements All IRF member devices must run the same system software image version. MPU and IRF physical port restrictions •...

  • Page 16: Setup And Configuration Task List

    Setup and configuration task list To set up and configure an IRF fabric: Tasks at a glance Remarks Planning the IRF fabric setup Required. Preconfiguring IRF member devices in standalone mode: Assigning a member ID to each IRF member device Required.

  • Page 17: Preconfiguring Irf Member Devices In Standalone Mode

    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. Assigning a member ID to each IRF member device A device by default operates in standalone mode without an IRF member ID.

  • Page 18: Saving Configuration To The Next-Startup Configuration File

    flow-interval commands on the physical port. For more information about these commands, see Layer 2—LAN Switching Command Reference. To bind physical ports to IRF ports: Step Command Remarks Enter system view. system-view Create an IRF port and By default, no IRF port is irf-port port-number enter IRF port view.

  • Page 19: Setting The Operating Mode To Irf Mode

    Figure 9 Connecting IRF physical ports Connect the devices into a daisy chain topology or a ring topology. A ring topology is more reliable (see Figure 10). In ring topology, the failure of one IRF link does not cause the IRF fabric to split as in daisy chain topology.

  • Page 20: Accessing The Irf Fabric

    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, and add the chassis ID in an interface number. To restore the standalone mode, use the undo chassis convert mode command. TIP: IRF generates packets on a device in IRF mode even if the device does not form an IRF fabric with any other device.

  • Page 21: Configuring Irf Member Devices In Irf Mode

    Task Command Remarks Log in to a standby MPU in the irf switch-to chassis By default, you are placed at the chassis-number slot slot-number IRF fabric. global active MPU's CLI. To return to the CLI of the global active MPU, use the quit command. Configuring IRF member devices in IRF mode After you access the global active MPU's CLI, you can perform the tasks in this section or configure features in other configuration guides for the IRF fabric.

  • Page 22: Changing The Member Id Of A Device

    Step Command Remarks Enter system view. system-view Assign a domain ID to the By default, the domain ID of an IRF fabric is irf domain domain-id 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.
  • Page 23 When performing this task, follow the IRF physical port restrictions and configuration guidelines in "MPU and IRF physical port restrictions" and "Binding physical ports to IRF ports." To configure IRF ports: Step Command Remarks Enter system view. system-view • Enter interface range view: Method 1: interface range { interface-type...

  • Page 24: Enabling Irf Auto Merge

    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 function enables the IRF fabric to automatically reboot all its member devices to complete the merge. This function can work only when it is enabled on both IRF fabrics that are merging.

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

    IMPORTANT: If ARP MAD is used, configure the undo irf mac-address persistent command to enable immediate bridge MAC address change after a master leaves. If two IRF fabrics have the same bridge MAC address, they cannot merge. To configure the IRF bridge MAC persistence setting: Step Command Remarks...

  • Page 26: Setting The Irf Link Down Report Delay

    Application scenario mechanism Link aggregation is used between the IRF fabric • Detection speed is fast. and its upstream or Requires an HPE device • downstream device. that supports LACP MAD Requires no LACP MAD packets as the intermediate MAD-dedicated physical For information about device.
  • Page 27 When you use LACP MAD, follow these guidelines: • The intermediate device must be an HPE device that supports extended LACP for MAD. • If the intermediate device is in an IRF fabric, assign this fabric a different domain ID than the LACP MAD-enabled fabric for correct split detection.
  • Page 28 Step Command Remarks 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. mad enable disabled.
  • Page 29 Category Restrictions and guidelines • Do not enable BFD MAD on a VLAN interface that has been assigned an IP address. The VLAN interface becomes unreachable even if you disable BFD MAD. To recover the connectivity of the VLAN interface, use the shutdown and undo shutdown commands or reset ARP.
  • Page 30 Step Command Remarks By default, no MAD IP address is configured on any VLAN interface. Configure a MAD IP mad ip address ip-address { mask | address for a member on Repeat this step to assign a mask-length } member member-id the VLAN interface.
  • Page 31 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 Assign the port or the range a trunk port: ARP MAD has no requirement of ports to the ARP MAD...

  • Page 32: Displaying And Maintaining An Irf Fabric

    Figure 12 Recovering the IRF fabric IP network IP network Network ports that have been shut IRF 2 IRF 1 down (Inactive) (Active) IRF link recovered Network ports that have been shut down IP network IP network If the active IRF fabric has failed, for example, because of device or link failures, before the IRF link is recovered (see Figure 13), use the mad restore command on the inactive IRF fabric to change its...

  • Page 33: Configuration Examples

    Set up a two-chassis IRF fabric at the access layer of the enterprise network in Figure 14. Configure LACP MAD in the IRF fabric, because the IRF fabric has a multichassis aggregate link to Router C, an HPE device that supports extended LACP. Figure 14 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.
  • Page 34 Info: Member ID change will take effect after the member reboots and operates in IRF mode. [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit [Sysname] irf-port 2 [Sysname-irf-port2] port group interface ten-gigabitethernet 3/0/1 [Sysname-irf-port2] quit [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit # Save the configuration.
  • Page 35 # 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. 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 36: Bfd Mad-Enabled Irf Configuration Example

    [Sysname] interface gigabitethernet 4/0/2 [Sysname-GigabitEthernet4/0/2] port link-aggregation group 2 [Sysname-GigabitEthernet4/0/2] quit BFD MAD-enabled IRF configuration example Network requirements Set up an IRF fabric at the distribution layer of the network in Figure 15. 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 with each other.
  • Page 37 [Sysname-Ten-GigabitEthernet3/0/1] quit # Specify the priority of Router A as 10 to make sure it is elected as the master when the IRF fabric is established. [DeviceA] irf priority 10 # Save the configuration. [Sysname] quit <Sysname> save # Enable IRF mode. <Sysname>...

  • Page 38: Arp Mad-Enabled Irf Configuration Example

    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. Now rebooting, please wait...

  • Page 39: Configuration Procedure

    Figure 16 Network diagram Configuration procedure Configure Router A: # Assign member ID 1 to Router A and bind Ten-GigabitEthernet 3/0/1 to IRF-port 2. <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 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] quit <Sysname> save # Connect the two devices as shown in Figure # Log in to Router B.

  • Page 41: Restoring Standalone Mode

    # Enable the spanning tree feature globally on Router C. <DeviceC> system-view [DeviceC] stp enable # Create VLAN 3, and add GigabitEthernet 4/0/1 and GigabitEthernet 4/0/2 to VLAN 3. [DeviceC] vlan 3 [DeviceC-vlan3] port gigabitethernet 4/0/1 gigabitethernet 4/0/2 [DeviceC-vlan3] quit Restoring standalone mode Network requirements Dismantle the IRF fabric in...
  • Page 42 The output shows that Router 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 VLAN interface on each device to be unique after their operating mode is changed to standalone.
  • Page 43 If you have configured a VLAN interface on the IRF fabric for a VLAN that has member ports on both member devices, change the IP address for the VLAN interface on one device to avoid an IP address collision.

  • Page 44: 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 45: Network Topology Icons

    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 46: 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 47: Websites

    For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs Documentation feedback 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,...
  • Page 48 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 49: Index

    Index configuring IRF, 11, 12 accessing IRF ARP MAD, 34 global active MPU (IRF), 16 IRF ARP MAD (IRF mode), 26 IRF fabric, 16 IRF BFD MAD, 32 standby MPU (IRF), 16 IRF BFD MAD (IRF mode), 24 active IRF bridge MAC persistence (IRF mode), 20 IRF active MPU, 4 IRF fabric, 29 adding...
  • Page 50 IRF master election, 6 IRF device member priority (standalone mode), 13 IRF member configuration (IRF mode), 17 IRF domain ID, 5 IRF member configuration (standalone mode), 13 IRF fabric access, 16 IRF member device description (IRF IRF fabric domain ID assignment (IRF mode), 17 mode), 20 IRF fabric recovery, 27 IRF member ID, 4...
  • Page 51 card compatibility, 1 port shutdown exclusion, 27 chassis compatibility, 1 software auto-update enable (IRF mode), 21 configuration, 11, 12 split, 5 configuration restrictions, 11 standalone mode restoration, 37 device member ID change (IRF mode), 18 standby MPU access, 16 device member priority (standalone mode), 13 displaying fabric, 28 LACP domain ID, 5...
  • Page 52 physical port to IRF port bind (standalone IRF configuration, 11, 12 mode), 13 IRF fabric configuration, 29 merging IRF LACP MAD configuration, 29 IRF auto merge (IRF mode), 20 IRF overview, 1 IRF fabric merge, 6 IRF standalone mode restoration, 37 IRF master election, 6 mode physical port...
  • Page 53 configuring IRF MAD (IRF mode), 22 specifying configuring IRF member device (IRF IRF device member priority (standalone mode), 17 mode), 13 configuring IRF member device description split (IRF mode), 20 IRF ARP MAD, 9 connecting IRF physical ports, 14 IRF BFD MAD, 8 displaying IRF fabric, 28 IRF fabric, 5 enabling IRF auto merge (IRF mode), 20...

Table of Contents