Skip to main content
NetApp Knowledge Base

Iscsi session connection not established during MCC-IP Installation/Head Upgrade

  1. Last updated
  2. Save as PDF
Views:
32
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster-IP
    • Head Upgrade
    • Installation
  • Systems using shared Cluster/HA ports

Issue

May 02 03:36:33 [localhost:config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.
May 02 03:36:33 [localhost:callhome.dsk.config:error]: Call home for DISK CONFIGURATION ERROR

Waiting for requisite number of local mailboxes... (Press Ctrl-C to abort wait)

  • The connections are not established with the iSCSI sessions:

May 02 03:26:02 [localhost:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.2016-06.com.netapp:ddXXXXdd-600X-11xx-8fxX-d039eXXXXXXX (type: dr_partner, address: 10.2.2.1:65200). Reason: session login timed out.

May 02 03:26:02 [localhost:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.2016-07.com.netapp:ccXXXXX0-600x-11xx-9fxx-d039eXXXXXXX (type: dr_auxiliary, address: 10.2.2.2:65200). Reason: session login timed out.

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.