Skip to main content
NetApp Knowledge Base

E-Series controller failover due to mellanox (mlx5) network driver fault

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • E5700

Issue

  • Controller A (or B) experienced a failover event.
  • The uploaded core dump shows the last running thread was CPU2Sched1.
  • The failover was triggered by a fault in the Mellanox (mlx5) network driver, which disrupted mirror channel communication between the controllers.

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.