Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Руководство администратора

Страница: 305 / 400

configuration 305
Media Flow Controller Administrator’s Guide Media Flow Controller CLI Commands
Notes:
•
copy
—Copy a configuration file. This does not affect the current running configuration.
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
—Delete a configuration file. This does not affect the current running
configuration. The active configuration file may not be deleted.
•
fetch
—Download (fetch) a configuration file. A file may not be downloaded over the
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
“Terminology” on page 30 for the scp URL
format and requirements.
•
merge
—Merge the shared configuration from one (non-active) configuration file into the
running configuration. No configuration files are modified during this process.
•
move
— Move a configuration file. This do not affect the current running configuration. The
active configuration file may not be the target of a move or copy.
•
new
—Create a new configuration file under the specified filename. The arguments
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
—Preserves licenses, and SSH host keys, and CMC rendezvous
configuration.
•
keep-connect
—Preserves anything necessary to maintain network connectivity to
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
—Revert both running and saved configurations to factory defaults. The
keep arguments preserve portions of the running configuration as described under
configuration new. The saved option reverts the running configuration to the latest
saved version of the active configuration.
Important! Reverting to the factory defaults
wipes the IP address of your management interface; you must use the serial console to re-
configure or switch to a saved configuration.
•
text
—Manage text configuration files; see “configuration text," for details.
•
switch-to
—Load configuration from the specified file and change that to be the active
configuration file. The current running configuration is lost, and not automatically saved to
the previous active configuration file.
•
upload
—Upload a configuration file. If active is specified for a configuration upload, the
currently-active configuration file is uploaded. No configuration file may have the name
active.
•
write
—Write the running configuration to persistent storage. If the to keyword is not
used, write to the currently active file. If to is used, write to persistent storage to the
specified file, and change the active file to that one. If no-switch is specified after to, the
active configuration file is not changed to the named file after the save.