Latest Posts


Total Pageviews

Thursday, 29 January 2015

Large VM copy to vCloud Director fails with "OVF Import failed. Attempted read from closed socket." error (2041322)


Copying a large virtual machine to vCloud Director can fail during the "import to destination cloud" phase for the following reasons:
  • Destination vCloud Director does not have enough storage on transfer spooling area 
  • Transfer session timed out


  1. Increase the transfer spooling area of vCloud Director by mounting the required storage to /opt/vmware/vcloud-director/data/transfer.
  2. Increase the vCloud Director transfer session timeout: 
    1. Log on to vCloud Director as a system administrator.
    2. Select the System > Administration tab, then select General in the Administration panel.
    3. Under Timeouts, increase the Transfer session timeout.


General System Settings - vCloud Director

Cloud Director includes general system settings that you can modify to meet your needs.
General System Settings
Synchronization Start Time
LDAP Synchronization
Time of day to start LDAP synchronization.
Synchronization Interval
LDAP Synchronization
The number of hours between LDAP synchronisations.
Login policy
Login Policy
Select a login policy.
Activity log history to keep
Activity Log
Number of days of log history to keep before deleting it.
Type 0 to never delete logs.
Activity log history shown
Activity Log
Number of days of log history to display.
Type 0 to show all activity.
Display debug information
Activity Log
Enable this setting to display debug information in the vCloud Director task log.
IP address release timeout
Number of seconds to keep released IP addresses on hold before making them available for allocation again. This default setting is 2 hours (7200 seconds) to allow old entries to expire from client ARP tables.
Allow Overlapping External Networks
Select the check box to add external networks that run on the same network segment.
Enable this setting only if you are using non-VLAN-based methods (for example, VMware vShield Manager) to isolate your external networks.
Default syslog server settings for networks
Type IP addresses for up to two Syslog servers for networks to use. This setting does not apply to Syslog servers used by cloud cells.
Provider Locale
Select a locale for provider activity, including log entries, email alerts, and so on.
Idle session timeout
Amount of time the vCloud Director application remains active without user interaction.
Maximum session timeout
Maximum amount of time the vCloud Director application remains active.
Host refresh frequency
How often vCloud Director checks whether its ESX/ESXi hosts are accessible or inaccessible.
Host hung timeout
Select the amount of time to wait before marking a host as hung.
Transfer session timeout
Amount of time to wait before failing a paused or canceled upload task, for example upload media or upload vApp template. This timeout does not affect upload tasks that are in progress.
Chargeback Event History to Keep
Number of days of chargeback event history to keep before deleting it.
Chargeback Event Cleanup Start Time
Time of day to start chargeback event history cleanup.
Provide default vApp names
Select the check box to generate default names for vApps.
Enable upload quarantine with a timeout of __ seconds
Select the check box and enter a timeout number representing the amount of time to quarantine uploaded files.
For more information about working with quarantined files, see Monitoring Quarantined Files.
Verify vCenter certificates
Select the check box to allow vCloud Director to communicate only with trusted vCenter servers. Click Browse to locate the JCEKS keystore and type the keystore password.

Source VMware Documentation

XaaS - Anything as a Service

Monday, 26 January 2015

Notice of vCenter Chargeback Manager End of Availability

VMware has announced the End of Availability of all versions of VMware® vCenter™ Chargeback Manager™ for non-Service Provider customers, effective of June 10, 2014. 

All support and maintenance for the removed versions of vCenter Chargeback Manager will be unaffected and will continue as per VMware Life Cycle Support Policy through the published support period, June 30, 2015. Existing customers can continue to use vCenter Chargeback Manager beyond the End of Availability and receive customer support until June 30, 2015.

vRealize Suite Consist of

Special Thanks to VMware for the Image

Sunday, 25 January 2015

vRealize Business Taxonomy & Definitions

Before we dig into the solution itself, it is important to understand the key components that will be referenced in this vRealize Business
  • Cost Model - a visual diagram that demonstrates and cost structure and flow of dollars through an organization.
  • Cost Object - an element of a Cost Model that depicts a single cost item. Examples include server type, storage type, or a specific data center.
  • Cost Group - an element of a Cost Model that is made up of multiple cost objects.  A cost group called 'Physical Servers' would contain several server cost objects like 'Linux', 'Windows', or 'Unix', for example.
  • Cost Driver - in a Cost Model, these are the costs that a cost object inherits from other cost objects. For example, the cost drivers for Servers may be Data Center, Hardware, Software, and Labor.
  • Allocation - in a cost model, this is the spread of costs from one cost object to another. An example would be that costs from Servers are allocated to Applications.
  • Allocation Method - in a cost model, the manner in which costs are pushed to another cost object. This could be based on a predetermined percentage, price, or, most accurately, by actual consumption.

Saturday, 24 January 2015

How to Integrate Redhat (KVM) with vCAC?

1. Configure Redhat (KVM) Server

 2. Create a blueprint for Redhat KVM Virtual Machine

3. Finally Use the Self Service Portal and Request the VM from this portal to verify machine provisioning is completing successfully or not.

How to Integrate AWS with vCAC?

1. Generate the Access ID and Security Key Because that is what we will use as an Username and Password in vCAC Credentials for the AWS.

2. Now in vCAC Login with tenant URL with Infra admin role user and add AWS as an endpoint.

3. Create the Reservation for AWS in vCAC

4. Create a Blueprint for AWS

 5. Request the Machine from self service portal.

Reference Video is here

Tuesday, 20 January 2015

Free Instructional Videos From VMware For VMware Products

 Click Here to Access the Videos

vRealize Automation Step by Step Videos Links

Storage as a Service VMware vCloud Automation Center & NetApp

Click here to Download

Monday, 19 January 2015

Sunday, 11 January 2015

VMware NSX Videos Link

Click Here to watch the VMware NSX Videos

Managing Network Profiles for NSX Integration with vCAC 6.x

Upgrading from vRealize Automation (vCAC) 6.x to 6.1

vCAC 6.x - What's New

vCAC Automated Provisioning with NSX

Migrating to vRealize Automation 6.1 From 5.2



Preparing vCloud Automation Center for NSX Integration

Thursday, 8 January 2015

VMware vCAC Videos Link

Click Here to Watch All the Videos

Friday, 2 January 2015

VMware vSphere “I moved it” or “I copied it” – What’s the difference in these Options?

When you copy or move the data store location of an existing VM running on VMware vSphere you will be presented with a message box (as seen below) in the vCenter Client asking if your VM has either been ‘moved’ or ‘copied’. As you can see the message box also mentions “msg.uuid.altered: This virtual machine may have been moved or copied”, but what does this actually mean?

What is a VM’s UUID?

Firstly, it is important to have an understanding of what a ‘UUID’ (universally unique identifier) is. As the name suggests the UUID is a ‘identifier’ (128 bit integer) which is ‘unique’ to that VM, and effectively gives it a digital fingerprint to differentiate it from other VMs.

The UUID is automatically generated when a VM is first powered on or moved, with the UUID value being based on the physical host’s identifier and also the path to the VM’s configuration (vmx) file. Within this configuration file the UUID value is stored in two places:
  • uuid.bios
  • uuid.location (hash based on the current path of the VM)

For example: uuid.bios = "56 4d 5e 58 66 f5 2d 04-03 31 0a bd 6f a7 19 88"

The UUID is also stored in the SMBIOS system information (ie: the BIOS of the VM) descriptor. When the VM is started or moved the location UUID (ie: uuid.location) which is hashed from the VM’s data store path is compared to the UUID location hash which already exists in the configuration file. At this point if the new and existing location UUID value differs then ESX knows that the VM is now running from a different data store location and will present the ‘Virtual Machine Message’ in figure 1 above.

We saw in the message above provided by ESX informing that the UUID has in someway been altered but why does this really matter? The answer to this you’ll be pleased to know is quite simple. A VM’s unique UUID is used to generate other unique values used by the VM such as the unique MAC (media access control) address of the network card(s). For example if you had multiple copies of the same VM/Guest OS running in your vSphere environment all with the same (ie: non-unique) network MAC address you will likely receive duplicate MAC address error messages within the guest OS which can cause a number of issues.

Another potential point to be mindful of is that some software licensing can be linked to a MAC address of a guest OS’s network card. This includes software such as Microsoft Windows where changing the MAC address and some other key hardware components (eg: moving from an Intel based ESX host to a AMD based ESX host) can mean you have to re-activate the software again. The changing of a VM’s MAC address will occur when you select “I copied it”, the next couple of sections will go into more detail on what exactly is altered.
Should I Select “I Moved It” or “I Copied It”?
So what is the difference between selecting “I_moved it” or “I_copied it”? The easiest way to demonstrate the differences is by viewing the configuration file (vmx) for the VM before and after the two different options have been selected. 

“I Moved It”

By indicating that you had moved the VM (instead of copying it) the only UUID change that is made to the configuration file is to the ‘uuid.location’ setting, which as you’d expect indicates a change of location for the VM. The ‘uuid.bios’ and the existing generated network MAC address remains that same.

You will also notice that the CPUID settings have also changed which is also the case for when you indicate that the VM was copied.

The “I Moved It” option should be used when ‘moving’ the location of where a VM resides and a copy of the VM has not been made.
“I Copied It”

When you select that the VM has been copied then there a few more changes that are made to the VM’s configuration file when compared to just moving it. These changes are to the ‘uuid.bios’, ‘uuid.location’ and as a result of these changes a newly generated network MAC address (ethernet.generatedaddress).

The “I Copied It” option should be used when you’ve made, and intend to run, more than one copy of the VM in your vSphere environment.

To summarise, here is a table which outlines the changes that are made when either the “I Moved It” or “I Copied It” are selected

As you can see it is worth spending the time to understand the changes which will be made when presented with the “I moved it” or “I copied it” options as it can impact (eg: software re-activation) the guest OS of the VMware vSphere VM.

I hope this helps clarify this small aspect of VMware vSphere administration which can sometimes be an area of confusion.