In the end we managed to get HP to deal with it as a warranty issue, we raised enough of a fuss that they had someone come in and do it for us. One co-worker told me that he'd been warned by HP that there is a specific order you have to run the updates in, otherwise you risk bricking components however an HP service agent denied that. The whole chassis will be inoperable during this update, and components are updated serially so it can take several hours to run.
#HP ILO 4 WEB INTERFACE NOT WORKING UPDATE#
Note that you have to update the firmware for all components - OA, VC (if you have it), as well as individual iLOs, and blade BIOSs. Look for, or call HP and ask for, a firmware update and apply that. In our case, HP denied there was a known problem even though both of our chassis exhibited the issue.ĭepending on when this chassis was shipped, you may be in this boat. I will admit we didn't try the downloadable iLO configuration application a couple of these blades run ESX, which makes the tool rather academic anyways. Removing and reseating individual modules didn't work. The only way to get everything talking together again was to power-cycle the whole chassis - shutdown all blades, then pull the power inputs. This was repeatable, and all blade iLOs would go unresponsive within about an hour of each other, 30 to 90 days after being started. With an older firmware, the iLO on the blades would become non-responsive both to the chassis and to the rest of the network (the iLOs were IP-enabled for IP-KVM purposes). One of my customers has a couple of C3000 chassis. This research only applies to iLO version 4. This blog post aims at giving some details about this vulnerability, and a few hints for administrators to protect their servers. While the firmware update adds several enhancements, the one generating the most buzz is HTML5 support for Remote Console. If the OA can't talk to the iLOs on the blades, you have a problem. On August 28th, HP published a security bulletin regarding a critical vulnerability in HP Integrated Lights-Out (iLO) 4. Recently, Hewlett Packard Enterprise (HPE) rolled out the latest firmware update to its Integrated Lights-Out Management (iLO) 4, version 2.70. You should be able to apply iLO configuration values to the iLO via the OA. This advisory will be updated when additional information becomes available.The chassis OA has the ability to over-ride existing iLO configurations and talk to the blades no matter what the previous admin did. iLO Mobile Application to access the iLO Remote console.
NET IRC application available from hp.com
#HP ILO 4 WEB INTERFACE NOT WORKING SOFTWARE#
However, the ClickOnce extension is not an HP product, nor is it endorsed by HP.Īny HP ProLiant server configured with any previous or current firmware versions of Integrated Lights-Out 3 (iLO 3) or Integrated Lights-Out 4 (iLO 4) and with the Google Chrome browser and "ClickOnce for Chrome" software application installed.Ī future version of iLO 3 and iLO 4 firmware will remove the link from the Integrated Lights-Out (iLO) webpage.Īs a workaround, uninstall the ClickOnce extension for Chrome browser. The link to the extension's home page is displayed on the Integrated Lights-Out (iLO) web pages and the iLO user guide. This update adds permissions and changes the extension's behavior. The ClickOnce browser extension has recently been updated and now unsolicited advertising may display unexpectedly. The "ClickOnce" for Google Chrome browser extension may be used in some instances to access the HP Integrated Lights-Out (iLO). This document is subject to change without notice. NOTICE: The information in this document, including products and software versions, is current as of the Release Date. SUPPORT COMMUNICATION - CUSTOMER ADVISORYĪdvisory: HP Integrated Lights-Out (iLO) - "ClickOnce" for Google Chrome Browser May Trigger Unwanted Behavior for iLO 3 or iLO 4
Apparently iLO on Chrome says to use a browser extension called ClickOnce, which they have no control over and now is an advertising platform.
0 kommentar(er)
