Skip to main content
NetApp Knowledge Base

Cluster not reachable after replacing data network switches

Views:
187
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS9000
  • Qlogic 8324 CNA adapter
  • Cisco N2K-C2248TP-E Fabric Extender (FEX)
  • ONTAP 9.7

Issue

  • After upgrading Data Network Switch models OnCommand Unified Manager reports the cluster as unreachable
  • CIFs shares no longer accessible
  • Only ports on Qlogic CNA adapters are affected. Example:

slot 2: 1G/10G Ethernet Controller CNA EP 8324
(Multiple Dual-port, QLogic CNA 8324(8362) rev. 2)
e2d MAC Address:    00:a0:98:ed:e9:5f (auto-unknown-fd-down)
e2c MAC Address:    00:a0:98:ed:e9:5e (auto-unknown-fd-down)
e2b MAC Address:    00:a0:98:ed:e9:59 (auto-10g_sr-fd-up)
e2a MAC Address:    00:a0:98:ed:e9:58 (auto-10g_sr-fd-up)
Device Type:        EP8324N
Firmware Version:   5.4.66.0
Part Number:        111-02397
Hardware Revision:  A3
Serial Number:      031848004935

  • DMESG logs show errors for the CNA adapters
[116] e2d: **** flash fw version 5.4.53, peg 0x0000ff01 function 0
[116] e2d: **** First driver-load *****, func 0
[123] e2d: **** fw version 5.4.66, peg 0x0000ff01, function 0
[123] e2d: qla_pci_attach: firmware[5.4.66.0]
[123] e2d: qla_pci_attach: ha 0xfffffe00310d2000 pci_func 0x0 rsrc_count 0x00200000 msix_count 0x40 pci_reg 0xfffff8017bb50880 num_rcvq = 32
[123] e2d: qla_pci_attach: mp__ncpus 36 sds 16 rds 16 msi-x 17
[123] e2d: This platform does not support CPR
[123] FuseN mode: 40/0/1 unclaimed NIC device
[123] ql1: <Qlogic EP 83xx PCI CNA Ethernet Function v3.10.35> mem 0x91000000-0x911fffff,0x91610000-0x91611fff at device 0.1 on pci8
[123] changing device name from ql1 to e2c
[123] e2c: **** fw version 5.4.66, peg 0x0000ff01, function 1
[123] e2c: qla_pci_attach: firmware[5.4.66.0]
[123] e2c: qla_pci_attach: ha 0xfffffe00314ac000 pci_func 0x1 rsrc_count 0x00200000 msix_count 0x40 pci_reg 0xfffff8017bb50680 num_rcvq = 32
[123] e2c: qla_pci_attach: mp__ncpus 36 sds 16 rds 16 msi-x 17
[123] e2c: This platform does not support CPR
[123] FuseN mode: 41/0/0 unclaimed NIC device
[123] ql2: <Qlogic EP 83xx PCI CNA Ethernet Function v3.10.35> mem 0x90600000-0x907fffff,0x90a12000-0x90a13fff at device 0.0 on pci9
[123] changing device name from ql2 to e2b
[123] e2b: **** flash fw version 5.4.53, peg 0x0000ff01 function 0
[123] e2b: **** First driver-load *****, func 0
[130] e2b: **** fw version 5.4.66, peg 0x0000ff01, function 0
[130] e2b: qla_pci_attach: firmware[5.4.66.0]
[130] e2b: qla_pci_attach: ha 0xfffffe0031886000 pci_func 0x0 rsrc_count 0x00200000 msix_count 0x40 pci_reg 0xfffff8017bb50000 num_rcvq = 32
[130] e2b: qla_pci_attach: mp__ncpus 36 sds 16 rds 16 msi-x 17
[130] e2b: This platform does not support CPR
[130] FuseN mode: 41/0/1 unclaimed NIC device
[130] ql3: <Qlogic EP 83xx PCI CNA Ethernet Function v3.10.35> mem 0x90400000-0x905fffff,0x90a10000-0x90a11fff at device 0.1 on pci9
[130] changing device name from ql3 to e2a
[130] e2a: **** fw version 5.4.66, peg 0x0000ff01, function 1
[130] e2a: qla_pci_attach: firmware[5.4.66.0]
[130] e2a: qla_pci_attach: ha 0xfffffe0031c84000 pci_func 0x1 rsrc_count 0x00200000 msix_count 0x40 pci_reg 0xfffff8017bb4fd80 num_rcvq = 32
[130] e2a: qla_pci_attach: mp__ncpus 36 sds 16 rds 16 msi-x 17
[130] e2a: This platform does not support CPR
  • Rebooting node and replacing SFPs does not restore data access

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.