When deployed together, ONTAP Select and Cisco Unified Edge create a consolidated edge architecture. A storage-optimized compute node supplies the local NVMe media. The hypervisor presents the appropriate resources to the ONTAP Select virtual machine. ONTAP Select then organizes the local media into ONTAP aggregates and volumes, exposing storage to application workloads running locally in the same chassis or elsewhere at the edge site. This design keeps data close to applications, reduces dependency on WAN connectivity for day-to-day operations, and aligns with centralized management and data protection practices.

The four drive limitation and dependence on software RAID in XE130c and XE150c compute nodes limits ONTAP Select deployments to a single-controller architecture. Unlike a multi-node storage architecture with controller failover, a single storage controller cannot be taken offline for controller-level maintenance without affecting the local storage services it hosts.

This limitation does not eliminate the value of the architecture, but it must be reflected in the operational model. Suitable workloads are those that can tolerate planned storage outages, rely on application-level resiliency, or use replication to a central ONTAP environment for recovery. Customers should define maintenance calendars, communicate service windows to application owners, verify current backups or replicas before disruptive work, and document rollback procedures. If workloads require continuous storage availability during controller maintenance, customers should evaluate an external ONTAP storage array instead of a single-controller ONTAP Select configuration.