Sunday, January 8, 2017

VMware NSX Setup Script

Description


It contains Power CLI Scripts(16) to quickly setup VMware NSX Lab to perform testing for basic Testing It takes input from JSON file and performs following tasks  

  1. NSX Manager Deployment
  2. Register VC in NSX Manager
  3. Assign NSX License
  4. Prepare ESXi Host(s) in Cluster
  5. Create IP Pool for Controller & VTEP
  6. Deploy Controller ( As it is lab currently deploying only 1 , Can we use same script to deploy multiple if required)
  7. Add/Create Segment
  8. Configure VXLAN
  9. Create Transport Zone
  10. Create Transit Logical Switch to interconnect DLR and Edge
  11. Deploy DLR with uplink from Transit Logical Switch
  12. Deploy ESG with Uplink from VLAN backed PG and Internal NIC from Transit Logical Switch
  13. Configure Default Gateways on DLR and Edge
  14. Configure OSPF in DLR
  15. Configure  OSPF in Edge


Download


It can be downloaded from GitHub


Usage Instructions

  1. Create a folder called "Scripts" under C:\ for windows ( I haven't had chance to test it in Linux) and save all the scripts along with JSON file
  2. Modify the JSON file as per your environment
  3. Open Power CLI and navigate to the C:\Scripts and execute "nsxsetup.ps1"


Pre-requisites

  1. Management VC – VC where NSX Manager will be deployed. It could be same as Compute VC
  2. Compute VC -   VC which will be integrated with NSX
  3. VDS – Distributed Switch on Compute VC along with Port Group with MTU 1600
  4. Datastore(s) – Datastores where all the VMs will be deployed i.e. NSX Manager , NSX Controller, NSX DLR & NSX Edge. Details needs to be updated in JSON file
  5. IP Details – All the IP details for all the VMs deployed. Details needs to be updated in JSON file


Demo Link


I have recorded Demo for the Script . ### No Audio. Visual Updates Only ###


Friday, January 6, 2017

VCSA 6.5 CLI Installation

You can use the CLI installer to perform a silent deployment of a vCenter Server Appliance or Platform Services Controller appliance on an ESXi host or vCenter Server instance.

Reference Documentation



Before we being we need to ensure we do following

  1. Download and Mount the vCenter Server Appliance Installer
  2. Prepare Your JSON Configuration File for CLI Deployment


Prepare JSON File


Browse to the template directory and choose your appropriate json file. I  will be deploying embedded VCSA on VC in my lab. Update the file with your environment specific details. Following is my JSON file



Installation


Mount the ISO as CD-ROM and Browse the vcsa-deploy.exe setup file
Run the deployment command
vcsa-deploy install --accept-eula --acknowledge-ceip optional_arguments path_to_the_json_file
You might get warnings for the certificate thumb print  which you need to Accept
You could provide additional argument so that you don’t have this warning. I wanted to demonstrate hence I ran with minimal arguments


Once you Accept and Continue it will deploy the VCSA Appliance


Once it is deployed it will Power ON the VM and start installing & configuring services




It should take about 20-25 mins to finish the setup post which you should be able to access it via web client



You should be able to access vCenter it via Web Client.

Caution - As of vSphere 6.5 Windows Client is not Supported


Wednesday, December 28, 2016

VCSA 6.5 Installation

In this post I will share the installation procedure for the GUI deployment

It includes a series of two stages. 


Stage 1 - OVA Deployment


The first stage walks you through the deployment wizard to choose the deployment type and appliance settings. This stage completes the deployment of the OVA file on the target server with the deployment type and appliance settings that you provide

Stage 2 - Appliance Setup


The second stage walks you through the setup wizard to configure the appliance time synchronization and vCenter Single Sign-On. This stage completes the initial setup and starts the services of the newly deployed appliance.

Installation Observations


I thought of sharing what I observed during installation in advance before starting the deployment and setup. I got Install failure – VMware Identity Management Service error on first boot in Stage 2 of installation

For lab I have never used host name for VCSA and always used IP as the hostname and Gateway as DNS. It has worked till 6.0 U2 however it caused the error I mentioned above. When I researched I landed up to following community post


As a work around I tried following

  1. Left FQDN field blank as it is says its optional it should take IP as the hostname – Failed                                                         It took localhost as the hostname and I got the same error for VIDM
  2. Use DHCP for IP Address without DNS – Success
  3. Use DNS Server IP as itself (i.e. same IP as VCSA IP) – Success                                                                                             Community Thread has a work around mentioned by VMware Support however that would require manual intervention which will not go well with automated installation in lab



Stage 1 – OVA Deployment


Mount the ISO as CD-ROM and navigate to the folder “vcsa-ui-installer\win32” and click installer.exe


It will open up the installer and you can choose Install the VCSA



As this is for our lab environment I have chosen as embedded PSC however when deploying in Production you should choose the appropriate








I have chosen Deployment Size as Small as it is my lab howeer in Production it should depend on your environment




Note – Please refer the observations section of my post to see what errors I came across










Once you have the above screen means it is completed the Deployment Stage and the 2nd Stage will start i.e. Appliance Setup

Stage 2 – Appliance Setup









I noticed that it took about 20-25 mins to finish and you should be able to access using web client



In next post I will show the proceudre how to install Embedded VCSA using CLI Installer


Wednesday, December 21, 2016

VMware NSX Not Supported with vSphere 6.5

While researching compatibility between NSX and latest vSphere version I observed that All versions of NSX for vSphere including 6.1.x and 6.2.x are currently not supported with VMware vSphere 6.5. For more information, see KB 2147548

I cross verified on VMware Product Interoperability Matrix as well




Tuesday, December 20, 2016

Operations Differences for vSphere & SRM versions 6.5 & 6.0

Updated Table to include 6.5. If you want to check out for previous version please refer my earlier blog - http://bit.ly/295GRG9


Component
6.5
6
Virtual CPUs per virtual machine (Virtual SMP)
128
128
RAM per virtual machine
6 TB
4 TB
Virtual disk size
62 TB
62 TB
Virtual Disks per virtual machine
per Host 2048
per Datastore Cluster 9000
per Host 2048
per Datastore Cluster 9000
Logical CPUs per host
576
480
Virtual machines per host
1024
1024
Virtual CPUs per host
4096
4096
Virtual CPUs per core
32
32
RAM per host
12 TB
6 TB
LUN size
64 TB
64 TB
Raw Device Mapping size (virtual compatibility)
62TB
62TB
Raw Device Mapping size(physical compatibility)
64TB
64TB
Virtual machines per cluster
8000
8000
Resource pools per cluster
1600
1600
Hosts per vCenter Server
2000
1000
Number of host per datacenter
2000
500
Powered-on virtual machines per vCenter Server
25000
10000
Registered virtual machines per vCenter Server
35000
15000
Distributed switches per vCenter
128
128
Single Sign On (SSO)
Required
Required

VMware Site Recovery Manager (SRM)
Protected virtual machines in total
5000
5000
Protected virtual machines in a single protection group
500
500
Protection groups per recovery plan
250
250
Datastore groups
255
255
Simultaneously running recovery plans
10
10


Tuesday, November 22, 2016

VMware NSX Configuration Part 2

I will be demonstrating following configuration tasks in this post

  • Configure Default Gateway in Logical Router as IP of Edge Services Gateway
  • Configure OSPF on Logical Router with Area ID 101
  • Configure Uplink Interface on Edge Services Gateway attached to VLAN based Port Group
  • Configure OSPF on Edge Services Gateway with Area ID 101


Configure Default Gateway in Logical Router


Navigate to Logical Router under NSX Edges and Click on Routing Tab. You may notice Default Gateway is not configured. Click on Edit and specify the details


You will need to publish the change to get it reflected


To Test the connectivity  SSH into the Edge Services Gateway and try pinging IP for Logical Router. It should work fine



Configure OSPF on Logical Router


This will help configure dynamic routing between Logical Router and Edge Services Gateway

Navigate to Logical Router under NSX Edges and Click on Routing Tab Press  Global Configuration

You may notice OSPF is Disabled under Dynamic Routing Configuration


Click on Edit and set the "Router ID"


Don’t forget to Publish the Changes



Navigate to the OSPF on the left


Specify the Uplink Interface Address as "Forwarding Address" and Chose any free IP from the same Range as "Protocol Address'


Don’t forget to publish




Now we will create an Area Definition for the communication between Logical Router and Edge Services Gateway



Don’t forget to publish the Changes. By now you would have already noticed that I prefer to public with each change I make


Next we will do Area to Interface Mapping


Publish the Changes



Configure Uplink Interface on Edge Services Gateway


Navigate to Edge Services Gateway under NSX Edges and Click on Settings Tab Press  Interface

Select vnic1 and Click Edit icon



Select the Transport VLAN Port Group  which has access to the External World





Make sure IP is reachable from external servers

Configure OSPF in Edge Services Gateway


This will help configure dynamic routing between Logical Router and Edge Services Gateway

Navigate to Edge Services Gateway under NSX Edges and Click on Routing Tab Press  Global Configuration

You may notice OSPF is Disabled under Dynamic Routing Configuration
Click on Edit and set the "Router ID"






 Navigate to the OSPF on the left



Please ensure to check Enable OSPF


Publish the Changes


Now we will create an Area Definition for the communication between Edge Services Gateway and Logical Router. Please ensure Area ID is the same we created in Logical Router



Publish the Changes



Next we will do Area to Interface Mapping


Publish the Changes



Tests


In order to Test I created a New Logical Switch Test and added Internal Interface on the Logical Router with IP Range of 172.17.1/24

I logged in the console for Edge Services Gateway to see if it propagated route automatically for 172.17.1.x



With this base configuration for NSX has been completed. Now if you need more Logical Switches you can create as per you design and map it to the Interface in Logical Router

There are additional Services which we can configure in Edge Services Gateway as per your requirement. I will try go demonstrate couple of them in future posts

Please feel free to provide comments if the posts have been helpful