CloudLabBox
Try the free demo

JNCIA-Junos lab 1 of 15

First boot - from factory default to a managed router

Log in to a brand-new Junos router, explore what the factory configuration contains, and give it the minimum configuration every device needs before it goes on a network: a root password of your choosing, a name, an admin account, SSH and its first interface addresses.

Run this lab

It needs Lite: its 1 node is set to 4 vCPU and 5,120 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIA-Junos JN0-106 guided labs, then 01 - First boot - from factory default to a managed router

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Beginner
Time
About 40 minutes
Nodes need
4 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Ashby Freight has just bought a router for its head office. The supplier's installer powered it on once, set a temporary root password (Juniper) and switched off zero-touch provisioning; apart from that it is exactly as it left the factory: no name, no users, no addresses. Before it can join the network you have to give it a safe minimum configuration. You are on the console, which is how every Junos device is first configured.

ItemValue
Host nameHQ
Domain nameashby.example
Time zoneEurope/London
Root passwordJuniper (keep it: the rest of the course uses it)
Admin accountlab, class super-user, password lab123
ge-0/0/0 (Office LAN)10.1.0.1/24 and 2001:db8:1::1/64
lo0 (loopback)192.168.255.1/32 and 2001:db8:255::1/128

The router takes several minutes to boot. Open its console and wait for the login: prompt below FreeBSD/amd64 (Amnesiac) (ttyu0). If you see qemux86-64 login: earlier, ignore it: that is the virtual machine's host system starting, not Junos.

What you’ll practise

  • Recognise the factory-default (Amnesiac) state and the difference between the shell and the Junos CLI
  • Explain zero-touch provisioning (Auto Image Upgrade) and how to stop it
  • Move between operational and configuration mode
  • Explain why Junos refuses to commit without a root password
  • Set the host name, domain name, time zone and a login message
  • Create a super-user account and enable SSH without root logins
  • Address an Ethernet interface and the loopback with IPv4 and IPv6, then commit with a comment

The tasks

  1. Log in and start the CLI
  2. Explore the factory configuration
  3. Configuration mode and the root-password rule
  4. Give the router its identity
  5. Create an admin account and enable SSH
  6. Address the interfaces
  7. Review and commit like a professional

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of First boot - from factory default to a managed router1 node and 1 network, 1 link. Every link is listed as text below the diagram.HQOffice-LANge-0/0/0
1 node and 1 network, with the interface names each link uses.
Every link, as text
  • HQ ge-0/0/0 to Office-LAN (network)
Nodes in First boot - from factory default to a managed router, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQJuniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder JNCIA-Junos JN0-106 guided labs.

  3. Open 01 - First boot - from factory default to a managed router and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More JNCIA-Junos labs

All JNCIA-Junos labs

Related labs in other courses

CloudLabBox is independent of Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.