Loading...
Loading...
Document VersionRelease DateDetails201/04/2018Updated Resolution with permanent fix, OA firmware 4.70108/03/2017Original document releaseIn rare instances, a small number of Onboard Administrator (OA) Trays may contain a component that results in the ?Power-Off Protection? function not operating properly on the OA Tray. This issue only occurs when ALL OA Modules are removed from an affected tray, so that the tray is empty.When this occurs, all server blades installed in the enclosure will detect a power event because ?Power-Off Protection? does not function properly, causing the servers be throttled to less than 50% performance to reduce power consumption. Re-installing the OA Modules will not recover from the condition.This issue could occur on an HP c-Class BladeSystem Onboard Administrator Tray found in the serial number range list provided in the Resolution section below.If this occurs, the server blades will display the following entry in the Integrated Management Log (IML):Bay#1 05/02/2016 17:19:00,14: Maintenance note:CPU(s) operating at reduced performance level due to an enclosure power event.If the blade has been restarted, the following message will be displayed at POST:320-IMPORTANT:Enclosure Power Event detectedBoot Delayed until condition is resolved.All server blades in the enclosure will be in a degraded performance state; however, the OA will falsely report a healthy enclosure status.
Any HPE c-Class BladeSystem in the configuration detailed above.
OA firmware version 4.70 corrects this issue, and will auto-recover this condition. This firmware enhanced OA to bring the server from a power throttled state back to a normal power state upon an OA reboot to circumvent an unwarranted emergency brake.https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_32d2b2aadb81438d8901465facOA Firmware release notes:https://support.hpe.com/hpsc/doc/public/display?sp4ts.oid=1844065&docLocale=en_US&docId=emr_na-a00019233en_usAs a workaround, if reduced performance occurs because both OA Modules were removed from the OA tray, restore the server blade performance by performing ONE of the following.The first option can be accomplished without resetting any of the server blades. However, Options 2 or 3 will reset the server blades and should only be done after an orderly shutdown of every affected server.OPTION 1:Use the IPMI command to remove each server degraded state.LINUX IPMI release METHOD:Configure a local Linux PC for remote communications with the iLO in each affected server blade:For the affected server blades running in degraded mode, determine each servers iLO IP, User name, and Password.Open a terminal window and at the prompt, enter the following command substituting in an iLO IP and user name:ipmitool -H <iLO ip address> -U <iLO user name> -I lanplus raw 0x30 0x01 0x0fWhen prompted, enter the iLO password from the affected unit.Re-run the command with the iLO credential of the next degraded server.Repeat for each affected server blade.WINDOWS IPMI release METHOD:Configure a local Windows PC for remote communication with the degraded servers iLO as follows:Create a directory off the root named ipmirel(can be any name).Download the tool from:http://ipmiutil.sourceforge.net/FILES/ipmiutil-301.exeand move it to the ipmirel directory.Download one of the below driver packages in Step 5 or Step 6, based on the Windows version used.For Win64:http://ipmiutil.sourceforge.net/FILES/ipmiutil-3.0.0-win64.zipFor Win32:http://ipmiutil.sourceforge.net/FILES/ipmiutil-3.0.0-win32.zipUnzip the downloaded driver package zip file into the ipmirel directory.Install the driver by running the ?install.cmd?file located in the ipmirel directory.For the affected servers running in degraded mode, determine each servers iLO IP, User name, and Password.Open an Administrator Command prompt.Substitute the iLO IP, Username and PW from the 1st affected server into this command line and execute it:ipmiutil-301.exe cmd -N <iLO IP> ?U <User name> -P <password> -J 3 -V 4 00 20 C0 01 0fThe command will respond with ?ipmiutil cmd,completed successfully?.Repeat this command for each affected server substituting in the iLO credentials for each.OPTION 2:After the Onboard Administrator modules have been reinstalled and booted, perform an orderly shutdown of the OS, then open an SSH CLI session with the OA and issue the ?reset server x? command, where ?x? is the server bay number. This remotely power-cycles the server and must be done for EACH server bay that has a blade populated init.OPTION 3:Perform an orderly shutdown of the OS and Power off each server blade in the enclosure. Remove each blade for 10 seconds, then reinstall the blade and allow it to power up.NOTE: The AlertMail notification tool may be used to send email notifications to indicate if the performance is degraded or restored.Login to the Enclosure Onboard AdministratorUnder ENCLOSURE INFORMATION, Expand the ENCLOSURE SETTINGS TabSelect the ALERTMAIL optionCheck the Enable Alertmail checkboxEnter the email address where the notification is to be sentEnter the SMTP server informationSelect and enter the Alert Sender DomainClick APPLYRECEIVE PROACTIVE UPDATES: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice 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 for ProLiant servers and Options, refer to theNavigation Tips document.SEARCH TIP: For hints on locating similar documents on HPE.com, refer to theSearch Tips document.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.