You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/route-server/tutorial-configure-route-server-with-quagga.md
+35-22Lines changed: 35 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,18 +5,18 @@ author: halkazwini
5
5
ms.author: halkazwini
6
6
ms.service: route-server
7
7
ms.topic: tutorial
8
-
ms.date: 03/28/2023
8
+
ms.date: 07/10/2023
9
9
ms.custom: template-tutorial, engagement-fy23
10
10
---
11
11
12
12
# Tutorial: Configure peering between Azure Route Server and Network Virtual Appliance
13
13
14
-
This tutorial shows you how to deploy an Azure Route Server into a virtual network and establish a BGP peering connection with a Quagga network virtual appliance (NVA). You'll deploy a virtual network with four subnets. One subnet will be dedicated to the Route Server and another subnet dedicated to the Quagga NVA. The Quagga NVA will be configured to exchange routes with the Route Server. Lastly, you'll test to make sure routes are properly exchanged on the Route Server and Quagga NVA.
14
+
This tutorial shows you how to deploy an Azure Route Server into a virtual network and establish a BGP peering connection with a Quagga network virtual appliance (NVA). You deploy a virtual network with four subnets. One subnet is dedicated to the Route Server and another subnet dedicated to the Quagga NVA. The Quagga NVA will be configured to exchange routes with the Route Server. Lastly, you'll test to make sure routes are properly exchanged on the Route Server and Quagga NVA.
15
15
16
16
In this tutorial, you learn how to:
17
17
18
18
> [!div class="checklist"]
19
-
> * Create a virtual network with five subnets
19
+
> * Create a virtual network with four subnets
20
20
> * Deploy an Azure Route Server
21
21
> * Deploy a virtual machine running Quagga
22
22
> * Configure Route Server peering
@@ -26,15 +26,15 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
26
26
27
27
## Prerequisites
28
28
29
-
* An Azure subscription
29
+
* An active Azure subscription
30
30
31
31
## Sign in to Azure
32
32
33
33
Sign in to the Azure portal at https://portal.azure.com.
34
34
35
35
## Create a virtual network
36
36
37
-
You'll need a virtual network to deploy both the Route Server and the Quagga NVA. Azure Route Server must be deployed in a dedicated subnet called *RouteServerSubnet*.
37
+
You need a virtual network to deploy both the Route Server and the Quagga NVA. Azure Route Server must be deployed in a dedicated subnet called *RouteServerSubnet*.
38
38
39
39
1. On the Azure portal home page, search for *virtual network*, and select **Virtual networks** from the search results.
40
40
@@ -100,7 +100,7 @@ The Route Server is used to communicate with your NVA and exchange virtual netwo
100
100
101
101
## Create Quagga network virtual appliance
102
102
103
-
To configure the Quagga network virtual appliance, you'll need to deploy a Linux virtual machine, and then configure it with this [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh).
103
+
To configure the Quagga network virtual appliance, you need to deploy a Linux virtual machine, and then configure it with this [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh).
104
104
105
105
### Create Quagga virtual machine (VM)
106
106
@@ -120,19 +120,19 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
| Username | Enter *azureuser*. Don't use *quagga*as the user name or else the setup script will fail in a later step. |
127
+
| Username | Enter *azureuser*. Don't use *quagga*for the username as it causes the setup to fail in a later step. |
128
128
| Password | Enter a password of your choosing. |
129
129
| Confirm password | Reenter the password. |
130
130
|**Inbound port rules**||
131
131
| Public inbound ports | Select **Allow selected ports**. |
132
132
| Select inbound ports | Select **SSH (22)**. |
133
133
134
134
:::image type="content" source="./media/tutorial-configure-route-server-with-quagga/create-quagga-basics-tab.png" alt-text="Screenshot of basics tab for creating a new virtual machine." lightbox="./media/tutorial-configure-route-server-with-quagga/create-quagga-basics-tab-expanded.png":::
135
-
135
+
136
136
1. On the **Networking** tab, select the following network settings:
137
137
138
138
| Settings | Value |
@@ -146,7 +146,7 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
146
146
147
147
:::image type="content" source="./media/tutorial-configure-route-server-with-quagga/create-quagga-networking-tab.png" alt-text="Screenshot of networking tab for creating a new virtual machine." lightbox="./media/tutorial-configure-route-server-with-quagga/create-quagga-networking-tab-expanded.png":::
148
148
149
-
1. Select **Review + create** and then **Create** after validation passes. The deployment of the virtual machine will take about 10 minutes.
149
+
1. Select **Review + create** and then **Create** after validation passes.
150
150
151
151
1. Once the virtual machine has deployed, go to the **Networking** page of **Quagga** virtual machine and select the network interface.
152
152
@@ -156,7 +156,7 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
156
156
157
157
:::image type="content" source="./media/tutorial-configure-route-server-with-quagga/quagga-ip-configuration.png" alt-text="Screenshot of IP configurations page of the Quagga VM.":::
158
158
159
-
1. Under **Private IP address Settings**, change the **Assignment** from **Dynamic** to **Static**, and then change the **IP address** from **10.1.4.4** to **10.1.4.10**. This IP address is used in this [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh), which will be run in a later step. If you want to use a different IP address, ensure to update the IP in the script.
159
+
1. Under **Private IP address Settings**, change the **Assignment** from **Dynamic** to **Static**, and then change the **IP address** from **10.1.4.4** to **10.1.4.10**. The [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh) that you run in a later step uses **10.1.4.10**. If you want to use a different IP address, ensure to update the IP in the script.
160
160
161
161
1. Take note of the public IP, and select **Save** to update the IP configurations of the virtual machine.
162
162
@@ -166,15 +166,25 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
166
166
167
167
1. If you are on a Mac or Linux machine, open a Bash prompt. If you are on a Windows machine, open a PowerShell prompt.
168
168
169
-
1. At your prompt, open an SSH connection to the Quagga VM. Replace the IP address with the one you took note of in the previous step.
169
+
1. At your prompt, open an SSH connection to the Quagga VM by executing the following command. Replace the IP address with the one you took note of in the previous step.
1. When prompted, enter the password you previously created for the Quagga VM.
174
176
175
-
3. When prompted, enter the password you previously created for the Quagga VM.
177
+
1. Once logged in, enter `sudo su` to switch to super user to avoid errors running the script.
176
178
177
-
1. Once logged in, enter `sudo su` to switch to super user to avoid errors running the script. Copy this [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh) and paste it into the SSH session. The script will configure the virtual machine with Quagga along with other network settings. Update the script to suit your network environment before running it on the virtual machine. It will take a few minutes for the script to complete the setup.
179
+
1. Copy and paste the following commands into the SSH session. These commands download and install this [script](https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh) to configure the virtual machine with Quagga along with other network settings.
:::image type="content" source="./media/tutorial-configure-route-server-with-quagga/routes-learned.png" alt-text="Screenshot of routes learned by Route Server.":::
217
227
218
-
1. To check the routes learned by the Quagga NVA, enter `vtysh` and then enter `show ip bgp` on the NVA. Output should look like the following:
228
+
1. To check the routes learned by the Quagga NVA, enter `vtysh` and then enter `show ip bgp` on the NVA. The output should look like the following output:
219
229
220
230
```
221
231
root@Quagga:/home/azureuser# vtysh
@@ -243,13 +253,16 @@ When no longer needed, you can delete all resources created in this tutorial by
243
253
244
254
1. On the Azure portal menu, select **Resource groups**.
245
255
246
-
2. Select the **myRouteServerRG** resource group.
256
+
1. Select the **myRouteServerRG** resource group.
257
+
258
+
1. Select **Delete a resource group**.
247
259
248
-
3. Select **Delete resource group**.
260
+
1. Select **Apply force delete for selected Virtual machines and Virtual machine scale sets**.
249
261
250
-
4. Enter *myRouteServerRG* and select **Delete**.
262
+
1. Enter *myRouteServerRG* and select **Delete**.
251
263
252
264
## Next steps
253
265
254
266
In this tutorial, you learned how to create and configure an Azure Route Server with a network virtual appliance (NVA). To learn more about Route Servers, see [Azure Route Server frequently asked questions (FAQs)](route-server-faq.md).
0 commit comments