H3C S5120-EI Series Operation Manual page 1150

Or:
<Master> cd slot3#flash:/
<Master> mkdir test
%Created dir slot3#flash:/test.
3) To copy the test.app file on the master to the root directory of the flash on stack 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.app slot3#flash:/
Copy flash:/test.app to slot3#flash:/test.app?[Y/N]:y
%Copy file flash:/test.app to slot3#flash:/test.app...Done.
Stack Maintenance
In an IRF stack, direct neighbors exchange hello packets periodically (the period is 200 ms). Without
receiving any hello packet from a direct neighbor for ten periods, a member considers that the hello
packets timed out, and the stack isolates the expired device in the topology and updates its topology
database.
When a stack port of a member becomes down, the member broadcasts the information to all the other
members immediately. If the stack port of the master is down, an election is triggered.
IRF Stack Configuration Task List
Before configuring an IRF stack, you need to define the roles and functions of all the members for better
planning. Because the configuration of some parameters takes effect after device reboot, you are
recommended to first configure parameters, power off the devices, connect devices physically, power
on the devices, and finally the devices will join in the stack automatically. After an IRF stack is formed,
you can configure and manage the stack by logging in to any device in the stack. The operations you
make take effect on the master, and will be applied to the member devices in the stack. For easy fault
location and device maintenance, the S5120-EI switch provides slave view, where you can execute the
display, terminal, and debug commands.
1-11