![H3C S5820 series Configuration Manual Download Page 19](http://html1.mh-extra.com/html/h3c/s5820-series/s5820-series_configuration-manual_4186693019.webp)
1-12
easy fault location and device maintenance, the S5820X series or S5800 series provides slave view,
where you can execute the
display
,
terminal
, and
debug
commands.
Complete the following tasks to configure an IRF virtual device:
Task
Remarks
Specifying a Domain ID for an IRF Virtual Device
Optional
Setting a Member ID for a Device
Optional
Configuring IRF Ports
Required
Specifying a Priority for a Member
Required
Specifying the Preservation Time of the Bridge MAC
Address
Optional
Enabling Auto Upgrade of Boot Files
Optional
IRF Virtual Device
Configuration
Setting the Delay Time for the Link Layer to Report a
Link-Down Event
Optional
Connect the physical IRF ports of devices by using SFP+ cables or optical fibers (a ring connection is
recommended), and then power on the devices.
Configuring LACP MAD
Optional
Configuring BFD MAD
Optional
Excluding a Port from the Shut Down Action upon
Detection of Multi-Active Collision
Optional
Configuring MAD Detection
Manually Recovering an IRF Virtual Device
Optional
Logging In to the Master
Required
Logging In to an IRF Virtual
Device
Logging In to a Slave
Optional
To avoid influence to your network caused by accidental partition of an IRF virtual device, you are
recommended to enable the MAD detection function after establishing the IRF virtual device.
IRF Virtual Device Configuration
Specifying a Domain ID for an IRF Virtual Device
Introduction to domain
To differentiate IRF virtual devices, each IRF virtual device is assigned a domain ID.
As shown in
Figure 1-8
, Switch A and Switch B form IRF virtual device 1, and Switch C and Switch D
form IRF virtual device 2. If there is an LACP MAD detection link between IRF virtual device 1 and IRF
virtual device 2, they send MAD detection packets to each other through the detection link. In this case,
the system statuses and operations of both IRF virtual device 1 and IRF virtual device 2 are affected. To
solve this problem, specify different domain IDs for the two IRF virtual devices.