CloudLabBox
Try the free demo

JNCIA-SEC and JNCIS-SEC lab 14 of 16

Logging and monitoring

Send session logs to a local file and a remote server, read sessions and counters, trace a dropped packet to the policy that dropped it, and find out who changed what.

Run this lab

It needs Lite: its 4 nodes are set to 5 vCPU and 7,168 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIA-SEC and JNCIS-SEC SRX security guided labs, then 14 - Logging and monitoring

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
Intermediate
Time
About 65 minutes
Nodes need
5 vCPU, 7,168 MB
Smallest plan
Lite

The scenario

Hartwell's auditors want a record of what crosses the firewall, kept off the box. And the service desk has a ticket: a member of staff can't reach a supplier's system on port 8080. You'll set up logging both ways, get comfortable reading sessions and counters, and trace that dropped packet to its cause.

DeviceInterfaceAddressZone or gateway
SRXge-0/0/0203.0.113.1/24zone untrust
SRXge-0/0/110.10.10.1/24zone trust
SRXge-0/0/210.10.20.1/24zone dmz
LAN-PCeth010.10.10.10/24gateway 10.10.10.1
LOG-SRVeth010.10.20.50/24gateway 10.10.20.1, runs a syslog receiver
OUTeth0203.0.113.10/24gateway 203.0.113.1

LOG-SRV runs a small syslog receiver that writes everything arriving on UDP 514 to /var/log/srx-syslog.log. Policy LAN-OUT permits HTTP and ping from trust to untrust.

What you’ll practise

  • Explain event, stream and stream-event logging
  • Read RT_FLOW lines in both formats
  • Filter the session table and read flow statistics
  • Use filtered flow traceoptions to find why a packet dropped
  • Read commit history and alarms

The tasks

  1. Event-mode logging
  2. Stream to a server
  3. Sessions and counters
  4. Why was it dropped?
  5. Who changed what?

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 Logging and monitoring4 nodes, 3 links. Every link is listed as text below the diagram.SRXLAN-PCLOG-SRVOUTge-0/0/2eth0ge-0/0/1eth0ge-0/0/0eth0
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • SRX ge-0/0/0 to OUT eth0
  • SRX ge-0/0/1 to LAN-PC eth0
  • SRX ge-0/0/2 to LOG-SRV eth0
Nodes in Logging and monitoring, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
SRXJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
LAN-PCEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
LOG-SRVEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
OUTEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 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-SEC and JNCIS-SEC SRX security guided labs.

  3. Open 14 - Logging and monitoring 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-SEC and JNCIS-SEC labs

All JNCIA-SEC and JNCIS-SEC labs

Related labs in other courses

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