Wu's Blog

VMware vRealize Automation 6.2 Configuration vCAC configuration is little complicate. I'll separate to vCAC server, IaaS, vCAC itself and VCO configurations, 4 sections.

vCenter Server Configuration We will do identity source and permission settings on vCenter Server.

In previous articles I shared how to build vCAC 6.2 LAB, we created domain controller and DNS services on DC01.contoso.com , vCenter Server on VC01.contoso.com , 3 ESXi hosts on ESX01/02/03.contoso.com , vCAC server on vCAC.contoso.com , IaaS server of vCAC on IaaS.contoso.com and FreeNAS server on FreeNAS.contoso.com .

VMware vRealize Automation 6.2 (vCAC) installation vCAC contains 3 components: vCAC itself, vRealize Orchestrator (VCO) and IaaS server. I used native VCO to save resource. I'm going to share how to install vCAC by two sections: vCAC installation and IaaS installation .

FreeNAS Installation I need FreeNAS provides shared NFS storage for ESXi hosts to enable advanced features such as HA or vMotion. I gave 1GB RAM, 4 vCPU and 2GB local disk to FreeNAS virtual machine. DNS name is FreeNAS.contoso.com .

Recently VMware released VMware vRealize Automation Center 6.2 (vCAC). I guess there will be a newer version along with vSphere 6.0. Be an ITPro you have to keep learning new stuff! I built a lab environment on my laptop for learning. I'm going to share my implementation experience below, it spent me dozen hours plus lot of documents reading. Initially I felt it's to complicate to deploy (That's looks like a tradition of VMware products). But eventually I thought it's not easy to provide a unified self-service end user interface in a multi-vendors infrastructure. Even OpenStack is not easy!

*** English Version *** You are using HP ProLiant BL460c G7 or Gen8, ESXi version is 5.5, NIC is Emulex chipset. You are using driver version 10.x.x.x. You may experience the host randomly lost connectivity on vCenter Server, host status show "No responding". You cannot ping any virtual machine hosted on the blade. High pause frame is observed on HP virtual connect model down links after problem occurred. And you see similar error in vmkernel logs:

Some of my virtual machines used ISL logical SCSI controller. It's not recommended for Red Hat 6 virtual machines. We need to change it to VMware Paravirtual SCSI controller. Basically the steps is power off virtual machine, change the SCSI controller type, and power on. Then you lost operation system. :-)

It's easy to find a solution for this particular problem. VMware has a KB for this error. Somehow it's not my case. I don't know what's the exactly root cause but you can try vMotion the virtual machine to other host and give a try. Chinese Version 这个问题的解决方案很容易找到，VMware有一个知识库。但不知道为什么，我遇到的问题没法用此 知识库 解决。我通过vMotion虚拟机到其他ESXi 主机解决此问题，也不知道具体原因是什么。