VMware

My eth0 is now called eno16777736

Interesting and new to me is that my network interface which was known to be called eth0 is now called eno16777736 in my new installs.

The following document indicates that 16777736 is the device’s acpi_index as provided by the firmware (BIOS/EFI)

This seems to happen on my VMware hosts where I’ve installed the latest Ubuntu OS releases. I am still looking into why this is happening and will update as soon as I have a better understanding.

For now, here is some info I found:

What does “eno” stand for?

en is for Ethernet
o is for on-board
The number is a firmware/BIOS provided index.

 

VMware Flings: Embedded Host Client Update

I am excited about the release of VMware Labs Flings release of  version 3 of the Embedded Host Client. For those of you who find yourself out of the loop at time, no worries it happens.  Here is some details about the the embedded host client:

The Embedded Host Client is written purely in HTML and JavaScript, and is served directly from your ESXi host. The installed client is in its development phase at this time and does not have full feature sets, but has implemented a very useful feature set.

These features include:

  • VM operations (Power on, off, reset, suspend, etc).
  • Creating a new VM, from scratch or from OVF/OVA (limited OVA support)
  • Displaying summaries, events, tasks and notifications/alerts
  • Providing a console to VMs
  • Configuring host networking
  • Configuring host services

 

Installation Steps:

  1. Enable SSH on your ESXi host, using DCUI (Direct Console User Interface) or the vSphere web client.
  2. SCP the VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib to a directory on your ESXi host. In my case I used a shared storage LUN or NFS volume as I will apply this to multiple hosts.
  3. Next issue the following command:

     

Upgrade Steps

  1. Enable SSH on your ESXi host, using DCUI (Direct Console User Interface) or the vSphere web client.
  2. SCP the VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib to a directory on your ESXi host. In my case I used a shared storage LUN or NFS volume as I will apply this to multiple hosts.
  3. Next issue the following command:

     

Example output from running the above command:

[root@esx1:~] esxcli software vib update -v /vmfs/volumes/nfs/installs/flings/VMware_bootbank_esx-ui_0.0.2-0.1.3172496.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_bootbank_esx-ui_0.0.2-0.1.3172496
VIBs Removed: VMware_bootbank_esx-ui_0.0.2-0.1.2976804
VIBs Skipped:

 

Tools of choice

WinSCP – http://winscp.net/eng/index.php

Putty – http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

 

For more info on ESXi Embedded Host Client: https://labs.vmware.com/flings/esxi-embedded-host-client

 

Thanks for visiting – jermal

 

OVF Deployment Issue Ubuntu Snappy 15.04-stable (5 cloud)

When you have time, you do something.

Tonight I was headed over the Ubuntu site to grab me the latest version because I was thinking of installing OpenStack when I noticed on their landing page and noticed “Get Ubuntu Core” ; yes something new.

But where is my Raspberry Pi? No worries they have OVF images I can use to deploy to my vCenter Lab here at home. So I started just this and encountered an issue I once had.

Lets walk you through my events.

Downloading the image

  1. Found myself on the Ubuntu Internet of Things landing page: http://www.ubuntu.com/internet-of-things
  2. Located the OVF section of the getting started page: http://developer.ubuntu.com/en/snappy/start/
  3. Downloaded the OVA image (x86): 15.04/stable

Deploying the OVF Template 

  1. Using the vSphere Client, connected to vCenter (or stand alone ESXi host)
  2. Select server to deploy to and choose file > Deploy OVF Template
  3. Browse to the path were you downloaded your OVF image and select it

This is when I received the following error:
The following manifest file entry (line 1) is invalid: SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c

Troubleshooting Step 1

  1. I extracted the OVA image (core-stable-amd64-cloud) with 7zip
  2. Once extracted attempted the steps detailed above “Deploying the OVF Template”

The same error was thrown once more.

Troubleshooting Step 2

Within the extracted folder exists the following file types: certificate, manifest, ovf (instruction / configuration) and disk image

  1. I remove the SHA256(core-stable-amd64-cloud.ovf)= d4b8922ed38a4eb9055576f7b46f8e92f463398298f3a42af942f25457d4d41c line from the .MF (manifest)
  2. Once removed I attempted the steps detailed above “Deploying the OVF Template”

It failed also, only this time the error started the the remaining SHA256 was also invalid.

Troubleshooting Step 3 – Third time is the charm

  1. Moved into the extracted OVA folder
  2. Deleted the .mf (manifest) file
  3. Followed steps above “Deploying the OVF Template” only this time using the OVF located in the extracted folder

This go around everything worked

So why did this happen?

The template was changed after its creation which invalidated the SHA256 key.  I have made templates myself, only to have to edit something out such as removing a CD Rom reference which later caused me issues.

I hope this helps if you face this incident or something similar

 

Thanks for visiting – jermal

Also published here

VMware: vCenter Server Appliance 6.0 Update 1

That time has come, when you upgrade vCenter 6.0.  Here are some quick simple steps to see this done.

As always, its a good idea to have a backup before proceeding.  In my case I used a snapshot of my appliance. This was done by me connecting directly to the ESXi and creating a snapshot.

And here are the steps to start this process:

  1. Download the VCSA 6.0 Update 1 from  the VMware Patch Download Website. File-name: VMware-vCenter-Server-Appliance-6.0.0.10000-3018521-patch-FP.iso
  2. Mount the VCSA 6.0 Update 1 Patch ISO to your VCSA 6.x appliance. I attached the ISO by logging into the ESXi and then attaching to the guest appliance
  3. Next is to be logged into the VCSA 6.x appliance via SSH – note this must be an admin account.  I used the local root user and password
  4. Run the following command to begin the installation process: software-packages install –iso –acceptEulas

  5. When completed issue the reboot command: shutdown reboot -r “Updated, thanks to my buddy jermsmit”

     

Congrats you have upgraded.

Info sources:

VMware KB – for additional info

William Lam – who’s tweet informed me of this release, thanks dude

 

I hope you enjoyed this post, thanks for visiting – jermal

Tech Short: Change Password VMware vCenter 6

The day would come where I would need to change my password in vCenter… Today was that day; Thankfully vCenter places am informative notice of your expiring password.

Here is how you can change your password using vCenter 6:

Log into vCenter 6

  1. Click Home.
  2. Click Administration.
  3. Click Single Sign-On > Users and Groups.
  4. Click the Users tab.
  5. Right-click the affected user account, selecting edit user
  6. Enter in the current password, followed by your new (it could be the same, I don’t ever recommend this practice)
  7. Click OK to save changes.

 

I hope you enjoyed this techshort, thanks for visiting – jermal