What is Azure VMware Solution (AVS):
Azure VMware Solution enables a fast path to the cloud, seamlessly migrating or extending existing VMware workloads from on-premises environments to Azure without the risk of re-architecting applications or retooling operations.
Top 5 typical business challenges:
Top 5 governance framework for AVS:
- Incompatible, non-interoperable stacks
- Cross-site networking and security issues
- Application dependency mapping delays
- Business Disruption
- Migrating Large scale to VMC
Access control and security
Compliance and policies
Unified hybridity visibility
Automated integration Ops
Foremost 10 steps to plan the foundation for AVS:
Request host quota and enable Azure VMware Solution
Identify the subscription, resource group, region/ location
Identify the size of hosts required
Determine the number of clusters and hosts required
Define the IP address segment for private cloud management with /22 CIDR in NSX-T in AVS
Define the IP address segment for VM workloads
Define the virtual network gateway in NSX-T in AVS
Define VMware HCX network segments
Extend specific networks to AVS.
Networks must connect to a vSphere Distributed Switch (vDS) in your on-premises VMware environment
Prime 10 steps to configure AVS:
- Deploy the on-premises VMware HCX OVA (VMware HCX Connector).
- Pair your on-premises VMware HCX Connector with your Azure VMware Solution HCX Cloud Manager.
- Configure the interconnect (network profile, compute profile, and service mesh).
- Configure Azure ExpressRoute Global Reach is between on-premises and AVS private cloud ExpressRoute circuits.
- Connect to Azure Virtual Network with ExpressRoute
- Create an ExpressRoute authorization key in the on-premises ExpressRoute circuit
- Ensure that all gateways, including the ExpressRoute provider's service, supports 4-byte Autonomous System Number (ASN)
- AVS uses 4-byte public ASNs for advertising routes
- Peer private cloud to on-premise
- Identify the VMs need to migrate to AVS
Top 5 lessons learned during AVS planning exercise:
- Appropriate assessment was not performed to determine the number of vRA instances exist in on-premise (if any)
- Adequate planning was not done for network segment requirements for AVS deployment.
- Proper sizing of AVS hosts and cluster requirements were not analyzed to meet business demand.
- Network throughput requirement was not analyzed proactively before the go-live.
- All dependencies (client and vendor) were not identified before workload migration to AVS.
I just vRealized that VMware HCX is one of the key component in AVS.
Top 5 HCX advantages on AVS:
- Driving Large scale migration
- HCX for Protection to DR side
- Secure migration and DR traffic
- Network and IP preservation
- High scale L2 Extensibility
Top 5 benefits from HCX on AVS:
- Save time and lower costs
- Reduced risk and Minimize disruption
- Optimize control with existing VMware skills
- Accelerate flexibility and resiliency
- Empower IT with choices
Top 10 functionalities of HCX on AVS:
- Hybrid interconnect services
- WAN optimization services
- Cross cloud vMotion migration services
- Bulk migration services
- Replication assisted vMotion migration services
- Network extension services
- Disaster recovery services
- OS assisted migration services
- Continues replication
- Simplifies hybridity
Please watch out for next blog for more details on HCX.