Skip to main content
NetApp Knowledge Base

AWS CVO single node instance doesn't start after M5 instance change

  1. Last updated
  2. Save as PDF
Views:
54
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Cloud Volumes ONTAP for AWS
  • ONTAP 9

Issue

  • CVO upgrade from 9.7x to 9.8x
  • Instance changed from M4 to M5 via BlueXP prior to upgrade
  • Instance doesn't start on M5 instance and has error:
Enhanced Networking ENA/SR-IOV needs to be enabled for the m5 instance type

 

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.