vRA 6 distributed setup problems
This week I’m at the SDDC consulting training at the VMware EMEA HQ in Staines. There is a really full program with presentations and labs about the VMware SDDC portfolio. Products that will be covered in the training are:
- vRealize Automation
- vRealize Orchestrator
- VMware NSX
- VMware SRM
But the most important focus this week is the integration between all VMware products and 3th party products like InfoBlox and Service Now.
We started yesterday with the installation of a distributed vRealize Automation 6 environment. After clicking thru 281 pages of instruction the installation was finished. Some people in the class had problems with the lab base environment because of time out errors. The reason was a slow network connection not just slow but really really slow…
The lab environment consists of virtualized ESXi hosts and is using NSX for the networking part. In NSX there is some bug (or should I say undocumented feature ;-)) that cause lots of packet drops when using virtualized ESXi hosts and NSX. The solution to work around is to create DRS rules to keep some of the VMs (the ones you are working on) together on a virtualized ESXi host so all network traffic is kept locally. I think it’s also possible you experience the same slow connection if you are doing the VMware Hands On Labs because the setup is probably the same.
Today when booting up my lab again I had the issue that the infrastructure tab had a strange name. The name was changed in: email@example.com instead of just Infrastructure. All underlying tabs had the same problems. If you know where to click everything is still working, but it doesn’t feel good.
The solution to this problem is to just reboot some nodes of the vRA installation. But wait, which of the 10 servers do need a reboot? The answer is nearly all of them. The boot order for the complete stack is:
- Microsoft SQL Database server
- Identity appliance
- vRealize appliance 1
- vRealize appliance 2
- IAAS webserver 1 & 2 (vRealize webportal and ModelManagerData services)
- Application server 1 ( primary IAAS Manager and the DEM Orchestrator Server services)
- Application server 2 (secondary IAAS Manager and the DEM Orchestrator Server services)
- Proxy server 1 & 2 (DEM worker and Proxy Agent server services)
Rebooting from step 3 will resolve this issue. First shutdown all services in the reverse order and when you are at the vRealize appliance 1 just reboot this one. Wait till the VAMI is showing up in the console and then (and not earlier!) start the next one of the list. If the server is a Windows server give it some extra time to boot up all services.
If everything is restarted then you will see the normally names and tabs.