Aravel SwitchManager

edge-sw-03 · firmware v4.6.1

SY0-701 · 4.4 SY0-701 · 4.9

Lab scenario

Tier the switch's event logging by severity

You just started as the security admin at Foxglen Outfitters, a regional outdoor-gear distributor. The managed access switch in the warehouse mezzanine closet ships with logging switched off. Before it goes into service you need to turn logging on, point it at the company's log aggregator, and tier which event severities are kept in fast volatile memory versus written to the device's limited persistent flash — then make the change survive a reboot.

Connected to edge-sw-03 (10.40.12.2) Warehouse / Mezzanine IDF

Event Logging

Control whether the switch records events, where it forwards them, and which severities are retained in each store.

Logging Service Master control. While off, the switch records nothing.
Syslog Aggregator Forward events to the central collector at logs.foxglen.internal for correlation.
Severity level (RFC 5424) VolatileRAM buffer PersistentFlash store

Lower numbers are more urgent. Flash has finite write endurance, so reserve it for events that must survive a reboot.

Configuration Running changes are live but volatile until committed to the startup config.
No changes yet

Submit completed lab

Enter a pseudonymous handle (no real names). Submitting captures a snapshot of your work and sends it to your instructor.

Score 0 / 9

Severity-Tiered Switch Logging · Security+ SY0-701 lab · © 2026 [Author Name]. Original clean-room simulation.