System
Administration
Motorola, Inc.
549453-001-00-a
Page 14 of 51
a. Source can be a local file, a remote FTP or TFTP file, or a pre-defined keyword. Keywords allow you to capture
the startup and running configuration to a file. Supported keywords are “startup” and “running”.
b. Destination can be a local file or a remote FTP or TFTP file. Note that the combination of the Source keywords
and the remote Destination allows you to copy the running config directly to a remote server. For example; file
copy running to tftp://192.168.1.1/my-t2-config.txt
c. At least one (source or destination) must be the local file system. If the source and destination are remote
servers, the command will fail.
file delete <string(file)>
d. Delete a file from the file system
file
dir
e. List the files in the system and display the remaining storage
file exec <string(file)>
f.
Executes a file as a set of configuration commands. Note that “file” is a local file in the file system. The file must
have previously been copied to the filesystem from the external server using the
file copy
command.
C
C
o
o
n
n
f
f
i
i
g
g
u
u
r
r
a
a
t
t
i
i
o
o
n
n
F
F
i
i
l
l
e
e
s
s
u
u
s
s
i
i
n
n
g
g
t
t
h
h
e
e
w
w
e
e
b
b
U
U
I
I
From the webUI, the administrator can save and load configuration files. Note that these configuration files are non-
editable binary format for configuration security. If editable configuration is desired, use the CLI script files.
Configuration files from the webUI can be used to create secure template configurations.
Note: The Configuration File contains every configuration possible including the “Admin” account password. When
combined with RADIUS network authentication, the non-editable Configuration Files provide a secure method to pre-
configure systems in a staging area and apply the secure “admin” password without revealing the password. Contact
a Tut Systems support person for assistance with a setting up secure, staged configurations.
To save or load a Configuration file from the webUI, access the
System – Configuration
screen from the webUI.
Follow these steps to create a template configuration file:
1. Configure a complete system configuration
2. Set the system name to “template configuration” or similar name
3. Save the configuration file using the webUI
System-Configuration screen
Follow these steps to apply the template to a new system:
1. Boot a new system
2. Using the serial console login, set the IP address (or use the default IP address)
3. Reboot the system to apply the IP address
4. Login via the webUI
5. Load the template configuration file using the System-Configuration screen
6. Change the system name to the correct name
7. Change the IP address to the correct IP address
8. Power off or reboot the system. The next time the system is booted, it will have the complete configuration
with the correct IP address and system name.
