Skip to main content
NetApp Knowledge Base

Do AQoS Policy changes to a service level have an impact on billing in NetApp Keystone

  1. Last updated
  2. Save as PDF
Views:
56
Visibility:
Customer
Votes:
0
Category:
keystone
Specialty:
keystone
Last Updated:

Applies to

  • NetApp Keystone
  • ONTAP
  • Adaptive Quality of Service (AQoS)

Answer

Yes, even a brief policy change to a higher or lower Keystone Service Level on a volume can affect billing

  1. Impact on Billing:
  • Only the highest contractual service level activated can be billed.
  • Changing a volume’s AQoS policy to a higher service level (e.g., from Performance to Extreme) will incur charges at the higher tier for the duration of the change.
    • The metering system captures all policy changes, even brief ones
  • Moving a volume to a higher tier may trigger burst charges if usage exceeds the subscribed level.
  • Moving a volume to a lower tier may cause the lower tier to enter burst, also increasing charges.
  1. Conditions Affecting Billing Impact:
  • If sufficient capacity exists within your committed subscription and no tier enters burst, billing remains unaffected.
  • It is essential to monitor usage to avoid exceeding subscription thresholds, which would result in additional charges.
  1. Practical Steps for testing a policy change:
  1. Review Commitments: 
    Confirm available capacity to assess burst risk.
  2. Monitor Usage: 
    Use AIQ dashboards to track consumption during the policy change.
  3. Revert Promptly: 
    After testing, restore the original AQoS policy using ONTAP CLI or System Manager to prevent extended higher-tier billing.

Additional Information

 

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.