70 533 - Module 02 : Implementing and Managing Virtual Networks
•Télécharger en tant que PPTX, PDF•
0 j'aime•1,067 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à 70 533 - Module 02 : Implementing and Managing Virtual Networks
Similaire à 70 533 - Module 02 : Implementing and Managing Virtual Networks (20)
Dernier
Dernier (20)
70 533 - Module 02 : Implementing and Managing Virtual Networks
- 1. IMPLEMENTING MICROSOFT AZURE INFRASTRUCTURE SOLUTIONS Microsoft Certified Specialist | Microsoft Azure Infrastructure Solutions
- 2. WELCOME NOTE
- 3. MODULE 2: IMPLEMENTING AND MANAGING VIRTUAL NETWORKS • Planning Virtual Networks • Administering Virtual Networks • Inter-Site Connectivity • Lab : Implementing and Managing Virtual Networks
- 4. 1.1 | PLANNING VIRTUAL NETWORKS • Azure Virtual Network glossary
- 5. 1.1 | PLANNING VIRTUAL NETWORKS • Do you need a virtual network ?
- 6. 1.1 | PLANNING VIRTUAL NETWORKS • Specific considerations • Name Resolution • Enhanced security and isolation • Extended trust and security boundary • Extend your on-premises network to the cloud • Use persistent private IP addresses
- 7. 1.2 | ADMINISTERING VIRTUAL NETWORKS • Demo • Using Portals to manage virtual networks • Using PowerShell to manage virtual networks
- 8. 1.2 | ADMINISTERING VIRTUAL NETWORKS • Demo • Using Portals to manage virtual networks • Using PowerShell to manage virtual networks
Notes de l'éditeur
- Settings include reserved IP addresses, access control list (ACL), internal name resolution, DNS at the cloud service level, load balancing endpoints, HTTP and TCP health probes, public IPs, firewall rules, direct server return, and Keep Alive
- A virtual network is a network overlay that you can configure in Azure. VMs and services that are part of the same virtual network can access each other. However, services outside the virtual network have no way to identify or connect to services hosted within virtual networks unless you decide to configure that specific type of connection, as in the case of VNet to VNet configurations. This provides an added layer of isolation to your services. Azure Virtual Network also lets you extend your network into Azure and treat deployments as a natural extension to your on-premises network. Whether you need a virtual network depends entirely on what you are trying to do Source: http://msdn.microsoft.com/library/azure/jj156007.aspx
- A virtual network is a network overlay that you can configure in Azure. VMs and services that are part of the same virtual network can access each other. However, services outside the virtual network have no way to identify or connect to services hosted within virtual networks unless you decide to configure that specific type of connection, as in the case of VNet to VNet configurations. This provides an added layer of isolation to your services. Azure Virtual Network also lets you extend your network into Azure and treat deployments as a natural extension to your on-premises network. Whether you need a virtual network depends entirely on what you are trying to do Source: http://msdn.microsoft.com/library/azure/jj156007.aspx
- When deciding if you need a virtual network, there are a few other things to consider. You may also want to create a virtual network for the following reasons: Name resolution: If you want to connect to your VMs and cloud services by hostname or SRV records, rather than using the IP address and/or port number, you’ll need name resolution. When you deploy VMs and cloud services to a virtual network you can use Azure-provided name resolution or your own DNS solution, depending on your name resolution requirements. For information about name resolution options, see Name Resolution (DNS). Enhanced security and isolation: Since each virtual network is run as an overlay, only virtual machines and services that are part of the same network can access each other. Services outside the virtual network have no way to identify or connect to services hosted within virtual networks. This provides an added layer of isolation to your services. Extended trust and security boundary: The virtual network extends the trust boundary from a single service to the virtual network boundary. You can create several cloud services and virtual machines within a single virtual network and have them communicate with each other without having to go through the internet. You can also setup services that use a common backend database tier or use a shared management service. Extend your on-premises network to the cloud: You can join VMs in Azure to your domain running on-premises. You can access and leverage all on-premises investments around monitoring and identity for your services hosted in Azure. Use persistent private IP addresses: Virtual machines within a VNet will have a stable private IP address. We assign an IP address from the address range you specify and offer an infinite DHCP lease on it. You can also choose to configure your virtual machine with a specific private IP address from the address range when you create it. This ensures that your virtual machine retains its private IP address even when Stop/Deallocated. See Configure a static internal IP address for a VM. Source: http://msdn.microsoft.com/library/azure/jj156007.aspx
- http://msdn.microsoft.com/en-us/library/azure/jj156206.aspx
- http://msdn.microsoft.com/en-us/library/azure/jj156206.aspx