Table of Contents
Advertisement
# Copy the file to member device 3.
<Master> copy test.ipe slot3#flash:/
Copy flash:/test.ipe to slot3#flash:/test.ipe?[Y/N]:y
Copying file flash:/test.ipe to slot3#flash:/test.ipe... Done.
For more information about storage device naming conventions, see Fundamentals Configuration
Guide.
Configuration synchronization
IRF uses a strict running-configuration synchronization mechanism. In an IRF fabric, all member
devices get and run the running configuration of the master. Any configuration change is
automatically propagated from the master to the other member devices. The configuration files of
these devices are still retained, but these 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
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.
NOTE:
Master election does not occur when two split IRF fabrics merge.
Master election selects a master in descending order:
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. If all members have the same priority, this rule is skipped.
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.
Multi-active handling procedure
The multi-active handling procedure includes detection, collision handling, and failure recovery.
Detection
MAD identifies each IRF fabric with a domain ID and an active ID (the member ID of the master). If
multiple active IDs are detected in a domain, MAD determines that an IRF collision or split has
occurred.
6
Advertisement
Table of Contents
