SRX Series Services Gateways · Topic 4 of 4
J-Web and the vSRX Virtual Firewall
Learn how to enable and use J-Web on an SRX, how J-Web commits relate to the CLI, and where the vSRX Virtual Firewall runs and how its interfaces map.
- 6 min
- J-Web is enabled under
system services web-managementwithhttporhttpsand the interfaces it listens on. - Revenue ports also need host-inbound-traffic for
httporhttps. - J-Web uses Junos user accounts and login classes.
What it is
J-Web is the web-based graphical interface built into Junos OS on the SRX. It lets you monitor, configure and maintain one device from a browser instead of the CLI.
The vSRX Virtual Firewall is the SRX as a virtual machine. It runs the same Junos OS and the same security features in a hypervisor or a public cloud, with no SRX hardware.
How it works
Enabling J-Web
J-Web is a service of the device, configured under system services web-management. You enable HTTPS (or HTTP) and choose which interfaces it listens on.
user@srx# set system services web-management https system-generated-certificate
user@srx# set system services web-management https interface ge-0/0/1.0
user@srx# set security zones security-zone trust host-inbound-traffic system-services https
user@srx# commit
As with SSH, two things must be true on a revenue port. The web management service must be configured, and host-inbound-traffic on the ingress zone or interface must allow https (or http).
You then browse to the interface address and log in with a Junos user account. J-Web uses the same login classes as the CLI, so a read-only user cannot change the configuration in J-Web either.
What J-Web offers
| Area | Typical tasks |
|---|---|
| Dashboard | System health, resource use, active sessions and threat summaries at a glance |
| Monitoring | Interfaces, routes, sessions, policies, NAT, events and logs |
| Configuration | Interfaces, zones, address books, applications, security policies, NAT, VPNs and Content Security |
| Device administration | Users, software upgrades, licenses, configuration management and rollback |
The exact menu names change between Junos releases, but the idea is the same: everything you can see or change in J-Web maps to the same Junos configuration hierarchy you use in the CLI.
How J-Web changes the configuration
J-Web does not have its own configuration store. Changes you make in J-Web edit a candidate configuration, and nothing affects the device until you commit, exactly as in the CLI.
Because both tools share one configuration, a commit made in J-Web shows up in the CLI commit history (show system commit) and creates a new rollback version. You can also roll back from J-Web.
J-Web also includes CLI tools, so you can view the configuration as text or run commands from the browser.
If the exam asks how a J-Web change becomes active, the answer is a commit. J-Web follows the same candidate, commit and rollback model as the CLI.
When to use J-Web
| J-Web | CLI |
|---|---|
| Visual monitoring and dashboards | Fastest for experienced administrators |
| Guided setup for new users | Scripting and copy and paste of set commands |
| Building policies and objects with forms | Full access to every option and trace command |
Many administrators use both: J-Web to see the state of a device and the CLI for detailed changes and troubleshooting.
The vSRX Virtual Firewall
The vSRX gives you SRX security in places where there is no room or need for a hardware appliance.
| Platform type | Examples |
|---|---|
| Private cloud and hypervisors | KVM, VMware ESXi, Microsoft Hyper-V |
| Public cloud | Amazon Web Services, Microsoft Azure, Google Cloud |
Typical uses are protecting traffic between virtual machines, securing a cloud virtual network edge, building VPNs into the cloud and running a lab or test firewall.
Same Junos OS, virtual hardware
The vSRX runs the same Junos OS CLI, commit model, zones, policies, NAT, IPsec VPN and Content Security as a hardware SRX. The differences are about the platform, not the features you configure.
| Topic | vSRX behavior |
|---|---|
| CPU and memory | Virtual CPUs and memory assigned by the hypervisor set the performance |
| Interfaces | Virtual NICs map to Junos interface names |
| Licensing | Advanced features and higher throughput need licenses |
| Management | Usually through fxp0, the first virtual NIC |
vSRX interface mapping
The order of the virtual NICs decides the interface names. The first virtual NIC becomes the management interface fxp0. The second becomes ge-0/0/0, the third ge-0/0/1, and so on.
After that, the revenue ports go into security zones and need policies exactly as on a hardware SRX. In public clouds the cloud network also has its own controls, such as security groups, that must allow the traffic to reach the vSRX.
user@vsrx> show interfaces terse
Interface Admin Link Proto Local Remote
ge-0/0/0 up up
ge-0/0/0.0 up up inet 10.0.1.10/24
ge-0/0/1 up up
ge-0/0/1.0 up up inet 10.0.2.10/24
fxp0 up up
fxp0.0 up up inet 10.0.0.10/24
The first virtual NIC is fxp0, not ge-0/0/0. Exam options often assume the first NIC is the first revenue port, which puts every interface off by one.
Common mistakes
Enabling the web service but not host-inbound-traffic. On a revenue port, J-Web is unreachable until the ingress zone or interface allows https or http.
Thinking J-Web changes take effect immediately. J-Web edits the candidate; a commit activates the change.
Thinking the vSRX is a cut-down OS. The vSRX runs full Junos OS with the same security features; scale and licensing differ.
Assuming the vSRX needs no zones or policies. Revenue ports on a vSRX need zones and policies just like on a hardware SRX.
What to remember for the exam
- J-Web is enabled under
system services web-managementwithhttporhttpsand the interfaces it listens on. - Revenue ports also need host-inbound-traffic for
httporhttps. - J-Web uses Junos user accounts and login classes.
- J-Web edits the candidate configuration and needs a commit; commits appear in the CLI history and rollback list.
- The vSRX runs on hypervisors such as KVM, VMware ESXi and Hyper-V, and in AWS, Azure and Google Cloud.
- First vNIC is fxp0, second vNIC is ge-0/0/0.
- Advanced vSRX features and higher throughput require licenses.
Check yourself
HTTPS web management is configured, but J-Web on ge-0/0/1.0 does not load. What is the likely cause?
The ingress zone or interface does not allow
httpsin host-inbound-traffic.A vSRX has three virtual NICs. Which Junos interface is the second NIC?
ge-0/0/0. The first NIC is the management interface fxp0.
You change a security policy in J-Web. When does the device start using it?
When the change is committed. J-Web edits the candidate configuration like the CLI.
Topic 4 of 4 in SRX Series Services Gateways
Test yourself on SRX Series Services Gateways
The full Juniper JNCIA-SEC JN0-232 question bank has 658 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Juniper. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.