An Azure service that enables network appliances to exchange route information with Azure virtual networks dynamically.
Hello @ adm_Enzo Smeriglio,
Thanks for reaching out to Microsoft of Q&A.
I see you're looking to deploy a route server into your existing VNet without incurring an outage. Unfortunately, here’s the info you need to know: when a Route Server is created or deleted in a virtual network that includes a virtual network gateway (like ExpressRoute or VPN), there will be a brief downtime expected to last around 10 minutes. It's also recommended to plan for a maintenance window of about 60 minutes for the entire deployment process.
Here's what I suggest:
- Schedule Your Deployment: Given the expected downtime, pick a maintenance window when network traffic is at its lowest.
- Prepare Your Environment:
- Ensure the subnet for the Route Server is at least /26 in size.
- Check that your NVA is properly configured to BGP peer with both Route Server instances.
- Follow Best Practices:
- Review the Azure Route Server setup documentation for specifics about deployment configuration.
- Look through the FAQ to prepare for any potential concerns you may come across during deployment.
Reference Document:
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".