System CPU plan and licensing
The system view owns the box-level knobs: the CPU plan the daemon lays out at boot, and the persistent diagnostic-log level and sink. Licensing sits beside it. Everything on this page requires the full operator role; compliance logging has its own page.
The CPU plan
At boot the planner divides the machine into MAIN, CONTROL and WORKER lcores — show topology prints the live plan. Three knobs steer it: control-cores sets how many cores are reserved for the control plane rather than forwarding; ht-policy chooses how hyper-thread siblings are treated in the plan, isolate or shadow; and max-workers-per-10g caps how many workers the planner assigns per 10G of port capacity. These change state that is fixed when the daemon boots, so they re-plan the worker layout on restart: commit records the change and save persists it, but the running layout does not move until the daemon is restarted.
system-view system control-cores <n> # ON RESTART system ht-policy isolate|shadow system max-workers-per-10g <n> system undo <control-cores|ht-policy|max-workers-per-10g> commit ; save # then restart the daemon show system # the configured knobs show topology # the live MAIN / CONTROL / WORKER plan
Persistent log level and sink
The persistent global diagnostic-log level and output sink live in the system view and stage like any other config change. The live per-module controls — log level <module> <lvl> — and the reading commands, show logging and show log, are covered on the Troubleshooting page.
system logging level <off|critical|error|warning|notice|info|debug> system logging output memory|stdout|stderr|file <path> system undo logging <level|output> commit ; save
Licence state and requests
show license reports the licence state, with detail, usage and server views for caps, consumption and the licence-server link. license request generates a host request — the fingerprint needed to issue or reissue a licence for this machine — and the export form writes it to a file for transfer.
show license [detail|usage|server] license request license request export <file>
Licence maintenance commands
The remaining licence commands are maintenance actions, normally run during onboarding or a support session: activate applies a key, install loads a licence file, reload re-reads the installed licence, and the checkin family points the box at a licence server and sets the check-in interval and key. They are hidden commands — executable when typed in full, but never offered by ? or TAB completion — and require the full role.
license activate <key> license install <file> license reload license checkin enable|disable license checkin server <host> license checkin interval <secs> license checkin key <key>