You can use any of the methods shown in Table 4 to configure JUNOS system software:
Table 4: Methods
for Configuring JUNOS Software
Method
Description
Command-line interface (CLI)
Create the configuration for the router 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 router 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.
J-Web graphical user
interface (GUI)
Use the J-Web graphical user interface (GUI) to configure
the router. J-Web enables you to monitor, configure, troubleshoot,
and manage the router on a client by means of a Web browser. The J-Web
GUI is preinstalled on J Series Services Routers and is an optional
software package that can be installed on M Series and T Series routers.
Use JUNOScript Perl client modules to develop custom
applications for configuring information on routers that run JUNOS
Software. Client applications use the JUNOScript API to request and
change configuration information on Juniper Networks J Series, M Series,
and T Series routers. The JUNOScript API is customized for JUNOS Software
and operations in the API are equivalent to JUNOS CLI.
NETCONF application programming interface
(API)
Use NETCONF Perl client modules to develop custom applications
for configuring information on routers that run JUNOS Software. Client
applications use the NETCONF API to request and change configuration
information on Juniper Networks J Series, M Series, and T Series routers.
The NETCONF API 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 Extensible Stylesheet
Language Transformations (XSLT).
The following sections contain
complete descriptions of the methods you can use to configure JUNOS
system software:
The JUNOS CLI is a straightforward 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. For more information about the CLI, see the JUNOS CLI User Guide and JUNOS System Basics and Services Command Reference.
ASCII File
You can load an ASCII file containing a router 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.
J-Web Package
As an alternative to entering CLI commands, the
JUNOS Software supports a J-Web graphical user interface (GUI). The
J-Web user interface enables you to monitor, configure, troubleshoot,
and manage the router on a client by means of a Web browser with Hypertext
Transfer Protocol (HTTP) or HTTP over Secure Sockets Layer (HTTPS)
enabled.
The J-Web user interface is preinstalled on J Series
Services Routers. It is provided as an optional, licensed software
package (jweb package) on M Series and T Series routers.
The jweb package is not included in jinstall and jbundle software bundles. It must be installed separately. To
install the package on M Series and T Series routers, follow
the procedure described in the JUNOS Software Installation and Upgrade Guide.
J-Web supports weak (56-bit) encryption by default.
This enables international customers to install J-Web and use HTTPS
connections for J-Web access. Domestic customers can also install
the jcrypto strong encryption package. This package automatically
overrides the weak encryption. For more information about the J-Web
GUI, see the J-Web Interface User Guide.
Note:
Because the J-Web package is bundled separately
from other packages, it is possible to have a version mismatch between
J-Web and other JUNOS Software packages you have installed.
To check for a version mismatch, use the show
system alarms CLI command. If the version number does not match
exactly, a system alarm appears. For example, if you install the 7.4R1.2 jroute package and the 7.4R1.1 jweb package, an alarm
is activated. For more information on the show system alarms command, see the JUNOS System Basics and Services Command Reference.
JUNOScript API Software
The JUNOScript API is an Extensible Markup Language
(XML) application that client applications use to request and change
configuration information on Juniper Networks J Series, M Series,
MX Series, and T Series routers. This API is customized for JUNOS
Software, and operations in the API are equivalent to JUNOS CLI configuration
mode commands. The JUNOScript API includes a set of Perl modules that
enable client applications to communicate with a JUNOScript server
on the router. The Perl modules are used to develop custom applications
for configuring and monitoring JUNOS Software.
For a complete description of how to use JUNOS
XML and JUNOScript API software, see the JUNOScript API Guide.
NETCONF API Software
The NETCONF API is an Extensible Markup Language
(XML) application that client applications can use to request and
change configuration information on Juniper Networks J Series, M Series,
MX Series, and T Series routers. This API is customized for JUNOS
Software, and includes features that accommodate the configuration
data models of multiple vendors. The NETCONF API includes a set of
Perl modules that enable client applications to communicate with a
NETCONF server on the router. The Perl modules are used to develop
custom applications for configuring and monitoring JUNOS Software.
For a complete description of how to use JUNOS
XML and NETCONF API software, see the NETCONF API Guide.
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 Software
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 configuration statements.
Commit scripts are written in Extensible Stylesheet Language Transformations
(XSLT). For more information, see the JUNOS Configuration and Diagnostic Automation Guide.
