Skip to main content
NetApp Knowledge Base

Azure CVO instance will not boot due to Network port down

Views:
440
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Azure CVO (Cloud Volumes ONTAP)
  • Azure: CX4 hardware
  • Applies to ONTAP 9.5P1 to 9.7P1

Issue

  • Azure CVO instance was unable to boot while upgrading ONTAP
  • CVO instance unable to boot instance after instance stop/deallocate/start
  • Network port not able to be brought online
  • The console logs will illustrate the following errors:
e0a: got notify, nvs type 128
e0a: mlx5e_set_board_type(epriv = 0xfffffe00159dd000, mdev = 0xfffffe0015430000) Unknown board_id = MSF0010110035
.
.
e0a: mlx5e_open: Setting port status to up failed
e0a: mlx5e_open_locked: mlx5e_open_tises failed, -5
.
.
e0a: no link .............. giving up
.
.
e0a: mlx5_fw_version_check ONTAP does not have valid firmware image for PSID=MSF0010110035

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

******************************************************* *******************************************************