Skip to main content
NetApp Knowledge Base

ONTAP SAN Multipathing issue not all HBA logged in

Views:
107
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • ONTAP
  • Hyper-V 2016
  • Brocade
  • HPE BL460c G9 c7000
  • QLOGIC QMH2672 FW:v8.08.232 DVR:v9.4.5.20

Issue

  • Microsoft Hyper-V HBA Storage adapters device does not detect all avaialble paths after motherboard and HBA replacment.
  • All Storage LIF's are up/up and availble to other hosts
 
Example:
Hyper-V
 
c:\mpclaim -s -d 1
MPIO Disk1: 02 Paths, Round Robin with Subset, Implicit Only
Controlling DSM: Microsoft DSM
Supported Load Balance Policies: FOO RRWS LQD WP LB

Path ID          State              SCSI Address      Weight
---------------------------------------------------------------------------
00000000123 Active/Optimized   003|000|007|000   0
TPG_State : Active/Optimized  , TPG_Id: 1003, : 8

00000000124 Active/Unoptimized 003|000|006|000   0
TPG_State : Active/Unoptimized, TPG_Id: 1002, : 9
 
ONTAP:
cluster1::> row 0;network interface show -data-protocol fcp
svm_windows
lif_svm_windows_1 up/up WWPN cluster1-01   e0c     true
lif_svm_windows_2 up/up WWPN cluster1-01   e0e     true
lif_svm_windows_3 up/up WWPN cluster1-02   e0e     true
lif_svm_windows_4 up/up WWPN cluster1-02   e0e     true

 

 

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.