Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 306 / 400

Media Flow Controller CLI Commands Media Flow Controller Administrator’s Guide
306 configuration text Copyright © 2010, Juniper Networks, Inc.
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.
show configuration
files [<filename>]
full
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, list configuration files in persistent storage. If
filename is specified, list 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
—List 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.
configuration text
Manage text-based configuration files (lists of CLI commands). These files are stored in /
config/text on the appliance. Not all configuration is included in the show configuration
output, so a text configuration file generated and re-applied later may not fully recreate the
same configuration.
text
fetch <URL_or_SCP>
apply [discard][fail-continue][verbose]
filename <filename> [apply [fail-continue][verbose]]