Why PXE Booting Matters
Many of the servers we maintained were older ProLiant G6 systems running iLO2. Anyone who has used iLO2 knows the limitations: slow virtual media, unreliable ISO mounting, and frequent disconnects. When working remotely over VPN, especially on weekends, these limitations made even simple maintenance tasks slow and unpredictable.
To solve this, we built a complete PXE boot environment that allowed us to install operating systems, update firmware, run diagnostics, and repair systems without relying on iLO virtual media. This approach turned routine maintenance into a fast, repeatable process that could be performed entirely remotely.
Building a Remote Maintenance Toolkit
The PXE environment was designed to provide everything needed to maintain and repair servers without physical access. It included:
- XCP‑ng installers for hypervisor upgrades
- Multiple versions of HP Service Pack for ProLiant (SPP)
- CentOS and other Linux installers
- Trinity Rescue Kit for recovery tasks
- Memtest86+ for RAM diagnostics
- Filesystem repair tools
- A consistent graphical menu system
- Password‑protected submenus for sensitive tools
This meant that almost any maintenance task could be performed by simply rebooting the server into the PXE menu.
Why iLO2 Made PXE Essential
On G6 hardware, iLO2 virtual media typically transfers data at a few hundred kilobytes per second. Mounting an ISO could take several minutes, and installations often failed due to timeouts or browser issues. When working from home over VPN, these problems were magnified.
PXE booting avoided all of these issues:
- No ISO mounting
- No Java plugin failures
- No browser compatibility problems
- No mid‑install disconnects
- Full network speed for loading installers
- Predictable, repeatable behaviour
This made remote maintenance practical and reliable.
A Typical Workflow
Most upgrades were performed on Sunday afternoons from home. After connecting to the site via VPN, the process was straightforward:
- Open iLO2 for the target server
- Reboot into the PXE menu
- Select the required installer or tool
- Perform the upgrade or repair
- Reboot back into the local system
Because everything was delivered over PXE, the process was fast and consistent. There was no waiting for virtual media or dealing with failed ISO mounts.
Supporting Multiple Generations of Firmware
The PXE environment included several versions of HP SPP, covering a wide range of hardware:
- SPP 2013.09
- SPP 2016.10
- SPP 2017.04
- SPP 2021.10
This allowed firmware updates on older G6 systems as well as newer Gen9 hardware, all from the same menu system.
Diagnostics and Recovery Tools
In addition to installers and firmware updates, the PXE menu provided tools for diagnosing and repairing systems:
- Memtest86+ for identifying faulty RAM
- Trinity Rescue Kit for password resets, bootloader repair, and network troubleshooting
- Filesystem repair tools for recovering unbootable Linux systems
These tools made it possible to resolve many issues without visiting the site.
Engineering Philosophy
The PXE environment reflects a broader approach to system design:
- Automate repetitive tasks
- Avoid unreliable tools
- Build once and use for years
- Keep systems simple and predictable
- Make remote work practical
- Provide consistent interfaces for maintenance
By investing time in building a robust PXE system, we reduced the effort required for ongoing maintenance and improved the reliability of remote operations.
Conclusion
PXE booting allowed us to maintain and upgrade servers efficiently, even when working remotely on older hardware with limited management capabilities. By providing a complete set of installers, firmware updates, and diagnostic tools, the PXE environment became an essential part of our infrastructure. It saved time, reduced frustration, and made weekend maintenance far more manageable.