VMware Consultancy Services

You may noticed ESXi host may fail to authenticate to AD when lsassd service fails To resolve the issues 1. Place the host in Maintenance mode 2. Connect to host using SSH 3. Stop the lsassd services by runing /etc/init.d/lsassd stop 4. Copy the file /etc/krb5.conf from one host where the authentication works fine 5. Start the lsassd services /etc/init.d/lsassd start

When we try to reduce or shrink the size of an existing vmdk file, the operation fails. Resolution There is no option to reduce the size using vSphere client. For this you may need to use putty or cli. Please remember to delete unwanted data from the OS and to shrink the partition internally using the diskmgmt.msc tool. After shrinking , perform the below: Login to the ESXi using putty Browse to the vmdk location (eg: cd vmfs/volumes/datastore1/VMname) Take a backup of the existing vmname.vmdk and vmname-flat.vmdk files using the cp command in linux (cp filename backup_filename) Open the vmdk file using vi editor - vi vmname.vmdk Modify the value corresponding to RW to the required disk space. If you need to shrink the file to xGB, use the value : x*1024*1024*2. For eg: if you want to shrink the disk to 25GB, give the value 25*1024*1024*2= 52428800 Once finished save the file and use vmkfstools command to clone a disk using the new settings. vmkfstools -i vmname.

Reason A VM can become inaccessible due to any of the below reason: Issue with the ESXi servers Issue with the vCenter Issue with the datastore Resolution In all the three cases these are the below three troubleshooting steps: First step will be to restart the management agents in the ESXi. Login to the ESXi using SSH Run any of the below commands to restart the management agents /etc/init.d/hostd restart /etc/init.d/vpxa restart OR services.sh restart If this step did not resolve the issue for you, try the second step Second step will be to remove the VM from the inventory and add using the vmx file Right click on the affected VM Choose the option 'Remove from the Inventory' (Be cautious about this action...Do not delete the VM) After this step, go to the vmx location of the VM Right click on the VM and 'Add to the Inventory' This step will definitely resolve your issue. But this step works fine only when we

Fabric OS (goals) Fabos Version 5.3.1 Welcome to VMware Consultancy Services(vCloud Automation Center). goals login: admin Password: goals:admin> switchshow switchName:     goals switchType:     26.2 switchState:    Online switchMode:     Native switchRole:     Principal switchDomain:   1 switchId:       fffc01 switchWwn:      10:00:00:05:1e:35:7f:aa zoning:         ON (configfile) switchBeacon:   OFF Area Port Media Speed State     Proto =====================================   0   0   id    N2   Online           F-Port  50:06:01:68:3e:e0:38:39   1   1   --    N2   No_Module   2   2   id    N2   Online           F-Port  10:00:00:00:c9:44:f1:af   3   3   --    N2   No_Module   4   4   --    N2   No_Module   5   5   --    N2   No_Module   6   6   --    N2   No_Module   7   7   --    N2   No_Module   8   8   id    N2   Online           F-Port  50:06:01:60:3e:e0:38:39   9   9   --    N2   No_Module  10  10   --    N2   No_Module  11  11   --    N2   No_M

Scenario When we use thin provisioned vmdk, the size of the vmdk expands as we pile up data in the OS. But if we delete some data from OS, the reclaimed space in the OS will not be reclaimed from the vmdk. It will continue to occupy the maximum space it have ever used after creation. Resolution There is no resolution to reduce the size using vSphere client. For this you may need to seek the help of putty or cli. - Login to the ESXi using putty - Browse to the vmdk location (eg: cd vmfs/volumes/datastore1/VMname - List the available vmdk files in this location using the command: ls –lh *.vmdk - To know the actual size occupied by the vmdk file <   du –h *.vmdk - To shrink the size of the vmdk file vmkfstools -K AD01.vmdk - Re check the actual size of vmdk now.