Skip to main content
NetApp Knowledge Base

How to upgrade NSLM managed workloads from traditional QoS to AQoS after cluster upgrade

Views:
287
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
legacy
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP 9.1
  • ONTAP 9.2
  • ONTAP 9.3
  • ONTAP 9.4
  • ONTAP 9.5

Description

This article provides the procedure to upgrade NSLM managed workloads from traditional QoS to AQoS after cluster upgrade

NSLM ( NetApp Service Level Manager) 1.2 GA extends support for some older ONTAP versions, i.e., 9.1 and later. In NSLM, all workloads are assigned service levels supported by QoS polices. The allocation of IOPS in QoS policies for earlier versions of ONTAP is thick-provisioned based on the storage capacity of the workload, while for the later versions of ONTAP, the allocation of IOPS is thin-provisioned.

NSLM supports ONTAP QoS capabilities as follows:

  • File shares:
    ONTAP version < 9.3 - thick provisioned QoS IOPS limits (QoS)
    ONTAP version >= 9.3 - thin-provisioned QoS IOPS limits (AQoS)
     
  • LUNs:
    ONTAP version < 9.4 - thick provisioned QoS IOPS limits (QoS)
    ONTAP version >= 9.4 - thin-provisioned QoS IOPS limits (AQoS)

When NSLM assigns or reassigns performance service level to a workload, the QoS or the aQoS policies are chosen based on the ONTAP version of the cluster, as above. In case of upgrading an ONTAP cluster from a version that supports only thick IOPS limits (QoS) to a version that supports thin IOPS limits, then NSLM suggests assigning the workloads with the same performance service level, but thin-provisioned IOPS (aQoS), as a more efficient way of allocating IOPS.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.