Skip to main content

Onboarding experience of VMware ON AWS in Production Environment-Part2

 VMware ON AWS Deployment - Requirements. 

As mentioned in the previous post , when we are set with the project objective, we need to prepare the items mentioned in the VMC deployment checklist. Some of the basic requirements are, 

  1. The AWS account details - When we deploy our SDDC on VMware Cloud on AWS, it is created within an AWS account and a VPC dedicated to your organisation and managed by VMware. We must also connect the SDDC to an AWS account belonging to us, called the customer AWS account . This connection allows our SDDC to access AWS services belonging to our org  account.
  2. SDDC Management subnets - This is the most critical part of the deployment. Choosing the right network for SDDC and connect back to ON-Premise network (check with network team to make sure you provide unique range of CIDR, ASN etc to avoid conflicts) 
  3. Connectivity to On-Premise DC and VMC - There are different ways to connect to the On-Prem DC, using IPsec VPN, AWS Direct Connect, Hybrid Cloud Extension (HCX) /HCX Connector, or custom MPLS, network backend connections. ( example AT &T Netbond) 
  4. Region where we deploy the VMC SDDC stack ( we need to choose from AWS Regions) 
  5. Cluster type - We have an option to choose either Stretched or non-Stretched Cluster 
  6. Number of hosts do we need in the SDDC cluster ( remember we can start from 1 host but the recommended settings for production cluster is minimum of 3 nodes ) 

Getting Started with Deployment: 

Once we have the AWS account details ready, we need to provide that to the VMware backend team to provide us with the subscription. These subscriptions are mapped to our AWS account and ENI's to be attached at the later stage of this deployment 

Once we have a "Welcome" email from VMware, we are ready to go with the deployment. Login to VMC console and click on "Create SDDC" and provide the details as captured in the deployment checklist. 

The SDDC Stack deployment is fully automated and the creation of Datacenter, Cluster, addition of nodes, creation and configuration of vSAN datastore, deployment of NSX Components, etc are fully automatic. 

The wait of approx 2 hours would results us with the fully working setup. 

Post deployment Steps: 

Once the deployment is successful login to vmc.vmware.com console to perform the next steps. 

1. The landing page : In this page, we can check the summary of our deployed SDDC components, region where we deployed the stack, etc. 


2. Click on View details to review the connectivity details and configuration page. Note: The connection to on-premise is not yet done - we need to perform additional steps which we cover in the following sections of the blog post. 


3. VMC Network diagram : 

Below is a more detailed view of how NSX is deployed within VMware Cloud on AWS (diagram courtesy of Gilles Chekroun)


We will see how to connect to ON-Premise datacenter from our VMC setup in our next blog post 

Labels:

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...
Read more

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...
Read more

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely av...
Read more