The Ravello Systems blueprint of Autolab 2.6 is a great point of start for any deployment vSphere based.
In this case, I’ll report my experience where I used Autolab 2.6 for NSX 6.2 deployment.
I will jump over the steps needed to deploy Autolab in Ravello, I’ll report it in another post. This first part will reach the point of deployment of NSX inside the Autolab’s vCenter.
We’ve to move away from standard in the moment when, to have 2 clusters, 3 hosts are nomore enough – 3 hosts is the standard of Autolab.
Luckily the guys at Labguides had a good intuition, so that they added at IPXE’s ESXi menu the “install fourth ESXi” line. So, my task was only to deploy a brand new application from blueprint, save one of the standard ESXi, delete that application and deploy this new ESXi in my current installation, modifying all the networks and hosts stuff.
So, installed the fourth as I did with previously ones, I planned to have 2 Clusters: Management and Prod.
The Management cluster will serve NSX Manager, the Prod is the resource cluster, so it will take care of the Edges.
I’ll put the Host1 and Host2 inside cluster “Management”, and Host3 to cluster “Prod”- before moving it I had to set it in Maintenance Mode
That’s the new host ready to be inserted in my Prod cluster:
Now proceeding with Add host:
We’ll answer “yes” to the security alert, and going straight forward with all the defaults:
Now we can assist at the import process.
In my case, I had to reboot the host to permit HA agent to be installed on it.
Since the Add Host wasn’t automated by Autolab as the previous ones, but manual, I had to add NIC1 in teaming to the first vSwitch, to create the other vSwitch and to recreate all the storage connections.
From the beginning, I had to modify, for Management network, NIC teaming, setting vmnic0 as active and vmnic1 as standby, overwriting switch failover order:
And then create the following portgroups: IPStore2
We’re going to recreate the second switch, the one dedicated to VMs:
It’s time to reorder the storage connections too. We’ve to add, to the new host, the following:
I’ll jump this part since the purpose of the post is the NSX installation, and not recreate from scratch an host to be compliant with Autolab environment. Anyway, it’s simply a “copy&paste” process from the existing ones to the new one. Regarding iSCSI datastores, we’ll have to set up the HBA interfaces.
Time to deploy NSX. After download the OVA file we’ll use vCenter to deploy it on Management cluster. We’ll use the webclient and not C# client since the first one will give us more options (if we didn’t before, to deploy using webclient we need to download the client integration plug-in – link appears during deployment).
Using IE11 I wasn’t able to use the plugin, and neither Windows Authentication. Following several forum’s advices (https://communities.vmware.com/thread/515713?start=0&tstart=0 is one of them), I downloaded and used Chrome.
By the way, I don’t know if this is only my problem, but my vC server didn’t start automatically the vSphere Web Client service, although set as automatic.
It’s important to check the box accepting the extra configuration options.
Autolab sets its storages not larger than 58GB, that is less than NSX requires in its “thick” deploy. We can use “thin”, and iSCSI2 that is the larger DS available. Storage policy will be the default one – we’re not using vSAN neither VVol
At this point I encountered a boring error: “A connection error occurred. Verify that your computer can connect to vCenter server”:
Since my computer IS the vCenter, this didn’t make sense. Googling the error I discovered a related KB – https://kb.vmware.com/kb/2053229 – stating that it depended on a bad DNS configuration. This did’n make sense too, since I connected the webclinet using the DNS name, but I double checked pinging tha name, and I understood that my server was using IPv6 – solution was to disable IPv6 on my VC NIC:
It works now, and I’m able to continue.
The network to map is the “Servers” one, but it’s not important: we only have one physical network, so it doesn’t matter. In the last page we’ll be asked a password for default CLI user, a password for privileged and Network infos. We’ll assign the NSX the IP 192.168.199.200, providing an entry in DNS too, as nsx.lab.local. The same DC server acts as NTP server.
In our installation we won’t use IPv6 (ok… shame on me!)
And this is the summary and deployment:
I don’t choose to start it automatically because I could be forced to modify the resources assigned to nsx: my ESXi’s could offer 24GB of RAM and 12 CPUs – yes, I modified the default values of Autolab.
IMPORTANT: you must change the vNIC from VMXNET3 to E1000, according to Martijn Smit’s post: https://www.vmguru.com/2016/01/ravello-systems-vmware-nsx-6-2-management-service-stuck-in-starting/ . DO IT BEFORE STARTING THE VM – it won’t work changing it after, I had to redeploy. AND you should do it via SSH’ing the ESXi, not deleting and recreating from GUI because if so, the VM will rename it in eth1.
Actually, the nsx doesn’t start:
I must reduce assigned RAM from 16GB to 12GB and CPU from 4 to 3, otherwise it won’t start.
After the first boot, although, if you shut down, you’ll be allowed to use 16GB and 4CPU, as adviced.
And that’s the result of our efforts:
Logging in, this is the main window:
And the summary page:
This is the end of this first part. In the next one we’ll configure the NSX manager and we’ll deploy our Edges and VXlans.
Thank you for following!