vmware hub

after referring many post and articles related to particular error, I found 3 solutions which can be executed one after another depending on the situation. I recommend to ensure proper backups of VCSA. Below are the options which can help to fix this issue. 1. Perform the cleanup task on file system. Remove old compressed log from the file system. 2. Increase the size of the LVM mount point. 3. Increase the size non LVM mount point (eg:/dev/sda3). You can refer below details of mount points of vCenter Server Appliance are deployed using a Tiny specification. Your environment may differ depending on the sizing used.      Disk  VMDK)  Default Size  (Tiny VCSA) Mount Point Purpose VMDK1 12GB / (10GB) /boot (132MB) SWAP (1GB) Boot directory where the kernel images and boot load configurations are stored VMDK2 1.3GB /tmp Temporary directory used to store temporary files generated or used by services from vCenter Server VMDK3 25GB SWAP Swap directory used w

Issue: SRM (5.5)Test fail-over fail to power on Multiple machines withSRM Test failover fail to power on Multiple machines with Error - Timed out waiting for VMware Tools after 300 seconds Operation timed out: 900 seconds Timed out waiting for VMware Tools after 300 seconds Operation timed out: 1200 seconds Operation timed out: 1200 seconds , Note:Virtual machines have updated VMware tools, ESXi host (Protected and Recovery site) are running on same build version. Solution: Here since the vmware tools wait for the heartbeat from VM (guest OS needs to load and send heartbeat) so avoid this over all you can also uncheck below option , so the vmwaretools wouldn't wait for this and loads successfully .   Right-click virtual machine in the recovery plan and select Configure.                                                            Go to Startup Action > Power On > Wait for VMware tools. Or As a recommendation the only option to come out of this is to in

Now it’s time to create a new tenant in our vRealize Automation portal. Let’s login to the portal as the system administrator account as we have before. Click the Tenants tab and then click the “New” button. Give the new tenant a name and a description. Then enter a URL name. This name will be appended to this string: https://[vraappliance.domain.name]/vcac/org/ and will be the URL that users will login to. In my example the url is https://vra7.hollow.local/vcac/org/labtenant. Click “Submit and Next”. Enter a local user account. I used the vraadmin account much like I did in the previous post about setting up authentication. Click Next. In the administrators tab, I added the vraadmin account as both a tenant administrator and an IaaS Administrator. I will admit, I’m omitting some information here. After I added the vraadmin account, I logged into the tenant as this account. I setup directory services for this account the same way I did for the default tenant. Once th

In order to setup Active Directory Integrated Authentication, we must login to our default tenant again but this time as our “Tenant Administrator” instead of the system administrator account that is created during initial setup. Once you’re logged in, click the Administration tab –> Directories Management –> Directories and then click the “Add Directory” button. Give the directory a descriptive name like the name of the ad domain for example. Then select the type of directory. I’ve chosen the “Active Directory (Integrated Windows Authentication)” option. This will add the vRA appliance to the AD Domain and use the computer account for authentication. Note:  you must setup Active Directory in the default (vsphere.local) tenant before it can be used in the subtenants. Next choose the name of the vRA appliance for the “Sync Connector” and select “Yes” for the Authentication. I’ve chosen sAMAccountName for the Directory Search Attribute. After this, we need to enter a

We’ve got vRA installed and thats a good start. Our next step is to login to the portal and start doing some configuration. Go to https://vra-appliance-name-orIP and enter the administrator login that you specified during your install. Unlike prior versions of vRealize Automation, no domain vsphere.local domain suffix is required to login. To start, Lets add some local users to our vSphere.local tenant. Click on the vsphere.local tenant. Click on the “Local users” tab and then click the “New” button to add a local account. I’ve created a vraadmin account that will be a local account only used to manage the default tenant configurations. Click the Administrators Tab and add the account you just created to the Tenant Admins and IaaS Admins groups. Click Finish. Click on the Branding Tab. If you want to change any of the look and feel of your cloud management portal, uncheck the “Use default” check box and upload headers, change colors to fit your needs. Click on the E

This is our first stop in our journey to install vRealize Automation 7 and all of it’s new features. This post starts with the setup of the environment and assumes that you’ve deployed a vRealize Automation appliance from an OVA and that you’ve also got a Windows Server deployed so that we can install the IAAS components on it. After you’ve deployed the vRA7 OVA, login to the appliance with the root login and password supplied during your OVA deployment. Unlink past versions of vRA, we now have a lovely wizard that pops up and of course asks us to acknowledge that we will adhere to the End User License Agreement. Click the check mark (after reading all of the EULA of course) and click next. Look at this! We get a deployment wizard and it even asks us what kind of deployment we’re going for. A minimal deployment is what we’re doing in this post, but a fully distributed, highly available, “Enterprise deployment” is now an option as well. I’M REALLY EXCITED ABOUT THIS IF