Juniper J-Web Application Package User Manual
J-Web Application Package for EX Series
Published
2021-03-02
Ethernet Switches
J-Web Application Package User Guide for
EX Series Switches
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks
are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right
to change, modify, transfer, or otherwise revise this publication without notice.
J-Web Application Package for EX Series Ethernet Switches J-Web Application Package User Guide for EX Series Switches
Copyright © 2021 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
ii
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
Table of Contents
1
About the Documentation | x
Documentation and Release Notes | x
Using the Examples in This Manual | x
Merging a Full Example | xi
Merging a Snippet | xii
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Self-Help Online Tools and Resources | xvi
Creating a Service Request with JTAC | xvi
iii
Overview
Overview | 2
J-Web User Interface for EX Series Switches Overview | 2
J-Web Packages | 2
Release Compatibility | 4
Software Requirements | 5
J-Web Interface—Application Package | 6
J-Web Application Package—First Look | 6
Understanding J-Web User Interface Sessions | 9
Dashboard for EX Series Switches | 10
Graphical Chassis Viewer | 11
System Information Panel | 13
Health Status Panel | 16
Capacity Utilization Panel | 20
Alarms Panel | 20
File System Usage | 21
Chassis Viewer | 21
Understanding J-Web Configuration Tools | 37
Understand Alarm Types and Severity Levels on EX Series Switches | 39
Using the Commit Options to Commit Configuration Changes (J-Web Procedure) | 40
Configuration
2
Starting J-Web | 45
Starting the J-Web Interface | 45
J-Web Configuration Tools | 47
Using the Point and Click CLI Tool in the J-Web Interface to Edit Configuration Text | 47
Using the CLI Editor in the J-Web Interface to Edit Configuration Text | 49
Using the J-Web CLI Terminal | 50
Configuring the Web Browser | 50
Setting Domain Name, Hostname, and Name Server | 51
Enabling SSH on your system | 51
Sample Configuration on an EX Series Switch | 52
Using the CLI Viewer in the J-Web Interface to View Configuration Text | 53
iv
System Basics Configuration | 54
Connecting and Configuring an EX Series Switch (J-Web Procedure) | 54
Configuring Date and Time for the EX Series Switch (J-Web Procedure) | 59
Configuring System Identity for an EX Series Switch (J-Web Procedure) | 60
Configuring Management Access for the EX Series Switch (J-Web Procedure) | 61
Generating SSL Certificates to Be Used for Secure Web Access (EX Series Switch) | 66
Rebooting or Halting the EX Series Switch (J-Web Procedure) | 67
Class of Service Configuration | 68
Defining CoS Drop Profiles (J-Web Procedure) | 68
Defining CoS Classifiers (J-Web Procedure) | 70
Defining CoS Code-Point Aliases (J-Web Procedure) | 72
Assigning CoS Components to Interfaces (J-Web Procedure) | 73
Defining CoS Forwarding Classes (J-Web Procedure) | 75
Defining CoS Rewrite Rules (J-Web Procedure) | 78
Defining CoS Schedulers (J-Web Procedure) | 80
Defining CoS Scheduler Maps (J-Web Procedure) | 83
Security and Management Configuration | 85
Configuring 802.1X Authentication (J-Web Procedure) | 85
Configuring LLDP (J-Web Procedure) | 88
Configuring Port Mirroring to Analyze Traffic (J-Web Procedure) | 90
Configuring Port Security (J-Web Procedure) | 93
Routing Policies and Packet Filtering Configuration | 98
Configuring Routing Policies (J-Web Procedure) | 98
Configuring Firewall Filters (J-Web Procedure) | 105
Ethernet Switching Configuration | 112
Configuring VLANs for EX Series Switches (J-Web Procedure) | 112
Configuring Spanning Tree Protocols on EX Series Switches (J-Web Procedure) | 115
Configuring IGMP Snooping on EX Series Switches (J-Web Procedure) | 121
v
Configuring Redundant Trunk Groups on EX Series Switches (J-Web Procedure) | 124
Interfaces | 126
Configuring Gigabit Ethernet Interfaces (J-Web Procedure) | 126
Configuring Aggregated Ethernet Interfaces (J-Web Procedure) | 134
Configuring PoE (J-Web Procedure) | 139
Configuring PoE on EX2200, EX2200-C, EX3200, EX3300, EX4200, and EX4300 Switches | 139
Configuring PoE on EX6200 Switches | 141
Configuring Services | 143
Configuring DHCP Services (J-Web Procedure) | 143
Configuring DHCP Services (J-Web Procedure) on EX Series Switches | 143
Configuring DHCP Services on EX4300 Switches (J-Web Procedure) | 147
Configuring SNMP (J-Web Procedure) | 153
Configuring Layer 3 Protocols | 158
Configuring BGP Sessions (J-Web Procedure) | 158
Configuring an OSPF Network (J-Web Procedure) | 164
Configuring a RIP Network for EX Series Switches (J-Web Procedure) | 171
Configuring Static Routing (J-Web Procedure) | 175
Configuring Real-Time Performance Monitoring | 178
Configuring Real-Time Performance Monitoring (J-Web Procedure) | 178
Viewing Real-Time Performance Monitoring Information | 186
Software Installation and Upgrades | 187
Updating J-Web Interface on EX Series Switches (J-Web Procedure) | 187
Installing J-Web Application Package by Using Auto Update | 187
Installing J-Web Application Package by Using Manual Update | 188
Upgrading Junos OS on EX Series Switches (J-Web Procedure) | 189
Installing Junos OS Upgrades from a Remote Server | 190
Installing Junos OS Upgrades by Uploading File from Local Computer | 191
Configuration, Files, Users, Licenses, and Product Registration | 192
Managing Configuration Files Through the Configuration History (J-Web Procedure) | 192
vi
Displaying Configuration History | 193
Displaying Users Editing the Configuration | 194
Comparing Configuration Files with the J-Web Interface | 194
Downloading a Configuration File with the J-Web Interface | 195
Loading a Previous Configuration File with the J-Web Interface | 195
Setting or Deleting the Rescue Configuration (J-Web Procedure) | 196
Uploading a Configuration File (J-Web Procedure) | 196
Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) | 197
Cleaning Up Files | 197
Downloading Files | 198
Deleting Files | 199
Managing Users (J-Web Procedure) | 200
Managing Licenses for the EX Series Switch (J-Web Procedure) | 202
Adding New Licenses | 203
Deleting Licenses | 203
Displaying License Keys | 204
Downloading Licenses | 204
Registering the EX Series Switch with the J-Web Interface | 204
Generating Support Information Reports for EX Series Switches Using the J-Web Interface | 205
Virtual Chassis Configuration | 206
3
Configuring a Virtual Chassis on an EX Series Switch (J-Web Procedure) | 206
Configuring an EX2200, EX2200-C, EX3300, EX4200, EX4300, EX4500, EX4550, or EX4600
Virtual Chassis (J-Web Procedure) | 206
Enabling Virtual Chassis Mode on an EX8200 Switch (J-Web Procedure) | 208
Configuring an EX8200 Virtual Chassis (J-Web Procedure) | 209
Preprovision the Virtual Chassis | 209
Configure Virtual Chassis Members | 209
Configure Virtual Chassis Ports | 210
Monitoring
Monitoring Tasks | 213
Check Active Alarms with the J-Web Interface | 214
Monitor System Log Messages | 215
vii
Monitoring Chassis Information | 220
Monitoring System Properties | 223
Monitoring System Process Information | 225
Monitoring Switch Control Traffic | 226
Monitoring Interface Status and Traffic | 229
Monitoring PoE | 231
Monitoring Hosts Using the J-Web Ping Host Tool | 232
Monitoring Network Traffic Using Traceroute | 235
Monitoring DHCP Services | 237
Monitoring OSPF Routing Information | 243
Monitoring RIP Routing Information | 246
Monitoring BGP Routing Information | 248
Monitoring Routing Information | 250
Monitoring Ethernet Switching on EX Series Switches (J-Web) | 253
Monitoring IGMP Snooping | 256
Monitoring Spanning Tree Protocols on Switches | 259
Monitoring CoS Classifiers | 261
Monitoring CoS Drop Profiles | 263
Monitoring CoS Value Aliases | 264
Monitoring CoS Forwarding Classes | 266
Monitoring Interfaces That Have CoS Components | 268
4
Monitoring CoS Rewrite Rules | 270
Monitoring CoS Scheduler Maps | 271
Monitoring the Virtual Chassis Status and Statistics on EX Series Virtual Chassis | 274
Monitoring 802.1X Authentication | 276
Monitoring Port Security | 277
Administration
Software, Files, Licenses, Logs | 280
Uploading a Configuration File (J-Web Procedure) | 280
Managing Configuration Files Through the Configuration History (J-Web Procedure) | 281
Displaying Configuration History | 281
Displaying Users Editing the Configuration | 282
Comparing Configuration Files with the J-Web Interface | 283
viii
Downloading a Configuration File with the J-Web Interface | 284
Loading a Previous Configuration File with the J-Web Interface | 284
Setting or Deleting the Rescue Configuration (J-Web Procedure) | 285
Updating J-Web Interface on EX Series Switches (J-Web Procedure) | 285
Installing J-Web Application Package by Using Auto Update | 286
Installing J-Web Application Package by Using Manual Update | 287
Upgrading Junos OS on EX Series Switches (J-Web Procedure) | 288
Installing Junos OS Upgrades from a Remote Server | 288
Installing Junos OS Upgrades by Uploading File from Local Computer | 289
Managing Licenses for the EX Series Switch (J-Web Procedure) | 290
Adding New Licenses | 291
Deleting Licenses | 291
Displaying License Keys | 291
Downloading Licenses | 292
Rebooting or Halting the EX Series Switch (J-Web Procedure) | 292
Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure) | 293
Cleaning Up Files | 293
Downloading Files | 294
Deleting Files | 294
Registering the EX Series Switch with the J-Web Interface | 296
Generating Support Information Reports for EX Series Switches Using the J-Web Interface | 296
5
Troubleshooting
Troubleshooting Task | 299
Troubleshooting Interface Configuration and Cable Faults | 299
Interface Configuration or Connectivity Is Not Working | 299
ix
About the Documentation
IN THIS SECTION
Documentation and Release Notes | x
Using the Examples in This Manual | x
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Use this guide to configure, monitor, and troubleshoot your EX Series switch using the J-Web Application
package. The J-Web Application package provides complete features of J-Web and is an installable package.
x
Junos®OS for EX Series Ethernet Switches
•
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation, see the product
documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.
If the information in the latest release notes differs from the information in the documentation, follow the
product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts.
These books go beyond the technical documentation to explore the nuances of network architecture,
deployment, and administration. The current list can be viewed at https://www.juniper.net/books.
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative
command. These commands cause the software to merge the incoming configuration into the current
candidate configuration. The example does not become active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example
is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In
this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf. Copy the
ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
xi
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the
ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode
command:
[edit]
user@host# edit system scripts
[edit system scripts]
xii
3. Merge the contents of the file into your routing platform configuration by issuing the load merge
relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xiii defines notice icons used in this guide.
Table 1: Notice Icons
xiii
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xiii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
Fixed-width text like this
Italic text like this
Represents text that you type.Bold text like this
Represents output that appears on
the terminal screen.
Introduces or emphasizes important
•
new terms.
Identifies guide names.
•
Identifies RFC and Internet draft
•
titles.
To enter configuration mode, type
the configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
•
that defines match conditions and
actions.
Junos OS CLI User Guide
•
RFC 1997, BGP Communities
•
Attribute
Table 2: Text and Syntax Conventions (continued)
xiv
ExamplesDescriptionConvention
Italic text like this
Text like this
< > (angle brackets)
| (pipe symbol)
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
variables.
Indicates a choice between the
mutually exclusive keywords or
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
To configure a stub area, include
•
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
The console port is labeled
•
CONSOLE.
stub <default-metric metric>;Encloses optional keywords or
broadcast | multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
rsvp { # Required for dynamic MPLS
only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Table 2: Text and Syntax Conventions (continued)
xv
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You can use either
of the following methods:
Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper
•
Networks TechLibrary site, and do one of the following:
Click the thumbs-up icon if the information on the page was helpful to you.
•
Click the thumbs-down icon if the information on the page was not helpful to you or if you have
•
suggestions for improvement, and use the pop-up form to provide feedback.
E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
Product warranties—For product warranty information, visit https://www.juniper.net/support/warranty/.
•
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week,
•
365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
Find CSC offerings: https://www.juniper.net/customers/support/
•
Search for known bugs: https://prsearch.juniper.net/
•
xvi
Find product documentation: https://www.juniper.net/documentation/
•
Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
•
Download the latest versions of software and review release notes:
•
https://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:
•
https://kb.juniper.net/InfoCenter/
Join and participate in the Juniper Networks Community Forum:
•
https://www.juniper.net/company/communities/
Create a service request online: https://myjuniper.juniper.net
•
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool:
https://entitlementsearch.juniper.net/entitlementsearch/
Creating a Service Request with JTAC
You can create a service request with JTAC on the Web or by telephone.
Visit https://myjuniper.juniper.net.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
•
For international or direct-dial options in countries without toll-free numbers, see
https://support.juniper.net/support/requesting-support/.
1
PART
Overview
Overview | 2
CHAPTER 1
Overview
IN THIS CHAPTER
J-Web User Interface for EX Series Switches Overview | 2
J-Web Interface—Application Package | 6
Understanding J-Web User Interface Sessions | 9
Dashboard for EX Series Switches | 10
Understanding J-Web Configuration Tools | 37
Understand Alarm Types and Severity Levels on EX Series Switches | 39
Using the Commit Options to Commit Configuration Changes (J-Web Procedure) | 40
2
J-Web User Interface for EX Series Switches Overview
Juniper Networks EX Series Ethernet Switches are shipped with the Juniper Networks Junos operating
system (Junos OS) installed.
Junos OS has the following primary user interfaces:
Juniper Web Device Manager (J-Web) GUI
•
Junos OS CLI
•
You can use these interfaces to access, configure, and manage your EX Series switch.
This topic provides an overview of the J-Web interface. For information about the CLI, see CLI User Interface
Overview.
J-Web Packages
For Junos OS Release 14.1X53-D10 and later, the J-Web interface is available in two packages:
Platform package—Provides basic features of J-Web and is installed as part of Junos OS.
•
Application package—Provides complete features of J-Web and is an installable package.
•
Platform Package
The Platform package of J-Web is installed as part of Junos OS that is shipped with your EX Series
switch. The Platform package provides the basic features of the J-Web interface. The Platform package
enables you to configure and maintain your switch.
Application Package
The Application package is not installed by default on your switch. You must download it and install it
over the Platform package on your switch. The Application package provides all the features of the
J-Web interface that enable you to configure, monitor, maintain, and troubleshoot your switch.
The Platform package, which is installed as part of the Junos OS that is shipped with your switch, follows
the Junos OS release cycle. However, the Application packages have their own release cycle which is
independent of the Junos OS release cycle. This separate release cycle helps you get the latest features
of J-Web by installing the latest version of the Application package, without waiting for Junos OS releases.
NOTE: The J-Web Application package is hot-pluggable. You can install it on top of the current
Junos OS installation, and you need not reboot the switch after the installation.
3
NOTE: To determine which J-Web package you are currently using, click Help > About. The
About window appears. If you are using a Platform package, only the Platform package details
are displayed. If you are using an Application package, then the Platform package and Application
package details are displayed.
If your current J-Web
package is:
Application package
Then you can:
Upgrade to the Application package.Platform package
Update to a latest version of the Application package available on the Juniper
Networks server that is compatible with the Junos OS on your switch.
NOTE: If you upgrade Junos OS on your switch, the current J-Web package is
replaced with the J-Web Platform package that is associated with the upgraded
Junos OS release. You can then install the latest Application package that is associated
with the main release of the upgraded Junos OS, over the Platform package.
Release Compatibility
The Application packages of J-Web have their own release cycles (A1, A2, A3, and so on), which are
independent of the Junos OS release cycle. An Application package is compatible only with the
corresponding major release of Junos OS.
The Table 3 on page 4 illustrates the example of the release compatibility.
Table 3: J-Web Release Compatibility Matrix
Associated J-Web Application Package ReleaseJunos OS Release
Application package 14.1X53-A114.1X53-D10
Application package 14.1X53-A214.1X53-D35
Application package 15.1A115.1R1
4
15.1R3
Application package 15.1A2
NOTE: Application package 15.1A2 cannot be installed on Junos OS Release
15.1R1.
Application package 15.1A3 (if applicable)
16.1A116.1R1
Application package 17.1A117.1R1
Application package 17.2A117.2R1
Application package 17.3A117.3R1
Application package 15.1X53-A215.1X53-D57
Application package 17.4A117.4R1
Application package 18.1A118.1R1
Application package 18.1A218.1R2
Application package 18.2A118.2R1
Application package 18.3A118.3R1
Application package 18.4A118.4R1
Any available later version of the Application package for a Junos OS release supersedes the earlier version.
Thus, if Application package version 15.1A2 is available for 15.1R1, it will supersede version 15.1A1. We
recommend that you install the latest available version of the Application package.
Software Requirements
To access the J-Web interface, your management device requires the following software:
Supported browsers—Microsoft Internet Explorer version 9 or 10, Mozilla Firefox version 24 through
•
30, and Google Chrome version 27 through 36.
TIP: For best viewing of the J-Web user interface, set the screen resolution to 1440 X 900
pixels.
NOTE: Other browser versions might not work on the switch. The browser and the network
must support receiving and processing HTTP 1.1 GZIP compressed data.
5
Language support—English-version browsers
•
Release History Table
DescriptionRelease
Application package 15.1A2 cannot be installed on Junos OS Release 15.1R1.15.1R1
14.1X53-D10
For Junos OS Release 14.1X53-D10 and later, the J-Web interface is available in
two packages
RELATED DOCUMENTATION
FAQ: J-Web Application Package on EX Series Switches
EX Series Switch Software Features Overview
CLI User Interface Overview
J-Web Interface—Application Package
NOTE: This topic applies only to the J-Web Application package.
With the J-Web Application package, you can:
Get a high-level, graphical view of the chassis and the status of the switch, such as the system health
•
information, alarms, or system status.
Configure the switch, and view the configuration history.
•
Monitor the switch by viewing information about configuration and hardware on the switch such as
•
events, alarms, security, and routing options.
Maintain the switch by updating the J-Web interface, upgrading Junos OS, uploading configurations,
•
managing licenses and files, or rebooting the switch.
6
NOTE: Juniper Networks devices require a license to activate the feature. Refer to the Licensing
Guide for general information about License Management: Licenses for Network Management.
To understand more about managing licences through J-Web, see “Managing Licenses for the
EX Series Switch (J-Web Procedure)” on page 202.
Troubleshoot network issues by running diagnostic tools. Troubleshoot interface configuration and faults
•
by using ping, traceroute, or packet capture, or by using the CLI terminal.
J-Web Application Package—First Look
Each page of the J-Web interface is divided into panes.
Top pane—It is located at the top of the page. It displays the J-Web logo and hostname, tasks–Configure,
•
Monitor, and Maintain, Commit, Update Available logo (if available), and username and Help.
Side pane—It is located on the left side of the page. It displays suboptions of the tasks–Monitor, Configure,
•
or Maintain– currently selected in the top pane. Click a suboption to access it in the work area.
Work area—This is the main work area of the J-Web interface, located below the top pane and to the
•
right of the side pane. It displays various text boxes, selection boxes, buttons and other options
corresponding to the suboption that you select in the side pane. It is the location where you monitor,
configure, and manage (maintain) the switch.
The layout of the panes enables you to quickly navigate through the interface. Table 4 on page 7
summarizes the elements of the J-Web interface.
The J-Web interface provides CLI tools that enable you to perform all of the tasks that you can perform
from the Junos OS CLI, including a CLI Viewer to view the current configuration, a CLI Editor for viewing
and modifying the configuration, and a Point & Click CLI editor that enables you to click through all of the
available CLI statements.
Table 4: J-Web Application Package Interface Elements
DescriptionElement
Top Pane
The J-Web logo and hostname of the switch.J-Web
Hostname
7
Taskbar
Menu that displays the main options. Click the tab to access an option.
Configure—Configure the switch, and view the configuration history.
•
Monitor—View information about configuration and hardware on the switch
•
such as events, alarms, security, and routing options.
Maintain—Update the J-Web interface, upgrade Junos OS, upload
•
configurations, manage licenses and files, and reboot the switch.
Troubleshoot—Run diagnostic tools to troubleshoot network issues.
•
Troubleshoot interface configuration and faults by using ping, traceroute, or
packet capture, or by using the CLI terminal.
Table 4: J-Web Application Package Interface Elements (continued)
DescriptionElement
8
Commit Options
A set of options using which you can configure committing multiple changes
with a single commit.
Commit—Commits the candidate configuration of the current user session,
•
along with changes from other user sessions.
Compare—Displays the XML log of pending configurations on the device.
•
Discard—Discards the candidate configuration of the current user session,
•
along with changes from other user sessions.
Preference—Indicates your choice of committing all configurations changes
•
together or committing each configuration change immediately. The two
commit options are:
Validate configuration changes—Loads all configuration changes for an
•
accumulated single commit. If there are errors in loading the configuration,
the errors are logged. This is the default mode.
Validate and commit configuration changes—Sets the system to force an
•
immediate commit on every page after every configuration change.
NOTE: There are some pages on which configuration changes must be
committed immediately. For such pages, if you configure the commit options
for a single commit, the system displays warning notifications that remind
you to commit your changes immediately. An example of such a page is the
Ports page (Configure > Interfaces > Ports).
Update Available
username
Help
This icon message appears only if there is a J-Web Application package update
available on the Juniper Networks server.
Mouse over the icon to know the latest version of J-Web Application package
available on the Juniper Networks server. Click on the icon to update the J-Web
Application package.
The username you used to log in to the switch.
The down arrow option displays the Logout option. Logout ends your current
session and returns you to the login page.
Displays links to help topics and information about the J-Web interface.
Help Contents—Provides context-sensitive help topics.
•
About—Displays information about the J-Web interface, such as the version
•
number.
Table 4: J-Web Application Package Interface Elements (continued)
DescriptionElement
9
Icon legend
Work Area
Configuration hierarchy
(Applies to the Point & Click CLI editor only) Explains icons that appear in the
user interface to provide information about configuration statements:
C—Comment. Mouse over the icon to view a comment about the configuration
•
statement.
I—Inactive. The configuration statement does not apply for the switch.
•
M—Modified. The configuration statement has been added or modified.
•
*—Mandatory. The configuration statement must have a value.
•
(Applies to the Junos OS CLI configuration editor only) Displays the hierarchy
of committed statements in the switch configuration.
Click Expand all to display the entire hierarchy.
•
Click Hide all to display only the statements at the top level.
•
Click + to expand individual items.
•
Click - to hide individual items.
•
RELATED DOCUMENTATION
Using the Commit Options to Commit Configuration Changes (J-Web Procedure) | 40
EX Series Switch Software Features Overview
Connecting and Configuring an EX Series Switch (J-Web Procedure) | 54
CLI User Interface Overview
Understanding J-Web User Interface Sessions
You establish a J-Web session with the switch through an HTTP-enabled or HTTPS-enabled Web browser.
To use HTTPS, you must have installed a certificate on the switch and enabled HTTPS. See Generating SSL
Certificates to Be Used for Secure Web Access (EX Series Switch).
When you attempt to log in through the J-Web interface, the switch authenticates your username with
the same methods used for Telnet and SSH.
If the switch does not detect any activity through the J-Web interface for 15 minutes, the session times
out and is terminated. You must log in again to begin a new session.
To explicitly terminate a J-Web session at any time, click Logout in the top pane.
RELATED DOCUMENTATION
J-Web User Interface for EX Series Switches Overview | 2
Configuring Management Access for the EX Series Switch (J-Web Procedure) | 61
Dashboard for EX Series Switches
IN THIS SECTION
10
Graphical Chassis Viewer | 11
System Information Panel | 13
Health Status Panel | 16
Capacity Utilization Panel | 20
Alarms Panel | 20
File System Usage | 21
Chassis Viewer | 21
NOTE: This topic applies only to the J-Web Application package.
When you log in to the J-Web user interface, the dashboard for the Juniper Networks EX Series Ethernet
Switches appears. Use the dashboard to view system information.
The Update Available window appears if there is a latest update of the J-Web Application package available
on the Juniper Networks server. This window is enabled by the auto update feature of J-Web.
NOTE:
The Update Available window will not appear when you log in, if you have not selected the
•
Check for updates automatically on every login in the Update Preference section in the Maintain
> Update J-Web side pane. By default, the Check for update automatically on every login is
selected.
If you choose Update Later, you can update to the latest J-Web Application package by clicking
•
the orange icon next to Update Available on the top pane of the J-Web interface or through
Maintain > Update J-Web.
The dashboard comprises a graphical chassis viewer and four panels.
Graphical Chassis Viewer
The Dashboard panel displays a graphical view of the chassis of a switch. In a Virtual Chassis, it displays
a graphical view of each member switch.
11
In a Virtual Chassis, the default values are shown on the Dashboard panel when no chassis image is clicked.
The panel displays the value for a switch if you click its image.
NOTE:
If the member switch is not present, inactive, or not provisioned, you cannot expand the
•
member switch image.
In J-Web Application package Release 14.1X53-A2, you can form a Virtual Chassis using
EX4600 and EX4300 switches. When in a mixed Virtual Chassis consisting of EX4600 switches
and EX4300 switches, the EX4600 switches can be the primary, backup, or in the linecard role,
while the EX4300 switches must be in the linecard role.
Starting in J-Web Application Package Release 19.2A1, J-Web supports EX4650 switches.
•
NOTE: For EX4650 switches, chassis viewer supports only the standalone view and
does not support the Virtual Chassis configuration.
Table 5 on page 12 lists the details that are displayed on each member switch.
Table 5: Details of a Virtual Chassis Member Switch
ExampleDetails
EX3300Model number of the member switch
12
Assigned ID that applies to the entire Virtual Chassis
configuration
Role of the member switch
Status of the member switch
ID 2
NOTE: If the member switch is not provisioned, the serial
number of the switch is displayed instead of its ID.
Master
Possible roles are: Master, Backup, or Linecard
Prsnt
Possible statuses are: Prsnt, NotPrsnt, Inactive, or Unprvsnd
The status of the member switch is displayed on the image of the switch. If the member switch appears
dimmed, it means the switch is not present, is inactive, or is not provisioned in the Virtual Chassis. If the
member switch does not appear dimmed, it means the switch is present and is active.
Table 6 on page 12 describes the possible status of a member switch.
Table 6: Status of a Member Switch in a Virtual Chassis
It means the member switchIt appears asIf the member switch is
Has established physical and logical connections with
Virtual Chassis member switches.
Has been disconnected from the existing Virtual Chassis.dimmed and
Has established physical connections, but is unable to
establish logical connections.
Cannot synchronize with the existing preprovisioned Virtual
Chassis.
Not present
Inactive
Not provisioned
PrsntPresent
NotPrsnt
dimmed and
Inactive
dimmed and
Unprvsnd
Click Rear View for a graphical view of the rear panel of the switch.
Click Preferences to choose which panels must be displayed and set the refresh interval for chassis viewer
information. Click OK to save your changes and return to the dashboard or click Cancel to return to the
dashboard without saving changes.
NOTE: You can drag the various panels to different locations in the J-Web window.
System Information Panel
Table 7: System Information
DescriptionField
13
System name
Device model
Indicates the local name of the EX Series switch. The local
name of the EX Series switches changes when an individual
image is clicked.
For EX4650 switches, indicates the host name of the
switch. Specific host name of the EX4650 switch is
displayed when you click on the individual line card.
Indicates the model of the EX Series switch. In a Virtual
Chassis configuration, to indicate the model of a switch,
click the image of that switch.
NOTE: In a Virtual Chassis setup for an EX6210, EX8208,
or EX8216 switch, the Device model field displays details
of the primary Routing Engine. To view details of a
member, select it.
By default, the EX4650 switches show the model of the
primary switch. When you click on the image, the model
of the switch is displayed.
Table 7: System Information (continued)
Inventory details
14
DescriptionField
Loading...