Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual page 112

CHAPTER 5 CLI Commands
upload {active <URL> | initial.bak | initial}
write [to <filename>] [no switch]
Notes:
•
—Copy a configuration file. This does not affect the current running configuration.
copy
The active configuration file may not be deleted or renamed, nor may it be the target of a
move or copy. It may be the source of a copy, in which case the original remains active.
•
delete
configuration. The active configuration file may not be deleted.
•
fetch
active configuration file. If no filename is specified for a configuration fetch, it is given
the same name as it had on the server. See the
for the scp URL format and requirements.
•
merge
running configuration. No configuration files are modified during this process.
•
— Move a configuration file. This do not affect the current running configuration. The
move
active configuration file may not be the target of a move or copy.
•
—Create a new configuration file under the specified filename. The arguments
new
specify what configuration, if any, to carry forward from the current running configuration.
The factory argument creates the new file with only factory defaults. The optional keep
arguments preserve portions of the running configuration:
•
keep-basic
configuration.
•
keep-connect
the system: interfaces, routes, and ARP.
Either, both, or neither may be selected after factory; if neither are specified, the default is
keep-basic. Thus configuration new <filename> is the same as configuration new
<filename> factory keep-basic.
•
revert factory
keep arguments preserve portions of the running configuration as described under
configuration new above. The saved option reverts the running configuration to the
latest saved version of the active configuration.
defaults wipes the IP address of your management interface; you must use the serial
console to re-configure or switch to a saved configuration.
•
—Manage text configuration files; see
text
•
switch-to
configuration file. The current running configuration is lost, and not automatically saved to
the previous active configuration file.
•
upload
currently-active configuration file is uploaded. No configuration file may have the name
active.
•
write
used, write to the currently active file. If to is used, write to persistent storage to the
112 configuration
file {<filename> | initial | initial.bak}
[upload <URL_or_SCP>]
—Delete a configuration file. This does not affect the current running
—Download (fetch) a configuration file. A file may not be downloaded over the
—Merge the shared configuration from one (non-active) configuration file into the
—Preserves licenses, and SSH host keys, and CMC rendezvous
—Preserves anything necessary to maintain network connectivity to
—Revert both running and saved configurations to factory defaults. The
—Load configuration from the specified file and change that to be the active
—Upload a configuration file. If active is specified for a configuration upload, the
—Write the running configuration to persistent storage. If the to keyword is not
Media Flow Manager Administrator's Guide
[save <filename>]
"Command Arguments Key" on page 95
Reverting to the factory
Important!
"configuration text," next for details.
Copyright © 2010, Juniper Networks, Inc.