Skip to content

Latest commit

 

History

History
118 lines (80 loc) · 9.09 KB

pre-deployment-checklist.md

File metadata and controls

118 lines (80 loc) · 9.09 KB
title description ms.topic ms.date
Azure VMware Solution pre-deployment checklist
Use this checklist as part of the pre-deployment planning process.
how-to
10/02/2020

Azure VMware Solution pre-deployment checklist

You'll use this pre-deployment checklist during the planning phase.

Success criteria

Define what tests you are going to run and the expected outcome.

Fundamental information needed Your response
Deploy SDDC                
Create virtual network                
Create jump box                
Create virtual network gateway                
Connect ExpressRoute Global Reach                
Log into NSX Manager and vCenter                
Primary information needed Your response
Create DHCP server                
Create network segments                
Scale (add or delete nodes)                
Deploy VMware HCX                
Create virtual machines (VMs)                
Enable internet                
VM migration from on-premises to private cloud                
Additional information needed Your response
VM snapshot operations                
Deploy NSX-T load balancer                
Azure integration
  • Shared content library
  • Security integration
  • Upload ISO
  • Build from ISO
  • Azure Backup
               
Micro segmentation                
Routing                

Azure VMware Solution information

Azure subscription

Provide the subscription name and subscription ID for Azure VMware Solution. The subscription can be new or existing subscription. Do not use a Dev/Test Subscription.

Information needed Your response
Subscription and ID                
Subscription with an EA ☐ Yes   ☐ No
Resource Group name                
Location ☒ East US
Azure admin

Provide the name and contact of the admin
assigned to enable the service from marketplace.
Contributor is the minimum role required to
register the Azure VMware Solution resource provider.
               

On-premises VMware information

Information needed Your response
vSphere version                
vCenter version                
vCenter admin                
L2 extension

If extending L2 networks with VMware HCX,
provide the on-premises network you will extend.
               
vSwitch

Provide the type of vSwitch used throughout the environment.
☐ Standard   ☐ Distributed

If using Standard, then VMware HCX is not available.
DNS and DHCP

A proper DNS and DHCP infrastructure is required.
It is recommended to use the DHCP service built into
NSX or use a local DHCP server in the private cloud
rather than routing broadcast DHCP traffic over the
WAN back to on-premises. For more information,
see How to create and manage DHCP in Azure VMWare Solution.
               

Networking - Azure VMware Solution infrastructure

The data needed is to help you meet the Azure VMware Solution networking needs for stand-up and initial network testing.

Information needed Your response
Azure VMware Solution CIDR

Required for vSphere hosts, vSAN, and management
networks in Azure VMware Solution. For more
information, see Routing and subnet considerations.
               
Azure VMware Solution workload CIDR (optional)

Assign a network to be used in Azure VMware
Solution for initial testing. Virtual machines
will be deployed to validate network connectivity
from/to Azure VMware Solution.
               

Networking - connect Azure VMware Solution to Azure Virtual Network

The data needed for after the Azure VMware Solution cluster is stood up it can be connected to Azure via an ExpressRoute circuit, which is part of the Azure VMware Solution service.

Information needed Your response
Jump box - Windows Server                
Create virtual network                
Create gateway subnet                
Create virtual network gateway

For more information, see Create the virtual network gateway.
               

Networking - connect Azure VMware Solution to an on-premises datacenter

Information needed Your response
ExpressRoute peering CIDR

The /29 CIDR address block.
               
ExpressRoute authorization key and resource ID

Provide an authorization key and resource ID,
which is generated from the current ExpressRoute
circuit that connects to the on-premises datacenter.
               
Direction of default route

Should the virtual machines in Azure VMware Solution
access the internet via Azure VMware Solution provided
internet, or come back across the ExpressRoute circuit to
on-premises for the default route?
               
Network ports required to communicate with the service

For more information, see Required network ports.
               

Networking - VMware HCX

Information needed Your response
Network ports

If there is a firewall, make sure the required network ports
are opened between on-premises and Azure VMware Solution.
               
DNS

For information on configuring DNS,
see Networking - Azure VMware Solution infrastructure.
               
VMware HCX CIDRs

You require two /29 CIDR blocks, which are used for
the VMware HCX infrastructure components on-premises.