Table of Contents

Advertisement

Virtual Technologies Configuration Guide(V7)
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: SR6602X-CMW710-R7103
SR6600X-CMW710-R7103-RSE3
SR6600-CMW710-R7103-RPE3
Document version: 20150715-6PW100
H3C SR6600/SR6600-X Routers

Advertisement

Table of Contents
loading

Summary of Contents for H3C SR6600

  • Page 1 H3C SR6600/SR6600-X Routers Virtual Technologies Configuration Guide(V7) Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: SR6602X-CMW710-R7103 SR6600X-CMW710-R7103-RSE3 SR6600-CMW710-R7103-RPE3 Document version: 20150715-6PW100...
  • Page 2 Copyright © 2007-2015, Hangzhou H3C Technologies Co., Ltd. and its licensors All rights reserved No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Hangzhou H3C Technologies Co., Ltd.
  • Page 3 Preface The H3C SR6600/SR6600-X documentation set includes 14 configuration guides, which describe the software features for the H3C SR6600/SR6600-X Routers and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
  • Page 4 bars, from which you select one choice, multiple choices, or none. The argument or keyword and argument combination before the ampersand (&) sign can &<1-n> be entered 1 to n times. A line that starts with a pound (#) sign is comments. GUI conventions Convention Description...
  • Page 5 Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support & Documents > Technical Documents] –...
  • Page 6 [Technical Support & Documents > Software Download] – Provides the documentation released with the software version. Technical support service@h3c.com http://www.h3c.com Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
  • Page 7: Table Of Contents

    Contents IRF overview ································································································································································· 1   Application scenario ························································································································································· 1   Network topology ····························································································································································· 1   IRF functionality ································································································································································· 1   Simplified topology ·················································································································································· 1   Single point of management ··································································································································· 2   Node redundancy ···················································································································································· 2   Link redundancy ······················································································································································· 3  ...
  • Page 8 Accessing the IRF fabric ················································································································································ 18   Configuring IRF member devices in IRF mode ············································································································ 18   Assigning an IRF domain ID to the IRF fabric ····································································································· 18   Changing the member ID of a device ················································································································· 19   Changing the priority of a member device ········································································································ 19  ...
  • Page 9: Irf Overview

    IRF overview H3C Intelligent Resilient Framework (IRF) technology combines multiple physical devices into one virtual system to provide data center class availability and scalability. IRF virtualizes devices at the same layer into one node. This node is called an IRF fabric.
  • Page 10: Single Point Of Management

    devices in the IRF fabric or on the link aggregations. IRF also simplifies the Layer 3 network topology because it reduces the number of routing peers. The network topology does not change when a device is added to or removed from the IRF fabric. As shown in Figure 2, Device A and Device B form a two-chassis IRF fabric.
  • Page 11: Link Redundancy

    Link redundancy IRF link aggregation You can use multiple physical links to connect two IRF member devices. IRF automatically aggregates the physical links for redundancy and load balancing. The IRF links in an aggregation can be located on different cards. Multichassis link aggregation You can use the Ethernet link aggregation feature to aggregate the physical links between an upstream or downstream device and multiple devices in the IRF fabric.
  • Page 12: Mpu Roles

    By default, the standby MPU of a device is automatically assigned the same ID as the active MPU. MPU roles Each IRF member device has one or two MPUs. The following are MPU roles: Role Description Active MPU of the master device. It is also called the global active MPU. You Master MPU configure and manage the entire IRF fabric at the CLI of the global active MPU.
  • Page 13: 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, IRF fabric 1 contains Device A and Device B, and IRF fabric 2 contains Device C and Device D.
  • Page 14: Irf Merge

    IRF merge IRF merge occurs when two split IRF fabrics reunite or when two independent IRF fabrics are united, as shown in Figure Figure 5 IRF merge Member priority Member priority determines the possibility of a member device to be elected the master. A member with higher priority is more likely to be elected the master.
  • Page 15: Multi-Active Handling Procedure

    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. For more information about the MAD mechanisms and their application scenarios, see "MAD mechanisms."...
  • Page 16: Mad Mechanisms

    MAD mechanisms IRF provides MAD mechanisms by extending LACP and BFD. IMPORTANT: Do not configure both BFD MAD and LACP MAD, because they handle collisions differently. Table 1 compares the MAD mechanisms and their application scenarios. Table 1 Comparison of MAD mechanisms Advantages Disadvantages Application scenario...
  • Page 17: Bfd Mad

    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." Figure 6 LACP MAD scenario Customer premise network Device LACP-enabled dynamic link aggregation LACP-enabled dynamic link aggregation IRF link...
  • Page 18 If the IRF fabric is integrated, only the MAD IP address of the master is effective. The master cannot • establish a BFD session with any other member. If you execute the display bfd session command, the state of the BFD sessions is Down. •...
  • Page 19: Setting Up An Irf Fabric

    This chapter guides you through the IRF fabric setup procedure. Hardware compatibility An SR6602-X router can form an IRF fabric only with SR6602-X routers. Other H3C SR6600 routers can form an IRF fabric 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 20 Module Candidate IRF physical interfaces FIP-240 The two GE ports. FIP-300 The 12 GE ports. FIP-310 The four GE ports and the two 10GBASE-R/W ports. The four GE ports with the highest port numbers and the two SFP+ fiber SAP-20GE2XP ports.
  • Page 21: Connecting Irf Ports

    Fundamentals Configuration Guide. Configuration backup H3C 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 22: Planning The Irf Fabric Setup

    Tasks at a glance Remarks (Optional.) Configuring IRF member devices in IRF mode: CAUTION: Assigning an IRF domain ID to the IRF fabric Changing member IDs in an IRF Changing the member ID of a device fabric can void member ID-related Changing the priority of a member device configuration and cause Adding physical interfaces to an IRF port...
  • Page 23: Specifying A Priority For Each Member Device

    Step Command Remarks Check the MemberID field. If the (Optional.) Verify the device does not have an IRF member ID assignment display irf configuration member ID, the field displays status. two hyphens (--). Enter system view. system-view Assign an IRF member ID to By default, the device does not irf member member-id the device.
  • Page 24: Saving Configuration To The Next-Startup Configuration File

    Step Command Remarks By default, no physical interfaces are bound to any IRF port. Repeat this step to assign multiple physical interfaces to the IRF port. Bind a physical interface to port group interface interface-type An IRF physical interface the IRF port. interface-number [ mode enhanced ] operates in enhanced mode after the IRF binding takes effect,...
  • Page 25: Setting The Operating Mode To Irf Mode

    Figure 9 Daisy-chain topology As shown in Figure 10, you can use relay devices (for example, Layer 2 switches), to connect two IRF member devices that are far away from each other. Figure 10 Daisy-chain topology with a relay Setting the operating mode to IRF mode By default, the device operates in standalone mode.
  • Page 26: Accessing The Irf Fabric

    After you change the operating mode, the device automatically reboots for the change to take effect. During the reboot, you may choose to have the system automatically convert the startup configuration file. Automatic configuration conversion prevents slot- or interface-related settings from becoming invalid. For example, the system adds member ID information to interface numbers and file paths in IRF mode.
  • Page 27: Changing The Member Id Of A Device

    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. Make sure you fully understand its impact on your live network. The new member ID takes effect at 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.
  • Page 28 To configure IRF ports: Step Command Remarks Enter system view. system-view • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type To shut down a range of IRF interface-number ] } &<1-5> physical interfaces, enter Method 2: interface range view.
  • Page 29: Enabling Irf Auto-Merge

    Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-5> Method 2: Enter interface view or interface range name name interface range view. [ interface { interface-type interface-number [ to interface-type interface-number ] } &<1-5>...
  • Page 30: Configuring A Member Device Description

    Step Command Remarks By default, this feature is Enable IRF auto-merge. irf auto-merge enable enabled. Configuring a member device description Step Command Remarks Enter system view. system-view Configure a description for a By default, no member device irf member member-id description text member device.
  • Page 31: Enabling Software Auto-Update For Software Image Synchronization

    Step Command Remarks Enter system view. system-view • Retain the bridge MAC address permanently even if the address owner has left the fabric: irf mac-address persistent always • Retain the bridge MAC address for By default, the IRF fabric's Configure IRF bridge MAC 6 minutes after the address owner bridge MAC address does not persistence.
  • Page 32: Setting The Irf Link Down Report Delay

    Configuration prerequisites Make sure the MPU you are adding to the IRF fabric has sufficient storage space for the new software images. If sufficient storage space is not available, the MPU deletes the current software images automatically. If the reclaimed space is still insufficient, the MPU cannot complete the auto-update. You must reboot the device that holds the MPU, and then access the Boot menus to delete files.
  • Page 33 An IRF fabric has only one IRF domain ID. You can change the IRF domain ID by using the irf • domain or mad enable command. The IRF domain IDs configured by using these commands overwrite each other. • To prevent a port from being shut down when the IRF fabric transits to the Recovery state, use the mad exclude interface command.
  • Page 34 Step Command Remarks • Enter interface range view: Method 1: interface range { interface-type interface-number [ to interface-type To assign a range of ports to the interface-number ] } &<1-5> aggregation group, enter Method 2: interface range view. Enter Ethernet interface view interface range name name or interface range view.
  • Page 35 Step Command Remarks Create a Layer 3 aggregate interface route-aggregation interface for BFD MAD. interface-number Return to system view. quit • Enter interface range view: Method 1: interface range { interface-type interface-number [ to To assign a range of ports to the interface-type BFD MAD-enabled aggregation interface-number ] } &<1-5>...
  • Page 36: Recovering An Irf Fabric

    To configure a port to not shut down when the IRF fabric transits to the Recovery state: Step Command Remarks Enter system view. system-view Configure a network port to By default, all network ports on a not shut down when the IRF mad exclude interface interface-type Recovery-state IRF fabric are shut fabric transits to the...
  • Page 37: Displaying And Maintaining An Irf Fabric

    Figure 12 Active IRF fabric fails before the IRF link is recovered To manually recover an inactive IRF fabric: Step Command Enter system view. system-view Recover the inactive IRF fabric. mad restore After the IRF fabric is recovered, all ports that have been shut down by MAD come up automatically. Displaying and maintaining an IRF fabric Execute display commands in any view.
  • Page 38: Lacp Mad-Enabled Irf Configuration Example

    As shown in Figure 13, 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 H3C device that supports extended LACP. Figure 13 Network diagram...
  • Page 39 # 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 40: Bfd Mad-Enabled Irf Configuration Example

    # Assign domain ID 1 to the IRF fabric. <Sysname> system-view [Sysname] irf domain 1 # Create a dynamic aggregate interface and enable LACP MAD. [Sysname] interface route-aggregation 2 [Sysname-Route-Aggregation2] link-aggregation mode dynamic [Sysname-Route-Aggregation2] mad enable You need to assign a domain ID (range: 0-4294967295) [Current domain is: 1]: The assigned domain ID is: 1...
  • Page 41 Figure 14 Network diagram Configuration procedure Configure Device A: # Assign member ID 1 to Device 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 42 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 43: Configuration Example For Restoring Standalone Mode

    <Sysname> system-view [Sysname] interface route-aggregation 1 [Sysname-Route-Aggregation1] quit # Add GigabitEthernet 1/4/0/1 and GigabitEthernet 2/4/0/1 to the aggregation group. [Sysname] interface gigabitethernet 1/4/0/1 [Sysname-GigabitEthernet1/4/0/1] port link-aggregation group 1 [Sysname-GigabitEthernet1/4/0/1] quit [Sysname] interface gigabitethernet 2/4/0/1 [Sysname-GigabitEthernet2/4/0/1] port link-aggregation group 1 [Sysname-GigabitEthernet2/4/0/1] quit # Configure a MAD IP address for each member device on the aggregate interface.
  • Page 44 Standby 1 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 The output shows that Device A is the master.
  • Page 45 Saving the converted configuration file to main board succeeded. Chassis 2 Slot 1: Saving the converted configuration file succeeded. Now rebooting, please wait... Device B automatically reboots to complete the operating mode change.
  • Page 46: Index

    Index A B C D G H I M N P S functionality,1 Accessing the IRF fabric,18 Application scenario,1 mechanisms,8 Master election,6 Multi-active handling procedure,7 Basic concepts,3 Network topology,1 Configuration examples,29 Configuring IRF member devices in IRF mode,18 Connecting IRF physical interfaces,16 Planning the IRF fabric setup,14...

This manual is also suitable for:

Sr6600-x

Table of Contents