Planning IP Addresses for AWS VPCs and VMware SDDCs

-

Planning IP Addresses for AWS VPCs and VMware SDDCs


Before deploying your VMware Cloud on AWS SDDC, you must plan two separate blocks of IP address spaces:

  1. SDDC management CIDR block
  2. VPC CIDR block


When planning IP addresses for Amazon Web Services (AWS) Virtual Private Clouds (VPCs) and VMware Software-Defined Data Centers (SDDCs), there are a few key things to consider:

  1. IP address ranges: AWS VPCs have a default IP address range of 172.31.0.0/16, but you can specify a different range when creating a VPC. Make sure to choose non-overlapping IP address ranges for different VPCs and SDDCs to avoid conflicts.

  2. Subnetting: Utilize subnetting to divide the IP address range into smaller subnets, and assign each subnet to a different availability zone or cluster.

  3. CIDR notation: Use Classless Inter-Domain Routing (CIDR) notation to specify IP address ranges and subnets.

  4. Network address translation (NAT): Consider using NAT to enable instances in a private subnet to communicate with the internet, while still maintaining their private IP addresses.

  5. DHCP options: Configure DHCP options to automatically assign IP addresses and other network settings to instances when they launch.

  6. Reserved IP addresses Reserve a small number of IP addresses for use by specific instances or for future expansion.

Comments

Post a Comment

Popular posts from this blog

Error: "Datastore "XXX" conflicts with an existing datastore"

-
Image
  PROBLEM Recently I tried to upgrade one of my ESXi hosts from version 6.7 to 7.0 using VMware Lifecycle Manager. The upgrade gets stuck at 47%. However, when I take the remote console using iLO, I see the ESXi is already upgraded. The LCM Events and logs show that vCenter is not able to connect to the host.  I tried to connect the Host manually and got the below error: Datastore "XXX" conflicts with an existing datastore in the datacenter that has the same URL "UUID", but it is backed by different physical storage. RESOLUTION 1.     Check if the all the vmhba are visible: Run this command to see all vmhba - esxcfg-scsidevs -a or esxcli storage core adapter list 2.     Check if the vmhba drivers are compatible. In my case smartpqi driver had to be upgraded to latest version. (Microchip-smartpqi_70.4054.2.118-1OEM.700.1.0.15843807_17871815) 3.     Check if the datastore is accessible and visble from ESXi UI or ESXCLI. 4.     Remove the host from
Read more

All shared datastores failed on the host

-
  Sometimes post creating a new cluster or after re-configuring the existing cluster you might get an error on ESXi “All shared datastores failed on the host”  this can happen to you very often if you are running on HPE StoreVirtual VSA. Please follow the below steps to fix this error: 1.     At the very onset, Reconfigure the HA for the cluster. Disable and re-enable HA on Cluster Level or Right Click Host and select Reconfigure for vSphere HA. 2.     If the error still persists, then follow the next steps. 3.     Make sure you migrate all the VMs manually on the other host if the DRS is disabled on the cluster. 4.     If you have any VM running on ESXi local Datastore like HPE StoreVirtual Appliance (VSA) or Backup Proxy VM, ensure to gracefully shut them down. (For How to shutdown HPE VSA gracefully follow this KB ) 5.     Now, put the host in Maintenance Mode. 6.     Right Click Host and Remove from Inventory 7.     After the host is removed, Right Click on the cluster and click A
Read more

How to Change Hostname, IP, or DNS on vRealize Operations Manager appliance 6.x\7.x\8.x

-
Image
  Recently I had to perform rename of a few virtual appliances according to new naming conventions adopted by the organization. Going down the list I had my vROPS 8.0 to be renamed which is a VMware Photos OS appliance. Here, I bring you a simple way to rename or change your hostname, IP, Netmask, Gateway, or DNS of your VMware appliances using just one command: 1.     First and foremost, Login to vROPS admin console and bring the cluster offline. 2.     SSH into your appliance using root. 3.     Copy and paste the below command to open the vami config tool- /opt/vmware/share/vami/vami_config_net 4.     Choose option 0 to show current configurations or directly Choose Option 3 to change Hostname 5.     Enter new Hostname and reboot 6.     You may also choose other options such as changing DNS, Gateway or IP as per your requirement. If you rename the hostname, I recommend performing a Storage vMotion which renames the folder and files of the associated appliance accordingl
Read more