Recently, just some days before the writing of this post, one of my customers called me because of a vCenter issue. But if you read this blog post you can see that it fits very well. Hp ilo firmware download dl360 g9.Yes i know that, the title of this blog post doesn’t sound very well. All SQL queries work in the.I made a quick look through remote support and saw that. The customer told me that some VM’s aren’t running anymore and that both hosts aren’t available in vCenter management. With the added performance that 12 nvdimms and 10 nvme brings, the hpe proliant dl360 gen10 means business. Operating cpqonlin in manual configuration mode. Laptop Computers, Desktops, Printers, Ink & Toner, HP.
Hp Dl360 G9 Download Dl360 G9The hosts did respond to ping, so that’s at least a little light at the end of the tunnel.Product Support Software & Drivers Warranty Check Enhanced Support Services Education and Training Product Return and Recycling OEM Solutions. That’s kind of strange, didn’t see that until yet. At least we were able to logon, but the DCUI didn’t respond after successful login. We tried to access the DCUI with moderate success. We first tried to access the hosts through SSH but no success. My friend Andreas Lesslhumer from running-system.com just had this issue recently, so he created a blog post to help us others when we should encounter this issue too. Could it be a firmware / BIOS issue?A quick hipshot to Google showed up a promising result. The customer powered off and restarted the server but with the same issue. We waited for “some moments” but nothing happened. He told me that he just had this issue the same day when i had it, and a downgrade of the iLO firmware didn’t help in his case. There was nothing missed or wrong. We also did a System ROM downgrade to version 2.30 but that didn’t help too.I then contacted Andreas to ask him if i missed something. We tried to go a little lower to version 2.30 but that didn’t help neither. But unfortunately in our case it didn’t help. It looks that the recent iLO firmware 2.50 (which is included in the HPE Service Pack for ProLiant April 2017) has some issues.First we tried to downgrade the iLO firmware to version 2.40 as mentioned in his blogpost. Bumps on balls sackI’m working in IT several years now and i saw many things. HPE will check logs for you, check spare parts and logistics and so on. Even if you’re familiar with HPE servers and storage and work often with it i recommend you to open a support case. Let’s double check this now. Ok, it’s a HPE storage related issue…Now we’re talking! At least the boot problems are caused by the HPE MSA storage. We removed them but the server still didn’t boot. It was more a coincidence that we were thinking about “hey, let’s just unplug the storage and see if the server then will boot”.So we unplugged the SAS cables from the servers and voilà, both servers booted without any problems. We checked also the SD cards which are installed into the server as boot drive for ESXi. So help through the manufacturer was needed.Some time went by with up- and downgrades of iLO and System ROM firmware, rebooting and testing the servers if they now boot. Fingerprint time clocks small businessWe repeated this step but with controller 2. The server bootet without problems. After we shutdown both servers, we only plugged in the SAS cable from controller 1 to ESXi server 1. We also removed the power cables and let it spin down for a moment. When controller 2 is connected, the server won’t boot.We then unplugged the storage completely and did also a complete storage shutdown. And again the same picture. First boot with controller 1 connected, then second boot with controller 2 connected. So minimal configuration wasn’t necessary because server boots up without storage Servers doesn’t boot with storage controller 2 connected Both server boots with storage controller 1 connected The servers boot without connected storage It’s not a incompatibility between iLO firmware and System ROM And it did! Shutting down the storage and making it powerless helped!Both servers booted with each storage controller connected, and also when both controllers were connected! What we figured out so far…Let’s have quick look what we figured out until yet: It took just long.We did some final test after all the firmware upgrades and were finally able to properly boot the servers and to get the domain controller and vCenter back up and running. Updating the storage firmware took a long time, probably 20 to 30 minutes per controller, but to be honest I didn’t measure the time. MSA 2040 SAS Dual Controller: GL220P009System ROM, iLO and HBA firmware were part of the above mentioned HPE Service Pack for ProLiant (SPP) except the latest iLO version which we downloaded directly from HPE and updated it through iLO itself. At the time of the release of this blog post we had this firmware versions installed on the servers and storage: Final steps to solve the issueFinally we did a lot of firmware upgrades to make sure we’re on the most recent state with compatibility, functions and bug fixes. Complete shutdown of the storage and making it powerless helped!Now we knew how what’s the cause for the servers to not boot up properly or freeze in the POST screen and we were able to fix that. But in our case it was the MSA storage causing the servers not to boot if it’s connected to them.We were glad we figured that out and the customer is happy that the infrastructure is back online and all his services are running fine. The causes can be so different. I would not have wondered if it was an external USB drive that caused the issue or any USB dongle thingy. But it doesn’t have to be. It could happen that there is some software / firmware incompatibility. But i gained some good experiences. ConclusionIt took some hours to get this infrastructure back up and running.
0 Comments
Leave a Reply. |
AuthorKristen ArchivesCategories |