vCenter Log Insight – VMware – vSphere content pack v 2.0 reinstall

After upgrading to vCenter Log Insight v 2.0 I wanted to install the latest content packs so I downloaded the VMware – vSphere content pack from VMware Solution Exchange.

I imported the content pack and I was prompted if i wanted to upgrade.
Not paying attention I actually downgraded the content pack to v1.5 which is the latest which seems to be available on Solution Exchange.

Here are the steps to revert back to latest v 2.0 content pack for VMware – vSphere:

  1. Download 7zip.
  2. Open the archive PAK file which is downloaded for the upgrade of Log Insight.
  3. Browse to \usr\lib\loginsight\application\etc\content-packs\vsphere\
  4. Extract the file content.json.
  5. Open Log Insight.
  6. Select Content Packs
  7. Select “Import Content Pack”
  8. Browse for the content.json file.
  9. Upload
This will now again install the latest version 2.0.

vCenter Log Insight 1.0.4 upgrade to v2.0.3? where to now?

So I had vCenter Log Insight v 1.0.4 installed in our environment and just never had the time to upgrade this until recently.

The problem that exists in that in the old releases the rpm file was used to upgrade through CLI.
In the new releases since 1.5G they make use of PAK files for upgrades through the web interface which is must more user friendly.

Well since I only had v1 installed and uses RPM it caused a bit of issues since only the v2 PAK file is available on download site.

To fix this i did the following:

  1. Download the v1.5 file from following location:
  2. Backups / snapshot your VM appliance.
  3. Copy the rpm to the VM, i used the \tmp folder.
  4. Upgrade Log Insight through the CLI by running the following commands:
    1. service loginsight stop
    2. rpm -Uvh loginsight-cloudvm-1.5.0-1435442.x86_64.rpm
    3. service loginsight start
  5. Now login to the appliance.
    1. Go to administration
    2. Under management select Appliance
    3. upload the new PAK file for v2
    4. Click upgrade.
This should be it and you should have the new version ready.


Upgrade log insight installed versions:|utmccn=(organic)|utmcmd=organic|utmctr=vcenter%20log%20insight%20upgrade&__utmv=-&__utmk=81845013

VMWare OpenSSL fixes: what to do

Vulnerable Products:
  • ESXi hosts
  • Windows version of vCenter Server (only Atlanta)
  • vCenter Server appliance
  • VMware Client Integration Plug-in
  • vCenter Single Sign-On VMware Directory Service
  • ESXi hosts
    • Verify you version installed and only upgrade to the patch specified in the following KB:
    • Running following commands to re-issue the certificate:
      • cd /etc/vmware/ssl and ls -l
      • mv rui.crt /vmfs/volumes/ATL01PRDCS01_WINBUILD_01_01/VMH04orig.rui.crt
      • mv rui.key /vmfs/volumes/ATL01PRDCS01_WINBUILD_01_01/VMH04orig.rui.key
      • /sbin/generate-certificates
      • chmod +t rui.crt
      • chmod +t rui.key
    • Change root password
    • Reboot the server
    • Reconnect host again to vCenter
  • Windows version of vCenter Server
    • Verify log on as accounts for VMware services after upgrade.  For some reason mine changed to the user as was logged in as so some plugins did not start.
  • vCenter Server appliance
    • Upgrade to latest release to patch Client Integration Plug-in.
  • vCenter Single Sign-On VMware Directory Service
    • recreate certificates (reference KB 2076692)
    • change password
  • VMware Client Integration Plug-in
    • Download from webpage and upgrade for all users accessing vCenter web client.

Good KB to subscribe too for updates on this issue:

vCloud 5.5.1: Create new storage policy, add storage, migrate vApps.

We recently purchased new storage so the new datastores had to be added to vCloud director, and all the vApps migrated over.  There are many ways to go about doing this but the best solution I found was to create a new storage cluster and put all datastores in it and also create a new storage policy and profile.  I have been told it is also possible to just perform a storage vmotion on the VM’s but i had mixed results with this approach.  Here is my information which I hope might be useful to someone.

In Vcenter server:
  1. Create tag category (I called mine “storage policies” to keep it simple”, but description can also be used to describe the function)
  2. Create tag and add to category
  3. Open VM storage policies
    1. Create new VM storage policy
    2. Select vCenter
    3. Enter a policy name
    4. Provide description
    5. Add tag-based rule and assign newly create tag from tag category.
  4. I ALWAYS FORGET to enable the policy so here is not to you doing the same 🙂
    1. select the new policy name
    2. 2nd icon from left is “Enable VM storage policies per compute resource.
  1. Assign the newly created tag to datastore cluster
  2. Assign the newly created tag to each datastore within the cluster.

In vCloud director:
  1. Under Manage & Monitor tab select vCenters from vSphere resources.
  2. Right click the vCenter server name and select  “refresh storage policies
After you get the storage profile to show in storage policies you have to assign it:
  1. Go to Provider VDC and open it
  2. Select storage policies tab
  3. Add new storage policy! 
  4. There is a BUG in 5.5.1 which does not refresh or show the storage policy and an outage is actually necessary to clean up the database with a script (not very nice but works)
  1. Go to Organizations and open the one which will be using the new storage
  2. Select Virtual datacenter tab
  3. Select Storage policies tab
  4. Add the new storage policy
  5. If you want the new policy to be the default – Right click the new storage policy and select “Set as default”

Migrating vAPPS to new storage profile:

  • The best method I found was to shutdown the vAPP and right click select “move to” and then each individual VM select the new storage policy.
  • You can also do this with a powered on VM and go to properties and change the storage polic