Skip to main content
NetApp Knowledge Base

CONTAP-86540: Disable the Mellanox port monitoring daemon on CVO Azure

Views:
6
Visibility:
Customer
Votes:
0
Category:
ontap-9
Specialty:
cloud
Last Updated:

Issue

  • The EMS logs show that the mlx5dump process is running for a longer duration:

{}Thu Jun 15 06:38:25 -0400 [cluster1-01: sched_monitor: mgr.stack.longrun.proc:notice]: Long running process: mlx5dump{}{}Thu Jun 15 06:43:28 -0400 [cluster1-01: sched_monitor: sk.hog.runtime:notice]: Process mlx5dump ran for 15569 milliseconds{}
  • The above process triggers a node reboot: 

{}Thu Jun 15 06:43:36 -0400 [cluster1-01: pha_main000: kern.shutdown.initiator:debug]: SK reboot was initiated by "maytag.ko::fm_handleReserved+763".{}{}Thu Jun 15 06:59:16 -0400 [cluster1-01: sfo_status: callhome.reboot.giveback:notice]: Call home for REBOOT (after giveback){}
  • The node repeatedly reboots and displays the following error on the console.

mlx5_core2: ERR: mlx5e_ioctl:4600:(pid 0): tso6 disabled due to -txcsum6.
mlx5_core2: ERR: mlx5e_ioctl:4622:(pid 0): enable txcsum6 first.
e0c: Forced delayed initialize mlx5_core2 before network ifconfig call
e0c: mlx5_core2 SIOCGRSSKEY failed: 22
[node-01:netif.init.failed:ALERT]: Initialization of network interface mlx5_core2 failed due to unexpected software error mlx5_core err=0xffffffc4:100.

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.