Skip to main content
NetApp Knowledge Base

Paths to the Linux Oracle don't work in SM-BC environment

Views:
206
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
san
Last Updated:

Applies to

  • SAN
  • Oracle Linux
  • ONTAP 9
  • SM-BC(SnapMirror Business Continuity)
  • Cluster peer relationships in a customer(non-default) IPspace

Issue

  • Paths to the Linux Oracle don't work in SM-BC environment.
  • Oracle Linux servers are unable to determine and configure multiple paths to the LUNs(with SM-BC) and report I/O errors for remote paths:

Jun 17 15:26:26 linux kernel: sd 8:0:5:71: alua: port group 13e9 state N non-preferred supports TolUsNA
Jun 17 15:26:26 linux kernel: sd 8:0:4:71: alua: port group 13e8 state N non-preferred supports TolUsNA
Jun 17 15:26:46 linux kernel: sd 8:0:4:71: [sdh] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun 17 15:26:46 linux kernel: sd 8:0:4:71: [sdh] tag#4 Sense Key : Not Ready [current]
Jun 17 15:26:46 linux kernel: sd 8:0:4:71: [sdh] tag#4 Add. Sense: Logical unit not accessible, asymmetric access state transition
Jun 17 15:26:46 linux kernel: sd 8:0:4:71: [sdh] tag#4 CDB: Read(10) 28 00 00 00 00 80 00 00 80 00
Jun 17 15:26:46 linux kernel: print_req_error: I/O error, dev sdh, sector 128

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.
Scan to view the article on your device