/etc/vmware/vmware-vmon/svcCfgfiles imagebuilder.json updatemgr.json vsan-health.json Make a backup copy of each file chmod +rwx <file above> (to allow editing) Using a text editor (vi, etc), l...
See more...
/etc/vmware/vmware-vmon/svcCfgfiles imagebuilder.json updatemgr.json vsan-health.json Make a backup copy of each file chmod +rwx <file above> (to allow editing) Using a text editor (vi, etc), locate the "StartTimeout" field and change to 1500 in each file above
Part of the patch didn't complete. You should roll back your snapshot and contact support for assistance. I got the error due to service timeout during patching. Support increased the timeouts and...
See more...
Part of the patch didn't complete. You should roll back your snapshot and contact support for assistance. I got the error due to service timeout during patching. Support increased the timeouts and we were able to patch successfully.
I finally got through this with help from VMware support. We increased the service timeouts, which got us through the error. Used the patch ISO and installed through CLI.
Same issue after updating to 7.0.2.00500 as well. I'm not holding my breath that U3 fixes dark mode UI. I have to switch back to light mode to see progress numbers in the recent tasks pane. It's l...
See more...
Same issue after updating to 7.0.2.00500 as well. I'm not holding my breath that U3 fixes dark mode UI. I have to switch back to light mode to see progress numbers in the recent tasks pane. It's like no one at VMware uses dark mode
I feel dumb… I was using the latest Edge browser or Firefox. Neither worked. I opened the MOB in Chrome without issue. Seems to be a browser specific issue.
I am having the same patch error upgrading from 7.0u1c to any U2 release (tried u2d today). Today’s attempt was with VMware support on the line. We changed service timeouts in some json files, and ...
See more...
I am having the same patch error upgrading from 7.0u1c to any U2 release (tried u2d today). Today’s attempt was with VMware support on the line. We changed service timeouts in some json files, and reset the UMDB. No joy. Sent a support bundle for them to pour over tomorrow. I have a linked VC in another DC that updated no problem. My next patch window is two days from now.
I noticed the MOB page is no longer working on my 7.0u1 prod or lab instances. It used to work in v6.7. The error page says: "HTTP Error 401: This page isn't working right now"
We are also experiencing the same issue when disconnecting / reconnecting vNIC on VM's hosted on ESXi 6.7u3 hosts. Here's the VMware KB on this: VMware Knowledge Base Workarounds: Use an...
See more...
We are also experiencing the same issue when disconnecting / reconnecting vNIC on VM's hosted on ESXi 6.7u3 hosts. Here's the VMware KB on this: VMware Knowledge Base Workarounds: Use anything but the H5 client to reconnect the vNIC (Flash/Flex client, powershell, etc) Switch the vNIC portgroup to any other portgroup, enable the vNIC, then switch back to the original portgroup
Thanks. I've confirmed I checked both vCenter instances when importing vROPs - 2 nodes in primary VC, 1 remote collector in remote VC. Same error - "invalid vrops master address".
I am creating a new environment on a freshly deployed vRLCM 8.0.1, importing an existing vROPs 8.0.1 deployment. I entered all the information, but after starting the request I get the following...
See more...
I am creating a new environment on a freshly deployed vRLCM 8.0.1, importing an existing vROPs 8.0.1 deployment. I entered all the information, but after starting the request I get the following error: com.vmware.vrealize.lcm.plugin.common.vrops.exceptions.VropsAddressException: Invalid vrops master address at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.BaseConfigureVropsTask.init(BaseConfigureVropsTask.java:83) at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.DeploymentsDiscoveryTask.initialize(DeploymentsDiscoveryTask.java:406) at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.DeploymentsDiscoveryTask.execute(DeploymentsDiscoveryTask.java:128) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:45) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) I have triple confirmed the IP address of the vROPs Master Node. I am able to ping vROPs from vRLCM and vice versa - they are on the same subnet. Any ideas on what's going on here?