PieterjanMonten's Posts

My bad, this is what was actually happening: The OA firmware management somehow mangled the update, specifically of the emulex driver, which made it unusable and almost un-updatable Only way... See more...
My bad, this is what was actually happening: The OA firmware management somehow mangled the update, specifically of the emulex driver, which made it unusable and almost un-updatable Only way to put the emulex CNA's back in a working state seems to be by using the OneConnect flash iso (OneConnect-Flash-4.9.311.20.iso) available here: http://h20564.www2.hpe.com/hpsc/swd/public/detail?swItemId=co_128972_1 Once back in a working state, the latest SPP (2015.10 at this time) can be mounted with the remote console to perform the update. Once done, and even with the latest Emulex v10.5.155.0 firmware, ESXi 5.5u3 HP runs fine. One signal that the emulex firmware is corrupted is the repeated firmware boot message (which should only appear once) :
Not the same versions of hardware or software but comparable, the BL460C with the 553i emulex works with the service pack for proliant (SPP) 2015.6 (including the emulex firmware v. 10.5.65.21) o... See more...
Not the same versions of hardware or software but comparable, the BL460C with the 553i emulex works with the service pack for proliant (SPP) 2015.6 (including the emulex firmware v. 10.5.65.21) on esxi 5.5u3 HP.
So, just to  finish on a nice touch: esxi5.5u3 HP Cust installs just fine with SPP 2015.6. I had some trouble updating the firmware, the SPP iso couldn't load through the OA firmware manager, ... See more...
So, just to  finish on a nice touch: esxi5.5u3 HP Cust installs just fine with SPP 2015.6. I had some trouble updating the firmware, the SPP iso couldn't load through the OA firmware manager, so I had to launch the update manually with the remote console (>4Gb isos are marked as being unreliable in the 4.40 OA firmware)
Ok, trouble was definitely the v10.5.155.0 Emulex firmware for the 553i CNA adapter. I successfully downgraded it using a OneConnect-Flash iso ( OneConnect-Flash-4.9.311.20.iso ) available her... See more...
Ok, trouble was definitely the v10.5.155.0 Emulex firmware for the 553i CNA adapter. I successfully downgraded it using a OneConnect-Flash iso ( OneConnect-Flash-4.9.311.20.iso ) available here: Drivers & Software - HP Support Center. The host OS (server 2012 I installed just to test it out) finally recognized the NIC and started scanning the network, and the esxi5.5u3 Hp Cust. install loads just fine. Still, hard to imagine how HP can ship a service pack with a firmware that just fails under any conceivable OS. As I downgraded to the 2012.10 SPP (Nic firmware didn't downgrade...)  I'll patch back up to spp 2015.6 and just go backwards until I find the most recent working SPP for the BL460Cg7. With a bit of luck, the G7's will join the cluster for Christmas !
Finally found a related discussion: Vsphere 5.5 and Emulex OneConnect 10Gb NIC trouble I'll try to use the prescribed firmware & driver NIC versions (currently Emulex v10.5.155.0)
Hi Patrick, thanks for your response. Not really much to see, there aren't any mezzanine cards, we use a single [sic] VC Flex-10 10Gb ethernet interconnect module (part 455880-B21). This is th... See more...
Hi Patrick, thanks for your response. Not really much to see, there aren't any mezzanine cards, we use a single [sic] VC Flex-10 10Gb ethernet interconnect module (part 455880-B21). This is the hardware overview from the enclosure administrator (c3000): So we have, besides standard components : 2x Intel Xeon X5670 49152MB DDR3 RDIMM ECC (to be upgraded) Smart Array P410i RAID + 2x 146GB 15k SAS + battery pack NIC's are identified as: HP NC553i 10Gb FlexFabric Adaptor, using the converged network iSCSI personality (normally multiple NIC's are used, but for now they only provide standard LAN access) Up until this night, VC was using firmware 4.10. I was hoping upgrading to 4.45 would help, but that failed to have any impact (besides me erroneously believing the vcenter server crashed)
A small update: 5.1 u2 and u3 , while taking a long time to load at the "loading be2net" step, do load, but then complain there's no network adapter to be found. Thought for a second it was goin... See more...
A small update: 5.1 u2 and u3 , while taking a long time to load at the "loading be2net" step, do load, but then complain there's no network adapter to be found. Thought for a second it was going to be a fine day after all..
Hi, I'm upgrading some of our older blades (bl460c G8 and G9's passed without a hitch) to esxi5.5, but the installer keeps crashing. I've been trying every update of the 5.1 and 5.5 customise... See more...
Hi, I'm upgrading some of our older blades (bl460c G8 and G9's passed without a hitch) to esxi5.5, but the installer keeps crashing. I've been trying every update of the 5.1 and 5.5 customised HP images, to no avail. Installer seems to launch, but then PSOD's as soon as the network drivers load (that's what I concluded). I applied the latest Proliant service pack (2015.10.0), so firmwares are as up to date as can be (interesting note: with the older 2011 firmware the host installed successfully, but network was unusable) Some 5.5u3 (hp cust) screens: Here the installer stops loading: And then it psod's: Any suggestion or other resource I could give a try (Tried some vanilla esxi iso's as well, didn't help) ? I'd really like these ones to join the main cluster, a RAM upgrade and they could be running smoothly for another couple of years.
I had the same behaviour: debian hosts using e1000 driver with a MTU 9000 vlan, dropping 4 bytes on every TCP packet  who's size was in the vicinity of 4025: Server side: 14:20:58.899828 IP 1... See more...
I had the same behaviour: debian hosts using e1000 driver with a MTU 9000 vlan, dropping 4 bytes on every TCP packet  who's size was in the vicinity of 4025: Server side: 14:20:58.899828 IP 10.10.22.1.8000 > 10.10.22.21.34222: Flags [P.], seq 27011:31036, ack 184, win 8009, options [nop,nop,TS val 371053137 ecr 2338244542], length 4025 Client side: 14:20:59.196651 IP truncated-ip - 4 bytes missing! 10.10.22.1.8000 > 10.10.22.21.34222: Flags [P.], seq 27011:31036, ack 184, win 8009, options [nop,nop,TS val 371053243 ecr 2338244542], length 4025 I didn't want to switch to vmxnet3 drivers or disable jumbo frames right away, so I went with setting the MTU to 3000 (For the sake of keeping jumbo frames. I'd recommend simply going back to standard MTU 1500, there's not that much to win from it anyway). As fragmented packets now stay below the 4K limit, everything is smooth again, no more truncated packets !