Deploy CSR 1000v High Availability on Microsoft Azure

This video walks you through deployment of CSR high availability on Azure.

[rpb]

Nice demo which helps clarify some of the out of date info in the Cisco guide! Mostly around using the ARM portal.

[gavinschokman]

Hi Fan,

Great video… very useful to see the process walked-through. Thanks!

I’ve got two follow-up questions that you didn’t cover:

1. What happens when CSR-1 comes back online? Does it update the routing table again to make itself the next-hop?
If it doesn’t switch back automatically, how can we make it do so?
I have an IWAN deployment with 2x DMVPN clouds, where the routing metrics are setup so that DMVPN #1 is the preferred path (when available) and DMVPN #2 is the backup path. I'm planning to connect my Azure environment to my DMVPN topology. So I’m keen to know how we can ensure the UDR table is updated to point to CSR-1 again once it has comes back online. Otherwise, we will have asymmetric routing.

2. How do you configure CSR-1 & CSR-2 to be in the same Azure Availability Set?
(I’m sure you know this, but just in case) Availability sets are the way we tell Azure that these two VMs need to be run in different fault domains. You have to specify the Availability Set name at the time of creating the CSR 1000v VM. It’s not possible to add/modify later on. And since the “create wizard” in Resource Manager doesn’t ask for the Availability Set as an input parameter, I have been looking for how to do this, but I cannot find any reference material. If we don’t put CSR-1 and CSR-2 into the same Availability Set, there is a chance (maybe small, but still there) that they both get deployed on servers in the same Azure fault domain. This obviously negates the point of deploying two CSRs for HA.

Keen to hear your comments on these points

Many thanks,
Gavin

[andriiklymenko]

could we use EEM to config another IP address on the standby node when the primary node fails?