ESXi 4.1 upgrade to ESXi 5.0

Similar Questions

• Dell M620 (VRTX) blade - ESXi 5.1.0 Update 1 installation upgrade to ESXi 5.1.0 Update 3 (latest)

  This morning I did an installation of upgrade to ESXi 5.1.0 Update 1 to ESXi 5.1.0 Update 3 (latest Version) on one of the blades of my VRTX M620 three 3.  I have the same problem that I met about a year, when I tried to update 1-2 update.  I had to go down to 1 update to see the data store.

  With update 3, the data store does not appear on this blade.  I did a scan to see if the data store is present, but he did not.  Also, I restarted the blade which did not help.

  I have to keep upgrading to 3 update due to the necessary correction of problem CBT.

  How to troubleshoot and resolve this problem of my data store does not?

  Note: I have very little experience with virtualization.  I just found today on how to access the interface from the CLI of blades.

  Thanks in advance.

  SOLVED.

  The original sas megaraid drivers (even installed on the blades of M620 Dell) had to be installed.  It is my understanding that several versions of the megaraid sas driver provided on the Dell ESXi ISO are meant to satisfy the VMware HCL for this material.  However, the more recent does not show the data store.

• upgrade from 5.1 to 5.5 ESXi ESXi

  Hello

  I have two servers R510 Esxi 5.1.
  I have already updated the server vCenter to 5.5 and am ready to upgrade the network and storage drivers and firmware on the host.

  Is this image VMware-VMvisor-Installer-5.5.0-1746974.x86_64-Dell_Customized_A04.iso that I need?

  It says "VMware ESXi 5.5 Image" on the title...

  Thank you

  Avital

  It's good that the ISO I gave, but DevMgr is correct as well. The R510 is a statement of the 11th generation, so the Vmware 5.5 ISO should have these drivers, but the ISO Dell 5.5 those will have as well as the 12th generation models servers too. So, with the Vmware 5.5 you can do the 11th generation and more. With the Dell ISO you can do all the Dell servers (supporting ESXi) including the 12th generation.

  So both work really, but I'd personally go with the ISO Dell because it's specific to the products.

• ESXi 4.1 upgrade 5.1 in a Dell EqualLogic environment?

  Hi all, I am planning to upgrade our guests ESXi4.1 U1 to ESXi 5.1 Dell R610.  We use a PS6100E EqualLogic via iSCSI.  I installed 5.1 vCenter and prepared Update Manager with the image of Dell Custom ESXi 5.1, thinking that it would contain all the necessary drivers/modules.  However, after analysis of my ESXi hosts, I get the following caveat (see attachment).  Anyone has done an upgrade from 4.1 to 5.1 in a Dell EqualLogic environment?  I'm not warm and fuzzy about the procedure taking into account the warning.  Thank you!

  

  Hello

  There is no requirement for reconfiguration of re - install MEM after the upgrade.  It lies on the existing configuration as before.

  My personal preference is to uninstall 3rd party before the upgrade applications to make the cleaner process.  I don't know problem to upgrade to 1.1.2 and then the ESX upgrade, I have not tried it personally.

• Upgrade to ESXi on NGC

  Hello

  I have esxi4.1 installed on a few servers B200 M2, esxi has been installed with the cisco-ucs-esxi image.

  the question is I want to upgrade to esxi5, what image should I use now? the normal esxi5 of vmware or cisco-UCS-esxi5 image?

  IM upgrading to the formware ucs of 1.4 to 2.0 before that.

  I loaded about 100 B200s with ESXi 5 and never used the standard ISO VMware. The B200s were VIC M81KR adapters.

  To update to 4.1 I did only reconstructions. Many of them had the N1KV VEM and PowerPath VE so I thought it was the safest route.

• UCSM, ESXi upgrade options

  Hi all

  We are running a UCS environment with firmware 1.4.3.i & ESXi 4.1 update 1. We are looking for more to migrate to firmware 2.x & 5.x ESXi & I was wondering if there is a documented/suggested process for this type of upgrade.

  Thank you

  Kassim

  Hello Kassim,

  Here is the overview of high level.

  First of all, make sure that existing (especially the ANC) hardware are supported by ESXi 5.x or not

  http://www.Cisco.com/en/us/products/ps10477/prod_technical_reference_list.html

  IIRC, M71KR is not supported by the version 5.x ESXi.

  Start by upgrading the firmware and follow the steps in the same order as mentioned in the upgrade guide

  http://www.Cisco.com/en/us/products/ps10281/prod_installation_guides_list.html

  Then, upgrade the version of ESXi.

  Finally, update the drivers for ANC / new version of ESXi.

  Padma

• UCS-E140S-M1/K9 ESXi Upgrade Path?

  We have these (UCS-E140S-M1/K9) USCe modules installed in our routers ISR 3945.

  They come delivered installed with a custom Image ESXi profile, or you can download VMware.

  ESXi-5.0.0-623860-custom-Cisco-2.0.1.6.iso

  We can upgrade these modules UCSe to later versions of ESXi (5.1,5.5 etc.)?

  I looked around new custom images that are supported for these modules, but I am unable to find anything.

  I want to better understand the roadmap for these modules, because we must keep all our ESXi hosts, moving forward with the updates.

  These are the only hosts of ESXi, that we always stuck on ESXi 5.

  Hello

  There is updated firmware for devices of the e series that allows for Vmware 5.5

  The E-series release notes

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/e/2-0/release/notes/2_0_release_notes.html

  E-series configuration guide

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/e/2-0/SW/GUI/config/guide/b_2_0_GUI_Config_Guide/b_2_0_GUI_Config_Guide_chapter_010.html#task_14D4360DEF3849CC8BCA24A1ED330854

  The E-series firmware download

  http://software.Cisco.com/download/release.html?mdfid=284479227&softwareid=284480160&release=2.2.2&relind=available&rellifecycle=&RelType=latest

• ESXi VNIC speed fell after upgrade 2.2.2c

  Hello

  I hope someone can help me, I just finished the UCS upgrade to 2.2.2c and noticed that my ESXi hosts (with adapters 1240 B200M3) past the speed of 40000 to 10000.  I came across this bug https://tools.cisco.com/bugsearch/bug/CSCun21077 but my firmware and drivers are newer (2.2.2c and 2.1.2.50).  Anyone else run into this?

  Thank you

  If you hit the bug mentioned, so I guess that you have applied to the vNIC QoS policies? Change rate (KB/s) rate to 40000000 Presented to VMware speed will change immediately. Which unfortunately seems to rate some of the 2.2 release means 10GbE.

• UCS C260 M2 E7-2830 ESXI 5.5 Enterprise Plus for ESXI 6.0 upgrade

  What to upgrade to VMware ESXI 5.5 Enterprise Plus to ESXI 6.0? It s posibble?

  We have 3 servers in collaboration with Vmotion, VMS and startup files live in the SAN.

  Cisco UCS C260 M2

  Characteristics Description quantity
  Cache CPU 2.13 2 E7-2830 105W 8 c / 24 M
  Memory 2 2X16GB DDR3-1333-MHz NHS
  2 Emulex LPe 12002 Dual Port 8Gb Fibre Channel HBA
  1 Intel Quad Port 1 Gb network adapter i350
  O.S.                       1 company of Vmware ESXi 5.5 more

  BIOS C260.1.5.1A.0 17/07/2013
  Firmware 1.5 (3d)

  The Cisco interoperability matrix reference, if you choose the right level of firmware HUU (for example, 1.57, 1.58)

  interop_pic.jpg

  

  Simply adjust the "component" to get the info pilot different devices in your server.

  Kirk...

• Advice on the upgrade to ESXI 4.1.0 to 6

  I have ESXI 4.1.0 260247 that worked for about 5 years now as a champion.  My hard drives are becoming old and I need to upgrade my storage (currently raid 2 x 1 TB 1, need 2 TB of usable space) so I am looking to update my ESXI at the same time.  I'm a show making, software development, my needs are quite simple.  I have machines virtual linux for Jenkins, LAMP, nginx, svn, mysql and I have Windows VMs for Jenkins, MSSQL, versions of office to install testing.  The most great thing miss me with ESXI 4 is I would go an automatic weekly backups of my VM to my QNAP NAS.

  Essentials would be worth the money? I'm Canadian, so please consider I paid 32% more after the exchange of currencies.

  I'm not an experienced administrator, ESXI 4 was free for me problem since day 1.  If I replace all readers at the same time, would be a good upgrade path:

  1 export all as OVF of ESXI4 VMS

  2 replace the discs in Server

  3. installation of 6

  4 import OVF VM in ESXI 6

  Thanks in advance for the entry.

  I would backup all virtual machines to external storage, possible using https://www.veeam.com/virtual-machine-backup-solution-free.html

  Update as needed. You will not be able to skip from 4.1 to 6.0. so a reinstall would be my preferred option.

  Restore VMs return. Note that if you use free ESXi then you probably need to restore files on networked storage and copy them back to the store to host data because free ESXI does not include an API for veeam to restore. https://forums.Veeam.com/VMware-vSphere-F24/question-about-free-ESXi-5-and-restore-job-failed-error-t13345.html

  Essentials is really cheap for what you get. You will be able to use the above correctly, because you then will licenses for the API. You probably want 2-3 hosts so that the benefits of vCenter you get with the license are worth. It is not really worth it for a single host unless you need these API etc.

• ESXi 5.1 upgrade to ESXi 6.0 with 2 warehouses of data on the local host

  Hi, I'm a little new for vsphere stuff...

  I currently have a 5.1 ESXi host who I want to spend to 6.0. I did with another host with several virtual machines on which had a unique and just ran data store Installer, robbed the store of current data so it updated the system, but kept all my config and VMs in tact.

  However, with this other host, its data store has been expanded at some point, and rather than extend the data store, they have created an additional.

  So my question is now, if I run the Setup, what data store I point to and there are likely to be problems I might encounter?

  Thank you and I look forward to hearing from someone soon

  Ben

  Hello

  a multiple data store or data store is no question during the upgrade or install ESXi.

  I guess, you start using ESXi Server ISO.

  Select storage (disk or USB/flash storage) where old ESXi is installed during the Installation (upgrade).

  This allows to detect the existing ESXi installation invites you to upgrade instead of doing the new ESXi installation.

  During the upgrade, select preserve existing and upgrade VMFS ' option to make sure that you keep the old virtual machines and old configuration ESXi.

  Thank you

  Hentzien

  Virtual Admin

• The ESXi 4.1.0 to 6.0 upgrade. -upgarde and best practices

  Hi guys,.

  We are a small business with a single physical server, ESXi 4.1.0 installed with approx. 8 VMs. We plan on buying Essential Kit 6.0 ESXi because that's all we need right now. However, as VMWare says that 4.1.0 to 6.0 upgrade is NOT supported (matrices of the interoperability of products VMware), how we improve our host and VMS?

  I guess the correct way will be upgraded from 4.0. 5.5 U3 first, then to 6.0. However, if we buy the 6.0 license essential Kit, that we will be able to always download and install and upgrade of the host and all VMs to U3 5.5, and 6.0. Essentials?

  In addition, what are the best practices to upgrade a single host with multiple virtual machines? What I did research, we should back up important files from virtual machine, all critical data, etc. All recommendations are welcome. My understanding is that the upgrade also virtual machines will be upgraded automatically, that's correct - methods of upgrade to ESXi 5.5 (2058352) | VMware KB

  Best regards

  D. Stanchev

  Hello

  As you said, you cannot upgrade host ESXi 4.x to 6.x, you must first upgrade 4.x to 5.x and then switch to 6.x

  Before moving to 5 or 6, make sure you ESXi host is compatible with ESXi 6.

  Check cheque and VMware hardware compatibility list if your server is listed.

  Although you'll have a 6 ESXi license kit, you can download ESXi 5.x and use it to upgrade process.

  Only if you need to use 5.x permanently, then you need to get your license keys downgraded to 5.x, otherwise once you upgrade host to 5.x, go ahead and level to ESXi 6.x

  Backup-

  Before you begin the upgrade, make sure that you have backup of all VMs critics.

  Either you can download/export all VMs as OVF, or you can use Veeam's free edition to make the backup of virtual machines

  -Update

  You can join the server ESXi ISO Installer and boot server form ISO and update.

  During the Installation process make sure to select ' PRESERVER VMFS and upgrade ESXi host '

  If you do not keep vmfs, all virtual machines will get deleted during the installation/upgrade process.

  Once you get ESXi Host upgrade to Upgrade VMFS 5.x version so that it can support 6.

  Then finally the ESXi host to 6.x upgrade, yet once make sure PRESERVE you VMFS during installation.

  If you have vCenter Update manager, use update reach the average upgrade easy it is to upgrade.

  Thank you

  Hentzien

• Upgrade to esxi 6 - running in parallel 5.5 versions Enterprise

  Hello together,

  We want to improve our Enterprise 5.5 to 6.0 Enterprise environment more.

  Can we run in parallel business with Enterprise 6.0 5.5 more ESXi hosts.

  or

  We can add the license keys for the company more than 5.5 to existing hosts without any configuration problem, then

  upgrade the esxi hosts to 6.0?

  Thank you

  There is no problem, but I recommend to keep this scenario only during migration.

• One of the ESXi host 3 no HW Compatible for ESXi 6 upgrade?

  Hello

  There are 3 DELL servers (2 of them are running R530 and 1 is executed R900).

  When attempting to upgrade these 5.5 ESXi hosts to ESXi 6, we find that the R900 is no longer supported.

  Wonder what is the best way for us to do - keep using ESXi 5.5 or level 2 of them to ESXi 6 and leave remaining on an ESXi 5.5?   We have no intention to replace the R900 in the near future.

  Thank you

  If all three hosts are part of the ESXi Cluster, then you must do all the guests at the same version level. Therefore, keep all the on ESXi 5.5

  But if you use these host as a standalone ESXi host then you can upgrade the host to ESXi 6 two and let R900 on ESXi 5.5

  Thank you

  Hentzien

  Virtual Admin

• vCenter 5.5 and ESXi 5.5 trial upgrade to the licensed version

  I am currently using a trial of 5.5 and 5.5 ESXi vCenter.  We recently purchased version 6 Kit Essentials.  When I apply my licenses listed, I get a "invalid license key: Lincense file not found" error.  Do I have to upgrade to version 6 before a registered license is accepted?

  Yes, if you are using vSphere 6 key then you will need to use 6 ESXi and vCenter 6.

  don't know if you can get the license keys for 5.5 from your VMware account where the license is attached. You can give a try.

  ESXi update is easy process. It requires unavailability of ESXi host and the virtual machines if you use no shared storage.

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G