I’ve noted there isn’t a lot of up-to-date “CHR on Azure” documentation so I am attempting to create some here.
Maybe someone can copy to: https://wiki.mikrotik.com/wiki/Manual:CHR
It would be optimal for Mikrotik to create an azure marketplace CHR image. That would make this post mostly redundant.
step 1: download CHR vhdx and convert to vhd
example powershell:
Convert-VHD -Path C:\chr-6.45.6.vhdx -DestinationPath C:\chr-6.45.6.vhd -vhdtype fixed
step 2: upload vhd to a blob container:
Upload the VHD file using the Azure Portal.
In the Azure Portal, select Storage Accounts.
- Select the storage account where the CHR VHD file will be uploaded to.
Under BLOB SERVICE, select Containers.
Select a container to upload the CHR VHD file to.
If you do not have a storage container, click Add Container to create one.
Click Upload and select the CHR VHD file to upload.
Ensure that the Blob type is set to Page Blob.
step 3: 2. Create an image using the Azure Portal.
In the Azure Portal, select “Images”. (note this is different than “virtual machines”)
Click Add to create a new image.
Give the image a name. Remember that this image is a template that will later be deployed to a virtual machine with a different name.
Ensure that the location is the same as the location of your storage account.
iIn the OS disk section:
Select Linux and the OS type.
Click Browse on the Storage Blob field. A new panel will list your storage accounts. Using this panel, navigate through the storage account and container to locate the CHR VHD that was uploaded.
(os type linux)
(vm generation 1)
Click Create to begin the image creation process. This process typically takes minutes to complete.
When the process has completed, return to the Images panel and verify that the new image was created.
step 4: create the vm
In the Azure Portal, select “virtual machines”.
Click Add to create a new VM.
Under image, click “browse all public and private images”, and in the “my items tab” you should see the CHR vhd image you created in step 3.
I used the smallest size B1ls.
Note: you will need to set the “enable ip forwarding” parameter in the resulting azure vm network interface.
Note: the azure serial console feature works.
step 5: (optional) create a S2S vpn
note: profiles must have “nat traversal” enabled.
note: you will have to create a route table to direct vnet traffic over the vpn tunnel.
