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 H3C S5830V2 & S5820V2 documentation set includes 10 configuration guides, which describe the software features for the H3C S5830V2 & S5820V2 Switch Series 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
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. About the H3C S5830V2 & S5820V2 documentation set The H3C S5830V2&S5820V2 documentation set includes:...
Page 5
Command references commands. 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] –...
This book describes IRF concepts and guides you through the IRF setup procedure. Hardware compatibility You can establish an IRF fabric that only comprises H3C S5820V2 series switches or S5830V2 series switches, or establish a heterogeneous IRF fabric that comprises both H3C S5820V2 and S5830V2 switches.
Figure 1 IRF application scenario 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 devices form an IRF fabric, they elect a master to manage and control the IRF fabric, and all the other devices back up the master.
To use an IRF port, you must bind at least one physical port to it. The physical ports assigned to an IRF port automatically form an aggregate IRF link. An IRF port goes down only if all its physical IRF ports are down.
IRF split IRF split occurs when an IRF fabric breaks up into two or more IRF fabrics because of IRF link failures, as shown in Figure 3. The split IRF fabrics operate with the same IP address and cause routing and forwarding problems on the network.
[Sysname-Ten-GigabitEthernet1/0/1] port link-type trunk For another example, on the IRF fabric Master, Ten-GigabitEthernet 3/0/1 represents the first fixed port on member device 3. Set its link type to trunk, as follows: <Master> system-view [Master] interface ten-gigabitethernet 3/0/1 [Master-Ten-GigabitEthernet3/0/1] port link-type trunk File system naming conventions On a standalone device, you can use its storage device name to access its file system.
# Display the current working path. In this example, the current working path is the root directory of the Flash on member device 3. <Master> pwd slot3#flash: # Change the current working path to the root directory of the Flash on the master device: <Master>...
Figure 5. 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.
with the mad exclude interface command. The IRF fabric with lower active ID is still in Active state and forwards traffic. Figure 5 LACP MAD application scenario Customer premise network Device LACP-enabled dynamic link aggregation LACP-enabled dynamic link aggregation IRF link Subordinate Master Internet...
Figure 6 ARP MAD application scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) IRF link Subordinate Master Internet Common traffic path Extended ARP traffic path Each IRF member compares the domain ID and the active ID in incoming extended ARP packets with its domain ID and active ID: •...
Page 17
Figure 7 ND MAD application scenario Customer premise network STP domain (all devices must run the spanning Device tree feature) IRF link Subordinate Master Internet Common traffic path Extended ND traffic path Each IRF member device compares the domain ID and the active ID in incoming NS packets with its domain ID and active ID: •...
All IRF member switches must run the same software image version. IRF physical port restrictions and binding requirements All SFP+ and QSFP+ ports on the H3C S5820V2 switches and all SFP+ ports on the H3C S5830V2 switches can be used as IRF physical ports.
After the IRF fabric is set up, you can access the IRF fabric to manage its member devices as if they were one device. Figure 8 Basic IRF setup flow chart H3C recommends the following IRF fabric setup and configuration procedure: Task Remarks Planning the IRF fabric setup Required.
CAUTION: In an IRF fabric, changing IRF member IDs might cause undesirable configuration changes and even data loss. Before you do that, back up the configuration and make sure you fully understand the impact on your network. For example, all member switches in an IRF fabric are the same model. If you swapped the IDs of any two members, their interface settings would also be swapped.
Connecting physical IRF ports When you connect two neighboring IRF members, connect the physical ports of IRF-port 1 on one member to the physical ports of IRF-port 2 on the other, as shown in Figure IMPORTANT: No intermediate devices are allowed between neighboring members. Figure 9 Connecting IRF physical ports Connect the devices into a daisy chain topology or more reliably, a ring topology (see Figure...
Page 23
To bind physical ports to IRF ports: Step Command Remarks Enter system view. system-view • Enter interface range view: Approach 1: interface range { interface-type To shut down a range of physical interface-number [ to IRF ports, enter interface range interface-type view.
Step Command Remarks Activating IRF port configurations can cause IRF merge and reboot. To avoid Save the configuration. save data loss, save the running configuration to the startup configuration file before you perform the operation. After this step is performed, the state of the IRF port changes to UP, the member devices automatically elect a master,...
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 IP addresses, MAC addresses, and any combination of them.
Configuring IRF bridge MAC persistence An IRF fabric by default uses the bridge MAC address of the master device 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.
Enabling software auto-update for software image synchronization The software auto-update function automatically synchronizes the current software images of the master in an IRF fabric to all its members. To join an IRF fabric, a device must use the same set of software images as the master in the fabric. When you add a device to the IRF fabric, the software auto-update function compares the startup software images of the joining device with the current software images of the IRF master.
• Detection speed is fast. Requires an intermediate downstream device. LACP MAD • H3C switch that supports Requires no MAD-dedicated For information about extended LACP. physical ports or interfaces. LACP, see Layer 2—LAN Switching Configuration Guide.
The intermediate device must be an H3C device that supports extended LACP for MAD. • • If the intermediate device is in an IRF fabric, assign this fabric a different domain ID than the LACP MAD-enabled fabric to avoid false detection of IRF partition.
If an intermediate device is used, you can use common data links as ARP MAD links. If no • intermediate device is used, set up dedicated ARP MAD links between IRF member devices. Use a VLAN dedicated to ARP MAD. •...
If the intermediate device is in an IRF fabric, assign this fabric a different domain ID than the ND • MAD-enabled fabric to avoid false detection of IRF partition. If an intermediate device is used, you can use common data links as ND MAD links. If no •...
Exclude a port from the shutdown action, so you can telnet to the port for managing the device. • • Exclude a VLAN interface and its Layer 2 ports from the shutdown action, so you can log in through the VLAN interface. 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...
Figure 12 Recovering the IRF fabric when both IRF link and Active-state fabric failures occur To manually recover the 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.
Set up an IRF fabric as shown in Figure 13. Configure LACP MAD in the IRF fabric, because the IRF fabric has a multichassis aggregate link to Device E, an H3C device that supports extended LACP. Figure 13 Network diagram Device E...
Page 35
[Sysname] interface range name irf interface ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] quit # Bind Ten-GigabitEthernet 1/0/45 and Ten-GigabitEthernet 1/0/46 to IRF port 1/1. [Sysname] irf-port 1/1 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/45 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/46 [Sysname-irf-port1/1] quit # Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF port 1/2.
Page 36
# Bring up the IRF physical ports and save the configuration. [Sysname] interface range name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] quit [Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master.
Page 37
[Sysname] irf member 1 renumber 4 Renumbering the member ID may result in configuration change or loss. Continue? [Y/N]:y [Sysname] quit <Sysname> reboot # Choose a set of SFP+ ports (Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 in this example) as IRF physical ports, connect them to Device B and Device C as shown in Figure 13, and log in to Device D.
[Sysname] interface range ten-gigabitethernet 1/0/2 ten-gigabitethernet 2/0/1 ten-gigabitethernet 3/0/2 ten-gigabitethernet 4/0/1 [Sysname-if-range] port link-aggregation group 2 [Sysname-if-range] quit Configure Device E as the intermediate device: CAUTION: If the intermediate device is in an IRF fabric, assign this fabric a different domain ID than the LACP MAD-enabled fabric.
Page 39
Figure 14 Network diagram Configuration procedure Configure Device A: # Choose a set of SFP+ ports as IRF physical ports, and shut down these ports (Ten-GigabitEthernet 1/0/45 to Ten-GigabitEthernet 1/0/48 in this example). <Sysname> system-view [Sysname] interface range name irf interface ten-gigabitethernet 1/0/45 to ten-gigabitethernet 1/0/48 [Sysname-if-range-irf] shutdown [Sysname-if-range-irf] quit...
Page 40
[Sysname] save # Activate the IRF port configuration. [Sysname] irf-port-configuration active Configure Device B: # Change the member ID of Device B to 2 and reboot the device to validate the change. <Sysname> system-view [Sysname] irf member 1 renumber 2 Renumbering the member ID may result in configuration change or loss.
Page 41
# Choose a set of SFP+ ports (Ten-GigabitEthernet 3/0/45 to Ten-GigabitEthernet 3/0/48 in this example) as IRF physical ports, connect Ten-GigabitEthernet 3/0/45 and Ten-GigabitEthernet 3/0/46 to Device A as shown in Figure 14, and log in to Device C. (Details not shown.) # Shut down the IRF physical ports.
Page 42
[Sysname-irf-port4/1] port group interface ten-gigabitethernet 4/0/46 [Sysname-irf-port4/1] quit # Bind Ten-GigabitEthernet 4/0/47 and Ten-GigabitEthernet 4/0/48 to IRF port 4/2. [Sysname] irf-port 4/2 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/47 [Sysname-irf-port4/2] port group interface ten-gigabitethernet 4/0/48 [Sysname-irf-port4/2] quit # Bring up the IRF physical ports and save the configuration. [Sysname] interface range name irf [Sysname-if-range-irf] undo shutdown [Sysname-if-range-irf] quit...
# Create VLAN 3, and add Ten-GigabitEthernet 1/0/1 to Ten-GigabitEthernet 1/0/4 to VLAN 3 to forward ARP MAD packets. [DeviceC] vlan 3 [DeviceC-vlan3] port gigabitethernet 1/0/1 gigabitethernet 1/0/2 [DeviceC-vlan3] quit ND MAD-enabled IRF configuration example Network requirements Set up an IRF fabric in the IPv6 network in Figure 15.
Page 44
[Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/45 [Sysname-irf-port1/1] port group interface ten-gigabitethernet 1/0/46 [Sysname-irf-port1/1] quit # Bind Ten-GigabitEthernet 1/0/47 and Ten-GigabitEthernet 1/0/48 to IRF port 1/2. [Sysname] irf-port 1/2 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/47 [Sysname-irf-port1/2] port group interface ten-gigabitethernet 1/0/48 [Sysname-irf-port1/2] quit # Bring up the IRF physical ports and save the configuration.
Page 45
# Activate the IRF port configuration. [Sysname] irf-port-configuration active The two devices perform master election, and the one that has lost the election reboots to form an IRF fabric with the master. In this example, Device B reboots. Configure Device C: # Change the member ID of Device C to 3 and reboot the device to validate the change.
Page 46
# Choose a set of SFP+ ports (Ten-GigabitEthernet 4/0/45 to Ten-GigabitEthernet 4/0/48 in this example) as IRF physical ports, connect them to Device B and Device C as shown in Figure 14, and log in to Device D. (Details not shown.) # Shut down the IRF physical ports.
Page 47
The assigned domain ID is: 1 Configure Device E as the intermediate device: CAUTION: If the intermediate device is in an IRF fabric, you must assign this fabric a different domain ID than the ND MAD-enabled fabric. # Enable the spanning tree feature globally on Device E to prevent loops. <DeviceC>...
Index A B C D E F G H I M P R S File system naming conventions,5 Accessing the IRF fabric,17 Application scenario,1 General restrictions and configuration guidelines,1 1 Assigning a member ID to each IRF member device,13 Hardware compatibility,1 Basic concepts,2...
Need help?
Do you have a question about the S5830V2 Series and is the answer not in the manual?
Questions and answers