HP 4800G Series Configuration Manual page 1948

3) To copy the test.bin file on the master to the root directory of the flash on IRF member slave 3,
perform the following steps:
<Master> pwd
slot3#flash:
//The above information indicates that the current working path is the root directory of the flash on slave
3.
<Master> cd flash:/
<Master> pwd
flash:
// The above operations indicate that the current working path is the root directory of the flash on the
master.
<Master> copy test.bin slot3#flash:/
Copy flash:/test.bin to slot3#flash:/test.bin?[Y/N]:y
%Copy file flash:/test.bin to slot3#flash:/test.bin...Done.
Configuration file management
1) Configuration file synchronization
IRF uses a strict configuration file synchronization mechanism to ensure that devices in an IRF 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 an IRF start up simultaneously,
the slaves synchronize the master's initial configuration file and execute it.
When the IRF operates normally, all your configurations will be recorded into the current
configuration file of the master, and are synchronized to each device in the IRF; 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 IRF 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 IRF 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
configuration related to its own port, it will apply the configuration; if not, no matter what
configuration has been made to the port before the slave joins the IRF, the slave will function using
null-configuration.
1-11