ON THIS PAGE
What has changed in the distribution or packaging of J-Web for the EX Series switches?
Will the SRX Series platforms support the new J-Web distribution model?
Which EX Series switches does the new J-Web distribution model support?
How do I know whether an Application package is installed on my switch?
Do I need to reboot the switch as part an Application package installation?
Can I install Application package version 15.1X53-A1 on top of Junos OS Release 14.1X53-D10?
Can I install an Application package on top of Junos OS releases prior to Release 14.1X53?
Are there switch-specific Application package images available for EX Series switches?
Do I need Internet connectivity from the switch for the auto update feature to work?
J-Web Application Package for EX Series—Frequently Asked Questions
This FAQ addresses questions regarding J-Web distribution model for EX Series switches and upgrading the J-Web Application package. The J-Web distribution model is introduced on EX Series switches at Junos OS Release 14.1X53-D10.
This FAQ covers the following questions:
Does the J-Web Application package 15.1A1 support all the features supported in the previous release, that is, J-Web Application package 14.1X53-A1?
Yes. The J-Web Application package 15.1A1 supports all the features supported in the previous release.
What has changed in the distribution or packaging of J-Web for the EX Series switches?
In Junos OS Releases earlier than Release 14.1X53-D10, J-Web was available as a single package as part of the Junos OS. For Junos OS Release 14.1X53-D10 and later, J-Web is available in two packages:
- Platform package—Installed as part of Junos OS by default; provides only minimal or basic features of J-Web (which includes, EZ Setup, Interface configuration, management access, user management, static routing, and image management).
- Application package—Separately installable package; provides complete features of J-Web (which include configuring, monitoring, maintaining, and troubleshooting).
These distribution or packaging changes are specific to J-Web for EX Series switches.
What are the benefits of the new J-Web distribution?
The new distribution decouples J-Web release from the Junos OS release cycle and provides the following benefits:
- New features for J-Web are available as part of the Application package and delivered independent of Junos OS releases.
- Application package installation and upgrades do not mandate upgrade of Junos OS and the need to reboot the switch.
Will the SRX Series platforms support the new J-Web distribution model?
No. As of now, only EX Series switches will support this J-Web distribution model from Junos OS Release 14.1X53-D10.
Which EX Series switches does the new J-Web distribution model support?
Table 1 shows the Junos OS release, the associated J-Web Application package release, and the switches supported in that release.
| Junos OS Release |
Associated J-Web Application Package Release |
Switches Supported by the J-Web Interface |
For More Information |
|---|---|---|---|
|
14.1X53-D10 through 14.1X53-D46 |
Application package 14.1X53-A2 |
EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, EX4600, and EX6200 |
|
|
14.1X53-D47 and later |
Application package 14.1X53-A3 |
EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, EX4600, and EX6200 |
|
|
15.1R1 |
Application package 15.1A1 |
EX2200, EX3300, EX4200, EX4500, EX4550, and EX6210 |
|
|
15.1R3 |
Application package 15.1A2 |
EX2200, EX3300, EX4200, EX4300, EX4500, EX4550, and EX6200 |
|
|
15.1X53-D50 |
Application package 15.1X53-A1 |
EX2300, EX2300-C, and EX3400 |
|
|
15.1R4-S5 |
Application package 15.1A3 |
EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, and EX6200 |
|
|
16.1R1 |
Application package 16.1A1 |
EX4300 and EX4600 |
|
|
17.1R1 |
Application package 17.1A1 |
EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
17.2R1 |
Application package 17.2A1 |
EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
17.3R1 |
Application package 17.3A1 |
EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
15.1X53-D57 |
Application package 15.1X53-A2 |
EX2300, EX2300-C, and EX3400 |
|
|
17.4R1 |
Application package 17.4A1 |
EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
18.1R1 |
Application package 18.1A1 |
EX2300, EX2300-C, EX3400, EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
18.1R2 |
Application package 18.1A2 |
EX2300, EX2300-C, EX3400, EX4300 and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
15.1X53-D59 |
Application package 15.1X53-A3 |
EX2300, EX2300-C, and EX3400 |
|
|
18.2R1 |
Application package 18.2A1 |
EX2300, EX2300-C, EX3400, EX4300, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
18.2R1 and later and all service releases of 18.2R1 and later |
Application Package 18.2A2 |
EX2300, EX2300-C, EX3400, EX4300, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
15.1R2 and later and all service releases of 15.1R2 and later |
Application package 15.1A4 |
EX2200, EX3200, EX3300, EX4200, EX4300, EX4500, EX4550, and EX6200 |
|
|
18.3R1 |
Application package 18.3A1 |
EX2300, EX2300-C, EX3400, EX4300, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
18.4R1 |
Application package 18.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
18.4R1 and later and all service releases of 18.4R1 and later |
Application Package 18.4A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.1R1 |
Application package 19.1A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, and EX4600 Note:
You cannot connect to and perform initial configuration of EX4600 switch by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.2R1 |
Application package 19.2A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.3R1 |
Application package 19.3A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.3R1 and later and all service releases of 19.3R1 and later |
Application package 19.3A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.4R1 |
Application package 19.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
19.4R1 and later and all service releases of 19.4R1 and later |
Application package 19.4A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
20.1R1 |
Application package 20.1A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
20.1R1 |
Application package 20.1A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
20.2R1 |
Application package 20.2A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
20.3R1 |
Application package 20.3A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
20.4R1 |
Application package 20.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
21.1R1 |
Application package 21.1A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
21.2R1 |
Application package 21.2A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
21.3R1 |
Application package 21.3A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
21.4R1 |
Application package 21.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
21.4R1 |
Application package 21.4A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4300, EX4300-MP, EX4600, and EX4650 Note:
You cannot connect to and perform initial configuration of EX4600 and EX4650 switches by using the EZSetup procedure from the J-Web interface; you must use EZSetup from the switch console. |
|
|
22.1R1 |
Application package 22.1A1 |
EX2300, EX2300-C, EX2300-MP, and EX3400 |
|
|
22.2R1 |
Application package 22.2A1 |
EX2300, EX2300-C, EX2300-MP, and EX3400 |
|
|
22.2R1 |
Application package 22.2A2 |
EX2300, EX2300-C, EX2300-MP, and EX3400 |
|
|
22.3R1 |
Application package 22.3A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, and EX4400 |
|
|
22.3R1 You must upgrade from Junos OS Release 22.3R1 to 22.3R3-S3 or later to install Application Package 22.3A2. |
Application package 22.3A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, and EX4400 |
|
|
22.4R1 |
Application package 22.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, and EX4400 |
|
|
22.4R1 You must upgrade from Junos OS Release 22.4R1 to 22.4R3-S2 or later to install Application Package 22.4A2. |
Application package 22.4A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, and EX4400 |
|
|
23.1R1 |
Application package 23.1A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, EX4400, and EX4400-24X |
|
|
23.2R1 |
Application package 23.2A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, EX4400, and EX4400-24X |
|
|
23.2R1 |
Application package 23.2A2 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, EX4400, and EX4400-24X |
|
|
23.4R1 |
Application package 23.4A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, EX4400, and EX4400-24X |
|
|
24.2R1 |
Application package 24.2A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-F, EX4400, and EX4400-24X |
|
|
24.3R1 |
Application package 24.3A1 |
EX2300, EX2300-C, EX2300-MP, EX3400, EX4100, EX4100-H-12MP, EX4100-F, EX4400, and EX4400-24X |
What is included in the J-Web Platform package?
The J-Web Platform package is bundled and shipped along with the Junos OS Release 14.1X53-D10 or later image according to the Junos OS release cycle schedule. The Platform package includes support for basic configuration and maintenance of the applicable fixed chassis EX Series switches, namely, EZSetup, interface configuration, management access, user management, static routing, image management, and so on.
What is included in the J-Web Application package?
The J-Web Application package provides all the features and functionalities of the J-Web interface that enable you to configure, monitor, maintain, and troubleshoot your switch.
The Application packages have their own release cycles which are independent of the Junos OS release cycle. The Application package is not installed by default on your switch; you download and install it over the Platform package on your switch.
Do I need to install the J-Web Platform package?
No. The J-Web Platform package is included in the Junos OS from Release 14.1X53-D10. It is installed on your switch as part of the Junos OS installation.
How do I upgrade the J-Web Platform package?
The J-Web Platform package is included in the Junos OS from Release 14.1X53-D10 and is installed on your switch as part of the Junos OS installation. If you upgrade to a later version of Junos OS, you automatically get the Platform package associated with that Junos OS.
If you have the Application package installed on your switch, and you upgrade Junos OS on your switch, then the Application package is removed and the Platform package that is associated with Junos OS is installed on your switch. You must install the associated J-Web Application package over the Platform package.
How do I know whether an Application package is installed on my switch?
You can view details of the J-Web packages installed on your switch in the About window in the J-Web interface or in the output of the show version command in the Junos OS CLI.
How do I upgrade my J-Web Application package?
The new J-Web packaging supports two new features: the auto update feature and the manual update feature.
- Every time you log in to the J-Web interface, the auto update feature checks the Juniper Networks server for the availability of the latest version of Application package. If the latest version is available, you are prompted for installation.
- You also have the option of checking for the availability of the latest Application
package at the Juniper Networks’ download website and installing an available update on
your switch by using the J-Web interface or CLI.Note:
Using CLI, the application packages are available for both Occam and non-Occam. For example:
- jweb-ex-app-19.1A1_app.50-signed.tgz for non-Occam.
- jweb-ex-app-x86-32-19.1A1_bsdx-app.51.tgz for Occam. Where, x86 represents the Occam software.
Do I need to reboot the switch as part an Application package installation?
No. There is no need to reboot the switch after the installation. The J-Web Application package is hot pluggable and installs on top of the current Junos OS image.
What is the release compatibility between Junos OS, J-Web Platform packages, and J-Web Application packages?
The Application packages of J-Web henceforth 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.
Table 2 illustrates the release compatibility.
|
Junos OS Release |
Associated J-Web Application Package Release |
|---|---|
|
14.1X53-D10 through 14.1X53-D46 |
Application package 14.1X53-A2 |
|
14.1X53-D47 and later |
Application package 14.1X53-A3 |
|
15.1R1 |
Application package 15.1A1 |
|
15.1R2, 15.1R3, 15.1R4-S5, and so on. |
Application package 15.1A3 Note:
Application package 15.1A3 cannot be installed on Junos OS Release 15.1R1. |
|
15.1X53-D50 |
Application package 15.1X53-A1. Note:
Application package 15.1X53-A1 cannot be installed on Junos OS Release 15.1R3. |
|
16.1R1 |
16.1A1 |
|
17.1R1 |
17.1A1 |
|
17.2R1 |
17.2A1 |
|
17.3R1 |
17.3A1 |
|
15.1X53-D57 |
Application package 15.1X53-A2 |
|
17.4R1 |
17.4A1 |
|
18.1R1 |
18.1A1 |
|
18.1R2 |
18.1A2 |
|
15.1X53-D59 |
Application package 15.1X53-A3 |
|
18.2R1 |
18.2A1 |
|
18.2R1 and later and all service releases of 18.2R1 and later |
18.2A2 |
|
18.3R1 |
18.3A1 |
|
18.4R1 |
18.4A1 |
|
18.4R1 and later and all service releases of 18.4R1 and later |
18.4A2 |
|
19.1R1 |
19.1A1 |
|
19.2R1 |
19.2A1 |
|
19.3R1 |
19.3A1 |
|
19.3R1 and later and all service releases of 19.3R1 and later |
19.3A2 |
|
19.4R1 |
19.4A1 |
|
19.4R1 and later and all service releases of 19.4R1 and later |
19.4A2 |
|
20.1R1 |
20.1A1 |
|
20.2R1 |
20.2A1 |
|
20.3R1 |
20.3A1 |
|
20.4R1 |
20.4A1 |
|
21.1R1 |
21.1A1 |
|
21.2R1 |
21.2A1 |
|
21.3R1 |
21.3A1 |
|
21.4R1 |
21.4A1 |
|
21.4R1 |
21.4A2 |
|
22.1R1 |
22.1A1 |
|
22.2R1 |
22.2A1 |
|
22.2R1 |
22.2A2 |
|
22.3R1 |
22.3A1 |
|
22.3R1 You must upgrade from Junos OS Release 22.3R1 to 22.3R3-S3 or later to install Application Package 22.3A2. |
22.3A2 |
|
22.4R1 |
22.4A1 |
|
22.4R1 You must upgrade from Junos OS Release 22.4R1 to 22.4R3-S2 or later to install Application Package 22.4A2. |
22.4A2 |
|
23.1R1 |
23.1A1 |
|
23.2R1 |
23.2A1 |
|
23.2R1 |
23.2A2 |
|
23.4R1 |
23.4A1 |
|
24.2R1 |
24.2A1 |
|
24.3R1 |
24.3A1 |
Any available later version of the Application package for a Junos OS release supersedes the earlier version. Thus, if Application package version 17.3A2 is available for 17.3R1, it will supersede version 17.3A1. We recommend that you install the latest available version of the Application package.
Can I install Application package version 15.1X53-A1 on top of Junos OS Release 14.1X53-D10?
No. Releases 14.1X53 and 15.1X53 are two distinct major releases of Junos OS. You can install Application package 14.1X53-A<x> where x is the latest available version (14.1X53-A2) of the Application package, on top of Junos OS Release 14.1X53-D10.
Similarly, an Application package for Junos OS Release 14.1X53-D<x> is not compatible with Junos OS Release 15.1X53-D<x>.
Can I install an Application package on top of Junos OS releases prior to Release 14.1X53?
No. The feature that separates J-Web for EX Series switches into Platform and Application packages is introduced in Junos OS Release 14.1X53.
Are there switch-specific Application package images available for EX Series switches?
No. There is a single Application package image that is compatible with all EX Series switches that is supported by J-Web, for the given release.
Any exceptions or limitations are documented in the release notes for the corresponding Application package.
Do I need Internet connectivity from the switch for the auto update feature to work?
Yes. Internet connectivity is required for the auto update feature to work. However, the Internet connectivity can be either from the switch or from the computer.
Can I uninstall J-Web packages?
You can uninstall an Application package by using the CLI command. After the Application package is uninstalled, the Platform package features will still be available for use.
We recommended that you do not uninstall the Platform package. If you uninstall the Platform package, you must reinstall Junos OS on your switch for the J-Web interface to be restored.
You cannot uninstall the J-Web package from EX2300 or EX3400 switch.