On Tue, 6 Jul 2010 at 10:01pm, Michael Di Domenico wrote
Does anyone on the list have HP DL170h G6 blade chassis's on their floor? Ours came with the on-board NIC mac addresses programmed in descending order, I'm curious if this is something new, I've never seen this done before. Every machine we have on the floor now has them in ascending order. The downside to the nic enumeration is that in bios eth0 is eth0 and pxe's from eth0, however, when inside anaconda (redhat) eth0 is really eth1, and thus kickstart cant run. The only time i've seen this happen is when the nic drivers load out of order, but that's easy to fix in the initrd
I demoed the a chassis full of the HP SL2x170z G6s, and they had the same problem -- BIOS/PXE eth0 became eth1 in anaconda. I worked around it by passing anaconda "ksdevice=bootif" in the pxe config file. But, yeah, it's annoying having to work around oddness like that. I'm looking at that model or the DL160 G6 (standard 1U), and I imagine the 160 will have the same issue.
Does anyone know if this is firmware flash fixable? HP refuses to acknowledge the question...
And, if it is, how many person-years will it take to find said firmware flash file on HP's website (seriously, how broken is that site!?)?
-- Joshua Baker-LePain QB3 Shared Cluster Sysadmin UCSF _______________________________________________ Beowulf mailing list, [email protected] sponsored by Penguin Computing To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
