Cluster interconnect session failed with CSM_CONNABORTED
Applies to
ONTAP 9
Issue
- EMS has the following information
Sat Mar 25 21:56:35 KST [node1: CsmMpAgentThread: csm.sessionFailed:error]: Cluster interconnect session (req=node1:dblade, rsp=node2:dblade, uniquifier=0e05f7a4ec72fb2f) failed with record state ACTIVE and error CSM_CONNABORTED.
Sat Mar 25 21:56:35 KST [node1: CsmMpAgentThread: csm.sessionFailed:error]: Cluster interconnect session (req=node1:dblade, rsp=node3:dblade, uniquifier=0e05f7a4ec71da20) failed with record state ACTIVE and error CSM_CONNABORTED.
- The first two digits of the above uniquifier are 0e, These are hex numbers and match to 0x0e in the table. We can see this is a Cluster Peering Session.
0x0e | CSM_SESSION_TAG_CPEER | Cluster Peering Session |
- The destroying idle session can be seen in
CSM-TRACE-BUFFER.GZ
03/25 125635 (SpinNPSessionInt::timeoutIdleSession): this = 0xffffff800b0ef028, sessionId = (req=node1:dblade, rsp=node2:dblade, uniquifier=0e05f7a4ec72fb2f), Destroying idle session. now = 346086428, oldestAcceptable = 259686428, create = 259686414, lastRequest = 259686414/259686414/259686414, lastResponse = 259686414/259686414/259686414
CSM_IDLE_SESSION_TIMEOUT
is displayed on the source
Sat Mar 25 21:58:08 KST [node2: CsmMpAgentThread: csm.sessionFailed:debug]: Cluster interconnect session (req=node2:dblade, rsp=node4:dblade, uniquifier=0e05f7a4f1debaa2) failed with record state ACTIVE, CSM error CSM_IDLE_SESSION_TIMEOUT, low-level error UNKNOWN, socket error 0, and TLS error 0.
Sat Mar 25 21:58:08 KST [node3: CsmMpAgentThread: csm.sessionFailed:debug]: Cluster interconnect session (req=node3:dblade, rsp=node4:dblade, uniquifier=0e05f7a4f1dfaa13) failed with record state ACTIVE, CSM error CSM_IDLE_SESSION_TIMEOUT, low-level error UNKNOWN, socket error 0, and TLS error 0.