Azure Route Server

This is the part 2 of 2 series blog post on Azure Route Server. In this blog post we will deploy and configure Azure Route Server (ARS). As one of the pre-requisite to deploy ARS, is to have a dedicated subnet (RouteServerSubnet) in an existing or new Virtual network. I am going to create this new subnet in an existing Virtual Network

Now, we will deploy Azure Route Server.

Look for Route Server in the top Search Bar of Azure Portal

Then on the Route Server Home page, click on Create a new Route Server

Then fill up the deployment information, which includes Resource Group Name, Route Server Instance name, region, and select the virtual network in which "RouteServerSubnet" is created in the previous step.

Once the deployment is successfully completed, Route Server will be available for the configuration.

Now, we need to attach peers to the Route Server, so that it can learn the available routes from the Peer device. On the Route Server, go to Settings -> Peers and then Add. In the below scenario, I am adding the NVA IP address to add as a Peer.

If in your environment, you have Express Route Gateway and Site to Site Gateway and if you want to enable route exchange between them, then you can set the flag by enabling Branch to Branch to configuration.

On the Azure Route Server, go to Setting, Configuration and slide the toggle to Enabled

This ends the successful configuration of the Azure Route server.