{"id":137,"date":"2015-04-15T07:45:19","date_gmt":"2015-04-15T15:45:19","guid":{"rendered":"http:\/\/vspherestorage.com\/?p=137"},"modified":"2015-04-15T07:45:19","modified_gmt":"2015-04-15T15:45:19","slug":"esxi-5-5-ep07-posted-a-must-have-before-upgrading-to-vsan6-in-certain-configurations","status":"publish","type":"post","link":"https:\/\/vspherestorage.com\/?p=137","title":{"rendered":"ESXi 5.5 EP07 posted. A must have before upgrading to VSAN6 in certain configurations"},"content":{"rendered":"

A critical issue was reported with upgrading VSAN from ESXi 5.5 with Patch 4 or Express Patch 6 to vSphere\u00a06 GA.<\/p>\n

The problem was introduced in the above patches which attempted to fix an incorrect SSD capacity reporting when using RVC command vsan.disks_stats<\/span>.<\/p>\n

EP07 backs out the above fix.<\/p>\n

Here is the possible sequence of events:<\/p>\n

    \n
  1. Upgrade vCenter to 6.0<\/li>\n
  2. Enter maintenance mode on one VSAN cluster node (Ensure availability option)<\/li>\n
  3. Upgrade to ESXi 6.0 GA<\/li>\n
  4. Exit maintenance mode<\/li>\n
  5. vMotion some VMs to the upgraded node<\/li>\n<\/ol>\n

    The ESXi 6 node is unable to read the SSD UUID correctly on the remaining VSAN 5.5 nodes. This results in failure to access the VSAN objects on the 5.5\u00a0nodes and eventually, VMs become inaccessible and my disappear from vCenter inventory.<\/p>\n

    A look through the vmkernel.log file would show events like this:<\/p>\n

    2015-03-23T15:59:08.093Z cpu10:33023)WARNING: exprmsh: Error unmarshaling structure: Bad parameter<\/span><\/div>\n
    2015-03-23T15:59:08.093Z cpu10:33023)WARNING: Parse error at token 17. Message: Unexpected value type.<\/span><\/div>\n
    Expression up to error: …l0 i10 i15 l1600000 l0 l16777216 i0 52289c49-30c9-1ec7-16a9-57fc7ba21d7f “5422e4c9-32259101-000f-ac162d9dec28” l0<\/span><\/div>\n

     <\/p>\n

    This problem is more evident with 3 nodes clusters. If there are more nodes, the chances of hitting this issue are less depending on FTT policy and on which nodes the replicas are stored.
    \nExamples:<\/p>\n

    Cluster nodes count: 3
    \nFTT=1<\/p>\n

    Components placements:
    \n5.5 node 1: Replica
    \n5.5 node 2: Replica
    \n6.0 node: Witness<\/p>\n

    or<\/p>\n

    5.5 node 1: Replica
    \n5.5 node 2: Witness
    \n6.0 node: Replica<\/p>\n

    In either case, more than 50% of the components are on 5.5 nodes. As long as the associated VMs run on 5.5 nodes, they would be accessible. However, availability is not guaranteed if one of the remaining 5.5 nodes experiences a hardware component failure.<\/p>\n

    If you have 4+ nodes cluster, all 3 components (2 replica and a witness) may be on the 5.5 nodes. As long as the majority of the components are on the 5.5 nodes, the object should still be accessible.<\/p>\n

    The best approach to upgrading, with least disruption to the running VMs, is:<\/p>\n

      \n
    1. Upgrade vCenter to 6.0<\/li>\n
    2. Place one node in maintenance mode (Ensure accessibility option)<\/li>\n
    3. Install EP07<\/li>\n
    4. Reboot and exit maintenance mode<\/li>\n
    5. Wait for resync to complete<\/li>\n
    6. Repeat steps 2 through 5 for each node\u00a0in the cluster.<\/li>\n
    7. Place one node in maintenance mode (Ensure accessibility)<\/li>\n
    8. Upgrade to ESXi 6.0 GA<\/li>\n
    9. Exit maintenance mode.<\/li>\n
    10. Wait for resync to complete<\/li>\n
    11. Repeat steps 7 through 10 for each node in the cluster.<\/li>\n<\/ol>\n

      What if I already upgraded one host prior to installing EP07?<\/p>\n

      You have 2 choices:<\/p>\n

        \n
      1. Shutdown all VMs on the cluster and upgrade the remaining nodes to 6.0. Make sure to choose “No data Migration” option when entering maintenance mode on the 5.5\u00a0nodes.<\/li>\n
      2. Roll-back the 6.0 node to the previous version of 5.5<\/li>\n<\/ol>\n

        The first approach needs the least administrative effort but will disrupt all running VMs<\/p>\n

        The second approach is the least disruptive but will involve a rollback, installing EP07 then upgrading to 6.0<\/p>\n

        To rollback an upgrade, as long as you have not made any other configuration changes, you may follow VMware KB\u00a01033604<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

        A critical issue was reported with upgrading VSAN from ESXi 5.5 with Patch 4 or Express Patch 6 to vSphere\u00a06 GA. The problem was introduced in the above patches which attempted to fix an incorrect SSD capacity reporting when using RVC command vsan.disks_stats. EP07 backs out the above fix. Here is the possible sequence of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[11],"tags":[],"class_list":["post-137","post","type-post","status-publish","format-standard","hentry","category-vsan"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p4m26N-2d","jetpack-related-posts":[{"id":10608,"url":"https:\/\/vspherestorage.com\/?p=10608","url_meta":{"origin":137,"position":0},"title":"vSphere 6.0 Update 2 \u2013 What\u2019s New","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"#vSphere 6.0 Update 2 \u2013 What\u2019s NewvSphere 6.0 Update 2 \u2013 What\u2019s NewVMware just recently released Update 2 for vSphere 6.0. Update 2 is full of new features and bug fixes for both ESXi and vCenter Server. For a complete list of features and bug fixes make sure to review\u2026","rel":"","context":"In "VMware Advocacy"","block_context":{"text":"VMware Advocacy","link":"https:\/\/vspherestorage.com\/?cat=12"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4423,"url":"https:\/\/vspherestorage.com\/?p=4423","url_meta":{"origin":137,"position":1},"title":"Definici\u00f3n de VMware Virtual SAN (vSAN) ‘ Blog…","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"Definici\u00f3n de #VMware Virtual SAN (vSAN) ' Blog VMware por Leandro Ariel LeonhardtDefinici\u00f3n de VMware Virtual SAN (vSAN) ' Blog...almacenamiento, esxi, sds, vCenter, vmware, vsan - 7\/20\/2015 09:30:00 a. m. VMware vSAN en un almacenamiento definido por software que agrupa los discos duros (HDD) o de estado s\u00f3lido (SSD) formando\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":5399,"url":"https:\/\/vspherestorage.com\/?p=5399","url_meta":{"origin":137,"position":2},"title":"Dise\u00f1a vSAN con Virtual SAN TCO and Sizing…","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"Dise\u00f1a #vSAN con Virtual SAN TCO and Sizing CalculatorDise\u00f1a vSAN con Virtual SAN TCO and Sizing...almacenamiento, esxi, leo-ariel, sds, vCenter, virtualizaci\u00f3n, vsan - 7\/28\/2015 09:30:00 a. m. Esta semana tengo el placer de ofrecerte otro v\u00eddeo tutorial sobre almacenamiento definido por software y en el que te ense\u00f1ar\u00e9 a dise\u00f1ar\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4949,"url":"https:\/\/vspherestorage.com\/?p=4949","url_meta":{"origin":137,"position":3},"title":"VMware VSAN reusing SSD disks","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"#VMware VSAN reusing SSD disksVMware VSAN reusing SSD disksEalier this week I\u2019ve been configuring a new VSAN cluster. The old configuration was using hardware that wasn\u2019t complying with the VMware vSAN HCL. We ordered new raid controllers and HDD\u2019s and reused the SSD disks, as those where compliant with the\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":11522,"url":"https:\/\/vspherestorage.com\/?p=11522","url_meta":{"origin":137,"position":4},"title":"Oracle on VMware vSAN \u2013 Dispelling the…","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"Oracle on VMware vSAN \u2013 Dispelling the Licensing mythsOracle on VMware vSAN \u2013 Dispelling the...Introduction to VMware vSphere & vSAN Some key things to keep in mind when we talk about VMware vSphere Platform , ESXi hypervisor and vSAN: VMware vSphere is a platform of virtualized hardware that creates a\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":10234,"url":"https:\/\/vspherestorage.com\/?p=10234","url_meta":{"origin":137,"position":5},"title":"Step by Step Upgrade of VCSA 5.5 to VCSA 6.0","author":"Mostafa Khalil","date":"11 years ago","format":false,"excerpt":"Step by Step Upgrade of VCSA 5.5 to VCSA 6.0Step by Step Upgrade of VCSA 5.5 to VCSA 6.01. Mount the ISO and click on vcsa-setup.html . The upgrade and install button will only be displayed if you have installed client integration plugin. Once it is displayed on the web\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/posts\/137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=137"}],"version-history":[{"count":2,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/posts\/137\/revisions"}],"predecessor-version":[{"id":139,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=\/wp\/v2\/posts\/137\/revisions\/139"}],"wp:attachment":[{"href":"https:\/\/vspherestorage.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vspherestorage.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}