10 Replies Latest reply on Jul 11, 2014 9:54 AM by ixobelle

    Recent 5.1 upgrade knocked out vSphere client from accessing host

    BenConner Novice

      Hi,

       

      I have 2 hosts managed by vCenter under 5.1.  I hadn't applied patches in a few months and decided to update them through the Update Manager.

       

      After applying the patches to 1 host, I found I couldn't connect to it directly from the vSphere client.  Thought it was a fluke, so I applied patches to the 2nd host this morning and the same thing happened.  Good thing vCenter still works.   These are production boxes.

       

      The patches/updates I applied were:

       

      ESXi510-201401103-SG

      ESXi510-201401201-UG

      ESXi510-201401203-UG

      ESXi510-201401204-UG

      ESXi510-201401205-UG

      ESXi510-201401206-UG

      ESXi510-201401207-UG

      ESXi510-201401208-UG

      ESXi510-201401101-SG

      ESXi510-201401102-SG

      ESXi510-201401202-SG

      ESXi510-Update02

       

      Anyone have any suggestions on how to correct this issue or find out which patch tanked the connectivity?

      The error I'm getting back (which is immediate) is:

       

      vSphere Client could not connect to "10.0.0.5".

      An unknown connection error occurred. (The client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.))

       

      I've researched this in the KB and the usual steps they suggest didn't apply--I can ping the hosts, even access both via vCenter and log in with root.

       

      Is it even possible to back out patch(es)?

       

      --Ben