H3C S5120-EI Series Operation Manual page 1148

the front panel is numbered 0, and subslots of the two expansion slots on the rear panel are
numbered 1 and 2 from left to right.
Interface serial number is dependent on the number of interfaces supported by the device. View
the silkscreen on the LPU for the number of supported interfaces.
For example, GigabitEthernet 1/0/1 is an interface on the independently operating device Sysname. To
set the link type of GigabitEthernet 1/0/1 to trunk, perform the following steps:
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] port link-type trunk
For a stack member, the interface name also adopts the previously introduced format: member ID/slot
number/interface serial number, where
The member ID identifies the stack member on which the interface resides
Meaning and value of the subslot number and the interface serial number are the same as those on
an independently operating device.
For example, GigabitEthernet 1/0/1 is an interface on stack member slave 3 (member ID is 3). To set the
link type of GigabitEthernet 1/0/1 to trunk, perform the following steps:
<Master> system-view
[Master] interface gigabitethernet 3/0/1
[Master-GigabitEthernet3/0/1] port link-type trunk
Configuration file management
1) Configuration file synchronization
IRF stack uses a strict configuration file synchronization mechanism to ensure that devices in a stack
can work as a single device on the network, and to ensure that after the master fails, the other devices
can operate normally.
When a slave starts up, it automatically finds out the master, synchronizes the master's
configuration file, and executes the configuration file; if all devices in a stack start up
simultaneously, the slaves synchronize the master's initial configuration file and execute it.
When the IRF stack operates normally, all your configurations will be recorded into the current
configuration file of the master, and are synchronized to each device in the stack; when you save
the current configuration file of the master as the initial configuration file by using the save
command, all slaves execute the same saving operation to make the initial configuration files of all
devices consistent.
Through the real-time synchronization, all devices in the stack keep the same configuration file. If the
master fails, all the other devices can execute various functions according to the same configuration
file.
2) Configuration file application
The configuration file can be divided into two parts: global configuration and port configuration. When a
slave applies these two kinds of configurations of the master, it deals with them in different ways:
Global configuration: All slaves execute the current global configuration on the master exactly, that
is, all members in the stack apply the same global configuration.
Port configuration: When a slave applies the port configuration on the master, it cares about the
configuration related to its own port, for example, the slave with the member ID of 3 only cares
about the configuration related to the GigabitEthernet 3/0/x port on the master. If there is a
1-9