
Chapter 35 File Manager
35.4 File Manager Commands Summary
The following table lists the commands that you can use for file management.
Table 136 File Manager Commands Summary
COMMAND | DESCRIPTION |
apply /conf/file_name.conf | Has the NXC use a specific configuration file. You must |
[rollback] | still use the write command to save your |
| configuration changes to the flash |
| “long term”) memory. |
| Use this command without specify both ignore- |
| error and rollback: this is not recommended |
| because it would leave the rest of the configuration |
| blank. If the interfaces were not configured before the |
| first error, the console port may be the only way to |
| access the device. |
| Use |
| the valid parts of the configuration file and generates |
| error logs for all of the configuration file’s errors. This |
| lets the NXC apply most of your configuration and you |
| can refer to the logs for what to fix. |
| Use both |
| the valid parts of the configuration file, generates error |
| logs for all of the configuration file’s errors, and starts |
| the NXC with a fully valid configuration file. |
| Use rollback without |
| NXC started with a fully valid configuration file as |
| quickly as possible. |
| You can use the “apply /conf/system- |
| default.conf” command to reset the NXC to go |
| back to its system defaults. |
copy {/cert /conf /idp /packet_trace | Saves a duplicate of a file on the NXC from the source |
/script | file name to the target file name. |
conf /idp /packet_trace /script / | Specify the directory and file name of the file that you |
want to copy and the directory and file name to use for | |
| the duplicate. Always copy the file into the same |
| directory. |
|
|
copy | Saves your configuration changes to the flash (“non- |
| volatile” or “long term”) memory. The NXC immediately |
| uses configuration changes made via commands, but if |
| you do not use this command or the write command, |
| the changes will be lost when the NXC restarts. |
|
|
copy | Saves a duplicate of the configuration file that the NXC |
| is currently using. You specify the file name to which to |
| copy. |
|
|
delete {/cert /conf /idp /packet_trace | Removes a file. Specify the directory and file name of |
/script /tmp}/file_name | the file that you want to delete. |
dir {/cert /conf /idp /packet_trace | Displays the list of files saved in the specified directory. |
/script /tmp} |
|
rename {/cert /conf /idp /packet_trace | Changes the name of a file. |
/script | Specify the directory and file name of the file that you |
conf /idp /packet_trace /script / | want to rename. Then specify the directory again |
followed by the new file name. | |
run /script/file_name.zysh | Has the NXC execute a specific shell script file. You |
| must still use the write command to save your |
| configuration changes to the flash |
| “long term”) memory. |
|
|
| 227 |
NXC CLI Reference Guide | |
|
|