Skip to main content
NetApp Knowledge Base

FCP Lif operationally down with extended status as "LIF not initialized" post changing mode from CNA to FC

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

Applies to

  • Ontap 9
  • FCP
  • Cisco SAN Switch

Issue

  • FCP Lif operationally down and admin up with extended status as "LIF not initialized" as per network interface show output post changing from CNA mode to FC mode.

Extended Status: LIF not initialized
Operational Status: down
Administrative Status: Up

  • FCP port hosting the lif is up and running as per fcp adapter show command.
  • The current mode set is "FC" and type is set as "target" as per ucadmin show output
  • The physical port is logged in on switch end under flogi database. If the required device is displayed in the FLOGI table, that means the fabric login is successful. This can be checked using command # show flogi database interface <switchportwhere storage port is connected>
  • Zoning is configured using the lif wwpns on switch end as per NetApp's recommendation.
  • FCP service is allowed on the vserver under "allowed protocols", the same can be verified using command vserver show -vserver fcp-svm -fields allowed-protocols

 

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.