Master Election; Irf Fabric Management And Maintenance - H3C S9500E Series Configuration Manual

After all member switches have obtained topology information (known as topology convergence), the
IRF fabric enters the role election stage.

Master election

Master election is held each time the topology changes, for example, when the IRF fabric is established,
a new member switch is plugged in, the master switch fails or is removed, or the partitioned IRF fabrics
merge.
The master is elected based on the following rules in descending order:
• The current master, even if a new member has a higher priority. (When an IRF fabric is being
formed, all member switches consider themselves as the master, and this rule is skipped)
The switch with a higher priority.
•
The switch with the longest system up-time. (The member switches exchange system up-time in the
•
IRF hello packets)
The switch with the lowest bridge MAC address.
•
The IRF fabric is formed on election of the master.
NOTE:
During an IRF merge, an IRF election is held, the switches of the IRF fabric that fails the master election
•
must reboot to re-join the IRF fabric that wins the election. Then, the switch reboots with the execution of
a command.
After a master election, all slave member switches initialize and reboot with the configuration on the
•
master, and their original configuration, even if has been saved, will be lost.

IRF fabric management and maintenance

After the IRF fabric is established, you can access the master from any member switch to manage all the
resources of the member switches.
Member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. For example, if an interface
on a switch that operates in standalone mode is named GigabitEthernet 3/0/1. After the switch joins an
IRF fabric, it receives a member ID of 2. The name of the interface changes to GigabitEthernet 2/3/0/1.
Member ID is also used in file management. For example, when the switch operates in standalone mode,
the path of a file was slot1#flash:/test.cfg. After the switch joins an IRF fabric, the path changes to
chassis1#slot1#flash:/test.cfg, which indicates that the file is saved on the board in slot 1 of member
switch 1. Therefore, member IDs must be unique.
NOTE:
Member IDs and priorities are configured per switch. If you set the member ID or priority for a member
switch, the configuration is first saved on the active MPU of the member switch, and then synchronized to
the standby MPU. If the active MPU and standby MPU of a member switch keep different member IDs, the
member ID kept by the active MPU is applied. For example, if the switch with the member ID of 2 has only
one active MPU, after you plug in a standby MPU that keeps a member ID of 1, the member ID of the
switch is still 2 and the member ID kept on the standby MPU is synchronized to 2.
7