STATUS_INTERNAL_ERROR after cluster switch maintenance because port has no configuration

Last updated

Feb 25, 2025
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 30

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: nas

Last Updated:: 2/25/2025, 8:59:15 PM

Applies to

ONTAP 9
SMB
cluster switch

Issue

After cluster switch maintenance (e.g. firmware upgrade), File Explorer gets An internal error occurred when navigating into a share.
The share's data is on an aggregate that is on Node2
- If the client connects to a LIF that is on Node2, the access succeeds
- If the client connects to a LIF that is on Node1, the access fails.
  - Packet Trace shows that ONTAP responds to a FIND request with STATUS_INTERNAL_ERROR
    - At the time of the STATUS_INTERNAL_ERROR, EMS says
      - [Node1: kernel: Nblade_CifsOperationTimedOut_1:error]: params: {'commandName': 'SMB2_COM_QUERY_DIRECTORY', 'suspensionCnt': '6', 'cmdRestartCnt': '0', 'lastCsmError': 'CSM_TIMEOUT', 'remoteBladeID': 'd902e2c0-3041-11ee-84aa-d039eaa71a43 (Node02)', 'isQosEnabled': 'QoS_disabled', 'lastSpinNpError': 'SUCCESS', 'clientIpAddress': '10.30.30.60', 'localIpAddress': '10.50.40.170', 'vserverId': '3', 'dsId': '1200', 'vserverName': 'svm1'}
EMS contains cluster network alerts:
- [Node1: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node1_clus1 (node node1) to cluster lif Node2_clus1 (node Node2).
- [Node1: kernel: csm.createSessionFailed:debug]: Cluster Session Manager (CSM) failed to create session (req=d902b026-3041-11ee-84aa-d039eaa71a43, rsp=Node1:dblade, uniquifier=0a062efa5133dee5) with transport type RDMA_RoCEv2, session tag SAN_REMOTE, record state ACTIVE, CSM error CSM_CONNABORTED, low-level error UNKNOWN, socket error 0, and TLS error 0.
- [Node1: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e3a on node Node1 has gone down unexpectedly.