...
| Note |
|---|
If your login username is not a member of the "secrets" login user group and you either save a configuration through the REST API or use the save command, the encrypted passwords in the configuration file are replaced with the ******** placeholder. If you load this configuration, the replaced password fields trigger validation errors because the placeholder does not match the format for an encrypted password. Do not commit this configuration. If you ignore the error message |
...
load - load configuration from a file and replace candidate configuration
Syntax: load <file-name>
Use this command to load from a file a configuration that was previously saved.
The loaded configuration becomes the working configuration and must be committed before it becomes the active configuration.
Configuration can be loaded from a hard disk (including a Flash disk or USB device), a TFTP server, an FTP server, an SCP server, or an HTTP server. Note that you cannot load an empty configuration file; the configuration file must contain at least one configuration node. In addition, an error is reported if an invalid configuration file is loaded.
The default configuration directory is /config.
loadkey - load user SSH key from a file
...
merge - merge configuration from a file into the candidate configuration
Syntax: merge <file-name>
Use this command to load from a file a configuration that was previously saved and merge it with the active (running) configuration. The merger adds new configuration entries and applies any modifications to existing active entries to produce a new working configuration. This configuration must be committed before it becomes the active configuration.
Configuration can be loaded from a hard disk (including a Flash disk or USB device), a TFTP server, an FTP server, an SCP server, or an HTTP server. Note that you cannot load an empty configuration file; the configuration file must contain at least one configuration node.
The default configuration directory is /config.
rollback - rollback to a previous configuration
Syntax: rollback <rev-number> [ comment <comment-text> ]
Use this command to roll back to the configuration revision specified.
You can see the list of configuration file revisions using the show system commit operational mode command (use run show system commit from configuration mode).
run - run an operational-mode command
save - save the configuration to a file
Syntax: save <file-name>
Use this command to save the running configuration to a file.
The resulting file can later be loaded into the running system to replace the previous running configuration by using the load command. A nonabsolute path is interpreted relative to the default configuration directory, which is /config.
| Note |
|---|
If your login username is not a member of the "secrets" login user group and you either save a configuration through the REST API or use the save command, the encrypted passwords in the configuration file are replaced with the ******** placeholder. If you load this configuration, the replaced password fields trigger validation errors because the placeholder does not match the format for an encrypted password. Do not commit this configuration. If you ignore the error message and perform a commit with this invalid configuration, the passwords are deleted. |
set - set the value of a parameter or create a new element
Syntax: set config-name attribute [ value ]
Use this command to add a configuration element to the current configuration.
You can also use this command to modify the value of an existing configuration item. When setting configuration values, note that the change does not take effect until the change is committed by using the commit command.
After a configuration node has been added, you can modify it later by using set or delete it by using delete.
show - show the configuration
Syntax: show [ -all ] [ config-name ]
Use this command in configuration mode to display the configured state of the system.
This command displays the specified configuration node and all subnodes. The node specification is interpreted relative to your current location in the configuration tree.
Unless the -all keyword is used, default information is not included in the displayed information.
In addition to this command, a number of show commands are available in operational mode.
For example, see the difference between show interfaces and show -all interfaces.
| Code Block | ||
|---|---|---|
| ||
vyatta@R1# show interfaces
interfaces {
dataplane dp0p1s1 {
address 10.10.1.1/24
}
dataplane dp0s2 {
address dhcp
}
loopback lo
}
vyatta@R1# show -all interfaces
interfaces {
dataplane dp0p1s1 {
address 10.10.1.1/24
duplex auto
ip {
gratuitous-arp-count 1
rpf-check disable
}
ipv6 {
dup-addr-detect-transmits 1
}
mtu 1500
speed auto
vlan-protocol 0x8100
vrrp {
start-delay 0
}
}
dataplane dp0s2 {
address dhcp
duplex auto
ip {
gratuitous-arp-count 1
rpf-check disable
}
ipv6 {
dup-addr-detect-transmits 1
}
mtu 1500
speed auto
vlan-protocol 0x8100
vrrp {
start-delay 0
}
}
loopback lo
}
vyatta@R1# |
top - set the edit level to the root
Syntax: top
Use this command to navigate quickly to the top level of the configuration hierarchy.
up - set the edit level one level up
Syntax: up
This command navigates up one level in the configuration hierarchy. For example:
...