H3C Technologies H3C S7500E Series Switches - Manual (Page 31)

1-24
Figure 1-10 Network diagram for an IRF virtual device that uses BFD MAD detection
XGE1/3/0/25
(IRF-port1/2) XGE2/3/0/25
(IRF-port2/1)
GE1/3/0/1 GE2/3/0/1
Device A Device B
IRF virtual
device
Note: The solid orange line represents the IRF link; the solid magenta line represents
link used for BFD MAD detection; the solid black lines represent Ethernet links.
IP network
Configuration considerations
z To increase the number of access ports, additional devices are needed. In this example, Device B
is added.
z To address the requirements for high availability, ease of management and maintenance, use IRF2
technology to create an IRF with Device A and Device B at the access layer.
z To offset the risk of IRF virtual device partition, configure MAD to detect multi-active collisions. In
this example, BFD MAD is adopted because the downlinks of devices are PCs instead of
aggregated networking.
z To make sure that Device A is elected as the master of the IRF virtual device, specify priorities for
member devices.
z When IRF links fail, first repair IRF links and then reboot the device in the recovery state to make it
re-join the IRF virtual device.
Configuration procedure
1) Device A and Device B are not connected. Power them on and configure them separately.
# Configure Device A.
system-view
[Sysname] chassis convert mode irf
This command will convert the device to IRF mode and the device will reboot. Are you sure?
[Y/N]: y
The device reboots automatically to switch its operating mode. After logging in to the device again,
create IRF-port1/2 of the device, bind it to the physical IRF port Ten-GigabitEthernet 1/3/0/25.
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