Storage Admin HubConfiguration · Protection · Recovery
All guides/SAN
SAN · ONTAP 9

Provision a Fibre Channel LUN

WWPN zoning, target LIFs, igroups, and path verification.

Scenario

Example: an ESXi host has one initiator WWPN per fabric and receives one test datastore LUN. Exact zoning and host commands depend on switch and hypervisor release.

Before you change production

Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.

1. Plan dual fabrics

  1. Record HBA initiator WWPNs, ONTAP target WWPNs, switch ports, zoning convention, SVM, LUN OS type, and host utility/multipath requirement.
  2. Create FC data LIFs as supported on the relevant nodes. Verify link and fabric login before presenting a LUN. Keep fabrics independent where the design requires it.
Read-only checks 
vserver fcp show
network interface show
lun show

2. Zone and map

  1. Ask the SAN switch administrator to create approved initiator-to-target zones, typically isolating each host initiator to its intended target ports. Confirm active zoneset on both fabrics.
  2. In System Manager, create a LUN and an igroup containing only the intended host WWPNs. Map the LUN to the igroup and document the LUN ID.
  3. Rescan HBAs on the host. Match device identity and paths to the planned fabric endpoints. Format or create a datastore only after the serial and capacity match the change record.
Read-only validation 
lun mapping show
network interface show
storage failover show

3. Diagnose a missing path

  1. Start at HBA link and switch port, then zoning and target login. Check FC LIF online state, igroup WWPN spelling, LUN mapping, reporting nodes, and host rescan.
  2. Compare the failed fabric with the healthy fabric without changing both at once.
Verify

Host sees the mapped LUN and paths from both planned fabrics.

If validation fails

  1. If the switch sees no initiator, inspect HBA link, SFP, cable and switch port before changing storage zoning.
  2. If the initiator logs in but no device appears, compare the active zone, target WWPN, igroup WWPN and LUN mapping, then rescan the host.
  3. If path count is low, compare fabrics independently. Avoid changing the working fabric until the failed side is understood.
Verify

Re-run the original validation and record the observed result, exact error, time, and corrective action.

NetApp references