OPERATIONAL DEFECT DATABASE
...
...
Document Version Release Date Details 2 October 14, 2021 Updated Resolution to note that the issue is fixed for HPE Superdome Flex servers in firmware version 3.40.122 1 August 3, 2021 Original document release If an expansion chassis is modified and added to an existing nPar originally configured with CPU Hyper-Threading disabled (Example: "modify npar pnum=0 add_chassis=r00xixxb"), and if that expansion chassis being added had previously been configured on an nPar with HT enabled, the EFI, when booted on the newly modified nPar with the additional chassis added on, will display HT being enabled with all CPU Threads showing as available. In addition, once the OS is booted, it will also show all CPU Threads being available and running. However, "show npar verbose" from the RMC will still show the npar HT set to OFF (HT=off). The expected behavior is that HT will be disabled and no CPU threads should be available. However, if the expansion chassis was added, (which previously had been configured on an nPar with HT DISABLED), then the EFI/OS will come up with HT still disabled with no CPU Threads being available. (as expected). Example: After an expansion second Chassis has been added to the nPar. nPar showing CPU Hyper-Threading is configured and set to OFF: RMC:r001i06c cli> show npar verbose Partitions: 1 Partition 0: Run State : OS Boot Health Status : OK Chassis OK/In : 2/2 CPUs OK/In : 8/8 Cores OK/In : 128/128 DIMMs OK/In : 48/48 IO Cards OK/In : 6/6 Hyper-Threading : Off >>>> RAS : On Boot Chassis : r001i06b Boot Slots : 3,5 Secure Boot : Off Secure Boot Next : Off Memory Refresh Rate : Refreshx1 Memory Refresh Rate Next : Refreshx1 PCH SATA Interface Mode : RAID PCH SATA Interface Mode Next : RAID Volatile Memory : 1535 GiB Persistent Memory : 0 GiB However, when booted to EFI, it showed CPU Threads are enabled and running: In addition, when the OS is booted, it showed CPU Threads are running:
Any HPE Superdome Flex systems.
The issue is fixed for HPE Superdome Flex servers in firmware version 3.40.122, available at this link. On nPars that are configured and supposed to have CPU Hyper-Threading DISABLED, the option "hthread=off" must be included each time a new expansion chassis is added to the nPar. Example: RMC:r001i06c cli> modify npar pnum=x add_chassis=r00xixxb hthread=off This will ensure that HT remains disabled with no CPU Threads being available after EFI/OS is booted. Alternatively, if it is discovered that CPU Threads are running after adding an expansion chassis to an nPar that is configured with HT=OFF, run "modify npar pnum=x hthread=off" followed by a reboot to correct and to ensure CPU Hyper-Threading stays disabled. Example: RMC:r001i06c cli> modify npar pnum=x hthread=off 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.
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
