|
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.
|
|
JUNOScript application programming interface
(API)
|
Use JUNOScript Perl client modules to develop custom applications
for configuring information on routing platforms 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 routing
platforms. 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 routing platforms 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 routing
platforms. 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).
|
