Summary of File System Commands
The following lists the available file system commands in privileged EXEC mode.
Upgrading System Images
| Command | Purpose |
| controller> cd [filesystem] | Sets the default directory on the Flash memory device. If no directory name is specified, this sets the default directory to images. Permitted directories are:
images: The directory containing upgrade images ATS/scripts: The directory containing AP boot scripts backup: The directory containing database backup images. |
| controller> pwd | Displays the current working directory. |
| controller> dir [filesystem:][filename] | Displays a list of files on a file system. This can be one of the permitted directories given in the cd command or a remote directory referenced by an FTP URL. |
| controller# delete filename controller# delete directory:filename controller# delete flash: image | Deletes a file from the file system or deletes an upgrade image file from flash memory. The directory parameter can be used to delete a file from a different folder. |
| controller# show flash | Display the versions of the image files contained in the controller’s flash memory. |
| controller# rename old new | Renames a file from old to new. |
| controller# show running-config | Display the contents of the running configuration file. |
| controller# more running-config | Display the contents of the running configuration file. Alias for show running-config, but in contrast to that command, this one prompts the user to press a key to scroll the screen once it is filled. This allows the configuration to be shown a screen at a time, instead of scrolling all the way through instantly. |
| controller# copy running-config ftp|sftp|scp:[[[//username:password]@location/directory]/filename] | Copies the running configuration file to an FTP, SFTP, or SCP server, for example:
controller# copy running-config ftp://user1:userpass@server1/jan01config controller# copy running-config scp://user1:userpass@server1/ jan01-config |
| controller# copy running-config startupconfig | Saves the running-configuration to the startup configuration to make it persistent. You should always do this after a set of configuration commands if you want your changes to persist across reboots. |
Summary of File System Commands
| Command | Purpose |
| controller# reload ap [id] | all | controller | default | Reboots the controller and/or the specified AP:
If the ap keyword is specified, all APs are rebooted, or if id is included, the AP with the identifier id is rebooted. If the keyword all is specified, the Fortinet controller and all the APs are rebooted, using the current startup configuration. If the keyword controller is specified, the controller is rebooted, using the current startup configuration. If the keyword default is specified, the controller and all the APs are rebooted at the factory default startup configuration. |
| controller# upgrade feature version | Upgrades the system with the specified feature. |
| controller# upgrade system version | Upgrades the system image on the controller and all APs to the specified version. |
| controller# upgrade ap version | same
[id | range | all] |
Upgrades the access point image to the same version of system software that the controller is running.
id—Upgrades the access point with the specified ID to the same version of system software that the controller is running. range—Upgrades a range of APs, specified as a list using commas and dashes, without spaces or wildcards. AP IDs must be listed in ascending order. all—Upgrades all access point image to the same version of system software that the controller is running. |
| controller# downgrade system version | Downgrades the system image on the controller and all APs to the specified version. Note that when this command is executed, the user will be prompted to remove all local users and groups from the system. |
| controller# run script | Executes the named script. If the script is in the current directory, the relative path name is specified. Otherwise, the full path name must be specified. The script must be either in images, ATS/scripts, or backup. |