Methods for Configuring Junos OS Evolved
Depending on specific device support, you can use the methods shown here to configure Junos OS Evolved. For more information, see the Juniper Networks Feature Explorer.
|
Method |
Description |
|---|---|
|
Command-line interface (CLI) |
Create the configuration for the device using the CLI. You can enter commands from a single command line, and scroll through recently executed commands. |
|
ASCII file |
Load an ASCII file containing a configuration that you created earlier, either on this system or on another system. You can then activate and run the configuration file, or you can edit it using the CLI and then activate it. |
|
Junos XML management protocol (API) |
Client applications use the Junos XML management protocol to monitor and configure Juniper Networks devices. The Junos XML management protocol is customized for Junos OS Evolved, and operations in the API are equivalent to those in the Junos OS Evolved CLI. |
|
NETCONF application programming interface (API) |
Client applications use the NETCONF XML management protocol to monitor and configure supported devices. The NETCONF XML management protocol includes features that accommodate the configuration data models of multiple vendors. |
|
Configuration commit scripts |
Create scripts that run at commit time to enforce custom configuration rules. Commit scripts are written in Python, Stylesheet Language Alternative syntaX (SLAX), or Extensible Stylesheet Language Transformations (XSLT). |
The following sections describe the methods you can use to configure Junos OS Evolved:
Junos OS Evolved Command-Line Interface
The Junos OS Evolved CLI is a straightforward terminal-based command interface. You use Emacs-style keyboard sequences to move around on a command line and scroll through a buffer that contains recently executed commands. You type commands on a single line, and the commands are executed when you press the Enter key. The CLI also provides command help and command completion.
ASCII File
You can load an ASCII file containing a configuration that you created earlier, either on this system or another system. You can then activate and run the configuration file as is, or you can edit it using the CLI and then activate it.
Junos XML Management Protocol Software
The Junos XML Management Protocol is an XML-based protocol that client applications use to monitor and configure Juniper Networks devices. It uses an XML-based data encoding for the configuration data and remote procedure calls. This API is customized for Junos OS Evolved, and operations in the API are equivalent to CLI commands.
NETCONF XML Management Protocol Software
The NETCONF XML management protocol is an XML-based protocol that client applications use to monitor and configure network devices. It uses an XML-based data encoding for the configuration data and remote procedure calls. NETCONF includes features that accommodate the configuration data models of multiple vendors. Juniper Networks provides a set of Perl modules that enable Perl client applications to communicate with the NETCONF server on Junos devices. The Perl modules enable you to develop custom applications for configuring and monitoring Junos OS Evolved.
Configuration Commit Scripts
You can create and use scripts that run at commit time to enforce custom configuration rules. If a configuration breaks the custom rules, the script can generate actions that the Junos OS Evolved performs. These actions include:
-
Generating custom error messages
-
Generating custom warning messages
-
Generating custom system log messages
-
Making changes to the configuration
Configuration commit scripts also enable you to create macros, which expand simplified custom aliases for frequently used configuration statements into standard Junos OS Evolved configuration statements. Commit scripts are written in Python, Stylesheet Language Alternative syntaX (SLAX), or Extensible Stylesheet Language Transformations (XSLT).