Skip to main content
NetApp Knowledge Base

Output of "cluster peer health show" intermittently displays "session reachable" for data ping

Views:
2,246
Visibility:
Public
Votes:
1
Category:
snapmirror
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • Cluster Peering
  • SnapMirror 

Issue

The cluster peer health show command displays session_reachable for Data Ping status for one or more node pairs in a cluster peer relationship. In the following example, local node NETAPP-02 reports a session_reachable Data Ping status between it and remote node DRNETAPP-01.

NETAPP01::> cluster peer health show
Node       Cluster-Name                 Node-Name

            Ping-Status                RDB-Health Cluster-Health Availability
---------- --------------------------- --------- --------------- ------------
NETAPP01-01
           DRNETAPP01                   DRNETAPP01-01
            Data: interface_reachable
            ICMP: interface_reachable  true      true           true
                                        DRNETAPP01-02
            Data: interface_reachable
            ICMP: interface_reachable  true      true           true
NETAPP01-02
           DRNETAPP01                   DRNETAPP01-01
            Data: session_reachable
            ICMP: interface_reachable  true      true           true
                                        DRNETAPP01-02
            Data: interface_reachable
            ICMP: interface_reachable  true      true           true
4 entries were displayed.

A session_reachable Data Ping status for one or more node pairs will cause the cluster peer relationship to report Partial availability, as displayed in the cluster peer show command.
NETAPP01::> cluster peer show
Peer Cluster Name         Cluster Serial Number  Availability    Authentication
------------------------- ---------------------  --------------  --------------
DRNETAPP                  0-00-000000            Partial         ok

The Partial availability of the cluster peer relationship may block certain operations in management software such as OnCommand System Manager or the 7-Mode Transition Tool (7MTT).

In most cases of a session_reachable Data Ping status, the issue will be intermittent and SnapMirror will continue to function; however, the session_reachable status might also be present with Cluster Session Manager (CSM) connection failures, cluster peer connection drops, or SnapMirror aborts, such as the following logs viewable via the event log show command:

Sun Jan 01 2016 00:00:20 -05:00 [cpeer.unavailable:ALERT] Peer cluster DRNETAPP01 is no longer available.

Sun Jan 01 2016 00:00:40 -05:00 [csm.sessionFailed:warning] Cluster interconnect session (req=NETAPP01-01:dblade, rsp=DRNETAPP01-02:dblade, uniquifier=0f01234567890abc) failed with record state ACTIVE and error CSM_CONNABORTED.

Sun Jan 01 2016 00:00:50 EST 2016 ScheduledUpdate[Jan 12 22:15:00]:12345678-1234-1234-1234-123456789012 action=Defer source=SVMSource:SourceVol destination=SVMDestination:DestinationVol status=Failure message=Failed to start transfer for Snapshot copy "snapmirror.01234567-1234-1234-1234-123456789012_0123456789.2016-01-01_000040".(Failed to start transfer.(Replication operation request failed from Cluster Id: 12345678-1234-1234-1234-123456789012, Node Id: 12345678-1234-1234-1234-123456789012 to Cluster Id: 12345678-1234-1234-1234-123456789012, Node Id: 12345678-1234-1234-1234-123456789012 due to a network error(CSM: An operation did not complete within the specified timeout window.)))

 

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.