H3C S5120-EI Series Configuration Manual
Hide thumbs
Also See for S5120-EI Series:
- Operation manual (1191 pages) ,
- Command reference manual (242 pages) ,
- Configuration manual (206 pages)
Subscribe to Our Youtube Channel
Related Manuals for H3C S5120-EI Series
Summary of Contents for H3C S5120-EI Series
- Page 1 H3C S5120-EI Switch Series IRF Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Software version: Release 2220 Document version: 6W100-20130810...
- Page 2 Copyright © 2013, 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 The H3C S5120-EI documentation set includes 10 configuration guides, which describe the software features for the H3C S5120-EI Switch Series Release 2220, 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 Convention Description Square brackets enclose a set of optional syntax choices separated by vertical bars, from [ x | y | ... ] which you select one or none. Asterisk marked braces enclose a set of required syntax choices separated by vertical { x | y | ...
-
Page 5: Obtaining Documentation
Operations and Release notes compatibility matrix, version upgrade information, maintenance technical support information, and software upgrading. Obtaining documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. -
Page 6: Technical Support
– Provides information about products and technologies, as well as solutions. [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 Hardware compatibility ···················································································································································· 1 IRF benefits ········································································································································································· 1 Application scenario ························································································································································· 1 Basic concepts ··································································································································································· 2 IRF member roles ······················································································································································ 2 IRF member ID ··························································································································································· 2 IRF port ······································································································································································ 2 ... - Page 8 Configuring LACP MAD ········································································································································ 21 Configuring ARP MAD ·········································································································································· 22 Excluding a port from the shutdown action upon detection of multi-active collision ······································ 23 Recovering an IRF fabric ······································································································································· 24 Displaying and maintaining an IRF fabric ··················································································································· 25 ...
-
Page 9: Irf Overview
IRF overview The H3C Intelligent Resilient Framework (IRF) technology creates a large IRF fabric from multiple switches to provide data center class availability and scalability. IRF virtualization technology offers processing power, interaction, unified management, and uninterrupted maintenance of multiple switches. -
Page 10: Basic Concepts
Figure 1 IRF application scenario IP network IP network Subordinate Master Equal to IRF link Basic concepts This section describes the basic concepts that you might encounter when working with IRF. IRF member roles IRF uses two member roles: master and slave (called "subordinate" throughout the documentation). When switches form an IRF fabric, they elect a master to manage the IRF fabric, and all other switches back up the master. -
Page 11: Physical Irf Port
For two neighboring devices, their IRF physical links must be bound to IRF-port 1 on one device and to IRF-port 2 on the other. Physical IRF port Physical IRF ports connect IRF member devices and must be bound to an IRF port. They forward IRF protocol packets between IRF member devices and data packets that must travel across IRF member devices. -
Page 12: Irf Merge
forwarding problems on the network. To quickly detect a multi-active collision, configure at least one MAD mechanisms (see "IRF multi-active detection"). Figure 3 IRF split IRF merge IRF merge occurs when two split IRF fabrics reunite or when you configure and connect two independent IRF fabrics to be one IRF fabric, as shown in Figure Figure 4 IRF merge... -
Page 13: File System Naming Conventions
[Master] interface gigabitethernet 3/0/1 [Master-GigabitEthernet3/0/1] port link-type trunk File system naming conventions On a standalone switch, you can use the name of storage device to access its file system. For more information about storage device naming conventions, see Fundamentals Configuration Guide. On an IRF fabric, you can use the name of storage device to access the file system of the master. -
Page 14: Configuration Synchronization Mechanism
Configuration synchronization mechanism IRF uses a strict running-configuration synchronization mechanism so all chassis in an IRF fabric can work as a single node, and after the master fails, other members can operate normally. In an IRF fabric, all chassis get and run the running configuration of the master. Any configuration you have made is propagated to all members. -
Page 15: Lacp Mad
Figure 5. In addition, the intermediate device must be an H3C device that supports extended LACP for MAD. The IRF member switches 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... -
Page 16: Arp Mad
Figure 5 LACP MAD application scenario ARP MAD ARP MAD detects multi-active collisions by using extended gratuitous ARP packets that convey the IRF domain ID and the active ID. You can set up ARP MAD links between neighbor IRF member devices, or between each IRF member device and an intermediate device (see Figure 6). - Page 17 Figure 6 ARP MAD application scenario Each IRF member compares the domain ID and the active ID in incoming extended gratuitous ARP packets with its domain ID and active ID: • If the domain IDs are different, the extended gratuitous ARP packet is from a different IRF fabric, and the device does not continue to process the packet with the MAD mechanism.
-
Page 18: Configuring Irf
Modules Manual. The SFP+ modules and SFP+ cables available for the switch are subject to change over time. For the most up-to-date list of SFP+ modules and cables, consult your H3C sales representative or technical support engineer. IRF port binding restrictions Facing the rear panel, make sure the physical ports bound to IRF port 1 is on the left of the physical ports bound to IRF port 2. -
Page 19: Mad
• member devices. Setup and configuration task list H3C recommends the basic IRF setup procedure in Figure 7. Perform the tasks in this figure on each member switch. After the IRF fabric is set up, you can access the IRF fabric to manage its member switches as if they were one switch. -
Page 20: Planning The Irf Fabric Setup
H3C recommends the following IRF fabric setup and configuration procedure: Task Remarks Planning the IRF fabric setup Required. Required. Assigning a member ID to each IRF member switch Perform this task on each member switch. Required. Specifying a priority for each member switch Perform this task on each member switch. -
Page 21: Assigning A Member Id To Each Irf Member Switch
Hardware compatibility and restrictions • IRF fabric size • • Master switch IRF physical ports • Member ID and priority assignment scheme • Fabric topology and cabling scheme • For more information about hardware and cabling, see the switch installation guide. Assigning a member ID to each IRF member switch CAUTION: In an IRF fabric, changing IRF member IDs might cause undesirable configuration changes and even data... -
Page 22: Connecting Physical Irf Ports
A member priority change affects the election result at the next master election, but does not cause immediate master re-election. To specify a priority for the switch: Step Command Remarks Enter system view. system-view Specify a priority for the The default IRF member priority irf member member-id priority priority switch. -
Page 23: Binding Physical Ports To Irf Ports
Binding physical ports to IRF ports To establish an IRF connection between two devices, you must bind at least one physical port to IRF-port 1 on one device and to IRF-port 2 on the other. For link redundancy and load sharing, bind multiple physical ports to one IRF port. -
Page 24: Accessing The Irf Fabric
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 Ethernet interface view interface range name or interface range view. name [ interface { interface-type interface-number [ to interface-type interface-number ] }... -
Page 25: Accessing The Cli Of A Subordinate Switch
Remote login—Remotely log in at a Layer 3 interface on any member switch by using a methods • including Telnet, Web, and SNMP. For more information, see the chapter on login in Fundamentals Configuration Guide. Accessing the CLI of a subordinate switch You can log in to the CLI of a subordinate switch for maintenance or debugging. -
Page 26: Configuring Irf Link Load Sharing Mode
Step Command Remarks Enter system view. system-view Configure the description of By default, no member switch irf member member-id description text a member. description is configured. Configuring IRF link load sharing mode On an IRF port that has multiple links, traffic is balanced across its physical links. You can configure the IRF port to distribute traffic based on certain criteria, including source IP address, destination IP address, source MAC address, destination MAC address, or any combination of the criteria. -
Page 27: Configuring Irf Bridge Mac Persistence
Configuring IRF bridge MAC persistence An IRF fabric by default uses the bridge MAC address of the master switch as its bridge MAC address. This bridge MAC address is used by Layer 2 protocols, for example, LACP, to identify the IRF fabric, and must be unique on a switched LAN for proper communication. -
Page 28: Setting The Irf Link Down Report Delay
The software auto-update function automatically propagates the system software image of the master to all members in the IRF fabric. If software auto-update is disabled, you must manually update the switch with the system software image of the master. When you add a switch to the IRF fabric, the software auto-update function compares the system software versions of the switch and the IRF master. -
Page 29: Configuring Mad
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 30: Configuring Arp Mad
Use dynamic link aggregation mode. MAD is LACP dependent. Even though LACP MAD can be • configured on both static and dynamic aggregate interfaces, it takes effect only on dynamic aggregate interfaces. Configure link aggregation settings also on the intermediate device. •... -
Page 31: Excluding A Port From The Shutdown Action Upon Detection Of Multi-Active Collision
To configure ARP MAD: Step Command Remarks Enter system view. system-view Assign a domain ID to the IRF irf domain domain-id The default IRF domain ID is 0. fabric. Create a VLAN dedicated to The default VLAN on the device vlan vlan-id ARP MAD. -
Page 32: Recovering An Irf Fabric
CAUTION: Excluding a VLAN interface and its Layer 2 ports from the shutdown action introduces IP collision risks because the VLAN interface might be active on both the IRF fabric in Active state and the IRF fabric in Recovery state. By default, all ports except the console and physical IRF ports automatically shut down when the IRF fabric transits to the Recovery state. -
Page 33: Displaying And Maintaining An Irf Fabric
Figure 11 Active-state IRF fabric fails before the IRF link is recovered To manually recover an IRF fabric in Recovery state: Step Command Enter system view. system-view Change the state of the IRF fabric from mad restore Recovery to Active. After the IRF fabric is recovered, all ports that have been shut down by MAD automatically come up. -
Page 34: Configuration Examples
Set up a two-member IRF fabric at the access layer of the enterprise network in Figure 12. Configure LACP MAD in the IRF fabric, because the IRF fabric has a multi-chassis aggregate link to Device C, an H3C device that supports extended LACP. Figure 12 Network diagram... - Page 35 # Change the member ID of Device B to 2. <DeviceB> system-view [DeviceB] irf member 1 renumber 2 Warning: Renumbering the switch number may result in configuration change or loss. Continue? [Y/N]:y [DeviceB] Power off the devices, connect IRF links as shown in Figure 12, and power on the two devices.
-
Page 36: Arp Mad-Enabled Irf Configuration Example
[Current domain is: 0]: The assigned domain ID is: 0 Info: MAD LACP only enable on dynamic aggregation interface. # Assign ports GigabitEthernet 1/0/1 and GigabitEthernet 2/0/1 to the aggregate interface. [DeviceA] interface range gigabitethernet 1/0/1 gigabitethernet 2/0/1 [DeviceA-if-range] port link-aggregation group 2 [DeviceA-if-range] quit [DeviceA] interface gigabitethernet 2/0/1 [DeviceA-GigabitEthernet2/0/1] port link-aggregation group 2... -
Page 37: Configuration Procedure
Configuration procedure This example assumes that the system names of Device A, Device B and Device C are DeviceA, DeviceB, and DeviceC, respectively, before the IRF fabric is formed. Assign member IDs: # Keep the default member ID of Device A unchanged. # Change the member ID of Device B to 2. - Page 38 # Enable the spanning tree feature globally on the IRF fabric to prevent loops. <DeviceA> system-view [DeviceA] stp enable # Connect the ARP MAD links as shown in Figure # Configure the IRF fabric to change its bridge MAC address as soon as the master leaves. [DeviceA] undo irf mac-address persistent # Create VLAN 3, and add port GigabitEthernet 1/0/1 (on Device A) and port GigabitEthernet 2/0/1 (on Device B) to VLAN 3.
-
Page 39: Index
Index A B C D E F G H I M P S Accessing the IRF fabric,16 File system naming conventions,5 Application scenario,1 Assigning a member ID to each IRF member switch,13 General restrictions and configuration guidelines,10 Assigning an IRF domain ID to the IRF fabric,17 Hardware compatibility,1...
Need help?
Do you have a question about the S5120-EI Series and is the answer not in the manual?
Questions and answers