Back to portfolioPROJECT CASE STUDY / 03
NETWORK OPERATIONS LAB

ENGINEERING PROJECT / 03

NetOps Sentinel.

CASE STUDY
2026

A repeatable GNS3 network operations lab that validates a structured inventory, checks endpoint reachability and records monitoring results as JSON evidence.

PROJECTNetOps Sentinel
TYPENETWORK OPERATIONS LAB
TECHNOLOGIES5 core tools
PythonGNS3FRRoutingJSONunittest

01 / CONTEXT

THE WHY

The challenge

Network labs can be difficult to verify consistently when device inventories and reachability checks are performed manually. NetOps Sentinel pairs a documented multi-router topology with a read-only validation workflow and structured evidence.

02 / SYSTEM DESIGN

THE STRUCTURE

How the pieces fit together

A high-level view of the documented workflow and component boundaries.

01

GNS3 topology

Three FRRouting routers connect five switches, five LANs and two point-to-point transit networks.

02

JSON inventory

Describes devices, networks, endpoints, interfaces and routing intent.

03

Inventory validator

Checks expected inventory data and addressing before monitoring.

04

Read-only reachability probes

Uses the system ping utility with Linux and Windows probe support.

05

JSON evidence output

Records monitoring results for later review and comparison.

03 / ENGINEERING LOG

THE BUILD SEQUENCE

How the work took shape

A transparent sequence of engineering milestones. Status labels describe documented work—not a live completion percentage.

  1. 01
    01 · TOPOLOGYDocumented

    Model the routed lab

    Documented a topology with three FRRouting routers, five switches, five LANs and two point-to-point transit networks.

  2. 02
    02 · INVENTORYRecorded

    Define and validate expected state

    Created a JSON inventory and recorded validation for 8 devices, 7 networks, 5 endpoints and 4 interfaces.

  3. 03
    03 · MONITORINGRecorded

    Run read-only reachability checks

    Added platform-aware ICMP probes and recorded a baseline in which five HQ test destinations responded.

  4. 04
    04 · EVIDENCERecorded

    Persist results and automated checks

    Stored monitoring results as JSON evidence. The repository records seven passing unit tests for inventory, endpoint loading, probes and timeouts.

  5. 05
    05 · NEXT RUNNext

    Repeat the lab validation

    The recorded evidence describes a prior GNS3 run, not live device health. Re-run the checks against the current lab before treating the baseline as current.

04 / DESIGN JUDGMENT

TRADE-OFFS & REASONS

Decisions behind the design

The engineering choices that shape the system—and the reason each boundary exists.

01

Make the JSON inventory the expected-state contract

A single structured inventory lets validation happen before probes run and makes topology assumptions reviewable in version control.

02

Keep monitoring probes read-only

ICMP checks provide a low-impact reachability baseline without changing the GNS3 devices or claiming application-level health.

03

Persist each run as evidence

Structured JSON output supports comparison between runs and makes it possible to trace a reported result back to a specific lab execution.

05 / NEXT INVESTIGATION

THE NEXT USEFUL TEST

What I would test next

Extend the checks in two layers: verify routing-table and interface state on the routers, then add service-level TCP probes for selected endpoints. Keep ICMP and service availability as separate signals so a ping response is never mistaken for application health.

06 / IMPLEMENTATION

THE HOW

Engineering approach

The work is broken into practical building blocks, from initial design through to validation.

  1. 01

    Models the network with three FRRouting routers, five switches, five LANs and two transit networks.

  2. 02

    Defines an expected inventory of devices, networks, endpoints and interfaces in JSON.

  3. 03

    Validates inventory structure and addressing before probing endpoints.

  4. 04

    Runs read-only ICMP reachability checks with platform-aware probe support.

  5. 05

    Records structured JSON output so monitoring runs can be reviewed and compared.

07 / VERIFICATION

THE CHECKS

Validation & evidence

Specific checks documented for this project. Results are scoped to the recorded lab or test run.

Inventory validationPASS

The documented baseline checked 8 devices, 7 networks, 5 endpoints and 4 interfaces.

Automated tests7 passed

The README records a run of seven unit tests covering inventory, endpoint loading, probes and timeouts.

Reachability baseline5 destinations

The recorded HQ endpoint test reached its gateway, server, management and two branch endpoints.

08 / RESULTS

THE VALUE

What this project demonstrates

01

A repeatable validation workflow rather than a one-off topology diagram.

02

A documented GNS3 baseline spanning headquarters and two branch networks.

03

Structured JSON outputs and automated tests that support troubleshooting and future automation.

09 / EVIDENCE

THE BUILD

Project in practice

Original project captures and walkthrough media. Each item is labelled to explain what it demonstrates.

These are genuine captures from the documented GNS3 lab baseline. The evidence notes date the lab record to October 19, 2026; results describe that recorded test state, not current live device health.

10 / ENGINEERING NOTES

TRANSPARENCY

Scope, assumptions & limitations

Clear boundaries matter. These notes describe what the current project does—and what it does not claim to do.

  • This is a lab validation and monitoring project, not a production network monitoring service.
  • The documented routing baseline is static routing; OSPF is not claimed as implemented.
  • ICMP reachability confirms a response at the time of the check; it does not prove application availability or live route correctness.
  • Results depend on the configured GNS3 lab and its device state.
  • The recorded test and inventory results describe the documented run, not a guarantee of current live network health.