Multi-active handling procedure, Detection – H3C Technologies H3C SecPath F5020 User Manual
Page 17
8
1.
Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all members consider themselves as the master. This rule is
skipped.
2.
Member with higher priority.
3.
Member with the longest system uptime.
Two members are considered to start up at the same time if the difference between their startup
times is equal to or less than 10 minutes. For these members, the next tiebreaker applies.
4.
Member with the lowest CPU MAC address.
For the setup of a new IRF fabric, the subordinate devices must reboot to complete the setup after the
master election.
For an IRF merge, devices must reboot if they are in the IRF fabric that fails the master election.
The reboot is automatically performed if the auto-merge feature is enabled. You must perform the reboot
manually if the auto-merge feature is disabled or the device does not support the feature.
Multi-active handling procedure
The multi-active handling procedure includes detection, collision handling, and failure recovery.
Detection
For centralized IRF devices, IRF provides a MAD mechanism by extending BFD.
For distributed devices, IRF provides MAD mechanisms by extending BFD, ARP, and IPv6 ND.
For more information about the MAD mechanisms and their application scenarios, see "
An IRF fabric uses BFD MAD to detect multi-active collisions.
BFD MAD can work with or without intermediate devices. Intermediate device, if used, can come from
any vendor.
•
If no intermediate device is used, the IRF members must be fully meshed. This mechanism is only
suitable for IRF fabrics that have members geographically close to one another.
•
If an intermediate device is used, every IRF member must connect to the intermediate device.
shows a typical BFD MAD application scenario.