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.
Page 3
Preface The H3C S7500E documentation set includes 12 configuration guides, which describe the software features for the H3C S7500E Series Ethernet Switches 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
Symbols Convention Description Means reader be careful. Improper operation may cause data loss or damage to equipment. Means a complementary description. About the H3C S7500E Documentation Set The H3C S7500E documentation set includes: Category Documents Purposes Marketing brochures Describe product specifications and benefits.
Page 5
Power Module User installation and removal of the H3C PSR6000-ACV Manual power module. H3C PWR-SPA Power Describes the functions and appearance of the H3C Module Adapter User PWR-SPA power module adapter, and how to use it Manual with the PSR650 power module.
Page 6
Required software version Pluggable modules supported by the card 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 &...
At present, the S7500E Series Ethernet Switches support an IRF virtual device of two members, which means you can use two S7500E series switches to form an IRF virtual device: one operates as the master and the other operates as the slave.
devices can be aggregated, and thus the reliability of the IRF virtual device is increased through link redundancy. Powerful network expansion capability. By adding member devices, the number of IRF ports and network bandwidth of an IRF virtual device can be easily expanded. Each member device has its own CPU and they can process and forward protocol packets independently.
Basic Concepts Figure 1-2 IRF implementation schematic diagram As shown in Figure 1-2, Device A and Device B are physically connected. After you perform necessary configurations on them, they form an IRF virtual device, which has four switching and routing processing units (SRPUs) (one active SRPU and three standby SRPUs) and two interface cards.
Page 11
Physical IRF port Physical ports used for IRF connection on devices are called physical IRF ports. On the S7500E series, you can configure a 10 GE optical port as a physical IRF port. By default, a 10 GE optical port functions as a common service port and forwards data traffic. When bound with an IRF port, it acts as an IRF physical port and forwards packets among member devices.
IRF port or, to realize link backup, can bind to multiple physical IRF ports (known as aggregate IRF port). The S7500E series uses 10 GE optical ports as physical IRF ports. You can connect physical IRF ports with fibers. Fibers connect physical devices located very far from each other and provide flexible application.
Figure 1-5 Physical connections of IRF virtual device The orange line in the figure represents the IRF link, which is different from a common Ethernet link. An IRF link can be composed of either one physical cable or multiple physical links. Topology Collection Each member exchanges hello packets with the directly connected neighbors to collect topology of the IRF virtual device.
During the mergence, IRF election is held, and role election rules are followed. You need to manually reboot the members of the loser side, and then they join the winner side as slaves. IRF Virtual Device Management and Maintenance After role election, an IRF virtual device is established: all member devices operate as one virtual device, and all resources on the member devices are possessed by this virtual device and managed by the master.
Therefore, to make the IRF virtual device operate normally, you need to make sure that the link state is normal and connect the IRF ports of two devices correctly before configuring an IRF virtual device; after the establishment of the IRF virtual device, configure necessary anti-attack policies to ensure device safety.
For information about LACP, see Ethernet Link Aggregation Configuration in the Layer 2 - LAN Switching Configuration Guide; for information about BFD, see BFD Configuration in the High Availability Configuration Guide. When an IRF virtual device is partitioned, the system disables all service ports on the member device of the IRF virtual device that transits to recovery state (that is equal to executing the shutdown command on these ports).
Task Remarks Specifying the reserved ports Optional Failure recovery Optional Accessing the Master Required Accessing an IRF Virtual Device Accessing a Slave Optional After establishing an IRF virtual device, you are recommended to configure the MAD detection function to avoid the influences to the network caused by accidental partition of the IRF virtual device. Switching Operating Mode The device can operate in either IRF mode or standalone mode.
To do… Use the command… Remarks Enter system view system-view — Required Switch the operating mode of the chassis convert mode irf By default, the device operates device to IRF mode in standalone mode. The device automatically reboots as soon as you confirm the operation of switching the operating mode.
1. Configuring IRF Ports The S7500E series uses 10 GE optical ports, which are on the SRPU, or on SC, SD, or EB interface card, as physical IRF ports to perform IRF connection. For more information about LPUs providing 10 GE optical ports, see the related information in the H3C S7500E Series Ethernet Switches Installation Manual.
You can bind multiple physical IRF ports to one IRF port by executing the port group interface command for multiple times. In addition, the S7500E series allows you to bind multiple physical IRF ports on different LPUs to one IRF port.
Preserve for six minutes: After the master leaves, the bridge MAC address will not change within six minutes. If the master does not come back after six minutes, the IRF virtual device will use the bridge MAC address of the newly elected master as its bridge MAC address. Preserve permanently: No matter whether the master leaves the IRF virtual device or not, the bridge MAC address of the IRF virtual device remains unchanged.
To do… Use the command… Remarks Set the delay time for the link Optional layer to report a link-down event irf link-delay interval The default value is 200 ms. of an IRF virtual device Do not set the time interval to a very long time; otherwise, the IRF virtual device cannot be aware of the topology changes in time and thus services will be recovered slowly.
Page 23
Figure 1-6 Network diagram for BFD MAD detection Terminal network Device Aggregation group on Device, used for forwarding service packets IRF virtual device BFD MAD link Vlan2 Vlan2 192.168.1.2/24 192.168.1.3/24 IRF link Slave Master Internet Configuring BFD MAD detection Configure BFD MAD detection in the following order: Create a VLAN dedicated for BFD MAD detection;...
Page 24
To do… Use the command… Remarks the BFD MAD according to the port type. detection BFD MAD detection has no requirement on the link type of the detection port, and you do Hybrid port port hybrid vlan vlan-id not need to modify the current link type.
Page 25
Networking requirements LACP MAD requires intermediate H3C devices that are capable of identifying and processing extended LACPDUs to carry the Active ID field. For more information, see LACP protocol section in Ethernet Link Aggregation Configuration. The commonly used networking diagram is as shown in...
Page 26
Enable LACP MAD detection on the dynamic aggregate interface Add member ports to the aggregation group.(also required on the intermediate device) Follow these steps to enable LACP MAD detection: To do… Use the command… Remarks Enter system view system-view — Required Enter Layer 2 aggregation port interface bridge-aggregation...
Page 27
To do… Use the command… Remarks Required Specify the reserved ports, that is, By default, no reserved port is the ports that will not be disabled mad exclude interface interface-type specified, that is, all service ports when the device is in the recovery interface-number will be disabled automatically state...
Page 28
As shown in Figure 1-9, if the IRF virtual device in active state fails due to exceptions (a member fails or link failure occurs, for example) before the IRF link is recovered, enable IRF virtual device 2 (in the recovery state) to change the state of IRF virtual device 2 from recovery to active, and repair the IRF links.
Accessing an IRF Virtual Device Accessing the Master After an IRF virtual device is formed, you can access the console of the IRF virtual device from the AUX or console port of any member device. Create a Layer 3 Ethernet interface, and configure an IP address for it, and make sure that the interface and the user terminal are routable to each other.
An IRF virtual device allows at most nine users to log in at the same time. The permitted login users include five users logged in through virtual type terminal (VTY) and four users logged in through the console port. Displaying and Maintaining an IRF Virtual Device To do…...
Page 31
Figure 1-10 Network diagram for an IRF virtual device that uses BFD MAD detection IP network GE2/3/0/1 GE1/3/0/1 XGE1/3/0/25 XGE2/3/0/25 IRF virtual Device A Device B (IRF-port1/2) (IRF-port2/1) device Note: The solid orange line represents the IRF link; the solid magenta line represents link used for BFD MAD detection;...
Page 32
[Sysname-Ten-GigabitEthernet1/3/0/25] undo shutdown # Specify the priority of Device A as 10 to make sure that it is elected as the master when the IRF virtual device is established, and save the configuration. [Sysname-Ten-GigabitEthernet1/3/0/25] quit [Sysname] irf member 1 priority 10 [Sysname] save # Configure Device B.
Reboot device by command. %May 6 15:31:09:734 2010 H3C DEVM/5/SYSTEM_REBOOT: System is rebooting now. # After device reboot, Device B re-joins the IRF virtual device. You can use the display irf command to view the topology information about the IRF virtual device.
Page 34
Figure 1-11 Network diagram for an IRF virtual device that uses LACP MAD detection IRF virtual device Device A Device B XGE1/3/0/25 XGE2/3/0/25 IRF link (IRF-port1/2) (IRF-port2/1) GE2/3/0/2 GE1/3/0/2 GE3/0/1 GE3/0/2 Note: The solid orange line represents for IRF link; the solid magenta lines represent links used for LACP MAD detection;...
Page 35
<Sysname> system-view [Sysname] interface ten-gigabitethernet 1/3/0/25 [Sysname-Ten-GigabitEthernet1/3/0/25] shutdown [Sysname-Ten-GigabitEthernet1/3/0/25] quit [Sysname] irf-port 1/2 [Sysname-irf-port 1/2] port group interface ten-gigabitethernet 1/3/0/25 [Sysname-irf-port 1/2] quit [Sysname] interface ten-gigabitethernet 1/3/0/25 [Sysname-Ten-GigabitEthernet1/3/0/25] undo shutdown [Sysname-Ten-GigabitEthernet1/3/0/25] save # Configure Device B. <Sysname> system-view [Sysname] chassis convert mode irf This command will convert the device to IRF mode and the device will reboot.
Page 36
Trap 1.3.6.1.6.3.1.1.5.4<linkUp>: Interface 277872640 ifAdminStatus ifOperStatus is 1 %May 7 09:23:16:069 2010 H3C IFNET/3/LINK_UPDOWN: GigabitEthernet2/3/0/2 link status is UP. #May 7 09:23:16:302 2010 H3C LAGG/1/AggPortRecoverActive: Trap 1.3.6.1.4.1.2011.5.25.25.2.4<hwAggPortActiveNotification>: Aggregation Group 1: port member 277872640 becomes ACTIVE! %May 7 09:23:16:322 2010 H3C LAGG/5/LAGG_ACTIVE: Member port GigabitEthernet2/3/0/1 of aggregation group BAGG1 becomes ACTIVE.
Page 37
IRF port 2 is up. #May 7 09:30:36:566 2010 H3C DEVM/1/BOARD INSERTED: # Execute the display irf command. You can see that the IRF virtual device is recovered, Device B is the master and Device A is the salve. <Sysname> display irf...
Index Accessing a Slave 1-22 Accessing the Master 1-22 Advantages Application Configuration Example of Using the BFD MAD Detection 1-23 Configuration Example of Using the LACP MAD Detection 1-26 Configuring IRF Ports 1-12 Configuring MAD Detection 1-15 IRF Multi-Active Detection Mechanism IRF Virtual Device Management and Maintenance Overview...