5 Replies Latest reply on May 15, 2019 9:48 AM by dcolpitts

    HP Gen8 with HPE Customized ESXi 6.7 U2 - Problem with patch ESXi-6.7.0-20190404001

    klemens.urban Lurker

      Hello,

       

      i try to update one of our HP Gen8 Server to ESXi-6.7.0-20190404001 unfortunately the whole thing does not work due to a dependency problem.

      (I know it's not officially supported for Gen8 Servers)

       

      The process was as follows

       

      VMware ESXi, 6.0.0, 8934903 -> Update to "VMware ESXi, 6.7.0, 13006603" with the HPE Customized Image - worked without any errors

       

      VMware ESXi, 6.7.0, 13006603 -> Update to "VMware ESXi, 6.7.0 13473784"  with the "ESXi-6.7.0-20190404001" Patch - Dependency Error

      Install Command was "esxcli software profile update -p ESXi-6.7.0-20190404001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml"

       

      [DependencyError]

      VIB EMU_bootbank_scsi-be2iscsi_11.1.145.8-1OEM.600.0.0.2494585 requires ima-version2, but the requirement cannot be satisfied within the ImageProfile.

       

      esxcli software vib list | grep ima

       

      elx-esx-libelxima-8169922.so 12.0.1188.0-03 ELX VMwareCertified   2019-05-07

      ima-be2iscsi 11.1.145.8-1OEM.600.0.0.2494585 EMU VMwareCertified   2019-05-07

      ima-qla4xxx 500.2.02.20-1vmw.0.5.021123 QLogic VMwareCertified   2019-05-07

       

      Which package is meant by "ima-version2"?

      I tried to install "EMU_bootbank_ima-be2iscsi_12.0.1108.0-1OEM.600.0.0.2494585", unfortunately without success

       

      Thank you for your support

        • 1. Re: HP Gen8 with HPE Customized ESXi 6.7 U2 - Problem with patch ESXi-6.7.0-20190404001
          Sureshkumar M Expert
          vExpert

          Hi ,

           

          Can you please attach esxupdate.log file to check .

          • 3. Re: HP Gen8 with HPE Customized ESXi 6.7 U2 - Problem with patch ESXi-6.7.0-20190404001
            Sureshkumar M Expert
            vExpert

            I can see the following messages relevant to the be2iscsi

             

            2019-05-08T11:45:59Z esxupdate: 2102969: imageprofile: DEBUG: VIBs {'EMU_bootbank_ima-be2iscsi_12.0.1108.0-1OEM.600.0.0.2494585'} are replaced by VIB VMware_bootbank_elx-esx-libelxima.so_11.4.1184.1-2.48.13006603, removing them from ImageProfile ESXi-6.7.0-20190404001-standard#

            2019-05-08T11:45:59Z esxupdate: 2102969: imageprofile: DEBUG: VIB EMU_bootbank_ima-be2iscsi_12.0.1108.0-1OEM.600.0.0.2494585 is being removed from ImageProfile ESXi-6.7.0-20190404001-standard#

             

            could be due to the manual attempt to install EMU_bootbank_ima-be2iscsi_12.0.1108.0-1OEM.600.0.0.2494585

             

            I browsed the patch for this vib EMU_bootbank_ima-be2iscsi, I think OS is looking for this vib in the patch file which is missing and this might be related to HP servers alone since you are trying to patch server installed using HP image...and patch is from vmware site which is generic. I could not find any other articles on this.

             

            $5BEF109952AC0FF2.jpg

            • 4. Re: HP Gen8 with HPE Customized ESXi 6.7 U2 - Problem with patch ESXi-6.7.0-20190404001
              klemens.urban Lurker

              I think i have resolved the problem.

               

              I removed all vib files with "Remove-EsxSoftwarePackage" in an new Image Profile, except the four packages which were updated according to VMWare, from ESXi670-201904001.zip

               

              • VMware_bootbank_esx-update_6.7.0-2.52.13473784
              • VMware_bootbank_vsanhealth_6.7.0-2.52.13110884
              • VMware_bootbank_esx-base_6.7.0-2.52.13473784
              • VMware_bootbank_vsan_6.7.0-2.52.13110883

               

              Now the Update works.

              • 5. Re: HP Gen8 with HPE Customized ESXi 6.7 U2 - Problem with patch ESXi-6.7.0-20190404001
                dcolpitts Enthusiast

                Personally when I'm migrating from 6.0 to 6.7, I just download the HPE OEM .iso and .zip, upload the .zip to the datastore and run:

                 

                esxcli software vib install -d /vmfs/volumes/datastore/VMware-ESXi-6.7.0-Update2-13006603-HPE-Gen9plus-670.U2.10.4.1.8-Apr2019-depot.zip

                 

                Then I reboot, and once back online, I then do this is patch it to the newest version.

                 

                esxcli software profile update -p ESXi-6.7.0-20190504001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

                 

                And if I am migrating from ESXi 6.0 to 6.7 on a Gen9 or Gen10 server, I take a few extra steps...

                 

                First I back up my patched 6.7 config:

                 

                vim-cmd hostsvc/firmware/sync_config

                vim-cmd hostsvc/firmware/backup_config

                 

                And copy the configBundle tgz backup from /scratch/downloads/{guid} using FileZilla

                 

                Then I mount the ISO (VMware-ESXi-6.7.0-Update2-13006603-HPE-Gen9plus-670.U2.10.4.1.8-Apr2019.iso) to the ILO and boot the host off it, and do a fresh install of ESXi (not an upgrade, but a fresh install, leaving the datastore alone)

                 

                Then I patch the host using "esxcli software profile update" again, and reboot.

                 

                Next I upload the configBundle tgz to /tmp (it **must** be named configBundle.tgz, otherwise the next step fails).

                 

                I Putty the host and run:

                 

                vim-cmd hostsvc/maintenance_mode_enter

                vim-cmd hostsvc/firmware/restore_config /tmp/configBundle.tgz

                 

                The host will immediately reboot without prompting if the restore worked correctly, and when it comes back up, it will have the exact same config as you previously had before the fresh install.

                 

                This basically clears out of all the old vibs and drivers left over from prior to the newest version of 6.7u2.  At this point, you can enable SecureBoot (my experience is if there are any old drivers or vibs there, ESXi won't boot with SecureBoot enabled).

                 

                dcc