ASA r2: the SAN-focused ONTAP operating model
ASA r2 is not merely a classic ASA with a newer controller. It exposes a deliberately simplified SAN data model, vocabulary, interface, and REST surface.
Classic ASA versus ASA r2
| Area | Classic ASA | ASA r2 |
|---|---|---|
| Primary data object | Traditional ONTAP volume containing LUNs or NVMe namespaces | Storage unit presented through a simplified SAN workflow |
| Placement view | Aggregates/local tiers, SVMs, volumes, LUNs | Storage availability zones abstract controller-pair resources |
| Host paths | Symmetric active-active on ASA platforms | Symmetric active-active SAN access with simplified provisioning |
| Protocols | Block: FC, iSCSI and supported NVMe variants | Block-only workflows; consult model/version docs for exact protocol support |
| Automation | Standard ONTAP REST API and CLI model | Distinct ASA r2 REST resources and a reduced/different command surface |
Identify before automating. Do not aim a volume/LUN workflow written for AFF or classic ASA at ASA r2 without checking the ASA r2 API and CLI documentation. Similar outcomes use different resources.
Core concepts
- Storage unit: host-consumable block storage. Provisioning combines capacity and host mapping in a simpler object than the traditional volume-plus-LUN workflow.
- Storage availability zone: the fault and placement abstraction presented by ASA r2. It helps express resilience without making routine operators manage every underlying ONTAP object.
- Symmetric active-active: all reported paths are optimized, reducing host path transitions during controller failover. Host multipathing is still mandatory.
- Consistency and protection: snapshots, replication, consistency groups, and ransomware-resilience capabilities remain version- and workflow-dependent; verify them for the exact ASA r2 release.
Operational checklist
- Confirm the exact model, ONTAP release, protocol, host OS, HBA/NIC, multipath software, and switch firmware in the Interoperability Matrix.
- Use the ASA r2 documentation set for provisioning and protection; do not mix it with classic ASA procedures.
- Provide redundant initiator paths through independent fabrics or networks to both controllers.
- Test controller takeover/giveback and planned fabric loss while watching host multipath behavior.
- Back up configuration and record mappings before upgrades or disruptive maintenance.
Version and model orientation
The first ASA r2 generation—A1K, A70, and A90—began with ONTAP 9.16.0. A20, A30, A50, and C30 support begins with 9.16.1 according to the official platform matrix. Always recheck current documentation because platform additions and feature parity continue across trains.
Authoritative reading
Use NetApp's ASA r2 documentation for configuration and the classic ASA overview to understand the boundary. See the ONTAP release guide for train-level planning and hardware lineup for family orientation.