I85PREP
⌘ K
HPE ASE Storage Architect study materials
HPE ASE Storage Architect study resources

HPE ASE Storage Architect: Storage Deployment and Implementation

HPE ASE Storage Architect · Work through your exam, one topic at a time.

All guide sections

Storage Deployment and Implementation

This domain tests execution rather than theory: turning a validated design into correctly zoned, correctly presented and correctly multipathed LUNs, and onboarding the array into HPE management tooling without breaking support entitlement.

Before the first cable

  • Confirm the firmware baseline and array template in Data Services Cloud Console (DSCC) or OneView.
  • Prepare management IPs, DNS, NTP, alert destinations and remote support enablement; register GreenLake subscriptions where applicable.
  • Map host OS version to the supported host persona and multipath stack from the HPE support matrix.

Provisioning sequence for Primera and Alletra block

  1. Initialise the array, set domain, time zone, NTP, notifications and remote support.
  2. Create CPGs per tier with RAID type, growth increment and warning limit.
  3. Create host objects from WWPN, IQN or NQN with the correct persona, then host sets for clusters.
  4. Create volumes in the CPG and export them to the host set with explicit LUN IDs.
  5. On the host, install the supported multipath stack, set ALUA or round-robin policy, rescan, then align and format.

Zoning and fabric rules

  • Single-initiator, single-target zoning (or single-initiator, multiple-target on large fabrics), applied identically on both fabrics; use NPIV for VMware; never zone initiators to each other or put ISLs in zones.
  • iSCSI and NVMe/TCP: CHAP in both directions, jumbo frames configured end to end, separate VLANs, and discovery controller configuration for NVMe/TCP.

Worked example

A two-node VMware cluster with two FC HBAs per host gives four initiator ports. Create a host object per WWPN with the VMware persona, place all four in one host set, present the datastore volume to the host set, and use the same LUN ID for every member, because ESXi clustering requires identical LUN IDs across hosts. Zone each initiator to one target port per fabric, verify path state with the ESXi storage commands before formatting VMFS, and confirm both fabrics show active paths rather than standby-only.

Traps that cost marks

Wrong persona causing ALUA or path failures; mismatched LUN IDs inside a cluster; zoning only one fabric; forgetting to install or enable the host multipath driver; reusing a LUN ID after deletion; MTU mismatch on iSCSI; presenting to individual hosts instead of the host set; and time drift that breaks LDAP or Kerberos authentication.