Virtual Lab setup – high level overview

Share This:

If anyone’s interested in the setup for virtual LAB consisting of:vsphere lab

  • vCenter (vDS, HA, DRS)
  • Esxi hosts (vhosta,b,c) / 2 Clusters – Management and Resource
  • vCloud Director / 2 orgs – IT Depts and VMware for catalog sharing
  • vCNS / vShield Manager – VXLAN for Resource cluster
  • DNS and NFS server
  • Multipath iSCSi – because it’s cool 🙂
  • vCD org VM deployed from public catalog,  connected via Routed network (EGW) connected to external network  + SNAT + DHCP

 

 

vlab.com setup for future reference before I mess it up with NSX 🙂

This is just high level overview:

unnamed0

DNS:

Reverse lookup:

Storage:

storage

 

 

 

 

iSCSI

iscsivSphere iscsi bindings:

Each host has 2 vmkernel adapters which are blinded to storage server.

Screen Shot 2015-08-07 at 11.09.10Distributed Switch and Networking:

  • vdsClusters – General pg for VM traffic
  •   DMZ – initialised so far
  •   EXT – External network pg
  •   Management – VMotion traffic
  •   Storage 1 – storage pg for iscsi binding
  •   Storage 2 – storage pg for iscsi binding
  •  IT routed pg from IT Dept org
  • VXLAN pg

Physical and Virtual nics on hosts:

Host A: (4x vNIC uplinks – host based only- VMware Workstation)

  • vmk0 – 172.16.209.128 – vDS Management
  • vmk1 –  172.16.209.225 – vDS Storage 1
  • vmk2 – 172.16.209.226 – vDS Storage 2

Host B: (4x vNIC uplinks – host based only- VMware Workstation)

  • vmk0 – 172.16.209.129 – vDS Management
  • vmk1 –  172.16.209.201 – vDS Storage 1
  • vmk2 – 172.16.209.202 – vDS Storage 2

Host A: (3x vNIC uplinks – host based only + 1x vNIC NAT – VMware Workstation,)

  • vmk0 – 172.16.209.185 – vDS Management
  • vmk1 –  172.16.209.203 – vDS Storage 1
  • vmk2 – 172.16.209.204 – vDS Storage 2
  • vmk3 – 192.168.44.46 – vDS EXT
  • vmk4 – 192.168.44.20 – VXLAN network

Resource Cluster (Enabled for VXLAN) – consist of 2 organisations:

– IT Department and VMware vCD

VMware vCD hold catalogs that are being shared with other organizations.

IT Department has vSM VM with IP of 10.0.0.20,that connects to Edge GW (192.168.44.50) which connects to EXT (external network 192.168.44.0/24)

Screen Shot 2015-08-07 at 12.52.22

GW settings

 

The SNAT allows the VM to be ping-able from external network. (via EGW)

SNAT

 

Pinging the VM (10.0.0.20 NAT -> 192.168.44.51) from external network via Routed IT network (IT_ORG_GW)

C:\WINDOWS\system32>ping 192.168.44.51

Pinging 192.168.44.51 with 32 bytes of data:
Reply from 192.168.44.51: bytes=32 time=4ms TTL=64
Reply from 192.168.44.51: bytes=32 time=1ms TTL=64
Reply from 192.168.44.51: bytes=32 time=3ms TTL=64
Reply from 192.168.44.51: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.44.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 2ms

Leave a comment

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.