Hi Guys,

I've having a strange issue upgrading from ESXi 5.5 Update 2 to ESXi 6.0 Update 1. I've following hardware:

HP ProLiant BL460c G7

6 CPUs x 2.533 GHz

Intel (R) Xeon(R) CPU

E5649 @ 2.53GHz

VMware compatibility matrix shows that this hardware is compatible with ESXi 6.0 Update 1. When I upgraded from ESXi 5.5 Update 1 to ESXi 6.0 Update 1 my host networking is't working. On iLO console I can see host showing upgrade to ESXi 6.0 Update 1 with all the configs still in there, but I can't ping it in or ping out of it. Also it's really slow if I want to change options in the shell.

I tested to revert it back to ESXi 5.5 and everything started working as before.

Could someone please help me with this? Do I need to upgrade some drivers to make this working?

Regards,

Mobin

After updating a mixture of G7, G8 and G9 VMHosts to 5.5 update 3a and Cookbook release September 2015 (SPP JUN 15). I started having host errors specifically on my G7 hardware. One host went so far as to disconnect from VCenter.

I went the full boat update on the OS to bring it fully in line with HP's recipe. This was the first time hitting drivers in quite a while. So when the first errors started coming in, I immediately suspected the HPSA v106 ( Version:5.5.0.106-1OEM ) which was updated from v50 ( Version:5.5.0.50-1OEM)

VCenter is reporting errors

Lost access to volume 56424481-7f094eb0-8ee6-

80c16e6e15e0 (VMHost_local) due to

connectivity issues. Recovery attempt is in

progress and outcome will be reported shortly.

info 2/2/2015 9:00:45 AM (VMHost_local)

VMKernel.log was reporting some conflict's with claim rules between PowerPath and the NMP for the local disk but that was cleared.

2015-11-29T07:53:04.162Z cpu22:33327)WARNING: LinScsi: SCSILinuxAbortCommands:1843: Failed, Driver hpsa, for vmhba1

Hostd.log

2015-11-30T19:37:48.614Z [248C4B70 info 'Vimsvc.ha-eventmgr'] Event 1820 : Lost access to volume 4ffd89b4-760e9689-81e3-e83935a81a45 (gldpiesx002_local) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.

2015-11-30T19:37:48.615Z [248C4B70 info 'Vimsvc.ha-eventmgr'] Event 1821 : Successfully restored access to volume 4ffd89b4-760e9689-81e3-e83935a81a45 (gldpiesx002_local) following connectivity issues.

I opened tickets with both HP and VMWare

VMWare came back with the first fix which was to upgrade the hpsa driver(hpsa 5.5.0.114-1OEM) which can be downloaded from https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI55-HP-HPSA-550114-1OEM&productId=353. however overnight , the errors returned.

HP has suggested back-revving to 5.5.0.74-1(1 Oct 2014) but from a previous discussion here [ Datastore / Disk latency problems with HP ProLiant DL380 G7 - HP Smart Array P410i controller after SPP 2014.09.0 / hpsa-5.0.0.74 update   ]  I believe that was also a bad version.

I'm going to wander down the road a bit and see where it leads and if necessary go back to the 70 or even 50 release

Comments welcome

Hi There,

I'm going to be configuring an environment with ESXi6 hosts (vCenter Standard Licencing), and we will be using Datacenter Bridging (DCB), with Mellanox QSPF+ Converged Network Adapters (CNAs).

I've been searching for some information on the specifics of vSwitch configuration with this type of setup in mind and was wondering if anyone can point me in the right direction?

Thanks in advance

I am in the process of upgrading from vSphere 5.1 to 6.0.  All of our ESXi hosts boot from SD Cards and do not use the local array controllers (they don't even have disks).  We have had some internal discussions about the necessity to update the Array Controller drivers and firmware on our ESXi hosts if we don't use the Array.  Those that are for updating the drivers are firmware are concerned about potential issues when the OS scans the controller (either on boot for when scanning for new volumes) if the firmware or drivers were written for vSphere 4.1.  Those that are against updating the drivers and firmware feel that since there are no disks there is no issue. 

Does VMware have any specific recommendations? 

What others are doing regarding the Array Controller drivers on systems that don't use local disk (i.e. boot from SAN, Auto Deploy, SD Cards). 

Thanks. 

P.S.  We are using HP Proliant DL and BL series servers, but I would assume this would apply to any vendor. 

Looking for someone who knows Xaas, vRO and vRA7

Here is our scenario

I want to send a notification email at the very end of a machine being built, after all software components have been executed.  Our blueprints have software components run after a machine is built.  We use software components to run custom commands to install software on Linux and Windows machines.  I'd LOVE to use the EBS (event broker service), but this is no longer viable after machine is built and I don't want to send custom emails using EBS, which would send a custom email in the middle of the build.

I'm looking to pass a set of properties (list below) back to a Xaas blueprint, write data locally on the machine or on a powershell host.  My last software component would read the data, send the custom email to the end user.  Our current self-service portal sends emails at the end to notify the machine is done.  The custom notification system implementation is less than ideal and is almost impossible in customizing.

Any ideas??

Do I use custom resources? I've read the docs and wondering if this is a potential workaround??

vRealize Automation 7.0

Custom Properties and a set of these are the properties I'm referring to above

Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.BuildingMachine : *

   Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.Disposing : *

   Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.MachineActivated : *

   Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.MachineProvisioned : *

   Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.Requested : *

   Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.UnprovisionMachine : *

All plug-in for vRA is installed in vRealize Orchestrator, right? Or some plugin for vRA has to be installed in vRA?

Hi All.

I have been asked to create a VM that requires: " Virtual Server needs to be configured to allow the Processor Serial Number (Processor ID) to be persisted. "

The only CPUID-type setting I am aware in a VM configuration is CPUID Mask: Expose the NX/XD flag to guest or not. Is this what they mean with their requirement?

I though that a CPU's ID would be virtual for that VM only and following it if the VM is migrated.

Any thoughts or help is appreciated.

- Dave Claussen

Hello,

I am testing a vSphere upgrade in a test network.  Basically I restored, using Veeam a DC, Internal CA and our vCenter windows VM's into their own test network, internet access provided by proxy when needed via Veeam SureBackup Lab Proxy.

Anyway I learned through the process that vSphere 6.1 will require a SQL upgrade.  No problem, Upgraded SQL express 2005 to 2012.  Sucessful so I performed the same upgrade in the live environment, as well as remove and recreate the ODBC drivers using the updated SQL Server 11.0 client.

So now in my lab vCenter 6.0U2 is up and running, esxi hosts obviously "not responding" since this is just a lab for learning... but the next thing I need to figure out is how to get SRM and vSphere replication upgraded.  I don't think I can test vSphere replication as this is in a test network with no actual ESXi hosts, but I should be able to get the SRM components installed correct?

Coming from vCenter serve 5.0 update 3, we were on the vSphere replication that involved 2 VM's, a management server and a replication server, version number 1.x.  SRM is version 5.0.3.

For no good reason it doesn't seem like VMWare built in upgrade routines to take you from 5.0.3 directly to 6.1, unlike vCenter server which has no qualms about such a big jump (must be two different teams with different motivational levels).  So I take it you have to take SRM 5.0.3 to 5.5.1-3572851 and then take that 5.5.1 to 6.0 and then take 6.0 to 6.1, according to the upgrade path.

However I go to install it and first it warns me that I need to create a 64-bit DSN.  I believe that is done by running C:\windows\syswow64\odbcad32.exe, so I do so and I create the same DSN name and pointer that I have under C:\windows\system32\odbcad32.exe.  That should take care of the requirement I would think, anyway in both cases doing a "TEST" indicates a successful connection to the database.  The next step asks if I want to include VSphere Replication, yes I do, then finally credentials to the vCenter server. I enter the brand new Administrator@vsphere.local credentials that I created during the 6.0U2 upgrade (which work great by the way either with the C# client or the web interface), but when I click next I get an "Internal error: unexpected error code: -1.". First thing I do with such a message is google it, along with Site Recovery Manager.  Since I'm not coming up with anything clear from others I decided to post here.

Any idea the best upgrade path?  Should I just start SRM over?  What ramifications would I have?  I'm replicating 28 VM's, and if its just a days work great... however if ALL the data has to be deleted and then rehydrated over the 50mbps wan, it could take a month. 

In my all flash vsan, I see I have 32GB as space VM OVERRESERVED but I do not have any policy with a kind of space reservation so how this overreserved space is allocated ?

I will shortly be embarking on a project to upgrade all of my Servers to Windows 2012 and want to make the process as slick as possible to reduce the amount of time.

At the moment, our process is that you clone the VM from the Template, and then run 'sysprep /generalize /oobe' on the VM, but when I am trying that on our Windows 2012 machine, it does actually revert to being 'out the box' and I lose the customization which is in the Template.

I know that I can use the wizard in vSphere when cloning a VM from the Template to do the customization, but my IT Team want assurance on what sysprep options are run as part of the wizard.  Does it call sysprep in the same way as me actually running sysprep locally?

Thanks!

I am running VM 12.1.1 on Windows 10.

I have a created a Windows 10 virtual machine with several snapshots. I need to move this to a different location so I copied the full VM directory to a different drive. Checked properties on this new folder and the original folder and they are the same size and contain the same number of files. After moving the files to a new location and cleaning out the VM library, when I try to open a snapshot I get an error stating "Error restoring snapshot: One of the disks in the virtual machine is already in use by a virtual machine or by a snapshot". If I try resuming the machine I get a similar error. So the VM machine in the new location is totally inaccessible. I have tried this twice now thinking perhaps something it did not copy correctly the first time, but I run into the same issue.

Any ideas on what is causing this? Is there a better way to be moving the virtual machine?

Hello,

We have a puzzling issue with 2 of our vCenter appliances.  The hardware tab has no data, or at best shows sensors with no data. (note this is not the same as VMware KB: In the vSphere Web Client in vCenter Server 6.0 the Hardware Status tab reports: No host data available)

My dev vCenter appliance started showing this behavior in December.  Worked fine for about 2 months post upgrade from 5.5.   We've had a case with support open since then with no results.

This past weekend, we migrated our production hosts to a clean install 6 appliance, and now this appliance is showing the issue.

Before the migration to the clean prod install, the hardware status tab was working for host that tested the migration.  This is no longer the case.

If I use the fat client and log into a host directly, the hardware status is working.  The issue is with the vCenter appliances themselves. 

Has anyone else ever seen this behavior?

Thank you in advance.

Dear All,

I have two vCenter with external PSC:

1 vCenter with External PSC in Europe region-physically located

1 vCenter with External PSC in Americas region- physically located

Can anyone assist me how to connect two PSC for these two regions as I want to have a single console to monitor two vCenter.

Is there any cons in connecting two vCenters.

Regards,

Anand S

Hello!

I tried to update the (beautiful) ESXi UI to the latest version 7 using Help -> Update, but even though the update runs successfully the UI is still saying it's a 6.0.0 (Build 3620759) version.

I did not try to upload the fling and run the command line, one because i'm lazy but two in case you have questions / things to try to fix it through the help -> update method, since i'm in no big rush to update the working 6 version.

Thanks!

Screenshots attached.

Какая-то ерунда с принтерами стала твориться в Horizon View 6.2, в 5.3 такого не было. Верю что задумка благая, но у меня работает так:

В случае подключения к ВМ через клиента ПК в списке устройств показываются принтеры моего ПК. Если подключение происходит с тонкого клиента, то не видно ни одного принтера, даже встроенных "Fax", "Microsoft XPS" и "Отправить в One Note 2013" (появляется после установки офиса). Если ставлю драйвер принтера из под ПК, то принтер появляется. Потом человек заходит с клиента и принтера не видит, как и всего остального. Попробовал ставить принтер с аналогичного клиента (он потом остаётся), но тут выяснилось что он снова пропадёт после очередного подключения с ПК. Что это за технология и как её настроить нормально или может отключить?

Hello Gurus,

Offlate i noticed an event log entry in vSphere client twice in short span of less than a day related to local storage as follows:

Lost access to volume

4f4c8bc0-4d13eab8-c8fc-5cf3fc09c3fa (vms-1)

due to connectivity issues. Recovery attempt is in

progress and outcome will be reported shortly.

info

8/18/2013 2:01:22 AM

vms-1

and immediately

Successfully restored access to volume 4f4c8bc0-

4d13eab8-c8fc-5cf3fc09c3fa (vms-1) following

connectivity issues.

info

8/18/2013 2:01:22 AM

nesxi1.x.x

The event details itself recommends "Ask VMware" link leads to VMware KB: Host Connectivity Degraded

and

this VMware KB: Host Connectivity Restored

As per the KB VMware is referring to SAN LUN, but in our case its the local storage, kindly shed some info as to why the local storage would lost its connectivity.

Note: all the local disk are on RAID-10.

thanks

I am currently developing a Web application around VMware vCloud SDK for Java 5.5.0. However, I cannot query the metrics entities unless I specify API version 5.6.

I looked for version 5.6.0 of the VMware vCloud SDK for Java everywhere without success. My question is: does VMware vCloud SDK for Java 5.6.x exist, or am I stuck with VMware vCloud SDK for Java 5.5.0?

Thx!

Hello,

We had a system with 1 ESXi 5.1 host with local disks.

Now we install redundancy by adding an ESXi 5.5 U2 host and a vCenter 5.5 appliance.

After installing and adding everything to vcenter, we upgraded the ESXi 5.1 to ESXi 5.5 U2. The SAN is operating correctly (vMotion is working on seperate NIC).

Now, if I try to enable High Availability, both servers will install the HA Agent, and start "Election".

All datastores (4) on the SAN are chosen for the HA heartbeat, isolation response is "keep powered on" default.

One server will always get this process done, and the other will keep "electing" until it gets to 100% and errors on the election "operation timed out".

I have seen this problem on both servers, so I think the elected "master" does not have the problem, only the "slave".

I have checked these articles and executed them, but non worked:

VMware KB:     Reconfiguring HA (FDM) on a cluster fails with the error: Operation timed out  

- The services were running

VMware KB:     Configuring HA in VMware vCenter Server 5.x fails with the error: Operation Timed out  

- All MTU's were set to 1500

VMware KB:     Configuring VMware High Availability fails with the error: Cannot complete the configuration of the HA ag…

- the default gateway was not the same on both hosts, but I corrected this. There are no routings. HA setting is "leave powered on". After correcting and disabling/reenabling HA, problem is still the same.

VMware KB:     Verifying and reinstalling the correct version of the VMware vCenter Server agents  

- I executed "Reinstalling the ESX host management agents and HA agents on ESXi" for the HA Agent, and I verified that it was uninstalled and reinstalled when reenabling HA.

cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
/tmp/VMware-fdm-uninstall.sh

I did this for both hosts. This actually fixed the election problem, and I was even able to run a HA test succesfully, but when after this test I powered down the 2nd server (to test the HA in the other direction), HA did not do the failover to the 1st and everything remained down. After pushing "reconfigure HA", the election problem appeared again on 1 of the hosts.

These are some extractions from the logs:

-The vSphere HA availability state of this host has changed to Election  info  11/29/2014 10:03:00 PM     192.27.224.138

-vSphere HA agent is healthy  info  11/29/2014 10:02:56 PM     192.27.224.138

-The vSphere HA availability state of this host has changed to Master  info  11/29/2014 10:02:56 PM     192.27.224.138

-The vSphere HA availability state of this host has changed to Election  info  11/29/2014 10:01:26 PM     192.27.224.138

-vSphere HA agent is healthy  info  11/29/2014 10:01:22 PM     192.27.224.138

-The vSphere HA availability state of this host has changed to Master  info  11/29/2014 10:01:22 PM   192.27.224.138

-The vSphere HA availability state of this host has changed to Election  info  11/29/2014 10:03:02 PM     192.27.224.139

-Alarm 'vSphere HA host status' on 192.27.224.139 changed from Green to Red  info  11/29/2014 10:02:58 PM     192.27.224.139

-vSphere HA agent for this host has an error: vSphere HA agent cannot be correctly installed or configured  warning  11/29/2014 10:02:58 PM     192.27.224.139

-The vSphere HA availability state of this host has changed to Initialization Error  info  11/29/2014 10:02:58 PM     192.27.224.139

-The vSphere HA availability state of this host has changed to Election  info  11/29/2014 10:00:52 PM     192.27.224.139

-Datastore DSMD3400DG2VD2 is selected for storage heartbeating monitored by the vSphere HA agent on this host  info  11/29/2014 10:00:49 PM     192.27.224.139

-Datastore DSMD3400DG2VD1 is selected for storage heartbeating monitored by the vSphere HA agent on this host  info  11/29/2014 10:00:49 PM     192.27.224.139

-Firewall configuration has changed. Operation 'enable' for rule set fdm succeeded.  info  11/29/2014 10:00:45 PM     192.27.224.139

-The vSphere HA availability state of this host has changed to Uninitialized  info  11/29/2014 10:00:40 PM  Reconfigure vSphere HA host  192.27.224.139  root

-vSphere HA agent on this host is disabled  info  11/29/2014 10:00:40 PM  Reconfigure vSphere HA host  192.27.224.139  root

-Reconfigure vSphere HA host  192.27.224.139  Operation timed out.     root  HOSTSERVER01  11/29/2014 10:00:31 PM  11/29/2014 10:00:31 PM  11/29/2014 10:02:51 PM

-Configuring vSphere HA  192.27.224.139  Operation timed out.     System  HOSTSERVER01  11/29/2014 9:56:42 PM  11/29/2014 9:56:42 PM  11/29/2014 9:58:55 PM

Can someone please provide me with some help here?

Or extra things I can check or provide?

I am running out of options currenty.

Best Regards,

Joris

P.S. I had problems with Cold Migration when implementing the SAN. After setting up everything (vMotion, upgrading ESX), these problems were gone.

When searching for this error, I came to this article: VMware KB: VMware vCenter Server displays the error: Failed to connect to host

And that cause could make sense, since the vCenter server changed and IP addressing was changed during implementation.

However, in the vpxa.cfg files, the <hostip> and <serverip> is correct (checked using https://<hostip>/host).

Tried this again today, no problem at all.

P.P.S. I have configured more of these systems from scratch in the past with no problem (though this is an 'upgrade').

New to Mirage so i apologize if my problems are due to me!

First, is it possible to deploy a base layer to an out of the box remote computer/laptop over the WAN?  From all I've read the answer is yes, and so i proceeded using the "Provision a Device with Mirage by Using a WinPE Image" instructions in the VMware documentation . 

My problem is that I am getting no where after trying for almost a week of tinkering.

I succeed in creating the ISO and WIM files using the BuildMirageWinPE.cmd

I succeed in creating the bootable usb using the win7usb.cmd

Boot new laptop using USB and I never succeed in getting communication with Mirage server

I have tested with x86 and x64 with similar results.

x64 boot from USB at the deployment machine starts and loops the message "the drive of the specified mount path is not supported"

x86 boot from USB at the deployment machine starts and loops the message "1073741515"

I am using the following versions

x64 - Mirage.WinPE.x64.119795

x86 - Mirage.WinPE.x86.119795.zip

Mirage 5.7

I've added the appropriate mirage client to the C:\BootUSB\MirageClient folder

I've added the network drivers to the C:\BootUSB\Drivers

The hardware is Lenovo T450s laptop with 256G SSD drive and Intel NIC

I've searched everywhere and cannot find resolution.  There is the VMware bare metal provisioning video but that uses WDS, and I am hoping this is not required.  My hope is that WinPE boots and loads the mirage client and then the server would show it as a pending device that I could push a base layer onto.

Help!!  and thank you

Hello,

I am encountering a permission issue with sharing VMs in Workstation.  I have Workstation 12.0.  I am trying to share VM3.  It previously worked to share VM1 and VM2. 

The issue I am encountering is permission to perform this operation was denied.

I have researched various reasons why.  From other posts I can see people have this error or similar in VM product, where they are not administrator, user account control is on.    I am presently logged in as  administrator.  I have UAC off.  I have restarted the VM services a few times.  I have reset the server twice.  My permissions set on shared VM's specify me as administrator.

Does any have any help in solving this issue?

I attached my log file for my VM as well.