Skip to content

Commit 2622126

Browse files
committed
small change
1 parent 6d97ca8 commit 2622126

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/route-server/route-server-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ No. Azure Route Server is a service designed with high availability. Your route
2222

2323
### Do I need to peer each NVA with both Azure Route Server instances?
2424

25-
Yes, to ensure that routes are successfully advertised to Route Server and to configure high availability, it is required to peer each NVA instance with both instances of Route Server. It is also recommended to peer at least 2 NVA instances with both instances of Route Server.
25+
Yes, to ensure that routes are successfully advertised to Route Server and to configure high availability, it is required to peer each NVA instance with both instances of Route Server and advertise the same routes to both instances. It is also recommended to peer at least 2 NVA instances with both instances of Route Server.
2626

2727
>[!NOTE]
2828
> During Route Server maintenance events, BGP peering may go down between your NVA and one of Route Server's instances. As a result, if you configure your NVA to peer with both instances of Route Server, then your connectivity will remain up and running during maintenance events.

0 commit comments

Comments
 (0)