A new SRX: console, factory state and what J-Web is
Where this module fits. The Junos modules start with a device you can already reach. On day one you have a box (or vSRX), a console and a cable. This module covers the first hour: console login, the root password, a management address, a named administrator and J-Web.
Analogy: the new office with no keys
A factory-fresh SRX is an office with an open door and no keys cut yet. Anybody can walk in at the console as root with no password, and the configuration will not even commit until you set one. That one rule explains most of the first hour.
Factory state (as modelled in the simulator)
| Item | Value |
|---|---|
| Management access | ge-0/0/1 at 192.168.1.1/24 in the trust zone |
| J-Web | enabled on ge-0/0/1 over https |
| Root login | console login root, no password |
| Accounts that can sign in to J-Web | none until a password is set |
Real branch SRX models ship with a similar factory-default configuration, and larger or virtual models use the fxp0 management port instead. The simulator lets the lab choose which port the admin laptop is cabled to.
CLI and J-Web
The Junos CLI has two modes: operational mode (>) and configuration mode (#, entered with configure). Changes live in a candidate configuration until you commit. J-Web is the web interface that edits the same configuration in a browser.
Key takeaways: factory root has no password and nobody can commit until one is set. Factory management: ge-0/0/1 192.168.1.1/24, J-Web on https. Candidate, then commit.