Host Connectivity, Multipathing, and Front-End Configuration
Host connectivity and front-end configuration questions test zoning, initiator setup, multipathing and protocol choice. The array side is only half the answer: you are expected to reason about host, fabric and array port group together.
Protocols and ports
- PowerMax presents over Fibre Channel (FC), iSCSI and, on PowerMaxOS 10, NVMe (FC-NVMe and NVMe/TCP). Choose NVMe for latency-sensitive workloads with a supported host stack; otherwise FC remains the default for enterprise hosts.
- Front-end ports belong to director emulations (FA for FC, FE for iSCSI/GigE). iSCSI and NVMe/TCP need IP interfaces on the ports, with correct VLAN and MTU settings and discovery portals configured on the host.
Zoning and initiator groups
- Zone one initiator HBA port to the array ports, single-initiator/single-target or single-initiator/multiple-target. Never zone initiator-to-initiator.
- Use at least two fabrics, and place array ports in a port group so each host has paths through different directors.
- Register the exact WWPN or NQN in the initiator group and set the correct host flags; a wrong flag produces failover, clustering or timeout problems rather than a clean failure to see the LUN.
Multipathing
- Each host needs multiple paths and a multipathing layer: Dell PowerPath or the native stack (DM-MPIO on Linux, MPIO on Windows, AIX MPIO, ESXi NMP). PowerMax is active/active, so all paths in the port group should be usable and load-balanced.
- Path count follows from host HBA ports multiplied by array ports in the port group; keep it practical and consistent across the estate.
Worked example
A Linux host has two HBAs, each zoned to two array ports on separate directors, and the port group contains four ports. Expect two HBAs x four ports = eight paths, all active. If dm-multipath shows two paths, check zoning first: a missing zone shows as a missing path, not as an array fault. If paths exist but I/O fails, check initiator group flags and rescan the host.
Traps
Zoning a host to only one director; using a WWN that belongs to another host; mismatched iSCSI MTU or VLAN; and expecting PowerPath to compensate for a missing zone.