1 2 3 4 Previous Next 45 Replies Latest reply on Oct 17, 2011 4:04 PM by Terry@MNP Go to original post
      • 15. Re: ESXi lost configuration on reboot
        wolfwolf Enthusiast

        Yes, the MD5 sum is correct.

        And we can reproduce the issue installing Dell ESXi on our M610 servers and also in a VM on VMware Fusion.

        • 16. Re: ESXi lost configuration on reboot
          DSTAVERT Guru

          I can also confirm that same behavior using your Dell download link. Shift + R does boot the correct bootbank and a subsequent reboot does come up in a configured state.

           

          Does this server have the dual SD card slots?

          • 17. Re: ESXi lost configuration on reboot
            Dave.Mishchenko Guru

            oem.tgz on Hypervisor1 contains a tweak for MD36xxi support in the form of a VIB which means that /altbootbank being set as the active boot partition for the next reboot is correct.  They should have included a reboot command in  the customization. Since the host doesn't reboot  your changes get written to /bootbank either when you reboot or when the auto backup process runs (1 min past the hour).

            • 18. Re: ESXi lost configuration on reboot
              krishnaprasad Hot Shot

              That's exactly the case Dave.

               

              In this case, 'updated' variable in /bootbank becomes 1 and same in /altbootbank becomes '2'. hence in the next bootup the bootup will uncompress files from /altbootbank which dont carry the changes like password change, IP changes etc.

               

              As you mentioned, Dell carries an init script for configuring their MD36xxi array and during clean up of the VIB ( which contains the script ) via esxupdate, this scenario happens. 

               

              I also see an esxupdate command, 'esxupdate clearpending' executed in a VMware script 130.-x.x... Does this removes the locks or sync the VIB database in SYNC?

               

              So other than rebooting the server to make the changes effective ( removal of the VIB ), is there any other way to remove the VIB from the init script but still the updated variable can be kept as '1' for altbootbank and '2' for bootbank? 

               

              BTW, wolfwolf , you can Call Dell tech support so that they can change the ISO images.

              • 19. Re: ESXi lost configuration on reboot
                wolfwolf Enthusiast

                Dave Mishchenko wrote:

                 

                oem.tgz on Hypervisor1 contains a tweak for MD36xxi support in the form of a VIB which means that /altbootbank being set as the active boot partition for the next reboot is correct.  They should have included a reboot command in  the customization. Since the host doesn't reboot  your changes get written to /bootbank either when you reboot or when the auto backup process runs (1 min past the hour).

                Thanks for the explanation.

                 

                At this point, is it safe to go with the Dell ISO (doing a manual first reboot, after the initial boot, before applying any configuration) or is it better to go with the stock VMware ISO to avoid any risks of losing the configuration at future ESXi reboots/updates?

                 

                Besides the Intel 10G NIC driver missing from the VMware ISO, what are the advantages of the Dell ISO?

                 

                It looks like you can download the Intel 10G NIC driver from VMware site and apply it to the stock ESXi installation from VMware.

                If you do so, will the driver be carried over when applying future ESXi updates to the host?

                 

                About the Dell ISO bug, what would be the best way to report it to Dell? Any specific email address?

                 

                Thanks.

                • 20. Re: ESXi lost configuration on reboot
                  krishnaprasad Hot Shot

                  I think it's okay to still use the Dell ISO image with an additional reboot after first bootup. The configuration loss will happen only on for the first boot.

                   

                  To know what is extra in Dell Customized images, i think you can refer Dell support website. They have documented what's additional available in Dell Customized image. This is how i could see the information. Might be helpful to you.

                   

                  http://support.dell.com/support/index.aspx?c=us&l=en&s=biz  --> Select  “Drivers & Downloads” section --> Choose the System model that you have by going to “Select Model” tab  --> Select “Servers, Storage, networking” tab from ‘Select your product family’ section --> Click on ‘PowerEdge Server’ --> Select your product Model ( Eg/- R910 ) --> Confirm

                   

                  See the attached screenshots where i could see the info.

                   

                  For fixing the issue in Dell ISO, You can call Dell Tech support . you may hve got tech support numbers / mail id when you purchased servers from them?

                  • 21. Re: ESXi lost configuration on reboot
                    Dave.Mishchenko Guru

                    I'd go with the dell iso as well.   The issue you've had with the ISO will be a one time thing.

                    • 22. Re: ESXi lost configuration on reboot
                      krishnaprasad Hot Shot

                      forgot to mention that "Additional Information" section carries the information on what's extra in Dell Customized images. Refer the screenshot ( attached ) as well for 4.1 Update1

                      • 23. Re: ESXi lost configuration on reboot
                        wolfwolf Enthusiast

                        It looks like the only driver from the Dell ISO missing from the VMware ISO is the Intel 10G NIC ixgbe driver and you can download version 3.x of in from the VMware site, while the Dell ISO contains older version 2.x. Not sure what are the practical advantages of the newer version from VMware site, if any.

                         

                        Is it still better to go with the Dell ISO?

                         

                        In case, we decide to go with the VMware ISO and add the ixgbe driver to it using the vihostupdate utility, will the driver remain in place when we apply future ESXi updates to the hosts?

                         

                        Thanks.

                        • 24. Re: ESXi lost configuration on reboot
                          krishnaprasad Hot Shot

                          I dont think it's just one driver update in the Dell image. if you see the screenshots that i had attached, the 'additional information' section talks about different driver updates/inclusions. For example  bnx2 driver version available in Dell Customized image is later version compared to VMware ISO.  and 'qlge' driver included in the image is not part of VMware image by default. Need to really see what happens on an upgrade.

                          • 25. Re: ESXi lost configuration on reboot
                            wolfwolf Enthusiast

                            Yes, the Dell ISO contains other customizations, but since we're only going to use the 10G Intel NIC with ESXi, the other drivers shouldn't matter.

                            And for the 10G Intel NIC the driver available as a separate download on the VMware site (version 3.x) is actually newer than the one available from the Dell ISO (version 2.x).

                            But I'm still not sure installing that driver manually on a stock VMware installation is a good choice, e.g. if future ESXi updates will retain it.

                            And I'm not sure how to test that either, since there are no updates available for ESXi 4.1 Update 1 yet.

                            Anyone tested this in the past?

                             

                            Thanks.

                            • 26. Re: ESXi lost configuration on reboot
                              DSTAVERT Guru

                              I would go with the Dell ISO. A later driver version may not be the most appropriate version or the tested and supported version from Dell's persective. Before considering using the VMware downloaded driver I would check with Dell support. I would also suspect that the Dell version of the ISO would include Dell specific CIM providers.

                              • 27. Re: ESXi lost configuration on reboot
                                krishnaprasad Hot Shot

                                The OM providers are not included in Dell Customized image. it can be separately downloadable and installed on the ESX/ESXi images.  You can see this information from the 'additional information' section screenshot that i had poster earlier ( From Dell Support website ) .

                                 

                                I think you can even use the drivers posted @ VMware website since it might be tested by VMware or the driver vendor before posting it in VMware website. I second Dave and DSTAVERT for continued usage of Dell ISO since the issue will be present only on the first bootup.

                                • 28. Re: ESXi lost configuration on reboot
                                  krishnaprasad Hot Shot

                                  This issue can be even reproducible with VMware ISO.

                                   

                                  1. Let's say We have VMware ESXi 4.1 Update1 ISO installed on a system.

                                  2. Boot into the USB key/LUN where the image is installed.

                                  3. Make some changes to the configuration ( Eg/- Change the password of ESXi host )

                                  4. Install an offline bundle/VIB  ( eg/- any Driver package available @ VMware.com ) using vihostupdate/esxupdate command sets.

                                  5. Make the configuration changes again in the system ( eg/- Create a vSwitch, Register a Virtual Machine to the host etc )

                                  6. Reboot the server

                                  7. Boot into ESXi.

                                   

                                  You can see that the changes made like vSwitch creation, Registering VM to the host are lost where as password change is persistent.

                                   

                                  i.e. whatever changes made AFTER execution of esxupdate command is found be to lost.

                                  • 29. Re: ESXi lost configuration on reboot
                                    krishnaprasad Hot Shot

                                    The reason of the failure is because when a package is installed/uninstalled on ESXi, the changes are made to the alternate bootbank ( where updated=2 in boot.cfg so that this becomes /bootbank in next bootup ). The changes made between the updates (package install/Uinstall) and reboot are written into /bootbank only. So it is not available during next bootup.