Skip to content

Commit 33f2494

Browse files
Merge pull request #244470 from halkazwini/rs-quagga
Update tutorial
2 parents cf7545f + a435063 commit 33f2494

File tree

1 file changed

+35
-22
lines changed

1 file changed

+35
-22
lines changed

articles/route-server/tutorial-configure-route-server-with-quagga.md

Lines changed: 35 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,18 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: route-server
77
ms.topic: tutorial
8-
ms.date: 03/28/2023
8+
ms.date: 07/10/2023
99
ms.custom: template-tutorial, engagement-fy23
1010
---
1111

1212
# Tutorial: Configure peering between Azure Route Server and Network Virtual Appliance
1313

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.
1515

1616
In this tutorial, you learn how to:
1717

1818
> [!div class="checklist"]
19-
> * Create a virtual network with five subnets
19+
> * Create a virtual network with four subnets
2020
> * Deploy an Azure Route Server
2121
> * Deploy a virtual machine running Quagga
2222
> * Configure Route Server peering
@@ -26,15 +26,15 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
2626

2727
## Prerequisites
2828

29-
* An Azure subscription
29+
* An active Azure subscription
3030

3131
## Sign in to Azure
3232

3333
Sign in to the Azure portal at https://portal.azure.com.
3434

3535
## Create a virtual network
3636

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*.
3838

3939
1. On the Azure portal home page, search for *virtual network*, and select **Virtual networks** from the search results.
4040

@@ -100,7 +100,7 @@ The Route Server is used to communicate with your NVA and exchange virtual netwo
100100

101101
## Create Quagga network virtual appliance
102102

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).
104104

105105
### Create Quagga virtual machine (VM)
106106

@@ -120,19 +120,19 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
120120
| Region | Select **(US) East US**. |
121121
| Availability options | Select **No infrastructure required**. |
122122
| Security type | Select **Standard**. |
123-
| Image | Select an **Ubuntu**, **SUSE** or **RHEL** image. |
123+
| Image | Select an **Ubuntu** image. This tutorial uses **Ubuntu 18.04 LTS - Gen 2** image. |
124124
| Size | Select **Standard_B2s - 2vcpus, 4GiB memory**. |
125125
| **Administrator account** | |
126126
| Authentication type | Select **Password**. |
127-
| 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. |
128128
| Password | Enter a password of your choosing. |
129129
| Confirm password | Reenter the password. |
130130
| **Inbound port rules** | |
131131
| Public inbound ports | Select **Allow selected ports**. |
132132
| Select inbound ports | Select **SSH (22)**. |
133133

134134
:::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+
136136
1. On the **Networking** tab, select the following network settings:
137137

138138
| Settings | Value |
@@ -146,7 +146,7 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
146146

147147
:::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":::
148148

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.
150150

151151
1. Once the virtual machine has deployed, go to the **Networking** page of **Quagga** virtual machine and select the network interface.
152152

@@ -156,7 +156,7 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
156156

157157
:::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.":::
158158

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.
160160

161161
1. Take note of the public IP, and select **Save** to update the IP configurations of the virtual machine.
162162

@@ -166,15 +166,25 @@ To configure the Quagga network virtual appliance, you'll need to deploy a Linux
166166

167167
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.
168168

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.
170+
171+
```console
172+
173+
```
170174

171-
```console
172-
173-
```
175+
1. When prompted, enter the password you previously created for the Quagga VM.
174176

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.
176178

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.
180+
181+
```console
182+
wget "raw.githubusercontent.com/Azure/azure-quickstart-templates/master/quickstarts/microsoft.network/route-server-quagga/scripts/quaggadeploy.sh"
183+
 
184+
chmod +x quaggadeploy.sh
185+
 
186+
./quaggadeploy.sh
187+
```
178188

179189
## Configure Route Server peering
180190

@@ -211,11 +221,11 @@ ssh [email protected]
211221
Get-AzRouteServerPeerLearnedRoute @routes | ft
212222
```
213223

214-
The output should look like the following:
224+
The output should look like the following output:
215225

216226
:::image type="content" source="./media/tutorial-configure-route-server-with-quagga/routes-learned.png" alt-text="Screenshot of routes learned by Route Server.":::
217227

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:
219229

220230
```
221231
root@Quagga:/home/azureuser# vtysh
@@ -243,13 +253,16 @@ When no longer needed, you can delete all resources created in this tutorial by
243253

244254
1. On the Azure portal menu, select **Resource groups**.
245255

246-
2. Select the **myRouteServerRG** resource group.
256+
1. Select the **myRouteServerRG** resource group.
257+
258+
1. Select **Delete a resource group**.
247259

248-
3. Select **Delete resource group**.
260+
1. Select **Apply force delete for selected Virtual machines and Virtual machine scale sets**.
249261

250-
4. Enter *myRouteServerRG* and select **Delete**.
262+
1. Enter *myRouteServerRG* and select **Delete**.
251263

252264
## Next steps
253265

254266
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).
255267

268+

0 commit comments

Comments
 (0)