Vimware

How to remove conflicting VIB's during Esxi host upgrade

So you want to upgrade your Esxi version from 5.5 to 6.5 using the host upgrade option with the vsphere client, which in my case that is what I was trying to perform. I have a Cisco UCS server, so I downloaded the custom Cisco image from the Vmware website to make life a little easy during the upgrade.

So when you create a new baseline for your Cisco UCS image and attach it to the host (I am assuming you guys know how to create a baseline and attach it to the host) and within update manager click on the "Scan for Updates" button and select "Upgrades".

4.JPG

You notice that after the scan completes in the summary box below, that the status details say that there are a few conflicting VIB's that need to be removed in order for the upgrade to proceed.

1.JPG

Here is what you do to remove those VIB's, so that you can proceed with the upgrade.

  • Enable SSH on the desired host from the security profile of the host
  • Use Putty and ssh to the host using the root credentails
  • Once at the console, type  the command --> esxcli software vib list
2.JPG
  • Match the conflicting Vib name that you encountered earlier to this list and note down the name. (In my case it was net-mst)
  • So at the ssh console type the command --> esxcli software vib remove -n=net-mst
3.JPG
  • Once the VIB has been removed, it will prompt you for the reboot. So go ahead and reboot your host.
  • Once the host is back and connected within your vcenter, go under update manager and scan for updates again and this time, you should see the image being Non-Compliant. Now you can proceed with the Remediation of this host to apply this image.
5.JPG

Can i cancel Vmware snapshot, stuck at 99%!

This is probably the most trickiest decision to make at any time, you have clicked on the action to delete a snapshot on a virtual machine and its stuck at 99% for like a very long time.  You want to cancel the task, but you are not sure if its safe?!

I have had to do this a couple of times and I am thankful, everything has gotten back to normal. So the situation is, you have a snapshot at 99% and you gather up the courage to cancel it and it gets stuck again and you are just waiting! First I recommend reading up the below blog and do a quick check if at all you need to perform a hard kill. (Read this). Its a pretty well written blog and in case you want to do ahead, which I did on a couple of occasions, just enabled SSH on your host and type in the command:

services.sh restart ( Please note that this will not affect your working virtual machines and its completely safe, you might see the host getting disconnected from vcentre for a bit but it will come back, so don't worry)

Once done, the snapshot tasks will be cancelled and then you may be prompted to consolidate your disks, which would be slow as well but please don't cancel the consolidation at this point.

I know it's not recommended to cancel a snapshot, but sometimes you have to take a leap of faith!

Remove old/orphaned vcenter from linked mode - The vSphere client is not connected to the following vCenter server

In case you guys land into an issue when you have decomissioned your old linked vcenter or migrated to a new one but when you login using the vpshere client you get the below message.

 It means that you have a stale entry in the ADAM database and here is how you can fix it. (Be careful what you do in here!)

Open up ADSI EDIT, right click  and select "Connect to"

 In the following dialog box click "Select or type a distiniguished or Naming Context" and type dc=virtualcenter,dc=vmware,dc=int

Then in the below section select the option under Computer as seen below,and here type the name of your working vcenter in which you are receiving the pop up box and then after you have filled in the information click OK.

 After you have connected to your vcenter server context, drill down to OU=Instances as you can see below and right click on each of the instances below and look at the vmw-vc-URL and vmw-vc-InstanceName value and if you see your old vcenter name in them which you have decommiomsed or un-linked, this is the intance you have to delete. So go ahead and delete it. After this restart your vsphere client and login again and now you will no longer see the message.

-Alstar

Vsphere web client service crashes after upgrading to Update 3

Today I ran into a minor issue when I upgraded my Vcentre and all the components to Update 3. My web client service would just crash on me even if I started it manually. So here is what I did to fix that.

  1. Stop the vSphere Web Client Service. 
  2. Move the WORK folder from this location. (DO NOT DELETE THE FOLDER)
    C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\work
  3. Start the vSphere Web Client Service.

-Alstar

Find out harwarde details of Esxi servers using SSH

I wanted to find out the serial number and the model of my Esxi host using SSH. I know we can find this out using the vcentre client under the hardware status tab but I wanted to SSH and find out the info.

It was fairly simple to do..

  • Start the SSH service on the host
  • Open up putty and connect using SSH to the host
  • Run the command smbiosDump | egrep '(Product|Serial)'
 # smbiosDump | egrep '(Product|Serial)'
      Serial Services supported
    Product: "ProLiant DL380p Gen8"
    Serial: "CZxxxxxC5F"
    Serial: "CZxxxxxC5F"
    Type: 0x09 (Serial Port 16550A Compatible)
    Product ID: 642119-421