SPRZEDAŻ: 1-800-867-1389
EN
Ta zawartość nie jest dostępna w wymaganym języku. Wersja w języku angielskim znajduje się tutaj.

Create a Virtual Network

Updated: April 14, 2015

When you create a virtual network, your services and VMs within the VNet can communicate securely with each other without having to go out through the Internet. Creating a private virtual network is a relatively fast and easy process. Because this virtual network isn’t intended to be connected to other VNets or for cross-premises configurations, you won’t need to acquire and configure a VPN device, or coordinate the IP addresses you choose with other VNets or the local network.

Don’t use this procedure to create a virtual network that will later be connected other VNets or local networks. If you want to create a secure cross-premises or hybrid connection, see About Virtual Network Secure Cross-Premises Connectivity. If you want to create a virtual network that connects to another virtual network, see Configure a VNet to VNet Connection.

  1. Log in to the Azure Management Portal.

  2. In the lower left-hand corner of the screen, click New. In the navigation pane, click Network Services, and then click Virtual Network. Click Custom Create to begin the configuration wizard.

  3. On the Virtual Network Details page, enter the information below:

    Virtual Network Details
    • Name - Name your virtual network. For example, we created the name EastUSVNet. You can create whatever name you’d like. You’ll use this virtual network name when you deploy your VMs and services, so it’s best not to make the name too complicated.

    • Location – Select the location (region) from the dropdown. The location is directly related to the physical location where you want your resources (VMs) to reside when you deploy them to this virtual network. For example, if you want your VMs to be physically located in East US, select that location region. You can’t change the region associated with your virtual network after you create it.

  4. On the DNS Servers and VPN Connectivity page, don’t make any changes. Just move forward to the next page by clicking the arrow. By default, Azure provides basic name resolution for your virtual network. It’s possible that your name resolution requirements are more complex than can be handled by the basic Azure name resolution. In that case, you may later want to add a virtual machine running DNS to your virtual network. For more information about Azure name resolution and DNS, see Name Resolution (DNS).

  5. The Virtual Network Address Spaces page is where you enter the address space that you want to use for this VNet. Unless you require a certain internal IP address range for your VMs or you want to create a specific subnet for VMs that will receive a static DIP, you don’t need to make any changes on this page. If you do want to create multiple subnets, you can do so on this page by clicking add subnet.

    Additional Information:

    • The ranges on this page contain the dynamic internal IP addresses (DIPs) that your VMs will receive when you deploy them to this virtual network. These IP addresses are for communicating within the virtual network only. They are not IP addresses for internet endpoints.

    • Because you aren’t going to connect this private virtual network to your on-premises network by using a cross-premises VPN configuration, you won’t need to coordinate these settings with your existing on-premises network IP address ranges. If you think you may want to create a cross-premises configuration later, you’ll need to coordinate the address spaces now with the ranges that already exist on your local site to avoid routing issues. Changing the ranges later can be somewhat complicated, especially if you have overlapping address ranges.

    Address Space
  6. Click the checkmark on the lower right of the Virtual Network Address Spaces page and your virtual network will begin to create. When your virtual network has been created, you will see Created listed under Status on the networks page in the Management Portal.

  7. Once your virtual network has been created, you can create VMs and PaaS instances within the virtual network. Be sure to select From Gallery when creating a new VM in order to have the option of selecting your virtual network. Note that if you have already existing VMs and PaaS instances deployed, they cannot simply be moved to your new VNet. This is because the network configuration settings that they’ll need are added during deployment.

After you create your virtual network, you can add new VMs to it. It’s important to create the virtual network first, then deploy the VM. After a VM has been deployed, you can’t move it to the virtual network without redeploying it. If you use the Management Portal to create your VMs, the interface to deploy your VM to a virtual network is only available when you select New/ Compute/ Virtual Machine/ From Gallery. When you go through the wizard to create your VM, on the Virtual machine configuration page, you’ll see Region/Affinity Group/Virtual Network. From the dropdown list, select the already-created virtual network. For more information about creating virtual machines, see Azure virtual machines.

See Also

Czy oceniasz te materiały jako pomocne?
(Pozostało znaków: 1500)
Dziękujemy za opinię.
Pokaż:
© 2015 Microsoft