Skip to main content
NetApp Knowledge Base

Falpping cluster port on X50130A NIC adapter

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
HW
Last Updated:

Applies to

  • AFF-C80 system
  • X50130A NIC (Network Interface Card) adapter
  • X65405 - 100G optical QSFP (Quad Small Form-factor Pluggable)
  • N9K-C9336C-FX2 - Cisco switch
  • NX-OS  10.4(4)
  • MCC-IP

Issue

  • In EMS-LOG-FILE autosupport section:

Thu Oct 09 01:18:58 +0200 [node-1: kernel: netif.linkDown:info]: Ethernet e7a: Link down, check cable.
...
Thu Oct 09 01:18:58 +0200 [node-1: kernel: netif.linkUp:info]: Ethernet e7a: Link up.
Thu Oct 09 01:23:25 +0200 [node-1: kernel: netif.linkDown:info]: Ethernet e7a: Link down, check cable.
...
Thu Oct 09 01:23:25 +0200 [node-1: kernel: netif.linkUp:info]: Ethernet e7a: Link up.

  • In switch logs

[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: ERR: mlx5_cmd_check:735:(pid 0): ACCESS_REG(0x805) op_mod(0x1) failed, status bad parameter(0x3), syndrome (0xc2b9a2)
[3741499] e7a: mlx5e_update_carrier query port paddr failed, err:-22,i:9, cable_type:255

 

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.