hit counter script
HP FlexFabric 5700 series Configuration Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Switch
  5. FlexFabric 5700 series
  6. Configuration manual

HP FlexFabric 5700 series Configuration Manual

Hide thumbs Also See for FlexFabric 5700 series:
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual
HP FlexFabric 5700 Switch Series
IRF

Configuration Guide

Part number: 5998-6684
Software version: Release 2416
Document version: 6W100-20150130

Advertisement

Table of Contents
loading

Related Manuals for HP FlexFabric 5700 series

Summary of Contents for HP FlexFabric 5700 series

  • Page 1: Configuration Guide

    HP FlexFabric 5700 Switch Series Configuration Guide Part number: 5998-6684 Software version: Release 2416 Document version: 6W100-20150130...
  • 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 3: Table Of Contents

    Contents Setting up an IRF fabric ··············································································································································· 1   Overview ············································································································································································ 1   Network topology ····························································································································································· 2   Basic concepts ··································································································································································· 2   IRF member roles ······················································································································································ 2   IRF member ID ··························································································································································· 2   IRF port ······································································································································································ 2   IRF physical interface ···············································································································································...
  • Page 4 Configuring the device as a PEX ························································································································· 50   Configuring the device as an independent switch ···························································································· 50   Support and other resources ····································································································································· 51   Contacting HP ································································································································································ 51   Subscription service ·············································································································································· 51   Related information ························································································································································ 51  ...

  • Page 5: Setting Up An Irf Fabric

    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.

  • Page 6: Network Topology

    Network scalability and resiliency—Processing capacity of an IRF fabric equals the total • processing capacities of all the members. You can increase ports, network bandwidth, and processing capacity of an IRF fabric simply by adding member devices without changing the network topology.

  • Page 7: Mad

    An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 settings, including the same IP address. To avoid IP address collision and network problems, IRF uses multi-active detection (MAD) mechanisms to detect the presence of multiple identical IRF fabrics, handle collisions, and recover from faults.

  • Page 8: Irf Merge

    Figure 3 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 4 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.

  • Page 9: File System Naming Conventions

    [Master-Ten-GigabitEthernet3/0/1] port link-type trunk File system naming conventions On a single-chassis fabric, you can use its storage device name to access its file system. On a multichassis IRF fabric, you can use the storage device name to access the file system of the master. access file system...

  • Page 10: Configuration Synchronization

    <Master> pwd slot3#flash: # Change the current working path to the root directory of the flash memory on the master device. <Master> cd flash:/ <Master> pwd flash: # 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...

  • Page 11: Multi-Active Handling Procedure

    For an IRF merge, devices must reboot if they are in the IRF fabric that fails the master election. Multi-active handling procedure The multi-active handling procedure includes detection, collision handling, and failure recovery. Detection MAD identifies each IRF fabric with a domain ID and an active ID (the member ID of the master). If multiple active IDs are detected in a domain, MAD determines that an IRF collision or split has occurred.

  • Page 12: Mad Mechanisms

    MAD mechanisms IRF provides MAD mechanisms by extending LACP, ARP, and IPv6 ND. IMPORTANT: You can configure ARP MAD and ND MAD together in an IRF fabric for prompt IRF split detection. However, do not configure any of these mechanisms together with LACP MAD, because they handle collisions differently.

  • Page 13: Arp Mad

    If the domain IDs and active IDs sent by all the member devices are the same, the IRF fabric is • integrated. If the extended LACPDUs convey the same domain ID but different active IDs, a split has occurred. • LACP MAD handles this situation as described in "Collision handling."...

  • Page 14: Nd Mad

    Figure 6 ARP MAD scenario Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID. If the domain IDs are different, the extended ARP packet is from a different IRF fabric. The device •...

  • Page 15: Hardware Compatibility

    If the active IDs are the same, the IRF fabric is integrated. Hardware compatibility An HP FlexFabric 5700 switch can form an IRF fabric only with devices 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 "Setup and configuration task...

  • Page 16: Software Requirements

    NOTE: The SFP+/QSFP+ modules and SFP+/QSFP+ DAC cables available for the switch are subject to change over time. For the most up-to-date list of SFP+/QSFP+ modules and DAC cables, contact HP technical support or marketing staff. 10-GE port restrictions for the HP FlexFabric 5700-32XGT-8XG-2QSFP+ Switch and HP FlexFabric...

  • Page 17: Connecting Irf Ports

    SFP+ port restrictions for the HP FlexFabric 5700-40XG-2QSFP+ Switch and HP FlexFabric 5700-40XG-2QSFP+ TAA-compliant Switch When you use the SFP+ ports on the HP FlexFabric 5700-40XG-2QSFP+ Switch (JG896A) and HP FlexFabric 5700-40XG-2QSFP+ TAA-compliant Switch (JG897A) as IRF physical interfaces, follow these restrictions and guidelines: The SFP+ ports are grouped by port number in order, starting from 1.

  • Page 18: Configuration Backup

    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. 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

    Configuring IRF link load sharing mode: Configuring the global load sharing mode Configuring a port-specific load sharing mode (Optional.) Configuring IRF bridge MAC persistence HP recommends enabling (Optional.) Enabling software auto-update for software image software auto-update to ensure synchronization system software image synchronization.

  • Page 20: Specifying A Priority For Each Member Device

    The new member ID takes effect at a reboot. After the device reboots, the settings on all member ID-related physical resources (including common physical network ports) are removed, regardless of whether you have saved the configuration. To assign a member ID to a device: Step Command Remarks...

  • Page 21: Binding Physical Interfaces To Irf Ports

    Figure 9 Connecting IRF physical interfaces 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 22 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 interface-number ] } Enter interface view or interface range view. &<1-24>...

  • 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: Local login—Log in through the console port of any member device.

  • Page 24: Configuring The Global Load Sharing Mode

    Set the IRF link load sharing mode and the global load sharing mode for Ethernet link aggregation • as follows: Set the IRF link load sharing mode to distribute traffic based on source IP, destination IP, or both source and destination IP addresses. The command syntax is irf-port load-sharing mode { destination-ip | source-ip } *.
  • Page 25 To avoid duplicate bridge MAC addresses, an IRF fabric can change its bridge MAC address automatically after its bridge MAC owner leaves. However, the change causes temporary traffic disruption. Depending on the network condition, enable the IRF fabric to preserve or change its bridge MAC address after the address owner leaves.

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

    Enabling software auto-update for software image synchronization IMPORTANT: To ensure a successful software auto-update in a multi-user environment, prevent anyone from rebooting member devices during the auto-update process. To inform administrators of the auto-update status, Network configure the information center to output the status messages to configuration terminals (see Management and Monitoring Configuration Guide The software auto-update feature synchronizes the current software images of the master in an IRF fabric to all its members automatically.

  • Page 27: Setting The Irf Link Down Report Delay

    Setting the IRF link down report delay To prevent frequent IRF splits and merges during link flapping, configure the IRF ports to delay reporting link down events. An IRF port does not report a link down event to the IRF fabric immediately after its link changes from up to down.

  • Page 28: Configuring Lacp Mad

    Configuring LACP MAD When you use LACP MAD, follow these guidelines: • The intermediate device must be a device that supports extended LACP for MAD. If the intermediate device is also an IRF fabric, assign the two IRF fabrics different domain IDs for •...
  • Page 29 If an intermediate device is used, you can use common data links as ARP MAD links. If no • intermediate device is used, set up dedicated ARP MAD links between IRF member devices. If an intermediate device is used, make sure the following requirements are met: •...

  • Page 30: Configuring Nd Mad

    Configuring ND MAD When you use ND MAD, follow these guidelines: • Do not configure ND MAD on VLAN-interface 1. Do not use the VLAN configured for ND MAD for any other purpose. • If an intermediate device is used, you can use common data links as ND MAD links. If no •...

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

    Step Command Remarks ipv6 address Assign the interface an IP By default, no IPv6 address is { ipv6-address/pre-length | ipv6 address. assigned to any VLAN interface. address pre-length } Enable ND MAD. mad nd enable By default, ND MAD is disabled. Excluding a port from the shutdown action upon detection of multi-active collision CAUTION:...
  • Page 32 Figure 11 Recovering the IRF fabric If the active IRF fabric fails before the IRF link is recovered (see Figure 12), use the mad restore command on the inactive IRF fabric to recover the inactive IRF fabric. The command also brings up all network ports that were shut down by MAD.

  • Page 33: Displaying And Maintaining An Irf Fabric

    LACP MAD-enabled IRF configuration example Network requirements As shown in Figure 13, set up a four-chassis IRF fabric at the access layer of the enterprise network. Configure LACP MAD on the multichassis aggregation to Device E, an HP device that supports extended LACP.
  • Page 34 Figure 13 Network diagram Configuration procedure Configure Device A: # Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.
  • Page 35 [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active Configure Device B: # Change the member ID of Device B to 2 and reboot the device to validate the change. <Sysname> system-view [Sysname] irf member 1 renumber 2 Renumbering the member ID may result in configuration change or loss.
  • Page 36 # Connect Device C to Device A as shown in Figure 13, and log in to Device C. This example uses the SFP+ port group that contains Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 for IRF links. # Shut down the physical interfaces. <Sysname>...
  • Page 37 # Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48 [Sysname-irf-port4/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...

  • Page 38: Arp Mad-Enabled Irf Configuration Example

    [Sysname-if-range] quit ARP MAD-enabled IRF configuration example Network requirements As shown in Figure 14, set up a four-chassis IRF fabric in the enterprise network. Configure ARP MAD in the IRF fabric and use the links connected to Device E for transmitting ARP •...
  • Page 39 # Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF-port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/47 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/48 [Sysname-irf-port1/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range] undo shutdown [Sysname-if-range] quit [Sysname] save...
  • Page 40 Configure Device C: # Change the member ID of Device C to 3 and reboot the device to validate the change. <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>...
  • Page 41 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 4/0/45 and Ten-GigabitEthernet 4/0/46 to IRF-port 4/1. [Sysname] irf-port 4/1 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/45 [Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF-port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48...

  • Page 42: Nd Mad-Enabled Irf Configuration Example

    The assigned domain ID is: 1 Configure Device E as the intermediate device: CAUTION: If the intermediate device is also in an IRF fabric, assign the two IRF fabrics different domain IDs for correct split detection. False detection causes IRF split. # Enable the spanning tree feature globally.
  • Page 43 Figure 15 Network diagram Configuration procedure Configure Device A: # Shut down the physical interfaces used for IRF links. This example uses the SFP+ port group that contains Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 for IRF links. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF-port 1/1.
  • Page 44 # Activate the IRF port configuration. [Sysname] irf-port-configuration active Configure Device B: # Change the member ID of Device B to 2 and reboot the device to validate the change. <Sysname> system-view [Sysname] irf member 1 renumber 2 Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y [Sysname] quit <Sysname>...
  • Page 45 # Shut down the physical interfaces. <Sysname> system-view [Sysname] interface range ten-gigabitethernet 3/0/45 to ten-gigabitethernet 3/0/48 [Sysname-if-range] shutdown [Sysname-if-range] quit # Bind Ten-GigabitEthernet 3/0/47 and Ten-GigabitEthernet 3/0/48 to IRF-port 3/1. [Sysname] irf-port 3/1 [Sysname-irf-port3/1] port group interface ten-gigabitethernet 3/0/47 [Sysname-irf-port3/1] port group interface ten-gigabitethernet 3/0/48 [Sysname-irf-port3/1] quit # Bind Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to IRF-port 3/2.
  • Page 46 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48 [Sysname-irf-port4/2] quit # Bring up the SFP+ ports and save the configuration. [Sysname] interface range ten-gigabitethernet 4/0/45 to ten-gigabitethernet 4/0/48 [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 47 [DeviceC-mst-region] instance 1 vlan 3 [DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit # Create VLAN 3, and add ports Ten-GigabitEthernet 1/0/1, Ten-GigabitEthernet 1/0/2, Ten-GigabitEthernet 1/0/3, and Ten-GigabitEthernet 1/0/4 to VLAN 3 for forwarding ND MAD packets. [DeviceE] vlan 3 [DeviceE-vlan3] port ten-gigabitethernet 1/0/1 to ten-gigabitethernet 1/0/4 [DeviceE-vlan3] quit...

  • Page 48: Setting Up An Eirf System

    Setting up an eIRF system Overview eIRF integrates multiple lower-layer devices with a higher-layer IRF fabric to provide high-density, low-cost connectivity at the access layer. In an eIRF system, the higher-layer IRF fabric is called the parent fabric and the lower-layer devices are called port extenders (PEXs).
  • Page 49 Figure 16 eIRF application scenario eIRF provides the following benefits: Simplified topology—Devices in an eIRF system appear as one node. For redundancy and load • balancing, a downstream or upstream device can connect to the eIRF system through multichassis link aggregation. Together with link aggregation, eIRF creates a loop-free Layer 2 network. The spanning tree feature is not needed among devices in the eIRF system or on the link aggregations.

  • Page 50: Basic Concepts

    Network scalability and resiliency—You can increase the number of ports in an eIRF system by • adding PEXs without changing network topology. High availability—Each PEX has multiple high-speed physical ports for uplink connectivity to the • parent fabric. The links on these ports are aggregated and load balanced automatically. Decreased TCO—eIRF decreases hardware investments and management costs.

  • Page 51: Eirf Operating Mechanisms

    On the parent fabric, you must assign the PEX physical interfaces for one PEX to the same PEX port. On a PEX, you must connect all its PEX physical interfaces to the physical interfaces in the same PEX port. Table 4 describes the states of PEX physical interfaces.

  • Page 52: Hardware Compatibility

    Figure 17 Data forwarding model Hardware compatibility HP FlexFabric 5700 switches can only operate as PEXs. The parent devices are from HP 5900 switch series. For more information, see the IRF configuration guide for the HP 5900 switch.

  • Page 53: Configuration Restrictions And Guidelines

    • The highest-numbered four SFP+ ports on the front panel. • QSFP+ ports on the front panel. HP FlexFabric 5700 switches NOTE: Do not use both SFP+ and QSFP+ ports for PEX links. PEX cabling requirements When you connect the parent fabric and PEXs, follow these cabling restrictions and guidelines: On the parent fabric, connect a PEX port's all physical interfaces to the same PEX.

  • Page 54: Configuring The Device As A Pex

    Configuring the device as a PEX To add the device to an eIRF system as a PEX, you must change its operating mode to auto or PEX. To configure the device as a PEX: Step Command Remarks Enter system view. system-view By default, the device operates in auto mode.

  • Page 55: Support And Other Resources

    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. •...

  • Page 56: Conventions

    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 57 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 58: Index

    Index Numerics IRF bridge MAC persistence, IRF fabric, 14, 10-GE IRF fabric ARP MAD, IRF 10-GE grouped port restrictions, IRF fabric LACP MAD, IRF fabric ND MAD, accessing IRF LACP MAD, IRF fabric, IRF link load sharing mode, application IRF link load sharing mode (global), IRF ARP MAD application scenario, IRF link load sharing mode (port-specific), IRF LACP MAD application scenario,...
  • Page 59 IRF software auto-update, ARP MAD configuration, establishing basic concepts, eIRF membership establishment, bridge MAC persistence, excluding collision handling, IRF port from shutdown action, configuration backup, configuration restrictions, configuration synchronization, fabric device member ID assignment, IRF ARP MAD, device member priority, IRF bridge MAC persistence, domain ID, IRF configuration, 14,...
  • Page 60 MAD, IRF mode configuration (port-specific), MAD configuration, local MAD detection, IRF fabric access local login, MAD handling procedure, MAD mechanism, MAC addressing master election, IRF bridge MAC persistence, member device description, member ID, ARP. See ARP MAD member priority, IRF fabric recovery, member role, IRF MAD, merge,...
  • Page 61 eIRF PEX port, physical interface eIRF PEX virtual slot number, IRF 10-GE grouped port restrictions, eIRF roles, IRF QSFP+ port restrictions, IRF ARP MAD, IRF restrictions, IRF ARP MAD configuration, IRF SFP+ port restrictions, IRF configuration synchronization, IRF SFP+ port restrictions (5700-48G-4XG-2QSFP+), IRF fabric ARP MAD configuration, IRF transceiver modules+cables restrictions,...
  • Page 62 configuring IRF member device description, IRF SFP+ port restrictions (5700-48G-4XG-2QSFP+), configuring IRF ND MAD, shutting down connecting IRF physical interface, IRF port shutdown exclusion, displaying IRF fabric, software enabling IRF software auto-update, IRF software auto-update, excluding IRF port from shutdown action, specifying planning IRF fabric setup, IRF device member priority,...
  • Page 63 IRF ND MAD configuration, IRF port shutdown exclusion, updating IRF software auto-update, virtual eIRF PEX virtual slot number, virtual technologies eIRF system setup, IRF ARP MAD, IRF ARP MAD configuration, IRF basic concepts, IRF bridge MAC persistence, IRF configuration synchronization, IRF device member ID assignment, IRF device member priority, IRF fabric access CLI login,...

Table of Contents