Is anyone running Fedora 25 in 4K? I cannot get more than 2560 x 1600, though Fedora 24 had no problem going to 3840 x 2160. The VM is set to use host settings for the monitor, VMWare Tools seems to be installed. Any ideas?

Hi,

I am having the same problem, not possible to install vCenter on ESXi_A. After thousands trys I decided to remove my ESXi_A host from lab1 where I have the problem and install it into lab2 where I have several ESXi hosts and one vCenter; and here no problem to install vCenter successfully. So it seems the problem in lab1 is not related to the ESXi_A host configuration, but once back in Lab1 same problem, vCenter install fails with same callback error message. I have in this lab1 four ESXi hosts and the vCenter install fails on both of them. My network admin pretend there is no network problem in lab1... so it should be the airco... Obviously here, the error message is not helpful,

RGDS

cl.

Hi ,

Could you please check the logs and access to the port 5090

It may related to the SSL certificate

That is correct, but as the 2nd post shows, you use the PowerCLI cmdlets to set up the connection.

And from there you have access to the complete vROPs API.

Hi ,

Please check the below kB  ,  you may have to restart the services and wait for some time.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2121043

I have seen similar problems due to missing/corrupt OVF environment, similar to this: https://kb.vmware.com/kb/2084652

KB recommends power off, and power on but you say that hasn't worked.

Something else that may help: did you deploy the appliance using the Web Client? If you used the old vSphere Client, then try deploying using the Web Client instead.

You can do it from the ISE, but it requires some additional installs.

There is the popular Show-Object function from Lee Holmes's Windows PowerShell Cookbook.

There is ISESteroids, an add-on to the ISE.

But it comes at a price.

The PowerShell Plus editor is another free option, it allows variable inspection and drill down.

They had a new release in March 2016.

And there is another commercial option, the editor in the Sapien PowerShell Suite also allows variable drill downs.

Hi ,

Each Instance refereed to vCenter Server  , Please refer below for detailed information .  Also based on the number of vCenter Instance only Licencing , and it varies based on configurations such as linked mode .

https://pubs.vmware.com/view-50/index.jsp?topic=%2Fcom.vmware.view.administration.doc%2FGUID-F8210848-BBF9-4943-BCD8-75E7F5AEFEE8.html

From a monitoring perspective, I am pretty that what I described applies actually. Your wmi monitoring reports more accurate data because it is guest centric as opposed to vsphere that reports what it sees going through the pipe.

If you are licensed for vrops advanced (as mentionned there), like you said it would be more relevant to install the vRops agent on your top tier VMs and monitor them from there.

If this change in behaviour isn't expected (no changes have been made) then I would try and pin down the issue on the guest OS like check the eventvwr for errors, user sessions disconnected but still here, stuck process, maybe even try to give it a reboot if that's an option.

If this increase in workload can be explained (lot of new rdp users, new service, or whatever) then I would add an extra 5GB of ram to give it some slack and adjust if needed.

Hi guys!

I have two servers with the boards Supermicro X8STE + Xeon 5504 and X8DTL-IF + Xeon 5504. I can install on these servers only ESXi-5.1. If you try to install other version, then after booting from the CD the process stops with the inscription "Loading /state.tgz Relocating modules and starting up the kernel...". Then nothing happens. The VMware vSphere Client connects, operates, there is no problem. The same is repeated and when upgrading. I can install ESXi-5.1, then upgrade it to version 5.5, 6.0, 6.0U2, etc (ssh + ESXi*.zip).  But at the starting of the server I see on the screen only one line "Loading /state.tgz Relocating modules and starting up the kernel...". In version 5.1 I see the invitation to the settings, F2, etc. Why is that? Can this be fixed?

Продублирую на русском.

Есть два сервака с платами Supermicro X8STE + Xeon 5504 and X8DTL-IF + Xeon 5504.

Получается установить только ESXi-5.1.

При попытке загрузки CD с более новой версией весь процесс останавливается с надписью "Loading /state.tgz Relocating modules and starting up the kernel...".

То же самое происходит и при обновлении. Можно установить версию 5.1, затем обновиться через ssh до 5.5, 6.0, 6.0U2 и т.д.

При этом VMware vSphere Client подключается и все работает хорошо, но на экране монитора при запуске висит все то же сообщение "Loading /state.tgz Relocating modules and starting up the kernel...".

Почему так и можно ли все это починить?

Would be interested to hear your say on the below issue:

We assume that all start menu settings are under taskbar...So, This is what we have set for TaskBar settings under UEM 9.0

Still, once the user erase some of his shortcuts from the startup menu - they re-appear in the next session...meaning this is not getting saved. any ideas?

Any help would be greatly appreciated for the above issue...

thanks!

what do you think of having a vCenter 6.0 managing ESXi 5.5 and 6.0 hosts in the same cluster?

vCenter 6.0 support and it will manage Esxi 5.0 to 6.0 , so you may use same vCenter to manage them .

If you have enogh resources , you may go with multiple cluster for differnt H/W .

good practice? might happen something unpredictable ?

Good practice is cluster with the same hardware and same ESXi version .

any recommendation?

Try to keep all hosts in a cluster with the same hardware and same version.

This will avoid issues such as VM tools / VM hardware compatibility on different ESXi versions .

Hi ,

If you need to migrate or deploy  vCenter new VM / Appliance you don't need to power off ESXi hosts /  VMS .

Deploy New vCenter - VCSA

1 . Deploy New VC

2 . Disconnect the esxi host from old VC

3. Connect the ESXi on new VC

4. Apply Licences

* you have to note the Licence details

  If you gonna use old VC IP and Name for new , then you have disconnect ESXi from Old  VC and shutdown as normally .

  While deploying new VC you can provide name and ip

Migration

1. Disconnect the ESXi hosts

2. you can follow below link 

vCenter Server Migration Tool: vSphere 6.0 Update 2m - VMware vSphere Blog

3. once migration completed you can  verify the vCenter and connect the ESXi hosts

4. You may do normal shutdown of the Windows VC

Hi ,

First you have to add the ESXi host to domain

Add the Domain Name to Preferred Domain Controller Entry

Provide the permission for the Group or User

You may get a error message some times you can ignore that after verifying host is in Domain or Not .

Also some time adding the host to Domain may fail with providing credentials format , so you have to follow both options  ( admin@domain.com /  domain\admin  )

Reboot is not mandatory but if you are facing any trouble on login , first you can restart the services  after that same issue go with reboot .

Hello,

I'm creating reporting script (aren't we all) to server various VMware environments, and one thing to get reported would be ESXi installation type.

This is possible via SSH running "esxcfg-info -e" ( Determining the ESXi installation type (2014558) | VMware KB )

Problem is that esxcfg-info does not have PowerCLI equivalent out of the box. I found William Lams script for this: Using the vSphere API to remotely collect ESXi esxcfg-info | virtuallyGhetto

But the output info from this does not hold "boot type" or "visor-" info, which I could parse out.

Has anyone done this kind of info pull with PowerCLI so far?

The obvious step is (in case type is visor-thin) to see if ESXi host is installed on local disk or SAN LUN. KB article for this is Identifying ESXi/ESX boot LUNs for Boot From SAN configurations (2030957) | VMware KB

-Mikko

hi please could you clarify what you mean by baseline data protection?

what action do we need to take to resolve this?

we have 3 identical vm's, 2 set up in August ok, one now which is showing the error

Hi,

Is it possible to somehow lock a vRA blueprint to prevent its modification by others?

Thanks,

Leonid

Upgrade from 6.0 HPE to 6.5 via cli fails with dependencies error :

Host in Maintenance mode.

Command used :

esxcli software vib update -d /vmfs/volumes/500GB\ Storage/VMware-ESXi-6.5.0-OS-Release-4564106-HP

E-650.9.6.0.28-Nov2016-depot.zip

And output :

[DependencyError]

VIB VMW_bootbank_uhci-usb-uhci_1.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-mlx4-en_1.9.7.0-1vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Intel_bootbank_net-igb_5.3.1-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Intel_bootbank_net-i40e_1.3.45-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-via_0.3.3-2vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bnx2i_2.713.10.v60.3-1OEM.600.0.0.2494585 requires com.vmware.iscsi_linux-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-ata-piix_2.12-10vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-ata-piix_2.12-10vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-forcedeth_0.61-2vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.650.0.0.4564106 requires com.vmware.libfc-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_uhci-usb-uhci_1.0-3vmw.650.0.0.4564106 requires com.vmware.usb-10.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-svw_2.3-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Intel_bootbank_net-ixgbe_4.1.1.1-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-serverworks_0.4.3-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-sil24_1.1-1vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-qla4xxx_644.6.05.0-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-nv_3.5-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-sil_2.3-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_xhci-xhci_1.0-3vmw.650.0.0.4564106 requires com.vmware.usb-10.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-vmxnet3_1.1.3.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_xhci-xhci_1.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-nv_3.5-4vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ohci-usb-ohci_1.0-3vmw.650.0.0.4564106 requires com.vmware.usb-10.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-sil24_1.1-1vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_misc-drivers_6.5.0-0.0.4564106 requires com.vmware.vmkplexer-4.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ohci-usb-ohci_1.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-qla4xxx_644.6.05.0-1OEM.600.0.0.2494585 requires com.vmware.iscsi_linux-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-megaraid2_2.00.4-9vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_misc-cnic-register_1.713.10.v60.1-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bnx2i_2.713.10.v60.3-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-sil_2.3-4vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-amd_0.3.10-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bnx2fc_1.713.20.v60.4-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-e1000_8.0.3.1-5vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_net-bnx2_2.2.6a.v60.4-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-mlx4-core_1.9.7.0-1vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-sil680_0.4.8-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-pdc2027x_1.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bnx2fc_1.713.20.v60.4-1OEM.600.0.0.2494585 requires com.vmware.libfc-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-fnic_1.5.0.45-3vmw.650.0.0.4564106 requires com.vmware.libfcoe-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ehci-ehci-hcd_1.0-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-mptsas_4.23.01.00-10vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-ahci_3.0-22vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_net-bnx2x_2.713.10.v60.4-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB BRCM_bootbank_net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_net-qlcnic_6.1.191-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Hewlett-Packard_bootbank_scsi-hpsa_6.0.0.116-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bnx2fc_1.713.20.v60.4-1OEM.600.0.0.2494585 requires com.vmware.libfcoe-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-promise_2.12-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-mptspi_4.23.01.00-10vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-cmd64x_0.2.5-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ipmi-ipmi-devintf_39.1-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ehci-ehci-hcd_1.0-3vmw.650.0.0.4564106 requires com.vmware.usb-10.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-atiixp_0.4.6-4vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-ahci_3.0-22vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-svw_2.3-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-enic_2.1.2.38-2vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_net-e1000e_3.2.2.1-2vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-aacraid_1.1.5.1-9vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-aic79xx_3.1-5vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-amd_0.3.10-3vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-adp94xx_1.0.8.12-6vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_net-nx-nic_6.0.643-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_ata-pata-via_0.3.3-2vmw.650.0.0.4564106 requires com.vmware.libata-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_scsi-ips_7.12.05-4vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_block-cciss_3.6.14-10vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB HPE_bootbank_scsi-hpdsa_5.5.0.54-1OEM.550.0.0.1331820 requires com.vmware.driverAPI-9.2.2.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMW_bootbank_sata-sata-promise_2.12-3vmw.650.0.0.4564106 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

VIB QLogic_bootbank_net-cnic_2.713.20.v60.5-1OEM.600.0.0.2494585 requires com.vmware.driverAPI-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

Hi ,

Please try like below commands

1. Download the file from My VMware portal (esxi6.0-6.0_update02.zip- example).

2. Upload this file to the datastore visible by your ESXi host.

3. Put your host in maintenance mode

4. access host through putty / DCUI

5. esxcli software profile update -d /vmfs/volumes/datastore1/update-from-esxi6.0-6.0_update02.zip -p ESXi-6.0.0-20160302001-standard

Check the Profile Details

6. Reboot your host and exit maintenance mode.

esxcli software profile update -d /vmfs/volumes/datastore1/ESXi600-201601001.zip -p ESXi-6.0.0-20160101001s-standard

(it will list the profiles image below )

run with required profile

esxcli software profile update -d /vmfs/volumes/datastore1/ESXi600-201601001.zip -p ESXi-6.0.0-20160101001s-standard

Hi ,

1. You can use Active - Active  fail over mode .

2. You can configure OS level multi-path

3. you can use two virtual switch and  H/W iSCSI mode