JNCIA-Junos lab 6 of 15

Configuration groups and management services

Standardise two routers with a configuration group, point them at the company time and DNS servers, make them manageable by SNMP, and have HQ copy its configuration to DEPOT automatically on every commit. Finish with what J-Web offers and how to switch it on.

Run this lab

It needs Standard: its 2 nodes are set to 8 vCPU and 10,240 MB in total.

In your workspace: Shared, then JNCIA-Junos JN0-106 guided labs, then 06 - Configuration groups and management services

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 8 vCPU and 10,240 MB together. Every lab plan includes every guided lab.

Level
Beginner
Time
About 50 minutes
Nodes need
8 vCPU, 10,240 MB
Smallest plan
Standard

The scenario

Ashby Freight wants every router built the same way. You will put the company standard into a configuration group that any router can apply, add the management services the network team needs, and protect against lost configurations by archiving HQ's configuration to another device on every commit. Until the new archive server is installed, DEPOT stands in for it.

ItemValue
Domain nameashby.example
Time zoneEurope/London
DNS server10.1.0.53
NTP servers10.1.0.123 (and a second one, 10.4.0.123, at the depot only)
SNMPcommunity ashby-ro, read-only, only from 10.1.0.0/24; contact noc@ashby.example; traps to 10.1.0.60
Archive serverDEPOT 172.16.14.2, FTP user lab, password lab123

The DNS, NTP and network management servers are planned but not installed yet, so you will configure them and see how Junos reports a server it cannot reach.

What you’ll practise

  • Build a configuration group, apply it, and see inherited statements with display inheritance
  • Explain how local statements and group statements combine, and exclude a group with apply-groups-except
  • Configure NTP and DNS servers and read the NTP status
  • Configure SNMP: community with a client list, location, contact and a trap target
  • Archive the configuration to a remote server on every commit
  • Describe J-Web's role and how it is enabled

The tasks

  1. Build a configuration group
  2. Exclude a group where it does not belong
  3. Time and name services
  4. SNMP
  5. Archive the configuration on every commit
  6. J-Web

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 Configuration groups and management services2 nodes and 2 networks, 3 links. Every link is listed as text below the diagram.HQDEPOTHQ-LANDEPOT-LANge-0/0/2ge-0/0/2ge-0/0/0ge-0/0/0
2 nodes and 2 networks, with the interface names each link uses.
Nodes in Configuration groups and management services, 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
DEPOTJuniper 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 06 - Configuration groups and management services 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.