Skip to main content
NetApp Stage KB

Why does ONTAP report different CPU clock speeds when deployed on virtual HW

Last Updated:

Applies to

  • NetApp ONTAP 9
  • Cloud Volumes ONTAP (CVO)
  • NetApp ONTAP Select
  • Microsoft Azure
  • High Availability


  • Different CPU GHz may be reported by ONTAP HA running on virtual HW such as ESXi or Microsoft Azure as a result of the difference in underlying CPU family/type on the physical host.
  • This is most commonly seen in the output of sysconfig-a which contains information about the System Board
  • For example, in the case of Azure according to their documentation, it is an expected behavior because the CPU is allocated based on availability. Users can deploy on identical HW only on Azure Dedicated Hosts

Additional Information

  • To confirm ONTAP shows the correct clock speed and system board information, please consult with the OEM vendor (eg. Microsoft) to verify what HW the ONTAP virtual host is running on.
  • If ONTAP is giving false information in comparison to the backend HW, please contact NetApp Technical Support and reference this KB.
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.