Media Flow Controller CLI Commands : configuration

The system can store one or more configuration files on persistent storage with one of the files is designated as active: the file that configuration is loaded from on boot, and to which configuration is saved upon a save request. Configuration changes are immediately applied to the running configuration, but are not made persistent until they are explicitly saved using configuration write. See “Saving and Applying Configurations” on page 106 for task details.
copy {initial.bak | initial | <source_filename>} <dest_filename>
delete {<filename> | initial.bak | initial}
fetch {<URL> | <SCP>]
merge {<filename> | initial.bak | initial}
move {<source_filename> | initial.bak | initial} <dest_filename>
new <filename> [factory [keep-basic] [keep-connect]]
revert {factory [keep-basic] [keep-connect] | saved}
switch-to {<filename> | initial.bak | initial}
fetch <URL_or_SCP>
apply [discard][fail-continue][verbose]
filename <filename> [apply [fail-continue][verbose]]
file <filename>
apply [fail-continue][verbose]
rename <new_filename>
upload <URL or SCP>
active {running | saved} [save <filename>] [upload <URL_or_SCP>]
file {<filename> | initial | initial.bak} [save <filename>] [upload <URL_or_SCP>]
upload {active <URL> | initial.bak | initial}
write [to <filename>] [no switch]
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 the “Command Arguments Key” on page 161 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 above. 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," next 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.
Note! If downloading configuration files from another system running the management system, they can be found in the /config/db directory. So an example command line to fetch the initial configuration database would be:
configuration fetch scp://admin:password@hostname/config/db/initial
write [memory] [terminal]
These commands preform the same functions as the as configuration write commands; included for ease-of-use. Notes:
write memory—Same as configuration write.
write terminal—Same as show running-config (described below).
show configuration
files [<filename>]
running [full]
text files
List the CLI commands needed to bring the state of a fresh system up to match the current persistent (saved) state of this system. A short header is included, containing the name and version number of the configuration, in a comment. Arguments:
files—If no filename is specified, display a list of configuration files in persistent storage. If filename is specified, display the commands to recreate the configuration in that file; only non-default commands are shown.
full—Same as show configuration but includes commands that set default values.
running—Same as show configuration except that it applies to the currently running configuration, rather than the active saved configuration.
text files—Display text-based configuration files.
Note! Commands that would set something to its default are not included—so this command on a fresh configuration produces no output, except the header.
Note! This does not include changes that have been made but not yet written to persistent storage.
show running-config
show running-config [full]
The show running-config commands perform the same functions as the show configuration commands and are included for ease-of-use.

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.