HP SET cheat sheet
HP SET · Keep the key ideas within reach.
Enterprise Portfolio and Positioning
HPE portfolio tiers: ProLiant DL/ML/BL for rack, tower, blade; Synergy for composable; Apollo for HPC and AI; Superdome Flex for scale-up mission-critical.
Positioning rule: match customer workload profile (virtualization density, latency sensitivity, scale-out vs scale-up) to platform family before sizing SKUs.
HPE GreenLake is the consumption layer across the portfolio; it does not replace the product family, it changes the buying model (OpEx, metered, HPE-managed).
Compute market share context: HPE is a top-two global x86 server vendor by units and revenue; differentiation rests on silicon root of trust, iLO, and GreenLake.
Portfolio adjacency: Aruba (networking), Primera/Nimble/MSA (storage), StoreOnce (data protection), Pointnext (services) - bundle for full-stack deals.
Edge-to-cloud narrative maps to three tiers: edge (ProLiant DL20/DL3xx, Aruba), core data center (Synergy, Primera), cloud (GreenLake, Ezmeral).
Competitive frame: Dell (breadth, direct model), Lenovo (price), Cisco (UCS + networking lock-in), Supermicro (white-box cost); HPE counters on security, services, and consumption.
Deal qualification: confirm workload, growth forecast, refresh timeline, and whether customer wants CapEx purchase, lease, or metered consumption.
Servers and Compute (ProLiant, Synergy, Apollo)
ProLiant Gen11 naming: DL = rack, ML = tower, BL = blade; first digit indicates series (1xx entry, 3xx mainstream,5xx/6xx scale-up), second digit generation.
HPE iLO 6 (Gen11) provides out-of-band management, Redfish API, and iLO Advanced/Advanced Security license tiers.
HPE Silicon Root of Trust anchors firmware to an immutable fingerprint in silicon; verifies boot chain and enables iLO Advanced Security recovery.
Synergy composability: frame (1200/600/500) + compute module + interconnect link module + storage module; profiles are applied via HPE OneView.
Synergy value case: reduce cabling and over-provisioning, deploy profiles in minutes, and converge HPE ProLiant, BladeSystem, and storage management under OneView.
Apollo families: Apollo 2000/4000/6500 for dense HPC; Apollo 6500 Gen10 Plus supports up to 8 double-wide GPUs for AI training/inference.
Sizing rule: for virtualization, estimate vCPU per core with overcommit ratio, then RAM (usually the binding constraint), then local vs SAN storage, then NIC bandwidth.
HPE Compute Ops Management is the cloud-native management console for ProLiant/Apollo fleets; complements on-prem OneView.
Storage and Data Services (Primera, Nimble, MSA, StoreOnce)
Primera: mission-critical all-NVMe, 100% availability guarantee, Peer Persistence for stretched clusters, InfoSight/AIOps telemetry.
Primera A630/A650/A670 tiers differ in controller count and scalability; A670 scales to 8 controllers in a cluster for scale-out performance.
Nimble Storage: hybrid or all-flash (AF) arrays with InfoSight predictive analytics, triple-parity RAID, and integrated replication for SMB/midmarket.
Nimble dHCI combines Nimble storage with ProLiant compute under one management plane for simplified virtualization.
MSA: entry-level SAN (MSA 2060/2062/2070/2072) with dual controllers, FC/iSCSI, and snapshots; targets small business and remote offices.
StoreOnce: deduplicating backup appliance (single-node and multi-node), Catalyst protocol integration with backup software, and Cloud Bank for tiering to object storage.
StoreOnce federated dedupe and replication reduce WAN bandwidth; Recovery Manager Central (RMC) integrates snapshots with backup workflows.
RPO/RTO mapping: synchronous replication (Peer Persistence, zero RPO) for tier-1; async replication for regional DR; snapshots for operational recovery.
Networking and Aruba Fabric/Switching
Aruba CX switching runs AOS-CX with a REST API and the Network Analytics Engine (NAE) for automated troubleshooting.
Aruba CX 6300/6400 stack with VSF (Virtual Switching Framework); CX 8320/8360/8400 form the data center core/leaf.
Aruba Fabric Composer orchestrates EVPN-VXLAN fabrics and integrates with VMware NSX and HPE compute/storage for a unified data center.
Aruba Central is the cloud management plane for wired, wireless, and SD-WAN; Aruba ClearPass handles NAC and policy.
EVPN-VXLAN is the modern leaf-spine overlay; VXLAN provides Layer 2 extension over Layer 3 underlay with BGP EVPN control plane.
AOS-CX VSX (Virtual Switching Extension) provides active-active multichassis redundancy at the core with in-service software upgrade.
Oversubscription rule of thumb: 3:1 or less for general access, 1:1 or better for storage and latency-sensitive leaf-spine uplinks.
Aruba + HPE synergy: bundled switching with ProLiant/Synergy and GreenLake networking-as-a-service for OpEx consumption.
Hybrid IT
Hybrid IT spans on-premises data center, colocation, edge, and public cloud; HPE positions GreenLake as the consistent operating model across all.
HPE GreenLake for private cloud (formerly GreenLake Private Cloud Enterprise) delivers VM and container services on HPE-managed infrastructure.
HPE Ezmeral provides the data and analytics/container platform layer for hybrid workloads, including Ezmeral Data Fabric and Unified Analytics.
Morpheus (HPE Morpheus Enterprise) provides multicloud orchestration and self-service provisioning across on-premises and public cloud.
Hybrid cloud decision rule: keep latency-sensitive, regulated, or high-egress workloads on-premises; burst or dev/test to public cloud.
Data mobility: HPE Storage replication, StoreOnce Cloud Bank, and backup to cloud object storage enable hybrid data protection.
HPE GreenLake cloud services connect on-premises infrastructure to the HPE GreenLake platform for monitoring, metering, and lifecycle management.
Hybrid IT TCO includes data egress, interconnect, and operational tooling - compare against pure public cloud for steady-state workloads.
Hybrid IT, Cloud and GreenLake Consumption Models
GreenLake consumption models: metered (pay per use), reserved (capacity commitment), and managed services; billing is monthly based on measured usage.
GreenLake contract mechanics: minimum commitment, buffer capacity, term length (typically 3-5 years), and true-up/true-down at defined intervals.
GreenLake shifts spend from CapEx to OpEx; the customer pays for consumed capacity above the committed buffer, aligning cost with growth.
GreenLake Central / GreenLake platform provides a single dashboard for cost, compliance, and capacity across GreenLake services.
GreenLake for Compute (ProLiant/Synergy), GreenLake for Block Storage (Primera/Nimble), and GreenLake for Backup (StoreOnce) are the core metered offers.
Comparison rule: GreenLake wins when customer wants predictable OpEx, faster deployment, and HPE-managed operations; CapEx wins for stable, long-lived, fully utilized workloads.
GreenLake pricing includes hardware, software, and HPE services; exit/return terms and data migration obligations must be reviewed in the contract.
CloudPhysics/GreenLake cost analytics help right-size before committing to a capacity buffer.
HPE Pointnext Services and Support
HPE Pointnext Tech Care: 24x7 reactive support with access to experts, firmware/software updates, and knowledge base - replaces legacy Care Pack tiers.
HPE Pointnext Complete Care: proactive, personalized service with assigned account team, proactive monitoring, and incident prevention.
HPE Pointnext Operational Services: deployment, migration, and managed services delivered by HPE or partners.
HPE Pointnext Lifecycle services: install, startup, and deployment (Install & Start), plus education and residency options.
Support tier mapping: Foundation Care (basic) < Tech Care (expert access) < Complete Care (proactive, assigned team).
HPE Pointnext Financial Services (HPE Financial Services) provides leasing, asset upcycling, and refresh financing to align with GreenLake.
Service-level design: define response time (4-hour vs next business day), coverage window (24x7 vs 9x5), and parts availability per site.
Pointnext advisory services include transformation workshops, TCO/ROI analysis, and architecture design for hybrid cloud.
Solution Design
Design sequence: requirements (workload, SLA, growth) → architecture (compute/storage/network) → sizing → validation → TCO/ROI → proposal.
Workload profiling: capture IOPS, throughput, latency, capacity, and growth rate for storage; vCPU, RAM, and network for compute.
Availability design: N+1 for most workloads, N+N or 2N for tier-1; use Peer Persistence or VSX for stretched clusters.
Storage sizing: usable capacity = raw × (1 - RAID overhead) × (1 - sparing) × (1 - snapshot/reserve); account for growth headroom.
Network design: leaf-spine with EVPN-VXLAN for scale-out; VSX or VSF for redundancy; size uplinks to peak east-west traffic.
Management design: OneView for compute/storage, Aruba Central/Fabric Composer for network, GreenLake platform for consumption and telemetry.
Validation: use HPE sizing tools (e.g., Ninja, InfoSight) and proof-of-concept to confirm performance before commitment.
Document assumptions and exclusions; align design to customer's security, compliance, and DR requirements.
Sizing and TCO/ROI Justification
TCO components: hardware, software/licenses, support, power/cooling, floor space, admin labor, migration, and refresh/disposal.
ROI formula: ROI = (net benefit / total cost) × 100; payback period = initial investment / annual net benefit.
GreenLake TCO comparison: model CapEx purchase vs metered OpEx over the same term, including buffer capacity and true-up assumptions.
Power/cooling: use vendor power calculators and PUE; a lower-wattage server reduces both energy and cooling cost.
Consolidation math: refresh ratio (e.g., 10:1 or 20:1) driven by core count, RAM, and performance per watt of new generation.
InfoSight/AIOps value: quantify reduced downtime hours × cost per hour of downtime for the ROI case.
Sensitivity analysis: vary growth rate, utilization, and term length to show TCO range, not a single point estimate.
Competitive TCO: normalize by performance per watt, support inclusion, and management software to avoid apples-to-oranges comparisons.
Competitive Differentiation and Objection Handling
Differentiators: Silicon Root of Trust, iLO, InfoSight/AIOps, GreenLake consumption, and Pointnext services - lead with security, manageability, and economics.
Objection 'Dell is cheaper': compare total cost including support, management software, power, and refresh; HPE differentiates on security and services.
Objection 'We're going to public cloud': position hybrid - keep steady-state and regulated workloads on-premises; GreenLake provides cloud-like OpEx.
Objection 'Cisco UCS is integrated': HPE counters with Synergy composability, OneView, and Aruba Fabric Composer integration.
Objection 'Lenovo/Supermicro price': emphasize iLO/Silicon Root of Trust, global support, and lifecycle services over lowest unit price.
Objection 'GreenLake lock-in': highlight term flexibility, buffer capacity, exit terms, and that hardware can be purchased outright.
Proof points: use customer references, InfoSight predictive analytics data, and TCO/ROI models to substantiate claims.
Never disparage competitors; reframe the comparison on the customer's stated priorities (security, uptime, cost predictability).