Point and Click CLI (J-Web Configuration Editor)
Using Point and Click CLI, you can configure all properties of the Junos OS, including interfaces, general routing information, routing protocols, and user access, as well as several system hardware properties.
The configuration is stored as a hierarchy of statements. You create the specific hierarchy of configuration statements that you want to use. After you finish entering the configuration statements, you commit them to activate the configuration on the routing platform.
You can create the hierarchy interactively, or you can create an ASCII text file that is loaded onto the routing platform and then committed. Edit Configuration (J-Web configuration editor) allows you to create the hierarchy interactively, and Edit Configuration Text allows you to create and commit statements as an ASCII text file.
To access Edit Configuration, also called the J-Web configuration editor, select Configure>CLI Tools>Point and Click. This page allows you to configure all routing platform services that you can configure from the Junos OS CLI. Each field in the J-Web configuration editor has the same name as the corresponding configuration statement at the same hierarchy level in the CLI. For example, the Policy Options field corresponds to the policy-options statement in the CLI. As a result, you can easily switch from one interface to the other or follow a CLI configuration example using the J-Web configuration editor.
Table 1 lists key J-Web configuration editor tasks and their functions.
Table 1: J-Web Configuration Editor Tasks Summary
| J-Web Configuration Editor Task | Function |
|---|---|
Access | Configure network access. For example, you can configure the Point-to-Point Protocol (PPP), the tracing access processes, the Layer 2 Tunneling Protocol (L2TP), RADIUS authentication for L2TP, and Internet Key Exchange (IKE) access profiles. For more information, see the Junos OS Administration Library for Routing Devices. |
Accounting options | Configure accounting profiles. An accounting profile represents common characteristics of collected accounting data, including collection interval, accounting data files, and counter names on which to collect statistics. On the Accounting options pages, you can configure multiple accounting profiles, such as the interface, filter, MIB, routing engine, and class usage profiles. For more information, see the Network Management Administration Guide for Routing Devices. |
Applications | Define applications by protocol characteristics and group the applications you have defined into a set. On the Applications pages, you can configure application properties, such as Internet Control Message Protocol (ICMP) code and type. You can also specify application protocols—also known as application-level gateways (ALGs)—to be included in an application set for service processing, or specify network protocols to match in an application definition. For more information, see the Junos OS Services Interfaces Library for Routing Devices. |
Chassis | Configure routing platform chassis properties. On the Chassis pages, you can configure different properties of the routing platform chassis, including conditions that activate the red and yellow alarm LEDs on the routing platforms and SONET/SDH framing and concatenation properties for individual Physical Interface Cards (PICs). For more information, see the Junos OS Administration Library for Routing Devices. |
Class of service | Define class-of-service (CoS) components, such as CoS value aliases, classifiers, forwarding classes, rewrite rules, schedulers, and virtual channel groups. The Class of service pages also allow you to assign CoS components to interfaces. For more information, see the Junos OS Class of Service Library for Routing Devices. |
Diameter | Configure Diameter base protocol. For example, you can specify the remote peers, the endpoint origin attributes, and network elements that associate routes with peers. For more information, see the Junos OS Subscriber Management and Services Library. |
Event options | Configure event policies. An event policy is an if-then-else construct that defines actions to be executed by the software on receipt of a system log message. For each policy, you can configure multiple actions, as follows—ignore the event, upload a file to a specified destination, execute Junos OS operational mode commands, or execute Junos OS event scripts (op scripts). For more information, see the Junos OS Automation Library. |
Firewall | Configure stateless firewall filters. With stateless firewall filters—also known as ACLs—you can control packets transiting the routing platform to a network destination and packets destined for and sent by the routing platform. On the Firewall pages, you can create filters and add terms to them. For each term, you can set the match conditions and associate actions to be performed on packets matching these conditions. For more information, see the Routing Policy Feature Guide for Routing Devices. |
Forwarding options | Configure traffic forwarding and traffic sampling options. You can sample IP traffic based on particular input interfaces and various fields in the packet header. You can also use traffic sampling to monitor any combination of specific logical interfaces, specific protocols on one or more interfaces, a range of addresses on a logical interface, or individual IP addresses. Traffic forwarding policies allow you to control the per-flow load balancing, port mirroring, and Domain Name System (DNS) or Trivial File Transfer Protocol (TFTP) forwarding. For more information, see the Routing Policy Feature Guide for Routing Devices. |
Interfaces | Configure physical and logical interface properties. For the physical interface on the routing platform, you can modify default values for general interface properties, such as the interface’s maximum transmission unit (MTU) size, link operational mode, and clock source. For each logical interface, you can specify the protocol family and other logical interface properties. For more information, see the Junos OS Network Interfaces Library for Routing Devices. |
Jsrc | Configure Jsrc. For example, you can configure the JSRC partition, associate a Diameter instance, SAE hostname, and the SAE realm with the partition. For more information, see the Junos OS Subscriber Management and Services Library. |
Policy options | Configure policies by specifying match conditions and associating actions with the conditions. On the Policy options page, you can create a named community and define autonomous system (AS) paths, damping parameters, and routing policies. You can also create a named prefix list and include it in a routing policy. For more information, see the Junos OS VPNs Library for Routing Devices. |
Protocols | Configure routing protocols such as Border Gateway Protocol (BGP), Distance Vector Multicast Routing Protocol (DVMRP), Intermediate System-to-Intermediate System (IS-IS), Multiprotocol Label Switching (MPLS), Open Shortest Path First (OSPF), Resource Reservation Protocol (RSVP) and Routing Information Protocol (RIP). For more information, see the Junos OS Routing Protocols Library for Routing Devices and the Junos OS MPLS Applications Library for Routing Devices. |
Routing instances | Configure routing instances. A routing instance is a collection of routing tables, interfaces, and routing protocol parameters. On the Routing instances pages, you can configure the following types of routing instances: forwarding, Layer 2 virtual private network (VPN), nonforwarding, VPN routing and forwarding (VRF), virtual rourter, and virtual private LAN service (VPLS). For more information, see the Junos OS Routing Protocols Library for Routing Devices. |
Routing options | Configure protocol-independent routing options that affect systemwide routing operations. On the Routing options pages, you can perform the following tasks:
For more information, see the Junos OS Routing Protocols Library for Routing Devices. |
Security | Configure Internet Protocol Security (IPsec) for authentication of origin, data integrity, confidentiality, replay protection, and nonrepudiation of source. In addition to IPsec, you can configure the Internet Key Exchange (IKE), which defines mechanisms for key generation and exchange, and manages security associations (SAs). You can also configure the SSH known host list, and the trace options for IPsec key management. For more information, see the Junos OS Administration Library for Routing Devices. |
Services | Configure application settings for services interfaces, such as dynamic flow capture parameters, the intrusion detection service (IDS), IPsec VPN service, RPM, stateful firewalls, and Network Address Translation (NAT). For more information, see the Junos OS Services Interfaces Library for Routing Devices. |
Snmp | Configure SNMP to monitor network devices from a central location. You can specify an administrative contact and location and add a description for each system being managed by SNMP. You can also configure SNMP community strings, trap options, and interfaces on which SNMP requests can be accepted. For more information, see the Network Management Administration Guide for Routing Devices. |
System | Configure system management functions, including the router’s hostname, address, and domain name; the addresses of Domain Name System (DNS) servers; user login accounts, including user authentication and the root-level user account; time zones and Network Time Protocol (NTP) properties; and properties of the router’s auxiliary and console ports. For more information, see the Junos OS Administration Library for Routing Devices. |
