Home / Reference / ONTAP 9.19.1 changes for ASA r2
ONTAP 9.19.1 changes for ASA r2 admins — validation guide
A focused checklist for operations teams: which of the ONTAP 9.19.1 changes and new features deserve regression testing after upgrading — starting with the ASA r2 behaviours that alter failover, pathing and protection assumptions.
What changes for ASA r2 admins in ONTAP 9.19.1?
The release adds useful options; it does not make them safe by default for every existing design. Use this as a change-review gate for ASA r2, then confirm platform, host and adapter support in NetApp’s current documentation.
| 9.19.1 change | Administrator consequence | Evidence to collect before acceptance |
|---|---|---|
| AIX support with SnapMirror active sync | AIX can use transparent application failover in symmetric active/active configurations. Treat this as a host and protection-topology qualification, not a blanket enablement. | Record the supported AIX, host utility, multipath and ONTAP combination; exercise planned and unplanned failover and prove zero-RPO behavior. See the active-sync runbook. |
| FLI with an iSCSI backend | An iSCSI-connected source array can enter a Foreign LUN Import workflow. The migration still needs discovery, path, performance, rollback and cutover gates. | Capture source-LUN identity and paths, baseline latency and throughput, validate import visibility, and document the rollback point before cutover. |
| Direct-attached FC and FC-NVMe | A supported host may connect without an FC switch. Removing the fabric also removes switch-based zoning and changes the failure domain. | Verify the exact ASA r2 adapter and host combination, cable redundancy, port ownership, host mappings and path survival during takeover/giveback. Use the SAN multipathing checklist. |
| Automatic SAN LIF failover for iSCSI and NVMe/TCP | ASA r2 IP SAN LIFs in an active-active multipath configuration can fail over automatically. This is a path-behavior change, not permission to reduce host-side multipathing. | Inventory LIF failover policies and host sessions, then prove I/O continuity and the expected LIF location through port and controller failures. |
| ARP/AI with SnapMirror active sync | Detection protects active read-write primary storage units. ARP snapshots are primary-only, so do not count them as replicated recovery points. | Confirm ARP/AI state and alert routing, trigger a controlled detection test, and prove the separate secondary-site recovery procedure. |
| TLS hardware offload | Supported Ethernet cards can offload encryption and decryption, reducing CPU work; benefit depends on the actual card and TLS workload. | Verify supported NICs, compare CPU and TLS throughput before and after, and confirm encrypted traffic and failover behavior remain correct. |
| TCP PRR and optional RACK loss recovery | PRR is enabled by default; RACK is intended for congested links around 25 Gb/s and is disabled by default. WAN behavior can therefore change even without enabling RACK. | Baseline retransmits, latency and throughput on replication or IP SAN paths; change RACK only with a measured congested-link case and a rollback value. |
| Global deduplication across a storage availability zone | Deduplication can eliminate duplicate blocks across storage units in the same SAZ and is enabled by default. Capacity results should be assessed at the SAZ boundary, not as classic aggregate or volume tuning. | Capture SAZ capacity and efficiency before upgrade, then compare savings and workload latency after representative data has been processed. |
| SAZ capacity alert in System Manager | System Manager adds an alert when a storage availability zone approaches capacity; it supplements rather than replaces external thresholds. | Confirm the alert is visible to the intended operators and that monitoring still tracks headroom for each HA pair’s SAZ. |
| Configurable automatic QoS ceiling increases | The defaults governing temporary throughput-ceiling increases can now be changed. Existing policy intent can drift if automation starts writing the new controls. | Record policy-group ceilings and automation payloads, leave defaults unchanged unless a burst requirement is documented, and compare peak latency and fairness. |
| Separated upgrade pre-check errors and warnings | Automated upgrade output makes blockers easier to distinguish from review items, but warnings still require an explicit disposition. | Archive the pre-check output; assign every error a remediation and every warning an accept, mitigate or defer decision before the maintenance window. |
Source boundary: feature availability above comes from NetApp’s ASA r2 9.19.1 What’s New. The acceptance evidence is an operator test plan, not a claim that every platform or host combination is supported.
What not to put in an ASA r2 test plan
ASA r2 is a SAN-only ONTAP personality: it does not support NAS protocols, and it uses storage availability zones and storage units instead of an administrator-managed aggregate, volume and LUN hierarchy. That removes several headline 9.19.1 features from an ASA r2 regression plan.
| General ONTAP 9.19.1 headline | ASA r2 disposition | Where it belongs |
|---|---|---|
| NFS over TLS, independent NFSv4.2 controls and small-directory listing acceleration | Exclude. ASA r2 has no NAS protocol support. | Test on NFS-enabled AFF or FAS SVMs. |
| Expanded system-defined failover targets for NAS data LIFs | Exclude. Do not confuse this with the new automatic failover for ASA r2 iSCSI and NVMe/TCP LIFs. | Test NAS failover groups on unified ONTAP; test IP SAN LIF failover separately on ASA r2. |
| SnapMirror active sync for NAS | Exclude. The ASA r2 change is ARP/AI protection for primary storage units in active-sync relationships, plus AIX host support. | The NAS feature applies to supported AFF and AFX configurations. |
| S3 conditional writes/deletes and a second S3 access key | Exclude. ASA r2 does not serve ONTAP S3 workloads. | Use the ONTAP S3 guide for unified ONTAP systems. |
NetApp’s ASA r2 personality comparison is the source of truth for this boundary. This filter is the practical difference between reading the broad ONTAP release notes and building an ASA r2 change plan.
Behavior to revalidate
- IP SAN LIF failover: test automatic iSCSI and NVMe/TCP LIF movement in the active-active configuration and verify host I/O stays on supported paths.
- SAN paths: re-test host multipathing, takeover/giveback and direct-attached FC designs against the exact platform and host stack.
- ARP/AI: review the pre-update warning where synchronous replication previously suppressed default enablement.
- Capacity efficiency: baseline each storage availability zone so global deduplication savings and capacity alerts are evaluated at the correct ASA r2 storage boundary.
Automation and monitoring checks
- Inventory scripts against the ASA r2 CLI and REST surface; do not assume a unified-ONTAP volume or aggregate endpoint exists on the streamlined personality.
- Review QoS automation before changing newly configurable throughput-ceiling behavior.
- Add SAZ capacity and efficiency to the evidence set; an individual storage unit view is not a substitute for HA-pair pool headroom.
- Record ARP/AI state, replication health, IP SAN LIF locations and host paths before and after the upgrade.
Post-upgrade validation
system health alert show
storage failover show
network interface show -fields home-node,home-port,curr-node,curr-port,status-oper
cluster peer health show
snapmirror show -fields status,healthy,lag-timeAdd workload-specific checks for NFS/SMB mounts, LUN and namespace paths, S3 clients, backup jobs and monitoring integrations. Use the upgrade runbook and troubleshooting guide for execution detail.
Scope boundary
This page deliberately does not repeat the feature catalog. The canonical 9.19.1 hub owns release notes, “what’s new,” ASA r2, comparison and advisory intent; this page owns an operator’s validation checklist.