Love your work John! Quick Qs: - 15:30 mark - Azure uses AS 12076 for ER private and MS peering, while internally Azure uses AS 65515. How do they relate? - 21:00 mark - If ARS added support for BFD, failover time would be cut down to ms vs minutes (assuming NVA BFD support). I know ARS doesn't support BFD today, but would be an excellent future enhancement.
Regarding 12076 and 65515, no, they're not related. ER has Microsoft Peering, that's why we need to use a public ASN. Route Server doesn't have this requirement, so they picked a private ASN
Love the content. Do you have any guidance on use with Azure vwan? Specifically, for hub routing tables and hub vnet connections in a hub/spoke topology with the NVAs in the transit hub. I find myself having to add routes for each peered spoke to the vwan routing tables. Thanks.
A really useful and timely video for me, so big thanks John! I'm similarly keen to play with/understand Route Server in the context of VWAN too. Use case is an SD-WAN NVA in a VNet which is connected to a VWAN hub. Hope is that I can use a Route Server in the NVA VNet to receive SD-WAN routes dynamically and that those routes from the NVA VNet can then be propagated to e.g. the default route table in the VWAN hub.
Good lad! Had a question re route server and expressroute recently and great to see John is covering the topic. Taking in what you say, we use the branch to branch option if we have vnet1 > vpn gateway > hub vnet > expressroute > onprem?
John, great video. Thanks! One question. When you implemented Azure Router Server for branch-to-branch (transit routing) communication between Virtual Network Gateways. Does is overrule the Route Table configuration setting "Propagate gateway route" set to 'No'? In many cases we have a hub-spoke model where we use an Azure Firewall. We don't want to mess with that setup and have more specific routes to propagate.
Dear John, what setup is required to make Azure Firewall in the hub advertise default route pointing to it? I couldn’t find a single article about that on the internet. Many thanks!
@@NTFAQGuy nooooooo :( I skipped through the video and missed this part. Now I know to use Transcript next time. This is a setback, but so is the limit of 6000 IPs. Say I have 20 spokes, /22 each. That is 20000 IPs. What happens there? ARS just randomly chooses what works and what does not?
When I enable Default information originate from the NVA (Fortigate) It creates a routing loop as OUSID interface of the firewall learn that the default route is available through INSID interface. Is there a way around this issue ? There's also another issue using the VNG, the VNG learns route via the peering, and I need to add a UDR for the GatewaySubnet with more specific routes for every spokes so that the VNG will route through the NVA first. If you don't do this you'll get symmetric routing has the VNG will reach the VM in spoke through the peering without passing trough the NVA first. This is really counter productive. If anyone has found a way to make it work without UDR please let me know.
@@NTFAQGuy I've found out the I need to use UDR on the subnet where the NVA has it's OUSID interface to overide default route learned by the route server. I guess you need more UDRs to get rid of UDRs.
@@NTFAQGuy Umuntu ngumuntu ngabantu... you learn something new every day! Didn't realise Ubuntu was taken from African philosophy. At the same time, it doesn't matter the exact pronunciation is missed, the fact you understood is important 😁
