HPE FlexFabric 12900E Series Configuration Manual
  1. Manuals
  2. Brands
  3. HPE Manuals
  4. Switch
  5. FlexFabric 12900E
  6. Configuration manual
HPE FlexFabric 12900E Series Configuration Manual

HPE FlexFabric 12900E Series Configuration Manual

Virtual technologies
Hide thumbs Also See for FlexFabric 12900E Series:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual
HPE FlexFabric
12900E & 12900 & 7900 Switch Series
Virtual Technologies Configuration Guide
HPE FlexFabric 12900E Switch Series
HPE FlexFabric 12900 Switch Series
HPE FlexFabric 7900 Switch Series
Part number: 5200-4954a
Software version: Release 2710 and later
Document version: 6W100-2018426

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FlexFabric 12900E Series and is the answer not in the manual?

Questions and answers

Related Manuals for HPE FlexFabric 12900E Series

Summary of Contents for HPE FlexFabric 12900E Series

  • Page 1 HPE FlexFabric 12900E & 12900 & 7900 Switch Series Virtual Technologies Configuration Guide HPE FlexFabric 12900E Switch Series HPE FlexFabric 12900 Switch Series HPE FlexFabric 7900 Switch Series Part number: 5200-4954a Software version: Release 2710 and later Document version: 6W100-2018426...
  • Page 2 © Copyright 2018 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 Configuring an IRF fabric ···································································1 About IRF ··································································································································· 1 IRF network model ················································································································ 1 IRF benefits ························································································································· 2 Basic concepts ····················································································································· 3 IRF network topology ············································································································· 5 Master election ····················································································································· 5 Interface naming conventions ·································································································· 6 File system naming conventions ······························································································· 6 Configuration synchronization ··································································································...
  • Page 4 Example: Configuring an ND MAD-enabled two-chassis IRF fabric ··············································· 46 Example: Restoring standalone mode ····················································································· 49 Configuring MDCs ·········································································· 52 About MDC ······························································································································· 52 MDC advantages ················································································································ 52 MDC applications ················································································································ 52 Default MDC and non-default MDCs ······················································································· 53 Interface management ········································································································· 53 Restrictions and guidelines: MDC configuration ···············································································...

  • Page 5: Configuring An Irf Fabric

    Configuring an IRF fabric About IRF The 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: Irf Benefits

    Figure 2 Two-chassis IRF fabric implementation schematic diagram Device A Device B (Member ID=1) (Member ID=2) Active MPU Active MPU Standby MPU Standby MPU IRF-port 2 IRF-port 1 IRF link Network IRF physical IRF physical Network interfaces interfaces interfaces interfaces An IRF fabric is formed.

  • Page 7: Basic Concepts

    Basic concepts 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).
  • Page 8 IRF physical interface IRF physical interfaces connect IRF member devices and must be bound to an IRF port. They forward traffic between member devices, including IRF protocol packets and data packets that must travel across IRF member devices. IRF split IRF split occurs when an IRF fabric breaks up into multiple IRF fabrics because of IRF link failures, as shown in Figure...

  • Page 9: Irf Network Topology

    Figure 5 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 network topology The 12900E, 12900 or 7900 switch series supports only two-chassis IRF fabrics in daisy-chain topology, as shown in Figure Figure 6 Daisy-chain topology...

  • Page 10: Interface Naming Conventions

    NOTE: Master election does not occur when split IRF fabrics merge. For information about the master device of the merged IRF fabric, see "Failure recovery." Master election selects a master in descending order: Current master, even if a new member has higher priority. When an IRF fabric is being formed, all members consider themselves as the master.

  • Page 11: Configuration Synchronization

    <Master> mkdir test Creating directory flash:/test... Done. <Master> cd test <Master> dir Directory of flash:/test The directory is empty. 1048576 KB total (651568 KB free) • To create and access the test folder under the root directory of the flash memory in slot 0 on member device 1: <Master>...
  • Page 12 LACP MAD and BFD MAD use the following process to handle a multi-active collision: Compare the number of members in each fabric. Set all fabrics to the Recovery state except the one that has the most members. Compare the member IDs of the masters if all IRF fabrics have the same number of members. Set all fabrics to the Recovery state except the one that has the lowest numbered master.

  • Page 13: Mad Mechanisms

    Figure 8 Active IRF fabric fails before the IRF link is recovered IP network IP network IRF fabric 2 IRF fabric 2 (Recovery) (Recovery) Execute the mad fabric 1 IRF fabric 1 restore command (Active) IRF fabric 1 fails on IRF fabric 2 fails before because of physical...
  • Page 14 Application Advantages Disadvantages mechanism scenarios close to one another. • Detection speed is • No intermediate device is slower than BFD MAD required. Spanning tree-enabled and LACP MAD. • Intermediate device, if non-link aggregation • The spanning tree used, can come from any ARP MAD IPv4 network scenarios if feature must be...
  • Page 15 Figure 9 LACP MAD scenario Customer premise network Intermediate device LACP-enabled dynamic link aggregation fabric LACP-enabled dynamic link aggregation IRF link Subordinate Master Internet Common traffic path LACP MAD traffic path BFD MAD BFD MAD detects multi-active collisions by using BFD. You can use common or management Ethernet ports for BFD MAD.
  • Page 16 NOTE: • The MAD addresses identify the member devices and must belong to the same subnet. • Of all management Ethernet ports on an IRF fabric, only the master's management Ethernet port is accessible. Figure 10 shows a typical BFD MAD scenario that uses an intermediate device. On the intermediate device, assign the ports on the BFD MAD links to the same VLAN.
  • Page 17 If common Ethernet ports are used, ARP MAD can work with or without an intermediate device. Make sure the following requirements are met: • If an intermediate device is used, connect each IRF member device to the intermediate device, as shown in Figure 12.

  • Page 18: Restrictions And Guidelines: Irf Configuration

    Restrictions and guidelines: IRF configuration Hardware compatibility with IRF An HPE FlexFabric 12900E switch can form an IRF fabric only with devices of the same model. In addition, an HPE FlexFabric 12900E switch that uses type-H service modules cannot form an IRF fabric with an HPE FlexFabric 12900E switch that uses type-F service modules.

  • Page 19: Software Requirements For Irf

    IRF fabric size An HPE FlexFabric 12900E IRF fabric can contain a maximum of two member devices. An HPE FlexFabric 12900 IRF fabric can contain a maximum of two member devices. An HPE FlexFabric 7900 IRF fabric can contain a maximum of two member devices.

  • Page 20: Transceiver Modules And Cables Selection For Irf

    The transceiver modules at the two ends of an IRF link must be the same type. For more information about the transceiver modules and DAC cables, see the switch installation guide and HPE Comware-Based Devices Transceiver Modules User Guide. NOTE: The transceiver modules and DAC cables available for the switch are subject to change over time.

  • Page 21: Irf Physical Interface Configuration Restrictions And Guidelines

    IRF physical interface configuration restrictions and guidelines Command configuration restrictions On a physical interface bound to an IRF port, you can execute only the following commands: • Interface commands, including: description  flow-interval  priority-flow-control  priority-flow-control no-drop dot1p  shutdown ...

  • Page 22: Feature Compatibility And Configuration Restrictions With Irf

    Feature compatibility and configuration restrictions with IRF System operating mode To form an IRF fabric, all member devices must work in the same system operating mode. To set the system operating mode, use the command. For more information about system-working-mode the system operating mode, see device management in Fundamentals Configuration Guide.

  • Page 23: Planning The Irf Fabric Setup

    Setting the operating mode to IRF mode Accessing the IRF fabric Configuring MAD Configure a minimum of one MAD mechanism on an IRF fabric. For the MAD compatibility, see "MAD mechanism compatibility." Configuring LACP MAD  Configuring BFD MAD  Configuring ARP MAD ...

  • Page 24: Setting Up An Irf Fabric

    Setting up an IRF fabric Assigning a member ID to each IRF member device About assigning an IRF member ID Assign a unique IRF member ID to a device before changing the device's operating mode to IRF. If you do not assign a member ID to the device, the device automatically uses the member ID of 1 after the mode changes to IRF.

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

    By default, no physical interfaces are bound to an IRF port. Repeat this step to assign multiple physical interfaces to the IRF port. Saving configuration to the next-startup configuration file About running configuration saving Save the running configuration before converting to the IRF mode. The mode change requires a reboot, which causes all unsaved settings to be lost.

  • Page 26: Accessing The Irf Fabric

    Accessing the IRF fabric The following methods are available for accessing an IRF fabric: • Local login—Log in through the console port of any member device. • Remote login—Log in at a Layer 3 interface on any member device by using methods including Telnet and SNMP.

  • Page 27: Configuring Bfd Mad

    Create an aggregate interface and enter aggregate interface view. Enter Layer 2 aggregate interface view.  interface bridge-aggregation interface-number Enter Layer 3 aggregate interface view.  interface route-aggregation interface-number Perform this step also on the intermediate device. Configure the aggregation group to operate in dynamic aggregation mode. link-aggregation mode dynamic By default, an aggregation group operates in static aggregation mode.
  • Page 28 Category Restrictions and guidelines BFD MAD links to the BFD MAD VLAN. On the IRF fabric, create a VLAN interface for the BFD MAD VLAN.  • Make sure the IRF fabrics on the network use different BFD MAD VLANs. •...
  • Page 29 Category Restrictions and guidelines configure IP addresses on the BFD MAD-enabled interface. Do not configure an IP address by using the ip address command or configure a VRRP virtual address on the BFD MAD-enabled interface. • Make sure all the MAD IP addresses are on the same subnet. When you configure BFD MAD that uses management Ethernet ports, follow these restrictions and guidelines: Category...
  • Page 30 Assign the port or the range of ports to the BFD MAD VLAN. Assign the ports to the VLAN as access ports.  port access vlan vlan-id Assign the ports to the VLAN as trunk ports.  port trunk permit vlan vlan-id Assign the ports to the VLAN as hybrid ports.

  • Page 31: Configuring Arp Mad

    port link-aggregation group number Return to system view. quit Enter Layer 3 aggregate interface view. interface route-aggregation interface-number Enable BFD MAD. mad bfd enable By default, BFD MAD is disabled. 10. Assign a MAD IP address to a member device on the Layer 3 aggregate interface. mad ip address ip-address { mask | mask-length } member member-id By default, no MAD IP addresses are configured on aggregate interfaces.
  • Page 32 Category Restrictions and guidelines • Run the spanning tree feature between the IRF fabric and the intermediate device to ensure that there is only one ARP MAD link in forwarding state. For more information about the spanning tree feature and its configuration, see Layer 2—LAN Switching Configuration Guide. •...
  • Page 33 interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ] To assign a range of ports to the ARP MAD VLAN, enter interface range view. To assign one port to the ARP MAD VLAN, enter Ethernet interface view. Assign the port or the range of ports to the ARP MAD VLAN.

  • Page 34: Configuring Nd Mad

    Configuring ND MAD Restrictions and guidelines When you configure ND MAD settings, follow these restrictions and guidelines: Category Restrictions and guidelines • Do not enable ND MAD on VLAN-interface 1. • If you are using an intermediate device, perform the following tasks: On the IRF fabric and the intermediate device, create a VLAN for ND ...

  • Page 35: Excluding Service Interfaces From The Shutdown Action Upon Detection Of Multi-Active Collision

    interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24> ] To assign a range of ports to the ND MAD VLAN, enter interface range view. To assign one port to the ND MAD VLAN, enter Ethernet interface view. Assign the port or the range of ports to the ND MAD VLAN.

  • Page 36: Recovering An Irf Fabric

    Procedure Enter system view. system-view Configure a service interface to not shut down when the IRF fabric transits to the Recovery state. mad exclude interface interface-type interface-number By default, all service interfaces on a Recovery-state IRF fabric are shut down, except for the service interfaces automatically excluded by the system.

  • Page 37: Changing The Priority Of A Member Device

    must be the same as the specified in the chassis-number member-id irf member member-id renumber new-member-id command. Changing the priority of a member device About changing IRF member priority You can change the priority of a member device so it can be elected the master in the next master election.

  • Page 38: Bulk-Configuring Basic Irf Settings For A Member Device

    Enter Ethernet interface view or interface range view. Enter Ethernet interface view.  interface interface-type interface-number Enter interface range view. Choose one of the following commands:  interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-24> interface range name name [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-24>...

  • Page 39: Enabling Irf Auto-Merge

    Procedure Enter system view. system-view Bulk-configure basic IRF settings for the device. easy-irf [ member member-id [ renumber new-member-id ] domain domain-id [ priority priority ] [ irf-port1 interface-list1 ] [ irf-port2 interface-list2 ] ] Make sure the new member ID is unique in the IRF fabric to which the device will be added. Enabling IRF auto-merge About IRF auto-merge When two IRF fabrics merge, you must reboot the member devices in the IRF fabric that fails in the...
  • Page 40 The following methods are available to configure the IRF bridge MAC address for an IRF fabric: • Specifying a MAC address as the IRF bridge MAC address. The IRF fabric always uses the specified MAC address as the IRF bridge MAC address. You can specify the bridge MAC address of an existing IRF fabric for a new IRF fabric to replace the existing IRF fabric with transient packet loss.

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

    Enabling software auto-update for software image synchronization About IRF software auto-update The software auto-update feature automatically propagates the software images of the global active MPU to all other MPUs (including new devices) in the IRF fabric. To join an IRF fabric, an MPU must use the same software images as the global active MPU in the fabric.

  • Page 42: Setting The Irf Link Down Report Delay

    Setting the IRF link down report delay About 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 43: Display And Maintenance Commands For Irf

    As shown in Figure 15, 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 HPE device that supports extended LACP. Figure 15 Network diagram...
  • Page 44 # Assign member ID 1 to Device A, and bind FortyGigE 2/0/1 and FortyGigE 3/0/1 to IRF-port 2. <Sysname> system-view [Sysname] irf member 1 [Sysname] irf-port 2 [Sysname-irf-port2] port group interface fortygige 2/0/1 [Sysname-irf-port2] port group interface fortygige 3/0/1 [Sysname-irf-port2] quit # Save the configuration.

  • Page 45: Example: Configuring A Bfd Mad-Enabled Two-Chassis Irf Fabric

    [Sysname-Bridge-Aggregation2] link-aggregation mode dynamic [Sysname-Bridge-Aggregation2] mad enable You need to assign a domain ID (range: 0-4294967295) [Current domain is: 1]: The assigned domain ID is: 1 MAD LACP only enable on dynamic aggregation interface. [Sysname-Bridge-Aggregation2] quit # Assign FortyGigE 1/2/0/2 and FortyGigE 2/2/0/2 to the aggregate interface. [Sysname] interface fortygige 1/2/0/2 [Sysname-FortyGigE1/2/0/2] port link-aggregation group 2 [Sysname-FortyGigE1/2/0/2] quit...
  • Page 46 Figure 16 Network diagram (IRF-port1/2) (IRF-port2/1) Device A Device B FGE1/2/0/1 FGE2/2/0/1 FGE1/3/0/1 FGE2/3/0/1 FGE1/2/0/2 FGE2/2/0/2 BFD link …… Procedure IMPORTANT: By default, interfaces on the devices are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the command to enable that interface.

  • Page 47: Vlan Interface

    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 Now rebooting, please wait... Configure Device B: # Assign member ID 2 to Device B, and bind FortyGigE 2/0/1 and FortyGigE 3/0/1 to IRF-port 1. <Sysname>...

  • Page 48: Example: Configuring An Arp Mad-Enabled Two-Chassis Irf Fabric

    Example: Configuring an ARP MAD-enabled two-chassis IRF fabric Network configuration As shown in Figure 17, set up a two-chassis IRF fabric at the distribution layer of the enterprise network. • Configure ARP MAD for the IRF fabric and use Device C as an intermediate device. Device C can come from any vendor.
  • Page 49 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 Now rebooting, please wait...

  • Page 50: Example: Configuring An Nd Mad-Enabled Two-Chassis Irf Fabric

    [Sysname] interface vlan-interface 3 [Sysname-Vlan-interface3] mad arp enable You need to assign a domain ID (range: 0-4294967295) [Current domain is: 1]: The assigned domain ID is: 1 [Sysname-Vlan-interface3] ip address 192.168.2.1 24 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.
  • Page 51 Figure 18 Network diagram Device C FGE1/0/1 FGE1/0/2 FGE1/2/0/2 FGE2/2/0/2 FGE1/2/0/1 FGE2/2/0/1 FGE1/3/0/1 FGE2/3/0/1 Device A Device B (IRF-port1/2) (IRF-port2/1) Procedure IMPORTANT: By default, interfaces on the devices are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the command to enable that interface.
  • Page 52 [Sysname-irf-port1] port group interface fortygige 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 Device B. (Details not shown.) # Enable IRF mode. <Sysname> system-view [Sysname] chassis convert mode irf The device will switch to IRF mode and reboot.

  • Page 53: Example: Restoring Standalone Mode

    # Enable the spanning tree feature globally, and map the ND MAD VLAN to MSTI 1 in the MST region. <DeviceC> system-view [DeviceC] 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 FortyGigE 1/0/1 and FortyGigE 1/0/2 to VLAN 3.
  • Page 54 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 Mac persistent : always Domain ID Auto merge : yes...
  • Page 55 Device B automatically reboots to complete the operating mode change.

  • Page 56: Configuring Mdcs

    Configuring MDCs About MDC The Multitenant Device Context (MDC) technology can partition a physical device or an IRF fabric into multiple logical devices. Each of the logical devices is called an MDC. MDC advantages Each MDC uses its own hardware and software resources, runs independently of other MDCs, and provides services for its own customer.

  • Page 57: Default Mdc And Non-Default Mdcs

    Default MDC and non-default MDCs A device supporting MDCs is called the default MDC (for example, Device in Figure 20). The default MDC always uses the name Admin and the ID 1. You cannot delete it or change its name or ID. When you log in to the physical device, you are logged in to the default MDC.

  • Page 58: Creating An Mdc

    Starting an MDC Assigning hardware resources to an MDC Assigning physical interfaces and LPUs to MDCs  Specifying a CPU weight for an MDC  Specifying a memory space percentage for an MDC  Accessing an MDC (Optional.) Returning to the default MDC (Optional.) Deleting an MDC Creating an MDC...

  • Page 59: Assigning Hardware Resources To An Mdc

    Assigning hardware resources to an MDC About assigning hardware resources When you create an MDC, the system automatically assigns resources to the MDC, including CPU resources and memory space. You can adjust the resource allocations as required. An MDC needs interfaces to forward packets. The system does not automatically assign LPUs or interfaces to MDCs.
  • Page 60 Figure 21 IRF links for MDCs Interface A IRF link Interface D MDC Admin MDC Admin Interface B IRF link Interface E MDC A MDC A Interface C MDC B MDC B IRF link Interface F MDC C MDC C Master Subordinate •...

  • Page 61: Specifying A Cpu Weight For An Mdc

    If the command is not displayed for an LPU that you want to assign to a undo location non-default MDC, the LPU belongs to the default MDC. Use the undo location command to reclaim the LPU from the default MDC. Return to system view.

  • Page 62: Specifying A Memory Space Percentage For An Mdc

    limit-resource cpu weight weight-value The defaults are as follows: The default MDC has a CPU weight of 10 on each MPU and each LPU.  Each non-default MDC has a CPU weight of 10 on each MPU and each assigned LPU. ...

  • Page 63: Returning To The Default Mdc

    Restrictions and guidelines This feature provides the only method for you to access an MDC for the first time. After using this feature to access an MDC, you can perform the following tasks to allow the administrator of the MDC to log in to the MDC by using Telnet or SSH: •...

  • Page 64: Display And Maintenance Commands For Mdc

    If the MDC has IRF physical interfaces, use the command to remove the undo port group binding of physical interfaces to IRF ports. Reclaim the LPUs assigned to the MDC. undo location Reclaim the physical interfaces assigned to the MDC. undo allocate interface Delete the MDC.
  • Page 65 Figure 22 Network diagram Internet Device MDC A MDC B LAN 1 LAN 1 Server Server Department A Department B Procedure IMPORTANT: By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.
  • Page 66 [Device-mdc-2-MDCA] allocate interface ten-gigabitethernet 2/0/1 to ten-gigabitethernet 2/0/24 Configuration of the interfaces will be lost. Continue? [Y/N]:y Execute the location slot command in this view to make the configuration take effect. [Device-mdc-2-MDCA] quit # Authorize MDCA to use the LPU in slot 2. [Device-mdc-2-MDCA] location slot 2 # Set the CPU weight to 5 for MDCA.
  • Page 67 [MDCA-M-GigabitEthernet0/0/0] quit [MDCA] telnet server enable [MDCA] user-interface vty 0 63 [MDCA-line-vty0-63] authentication-mode none [MDCA-line-vty0-63] user-role mdc-admin # Return to the default MDC. [MDCA-line-vty0-63] return <MDCA> switchback [Device] Configure the management Ethernet interface for MDCB: # Log in to MDCB from the default MDC. Press Ctrl+D as prompted to access the CLI of MDCB.

  • Page 68: Example: Configuring Mdcs (In Irf Mode)

    ****************************************************************************** * Copyright (c) 2010-2017 Hewlett Packard Enterprise Development LP * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <MDCA> display current-configuration Example: Configuring MDCs (in IRF mode) Network configuration As shown in Figure 23, two departments need to use the IRF fabric to access the Internet.
  • Page 69 Figure 23 Network diagram IP network Chassis 1 Chassis 2 Slot 2 Slot 2 IRF link 1 HGE1/2/0/1 HGE2/2/0/1 MDC Admin MDC Admin MDC A MDC A Slot 3 Slot 3 HGE1/3/0/1 IRF link 2 HGE2/3/0/1 MDC B MDC B Master Standby HGE1/2/0/12...
  • Page 70 [IRF-mdc-3-MDCB] quit The output shows that MDCB is created successfully. As a best practice, make sure MDCB is created successfully before you perform the following tasks. Remove the bindings of HundredGigE 1/2/0/1 and HundredGigE 2/2/0/1 to IRF ports: TIP: To avoid IRF fabric split, make sure the other IRF link is in up state while you are performing the following tasks.
  • Page 71 [IRF-mdc-2-MDCA] quit Re-authorize the default MDC to use the two LPUs. [IRF] mdc Admin [IRF-mdc-1-Admin] location chassis 1 slot 2 [IRF-mdc-1-Admin] location chassis 2 slot 2 [IRF-mdc-1-Admin] quit Rebind HundredGigE 1/2/0/1 and HundredGigE 2/2/0/1 to IRF ports: # Bind HundredGigE 1/2/0/1 to IRF-port 1/1. [IRF] irf-port 1/1 [IRF-irf-port1/1] port group interface hundredgige1/2/0/1 [IRF-irf-port1/1] quit...
  • Page 72 [MDCA] user-interface vty 0 63 [MDCA-line-vty0-63] authentication-mode none [MDCA-line-vty0-63] user-role mdc-admin # Return to the default MDC. [MDCA-line-vty0-63] return <MDCA> switchback [IRF] Remove the bindings of HundredGigE 1/3/0/1 and HundredGigE 2/3/0/1 to IRF ports: TIP: To avoid IRF fabric split, make sure the other IRF link is in up state while you are performing the following tasks.
  • Page 73 [IRF-mdc-3-MDCB] limit-resource cpu weight 5 # Start MDCB. [IRF-mdc-3-MDCB] mdc start It will take some time to start MDC... MDC started successfully. [IRF-mdc-3-MDCB] quit 11. Rebind HundredGigE 1/3/0/1 and HundredGigE 2/3/0/1 to IRF ports: # Log in to MDCB from the default MDC. Press Ctrl+D as prompted to stop automatic MDC configuration and access the CLI of MDCB.
  • Page 74 * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <MDCB> system-view # Bring up HundredGigE 1/3/0/1 and HundredGigE 2/3/0/1. [MDCB] interface range hundredgige 1/3/0/1 hundredgige 2/3/0/1 [MDCB-if-range] undo shutdown [MDCB-if-range] quit # Assign an IP address to the management interface and configure Telnet login. [MDCB] display interface m-gigabitethernet brief Brief information on interfaces in route mode: Link: ADM - administratively down;...
  • Page 75 HundredGigE2/2/0/1(MDC1) HundredGigE2/3/0/1(MDC3) The output shows that two IRF links exist and are in up state. One IRF link is on the default MDC, and the other IRF link is on MDCB. Log in to MDCA as an administrator of Department A. View the running configuration of the MDC.

  • Page 76: Document Conventions And Icons

    Document conventions and icons Conventions This section describes the conventions used in the documentation. 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.

  • Page 77: 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 78: 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 79: Customer Self Repair

    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 80: Index

    Index IRF physical interface+port (standalone mode), accessing bridging IRF fabric, IRF bridge MAC address, MDC, IRF bridge MAC persistence, adding bulk IRF physical interface, IRF basic settings bulk configuration, aggregating IRF fabric link aggregation capability configuration restrictions, cable application IRF fabric transceiver module+cable restrictions, IRF fabric ARP MAD application scenario, IRF fabric BFD MAD application scenario, card...
  • Page 81 default IRF physical interface+port bind (standalone mode), MDC, IRF service interface shutdown exclusion, deleting IRF setting optimization, MDC, IRF software auto-update, detecting MDC access, IRF fabric ARP MAD, MDC application, IRF fabric BFD MAD, MDC configuration, 52, 53, 60, 64 IRF fabric failure recovery, MDC CPU weight specification, IRF fabric LACP MAD,...
  • Page 82 IRF fabric ARP MAD, ARP MAD configuration (VLAN interface), IRF fabric ARP MAD configuration ARP MAD configuration restrictions, (2-chassis), auto-merge enable, IRF fabric BFD MAD, basic concepts, IRF fabric BFD MAD configuration basic settings bulk-configuration, (2-chassis), basic settings bulk-configuration restrictions, IRF fabric configuration, 1, 18 BFD MAD,...
  • Page 83 fabric transceiver module+cable restrictions, LACP MAD. See LACP MAD interface card removal, LACP MAD interface card replacement, IRF configuration, LACP MAD, IRF fabric configuration (2-chassis), LACP MAD configuration, IRF fabric LACP MAD, link down report delay, link down report delay restrictions, default MDC, MAD, MDC application,...
  • Page 84 IRF fabric restrictions, IRF ARP MAD configuration, memory space percentage specification, IRF basic settings bulk-configuration, non-default MDC, IRF BFD MAD configuration, physical interface+LPU assignment, IRF configuration synchronization, physical interface+LPU assignment IRF fabric ARP MAD, restrictions, IRF fabric ARP MAD configuration (2-chassis), start, IRF fabric BFD MAD, member...
  • Page 85 physical configuring IRF BFD MAD (Layer 3 aggregate interface), IRF interface addition, configuring IRF BFD MAD (management Ethernet IRF physical interface, port), IRF physical interface connection, configuring IRF bridge MAC address, IRF port bind (standalone mode), configuring IRF bridge MAC persistence, planning configuring IRF fabric, IRF fabric setup,...
  • Page 86 resource IRF bridge MAC address, MDC hardware resource assignment, IRF device member priority (standalone mode), restoring MDC CPU weight, IRF fabric standalone mode, MDC memory space percentage, restrictions split IRF ARP MAD configuration, IRF fabric ARP MAD, IRF basic settings bulk-configuration, IRF fabric BFD MAD, IRF BFD MAD configuration, IRF fabric LACP MAD,...
  • Page 87 IRF bridge MAC address configuration, IRF network topology, IRF bridge MAC address configuration IRF next-startup configuration file, restrictions, IRF operating mode set, IRF bridge MAC persistence, IRF operating mode setting restrictions, IRF configuration restrictions, IRF physical interface connection, IRF configuration synchronization, IRF physical interface+port bind (standalone mode), IRF device member ID change,...

This manual is also suitable for:

Flexfabric 12900e seriesflexfabric 7900 seriesFlexfabric 12900 series

Table of Contents