Skip to content

P01-T08 - CHR Trial License

Objective

Register HQ-CHR01 with a MikroTik CHR trial or paid license so throughput-sensitive validation is not distorted by the default free CHR limit.

Validated lab status

The current lab was functionally validated without consuming the trial. This runbook documents the licensing procedure as an operational step and must be executed when the sysadmin is ready to bind the CHR system-id to the approved MikroTik account.

Do not activate the trial early just to satisfy documentation. Activate it when throughput, production-equivalent licensing, or long-lived CHR lifecycle validation is in scope.

Official MikroTik documentation states that CHR trial activation is requested from the CHR CLI with /system/license/renew, using a MikroTik.com account and a selected license level. The trial period is 60 days.

Reference:

Inputs

Key Value
Router HQ-CHR01
RouterOS version validated in lab 7.21.5
Internet access Required
MikroTik account Required
License level p1, p10, p-unlimited, or approved paid/prepaid equivalent

Target State

Property Value
License level Approved CHR trial or paid level
MikroTik account binding CHR system-id visible in the approved MikroTik account
Throughput posture No longer constrained by the default free CHR limit

Prechecks

  • Complete P01-T05 and P01-T06.
  • Confirm HQ-CHR01 has outbound internet access.
  • Confirm the CHR VM is the final router instance, not a disposable test clone.
  • Confirm the MikroTik account that will own the CHR license.
  • Confirm the desired license level before running /system/license/renew.
  • Capture the current license state.
/system/license/print

Expected pre-activation evidence on a new CHR:

  • a stable system-id
  • current level showing the free/default CHR state

Execution

Option A - CLI Licensing

Run on HQ-CHR01:

/system/license/renew

RouterOS prompts interactively for:

  • MikroTik.com account
  • MikroTik.com password
  • desired license level

Use the approved account and selected CHR level. For example, when prompted for level, enter the approved value such as:

p1

Do not paste MikroTik credentials into documentation, tickets, or chat. The sysadmin enters them interactively in the RouterOS prompt.

After the command completes, verify the license state:

/system/license/print

Option B - WinBox or WebFig Licensing

Use this path if the operating standard prefers a GUI for account-bound licensing:

  1. Connect to HQ-CHR01 using WinBox or WebFig from an approved management network.
  2. Open System -> License.
  3. Select the approved CHR level.
  4. Authenticate with the approved MikroTik account.
  5. Apply the trial or paid license.
  6. Return to the CLI and capture final evidence:
/system/license/print

Post-Licensing Validation

Run on HQ-CHR01:

/system/license/print
/ping 1.1.1.1 count=4
/ping cloudflare.com count=4

Validate:

  • license level matches the approved level
  • system-id remains stable
  • renewal/deadline fields are present if RouterOS exposes them for the selected state
  • router internet access still works
  • firewall and NAT behavior remain unchanged

Evidence

Capture:

  • output of /system/license/print before activation
  • selected license level
  • output of /system/license/print after activation
  • account owner confirmation without exposing the account password
  • optional screenshot from WinBox/WebFig System -> License

Warnings

  • Trial activation binds the CHR system-id to the MikroTik account.
  • The trial period is time-limited; do not activate it before the lab needs it.
  • Do not run /system license generate-new-id after a trial or paid license has been obtained. MikroTik documents that regenerating the ID after licensing can prevent the current key from being updated.
  • If the wrong MikroTik account is used, stop and correct ownership before proceeding with production validation.

Rollback

Licensing is not a normal RouterOS configuration rollback.

If the wrong router instance was licensed, preserve evidence and escalate before deleting or rebuilding the VM. If the wrong account was used, resolve the account ownership issue through the MikroTik account workflow before continuing.