HPE0-S59 Install, Configure, and Set Up, HPE Server Solutions

Install, Configure, and Set Up, HPE Server Solutions Detailed Explanation

1. Physical Installation and Cabling

Before any software is installed, you need to make sure the hardware is physically installed correctly, cabled properly, and the environment is ready for operation.

1.1 Rack and Stack

“Rack and Stack” means physically mounting the server hardware in a rack.

Here’s what you need to check and do:

• Verify Rack Compatibility

  • Check the rack’s depth — some servers are deeper and won’t fit in all racks.

  • Ensure there’s enough vertical space (measured in “U” units; 1U = 1.75 inches).

  • Make sure your power and cooling setup matches server requirements.

• Install Rail Kits

  • Servers slide into racks using rails, which must match the specific server model.

  • Use manufacturer-provided rails (HPE rails for HPE servers).

  • Always install rails level and firmly secured.

• Secure Grounding

  • Prevent electrical hazards by grounding the rack according to site standards.

  • This protects against electrostatic discharge (ESD).

• Weight Distribution

  • Place heavier servers at the bottom to prevent tipping.

  • Plan for airflow from front to back (most racks are designed this way).

1.2 Power and Cabling

This step ensures the server can power up and connect to other systems correctly.

• Redundant Power Supplies

  • Most enterprise servers have two power supplies (PSUs).

  • Each PSU should connect to a different PDU (Power Distribution Unit) to prevent a single point of failure.

• Cable Management

  • Use color-coded cables for power, management, and data lines.

  • Label each cable at both ends.

  • Bundle cables neatly using Velcro or cable trays (avoid zip ties, which can damage cables).

• Network Uplinks

  • Connect the correct NICs (network ports) to the right switches.

    • Example: Connect iLO port to management network, and main NICs to production switches.

  • Double-check VLAN and switch port configurations if needed.

1.3 Environmental Readiness

Before powering on the system, check if the environment supports stable operation.

• Temperature and Humidity

  • Follow ASHRAE standards:

    • Typical temp: 18°C–27°C (64°F–80°F)

    • Relative humidity: 40%–60%

  • Too much heat = risk of thermal shutdown. Too little humidity = static buildup.

• Airflow Direction

  • Make sure the rack and servers are aligned front-to-back (cold air in the front, hot air out the back).

  • Avoid placing equipment that reverses airflow in the same rack.

• Power Capacity

  • Calculate total wattage per rack.

  • Avoid overloading circuits; know how many amps are available.

  • Check for UPS (uninterruptible power supply) to protect from outages.

2. Initial Power-On and Firmware Update

Once the server is physically installed, connected, and powered, the next step is to verify hardware health, then bring the system up to date with the latest firmware and BIOS updates. This ensures stability, security, and compatibility before any OS is installed.

2.1 Power-On Process

Monitor POST (Power-On Self-Test)

• When the server is first powered on, it runs POST to check:

  • Memory

  • CPU

  • Drives

  • Power supplies

  • Fans

• Watch for:

  • Audible beeps (error codes)

  • Messages on the local or remote console

  • Diagnostic LEDs (green = good, amber/red = error)

Check for Hardware Health Indicators

• Use the front panel LED status lights on HPE ProLiant servers:

  • Green = normal

  • Amber = warning

  • Red = failure

• Also check the System Information Display Panel (if present) for temperature, power, and hardware status.

Access iLO for Remote Management

• Find the default iLO IP (either printed on a label or from DHCP).

• Connect via browser (HTTPS) or SSH.

• Login using default credentials (then change them immediately).

• iLO gives access to:

  • Remote console

  • Power on/off/reset

  • Firmware updates

  • System event logs

2.2 Firmware and BIOS/UEFI Updates

HPE servers ship with working firmware, but it may be outdated. Always update to the latest stable versions before installing the OS.

Use Intelligent Provisioning

• Built into most HPE ProLiant servers.

• Access it by pressing F10 at boot.

• It can:

  • Update firmware

  • Configure RAID

  • Install the operating system

Use Service Pack for ProLiant (SPP)

• A downloadable ISO from HPE.

• Contains tested firmware and driver versions for all components.

• Boot into it via:

  • USB

  • Virtual media over iLO

• Use this method if the system isn’t connected to the internet.

Update the Following Components:

• BIOS/UEFI

  • Controls system startup and hardware-level settings.

• iLO Firmware

  • Keeps management features secure and stable.

• Smart Array Controller

  • Handles RAID and disk configuration.

• NICs, Drives, and PCIe Cards

  • Update network cards, SSD/HDD firmware, and GPUs if present.

Other Firmware Tools:

• HPE SUM (Smart Update Manager)

  • GUI-based tool for updating multiple servers.

  • Good for bulk updates.

• iLO Amplifier Pack

  • Designed for updating firmware on many servers at once (fleet-wide updates).

• HPE OneView

  • Can enforce firmware compliance based on templates.

  • Especially useful in Synergy and managed ProLiant environments.

Best Practices:

Task	Why It Matters
Update firmware before OS	Prevents future bugs and improves stability
Use validated SPP bundles	Ensures compatibility with OS and drivers
Document all versions	Helps with support cases and audits
Verify success	Reboot and recheck firmware versions after update

3. Server Configuration

After initial power-on and firmware updates, you’ll configure the server's internal settings — including the BIOS, RAID, and iLO. This prepares the system for the operating system and ensures it runs reliably in the customer’s environment.

3.1 BIOS and Boot Configuration

The BIOS/UEFI (Basic Input Output System / Unified Extensible Firmware Interface) is the first software that runs when a server starts. It controls low-level hardware settings.

Key Tasks:

• Enable/Disable Virtualization Features

  • Intel VT-x or AMD-V must be enabled if the server will host virtual machines.

  • Also enable VT-d (Intel) or AMD IOMMU for device passthrough (needed for GPU, storage acceleration).

• Set Boot Order

  • Define which device the server tries to boot from:

    1. USB (for temporary installs)

    2. PXE (for network installs)

    3. Local Disk (for normal operation)

  • Reorder as needed depending on deployment method.

• Enable Secure Boot

  • Ensures that only digitally signed OS and drivers can load.

  • Recommended for security-focused environments.

• Enable TPM (Trusted Platform Module)

  • A hardware chip used for encryption and identity protection.

  • Required for Windows Server BitLocker, UEFI Secure Boot, and some compliance frameworks.

3.2 RAID Configuration

RAID (Redundant Array of Independent Disks) improves performance and/or data protection by combining multiple drives.

Configuration Tools:

• HPE Smart Array Configuration Utility (ACU) – UEFI-based.

• HPE Smart Storage Administrator (SSA) – Graphical interface accessible via Intelligent Provisioning or boot media.

Common RAID Levels:

RAID Level	Description	Min Drives	Benefits	Notes
RAID 0	Striping only	2	High performance	No redundancy
RAID 1	Mirroring	2	Redundancy	Only 50% usable capacity
RAID 5	Striping + parity	3	Balanced performance & protection	Slow rebuild time
RAID 6	Striping + dual parity	4	Can survive 2 disk failures	Lower write performance
RAID 10	Mirroring + striping	4	High performance and fault tolerance	Recommended for critical workloads

Configuration Options:

• Stripe Size: Affects performance (large = better for big files, small = better for small files).

• Caching Policies:

  • Write-back: Faster, but risky without battery backup.

  • Write-through: Safer but slower.

3.3 iLO Setup

iLO (Integrated Lights-Out) provides remote management access to the server — even if the server is powered off.

Configuration Tasks:

• Assign a Static IP Address

  • You can use DHCP at first, but a static IP is better for permanent management.

  • This makes it easier to script updates or access remotely.

• Create iLO User Accounts

  • Set up individual users with roles:

    • Administrator: Full access

    • Operator: Can power on/off but not configure settings

    • Viewer: Read-only access

• Configure Notifications and Alerts

  • Enable email alerts for hardware faults.

  • Configure SNMP traps for integration with monitoring tools (like Zabbix, SolarWinds).

  • Connect to LDAP or Active Directory for centralized user management.

Tip: Always change the default password for iLO to prevent unauthorized access.

Best Practices Recap:

Task	Tip
BIOS boot config	Set USB or PXE first for installation, then switch to disk
RAID level choice	Choose based on performance vs. protection
iLO network setup	Use a dedicated management VLAN if possible
iLO accounts	Follow least privilege — only give full access when needed

4. Operating System Installation

Once the server hardware is configured (BIOS, RAID, iLO), the next step is to install the operating system (OS). HPE provides powerful tools to simplify this, including built-in methods and support for automation.

4.1 Intelligent Provisioning

What is Intelligent Provisioning?

• A built-in feature in most HPE ProLiant Gen9 and Gen10+ servers.

• You access it by pressing F10 during POST.

• It provides a graphical wizard to help with:

  • OS installation

  • RAID configuration

  • Driver injection

  • System updates

Key Features

• OS Installation Wizard:

  • Supports Windows Server, Red Hat/CentOS, SUSE, VMware ESXi, etc.

  • Provides a guided interface to simplify installation.

• Driver Integration:

  • Automatically installs drivers for NICs, storage, and other devices.

  • Reduces the chance of “missing drivers” during install.

• RAID Configuration Access:

  • You can configure Smart Array controllers from within the same tool.

• Unattended Install:

  • You can create a silent install template (answer file) to speed up multi-server setups.

Best For: Beginners or quick single-server deployments without PXE setup.

4.2 Manual or Scripted OS Deployment

For large-scale or automated deployments, use network-based installation or automated scripts.

PXE Boot with WDS, MDT, or 3rd-Party Tools

• PXE = Preboot Execution Environment

• Boots over the network using DHCP + TFTP

• Tools:

  • WDS (Windows Deployment Services): Windows-only.

  • MDT (Microsoft Deployment Toolkit): Adds automation and driver packs.

  • Linux Kickstart: For automated Red Hat/CentOS installs.

  • unattend.xml: Automates Windows Server installs.

Virtual Media via iLO

• You can mount an ISO file remotely via iLO.

• iLO presents the ISO as a virtual CD/DVD drive.

• Ideal for:

  • Remote installs when PXE is unavailable.

  • Booting into ISO-based tools like SPP or custom images.

Best For: Remote installs or automated deployments.

4.3 Post-Installation Configuration

After the OS is installed, some final setup tasks are needed to ensure the system is secure, fast, and monitorable.

Install Latest OS Patches

• Use:

  • Windows Update (for Windows Server)

  • yum/dnf/apt (for Linux distros)

• Patch both the OS and any additional software (e.g., Hyper-V role).

Configure NIC Teaming or Bonding

• NIC Teaming (Windows) or Bonding (Linux):

  • Combines two or more NICs for:

    • Failover protection

    • Load balancing

• Set teaming mode to LACP or Static depending on switch setup.

Install HPE Management Agents

• AMS (Agentless Management Service):

  • Provides OS-level info to iLO (CPU usage, memory, processes).

• WBEM Providers / SNMP Agents:

  • Used by HPE Insight, OneView, and monitoring tools.

• Helps with:

  • Proactive support

  • Logging

  • Integration with tools like HPE InfoSight

Post-Install Checklist:

Task	Purpose
OS patches	Fix security holes and stability issues
NIC teaming	Increases availability and bandwidth
Management agents	Enable monitoring and remote support
Time and NTP configuration	Ensure correct logging and scheduling
Domain join (if needed)	Centralized authentication and policies

5. HPE OneView and Template Deployment

HPE OneView is a powerful management tool that automates and simplifies server provisioning, configuration, and monitoring. In this section, you'll learn how to deploy OneView, use Server Profile Templates, and — in Synergy environments — apply Image Streamer to create fast, repeatable infrastructure.

5.1 HPE OneView Installation (Appliance)

What Is OneView?

• OneView is a virtual appliance — a management server that you deploy as a VM.

• It provides centralized management for:

  • HPE ProLiant (Gen9/Gen10/Gen11)

  • HPE Synergy

  • Storage and networking components

• Accessed via a web interface or REST API.

Deployment Steps:

1. Download the Appliance:

   • Available in formats for VMware ESXi, Hyper-V, or KVM.

2. Deploy the VM:

   • Allocate appropriate resources (usually 2 vCPU, 16 GB RAM, 270+ GB disk).

3. Configure Initial Settings:

   • Set:

     • Static IP address

     • Hostname

     • Administrator credentials

4. Configure RBAC (Role-Based Access Control):

   • Create users and assign roles (e.g., Server Admin, Storage Admin, Operator).

   • Integrate with LDAP/Active Directory for enterprise login.

5. Add Managed Resources:

   • Discover and add:

     • HPE servers via iLO

     • Storage (Nimble, Primera)

     • Networks (Virtual Connect)

5.2 Server Profile Templates

What Are Server Profiles?

• A server profile is like a blueprint for a server.

• It contains:

  • BIOS settings

  • Firmware version

  • Boot order

  • Storage layout

  • Network configuration (VLANs, MAC addresses)

• You apply this profile to a physical server, and OneView automatically configures everything.

Benefits:

• Consistency: Every server gets the same setup — reduces human error.

• Speed: Provisioning takes minutes, not hours.

• Compliance: All servers stay on the approved firmware and settings.

Typical Steps:

1. Create a Server Profile Template

   • Define:

     • Server hardware type (e.g., DL380 Gen10)

     • Firmware baseline

     • BIOS settings (secure boot, hyperthreading, virtualization)

     • Storage: RAID config or SAN boot

     • Network: VLANs, FlexNICs

2. Apply the Template to a Target Server

   • OneView configures:

     • iLO settings

     • Firmware updates

     • Boot and RAID config

     • Network settings

   • The server is ready to deploy an OS.

3. Monitor and Enforce

   • OneView can detect if a server drifts from the template and trigger remediation.

5.3 Image Streamer (for HPE Synergy)

What Is Image Streamer?

• A specialized appliance used with HPE Synergy to enable stateless computing.

• Instead of installing the OS permanently, it streams a golden OS image over the network into memory.

Benefits:

• Instant Deployment: New servers boot in seconds with the desired OS and config.

• Stateless Infrastructure: No OS or config is stored locally — everything is from the template.

• DevOps-Ready: Integrates with tools like Ansible, Terraform, Jenkins.

Typical Use Case:

1. Create a Golden Image (OS + settings).

2. Store it in Image Streamer.

3. Apply it to a compute module via OneView.

4. The server boots directly from the image into a running OS — no need for PXE or local storage.

Best For:

• Rapid Dev/Test environments

• CI/CD pipelines

• Large-scale cloud infrastructure

Best Practices Recap:

Task	Why It Matters
Use templates in OneView	Standardize server builds and eliminate manual errors
Set firmware baselines	Avoid inconsistent hardware behavior
Integrate with LDAP	Centralized authentication and easier access control
Use Image Streamer (Synergy)	Speed up deployment and enable stateless architecture

6. Validation and Handoff

After installation and configuration, it’s crucial to ensure everything is working properly, documented, and ready for the operations team or customer to take over.

6.1 Hardware Validation

Before handing off the system, verify that all hardware and configurations are functioning as expected.

Use Insight Diagnostics or iLO Health Reports

• Insight Diagnostics (available in Intelligent Provisioning):

  • Tests:

    • CPU health

    • Memory integrity

    • Storage performance

    • System board checks

  • Run these tests after installation or when problems are suspected.

• iLO System Health Dashboard:

  • Accessible via iLO web interface.

  • Shows:

    • Power supply status

    • Temperature sensors

    • Drive health

    • Fan operation

  • Alerts are color-coded (green = OK, amber = warning, red = critical).

Tip: For HPE InfoSight-enabled systems (Gen10+), server telemetry can also be uploaded for deeper cloud-based analytics.

6.2 Document Configuration

Proper documentation ensures future support, maintenance, and troubleshooting are easier.

What to Capture:

• Firmware Versions:

  • BIOS/UEFI, iLO, RAID controller, NICs

• RAID and Disk Layout:

  • RAID level (e.g., RAID 10)

  • Drive types and sizes

  • Logical volume structure

• Network Settings:

  • IP addresses

  • Subnets, gateways

  • VLAN IDs

  • NIC teaming/bonding config

Format and Share:

• Use PDF or export from OneView/iLO.

• Include screenshots for visual confirmation.

• Store in a central documentation system (e.g., Confluence, SharePoint).

6.3 Backup Configuration Profiles

To prepare for future disaster recovery or scaling, export the server's configuration settings.

Backup Methods:

• iLO Scripting Toolkit or RESTful API:

  • Export settings like:

    • BIOS config

    • iLO user accounts

    • Boot order

• OneView Profile Export:

  • Back up entire Server Profiles (including firmware baseline, network/storage config).

  • Can be imported into a new server to replicate setup.

Benefits:

• Faster hardware replacement

• Easier cloning of servers

• Documentation for audits and change control

Tip: Store backups in a secure location, with access limited to authorized personnel only.

Summary

Step	Skill Acquired
Rack and connect servers	Physical setup, cabling, power, environment checks
Power up and update firmware	POST monitoring, BIOS/iLO updates
Configure BIOS, RAID, iLO	Setup for performance, security, remote access
Install the OS	Use Intelligent Provisioning, PXE, or scripting
Deploy with OneView templates	Use automation and consistency for rapid rollout
Validate and document the system	Ensure readiness for operations and future scaling

Install, Configure, and Set Up, HPE Server Solutions (Additional Content)

Common Deployment Mistakes and Troubleshooting Recommendations

Deploying HPE servers reliably requires precision across hardware setup, firmware configuration, and network services. The following are frequent setup mistakes, their symptoms, root causes, and troubleshooting strategies — all aligned with real-world HPE ProLiant deployment experience.

1. Incorrect RAID Configuration Prevents OS Installation

Symptoms:

• OS installer does not detect any drives

• Installer crashes or displays “no disk found” or “unsupported disk controller”

Cause:

• RAID not properly created in HPE SSA (Smart Storage Administrator)

• Controller mode (RAID vs HBA) is incorrectly set

• Driver for Smart Array Controller missing during OS install

How to Fix:

• Reboot and access Intelligent Provisioning (F10) → Launch SSA

• Verify:

  • Logical drive created?

  • RAID level chosen matches disk count (e.g., RAID 5 needs ≥3 disks)

  • Drive status is "OK"

• If OS install is manual, inject controller driver during install (especially for VMware or Linux)

Prevention:

• Always configure RAID before OS install

• Use HPE SPP ISO or Intelligent Provisioning to auto-load drivers

2. iLO IP Set to DHCP – Batch Deployment Breaks

Symptoms:

• Cannot reach iLO for some nodes during mass setup

• iLO addresses change unexpectedly after reboot or power loss

Cause:

• iLO IP assigned by DHCP, not static

• DHCP lease expires or server moves to a different subnet

How to Fix:

• Connect locally or via console cable

• Enter iLO setup (during POST → press F8 for iLO config)

• Assign static IP, subnet mask, gateway manually

Prevention:

• For all production servers, disable DHCP for iLO

• Maintain an iLO IP plan — document IP/MAC/hostname per server

• Optionally, configure DNS hostnames to match iLO addresses

3. Incorrect BIOS Boot Order Blocks PXE or ISO Boot

Symptoms:

• Cannot boot from USB, ISO, or PXE network

• Server boots into "No boot device" or attempts booting to disk too early

Cause:

• Boot order in BIOS/UEFI does not include:

  • USB device

  • PXE NIC

  • Virtual CD-ROM (from iLO)

How to Fix:

• During POST, press F9 to enter BIOS/UEFI setup

• Go to Boot Options:

  • Enable required boot device types (USB, Network)

  • Set correct boot order priority

Prevention:

• When scripting deployments, use OneView templates or iLO REST API to pre-configure boot settings

• After ISO or PXE boot, remember to reset boot order to boot from disk

4. PXE Boot Fails – TFTP Configuration Missing or Broken

Symptoms:

• PXE boot starts, then hangs at “TFTP open timeout” or “File not found”

• Client displays “PXE-E32: TFTP Open Timeout” or “PXE-M0F: Exiting PXE ROM”

Cause:

• PXE server (e.g., WDS, MDT, Kickstart, or custom TFTP server) not properly configured

• Missing or misnamed boot file (e.g., pxelinux.0, bootx64.efi, boot.wim)

• Firewall blocks UDP port 69 (used for TFTP)

How to Fix:

• Check that TFTP service is running

• Confirm boot filename matches architecture (UEFI vs BIOS)

• Use tools like TFTPD32 or Wireshark to trace traffic

• Verify DHCP options 66 (Server) and 67 (Boot file) are correct

Prevention:

• Create golden PXE templates per OS

• Store TFTP configs in version control

• Keep PXE and DHCP server roles logically separated

5. Missing OS Drivers – Installation Fails Midway

Symptoms:

• OS installer starts but fails with “no NIC detected” or “disk controller missing”

• VMware ESXi install halts due to unsupported NIC

Cause:

• OS lacks native drivers for HPE-specific hardware

  • Smart Array controller

  • iLO chipset

  • HPE FlexibleLOMs (custom NICs)

How to Fix:

• Download driver packs from HPE support portal

• Use HPE Custom ISO (available for ESXi, Windows, RHEL, etc.)

• For unattended installs, inject drivers into boot.wim/initrd.img

Prevention:

• Always use HPE-supported media

• Keep drivers updated alongside firmware via SPP

6. Unattended Deployment Fails – Template Errors or Media Issues

Symptoms:

• Kickstart/preseed/unattend.xml is ignored or crashes

• Server boots to PXE or ISO but doesn’t auto-install

Cause:

• Template file missing, misformatted, or not found

• Virtual media or PXE file not properly mounted

How to Fix:

• Re-check unattended file syntax:

  • ks.cfg, autoinst.xml, unattend.xml

• Use iLO Virtual Media to mount ISO + answer file together

• Test booting manually with logs enabled (e.g., vmlinuz init=/bin/sh for Linux)

Prevention:

• Validate template with 1–2 test servers before scaling

• Keep installation scripts and files under version control

Summary: Common Deployment Issues and Fixes

Issue	Root Cause	Fix
OS won’t see disks	RAID not configured, wrong controller mode	Use SSA to create logical volumes
iLO unreachable	DHCP used, IP changes	Set static iLO IP in POST
Can’t PXE boot	BIOS boot order wrong	Enter BIOS, fix boot sequence
PXE fails mid-boot	TFTP or DHCP misconfigured	Verify boot file, firewall, options 66/67
OS install fails	Drivers missing	Use HPE Custom ISO or inject manually
Unattended install broken	Template invalid	Validate syntax, mount correctly