VMware ESXi 6.7, Patch Release ESXi670-201807401-BG - Updates esx-base, vsan and vsanhealth VIBs
search cancel

VMware ESXi 6.7, Patch Release ESXi670-201807401-BG - Updates esx-base, vsan and vsanhealth VIBs

book

Article ID: 326747

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Release date: July 26, 2018

Patch CategoryBugfix
Patch SeverityImportant
Host Reboot RequiredYes
Virtual Machine Migration or Shutdown RequiredYes
Affected HardwareN/A
Affected SoftwareN/A
VIBs Included
  • VMware_bootbank_vsanhealth_6.7.0-0.17.9214924
  • VMware_bootbank_esx-base_6.7.0-0.17.9214924
  • VMware_bootbank_vsan_6.7.0-0.17.9214924
PRs Fixed 2140805, 2141362, 2140804, 2141219
Related CVE numbersN/A


Environment

VMware vSphere ESXi 6.7

Resolution

Summaries and Symptoms

This patch updates the esx-base, vsan and vsanhealth VIBs to resolve the following issue:

  • During an ESXi boot, if the commands issued over the initial device discovery fail with ASYMMETRIC ACCESS STATE CHANGE UA, the path failover might take longer because the commands are blocked within ESXi. This might lead to longer ESXi booting.

    You might see logs similar to:

    2018-05-14T01:26:28.464Z cpu1:2097770)NMP: nmp_ThrottleLogForDevice:3689: Cmd 0x1a (0x459a40bfbec0, 0) to dev "eui.0011223344550003" on path "vmhba64:C0:T0:L3" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x6 0x2a 0x6. Act:FAILOVER 2018-05-14T01:27:08.453Z cpu5:2097412)ScsiDeviceIO: 3029: Cmd(0x459a40bfbec0) 0x1a, CmdSN 0x29 from world 0 to dev "eui.0011223344550003" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. 2018-05-14T01:27:48.911Z cpu4:2097181)ScsiDeviceIO: 3029: Cmd(0x459a40bfd540) 0x25, CmdSN 0x2c from world 0 to dev "eui.0011223344550003" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. 2018-05-14T01:28:28.457Z cpu1:2097178)ScsiDeviceIO: 3029: Cmd(0x459a40bfbec0) 0x9e, CmdSN 0x2d from world 0 to dev "eui.0011223344550003" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. 2018-05-14T01:28:28.910Z cpu2:2097368)WARNING: ScsiDevice: 7641: GetDeviceAttributes during periodic probe'eui.0011223344550003': failed with I/O error.

  • You might see the Presence sensors in the Hardware Status tab of the vSphere Web Client displaying a status Unknown. This fix filters out only the Presence sensors that are not in a valid health state.

  • An ESXi host might fail with a purple diagnostic screen due to a race condition in a query by the Multicast Listener Discovery (MLD) version 1 in IPv6 environments. You might see an error message similar to:

    #PF Exception 14 in world 2098376:vmk0-rx-0 IP 0x41802e62abc1 addr 0x40
    ...
    0x451a1b81b9d0:[0x41802e62abc1]mld_set_version@(tcpip4)#+0x161 stack: 0x430e0593c9e8
    0x451a1b81ba20:[0x41802e62bb57]mld_input@(tcpip4)#+0x7fc stack: 0x30
    0x451a1b81bb20:[0x41802e60d7f8]icmp6_input@(tcpip4)#+0xbe1 stack: 0x30
    0x451a1b81bcf0:[0x41802e621d3b]ip6_input@(tcpip4)#+0x770 stack: 0x451a00000000
    ...

  • APIs for Storage Awareness (VASA) providers might not be available due to missing namespaces such as SERIALNUM and NAA in the ScsiLunDurableName property.

Patch Download and Installation

The typical way to apply patches to ESXi hosts is through the VMware vSphere Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.

ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples  and the VMware ESXi Upgrade Guide.