Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 3 September 14, 2022 Added an additional note to the Resolution, if an ESXi upgrade is performed, the smx-provider vib may be reinstalled and should be removed again. 2 June 29, 2022 Updated the Resolution, added the commands to disable the smx-provider before the removal. 1 June 16, 2022 Original Document Release. On any HPE SimpliVity Gen10 / Gen10 Plus node running VMware ESXi 6.5, VMware ESXi 6.7 or VMware ESXi 7.0, the sfcb-smx process fails and creates zdump files in /var/core/. When this occurs, the HPE SMX WBEM Provider causes the VMware ESXi host to become unresponsive. This issue is caused by the HPE SMX WBEM Providers running out of available memory due to a memory leak. When this occurs, the following message is logged repeatedly in the vmkernel.log file: 2022-05-25T13:42:12.294Z cpu44:2101197)MemSchedAdmit: 471: Admission failure in path: smx/sfcb-ProviderMa.2101193/uw.2101193 In certain scenarios this issue may cause a neighboring node to experience an APD event resulting in potential data unavailability.
Any HPE of the following SimpliVity Gen10 / Gen10 Plus nodes running VMware ESXi 6.5, VMware ESXi 6.7 or VMware ESXi 7.0: HPE SimpliVity 2600 HPE SimpliVity 325 HPE SimpliVity 380 Important Note: The smx-provider is required for HPE SimpliVity Gen9 nodes.
To resolve this issue, disable the "smx-provider" and then remove it from the installed VMware ESXi Operating System. To disable the "smx-provider" run the following commands: List the providers: esxcli system wbem provider list Disable the provider: esxcli system wbem provider set -e 0 -n vmw_smx-provider Restart WBEM: esxcli system wbem set -e 0; esxcli system wbem set -e 1 List the providers to confirm: esxcli system wbem provider list To remove the "smx-provider" run the following command: esxcli software vib remove -n smx-provider Notes: Disabling the smx-provider first is important, as not doing so prior to removal and reboot can result in APDs. The smx-provider VIB should be removed proactively on SimpliVity Gen10/Gen10 Plus products even if issue are not experienced. A reboot of the system is required after removing the smx-provider. If an issue with smx-providers is experienced on other HPE Gen10 platforms (or later generations), refer to the following Customer Advisory: (Revision) HPE Smart Array SR Gen10 Controllers - Additional Disks Are Displayed In ESXi /vCenter GUI and smx-provider Errors Are Logged On Platforms Configured With Controllers With FW v3.53 (Or Later) If an issue with smx-providers is experienced on HPE Gen9 platforms, refer to the following Customer Advisory: (Revision) VMware - HPE SMX WBEM Providers Causes The VMware ESXi Operating System Running on HPE Gen9 Platforms to Become Unresponsive If an ESXi upgrade is performed, the smx-provider vib may be reinstalled and should be removed again. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Support Alerts. Sign up for Support Alerts at the following URL: HPE Email Preference Center NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches and other support software downloads, refer to the Navigation Tips document. SEARCH TIP: For hints on locating similar documents on HPE.com, refer to the Search Tips document.