DCops AI
Login
Menu

Protected

Cumulus supplement content is available after admin verification. Redirecting...

If you are not redirected, login.

Access

Admin only

The Cumulus supplement is restricted to admin users.

Training / NCP-AIN / Cumulus

Unit 2: Cumulus Linux Overview

Per-unit concept, checklist, and command drill page

Unit 2 of 14

Objective

Build a precise model of Cumulus Linux architecture, config model, and management entry points.

Concept Notes

Cumulus Linux should be viewed as a Linux-based network operating system with clear control-plane and data-plane roles, not as a black-box appliance OS. That architecture is what enables automation at scale.

For exam and real operations, focus on “which subsystem owns what.” When issues occur, fast troubleshooting depends on knowing whether the source is NVUE state, FRR routing state, Linux interface state, or hardware/driver behavior.

Coverage Checklist

  • Open Ethernet separation of hardware and NOS.
  • Cumulus architecture: hardware, kernel, user space, top-level applications.
  • Configuration surfaces: Linux CLI, VTY shell, NVUE CLI/REST.
  • Core services: FRR, MSTPD, LLDPD, Linux LACP.
  • Primary config files: interfaces, FRR config, NVUE startup YAML.
  • Best-practice backup and change discipline in /etc.

Practice Outcomes

  • Explain why NVUE-generated files should not be manually edited.
  • Map each protocol/service to the file or daemon responsible for it.
  • Describe how Cumulus enables server-like operational consistency on switches.

Navigation

Back to Cumulus index Previous: Unit 1 Next: Unit 3