Creating Network Interfaces
A network interface enables an Azure VM to communicate with the Internet, Azure, and other on-premises resources. A VM can have one or more network interfaces.
For Aruba Virtual Gateway deployment, Aruba recommends that you create a separate network interface for each traffic type and map these to subnets in the following order:
- NIC1—Management traffic
- NIC2—Internet traffic– Requires a Public IP for connectivity to Aruba Central
- NIC3—VPN traffic
- NIC4—LAN traffic
- To create network interfaces follow these steps:
- In the Azure portal, click > .
- On the page, enter network interface in the search box to access the page.
- Click .
- In the window, configure the following parameters:
- —Enter a name for the interface; for example, NIC1.
- —Select the VNET to which you want to add the interface.
- —Select the subnet that you want assign to the interface.
- — Based on your configuration requirements, select either or addressing.
- —Select the network security group to which you want to attach this interface.
- —Select the subscription.
- —Select the resource group to which you want to map the interface.
- —Select the geographic location of your VNET.
- Click .
- Repeat these steps to create additional network interfaces, for NIC2, NIC3, and NIC4.
Figure 1 Creating Network Interfaces
- To enable IP forwarding for NIC2, NIC3, and NIC4, follow these steps:
- In the Azure portal, go to > .
- Select the resource group associated to your VNET.
- From the list of network interfaces, select the NIC.
- Under , select .
- Configure the following parameters:
— Set to .
Figure 2 Enabling IP forwarding
- To add Public IP to iNeT, follow these steps:
- Under , select .
- Set to .
- Click Save.
- Click the listed ipconfig1.
- In the new window, set the Public IP address as Enabled.
- Click Save.
No comments:
Post a Comment