H3C Technologies H3C SecPath F5020 - Manual (Page 13)

4
Multichassis link aggregation
You can use the Ethernet link aggregation feature to aggregate the physical links between an upstream
or downstream device and multiple devices in the IRF fabric.
Configuration synchronization
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 member devices. The configuration files of the subordinate 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.
Basic concepts
Operating mode
This concept only applies to distributed devices.
The device operates in one of the following modes:
• Standalone mode—The device cannot form an IRF fabric with other devices.
• IRF mode—The device can form an IRF fabric with other devices.
IRF member roles
IRF uses two member roles: master and standby (called subordinate throughout the documentation).
When devices form an IRF fabric, they elect a master to manage and control the IRF fabric, and all the
other devices back up the master. When the master device fails, the other devices elect a new master
automatically. For more information about master election, see " Master election ."
IRF member ID
An IRF fabric uses member IDs to uniquely identify and manage its members. This member ID information
is included as the first part of interface numbers and file paths to uniquely identify interfaces and files in
an IRF fabric. Two devices cannot form an IRF fabric if they use the same member ID. A device cannot join
an IRF fabric if its member ID has been used in the fabric.
For example, after you assign member ID 2 to a centralized IRF device, the name of the interface
GigabitEthernet 1/0/1 changes to GigabitEthernet 2/0/1. The file path of flash:/test.cfg changes to
slot2#flash:/test.cfg.
For example:
• After you assign member ID 2 to a centralized IRF device, the name of the interface GigabitEthernet
1/0/1 changes to GigabitEthernet 2/0/1. The file path changes from flash:/test.cfg to
slot2#flash:/test.cfg.