antipaucity

fighting the lack of good ideas

defaulting pxe boots with hpsa 10.0

In follow-up to my last post, which itself was a commentary on an earlier topic, I have the additional steps you need to do the previous procude (which is to edit /opt/opsware/boot/tftpboot/pxelinux.cfg/default):

/etc/init.d/opsware-sas stop smartboot

Edit file.

/etc/init.d/opsware-sas start smartboot

pxe works differently in hpsa 10.x

2 years ago I wrote-up how you can change the default choice for the PXE menu in HP Server Automation. Found out this week that those instructions are not valid if you are running 10.0 (release this past summer).

HP changed how they present their PXE menu with 10.x, and I have filed an RFE (on 18 Dec 2013) with them to get this fixed back to how it was (or provide a solid alternative).

This is one of the times when I’ve ever seen a vendor remove functionality in a product (at least, removed without providing an alternative).

Thanks, HP 😐

automatically returning a host to the unprovisioned server pool in hpsa

In conjunction with the customized PXE process I wrote about previously, it could be highly desirable to be able to return a server to the unprovisioned server pool in HP’s Server Automation.

This is a specifically-Linux procedure: though I’m sure something similar can be done with Windows*.

run an ad-hoc script against a target server that contains the following:

dd if=/dev/zero of=/dev/sda bs=512 count=1
sleep 1
nohup reboot

This will erase the MBR and partition table, and then reboot the server.

Before it reboots, however, you need to deactivate and delete the server from SA – otherwise it will not register correctly.

If you’ve already enabled (or not disabled) PXE booting, when it reboots, it will pick the default entry off the PXE menu, skipping the hard drive as there is no valid boot record available to it.

Why would you want to do this?

Well, let’s say you’re doing a lot of build testing (verifying ks.cfg or unattend.xml files, for example) – this could be useful.

Or, maybe you want to get your build process completely streamlined and you’re working with the MBC functionality in SA – again, rapid recycling of machines is highly desirable.

In a later post I’ll discuss freeing the VM from SA in the process (ie, removing it from the ESXi host to fully release resources).


*In fact, you may be able to run fdisk /mbr on a Windows server – but I haven’t tried.