Skip to content

Commit eb76845

Browse files
committed
move the rras note to the beginning of the section
1 parent 81ee949 commit eb76845

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/route-server/peer-route-server-with-virtual-appliance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,9 @@ In this section, you create a Windows Server VM in the virtual network you creat
130130

131131
In this section, you configure BGP settings on the VM so it acts as an NVA and can exchange routes with the Route Server.
132132

133+
> [!IMPORTANT]
134+
> The Routing and Remote Access Service (RRAS) isn't supported in Azure. However, in this tutorial, it's used to simulate an NVA and demonstrate how to peer a route server with it. For more information, see [Remote access overview](/windows-server/remote/remote-access/remote-access).
135+
133136
1. Go to **myNVA** virtual machine and select **Connect**.
134137

135138
1. On the **Connect** page, select **Download RDP file** under **Native RDP**.
@@ -161,9 +164,6 @@ In this section, you configure BGP settings on the VM so it acts as an NVA and c
161164
Add-BgpCustomRoute -network 172.16.2.0/24
162165
```
163166
164-
> [!IMPORTANT]
165-
> The Routing and Remote Access Service (RRAS) isn't supported in Azure. However, in this tutorial, it's used to simulate an NVA and demonstrate how to peer a route server with it. For more information, see [Remote access overview](/windows-server/remote/remote-access/remote-access).
166-
167167
## Configure Route Server peering
168168
169169
1. Go to the Route Server you created in the previous steps.

0 commit comments

Comments
 (0)