HP ProLiant DL360 Gen9 Analysis

• 1: Configuration Guide
• 2: Hardware Specifications
• 3: Network Boot Capabilities

1 - Configuration Guide

Initial Setup

Hardware Assembly

1. Install Processors:

   • Use thermal paste (HPE thermal grease recommended)
   • Align CPU carefully with socket (LGA 2011-3)
   • Secure heatsink with proper torque (hand-tighten screws in cross pattern)
   • Install both CPUs for dual-socket configuration

2. Install Memory:

   • Populate channels evenly (see Memory Configuration below)
   • Seat DIMMs firmly until retention clips engage
   • Verify all DIMMs recognized in POST

3. Install Storage:

   • Insert drives into hot-swap caddies
   • Label drives clearly for identification
   • Configure RAID controller (see Storage Configuration below)

4. Install Network Cards:

   • FlexibleLOM: Slide into dedicated slot until seated
   • PCIe cards: Ensure low-profile brackets, secure with screw
   • Note MAC addresses for DHCP reservations

5. Connect Power:

   • Install PSUs (both for redundancy)
   • Connect power cords
   • Verify PSU LEDs indicate proper operation

6. Initial Power-On:

   • Press power button
   • Monitor POST on screen or via iLO remote console
   • Address any POST errors before proceeding

iLO 4 Initial Configuration

Physical iLO Connection

1. Connect Ethernet cable to dedicated iLO port (not FlexibleLOM)
2. Default iLO IP: Obtains via DHCP, or use temporary address via RBSU
3. Check DHCP server logs for iLO MAC and assigned IP

First Login

1. Access iLO web interface: https://<ilo-ip>
2. Default credentials:
   • Username: Administrator
   • Password: On label on server pull-out tab (or rear label)
3. Immediately change default password (Administration > Access Settings)

Essential iLO Settings

Network Configuration (Administration > Network):

• Set static IP or DHCP reservation
• Configure DNS servers
• Set hostname (e.g., ilo-dl360-01)
• Enable SNTP time sync

Security (Administration > Security):

• Enforce HTTPS only (disable HTTP)
• Configure SSH key authentication if using CLI
• Set strong password policy
• Enable iLO Security features

Access (Administration > Access Settings):

• Configure iLO username/password for automation
• Create additional user accounts (separation of duties)
• Set session timeout (default: 30 minutes)

Date and Time (Administration > Date and Time):

• Set NTP servers for accurate timestamps
• Configure timezone

Licenses (Administration > Licensing):

• Install iLO Advanced license key (required for full virtual media)
• License can be purchased or acquired from secondary market

iLO Firmware Update

Before production use, update iLO to latest version:

1. Download latest iLO 4 firmware from HPE Support Portal
2. Administration > Firmware > Update Firmware
3. Upload .bin file, apply update
4. iLO will reboot automatically (system stays running)

System ROM (BIOS/UEFI) Configuration

Accessing RBSU

• Local: Press F9 during POST
• Remote: iLO Remote Console > Power > Momentary Press > Press F9 when prompted

Boot Mode Selection

System Configuration > BIOS/Platform Configuration (RBSU) > Boot Mode:

• UEFI Mode (recommended for modern OS):

  • Supports GPT partitions (>2TB disks)
  • Required for Secure Boot
  • Better UEFI HTTP boot support
  • IPv6 PXE boot support

• Legacy BIOS Mode:

  • For older OS or compatibility
  • MBR partition tables only
  • Traditional PXE boot

Recommendation: Use UEFI Mode unless legacy compatibility required

Boot Order Configuration

System Configuration > BIOS/Platform Configuration (RBSU) > Boot Options > UEFI Boot Order:

Recommended order for network boot deployment:

1. Network Boot: FlexibleLOM or PCIe NIC
2. Internal Storage: RAID controller or disk
3. Virtual Media: iLO virtual CD/DVD (for installation media)
4. USB: For rescue/recovery

Enable Network Boot:

• System Configuration > BIOS/Platform Configuration (RBSU) > Network Options > Network Boot
• Set to “Enabled”

Performance and Power Settings

System Configuration > BIOS/Platform Configuration (RBSU) > Power Management:

• Power Regulator Mode:

  • HP Dynamic Power Savings: Balanced power/performance (recommended for home lab)
  • HP Static High Performance: Maximum performance, higher power draw
  • HP Static Low Power: Minimize power, reduced performance
  • OS Control: Let OS manage (e.g., Linux cpufreq)

• Collaborative Power Control: Disabled (for standalone servers)

• Minimum Processor Idle Power Core C-State: C6 (lower idle power)

• Energy/Performance Bias: Balanced Performance (or Maximum Performance for compute workloads)

Recommendation: Start with “Dynamic Power Savings” and adjust based on workload

Memory Configuration

Optimal Population (dual-CPU configuration):

For maximum performance, populate all channels before adding second DIMM per channel:

64GB (8x 8GB):

• CPU1: Slots 1, 4, 7, 10 and CPU2: Slots 1, 4, 7, 10
• Result: 4 channels per CPU, 1 DIMM per channel

128GB (8x 16GB):

• Same as above with 16GB DIMMs

192GB (12x 16GB):

• CPU1: Slots 1, 4, 7, 10, 2, 5 and CPU2: Slots 1, 4, 7, 10, 2, 5
• Result: 4 channels per CPU, some with 2 DIMMs per channel

768GB (24x 32GB):

• All slots populated

Check Configuration: RBSU > System Information > Memory Information

Processor Options

System Configuration > BIOS/Platform Configuration (RBSU) > Processor Options:

• Intel Hyperthreading: Enabled (recommended for most workloads)

  • Doubles logical cores (e.g., 12-core CPU shows as 24 cores)
  • Benefits most virtualization and multi-threaded workloads
  • Disable only for specific security compliance (e.g., some cloud providers)

• Intel Virtualization Technology (VT-x): Enabled (required for hypervisors)

• Intel VT-d (IOMMU): Enabled (required for PCI passthrough, SR-IOV)

• Turbo Boost: Enabled (allows CPU to exceed base clock)

• Cores Enabled: All (or reduce to lower power/heat if needed)

Integrated Devices

System Configuration > BIOS/Platform Configuration (RBSU) > System Options > Integrated Devices:

• Embedded SATA Controller: Enabled (if using SATA drives)
• Embedded RAID Controller: Enabled (for Smart Array controllers)
• SR-IOV: Enabled (if using virtual network interfaces with VMs)

Network Controller Options

For each NIC (FlexibleLOM, PCIe):

System Configuration > BIOS/Platform Configuration (RBSU) > Network Options > [Adapter]:

• Network Boot: Enabled (for network boot on that NIC)
• PXE/iSCSI: Select PXE for standard network boot
• Link Speed: Auto-Negotiation (recommended) or force 1G/10G
• IPv4: Enabled (for IPv4 PXE boot)
• IPv6: Enabled (if using IPv6 PXE boot)

Boot Order: Configure which NIC boots first if multiple are enabled

Secure Boot Configuration

System Configuration > BIOS/Platform Configuration (RBSU) > Boot Options > Secure Boot:

• Secure Boot: Disabled (for unsigned boot loaders, custom kernels)
• Secure Boot: Enabled (for signed boot loaders, Windows, some Linux distros)

Note: If using PXE with unsigned images (e.g., custom iPXE), Secure Boot must be disabled

Firmware Updates

Update System ROM to latest version:

1. Via iLO:

   • iLO web > Administration > Firmware > Update Firmware
   • Upload System ROM .fwpkg or .bin file
   • Server reboots automatically to apply

2. Via Service Pack for ProLiant (SPP):

   • Download SPP ISO from HPE Support Portal
   • Mount via iLO Virtual Media
   • Boot server from SPP ISO
   • Smart Update Manager (SUM) runs in Linux environment
   • Select components to update (System ROM, iLO, controller firmware, NIC firmware)
   • Apply updates, reboot

Recommendation: Use SPP for comprehensive updates on initial setup, then iLO for individual component updates

Storage Configuration

Smart Array Controller Setup

Access Smart Array Configuration

• During POST: Press F5 when “Smart Array Configuration Utility” message appears
• Via RBSU: System Configuration > BIOS/Platform Configuration (RBSU) > System Options > ROM-Based Setup Utility > Smart Array Configuration

Create RAID Arrays

1. Delete Existing Arrays (if reconfiguring):

   • Select controller > Configuration > Delete Array
   • Confirm deletion (data loss warning)

2. Create New Array:

   • Select controller > Configuration > Create Array
   • Select physical drives to include
   • Choose RAID level:
     • RAID 0: Striping, no redundancy (maximum performance, maximum capacity)
     • RAID 1: Mirroring (redundancy, half capacity, good for boot drives)
     • RAID 5: Striping + parity (redundancy, n-1 capacity, balanced)
     • RAID 6: Striping + double parity (dual-drive failure tolerance, n-2 capacity)
     • RAID 10: Mirror + stripe (high performance + redundancy, half capacity)
   • Configure spare drives (hot spares for automatic rebuild)
   • Create logical drive
   • Set bootable flag if boot drive

3. Recommended Configurations:

   • Boot/OS: 2x SSD in RAID 1 (redundancy, fast boot)
   • Data (performance): 4-6x SSD in RAID 10 (fast, redundant)
   • Data (capacity): 4-8x HDD in RAID 6 (capacity, dual-drive tolerance)

Controller Settings

• Cache Settings:

  • Write Cache: Enabled (requires battery/flash-backed cache)
  • Read Cache: Enabled
  • No-Battery Write Cache: Disabled (data safety) or Enabled (performance, risk)

• Rebuild Priority: Medium or High (faster rebuild, may impact performance)

• Surface Scan Delay: 3-7 days (periodic integrity check)

HBA Mode (Non-RAID)

For software RAID (ZFS, mdadm, Ceph):

1. Access Smart Array Configuration (F5 during POST)
2. Controller > Configuration > Enable HBA Mode
3. Confirm (RAID arrays will be deleted)
4. Reboot

Note: Not all Smart Array controllers support HBA mode. Check compatibility. Alternative: Use separate LSI HBA in PCIe slot.

Network Configuration for Boot

DHCP Server Setup

For PXE/UEFI network boot, configure DHCP server with appropriate options:

ISC DHCP Example (/etc/dhcp/dhcpd.conf):

# Define subnet
subnet 192.168.10.0 netmask 255.255.255.0 {
    range 192.168.10.100 192.168.10.200;
    option routers 192.168.10.1;
    option domain-name-servers 192.168.10.1;
    
    # PXE boot options
    next-server 192.168.10.5;  # TFTP server IP
    
    # Differentiate UEFI vs BIOS
    if exists user-class and option user-class = "iPXE" {
        # iPXE boot script
        filename "http://boot.example.com/boot.ipxe";
    } elsif option arch = 00:07 or option arch = 00:09 {
        # UEFI (x86-64)
        filename "bootx64.efi";
    } else {
        # Legacy BIOS
        filename "undionly.kpxe";
    }
}

# Static reservation for DL360
host dl360-01 {
    hardware ethernet xx:xx:xx:xx:xx:xx;  # FlexibleLOM MAC
    fixed-address 192.168.10.50;
    option host-name "dl360-01";
}

FlexibleLOM Configuration

Configure FlexibleLOM NIC for network boot:

1. RBSU > Network Options > FlexibleLOM
2. Enable “Network Boot”
3. Select PXE or iSCSI
4. Configure IPv4/IPv6 as needed
5. Set as first boot device in boot order

Multi-NIC Boot Priority

If multiple NICs have network boot enabled:

1. RBSU > Network Options > Network Boot Order
2. Drag/drop to prioritize NIC boot order
3. First NIC in list attempts boot first

Recommendation: Enable network boot on one NIC (typically FlexibleLOM port 1) to avoid confusion

Operating System Installation

Traditional Installation (Virtual Media)

1. Download OS ISO (e.g., Ubuntu Server, ESXi, Proxmox)
2. Upload ISO to HTTP/HTTPS server or local file
3. iLO Remote Console > Virtual Devices > Image File CD-ROM/DVD
4. Browse to ISO location, click “Insert Media”
5. Set boot order to prioritize virtual media
6. Reboot server, boot from virtual CD/DVD
7. Proceed with OS installation

Network Installation (PXE)

See Network Boot Capabilities for detailed PXE/UEFI boot setup

Quick workflow:

1. Configure DHCP server with PXE options
2. Setup TFTP server with boot files
3. Enable network boot in BIOS
4. Reboot, server PXE boots
5. Select OS installer from PXE menu
6. Automated installation proceeds (Kickstart/Preseed/Ignition)

Optimization for Specific Workloads

Virtualization (ESXi, Proxmox, Hyper-V)

BIOS Settings:

• Hyperthreading: Enabled
• VT-x: Enabled
• VT-d: Enabled
• Power Management: Dynamic or OS Control
• Turbo Boost: Enabled

Hardware:

• Maximum memory (384GB+ recommended)
• Fast storage (SSD RAID 10 for VM storage)
• 10GbE networking for VM traffic

Configuration:

• Pass through NICs to VMs (SR-IOV or PCI passthrough)
• Use storage controller in HBA mode for direct disk access to VM storage (ZFS, Ceph)

Kubernetes/Container Platforms

BIOS Settings:

• Hyperthreading: Enabled
• VT-x/VT-d: Enabled (for nested virtualization, kata containers)
• Power Management: Dynamic or High Performance

Hardware:

• 128GB+ RAM for multi-tenant workloads
• Fast local NVMe/SSD for container image cache and ephemeral storage
• 10GbE for pod networking

OS Recommendations:

• Talos Linux: Network-bootable, immutable k8s OS
• Flatcar Container Linux: Auto-updating, minimal OS
• Ubuntu Server: Broad compatibility, snap/docker native

Storage Server (NAS, SAN)

BIOS Settings:

• Disable Hyperthreading (slight performance improvement for ZFS)
• VT-d: Enabled (if passing through HBA to VM)
• Power Management: High Performance

Hardware:

• Maximum drive bays (8-10 SFF)
• HBA mode or separate LSI HBA controller
• 10GbE or bonded 1GbE for network storage traffic
• ECC memory (critical for ZFS)

Software:

• TrueNAS SCALE (Linux-based, k8s apps)
• OpenMediaVault (Debian-based, plugins)
• Ubuntu + ZFS (custom setup)

Compute/HPC Workloads

BIOS Settings:

• Hyperthreading: Depends on workload (test both)
• Turbo Boost: Enabled
• Power Management: Maximum Performance
• C-States: Disabled (reduce latency)

Hardware:

• High core count CPUs (E5-2680 v4, 2690 v4)
• Maximum memory bandwidth (populate all channels)
• Fast local scratch storage (NVMe)

Monitoring and Maintenance

iLO Health Monitoring

Information > System Information:

• CPU temperature and status
• Memory status
• Drive status (via controller)
• Fan speeds
• PSU status
• Overall system health LED status

Alerting (Administration > Alerting):

• Configure email alerts for:
  • Fan failures
  • Temperature warnings
  • Drive failures
  • Memory errors
  • PSU failures
• Set up SNMP traps for integration with monitoring systems (Nagios, Zabbix, Prometheus)

Integrated Management Log (IML)

Information > Integrated Management Log:

• View hardware events and errors
• Filter by severity (Informational, Caution, Critical)
• Export log for troubleshooting

Regular Checks:

• Review IML weekly for early warning signs
• Address caution-level events before they become critical

Firmware Update Cadence

Recommendation:

• iLO: Update quarterly or when security advisories released
• System ROM: Update annually or for bug fixes
• Storage Controller: Update when issues arise or annually
• NIC Firmware: Update when issues arise

Method: Use SPP for annual comprehensive updates, iLO web interface for individual component updates

Physical Maintenance

Monthly:

• Check fan noise (increased noise may indicate clogged air filters or failing fan)
• Verify PSU and drive LEDs (no amber lights)
• Check iLO for alerts

Quarterly:

• Clean air filters (if accessible, depends on rack airflow)
• Verify backup of iLO configuration
• Test iLO Virtual Media functionality

Annually:

• Update all firmware via SPP
• Verify RAID battery/flash-backed cache status
• Review and update BIOS settings as workload evolves

Troubleshooting Common Issues

Server Won’t Power On

1. Check PSU power cords connected
2. Verify PSU LEDs indicate power
3. Press iLO power button via web interface
4. Check iLO IML for power-related errors
5. Reseat PSUs, check for blown fuses

POST Errors

Memory Errors:

• Reseat memory DIMMs
• Test with minimal configuration (1 DIMM per CPU)
• Replace failing DIMMs identified in POST

CPU Errors:

• Verify heatsink properly seated
• Check thermal paste application
• Reseat CPU (careful with pins)

Drive Errors:

• Check drive connection to caddy
• Verify controller recognizes drive
• Replace failing drive

No Network Boot

See Network Boot Troubleshooting for detailed diagnostics

Quick checks:

1. Verify NIC link light
2. Confirm network boot enabled in BIOS
3. Check DHCP server logs for PXE request
4. Test TFTP server accessibility

iLO Not Accessible

1. Check physical Ethernet connection to iLO port
2. Verify switch port active
3. Reset iLO: Press and hold iLO NMI button (rear) for 5 seconds
4. Factory reset iLO via jumper (see maintenance guide)
5. Check iLO firmware version, update if outdated

High Fan Noise

1. Check ambient temperature (<25°C recommended)
2. Verify airflow not blocked (front/rear clearance)
3. Clean dust from intake (compressed air)
4. Check iLO temperature sensors for elevated temps
5. Lower CPU TDP if temperatures excessive (lower power CPUs)
6. Verify all fans operational (replace failed fans)

Security Hardening

iLO Security

1. Change Default Credentials: Immediately on first boot
2. Disable Unused Services: SSH, IPMI if not needed
3. Use HTTPS Only: Disable HTTP (Administration > Network > HTTP Port)
4. Network Isolation: Dedicated management VLAN, firewall iLO access
5. Update Firmware: Apply security patches promptly
6. Account Management: Use separate accounts, least privilege

BIOS/UEFI Security

1. BIOS Password: Set administrator password (RBSU > System Options > BIOS Admin Password)
2. Secure Boot: Enable if using signed boot loaders
3. Boot Order Lock: Prevent unauthorized boot device changes
4. TPM: Enable if using BitLocker or LUKS disk encryption

Operating System Security

1. Minimal Installation: Install only required packages
2. Firewall: Enable host firewall (iptables, firewalld, ufw)
3. SSH Hardening: Key-based auth, disable password auth, non-standard port
4. Automatic Updates: Enable for security patches
5. Monitoring: Deploy intrusion detection (fail2ban, OSSEC)

Conclusion

Proper configuration of the HP ProLiant DL360 Gen9 ensures optimal performance, reliability, and manageability for home lab and production deployments. The combination of UEFI boot capabilities, iLO remote management, and flexible hardware configuration makes the DL360 Gen9 a versatile platform for virtualization, containerization, storage, and compute workloads.

Key takeaways:

• Update firmware early (iLO, System ROM, controllers)
• Configure iLO for remote management and monitoring
• Choose boot mode (UEFI recommended) and configure network boot appropriately
• Optimize BIOS settings for specific workload (virtualization, storage, compute)
• Implement security hardening (iLO, BIOS, OS)
• Establish monitoring and maintenance schedule

For network boot-specific configuration, refer to the Network Boot Capabilities guide.

2 - Hardware Specifications

System Overview

The HP ProLiant DL360 Gen9 is a dual-socket 1U rack server designed for data center and enterprise deployments, also popular in home lab environments due to its performance and manageability.

Generation: Gen9 (2014-2017 product cycle)
Form Factor: 1U rack-mountable (19-inch standard rack)
Dimensions: 43.46 x 67.31 x 4.29 cm (17.1 x 26.5 x 1.69 in)

Processor Support

Supported CPU Families

The DL360 Gen9 supports Intel Xeon E5-2600 v3 and v4 series processors:

• E5-2600 v3 (Haswell-EP): Released Q3 2014

  • Process: 22nm
  • Cores: 4-18 per socket
  • TDP: 55W-145W
  • Max Memory Speed: DDR4-2133

• E5-2600 v4 (Broadwell-EP): Released Q1 2016

  • Process: 14nm
  • Cores: 4-22 per socket
  • TDP: 55W-145W
  • Max Memory Speed: DDR4-2400

Popular CPU Options

Value: E5-2620 v3/v4 (6 cores, 15MB cache, 85W)
Balanced: E5-2650 v3/v4 (10-12 cores, 25-30MB cache, 105W)
Performance: E5-2680 v3/v4 (12-14 cores, 30-35MB cache, 120W)
High Core Count: E5-2699 v4 (22 cores, 55MB cache, 145W)

Configuration Options

• Single Processor: One CPU socket populated (budget option)
• Dual Processor: Both sockets populated (full performance)

Note: Memory and I/O performance scales with processor count. Single-CPU configuration limits memory channels and PCIe lanes.

Memory Architecture

Memory Specifications

• Type: DDR4 RDIMM or LRDIMM
• Speed: DDR4-2133 (v3) or DDR4-2400 (v4)
• Slots: 24 DIMM slots (12 per processor)
• Maximum Capacity:
  • 768GB with 32GB RDIMMs
  • 1.5TB with 64GB LRDIMMs (v4 processors)
• Minimum: 8GB (1x 8GB DIMM)

Memory Configuration Rules

• Channels per CPU: 4 channels, 3 DIMMs per channel
• Population: Populate channels evenly for optimal bandwidth
• Mixing: Do not mix RDIMM and LRDIMM types
• Speed: All DIMMs run at speed of slowest DIMM

Recommended Configurations

Basic Home Lab (Single CPU):

• 4x 16GB = 64GB (one DIMM per channel on both memory boards)

Standard (Dual CPU):

• 8x 16GB = 128GB (one DIMM per channel)
• 12x 16GB = 192GB (two DIMMs per channel on primary channels)

High Capacity (Dual CPU):

• 24x 32GB = 768GB (all slots populated, RDIMM)

Performance Priority: Populate all channels before adding second DIMM per channel

Storage Options

Drive Bay Configurations

The DL360 Gen9 offers multiple drive bay configurations:

1. 8 SFF (2.5-inch): Most common configuration
2. 10 SFF: Extended bay version
3. 4 LFF (3.5-inch): Less common in 1U form factor

Drive Types Supported

• SAS: 12Gb/s, 6Gb/s (enterprise-grade)
• SATA: 6Gb/s, 3Gb/s (value option)
• SSD: SAS/SATA SSD, NVMe (with appropriate controller)

Storage Controllers

Smart Array Controllers (HPE proprietary RAID):

• P440ar: Entry-level, 2GB FBWC (Flash-Backed Write Cache), RAID 0/1/5/6/10
• P840ar: High-performance, 4GB FBWC, RAID 0/1/5/6/10/50/60
• P440: PCIe card version, 2GB FBWC
• P840: PCIe card version, 4GB FBWC

HBA Mode (non-RAID pass-through):

• Smart Array controllers in HBA mode for software RAID (ZFS, mdadm)
• Limited support; check firmware version

Alternative Controllers:

• LSI/Broadcom HBA controllers in PCIe slots
• H240ar (12Gb/s HBA mode)

Boot Drive Options

For network-focused deployments:

• Minimal Local Storage: 2x SSD in RAID 1 for hypervisor/OS
• USB/SD Boot: iLO supports USB boot, SD card (internal USB)
• Diskless: Pure network boot (subject of network-boot.md)

Network Connectivity

Integrated FlexibleLOM

The DL360 Gen9 includes a FlexibleLOM slot for swappable network adapters:

Common FlexibleLOM Options:

• HPE 366FLR: 4x 1GbE (Broadcom BCM5719)

  • Most common, good for general use
  • Supports PXE, UEFI network boot, SR-IOV

• HPE 560FLR-SFP+: 2x 10GbE SFP+ (Intel X710)

  • High performance, fiber or DAC
  • Supports PXE, UEFI boot, SR-IOV, RDMA (RoCE)

• HPE 361i: 2x 1GbE (Intel I350)

  • Entry-level, good driver support

PCIe Expansion Slots

Slot Configuration:

• Slot 1: PCIe 3.0 x16 (low-profile)
• Slot 2: PCIe 3.0 x8 (low-profile)
• Slot 3: PCIe 3.0 x8 (low-profile) - optional, depends on riser

Network Card Options:

• Intel X520/X710 (10GbE)
• Mellanox ConnectX-3/ConnectX-4 (10/25/40GbE, InfiniBand)
• Broadcom NetXtreme (1/10/25GbE)

Note: Ensure cards are low-profile for 1U chassis compatibility

Power Supply

PSU Options

• 500W: Single PSU, non-redundant (not recommended)
• 800W: Common, supports dual CPU + moderate expansion
• 1400W: High-power, dual CPU with high TDP + GPUs
• Redundancy: 1+1 redundant hot-plug recommended

Power Configuration

• Platinum Efficiency: 94%+ at 50% load
• Hot-Plug: Replace without powering down
• Auto-Switching: 100-240V AC, 50/60Hz

Home Lab Power Draw (typical):

• Idle (dual E5-2650 v3, 128GB RAM): 100-130W
• Load: 200-350W depending on CPU and drive configuration

Power Management

• HPE Dynamic Power Capping: Limit max power via iLO
• Collaborative Power: Share power budget across chassis in blade environments
• Energy Efficient Ethernet (EEE): Reduce NIC power during low utilization

Cooling and Acoustics

Fan Configuration

• 6x Hot-Plug Fans: Front-mounted, redundant (N+1)
• Variable Speed: Controlled by System ROM based on thermal sensors
• iLO Management: Monitor fan speed, temperature via iLO

Thermal Management

• Temperature Range: 10-35°C (50-95°F) operating
• Altitude: Up to 3,050m (10,000 ft) at reduced temperature
• Airflow: Front-to-back, ensure clear intake and exhaust

Noise Level

• Idle: ~45 dBA (quiet for 1U server)
• Load: 55-70 dBA depending on thermal demand
• Home Lab Consideration: Audible but acceptable in dedicated space; louder than desktop workstation

Noise Reduction:

• Run lower TDP CPUs (e.g., E5-2620 series)
• Maintain ambient temperature <25°C
• Ensure adequate airflow (not in enclosed cabinet without ventilation)

Management - iLO 4

iLO 4 Features

The Integrated Lights-Out 4 (iLO 4) provides out-of-band management:

• Web Interface: HTTPS management console
• Remote Console: HTML5 or Java-based KVM
• Virtual Media: Mount ISOs/images remotely
• Power Control: Power on/off, reset, cold boot
• Monitoring: Sensors, event logs, hardware health
• Alerting: Email alerts, SNMP traps, syslog
• Scripting: RESTful API (Redfish standard)

iLO Licensing

• iLO Standard (included): Basic management, remote console
• iLO Advanced (license required):
  • Virtual media
  • Remote console performance improvements
  • Directory integration (LDAP/AD)
  • Graphical remote console
• iLO Advanced Premium (license required):
  • Insight Remote Support
  • Federation
  • Jitter smoothing

Home Lab: iLO Advanced license highly recommended for virtual media and full remote console features

iLO Network Configuration

• Dedicated iLO Port: Separate 1GbE management port (recommended)
• Shared LOM: Share FlexibleLOM port with OS (not recommended for isolation)

Security: Isolate iLO on dedicated management VLAN, disable if not needed

BIOS and Firmware

System ROM (BIOS/UEFI)

• Firmware Type: UEFI 2.31 or later
• Boot Modes: UEFI, Legacy BIOS, or hybrid
• Configuration: RBSU (ROM-Based Setup Utility) accessible via F9

Firmware Update Methods

1. Service Pack for ProLiant (SPP): Comprehensive bundle of all firmware
2. iLO Online Flash: Update via web interface
3. Online ROM Flash: Linux utility for online updates
4. USB Flash: Boot from USB with firmware update utility

Recommended Practice: Update to latest SPP for security patches and feature improvements

Secure Boot

• UEFI Secure Boot: Supported, validates boot loader signatures
• TPM: Optional Trusted Platform Module 1.2 or 2.0
• Boot Order Protection: Prevent unauthorized boot device changes

Expansion and Modularity

GPU Support

Limited GPU support due to 1U form factor and power constraints:

• Low-Profile GPUs: Nvidia T4, AMD Instinct MI25 (may require custom cooling)
• Power: Consider 1400W PSU for high-power GPUs
• Not Ideal: For GPU-heavy workloads, consider 2U+ servers (e.g., DL380 Gen9)

USB Ports

• Front: 1x USB 3.0
• Rear: 2x USB 3.0
• Internal: 1x USB 2.0 (for SD/USB boot device)

Serial Port

• Rear serial port for legacy console access
• Useful for network equipment serial console, debug

Home Lab Considerations

Pros for Home Lab

1. Density: 1U form factor saves rack space
2. iLO Management: Enterprise remote management without KVM
3. Network Boot: Excellent PXE/UEFI boot support (see network-boot.md)
4. Serviceability: Hot-swap drives, PSU, fans
5. Documentation: Extensive HPE documentation and community support
6. Parts Availability: Common on secondary market, affordable

Cons for Home Lab

1. Noise: Louder than tower servers or workstations
2. Power: Higher idle power than consumer hardware (100-130W idle)
3. 1U Limitations: Limited GPU, PCIe expansion vs 2U/4U chassis
4. Firmware: Requires HPE account for SPP downloads (free but registration required)

Recommended Home Lab Configuration

Budget (~$500-800 used):

• Dual E5-2620 v3 or v4 (6 cores each, 85W TDP)
• 128GB RAM (8x 16GB DDR4)
• 2x SSD (boot), 4-6x HDD/SSD (data)
• HPE 366FLR (4x 1GbE)
• Dual 500W or 800W PSU (redundant)
• iLO Advanced license

Performance (~$1000-1500 used):

• Dual E5-2680 v4 (14 cores each, 120W TDP)
• 256GB RAM (16x 16GB DDR4)
• 2x NVMe SSD (boot/cache), 6-8x SSD (data)
• HPE 560FLR-SFP+ (2x 10GbE) + PCIe 4x1GbE card
• Dual 800W PSU
• iLO Advanced license

Comparison with Other Generations

vs Gen8 (Previous)

Gen9 Advantages:

• DDR4 vs DDR3 (lower power, higher capacity)
• Better UEFI support and HTTP boot
• Newer processor architecture (Haswell/Broadwell vs Sandy Bridge/Ivy Bridge)
• iLO 4 vs iLO 3 (better HTML5 console)

Gen8 Advantages:

• Lower cost on secondary market
• Adequate for light workloads

vs Gen10 (Next)

Gen10 Advantages:

• Newer CPUs (Skylake-SP/Cascade Lake)
• More PCIe lanes
• Better UEFI firmware and security features
• DDR4-2666/2933 support

Gen9 Advantages:

• Lower cost (mature product cycle)
• Excellent value for performance/dollar
• Still well-supported by modern OS and firmware

Technical Resources

• QuickSpecs: HPE ProLiant DL360 Gen9 Server QuickSpecs
• User Guide: HPE ProLiant DL360 Gen9 Server User Guide
• Maintenance and Service Guide: Detailed disassembly and part replacement
• Firmware Downloads: HPE Support Portal (requires free account)

Summary

The HP ProLiant DL360 Gen9 remains an excellent choice for home labs and small deployments in 2024-2025. Its balance of performance (dual Xeon v4, 768GB RAM capacity), manageability (iLO 4), and network boot capabilities make it particularly well-suited for virtualization, container hosting, and infrastructure automation workflows. While not the latest generation, it offers strong value with robust firmware support and wide secondary market availability.

Best For:

• Virtualization hosts (ESXi, Proxmox, Hyper-V)
• Kubernetes/container platforms
• Network boot/diskless deployments
• Storage servers (with appropriate controller)
• General compute workloads

Avoid For:

• GPU-intensive workloads (1U constraints)
• Noise-sensitive environments (unless isolated)
• Extreme low-power requirements (100W+ idle)

3 - Network Boot Capabilities

Overview

The HP ProLiant DL360 Gen9 provides robust network boot capabilities through multiple protocols and firmware interfaces. This makes it particularly well-suited for diskless deployments, automated provisioning, and infrastructure-as-code workflows.

Supported Network Boot Protocols

PXE (Preboot Execution Environment)

The DL360 Gen9 fully supports PXE boot via both legacy BIOS and UEFI firmware modes:

• Legacy BIOS PXE: Traditional PXE implementation using TFTP

  • Protocol: PXEv2 (PXE 2.1)
  • Network Stack: IPv4 only in legacy mode
  • Boot files: pxelinux.0, undionly.kpxe, or custom NBP
  • DHCP options: Standard options 66 (TFTP server) and 67 (boot filename)

• UEFI PXE: Modern UEFI network boot implementation

  • Protocol: PXEv2 with UEFI extensions
  • Network Stack: IPv4 and IPv6 support
  • Boot files: bootx64.efi, grubx64.efi, shimx64.efi
  • Architecture: x64 (EFI BC)
  • DHCP Architecture ID: 0x0007 (EFI BC) or 0x0009 (EFI x86-64)

iPXE Support

The DL360 Gen9 can boot iPXE, enabling advanced features:

• Chainloading: Boot standard PXE, then chainload iPXE for enhanced capabilities
• HTTP/HTTPS Boot: Download kernels and images over HTTP(S) instead of TFTP
• SAN Boot: iSCSI and AoE (ATA over Ethernet) support
• Scripting: Conditional boot logic and dynamic configuration
• Embedded Scripts: iPXE can be compiled with embedded boot scripts

Implementation Methods:

1. Chainload from standard PXE: DHCP points to undionly.kpxe or ipxe.efi
2. Flash iPXE to FlexibleLOM option ROM (advanced, requires care)
3. Boot iPXE from USB, then continue network boot

UEFI HTTP Boot

Native UEFI HTTP boot is supported on Gen9 servers with recent firmware:

• Protocol: RFC 7230 HTTP/1.1
• Requirements:
  • UEFI firmware version 2.40 or later (check via iLO)
  • DHCP option 60 (vendor class identifier) = “HTTPClient”
  • DHCP option 67 pointing to HTTP(S) URL
• Advantages:
  • No TFTP server required
  • Faster transfers than TFTP
  • Support for HTTPS with certificate validation
  • Better suited for large images (kernels, initramfs)
• Limitations:
  • UEFI mode only (not available in legacy BIOS)
  • Requires DHCP server with HTTP URL support

HTTP(S) Boot Configuration

For UEFI HTTP boot on DL360 Gen9:

# Example ISC DHCP configuration for UEFI HTTP boot
class "httpclients" {
    match if substring(option vendor-class-identifier, 0, 10) = "HTTPClient";
}

pool {
    allow members of "httpclients";
    option vendor-class-identifier "HTTPClient";
    # Point to HTTP boot URI
    filename "http://boot.example.com/boot/efi/bootx64.efi";
}

Network Interface Options

The DL360 Gen9 supports multiple network adapter configurations for boot:

FlexibleLOM (LOM = LAN on Motherboard)

HPE FlexibleLOM slot supports:

• HPE 366FLR: Quad-port 1GbE (Broadcom BCM5719)
• HPE 560FLR-SFP+: Dual-port 10GbE (Intel X710)
• HPE 361i: Dual-port 1GbE (Intel I350)

All FlexibleLOM adapters support PXE and UEFI network boot. The option ROM can be configured via BIOS/UEFI settings.

PCIe Network Adapters

Standard PCIe network cards with PXE/UEFI boot ROM support:

• Intel X520, X710 series (10GbE)
• Broadcom NetXtreme series
• Mellanox ConnectX-3/4 (with appropriate firmware)

Boot Priority: Configure via System ROM > Network Boot Options to select which NIC boots first.

Firmware Configuration

Accessing Boot Configuration

1. RBSU (ROM-Based Setup Utility): Press F9 during POST
2. iLO 4 Remote Console: Access via network, then virtual F9
3. UEFI System Utilities: Modern interface for UEFI firmware settings

Key Settings

Navigate to: System Configuration > BIOS/Platform Configuration (RBSU) > Network Boot Options

• Network Boot: Enable/Disable
• Boot Mode: UEFI or Legacy BIOS
• IPv4/IPv6: Enable protocol support
• Boot Retry: Number of attempts before falling back to next boot device
• Boot Order: Prioritize network boot in boot sequence

Per-NIC Configuration

In RBSU > Network Options:

• Option ROM: Enable/Disable per adapter
• Link Speed: Force speed/duplex or auto-negotiate
• VLAN: VLAN tagging for boot (if supported by DHCP/PXE environment)
• PXE Menu: Enable interactive PXE menu (Ctrl+S during PXE boot)

iLO 4 Integration

The DL360 Gen9’s iLO 4 provides additional network boot features:

Virtual Media Network Boot

• Mount ISO images remotely via iLO Virtual Media
• Boot from network-attached ISO without physical media
• Useful for OS installation or diagnostics

Workflow:

1. Upload ISO to HTTP/HTTPS server or use SMB/NFS share
2. iLO Remote Console > Virtual Devices > Image File CD-ROM/DVD
3. Set boot order to prioritize virtual optical drive
4. Reboot server

Scripted Deployment via iLO

iLO 4 RESTful API allows:

• Setting one-time boot to network via API call
• Automating PXE boot for provisioning pipelines
• Integration with tools like Terraform, Ansible

Example using iLO RESTful API:

curl -k -u admin:password -X PATCH \
  https://ilo-hostname/redfish/v1/Systems/1/ \
  -d '{"Boot":{"BootSourceOverrideTarget":"Pxe","BootSourceOverrideEnabled":"Once"}}'

Boot Process Flow

Legacy BIOS PXE Boot

1. Server powers on, initializes NICs
2. NIC sends DHCPDISCOVER with PXE vendor options
3. DHCP server responds with IP, TFTP server (option 66), boot file (option 67)
4. NIC downloads NBP (Network Bootstrap Program) via TFTP
5. NBP executes (e.g., pxelinux.0 loads syslinux menu)
6. User selects boot target or automated script continues
7. Kernel and initramfs download and boot

UEFI PXE Boot

1. UEFI firmware initializes network stack
2. UEFI PXE driver sends DHCPv4/v6 DISCOVER
3. DHCP responds with boot file (e.g., bootx64.efi)
4. UEFI downloads boot file via TFTP
5. UEFI loads and executes boot loader (GRUB2, systemd-boot, iPXE)
6. Boot loader may download additional files (kernel, initrd, config)
7. OS boots

UEFI HTTP Boot

1. UEFI firmware with HTTP Boot support enabled
2. DHCP request includes “HTTPClient” vendor class
3. DHCP responds with HTTP(S) URL in option 67
4. UEFI HTTP client downloads boot file over HTTP(S)
5. Execution continues as with UEFI PXE

Performance Considerations

TFTP vs HTTP

• TFTP: Slow for large files (typical: 1-5 MB/s)
  • Use for small boot loaders only
  • Chainload to iPXE or HTTP boot for better performance
• HTTP: 10-100x faster depending on network and server
  • Recommended for kernels, initramfs, live OS images
  • iPXE or UEFI HTTP boot required

Network Speed Impact

DL360 Gen9 boot performance by NIC speed:

• 1GbE: Adequate for most PXE deployments (100-125 MB/s theoretical max)
• 10GbE: Significant improvement for large image downloads (1-2 GB/s)
• Bonding/Teaming: Not typically used for boot (single NIC boots)

Recommendation: For production diskless nodes or frequent re-provisioning, 10GbE with HTTP boot provides best performance.

Common Use Cases

1. Automated OS Provisioning

Boot into installer via PXE:

• Kickstart (RHEL/CentOS/Rocky)
• Preseed (Debian/Ubuntu)
• Ignition (Fedora CoreOS, Flatcar)

2. Diskless Boot

Boot OS entirely from network/RAM:

• Network root: NFS or iSCSI root filesystem
• Overlay: Persistent storage via network overlay
• Stateless: Boot identical image, no local state

3. Rescue and Diagnostics

Boot live environments:

• SystemRescue
• Clonezilla
• Memtest86+
• Hardware diagnostics (HPE Service Pack for ProLiant)

4. Kubernetes/Container Hosts

PXE boot immutable OS images:

• Talos Linux: API-driven, diskless k8s nodes
• Flatcar Container Linux: Automated updates
• k3OS: Lightweight k8s OS

Troubleshooting

PXE Boot Fails

Symptoms: “PXE-E51: No DHCP or proxy DHCP offers received” or timeout

Checks:

1. Verify NIC link light and switch port status
2. Confirm DHCP server is responding (check DHCP logs)
3. Ensure DHCP options 66 and 67 are set correctly
4. Test TFTP server accessibility (tftp -i <server> GET <file>)
5. Check BIOS/UEFI network boot is enabled
6. Verify boot order prioritizes network boot
7. Disable Secure Boot if using unsigned boot files

UEFI Network Boot Not Available

Symptoms: Network boot option missing in UEFI boot menu

Resolution:

1. Enter RBSU (F9), navigate to Network Options
2. Ensure at least one NIC has “Option ROM” enabled
3. Verify Boot Mode is set to UEFI (not Legacy)
4. Update System ROM to latest version if option is missing
5. Some FlexibleLOM cards require firmware update for UEFI boot support

HTTP Boot Fails

Symptoms: UEFI HTTP boot option present but fails to download

Checks:

1. Verify firmware version supports HTTP boot (>=2.40)
2. Ensure DHCP option 67 contains valid HTTP(S) URL
3. Test URL accessibility from another client
4. Check DNS resolution if using hostname in URL
5. For HTTPS: Verify certificate is trusted (or disable cert validation in test)

Slow PXE Boot

Symptoms: Boot process takes minutes instead of seconds

Optimizations:

1. Switch from TFTP to HTTP (chainload iPXE or use UEFI HTTP boot)
2. Increase TFTP server block size (tftp-hpa --blocksize 1468)
3. Tune DHCP response times (reduce lease query delays)
4. Use local network segment for boot server (avoid WAN/VPN)
5. Enable NIC interrupt coalescing in BIOS for 10GbE

Security Considerations

Secure Boot

DL360 Gen9 supports UEFI Secure Boot:

• Validates signed boot loaders (shim, GRUB, kernel)
• Prevents unsigned code execution during boot
• Required for some compliance scenarios

Configuration: RBSU > Boot Options > Secure Boot = Enabled

Implications for Network Boot:

• Must use signed boot loaders (e.g., shim.efi signed by Microsoft/vendor)
• Custom kernels require signing or disabling Secure Boot
• iPXE must be signed or chainloaded from signed shim

Network Security

Risks:

• PXE/TFTP is unencrypted and unauthenticated
• Attacker on network can serve malicious boot images
• DHCP spoofing can redirect to malicious boot server

Mitigations:

1. Network Segmentation: Isolate PXE boot to management VLAN
2. DHCP Snooping: Prevent rogue DHCP servers on switch
3. HTTPS Boot: Use UEFI HTTP boot with TLS and certificate validation
4. iPXE with HTTPS: Chainload iPXE, then use HTTPS for all downloads
5. Signed Images: Use Secure Boot with signed boot chain
6. 802.1X: Require network authentication before DHCP (complex for PXE)

iLO Security

• Change default iLO password immediately
• Use TLS for iLO web interface and API
• Restrict iLO network access (firewall, separate VLAN)
• Disable iLO Virtual Media if not needed
• Enable iLO Security Override for extra security during boot

Firmware and Driver Resources

Required Firmware Versions

For optimal network boot support:

• System ROM: v2.60 or later (latest recommended)
• iLO 4 Firmware: v2.80 or later
• NIC Firmware: Latest for specific FlexibleLOM/PCIe card

Check current versions: iLO web interface > Information > Firmware Information

Updating Firmware

Methods:

1. HPE Service Pack for ProLiant (SPP): Comprehensive update bundle

   • Boot from SPP ISO (via iLO Virtual Media or USB)
   • Runs Smart Update Manager (SUM) in Linux environment
   • Updates all firmware, drivers, system ROM automatically

2. iLO Web Interface: Individual component updates

   • System ROM: Administration > Firmware > Update Firmware
   • Upload .fwpkg or .bin files from HPE support site

3. Online Flash Component: Linux Online ROM Flash utility

   • Install hp-firmware-* packages
   • Run updates while OS is running (requires reboot to apply)

Download Source: https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1010026910 (requires HPE Passport account, free registration)

Best Practices

1. Use UEFI Mode: Better security, IPv6 support, larger disk support
2. Enable HTTP Boot: Faster and more reliable than TFTP for large files
3. Chainload iPXE: Flexibility of iPXE with standard PXE infrastructure
4. Update Firmware: Keep System ROM and iLO current for bug fixes and features
5. Isolate Boot Network: Use dedicated management VLAN for PXE/provisioning
6. Test Failover: Configure multiple DHCP servers and boot mirrors for redundancy
7. Document Configuration: Record BIOS settings, DHCP config, and boot infrastructure
8. Monitor iLO Logs: Track boot failures and hardware issues via iLO event log

References

• HPE ProLiant DL360 Gen9 Server User Guide
• HPE UEFI System Utilities User Guide
• iLO 4 User Guide (firmware version 2.80)
• Intel PXE Specification v2.1
• UEFI Specification v2.8 (HTTP Boot)
• iPXE Documentation: https://ipxe.org/

Conclusion

The HP ProLiant DL360 Gen9 provides enterprise-grade network boot capabilities suitable for both traditional PXE deployments and modern UEFI HTTP boot scenarios. Its flexible configuration options, mature firmware support, and iLO integration make it an excellent platform for automated provisioning, diskless computing, and infrastructure-as-code workflows in home lab environments.

For home lab use, the recommended configuration is:

• UEFI boot mode with Secure Boot disabled (unless required)
• iPXE chainloading for flexibility and HTTP performance
• iLO 4 configured for remote management and scripted provisioning
• Latest firmware for stability and feature support