Throughout this
document, a filename can be entered as either of the following:
l
A fully qualified filename with the path
included to indicate a file under a specific path. The filename can be 1 to 135
characters in length.
l
A short filename with the path excluded to
indicate a file in the current path. The filename can be 1 to 91 characters in
length.
When configuring the file system, go to
these sections for information you are interested in:
l
File System Management
l
Configuration File Management
1.1 File System Management
This section covers these topics:
l
Overview
l
Directory Operations
l
File Operations
l
Storage Device Operations
l
File System Prompt Mode Setting
l
File System Operations Example
1.1.1 Overview
A major function of the file system is to
manage storage devices. It allows you to perform operations such as directory
create and delete, and file copy and display. If an operation, delete or
overwrite for example, may cause problems such as data loss or corruption, the
file system will ask you to confirm the operation by default.
Depending on the managed object, file
system operations fall into directory operations, file operations, storage
device operations, and file system prompt mode setting.
1.1.2 Directory Operations
Directory operations include create,
delete, display the current directory, display files or subdirectories in a
specific directory as shown in the following table:
|
To do…
|
Use the command…
|
Remarks
|
|
Create a directory
|
mkdir directory
|
Optional
Available in user view
|
|
Remove a directory
|
rmdir directory
|
Optional
Available in user view
|
|
Display the current directory
|
pwd
|
Optional
Available in user view
|
|
Display files or directories
|
dir [ /all
] [ file-url ]
|
Optional
Available in user view
|
|
Change the current path
|
cd directory
|
Optional
Available in user view
|
1.1.3 File Operations
File operations include delete (removing files
into the recycle bin), restore the deleted, permanently delete (deleting files from
the recycle bin), display, rename, copy, and move as shown in the following
table:
|
To do…
|
Use the command…
|
Remarks
|
|
Remove a file to the recycle bin or
delete it permanently
|
delete [ /unreserved
] file-url
|
Optional
Available in user view
|
|
Restore a file from the recycle bin
|
undelete file-url
|
Optional
Available in user view
|
|
Empty the recycle bin
|
reset recycle-bin [ file-url ] [ /force ]
|
Optional
Available in user view
|
|
Display the contents of a file
|
more file-url
|
Optional
Available in user view
Currently, the file is displayed only in
the format of text.
|
|
Rename a file
|
rename fileurl-source fileurl-dest
|
Optional
Available in user view
|
|
Copy a file
|
copy fileurl-source
fileurl-dest
|
Optional
Available in user view
|
|
Move a file
|
move fileurl-source
fileurl-dest
|
Optional
Available in user view
|
|
Display files or directories
|
dir [ /all
] [ file-url ]
|
Optional
Available in user view
|
|
Enter system view
|
system-view
|
––
|
|
Execute the batch file
|
execute filename
|
Optional
Available in system view
|
Caution:
l
Empty the recycle bin timely with the reset
recycle-bin command to save memory space.
l
As the delete /unreserved file-url
command deletes a file permanently and the action cannot be undone, use it with
caution.
l
The execute command cannot ensure the
execution of each command. For example, if a certain command is not correctly
configured, the system will omit this command and go to the next one.
Therefore, each configuration command in a batch file must be a standard
configuration command, meaning the valid configuration information which can be
displayed with the display current-configuration command after this
command is configured successfully; otherwise, this command may not be executed
correctly.
1.1.4 Storage Device Operations
Storage device operations include disk fix
and format as shown in the following table:
|
To do…
|
Use the command…
|
Remarks
|
|
Restore the space of a storage device
|
fixdisk device
|
Optional
Available in user view
|
|
Format a storage device
|
format device
|
Optional
Available in user view
|
You may use the two commands when some
space of a storage device becomes inaccessible due to abnormal operations for
example.
Caution:
When you format a storage device, all the files stored on it are
erased and cannot be restored. In particular, if you format the Flash, the bootup
and configuration file will be missing.
1.1.5 File System Prompt Mode Setting
The file system provides the following two
prompt modes:
l
Alert, where the system warns you about
operations that may bring undesirable consequence such as file corruption or
data loss.
l
Quiet: where the system does not do that in any
cases. To prevent undesirable consequence resulted from misoperations, the
alert mode is preferred.
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
––
|
|
Set the operation prompt mode of the file
system
|
file prompt { alert | quiet }
|
Optional
The default is alert.
|
1.1.6 File System Operations Example
# Display the files under the root
directory.
<Sysname> dir
Directory of flash:/
0 drw- - Feb 16 2006
11:45:36 logfile
1 -rw- 1218 Feb 16 2006
11:46:19 config.cfg
2 drw- - Feb 16 2006
15:20:27 test
3 -rw- 184108 Feb 16 2006
15:30:20 aaa.bin
15240 KB total (2521 KB free)
# Create a new folder called mytest under
the test directory.
<Sysname> cd test
<Sysname> mkdir mytest
%Created dir flash:/test/mytest.
# Display the files under the test
directory.
<Sysname> dir
Directory of flash:/test/
0 drw- - Feb 16 2006
15:28:14 mytest
15240 KB total (2519 KB free)
# Return to the upper directory.
<Sysname> cd ..
1.2 Configuration File Management
This section covers these topics:
l
Overview
l
Saving Running Configuration
l
Erasing the Startup Configuration File
l
Specifying a Configuration File for Next Startup
l
Naming Configuration Files and Selecting One for
Startup
l
Displaying and Maintaining Device Configuration
1.2.1 Overview
I. Types of configuration
The configuration of a device falls into
two types:
l
Saved configuration, a configuration file used
for initialization. If this file does not exist, the default parameters are
used.
l
Current configuration, which refers to the user’s
configuration during the operation of a device. This configuration is stored in
the flash. It is removed when rebooting.
II. Format of configuration file
Configuration files are saved as text files
for ease of reading. They:
l
Save configuration in the form of commands.
l
Save only non-default configuration settings.
l
List commands in sections by view in this view order:
system, interface, routing protocol, and so on. Sections are separated with one
or multiple blank lines or comment lines that start with a pound sign (#).
l
End with a return.
The operating interface provided by the configuration
file management function is user-friendly. With it, you can easily manage your
configuration files.
III. Main/backup attribute of the configuration
file
A main configuration file and a backup configuration file can exist simultaneously
if the device supports main/backup configuration file attribute. As such, when the
main configuration file is missing or damaged, the backup file can be used
instead. This increases the safety and reliability of the file system compared
with the device that only support one configuration file. You can configure a
file to have both main and backup attribute, but only one file of either main
or backup attribute is allowed on a device.
The following three situations are
concerned with the main/backup attributes:
l
When saving the current configuration, you can
specify the file to be a main or backup or normal configuration file.
l
When removing a configuration file from a device,
you can specify to remove the main or backup configuration file. Or, if it is a
file having both main and backup attribute, you can specify to erase the main
or backup attribute of the file.
l
When setting the configuration file for next
startup, you can specify the main/backup attribute of the file.
IV. Startup with the configuration
file
The following steps are taken during
startup:
1)
If the main configuration file exists, the
device initializes with this configuration.
2)
If the main configuration file does not exist but
the backup configuration file exists, the device initializes with the backup
configuration.
3)
If neither the main nor the backup configuration
file exist, the device will:
l
Initialize with the default configuration file
if it exist;
l
Or initialize with empty configuration if the
default configuration file does not exist.
You can modify the configuration on your
device at the command line interface (CLI). To use the modified configuration for
your subsequent startups, you must save it (using the save command) as a
configuration file.
I. Two modes in saving the configuration
l
Fast saving mode. This is the mode when you use the
save command without the safely keyword. The mode saves the file
quicker but is likely to lose the configuration file if the device reboots or
the power fails during the process.
l
Safe mode. This is the mode when you use the save
command with the safely keyword. The mode saves the file slower but can
retain the configuration file in the flash even if the device reboots or the
power fails during the process.
II. Three attributes of the
configuration file
l
Main attribute. When you use the save [ [
safely ] [ main ] ] command to save the current configuration,
the configuration file you get has main attribute. If this configuration file
already exists and has backup attribute, the file will have both main and
backup attributes after execution of this command. If the filename you entered
is different from that existing in the system, this command will erase its main
attribute to allow only one main attribute configuration file in the device.
l
Backup attribute. When you use the save [
safely ] backup command to save the current configuration, the
configuration file you get has backup attribute. If this configuration file
already exists and has main attribute, the file will have both main and backup
attributes after execution of this command. If the filename you entered is
different from that existing in the system, this command will erase its backup
attribute to allow only one backup attribute configuration file in the device.
l
Normal attribute. When you use the save file-name
command to save the current configuration, the configuration file you get has
normal attribute if it is not an existing file. Otherwise, the attribute is
dependent on the original attribute of the file.
Follow the step below to save current
configuration:
|
To do…
|
Use the command…
|
Remarks
|
|
Save current configuration
|
save [ file-name
| [ safely ] [ main | backup ] ]
|
Required
Available in any view
|
l
Fast saving is suitable for environments where
power supply is stable. The safe mode, however, is preferred where stable power
supplies are unavailable or remote maintenance is involved.
l
The extension of the configuration file must be
.cfg.
1.2.3 Erasing the Startup Configuration File
After erasing the configuration file, your
device will boot up with the default configuration next time it is powered on.
You may need to erase the configuration
file for one of these reasons:
l
After you upgrade software, the old
configuration file does not match the new software.
l
The startup configuration file is corrupted or not
the one you needed.
The following two situations exist:
l
While the reset saved-configuration main command erases the configuration file with main attribute, it only
erases the main attribute of a configuration file having both main and backup
attribute.
l
While the reset saved-configuration backup command erases the configuration file with backup attribute, it
only erases the backup attribute of a configuration file having both main and
backup attribute.
Follow the step below to erase the
configuration file:
|
To do…
|
Use the command…
|
Remarks
|
|
Erase the startup configuration file from
the storage device
|
reset saved-configuration [ main | backup ]
|
Required
Available in user view
|
Caution:
This command will
permanently delete the configuration file from the device.
1.2.4 Specifying a Configuration File for Next Startup
You can assign main or backup attribute to the
startup configuration file.
I. Assign main attribute to the
startup configuration file
l
If you save the current configuration to the
main configuration file, the system will automatically set the file as the main
startup configuration file.
l
You can also use the startup saved-configuration
cfgfile main command to set the file as main startup
configuration file.
II. Assign backup attribute to the
startup configuration file
l
If you save the current configuration to the backup
configuration file, the system will automatically set the file as the backup
startup configuration file.
l
You can also use the startup saved-configuration
cfgfile backup command to set the file as backup startup
configuration file.
Follow the step below to specify a
configuration file for next startup:
|
To do…
|
Use the command…
|
Remarks
|
|
Specify a configuration file for next
startup
|
startup saved-configuration
cfgfile [ main| backup ]
|
Required
Available in user view
|
The configuration
file must have an extension of .cfg and must be saved at the root directory of
the device.
1.2.5 Backup/Restore the Configuration File
for Next Startup
I. Backup/restore function overview
The backup/restore function allows you to
backup or restore a configuration file for next startup through operations at the
CLI. TFTP is used for intercommunication between the device and the server. The
backup function enables you to backup the main startup configuration file to the TFTP server, while the restore function enables
you to download the main startup configuration file from the TFTP server for startup.
The effect of the
backup/restore operation applies to the main startup configuration file.
II. Backup the configuration file
for next startup
|
To do…
|
Use the command…
|
Remarks
|
|
Backup the configuration file for next
startup
|
backup startup-configuration to dest-addr [ dest-filename ]
|
Required
Available in user view
|
Before backup, you
should:
l
Ensure that the route between the device and the
server is reachable; the server is enabled with TFTP
service, the client has permission to read and write.
l
Use the display startup command (in user
view) to verify if you have set the startup configuration file, and use the dir
command to verify if this file exist. If the file is set as NULL or does
not exist, the backup will be unsuccessful.
III. Restore the startup
configuration file
|
To do…
|
Use the command…
|
Remarks
|
|
Restore the startup configuration file
|
restore startup-configuration from src-addr src-filename
|
Required
Available in user view
|
l
Before restoring, you should ensure that the
route between the device and the server is reachable; the server is enabled
with TFTP service, the client has permission to read and
write.
l
After the command is successful executed, you
can use the display startup command (in user view) to verify if the
filename of the startup configuration file is the same with the filename
argument, and use the dir command to verify if the restored file exist.
1.3 Displaying and Maintaining Device Configuration
|
To do…
|
Use the command…
|
Remarks
|
|
Display the configuration file saved in
the storage device
|
display saved-configuration [ by-linenum ]
|
Available in any view
|
|
Display the configuration file used for
this and next startup
|
display startup
|
|
Display the validated configuration in
current view
|
display this [ by-linenum ]
|
|
Display current configuration
|
display current-configuration [ configuration [ configuration-type ] | interface
[ interface-type ] [ interface-number ] ] [ by-linenum ]
[ | { begin | include | exclude } text ]
|
l
Configuration files are displayed in the same
format in which they are saved.
l
For detailed description of the display this
and display current-configuration command, refer to Basic System Configuration
and Maintenance Command Module.
