ONTAP Configuration

ONTAP Configuration

The prerequisites for ONTAP are:

  • The driver requires a storage controller running ONTAP 8.1.1 or later.

  • The storage system should have the following licenses applied:

  • Base

  • NFS (if the NFS storage protocol is used)

  • iSCSI (if the iSCSI storage protocol is used)

  • FCP (if the Fibre Channel protocol is used)

  • FlexClone

Additional Prerequisites for SnapMirror Replication

The following prerequisites apply when configuring any SnapMirror replication policy (MirrorAllSnapshots, Asynchronous, AutomatedFailOver, or AutomatedFailOverDuplex) in Cinder.

ONTAP Version Requirements

The minimum ONTAP version depends on the replication policy:

  • MirrorAllSnapshots or Asynchronous (async replication) — Unified ONTAP 9.15.1 or later. Supports iSCSI, FC, and NFS.

  • AutomatedFailOver (SnapMirror Active Sync — Asymmetric) — Unified ONTAP 9.15.1 or later. Supports iSCSI and FC only.

  • AutomatedFailOverDuplex (SnapMirror Active Sync — Symmetric) — Unified ONTAP 9.15.1 or later. Supports iSCSI and FC only.

Note

All replication policies are supported only on Unified ONTAP. ASA r2 (disaggregated) platforms are not supported for replication in this release.

Required Licenses

In addition to the standard protocol licenses above, the following must be active on both the source and destination clusters:

  • SnapMirror — Required for all asynchronous replication (MirrorAllSnapshots and Asynchronous policies).

  • SnapMirror Synchronous — Required for AutomatedFailOver and AutomatedFailOverDuplex (SnapMirror Active Sync) policies. Verify the exact license entitlement name with your NetApp account team or the ONTAP licensing documentation.

Cluster and SVM Peering

Replication requires a peer relationship between the source and destination ONTAP clusters and between the source and destination SVMs. Both must be established before the Cinder driver initializes replication:

  • Cluster peering — The source and destination ONTAP clusters must be peered. See the ONTAP cluster peering documentation for setup instructions.

  • SVM peering — The source and destination SVMs must be peered. The SVM peer relationship must permit the SnapMirror application. See the ONTAP SVM peering documentation for setup instructions.

REST API Access

The AutomatedFailOver and AutomatedFailOverDuplex policies require the ONTAP REST API. Set netapp_use_legacy_client = False in every backend stanza that uses these policies. ZAPI is not supported for SnapMirror Active Sync (ONTAP limitation).

For asynchronous policies (MirrorAllSnapshots and Asynchronous), both ZAPI and REST are supported.

ONTAP Mediator (AutomatedFailOver and AutomatedFailOverDuplex)

ONTAP SnapMirror Active Sync requires an ONTAP Mediator instance for automatic unplanned failover arbitration. The Mediator must be configured separately on ONTAP and must be reachable from both clusters. See the ONTAP Mediator documentation for installation and configuration steps.

Important

Without a properly configured and reachable ONTAP Mediator, automatic unplanned failover will not occur. Planned failover using the OpenStack CLI will still function.