The manual states: CHR system-id is bound to MBR and UUID - but what exactly does it mean? What is it checking on the MBR and UUID (disk UUID or hardware ID etc).

With the amount we've spent on licensing we expect it to just work, and not have to keep worrying about system ID's. Is there a definite answer over how CHR figures out what the system ID and the checks it performs to ensure the license is really valid? Nothing has changed with the disk image, nor the system/hardware UUID id the VirtualBox or KVM xml file, so what could cause this? each reboot the system ID is the same and the license just 'works'.Īfter booting the original image, drag-and-dropping the RouterOS upgrade file to the Files via Winbox and rebooting, again all good, but sometimes, even though the system id is the same, it throws an error stating the system id has already previously used a trial or that there is something wrong with the system id. They have been working fine until it comes to upgrade time. We purchased over 400 CHR P1 perpetual licenses a few years ago that are used on either VirtualBox/Linux KVM hosts. To get the free trial license, you should have an account on as all license management is done there. I have a question about how the CHR system id (for licensing purposes) is *really* generated/checked. The CHR has 4 license levels: free p1 perpetual-1 (45) p10 perpetual-10 (95) p-unlimited perpetual-unlimited (250) 60-day free trial license is available for all paid license levels.

Mikrotik chr p1 license