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/virtual-wan/how-to-network-virtual-appliance-add-ipconfigurations.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: 'Azure Virtual WAN: Manage IP Configurations for Network Virtual Appliance (NVA) in the hub'
3
3
description: Learn how to manage IP configurations for Network Virtual Appliance in the Virtual WAN hub.
4
4
author: wtnlee
5
-
ms.service: virtual-wan
5
+
ms.service: azure-virtual-wan
6
6
ms.topic: how-to
7
7
ms.date: 01/04/2023
8
8
ms.author: wellee
@@ -72,7 +72,7 @@ The following section describes known limitations and considerations associated
72
72
* Reference your NVA provider's documentation for the full list of supported use cases and for instructions on how to properly configure NVA operating systems to use additional allocated IP addresses. Azure allocates and assigns additional IP addresses to your NVA Virtual Machine instances and doesn't modify any NVA operating system internal configurations.
73
73
* Associating an additional IP configuration to your NVA allocates additional IP addresses to all NVA instances.
74
74
* The primary IP configuration associated to each NIC can't be modified or deleted.
75
-
* Azure automatically allocates IP addresses to each Network Virtual Appliance instance. You can't choose the IP addresses allocated to each NVA instance. Private IP addresses are allocated from the Virtual WAN hub address space that is reserved for Integrated NVAs in the hub. Public IP addresses are allocated from the set of available Azure-owned public IPs in the NVAs deployed Azure region.
75
+
* Azure automatically allocates IP addresses to each Network Virtual Appliance instance. You can't choose the IP addresses allocated to each NVA instance. Private IP addresses are allocated from a subnet within the Virtual WAN hub address space that is reserved for Integrated NVAs in the hub. Public IP addresses are allocated from the set of available Azure-owned public IPs in the NVAs deployed Azure region.
76
76
* IP addresses aren't preserved. Once an IP configuration is removed from a NIC, re-creating the IP configuration doesn't guarantee the same public and/or private IP addresses are allocated to the NVA.
77
77
78
78
## Creating IP configurations
@@ -94,6 +94,7 @@ The following section describes the steps needed to add additional IP configurat
94
94
:::image type="content" source="./media/network-virtual-appliance-address/add-configuration-button.png"alt-text="Screenshot showing how to find button used to manage NVA IP configurations."lightbox="./media/network-virtual-appliance-address/add-configuration-button.png":::
95
95
1. Type in the name of the new IP configuration and select **Save**.
96
96
:::image type="content" source="./media/network-virtual-appliance-address/add-and-save-configuration.png"alt-text="Screenshot showing how to create and save new NVA IP configurations."lightbox="./media/network-virtual-appliance-address/add-and-save-configuration.png":::
97
+
1. After the operation completes, reference your NVA provider's documentation for any configurations needed for the NVA operating system to use the newly allocated IP address(es).
97
98
98
99
## Checking IP addresses assigned to a VM instance
0 commit comments