Skip to main content

Posts

Issue: Operating System not found

                    Yesterday, I was working into my vsphere Lab where I have deployed one virtual machine into the environment. After deployment virtual machine was working perfectly fine. After some time, I have added 2 huge hdd of size 800 GB using PVSCSI. Once I added the hdd into the VM, and after accepting the change, I tried to open the console and found vm has rebooted and stuck at "Operating System not found" That’s look wired, as I have just added the hdd online and suddenly it rebooted and stuck at this stage. To troubleshoot this issue I tried to gracefully shutdown the VM and tried to bring online in hope, it will detect the changes, but again it stuck at same level "Operating System not found" I checked my OS drive which is  created with the LSI SCSI controller, and the 2 new hdd I created with PVSCSI controller. Here is what the problem exists!!!!! Basically, When the virtual machine is created with the LSI SCSI controller,

Issue: Connect-VIserver Could not connect using the requested protocol.

  Some time back I had an issue while I tried to connect my Vcenter from powercli but unable to connect and getting below error  ################################################## Connect-VIServer :  6/08/2015 3:31:27 AM        Connect-VIserver          Could not connect using the requested protocol. At line:1 char:1 + Connect-VIServer itvc001.age.com +         + CategoryInfo               : ObjectNotFound: (:) [Connect-VIserver], ViServerConnectionException         + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_ProtocolError, VMware.VimAutomation.ViCore.Cmd     lets.Commands.ConnectVIServer ################################################## This is all because, there are proxy setting configured into your explorer or into your system from where you are trying to connect the vcenter from powercli.  To resolve this Issue pls follow below KB articile. 2011395   http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=display

Virtual Volumes

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

Issue : Configure Management Network option is Grayed out into ESXi

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

SSO Password reset process and lockout process

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 ·        

To reset the SSO administrator password on a Windows server:

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 .