H3C WX3024E, Руководство по установке, Страница: 66 / 76

16
CAUTION:
• If you specify a filename that already exists in the Flash memory, the system prompts
The file is exist,will you overwrite it? [Y/N] If you select Y , the existing file will be overwritten.
• Make sure that sufficient space is available in the Flash memory. In case of insufficient
space, the upgrade cannot proceed and the system will give an error prompt.
• The new system software image file replaces the existing file of the same type, if any,
and becomes the only system software image file of that type. In this example,
wx3000.bin replaces the system software image file with the attribute of M and
becomes the only main system software image file.
•
For more information about the file types, see “ Files managed by the switch .”
Upgrading and backing up a system software image file by
using TFTP at the CLI
The access control engine and the switching engine have separate file systems. You need to log in to the
CLI of a specific system before you can do file operations in it.
After the switch starts, you are directly logged in to the access control engine system. To enter the
switching engine system, use the oap connect slot 0 command; to log out, press Ctrl + K .
NOTE:
•
A system software image file is managed only on the access control engine.
•
At the CLI of the access control engine, you can change to the CLI for the switching
engine through the
oap command and perform operations on the configuration files
and other files on the switching engine.
Setting up an upgrade environment
Set up a software upgrade environment and specify the working path of the server. For more information,
see “ Setting up an upgrade environment .”
•
For operations on the access control engine, the data needs to be transferred from the switching
engine to the access control engine, so you need to configure the IP addresses of the switching
engine, access control engine and the PC to be in the same network segment. For example,
configure the IP address of the TFTP server as 192.168.0.1, that of the access control engine of the
switch as 192.168.0.2, and that of the switching engine as 192.168.0.3 (to configure the IP address
of the switching engine, change to the CLI of the switching engine by using the oap command).
Verify the connection by using the ping command.
•
For operations on the switching engine, log in to the switching engine by using the oap command,
configure the IP addresses as mentioned above, and verify the connection by using the ping
command.
NOTE:
The IP addresses of the access control engine and switching engine are both configured in
VLAN interface view.