Home / Reference / ONTAP releases

ONTAP release guide: 9.16.1 through 9.19.1

A field map of recent ONTAP trains: what each one introduces, which new platforms require it, and what to verify before an upgrade.

NetApp AFF A800 platform running ONTAP
ONTAP on AFF hardwareKorP · CC BY-SA 4.0 · Wikimedia Commons
Release train is not patch level. Feature releases such as 9.17.1 establish capabilities. Production planning must also select a supported P-release and check known issues, upgrade paths, platform support, and host interoperability.

Feature matrix

TrainOperational highlightsPlatform context
9.16.1ARP/AI without the old learning period on supported NAS workloads; NVMe/TCP with TLS 1.3; broader multi-admin verification; Entra ID OAuth/group mappings; WebAuthn; S3 bucket snapshots and expanded REST coverage.Minimum train for AFF A20/A30/A50, AFF C30/C60/C80, ASA r2 A20/A30/A50/C30, and FAS50.
9.17.1ARP/AI coverage for SAN with entropy-based detection; NVMe host access with SnapMirror active sync; ONTAP Cloud Mediator; HSTS; post-quantum preshared keys for IPsec; JIT privilege elevation; S3 bucket restore.Minimum train for AFX 1K and its NSX224 shelf. Validate host and mediator requirements before using new SAN continuity features.
9.18.1A later feature train and an important gate for several controller-upgrade paths. Treat the official “What's new” page as authoritative because feature availability can vary by platform and protocol.Required by documented ARL paths including A70→A90, A30→A50, A20→A30/A50, C30→C60, and FAS70→FAS90.
9.19.1Newest documentation train in the release hub at time of review. Adoption should follow support policy and workload certification, not novelty.Minimum train listed for AFX 2K. Check Hardware Universe for the final supported configuration.

Upgrade decision workflow

  1. Inventory: record controllers, shelves, switches, protocols, licenses, cluster health, and current full version including P-release.
  2. Choose the target train: start from business need or hardware requirement, not simply the newest number.
  3. Gate compatibility: verify Hardware Universe, Interoperability Matrix, Active IQ Upgrade Advisor, release notes, and required intermediate hops.
  4. Read behavior changes: defaults, limits, removed support, security behavior, REST changes, and protocol-specific known issues can matter more than headline features.
  5. Validate and execute: use ONTAP image validation, fix warnings, take configuration backups, confirm failover health, then follow the upgrade runbook.

Pre-flight commands

version -v
system node show -fields model,serialnumber,health,uptime
cluster show
storage failover show
system health alert show
cluster image show
cluster image validate -version <target-version>

Sources and boundaries

Start with NetApp's release highlights, then open the complete “What's new” and release-notes page for the target train. Use the platform compatibility matrix for orientation, but use Hardware Universe and the Interoperability Matrix for configuration-level decisions.