...
Document Version Release Date Details 2 November 17, 2021 The Resolution section has been updated with the software version containing the solution. 1 July 22, 2020 Original document release. For HPE Gen10/Gen10 Plus platforms running VMware ESXi 6.x/7.x and iSUT versions 2.4.0 up to 2.8.0, the vSphere Web Client may fail to access the ESXi host server. This issue may occur if iSUT is installed and the iSUT mode is configured with either AutoStage, AutoDeploy or AutoDeployReboot; iSUT will consume approximately 400 KB per day and will not release the allocated memory. In order to check the memory usage, perform the following steps: Connect to the ESXi host using an SSH client Type esxtop Press "M" In order to check the init resource group, perform the memstats command on the vsi_traverse_-s.txt file. The vsi_traverse_-s.txt file is part of the VM-Support log, and detailed steps to collect the log can be found at the following link: Collecting diagnostic information for VMware ESX/ESXi Disclaimer: One or more of the above links redirects outside the HPE website. HPE is not responsible for content outside of its domain. Once the VM-Support log file has been collected, unzip the tgz file and the vsi_traverse_-s.txt file will be found in the following path: < ESXi host name >-< date--time >\commands\vsi_traverse_-s.txt The following is an example of the steps described above: esx-localhost.xx.local-2020-03-13--09.22-1022506\commands\vsi_traverse_-s.txt memstats -c vsi_traverse_-s.txt -r group-stats -s name | grep init 743 init 568 init.66110 memstats -c vsi_traverse_-s.txt -r group-stats -s name:parGid:max:eMinPeak:rMinPeak -g 743 -l 2 -u kb ------------------------------------- Start Group ID : 743 No. of levels : 2 Unit : KB Inclusion filter : (all) Exclusion filter : (none) Selected columns : gid:name:parGid:max:eMinPeak:rMinPeak -------------------------------------------------------------------------- gid name parGid max eMinPeak rMinPeak -------------------------------------------------------------------------- 743 init 14 111616 111616 115584 : 13015 sut.68726 743 -1 106772 107796 -------------------------------------------------------------------------- Note: The above output shows that eMinPeak (106772) is lower than rMinPeak (107796). As a result, iSUT requests more memory than the available resource limit.
In the scenario described above, any HPE ProLiant Gen10/Gen10 Plus servers or HPE Synergy Gen10/Gen10 Plus compute modules with iSUT versions 2.4.0 up to 2.8.0.
This issue has been resolved in iSUT version 2.9.0 (or later). This version can be found at the links show below. Integrated Smart Update Tools 2.9.0 for ESXi 7.0 Integrated Smart Update Tools 2.9.0 for ESXi 6.7 Integrated Smart Update Tools 2.9.0 for ESXi 6.5 Additionally, iSUT version 2.9.0 has been included in the following HPE Custom Images: HPE ProLiant Gen10/Gen10 Plus servers ESXi 6.7 U3 Oct 2021 - Support Gen9 Servers and forward ESXi 7.0 U3 Oct 26 2021 HPE Synergy Gen10/Gen10 Plus compute modules ESXi 6.7 U3 - HPE Synergy Only Nov 2021 ESXi 7.0 U3 - HPE Synergy Only Nov 2021 The above custom images can be found at the following link: VMWARE ESXI IMAGE FOR HPE SERVERS Additional information regarding Synergy compatibility can be found in the HPE Synergy Software Releases page. As a workaround, and to avoid maximum memory consumption by iSUT, perform the following steps: 1. Connect to the ESXi host using an SSH client 2. Set the iSUT mode to OnDemand (updates will require user intervention) # sut -set mode=OnDemand 3. Restart the iSUT to reset the memory usage # sut -stop # sut -start 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: Proactive Updates Subscription Form. 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.