1 5 6 7 8 9 Previous Next 157 Replies Latest reply on Apr 18, 2008 3:56 PM by Badsah Go to original post
      • 90. Re: VI 3.5 Update 1 upgrade experiences
        FrancWest Novice

         

        Hi,

         

         

        same here. Just downloaded it 5 minutes ago and has the wrong (6201BD703A932750CA2B4B9FE68996D8) checksum. It was downloaded from download2.

         

         

        Franc.

         

         

        • 91. Re: VI 3.5 Update 1 upgrade experiences
          kellino Hot Shot

           

          I'm wondering if either proxies or content delivery systems such as Akamai (not sure what VMWare uses) could be reponsible?

           

           

          In other words maybe VMWare did correct the download, but some points in the distribution chain (including proxy servers) are still serving the original version.

           

           

          Just pure specualtion on my part...

           

           

          • 92. Re: VI 3.5 Update 1 upgrade experiences
            NathalieMarshall Enthusiast

            I updated via updte manager just one ESX server and now I can't migrate

            any VM's to that ESX. I'm not prepared to upgrade the others until I can

            understand why I have this problem. I plan to rebuild the ESX server

            tomorrow.

             

             

            Nathalie Marshall - I.S. Infrastructure Support  x8427

             

             

             

             

            RParker <communities-emailer@vmware.com>

            14/04/2008 15:15

             

            To

            Nathalie <nathalie.marshall@honda-eu.com>

            cc

             

            Subject

            http://VI3 v3.5 New Features New message: "VI 3.5 Update 1 upgrade experiences"

             

             

             

             

             

             

            Nathalie,

             

            A new message was posted in the thread "VI 3.5 Update 1 upgrade

            experiences":

             

            http://communities.vmware.com/message/914254

             

            Author  : RParker

            Profile : http://communities.vmware.com/people/RParker

            Message:

            • 93. Re: VI 3.5 Update 1 upgrade experiences
              sbeaver Guru
              vExpertUser Moderators

              Edit your baseline or create a new one with just the updates that you want

              • 94. MD5 matches but experiencing symptoms.....
                kellino Hot Shot

                 

                Very confused.....

                 

                 

                We applied the VC update as a ZIP file.  I can confirm that we are suddenly experiencing all the symptoms (no vMotion, VC crashes, etc.).  When I do an MD5 on the zip I get:

                 

                 

                9146AA4743C0A56E37921F62FB898A64

                 

                 

                ...which is the same MD5 listed on the download page.

                 

                 

                If the problem has been corrected why would one be experiencing the symptoms when the MD5 matches?

                 

                 

                • 95. Re: VI 3.5 Update 1 upgrade experiences
                  jpoling Expert

                   

                  Jason,

                   

                   

                  I was dumb - After my initial download and install, I dowloaded the ZIP a second time because of the issues raised in this post.  Well, I overwrote my initial dowloaded zip file. .  .

                   

                   

                  THe download I ahve now, I ahve not extracted and installed, but the MD5SUM is:

                   

                   

                  6201bd703a932750ca2b4b9fe68996d8 VMware-VIMSetup-2.5.0-84782.zip

                   

                   

                  Jeff

                   

                   

                  • 96. Re: VI 3.5 Update 1 upgrade experiences
                    doubleH Expert

                    I upgraded from 2.0.2 u1 to 2.5.0 u1 last night (using the zip file with the wrong md5sum) and everything is working perfectly. no problems with vmotion (hosts are still at 3.0.2), able to deploy vm's from customized templates, vi client is not crashing, no issues with remote console connections, i did not install any plugins because i haven't had a chance to experiement with the added functionality yet.

                     

                     

                     

                     

                    If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

                    • 97. Re: MD5 matches but experiencing symptoms.....
                      jasonboche Champion
                      vExpert
                      kellino wrote:

                       

                      Very confused.....

                       

                       

                      We applied the VC update as a ZIP file.  I can confirm that we are suddenly experiencing all the symptoms (no vMotion, VC crashes, etc.).  When I do an MD5 on the zip I get:

                       

                       

                      9146AA4743C0A56E37921F62FB898A64

                       

                       

                      ...which is the same MD5 listed on the download page.

                       

                      That is also the same MD5SUM that the VMware employee was getting last night which is different than what Mittell and myself are getting.

                       

                       

                      If the problem has been corrected why would one be experiencing the symptoms when the MD5 matches?

                       

                      We will need to get clarification from VMware on how to proceed.  Still waiting the news on what is actually happening.  Hopefully today.

                       






                      [i]Jason Boche[/i]

                      [VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

                      • 98. MD5 Mayhem
                        kellino Hot Shot

                         

                        My confusion is growing...

                         

                         

                        I downloaded the VC update on Friday and again just minutes ago (around 12:30 EDT Monday).

                         

                         

                        After applying the update that was downloaded on Friday we suddently have all the symptoms (no vMotion, VI client crashes, etc.) and the VI client reports the build as being 84767.

                         

                         

                        Here is the results of running MD5 against BOTH downloads:

                         

                        H:\md5&gt;md5 h:\vmware\VMware-VIMSetup-2.5.0-84782.zip
                        9146AA4743C0A56E37921F62FB898A64 h:\vmware\VMware-VIMSetup-2.5.0-84782.zip

                        H:\md5&gt;md5 h:\vmware\VMware-VIMSetup-2.5.0-84782_new.zip
                        9146AA4743C0A56E37921F62FB898A64 h:\vmware\VMware-VIMSetup-2.5.0-84782_new.zip

                         

                        In other words the following are true:

                         

                        • the MD5 for either download matches the MD5 posted on the download page.

                        • immedaitely after applying the update we experience the symptoms

                         

                        Am I missing something? If not, how do we get obtain the "correct" zip to restore lost functionality?

                         

                         

                        Thanks!

                         

                         

                         

                         

                         

                        • 99. Re: MD5 Mayhem
                          dconvery Virtuoso
                          vExpert

                           

                          I just downloaded the zip. I used md5sums.exe to run and got the posted md5:

                           

                           

                          MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+

                          Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/

                          Type c:\software\utils\md5sums.exe -h for help

                           

                          / filename                              MD5 sum

                          -


                          VMware-VIMSetup-2.5.0-84782.zip           100% 9146aa4743c0a56e37921f62fb898a64

                           

                           

                           

                           

                           

                          The download link was  http://download2.vmware.com/software/vi/VMware-VIMSetup-2.5.0-84782.zip?HashKey=....

                           

                           

                           

                           

                           

                           

                           

                           

                          • 100. Re: VI 3.5 Update 1 upgrade experiences
                            v01d Enthusiast

                             

                            I upgraded friday morning and have had zero problems.

                             

                             

                             

                             

                             

                            1. VC 2.5 to 2.5u1 via ISO

                             

                             

                            2. Per the release notes I unistalled the VI plugins via the control panel.

                             

                             

                            3. I also uninstalled the VI client as well although I could have used VI update at this point

                             

                             

                            4. I reinstalled VI client and installed the updated plugins

                             

                             

                            5. I updated each of the ESX hosts via update manage

                             

                             

                             

                             

                             

                            I haven't experienced ANY issues with the updates.

                             

                             

                             

                             

                             

                            VC = 84767

                             

                             

                            VI = 84767

                             

                             

                            ESX = 82663

                             

                             

                            Update Manager Plugin = 1.0.0.63965

                             

                             

                            Enterprise Converter Plugin = 4.0.0.62387

                             

                             

                             

                             

                             

                            Fully automated DRS cluster, no vmotion issues.

                             

                             

                            • 101. Re: MD5 Mayhem
                              BryanMcC Expert

                              Wow.. They must have just changed it.. I downloaded 2 hours agao with the 6***** md5sum then just downloaded again and got the right one (9***).

                               

                               

                               

                               

                              Help me help you by scoring points.

                              • 102. Re: MD5 Mayhem
                                jasonboche Champion
                                vExpert
                                BryanMcC wrote:

                                Wow.. They must have just changed it.. I downloaded 2 hours agao with the 6***** md5sum then just downloaded again and got the right one (9***).

                                 

                                 

                                 

                                 

                                 

                                I don't think we don't know what the right one is until VMware draws a conclusion on our experiences and their findings and tells us.

                                 






                                [i]Jason Boche[/i]

                                [VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

                                • 103. Re: MD5 Mayhem
                                  jamieorth Expert

                                  Ok, so what to do?  Just wait?  My company has 2 hosts at 3.0.1, 42829 and 3 hosts at 3.0.2, 52542 and our VC is 2.0.2, 50618.  We have a SQL 2005 backend.

                                  • 104. Re: MD5 Mayhem
                                    kellino Hot Shot

                                     

                                    I have a new theory that I had the correct bits from the start......

                                     

                                     

                                    I have experienced the following symptoms:

                                     

                                    • VC client closes without warning, after opening a console window

                                    • VC client complains that a VPX log file is in use (this is a popup message and it appears to let us keep working when it happens).

                                    • VC client seems slower upon initialization.

                                    • I reconfigured HA on our hosts and vMotion is now working.

                                     

                                    The biggest show stopper was vMotion, but reconfiguring HA fixed that.  We still have some client anomolies that are "inconvenient" but they don't prevent us from working.

                                     

                                     

                                    Maybe the reason the MD5 matched was because we did have the correct build after all?

                                     

                                     

                                     

                                     

                                     

                                     

                                     

                                     

                                    1 5 6 7 8 9 Previous Next