5-16
z
The application files are managed only on the access control engine.
z
On 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 Web files on the
switching engine.
Setting up an update environment
Set up a software update environment and specify the working path of the server. For details, refer to
section Setting up an update environment on page 5-13.
z
For operations on the access control engine, the data needs to be transferred from the switching
engine to the access control engine; therefore, 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 device 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, you need to change to CLI of the switching engine by using
the
oap
command). Verify the connection by using the
ping
command.
z
For operations on the switching engine, you need to log in to the switching engine using the
oap
command, configure the IP addresses as mentioned above, and verify the connection by using the
ping
command.
The IP addresses of the access control engine and switching engine are both configured in VLAN
interface view.
Backing up and restoring application and configuration files
After setting up the environment, do the following on the terminal:
Use the
dir
command to check what files are in the file system:
<System>dir
Directory of flash:/
0 -rw- 855 Jul 26 2007 08:22:56 startup.cfg
1 -rw- 19189956 Jul 28 2035 10:35:38 main.bin
60884 KB total (41991 KB free)
<System>
For example, to copy the file
startup.cfg
on the device and save it as
config.bak
on the TFTP server,
use the following command:
