Tuesday, December 30, 2014

eBooks for only $5


WOOHOOOO last post of the year ….. and while I was struggling to get my mind to work this week ,it came across me that the last year promotion at Packt Publishing is back.



Until January 06th, 2015 you can buy any eBook or Video for just $5, and you can buy as many as you want. That's a great opportunity to get that book you want and improve your skills.
I got tell you, I’ve used it’s services before and it’s great, easy to use, several formats for reading the eBooks and also an amazing variety of contents.

I did a suggestion’s list just in case you are as lazy as I’m these days : )




Disclaimer: Compensation was provided by Packt Publishing. The opinion expressed here are those of the author and are not indicative of the opinion or positions of Packt Publishing.

Friday, December 19, 2014

vRealize Orchestrator 5.5 and Chargeback 2.6 Compatibility


I’ve been working on a public cloud solution for one of our vCloud Air Network Service Providers.  I was creating some automation for their billing system and one of the tasks was to automatize the extraction of vCenter Chargeback Cost Reports, this task is easily accomplished with vR Orchestrator.

vR Orchestrator has a plug-in for vCenter Chargeback which allow us to connect to it, generate reports and export it (among other things).

Sadly when I was configuring the integration, I started receiving and error message stating that Chargeback could not be added into vRO system.

The error said: java.lang.Exception: Unable to login as the service is not running on to the specified port


 Immediately I started with the basic troubleshoot scenario:

- Checked port (443) communication between vRO and Chargeback . It was OK.
- Credential to login on Chargeback. It was OK.
- SSL Certificates. Just to make sure, I re-generate the certificate and re-import into vRO. No problems here.

Since everything looked perfectly fine I decided to open a case with VMware support.

The environment was:
vRO: 5.5.2.1951762 (5.5.2.1946710)
vRO Plugin for Chargeback:  2.0.0.1
Chargeback: 2.6 (1445187)

After some exchange of information and tests they figured out what was wrong.

vRO 5.5 uses java 1.7 and the Chargeback SDK implemented on the plug-in could not establish communication with that version of java.

The solution was to update the plug-in to use a version compatible with java 1.7 of the vRO.
Once they provided me the new plug-in I was able to configure Chargeback successfully.

I’m expecting that the new plug-in will be updated at Solution Exchange very soon, meantime you can get the new version opening a case with VMware support, mention my case (SR14548138010) and they can provide you the new plug-in.

I little bit of extra information,  this issue does not happen on vRO 5.1.

BTW, is it Christmas already ?!?!

Thursday, December 11, 2014

Automatically Licensing ESXi


Let’s be honest, licensing each ESXi host we place on the environment is a tedious task right, so why not automatize it ?!?
The majority of environments I’ve been working with just have a single bulk of licenses, deciding what license to choose doesn't need much thought ; )

The solution has been always there, documented at ESXi Installation Guide.

Let’s see how to set up Bulk licensing.

You will need PowerCli to execute it. 
If you are not familiar with that, I recommend to start reading PowerCli basics.

- start PowerCli;
- connect to the vCenter you will set up the licenses;

First thing is to bind license manager to a variable, so we can reference it in the future

- run: $licenseDataManager = Get-LicenseDataManager

You can assign a license to a specific Cluster or an Entirely Datacenter, that way the host will be licensed depending on where it will be added to. I’ll add it to my datacenter, so every host on this datacenter will get the same license.

- run: $hostContainer = Get-Datacenter -Name “Datacenter_name”

Now it comes the magic, create the reference for your license

- run: $licenseData = New-Object VMware.VimAutomation.License.Types.LicenseData
- run: $licenseKeyEntry = New-Object Vmware.VimAutomation.License.Types.LicenseKeyEntry
- run : $licenseKeyEntry.TypeId = "vmware-vsphere”
- run: $licenseKeyEntry.LicenseKey = "Your license goes here"

Then you associate them together

- run: $licenseData.LicenseKeys += $licenseKeyEntry

Last step is to tie up the license with the datacenter we selected above

-run: $licenseDataManager.UpdateAssociatedLicenseData($hostContainer.Uid, $licenseData)

To make sure license has been configured and tied together properly you can run:

$licenseDataManager.QueryAssociatedLicenseData($hostContainer.Uid)

The output should be similar to the screen bellow


Now, let's make it a try !!!

I do have an ESXi host using an evaluation license


 Just removed the host from my inventory and added it back to the Datacenter where my bulk license is set up.

As we can see it has been licensed immediately.


One thing to notice is if your host is already licensed it wont get a new one.

Bye bye boring task ; )

Thursday, December 4, 2014

vShield Driver is now Guest Introspection.


These days one of my clients was working on an agentless antivirus solution for their VMware vSphere environment when suddenly he asked me: “Where’s vShield Driver ?

See an old Picture


It turns out, it has been renamed !!! Thin agent is now called Guest Introspection driver. 
The change came with ESXi 5.5 update 2 release.

But it’s implementation remains the same.

- starts VM tools installation
- select Custom


- Expand VMware Device Drivers / VMCI Driver


 See, it’s there as it supposed to be, just undercovered as a another feature; )



Who am I

My photo
I’m an IT specialist with over 15 years of experience, working from IT infrastructure to management products, troubleshooting and project management skills from medium to large environments. Nowadays I'm working for VMware as a Consulting Architect, helping customers to embrace the Cloud Era and make them successfully on their journey. Despite the fact I'm a VMware employee these postings reflect my own opinion and do not represents VMware's position, strategies or opinions. Reach me at @dumeirell

Most Viewed Posts

Blog Archive