User Interface Overview

This section contains the following topics:

• J-Web Overview
• CLI Overview

You can operate the device either in secure or router context. With the J-Web interface and the command-line interface (CLI), you configure the routing protocols that run on the device, and the device security features, including stateful firewall policies, Network Address Translation (NAT) attack prevention screens, Application Layer Gateways (ALGs), and IPSec VPNs. You also set the properties of its network interfaces. After activating a software configuration, you can use either user interface to monitor the system and the protocol traffic passing through the device, manage operations, and diagnose protocol and network connectivity problems.

For information about secure and router contexts, see Understanding Secure and Router Contexts.

J-Web Overview

The J-Web interface allows you to monitor, configure, troubleshoot, and manage your device by means of a Web browser enabled with Hypertext Transfer Protocol (HTTP) or HTTP over Secure Sockets Layer (HTTPS). J-Web provides access to all the configuration statements supported by the device, so you can fully configure it without using the CLI editor.

You can perform the following tasks with the J-Web interface:

• Dashboard (SRX Series devices only) — Displays a high-level details of Chassis View, system identification, resource utilization, security resources, system alarms, file usage, login sessions, chassis status, and storage usage.
• Monitoring — Displays the current configuration and information about the system, interfaces, chassis, routing protocols, routing tables, routing policy filters, and other features.
• Configuring — View the current configurations at a glance, configure the device, and manage configuration files. The J-Web interface provides the following different configuration methods:
  • Configure the device quickly and easily without configuring each statement individually.
  • Edit a graphical version of the JUNOS Software CLI configuration statements and hierarchy.
  • Edit the configuration in a text file.
  • Upload a configuration file.

  The J-Web interface also allows you to manage configuration history and set a rescue configuration.

• Diagnosing—Diagnose routing problems by running the ping or traceroute diagnostic tool. The diagnostic tools also allow you to capture and analyze control traffic on the devices.
• Managing — Manage log, temporary, and core (crash) files and schedule reboots on your devices. You can also manage software packages and licenses and copy a snapshot of the system software to a backup device.
• Configuring and monitoring events — Filter and view system log messages that record events occurring on the device. You can configure files to log system log messages and also assign attributes, such as severity levels, to messages.
• Configuring and monitoring alarms —Monitor and diagnose the device by monitoring active alarms that alert you to the conditions on a network interface. You can also set the conditions that trigger alarms on an interface.

For more information about the J-Web interface, see Using the J-Web Interface.

CLI Overview

The CLI is a straightforward command interface in which you type commands on a line and press Enter to execute them. The CLI provides command Help, command completion, and Emacs-style keyboard sequences for moving around on the command line and scrolling through a buffer of recently executed commands.

The CLI has two modes:

• Operational mode—Complete set of commands to control the CLI environment, monitor and troubleshoot network connectivity, manage the device, and enter configuration mode.
• Configuration mode—Complete set of commands to configure the device. This guide refers to configuration mode as the CLI configuration editor.

For more information about the CLI, see Using the Command-Line Interface.