Skip to main content
NetApp Knowledge Base

LUNs not visible on Hyper-V host after Datacenter migration

  1. Last updated
  2. Save as PDF
Views:
12
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • NetApp FAS8200
  • ONTAP 9.7P4
  • Microsoft Hyper-V host
  • SAN/FC

Issue

  • All Fibre Channel (FC) LUNs from NetApp FAS8200 were not visible on Hyper-V servers after a data center migration.
  • Hyper-V virtual machines could not power on due to lack of FC communication.
  • FC adapters and initiators were not detected by ONTAP (fcp adapter show and vserver fcp initiator show returned empty).
  • Storage-side configuration and LUN mappings appeared correct, but no FC initiator logins were seen.
  • FC LIFs showed status up/- (admin up, operational status indeterminate).
  • FC ports reported PortSpeed: 0Gb/s, PortStatus: offline.
  • Error when creating new LIF on FC port:

Error: command failed: 0g is an invalid port on node IOB-CHN-SAN01.

  • Issue began immediately after data center migration.

    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.