Release Notes: J-Web Application Package Release 15.1A4 for Juniper Networks EX Series Ethernet Switches
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 newly re-designed J-Web interface. For information about the CLI, see CLI User Interface Overview.
Supported EX Series Switches
In J-Web Application package Release 15.1A4, the J-Web interface supports EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, and EX6200 switches.
You cannot connect to and perform initial configuration of EX2200-24T-4G-DC switches by using the EZSetup procedure from the J-Web interface. For EX2200-24T-4G-DC switches, you must use EZSetup from the switch console.
New Features for J-Web
New Distribution Model
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.
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.
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.
For information about installing the Application package, see Upgrading to J-Web Application Package.
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.
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.
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, both the Platform package and Application package details are displayed.
If your current J-Web package is:
Then you can:
Upgrade to the Application 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.
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 1 illustrates examples of release compatibility.
Table 1: J-Web Release Compatibility Matrix
Junos OS Release
Associated J-Web Application Package Release
Application package 14.1X53-A1
Application package 14.1X53-A2
Application package 15.1A1
15.1R2,15.1R3, 15.1R4-S5, and so on
Application package 15.1A4
Note: You cannot install J-Web Application package 15.1A4 on Junos OS Release 15.1R1.
Any available later version of the Application package for a Junos OS release supersedes the earlier version. We recommend that you install the latest available version of the Application package.
What’s New in J-Web Application Package Release 15.1A4
In the J-Web Application package Release 15.1A4, you can set the interface description in the Configure > Interfaces page and commit the configuration to view the description.
The J-Web auto update feature automatically checks the Juniper Networks server for the latest update of the Application package each time you log in to J-Web. You can choose for J-Web to download the latest update and install it on your switch. Alternately, you can download it to your computer or remote server and install it on your switch.
For information about installation, see Table 2.
The J-Web manual update feature enables you to manually check the Juniper Network server for the latest update of the Application package. by using the J-Web interface. You can choose for J-Web to download the latest update and install it on your switch, or you can download it to your computer or remote server and install it on your switch.
For information about installation, see Table 2.
You can use the auto update and manual update features in the following scenarios:
When your switch has the Platform package installed and does not have the Application package, you can upgrade to the Application package.
When your switch has an earlier version Application package installed, and the latest version of the Application package is available on the Juniper Networks server, you can update to the latest version of the Application package.
Upgrading to J-Web Application Package
There are three ways in which you can download and install the J-Web Application package:
There is a prescribed order for the installation tasks for updating to the Application package from an earlier version or from the Platform package. See Table 2 to determine the prescribed order of tasks for your installation.
Table 2: Installation Outline
Mode of Installation
To automatically check and install the latest version of the J-Web Application package:
To manually check and install the latest J-Web Application package:
To access the J-Web interface for the switch, your management device requires the following software:
Supported browsers— Microsoft Internet Explorer versions 9 or 10, Mozilla Firefox version 24 through 38, and Google Chrome version 27 through 43.
We recommended a screen resolution of 1440 X 900 pixels.
Language support—English-version browsers
This section lists the known limitations in J-Web:
For EX Series switches, in the J-Web interface, the username field on the Login screen does not accept HTML tags or the
< and >characters. The following error message appears: A username cannot include certain characters, including < and >.
When you use an HTTPS connection in the Microsoft Internet Explorer browser to save a report from certain pages in the J-Web interface, the error message Internet Explorer was not able to open the Internet site is displayed. This problem occurs because the
Cache-Control: no cache HTTP headeris added on the server side, and Internet Explorer does not allow you to download the encrypted file with the
Cache-Control: no cache HTTP headerset in the response from the server.
As a workaround, refer to Microsoft Knowledge Base article 323308, which is available at http://support.microsoft.com/kb/323308. Alternatively, use HTTP in the Internet Explorer browser or use HTTPS in the Mozilla Firefox browser to save a file from one of these pages.
This section lists the limitations in J-Web Application package Release 15.1A4.
When you commit your configuration changes to the switch in the Configure > Interfaces > Ports page, the confirmation description is not displayed, though the configuration is committed.
When you try to commit your changes to the switch from your laptop by using the EZsetup procedure, the status of the commit operation is displayed as Success, even if the laptop is disconnected from the switch.
Workaround: Reconnect your laptop to the switch and commit the changes again.
In the Monitor > Interface page, the background color of the graph changes after refresh.
Workaround: Not required as it will not affect any functionality.
J-Web software does not compare for appropriateness of the Application package or restrict you from installing inappropriate Application package on top of a Platform or Application package.
Workaround: Install the appropriate J-Web package.
The J-Web interface does not display CLI generated certificates in the Certificate section in the Management Access Configuration page (Configure > System Properties > Management Access). Using J-Web interface you cannot create or edit certificates.
Workaround: Use the CLI interface for accessing certificate related configurations.
If you uninstall the J-Web Platform package by using CLI, reinstalling the Application package will not restore J-Web.
Workaround: Reinstall Junos OS software.
On an EX3300 switch, if you use the J-Web user interface to request support information for all members at the same time, the switch might not be able to retrieve the information.
Workaround: Request support information for each member one at a time.
On EX4300 switches, the structured data format for system log messages is not supported in the J-Web interface. If system log messages are configured to be written in structured data, the event logs in J-Web will not be populated, and you will not be able to view them using Monitor > Events and Alarms > View Events.
Workaround: Use the show log operational mode command for viewing structured-data format files.
In the J-Web interface, the Ethernet Switching Monitor page (Monitor > Switching > Ethernet Switching) might not display monitoring details if the switch has more than 13,000 MAC entries. This is a known software limitation.
In the J-Web interface for EX4500 switches, the Ports Configuration page (Configure > Interfaces > Ports), the Port Security Configuration page (Configure > Security > Port Security), and the Filters Configuration page (Configure > Security > Filters) display features that are not supported on EX4500 switches. This is a known software limitation.
The J-Web interface does not support role-based access control; it supports only users in the super-user authorization class. So a user who is not in the super-user class, such as a user with view-only permission, is able to launch the J-Web interface and is allowed to configure everything, but the configuration fails on the switch, and the switch displays access permission errors. This is a known software limitation.
In mixed EX4200 and EX4500 Virtual Chassis, the J-Web interface does not list the features supported by the backup or linecard members . Instead, it lists only the features supported by the master. This is a known software limitation.
If a Virtual Chassis contains more than six members, the Support Information page (Maintain > Customer Support > Support information) might not load. This is a known software limitation.
This section lists the resolved issues in J-Web Application package Release 15.1A4.
When you set the interface description in the Configure > Interfaces page, the description is not displayed, though the configuration is committed.
This issue has been resolved.
In EX4200, in the J-Web, interface list is not available under Configure>Security>Port security after port security is configured.
This issue has been resolved.
In EX2200, using J-Web we cannot add VLAN with ID outside 1-1024 range.
This issue has been resolved.