Managing Files

You are responsible for file management. Table 33 shows the types of system files and their corresponding extensions.

Table 33: Types of System Files and Corresponding Extensions

Type of File	Extension	Description
Configuration	*.cnf	Snapshot of the system’s configuration
Core dump	*.dmp	File you can create for troubleshooting if a module fails
History	*.hty (reboot.hty)	Details of when and why modules rebooted
Log	*.log	A series of messages that describe events that occurred on the system
Macro	*.mac	A macro program
Release	*.rel	Software releases you can install in the system
Script	*.scr	A sequence of CLI commands. When you run a script file, the system executes the commands as though they were entered at the terminal
Secure Shell (SSH) Server public key	*.pub	Host key for the SSH server
Statistics	*.sts	Bulk statistics created when you run the bulkstats commands
Text	*.txt	Text file

System files may reside in four locations:

The system space
The user space
A network host
The standby SRP module

The system space contains files for system operation. For example, the current software configuration is stored in the system space.

The user space is reserved for FTP server operations and has the typical directory structure of a secure FTP server. The root or top level directory is a read-only directory that contains two subdirectories:

/incoming—Read-write directory to and from which an FTP client can send and retrieve files.
/outgoing—Read-only directory from which an FTP client can retrieve files.

Users can transfer files through FTP to the user space from a network host and vice versa. However, users cannot access the system space through FTP. To install a file from the user space to the system space, use the copy command. For detailed information about transferring files between locations, see Transferring Files.

To conserve NVS and minimize the installation time, files are not stored in both the system space and the user space. When you issue the copy command to install a file from user space to system space, the E Series router establishes a link to the file, but does not make a physical copy.

Managing the User Space from a Network Host

If you enable the system’s FTP server (see Configuring the FTP Server), you can manage files on the user space from an FTP client on a network host. Table 34 lists the FTP protocol commands that the E Series router supports. Whether you can perform these functions on the user space depends on the features that the FTP client offers.

Table 34: FTP Commands That the System Supports

FTP Command	Function
HELP	List supported commands.
USER	Verify username.
PASS	Verify password for the user.
QUIT	Quit the session.
LIST	List contents of a directory.
NLST	List directory contents using a concise format.
RETR	Retrieve a file.
STOR	Store a file.
CWD	Change working directory.
CDUP	Change working directory to parent.
TYPE	Change the data representation type.
PORT	Change the port number.
PWD, XPWD	Get the name of current working directory.
STRU	Change file structure settings (only stream mode supported).
MODE	Change file transfer mode (only stream mode supported).
PASV	Make the server listen on a port for data connection.
NOOP	Do nothing.
DELE	Delete a file.
MKD, XMKD	Make directory.
RMD, XRMD	Remove directory.
RNFR	Rename from.
RNTO	Rename to.

File Commands and FTP Servers

Commands—copy, configure file, and macro—that invoke a remote FTP server take place in the context of the current virtual router rather than the default virtual router. You must configure the remote FTP server so that any traffic destined for the virtual router can reach the virtual router; typically, you configure the FTP server to reach the default address of the system, which will always be able to reach the virtual router.

Renaming Files

To rename files, use the rename command. Table 35 shows the types of files you can rename in different locations.

rename

Use to rename a local file.
You can change the base name but not the extension of a file.
Example
host1#rename boston1.cnf boston2.cnf

There is no no version.

Table 35: File Types You Can Rename

	Destination
Source	System Space	User Space (Linked Files and Unlinked Files)	Network Host Within a Firewall	Standby SRP Module
System	.cnf .dmp .hty .log .mac .rel .scr .txt Nonsystem files	.cnf .dmp .hty .log .mac .scr *.txt	*.sts	None
User Space	.cnf .hty (excluding reboot.hty) .log (excluding system.log) .mac .scr .txt	.cnf .dmp .hty .log .mac .pub .rel .scr .sts .txt Nonsystem files	None	None
Network Host Within a Firewall	None	None	None	None
Standby SRP Module	None	None	None	None

See rename.

Deleting Files

Use the delete command to delete files in NVS. Table 36 shows the types of files you can delete in different locations.

delete

Use to delete files in NVS.
To delete a file in user space, specify the incoming or outgoing directory on the FTP server. You can specify the name of a subdirectory in the incoming or outgoing directory.
You can include an asterisk (*) as a wildcard at any position in a specified filename. The asterisk substitutes for zero or more characters in the name. You cannot use an asterisk in a directory or subdirectory name.
You cannot delete reboot.hty or system.log files when you use a wildcard.
When you do not use a wildcard, the CLI deletes the file immediately without prompting you for confirmation. When you use a wildcard, the CLI prompts you for confirmation unless you also specify the force keyword; in that case the deletion takes place without confirmation.
The force keyword causes the immediate deletion of the directory or file even when it is not empty. However, if a file in the specified directory, or a specified file, is marked by the file system as in use because it is required for the current operation or configuration, the force keyword cannot force the deletion.
The force keyword is ignored when you attempt to delete any .dmp or .tsa file (unless the deletion is issued from a .mac or .scr file); this means that the CLI always prompts for confirmation for these file types.
Examples
host1#delete test-2.txt host1#
host1#del test*.txt Delete disk0:test-1.txt? [confirm] -> press ndisk0:test-1.txt: not deleted (per user request)Delete disk0:test-2.txt? [confirm] -> press ydisk0:test-2.dmp: DeletedDeleted 1 file, matched 2 files
host1#del test*.txt force disk0:test-1.txt: deleteddisk0:test-2.txt: deletedDeleted 2 files, matched 2 files
host1#del *.dmp force WARNING: The force option is ignored for this file type.Delete disk0:sample-1.dmp? [confirm] -> press ndisk0:sample-1.dmp: not deleted (per user request)Delete disk0:sample-2.dmp? [confirm] -> press ydisk0:sample-2.dmp: DeletedDeleted 1 file, matched 2 files
host1#delete /outgoing/test.scr

There is no no version.

Table 36: File Types You Can Delete

Location
System Space	User Space (Linked Files and Unlinked Files)	Network Host Within a Firewall	Standby SRP Module
.cnf .dmp .hty .log .mac .rel .scr .sts *.txt	.cnf .dmp .hty .log .mac .pub .rel (deletes .rel file only and not associated files) .scr .sts *.txt Nonsystem files	None	*.dmp

Location

System Space

User Space

(Linked Files and Unlinked Files)

Network Host Within a Firewall

Standby SRP Module

*.cnf

*.dmp

*.hty

*.log

*.mac

*.rel

*.scr

*.sts

*.txt

*.cnf

*.dmp

*.hty

*.log

*.mac

*.pub

*.rel
(deletes *.rel file only and not associated files)

*.scr

*.sts

*.txt

Nonsystem files

None

*.dmp

See delete.

Monitoring Files

Use the dir command to view files in NVS.

Note: When high availability is enabled on the router, it is possible that files or file attributes may appear unsynchronized when they are not. When enabled, high availability mirrors configuration changes instantly from the active SRP to the standby SRP. However, although these changes are reflected immediately in memory, the standby SRP NVS is updated at 5 minute intervals.

dir

Use to show a list of files in NVS.
Specify a directory path, a local filename, a local device name, or some combination of these to view any local files or directories. You canot use the dir command on a network device.
You can include an asterisk (*) at any position in a specified filename as a wildcard. The asterisk substitutes for zero or more characters in the name. You cannot use a wildcard in a path.
Bulk statistics .sts files are stored in volatile storage on a RAM disk, and are displayed only when bulkstats is configured.
Note: When you issue the dir command from Boot mode, a reduced set of file types is displayed.
Field descriptions
- file—Name of file or directory (DIR indicates a directory)
- size—Physical size of file
- unshared size—Size of file in user space
  - Value of zero indicates that this file has been installed onto the system space and that there is a link to this file.
  - Value other than zero indicates that the file has not been installed onto the system space and equals the physical size of the file.
- date—Date that file was created
- in use—An exclamation point (!) indicates that the system is using this file

Example 1

host1#dir
Please wait.....

Active/standby file systems are synchronized.

                                                         unshared
                 file                           size        size
--------------------------------------------   ---------   ---------
disk0:/incoming <DIR>                             0
disk0:/outgoing <DIR>                             0
disk0:810beta13.cnf                             280944      280944
disk0:800beta12.cnf                             327011      327011
disk0:bng___1.txt                               11092       11092
disk0:bng___2.txt                               11092       11092
disk0:bng___3.txt                               11092       11092
disk0:erx701rel.cnf                             255400      255400
disk0:730beta19.cnf                             283141      283141
disk0:730beta18.cnf                             284503      284503
disk0:erx_8-0-0b0-24.cnf                        327404      327404
disk0:7.3run.cnf                                 301635      301635
disk0:80beta_bce_backup.cnf                      333228      333228
disk0:800beta5.cnf                               300575      300575
disk0:820beta5.cnf                               311616      311616
disk0:810beta16.cnf                              297764      297764
disk0:SRP-10Ge_3_SC_08_22_2006_07_39.dmp         153268924   153268924
disk0:SRP-10Ge_3_SC_04_12_2007_09_47.dmp         182385184   182385184
disk0:reboot.hty                                 402368      402368
disk0:system.log                                    702         702
disk0:erx_9-0-0a1-7.rel                          176128192   160912356
disk0:erx_8-1-0b1-2.rel                          164065212   148633854
disk0:erx_8-2-0b1-5.rel                          166117319   150685961
disk0:testing_cat.txt                              21848       21848
standby-disk0:SRP-10Ge_1_SC_08_21_2006_13_48.dmp 153547479   153547479
standby-disk0:SRP-10Ge_1_SC_04_12_2007_10_04.dmp 194849368   194849368
standby-disk0:reboot.hty                              123136      123136
standby-disk0:system.log                                 855         855
                                                                     in
                      file                          date (UTC)      use
--------------------------------------------   -------------------   ---
disk0:/incoming <DIR>                             02/08/2008 15:06:42
disk0:/outgoing <DIR>                             02/08/2008 15:06:42
disk0:810beta13.cnf                               02/06/2007 15:13:44
disk0:800beta12.cnf                               09/29/2006 16:31:54
disk0:bng___1.txt                                 02/12/2008 07:05:20
disk0:bng___2.txt                                 02/12/2008 07:05:28
disk0:bng___3.txt                                 02/12/2008 06:59:46
disk0:erx701rel.cnf                               10/07/2005 13:01:02
disk0:730beta19.cnf                               07/12/2006 07:21:22
disk0:730beta18.cnf                               06/19/2006 15:23:46
disk0:erx_8-0-0b0-24.cnf                          11/02/2006 12:23:38
disk0:7.3run.cnf                                  08/21/2006 11:19:52
disk0:80beta_bce_backup.cnf                       10/04/2007 09:01:36
disk0:800beta5.cnf                                01/02/2007 16:01:36
disk0:820beta5.cnf                                05/09/2007 14:29:58
disk0:810beta16.cnf                               03/15/2007 06:58:14
disk0:SRP-10Ge_3_SC_08_22_2006_07_39.dmp          08/22/2006 07:43:14
disk0:SRP-10Ge_3_SC_04_12_2007_09_47.dmp          04/12/2007 09:51:08
disk0:reboot.hty                                  01/09/2008 13:57:02
disk0:system.log                                  11/12/2007 09:56:14
disk0:erx_9-0-0a1-7.rel                           10/04/2007 08:40:06    !
disk0:erx_8-1-0b1-2.rel                           03/15/2007 06:50:32
disk0:erx_8-2-0b1-5.rel                           05/09/2007 14:22:22
disk0:testing_cat.txt                             03/13/2006 17:42:12
standby-disk0:SRP-10Ge_1_SC_08_21_2006_13_48.dmp  08/21/2006 13:51:42
standby-disk0:SRP-10Ge_1_SC_04_12_2007_10_04.dmp  04/12/2007 10:08:38
standby-disk0:reboot.hty                          01/09/2008 13:53:10         
standby-disk0:system.log                          04/12/2007 09:47:24

                Disk capacity
              -------------
                  Capacity      Free      Reserved
    Device        (bytes)      (bytes)    (bytes)
--------------   ----------   ---------   --------
disk0:           1054900224   167372414   68157440
standby-disk0:   1054900224   153330775   68157440

Example 2

host1#dir *.txt
Please wait.....

Active/standby file systems are synchronized.

                                                unshared
                file                   size        size
----------------------------------   ---------   ---------
disk0:bng___1.txt                      11092       11092
disk0:bng___2.txt                      11092       11092
disk0:bng___3.txt                      11092       11092
                                                        in
                      file             date (UTC)      use
----------------------------------   --------------- ---
disk0:bng___1.txt                      02/12/2008 07:05:20
disk0:bng___2.txt                      02/12/2008 07:05:28
disk0:bng___3.txt                      02/12/2008 06:59:46

             Disk capacity
              -------------
                  Capacity      Free      Reserved
    Device        (bytes)      (bytes)    (bytes)
--------------   ----------   ---------   --------
disk0:           1054900224   167372414   68157440
standby-disk0:   1054900224   153330775   68157440

Example 3

host1#dir /incoming
                                unshared                      in
    file               size       size      date (UTC)        use
-------------       --------   --------   ----------------   ---
disk0:3-0-0a3-7.rel     256        0    12/19/2000 07:14:01
disk0:srp.exe         30012312     0    12/19/2000 07:14:12
disk0:srpIc.exe       1801208      0    12/19/2000 07:20:32
disk0:srpDiag.exe     6984222      0    12/19/2000 07:22:08

              Disk capacity
              -------------
          Capacity      Free      Reserved
Device    (bytes)      (bytes)    (bytes)
------   ----------   ---------   --------
disk0:    220200960   120616448   36700160

Example 4

host1#dir /outgoing
                           unshared                         in
    file          size       size         date (UTC)        use
-------------   --------   --------   -------------------   ---
disk0:test.scr    1204          0   12/18/2000 03:01:04
disk0:foo.scr     1278       1278   12/20/2000 04:02:12

              Disk capacity
              -------------
          Capacity      Free      Reserved
Device    (bytes)      (bytes)    (bytes)
------   ----------   ---------   --------
disk0:    220200960   120616448   36700160

There is no no version.
See dir.

Viewing Files

Use the more command to display the contents of a macro, script, or text file. The file can reside in NVS on the primary SRP module, in NVS on the redundant (standby) SRP module, or on a remote server that you access using FTP.

more

Use to display the contents of a macro, script, or text file that resides in NVS on the primary SRP module, in NVS on the redundant SRP module, or on a remote server that you access using FTP.
Specify the file you want to display using one of the following formats, depending on the location of the file:
- fileName—Name of the file that resides in NVS on the primary SRP module
- standby:fileName—Name of the file that resides in NVS on the redundant (standby) SRP module
- serverName:filePathName—Name of the remote server on which the file resides and the complete pathname of the file
Example 1—Displays the contents of a text file named erxconfig.txt that resides in NVS on the primary SRP module
host1#more erxconfig.txt
Example 2—Displays the contents of a macro file named mysetup.mac that resides in NVS on the redundant (standby) SRP module
host1#more standby:mysetup.mac
Example 3—Displays the contents of a script file named myconfig.scr that resides on a remote server named fileserver1
host1#more fileserver1:/startup/scripts/myconfig.scr
There is no no version.
See more.