Skip to content

Commit 8b7020d

Browse files
committed
ipallocationwaiting
1 parent 667a9f3 commit 8b7020d

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/virtual-wan/how-to-network-virtual-appliance-add-ipconfigurations.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: 'Azure Virtual WAN: Manage IP Configurations for Network Virtual Appliance (NVA) in the hub'
33
description: Learn how to manage IP configurations for Network Virtual Appliance in the Virtual WAN hub.
44
author: wtnlee
5-
ms.service: virtual-wan
5+
ms.service: azure-virtual-wan
66
ms.topic: how-to
77
ms.date: 01/04/2023
88
ms.author: wellee
@@ -72,7 +72,7 @@ The following section describes known limitations and considerations associated
7272
* 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.
7373
* Associating an additional IP configuration to your NVA allocates additional IP addresses to all NVA instances.
7474
* 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.
7676
* 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.
7777

7878
## Creating IP configurations
@@ -94,6 +94,7 @@ The following section describes the steps needed to add additional IP configurat
9494
:::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":::
9595
1. Type in the name of the new IP configuration and select **Save**.
9696
:::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).
9798

9899
## Checking IP addresses assigned to a VM instance
99100
1. Select **Instances** under settings.

0 commit comments

Comments
 (0)