Unfortunately someone changed something on the DNS server which caused the CHR to be unable to verify the license status. So in my case I have a CHR with a p1 license running on AWS for more than a year now.
However, router will continue to work with the same license tier as before.
If deadline-at date is reached without successfully contacting the account server, the router will consider that license has expired and will disallow further software updates. Communication attempts will be performed once an hour after the date on next-renewal-at and will not cease until the server responds with an error. This might keep the license.Ī disadvantage of of x86-ROS is that it wants to be a 32-Bit system when installed and a CHR-ROS system wants to be a 64-Bit system ( both are almost identical ).ĮDIT - also - I don't think x86-ROS supports para-virtual NICs ( aka 10-Gig vmnic anything ) which might limit you to a 1-Gig E1000e Nic.In '/system license' menu router will indicate the time next-renewal-at when it will attempt to contact server located on. The x86-ROS router uses a different license system from the CHR-ROS router. #2 I am not certain but I think this might work: Instead of using a CHR, try using an x86 ROS virtual router. The disadvantage of this is everything is slower. Any virtaul machines ( CHR ) running on the virtual hypervisor will still be there. With this #1 method - you move the virtual hypervisor and spin it up. Install your CHR on the virtual hypervisor. #1 Create a virtual hypervisor on you primary hypervisor.
There are two possible work-arounds options to retain the license ( for a CHR move ). When a Mikrotik CHR ( with the license ) is moved to another location on the hypervisor or to another hypervisor ( either manually or by automatically ) the new spun-up CHR will no longer retain the original license.
0 kommentar(er)
