Skip to content

Commit 0697c41

Browse files
committed
changed faq and partner list
1 parent 42ff18a commit 0697c41

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/virtual-wan/virtual-wan-faq.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -324,7 +324,7 @@ Yes. Virtual WAN prefers ExpressRoute over VPN for traffic egressing Azure. Howe
324324

325325
### When a Virtual WAN hub has an ExpressRoute circuit and a VPN site connected to it, what would cause a VPN connection route to be preferred over ExpressRoute?
326326

327-
When an ExpressRoute circuit is connected to virtual hub, the Microsoft Edge routers are the first node for communication between on-premises and Azure. These edge routers communicate with the Virtual WAN ExpressRoute gateways that, in turn, learn routes from the virtual hub router that controls all routes between any gateways in Virtual WAN. The Microsoft Edge routers process virtual hub ExpressRoute routes with higher preference over routes learned from on-premises.
327+
When an ExpressRoute circuit is connected to a virtual hub, the Microsoft Edge routers are the first node for communication between on-premises and Azure. These edge routers communicate with the Virtual WAN ExpressRoute gateways that, in turn, learn routes from the virtual hub router that controls all routes between any gateways in Virtual WAN. The Microsoft Edge routers process virtual hub ExpressRoute routes with higher preference over routes learned from on-premises.
328328

329329
For any reason, if the VPN connection becomes the primary medium for the virtual hub to learn routes from (e.g failover scenarios between ExpressRoute and VPN), unless the VPN site has a longer AS Path length, the virtual hub will continue to share VPN learned routes with the ExpressRoute gateway. This causes the Microsoft Edge routers to prefer VPN routes over on-premises routes.
330330

@@ -336,11 +336,11 @@ The current behavior is to prefer the ExpressRoute circuit path over hub-to-hub
336336

337337
* Contact the product team to take part in the gated public preview. In this preview, traffic between the 2 hubs traverses through the Azure Virtual WAN router in each hub and uses a hub-to-hub path instead of the ExpressRoute path (which traverses through the Microsoft Edge routers/MSEE). To use this feature during preview, email **[email protected]** with the Virtual WAN IDs, Subscription ID, and the Azure region. Expect a response within 48 business hours (Monday-Friday) with confirmation that the feature is enabled.
338338

339-
### When there's an ExpressRoute circuit connected as a bow-tie to a Virtual WAN hub and a non Virtual WAN (customer-managed) VNet, what is the path for the non Virtual WAN VNet to reach the Virtual WAN hub?
339+
### When there's an ExpressRoute circuit connected as a bow-tie to a Virtual WAN hub and a non Virtual WAN VNet, what is the path for the non Virtual WAN VNet to reach the Virtual WAN hub?
340340

341341
The current behavior is to prefer the ExpressRoute circuit path for non Virtual WAN VNet to Virtual WAN connectivity. It is recommended that the customer [create a Virtual Network connection](howto-connect-vnet-hub.md) to directly connect the non Virtual WAN VNet to the Virtual WAN hub. Afterwards, VNet to VNet traffic will traverse through the Virtual WAN router instead of the ExpressRoute path (which traverses through the Microsoft Enterprise Edge routers/MSEE).
342342

343-
### Can hubs be created in different resource group in Virtual WAN?
343+
### Can hubs be created in different resource groups in Virtual WAN?
344344

345345
Yes. This option is currently available via PowerShell only. The Virtual WAN portal requires that the hubs are in the same resource group as the Virtual WAN resource itself.
346346

@@ -410,7 +410,7 @@ You’ll only be able to update your virtual hub router if all the resources (ga
410410
If the update fails for any reason, your hub will be auto recovered to the old version to ensure there is still a working setup.
411411

412412
>[!NOTE]
413-
> The user will need to have an **owner** or **contributor** role to see an accurate status of the hub router version. If a user is assigned a **reader** role to the Virtual WAN resource, then Azure portal will display to that user that the hub router needs to be upgraded to the latest version, even if the hub is already on the latest version.
413+
> The user will need to have an **owner** or **contributor** role to see an accurate status of the hub router version. If a user is assigned a **reader** role to the Virtual WAN resource and subscription, then Azure portal will display to that user that the hub router needs to be upgraded to the latest version, even if the hub is already on the latest version.
414414
415415
### Is there a route limit for OpenVPN clients connecting to an Azure P2S VPN gateway?
416416

includes/virtual-wan-nva-hub-partners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The following SD-WAN connectivity Network Virtual Appliances can be deployed in
1515
|[VMware SD-WAN ](https://sdwan.vmware.com/partners/microsoft) | [VMware SD-WAN in Virtual WAN hub deployment guide](https://kb.vmware.com/s/article/82746). The managed application for deployment can be found at this [Azure Marketplace link](https://azuremarketplace.microsoft.com/marketplace/apps/velocloud.vmware_sdwan_in_vwan).| Yes|
1616
| [Versa Networks](https://versa-networks.com/partners/microsoft-azure.php) | If you're an existing Versa Networks customer, log on to your Versa account and access the deployment guide using the following link [Versa Deployment Guide](https://docs.versa-networks.com/Special:AuthenticationProviders?returntotitle=Getting_Started%2FDeployment_and_Initial_Configuration%2FBranch_Deployment%2FInitial_Configuration%2FInstall_a_VOS_Cloud_Gateway_on_an_Azure_Virtual_WAN). If you're a new Versa customer, sign-up using the [Versa preview sign-up link](https://versa-networks.com/demo/). | Yes |
1717
| [Fortinet SD-WAN](https://www.fortinet.com/products/next-generation-firewall) | [Fortinet SD-WAN deployment guide](https://aka.ms/fortinetsdwandeploy). The managed application for this deployment can be found at this [Azure Marketplace Link](https://portal.azure.com/#create/fortinet.fortigate_vwan_nvamanagedfgtvwan). | No|
18-
| [Aruba EdgeConnect](https://www.arubanetworks.com/products/sd-wan/edgeconnect) | [Aruba EdgeConnect SD-WAN deployment guide](https://aka.ms/arubasdwandeploy).| No|
18+
| [Aruba EdgeConnect](https://www.arubanetworks.com/products/sd-wan/edgeconnect) | [Aruba EdgeConnect SD-WAN deployment guide](https://aka.ms/arubasdwandeploy). **Currently in Preview**: [Azure Marketplace link] (https://ms.portal.azure.com/#create/silver-peak-systems.aruba_edgeconnect_enterprise_in_vwan_apparuba_edgeconnect_enterprise_in_vwan_v1)| No|
1919

2020
The following security Network Virtual Appliance can be deployed in the Virtual WAN hub. This Virtual Appliance can be used to inspect all North-South, East-West, and Internet-bound traffic.
2121

0 commit comments

Comments
 (0)