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
- 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.
| Item | Value |
|---|---|
| Domain name | ashby.example |
| Time zone | Europe/London |
| DNS server | 10.1.0.53 |
| NTP servers | 10.1.0.123 (and a second one, 10.4.0.123, at the depot only) |
| SNMP | community ashby-ro, read-only, only from 10.1.0.0/24; contact noc@ashby.example; traps to 10.1.0.60 |
| Archive server | DEPOT 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
- Build a configuration group
- Exclude a group where it does not belong
- Time and name services
- SNMP
- Archive the configuration on every commit
- 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.
Every link, as text
- HQ
ge-0/0/0to DEPOTge-0/0/0 - HQ
ge-0/0/2to HQ-LAN (network) - DEPOT
ge-0/0/2to DEPOT-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| HQ | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| DEPOT | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIA-Junos JN0-106 guided labs.Open
06 - Configuration groups and management servicesand 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
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.