Skip to content

virtual-wan-connect-vnet-hub-include.md

Latest commit

 

History

History
30 lines (24 loc) · 3.42 KB

virtual-wan-connect-vnet-hub-include.md

File metadata and controls

30 lines (24 loc) · 3.42 KB
author cherylmc
ms.author cherylmc
ms.date 12/12/2024
ms.service azure-virtual-wan
ms.topic include

  1. In the Azure portal, go to your Virtual WAN In the left pane, select Virtual network connections.

  2. On the Virtual network connections page, select + Add connection.

  3. On the Add connection page, configure the connection settings. For information about routing settings, see About routing.

    • Connection name: Name your connection.

    • Hubs: Select the hub you want to associate with this connection.

    • Subscription: Verify the subscription.

    • Resource group: Select the resource group that contains the virtual network to which you want to connect.

    • Virtual network: Select the virtual network you want to connect to this hub. The virtual network you select can't have an already existing virtual network gateway.

    • Propagate to none: This is set to No by default. Changing the switch to Yes makes the configuration options for Propagate to Route Tables and Propagate to labels unavailable for configuration.

    • Associate Route Table: From the dropdown, you can select a route table that you want to associate.

    • Propagate to labels: Labels are a logical group of route tables. For this setting, select from the dropdown.

    • Static routes: Configure static routes, if necessary. Configure static routes for Network Virtual Appliances (if applicable). Virtual WAN supports a single next hop IP for static route in a virtual network connection. For example, if you have a separate virtual appliance for ingress and egress traffic flows, it would be best to have the virtual appliances in separate VNets and attach the VNets to the virtual hub.

    • Bypass Next Hop IP for workloads within this VNet: This setting lets you deploy NVAs and other workloads into the same VNet without forcing all the traffic through the NVA. This setting can only be configured when you're configuring a new connection. If you want to use this setting for a connection you've already created, delete the connection, then add a new connection. See bypass next hop IP documentation for more information about routing behavior related to this setting.

      The bypass next hop IP setting does not apply to routes learnt via BGP peering from a NVA deployed in a Virtual Network directly connected to the Virtual Hub. This is because the virtual hub automatically learns about system routes associated with addresses in the spoke virtual network when the spoke virtual network connection is created. These automatically learned system routes are preferred over routes learned by the hub through BGP. The system routes can only be overriden by static routes.

    • Propagate static route: This setting lets you propagate static routes defined in the Static routes section to route tables specified in Propagate to Route Tables. Additionally, routes will be propagated to route tables that have labels specified as Propagate to labels. These routes can be propagated inter-hub, except for the default route 0/0.

  4. Once you've completed the settings you want to configure, select Create to create the connection.