Download
Share
Print this page
H3C S12500 Series Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S12500 Series
  6. Configuration manual
H3C S12500 Series Configuration Manual

H3C S12500 Series Configuration Manual

Routing switches
Hide thumbs Also See for S12500 Series:

Advertisement

Quick Links

Download this manual
H3C S12500 Series Routing Switches
IRF Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: S12500-CMW710-R7128
Document version: 6W710-20121130

Advertisement

loading
Need help?

Need help?

Do you have a question about the S12500 Series and is the answer not in the manual?

Questions and answers

Related Manuals for H3C S12500 Series

Summary of Contents for H3C S12500 Series

  • Page 1 H3C S12500 Series Routing Switches IRF Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: S12500-CMW710-R7128 Document version: 6W710-20121130...
  • Page 2 SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners Notice The information in this document is subject to change without notice.
  • Page 3 The IRF Configuration Guide describes the Intelligent Resilient Framework (IRF) technology developed by H3C. It covers the basic concepts and working process of an IRF fabric, and describes how to configure and access an IRF fabric.
  • Page 4 Layer 2 forwarding and other Layer 2 features. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your switch. About the H3C S12500 documentation set The H3C S12500 documentation set includes: Category...
  • 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 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 Contents IRF overview ································································································································································· 1   Hardware compatibility ···················································································································································· 1   IRF benefits ········································································································································································· 1   Application scenario ························································································································································· 1   Network topologies ·························································································································································· 2   Basic concepts ··································································································································································· 2   Operating mode ······················································································································································· 4   IRF member roles ······················································································································································ 4  ...
  • Page 8 Configuring a member device description ········································································································· 24   Configuring IRF bridge MAC persistence ··········································································································· 24   Enabling software auto-update for system software image synchronization ·················································· 25   Setting the IRF link down report delay ················································································································ 26   Enabling IRF link failure detection and auto-recovery ······················································································· 26  ...
  • Page 9 This book describes IRF concepts and guides you through the IRF setup procedure. Hardware compatibility An H3C S12500 switch can form an IRF fabric only with devices in the same series. IRF benefits IRF delivers the following benefits: •...
  • Page 10 Figure 1 IRF application scenario IP network IP network Standby Master Equal to IRF link Network topologies An IRF fabric can use a daisy chain topology or a ring topology. Full mesh topology is not supported. For information about connecting IRF member devices, see "Connecting IRF physical ports."...
  • Page 11 Figure 2 Two-chassis IRF fabric implementation schematic diagram In this figure, Device A and Device B form a two-chassis IRF fabric that has four MPUs (one active and three standbys) and two times the number of interface cards that a single device provides. The IRF fabric manages the physical and software resources of Device A and Device B in a centralized manner.
  • Page 12 Figure 3 Four-chassis IRF fabric implementation schematic diagram 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. •...
  • Page 13 elect a new master from among them to take over. For more information about master election, see "Master election." While backing up the master, all standby devices process and forward traffic independently. IRF member ID An IRF fabric uses member IDs to uniquely identify and manage its members. If two devices have the same IRF member ID, they cannot form an IRF fabric.
  • Page 14 To use an IRF port, you must bind at least one physical port to it. These ports are called "IRF physical ports." The physical ports assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down only if all its member physical ports are down.
  • Page 15 Figure 5 IRF split IRF merge IRF merge occurs when split IRF fabrics re-unite or when two independent IRF fabrics are united, as shown in Figure Figure 6 IRF merge IRF 1 IRF 2 XGE1/3/0/1 XGE2/3/0/1 IRF link Device A Device A Device B Device B...
  • Page 16 After a master election, all standby devices reboot with the configuration on the master, and their original next-startup configuration files do not take effect. IRF multi-active detection An IRF link failure causes an IRF fabric to split in two IRF fabrics operating with the same Layer 3 configurations, including the same IP address.
  • Page 17 Figure 7. In addition, the intermediate device must be an H3C 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 18 BFD MAD BFD MAD can work with or without intermediate devices. Figure 8 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 19 You can set up ARP MAD links between neighbor IRF member devices, or more commonly, between each IRF member device and an intermediate device (see Figure 9). If an intermediate device is used, you must also run the spanning tree feature between the IRF fabric and the intermediate device. Figure 9 ARP MAD application scenario Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID:...
  • Page 20 MPUs of a member device. If a member device has two MPUs, the MPUs must be the same model. • Both fiber and copper Ethernet ports can be used for IRF connection. H3C recommends using • 10-GE fiber ports for high performance.
  • Page 21 Save any configuration you have made to the startup configuration file before rebooting the IRF • member devices. Setup and configuration task list H3C recommends the following IRF fabric setup and configuration procedure: Setup and configuration procedure Remarks (Required.) Planning the IRF fabric setup (Required.)
  • Page 22 Setup and configuration procedure Remarks (Optional.) Enabling enhanced IRF mode in standalone If more than two devices are used to form mode one IRF fabric, this step is required. (Required.) Saving configuration to the next-startup configuration file (Required.) Connecting IRF physical ports Make sure that they are interoperable.
  • Page 23 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 24 Bind a physical IRF port to port group interface interface-type 12 physical ports to the IRF port. the IRF port. interface-number H3C recommends not creating MDCs on the device in standalone mode. Verify that the physical port has been bound to the IRF display irf configuration port.
  • Page 25 Step Command Remarks By default, enhanced IRF mode is disabled. After the enhanced IRF mode is enabled, you cannot create Enable enhanced IRF mode. irf mode enhanced Layer 3 Ethernet interfaces or subinterfaces or Layer 3 aggregate interfaces or subinterfaces. Saving configuration to the next-startup configuration file Save the running configuration before connecting IRF physical links.
  • Page 26 Figure 11 Daisy chain topology versus ring topology If two IRF member devices are far away from each other (for example, if they are in different cities), you can use a relay device, such as a Layer 2 switch, to connect them, as shown in Figure Figure 12 Daisy chain topology with a relay Setting the operating mode to IRF mode...
  • Page 27 Step Command Remarks Set the operating mode to The default operating mode is chassis convert mode irf IRF mode. standalone mode. After you change the operating mode, the device automatically reboots to validate the change. During the reboot, you may choose to have the system automatically convert the startup configuration file to prevent some slot- or interface-related configurations from becoming invalid.
  • Page 28 Figure 13 A network that comprises two IRF domains Core network IRF 1 (domain 10) Device A Device B IRF link IRF 2 (domain 20) Device D Device c IRF link Access network To assign a domain ID to an IRF fabric: Step Command Remarks...
  • Page 29 Step Command Remarks Save the running save [ safely ] [ force ] configuration. The chassis-number must be the same as the member-id specified Reboot the member device. reboot chassis chassis-number in the irf member member-id renumber new-member-id command. Changing the priority of a member device You can change the priority of a member device so it can be elected the master at the next master election.
  • Page 30 Step Command Remarks • Enter interface range view: Approach 1: interface range { interface-type interface-number [ to interface-type interface-number ] } &<1-5> To shut down a range of physical IRF ports, enter interface range Approach 2: Enter Ethernet interface view view.
  • Page 31 Enabling enhanced IRF mode in IRF mode You can enable enhanced IRF mode in both standalone and IRF modes. To enable enhanced IRF mode in IRF mode, you should follow these guidelines: Each member device must have two MPUs. • •...
  • Page 32 The auto reboot function does not take effect on the IRF fabric merge caused by binding a physical port to an IRF port in IRF mode. You must manually reboot the devices that have been defeated in the master election to complete the merge. To enable auto reboot for IRF fabric merge: Step Command...
  • Page 33 If two IRF fabrics have the same bridge MAC address, they cannot merge. To configure the IRF bridge MAC persistence setting: Step Command Remarks Enter system view. system-view • Keep the bridge MAC address unchanged even if the master has changed: irf mac-address persistent always By default, the IRF fabric's...
  • Page 34 Step Command Remarks Enter system view. system-view Enable software By default, this function is irf auto-update enable auto-update. enabled. Setting the IRF link down report delay You can avoid link flapping causing frequent IRF splits and merges during a short time by configuring the IRF ports to delay reporting link down events.
  • Page 35 • Detection speed is fast. Requires an intermediate downstream device. LACP MAD • H3C device that supports Requires no MAD-dedicated For information about extended LACP for MAD. physical ports or interfaces. LACP, see Layer 2—LAN Switching Configuration...
  • Page 36 When you use LACP MAD, follow these guidelines: • The intermediate device must be an H3C device that support extended LACP for MAD. If the intermediate device is in an IRF fabric, assign this fabric a different domain ID than the LACP •...
  • Page 37 Step Command Remarks Create a Layer 2 aggregate interface bridge-aggregation Perform this step also on the interface and enter interface-number intermediate device. aggregate interface view. By default, an aggregation group operates in static Configure the aggregation aggregation mode. group to operate in dynamic link-aggregation mode dynamic aggregation mode.
  • Page 38 Do not use the BFD MAD VLAN for any other purpose. No Layer 2 or Layer 3 features, including • ARP and LACP, can work on the BFD MAD-enabled VLAN interface or any port in the VLAN. If you configure any other feature on the VLAN, neither the configured feature nor the BFD MAD function can work correctly.
  • Page 39 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 a Assign the port or the range BFD MAD has no requirement trunk port: of ports to the BFD MAD...
  • Page 40 Step Command Remarks The default IRF domain ID is 0. You can change the IRF domain Assign a domain ID to the IRF irf domain domain-id ID only in the Admin MDC. The fabric. domain ID setting takes effect on all MDCs.
  • Page 41 Step Command Remarks By default, ARP MAD is disabled. After ARP MAD is enabled, the system instructs you to assign an IRF domain ID. At the prompt, Enable ARP MAD. mad arp enable enter a new domain ID or press Enter to confirm the domain ID you have assigned.
  • Page 42 Figure 14 Recovering the IRF fabric If the Active-state fabric has failed, for example, because of device or link failures, before the IRF link is recovered (see Figure 15), use the mad restore command on the Recovery-state fabric to change its state to Active to take over.
  • Page 43 The recovery procedure differs depends on whether a two-chassis device is available. H3C recommends performing fast IRF configuration restoration in IRF mode. This section assumes that the failed member device is Device A. If a two-MPU member device (Device B in this example) is available, use the following procedure:...
  • Page 44 Set up a two-chassis IRF fabric at the access layer of the enterprise network in Figure 16. Configure LACP MAD in the IRF fabric, because the IRF fabric has a multichassis aggregate link to Device C, an H3C device that supports extended LACP. Figure 16 Network diagram...
  • Page 45 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. Configure Device A: # Assign member ID 1 to Device A and bind Ten-GigabitEthernet 3/0/1 to IRF-port 2. <Sysname>...
  • Page 46 [Sysname-Ten-GigabitEthernet3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit # Save the configuration. [Sysname] quit <Sysname> save # Connect the two devices as shown in Figure # 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.
  • Page 47 %May 7 09:23:16:370 2010 H3C IFNET/3/LINK_UPDOWN: Bridge-Aggregation2 link status is UP. %May 7 09:23:16:381 2010 H3C IFNET/3/LINK_UPDOWN: Vlan-interface1 link status is UP. %May 7 09:23:16:391 2010 H3C IFNET/5/LINEPROTO_UPDOWN: Line protocol on the interface Vlan-interface1 is UP. The output shows that Device B is restored.
  • Page 48 MemberID Slot Role Priority CPU-Mac Description Standby 1 00e0-fc0f-8c02 ----- Master 00e0-fc0f-8c20 ----- -------------------------------------------------- * indicates the device is the master. + indicates the device through which the user logs in. The Bridge MAC of the IRF is: 0023-895f-954f Auto upgrade : yes Mac persistent : always...
  • Page 49 # 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. [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit [Sysname] irf-port 2...
  • Page 50 When an IRF split is detected, the system outputs an error message. %May 6 15:10:05:477 2010 H3C MAD/1/MAD_COLLISION_DETECTED: Multi-active devices detected, please fix it. Having a higher member ID than Device A, Device B transits to the Recovery state and shuts down...
  • Page 51 #May 6 15:31:09:724 2010 H3C DEVM/1/REBOOT: Reboot device by command. %May 6 15:31:09:734 2010 H3C DEVM/5/SYSTEM_REBOOT: System is rebooting now. # After the IRF merge is complete, verify that the IRF fabric is recovered. <Sysname> display irf topology Topology Info...
  • Page 52 Figure 18 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 53 Now rebooting, please wait... Configure Device B: # Assign member ID 2 to Device B and bind Ten-GigabitEthernet 3/0/1 to IRF-port 1. <Sysname> system-view [Sysname] irf member 2 Info: Member ID change will take effect after the member reboots and operates in IRF mode.
  • Page 54 [Sysname-vlan3] quit # Create VLAN-interface 3, assign it an IP address, and enable ARP MAD on the interface. [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:...
  • Page 55 Figure 19 Network diagram Device E IP network XGE1/3/0/2 XGE4/3/0/2 (IRF-port1/1) XGE1/3/0/1 XGE2/3/0/1 XGE3/3/0/2 (IRF-port4/2) XGE3/3/0/1 (IRF-port1/2) (IRF-port2/1) (IRF-port3/1) (IRF-port3/2) XGE4/3/0/1 Device C Device B Device A (IRF-port4/1) XGE2/3/0/2 Device D (IRF-port2/2) The orange lines represent IRF links. The black lines represent Ethernet links. The gray circles represent aggregate links. Configuration procedure IMPORTANT: For two neighboring IRF members, IRF links must be bound to IRF-port 1 on one member and to IRF-port...
  • Page 56 [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 # Enable enhanced IRF mode. [Sysname] irf mode enhanced # Save the configuration. [Sysname] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y...
  • Page 57 [Sysname-irf-port2] quit [Sysname] interface ten-gigabitethernet 3/0/2 [Sysname-Ten-GigabitEthernet3/0/2] undo shutdown [Sysname-Ten-GigabitEthernet3/0/2] quit # Enable enhanced IRF mode. [Sysname] irf mode enhanced # Save the configuration. [Sysname] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file.
  • Page 58 [Sysname] interface ten-gigabitethernet 3/0/1 [Sysname-Ten-GigabitEthernet3/0/1] undo shutdown [Sysname-Ten-GigabitEthernet3/0/1] quit # Enable enhanced IRF mode. [Sysname] irf mode enhanced # Save the configuration. [Sysname] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file.
  • Page 59 [Sysname-Ten-GigabitEthernet3/0/2] undo shutdown [Sysname-Ten-GigabitEthernet3/0/2] quit # Enable enhanced IRF mode. [Sysname] irf mode enhanced # Save the configuration. [Sysname] save The current configuration will be written to the device. Are you sure? [Y/N]:y Please input the file name(*.cfg)[flash:/startup.cfg] (To leave the existing filename unchanged, press the enter key): flash:/startup.cfg exists, overwrite? [Y/N]:y Validating file.
  • Page 60 Configuration procedure Identify the master. <IRF> display irf MemberID Slot Role Priority CPU-Mac Description Master 00e0-fc0a-15e0 DeviceA Standby 00e0-fc0f-8c02 DeviceA 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 : yes...
  • Page 61 Now rebooting, please wait... Device A automatically reboots to complete the operating mode change. Log in to Device B and change its operating mode to standalone. <IRF> system-view [IRF] undo chassis convert mode The device will switch to stand-alone mode and reboot. You are recommended to save the current running configuration and specify the configuration file for the next startup.
  • Page 62 Index 6 4 H 6 5 H 6 6 H 6 7 H 6 8 H 6 9 H 7 0 H 7 1 H 7 2 H 7 3 H 7 4 H 7 5 H Accessing the IRF fabric, Hardware compatibility, 2 0 4 H 2 1 4 H...