Figure 5 IRF merge
Member priority determines the possibility of a member device to be elected the master. A member with
higher priority is more likely to be elected the master.
IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all devices obtain
and run the running configuration of the master. Any configuration change is automatically propagated
from the master to the remaining devices. The configuration files of these devices are retained, but the
files do not take effect. The devices use their own startup configuration files only after they are removed
from the IRF fabric.
For more information about configuration management, see Fundamentals Configuration Guide.
Master election occurs each time the IRF fabric topology changes in the following situations:
The IRF fabric is established.
The master device fails or is removed.
The IRF fabric splits.
Independent IRF fabrics merge.
Master election does not occur when two split IRF fabrics merge.
Master election selects a master in descending order:
Current master, even if a new member has higher priority.
When an IRF fabric is being formed, all member devices consider themselves as the master. This
rule is skipped.
Member with higher priority.
Member with the longest system uptime.
Two members are considered to start up at the same time if their startup time difference is equal to
or less than 10 minutes. For these members, the next tiebreaker applies.
Member with the lowest member ID.