Skip to main content
NetApp Knowledge Base

Hosts are unable to login to FCP LIF on Brocade

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

​ ​

Applies to

  • ONTAP 9
  • FCP
  • Brocade Switches FOS v7.0 and prior

Issue

  • Check Active IQ if this impacts your systems
  • One or more hosts are unable to access one or more FCP LIFs on the storage system and are unable to login to the target LIFs
  • The problem occurs following a controller reboot or upgrades, power outage or may occur after some change in the fabric
  • Lun not getting mapped and initiators not logged into the storage post power outage
  • The storage system may log Fiber Channel fabric management server request failures with a reason code 0x5

Wed Jun 06 17:26:09 CEST [xx4-xx-c: fct_tpd_work_thread_0: scsitarget.hwpfct.mserr:debug]: The Fibre Channel fabric management server request (RFT_ID) sent from adapter 1b failed with reason code 0x5 (Server busy/cannot perform operation), explanation code 0x0 (No additional data), and response code 0x8001.

  • The switch shows that the LIF is logged into the fabric, but does not show FC4 enabled on the LIF

switch1:admin> nsshow
Type Pid    COS     PortName                NodeName                 TTL(sec)
N    010000; 3;50:0a:xx:81:xx:34:xx:78;50:0a:09:xx:xx:xx:56:78; na
    PortSymb: [46] "NetApp FC Target Adapter (8324) cluster1:0e"
    NodeSymb: [40] "NetApp FAS8080 (cluster1-01/cluster1-02)"
    Fabric Port Name: 20:00:xx:eb:xx:xx:xx:4d
    Permanent Port Name: 50:0a:09:81:12:34:56:78
    Port Index: 0
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Partial: No
N  010001;      3;20:00:00:a0:98:xx:xx:56;20:xx:00:a0:xx:12:xx:56; na
    PortSymb: [64] "NetApp FC Target Port (8324) fcp-svm:fcp-lif-01-0e"
    NodeSymb: [29] "NetApp Vserver fcp-svm"
    Fabric Port Name: 20:00:50:xx:xx:2b:xx:ed
    Permanent Port Name: 50:0a:09:xx:xx:xx:xx:78
    Port Index: 0
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Partial: No

  • In the example above, the LIF and port have logged into the fabric, but FC4 is not enabled. The entry for the LIF should show FC4s:FCP 

N  010001;      3;20:00:00:xx:xx:xx:34:56;20:04:00:a0:xx:xx:xx:56; na
    FC4s:FCP
    PortSymb: [64] "NetApp FC Target Port (8324) fcp-svm:fcp-lif-01-0e"
    NodeSymb: [29] "NetApp Vserver fcp-svm"
    Fabric Port Name: 20:00:50:eb:1a:xx:xx:ed
    Permanent Port Name: 50:0a:09:81:xx:xx:xx:78
    Port Index: 0
    Share Area: No
    Device Shared in Other AD: No
    Redirect: No
    Partial: No

  •  None connected status is seen in SAN initiator group tab on GUI/system manager

Additional Information

  • In FOS v7.0 and earlier, name server request RFT_ID for several NPIV ports is rejected with the reason 0x05 (Logical Busy)
  • The host cannot see the device if it does not retry the request. This can prevent the storage system LIF from using FC4 type. As a result, the initiator will not be able to login to the LIF

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.