Virtual Volume (VVols) is basically a latest introduction into Vsphere 6.0 environment which has significantly change the architecture of storage part. Traditionally into vsphere environment we are having a concept of LUN to provide storage into ESXi into which VMware administrator used to provision virtual machine into that peace of storage (LUN). In this process all vm’s which are deployed are depended into that LUN having dependency into it. Like, if that LUN having any issue like all path went down or its loosed its connectivity from ESXi or storage, into this case all its derivative vm’s will get affected. That dependency has moved out into VVol VVol has introduced where virtual machine is directly connected to SAN (Raw area of storage), not on LUN concept.  Architecture of VVol In Virtual Volumes storage has altogether changes compared to old architecture of Vsphere. VVols completely change the way storage is presented, managed and consumed and certainly fo

Overview of NSX 6

Whats New in VMware Vsphere 6.0

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0

Basically there are 2 way to reset the SSO password ·       From Command line ·       VMware vSphere Web Client ·       If by any chance if your password got lock or want to change the SSO password then it would be difficult to revert back unless changing the policy of SSO Password. By default it will not allow to reuse any previous 5 passwords.   ·       To change the password policy from web client pls follow below mentioned step.               1)      Login to Vmware vsphere web client               2)      Click Home à Click Configuration à Select Policy à Password policy               3)      Click Edit ·       Change the Users cannot reuse any previous password to 1 ·       Click OK ·       Click on SSO Users and Groups ·       Click user “admin” à Right Click and select Edit settings and change the password ·       Again got to Password policy and  Change the Users cannot reuse any previous password to 5 ·       Click OK ·        

Note : Resetting the password will also unlock the administrator account . 1.      Login as an administrator to the vCenter SSO server. 2.      Click  Start  >  Run , type cmd, and click  OK . The Command Prompt window opens. 3.      Navigate to the directory  SSOInstallDirectory \utils.  By default, the installation directory is  C:\Program   Files\VMware\Infrastructure\SSOServer \ utils . 4.      Run this command: rsautil reset-admin-password 5.      Enter the master password when prompted. Note : This is the password  s elected for the SSO administrator during the SSO installation. If you have changed your SSO administrator password later, the master password is still the original one chosen. 6.      Enter the SSO administrator name for which you want to reset the password. For example,  admin . 7.      Enter the new password for the user and then confirm it a second time. You should see the message   Password reset successfully .

Just wanted to share a couple of pointers which came up during a vSphere design review process for a customer. During my discussions there were arguments around tracking of the vCenter Virtual machine in a big environment and getting on to it for troubleshooting in case the vCenter Server service or the VM is down can be a little time consuming. Therefore, some of the organizations prefer a physical vCenter to have more control and a single point to look at and troubleshoot in case of issues. I would say this has more to do with comfort and mindset of the admin, that the application managing the virtual environment itself is not virtual and isolated from the virtual infrastructure. I would not say that these points are not valid, since no one would like to search for there vCenter VM in case of vCenter downtimes. If you have not planned the initial placement of the vCenter VM, then you might end up logging on to each ESXi server directly via vSphere Clie