Skip to main content
NetApp Stage KB

Host not establishing iSCSI session with one controller on E-Series causes disk access failures

  1. Last updated
  2. Save as PDF

Views:
2
Visibility:
Public
Votes:
0
Category:
e-series-santricity-os-controller-software
Specialty:
esg
Last Updated:

Applies to

  • E-Series
  • Windows Server with SANtricity Windows DSM
  • iSCSI-connected environments with multipath/failover configurations

Issue

  • After a server reboot, disk access failures occur on a virtual machine using iSCSI-connected E-Series storage.
  • The following errors frequently appear in Windows event logs:
    • Source: iScsiPrt Event IDs: 1, 20, 34
    • Source: mpio Event IDs: 16, 17, 32
    • DSM Operational Log: xxxx-Multipath-Dsm IDs: 1067, 1450
  • Additional Findings:
    • dsmUtil.exe -a [WWN/iSCSIName] output on the specified host only lists Controller A, not Controller B.
    • Another host does not exhibit the issue.
    • Recovery Guru entries:
      • NON_PREFERRED_PATH (Code: 10)
      • HOST_REDUNDANCY_LOST (Code: 475), Affected host: <the specified host name>, Affected controller: Controller in bay B

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.