Skip to main content
NetApp Knowledge Base

Host initiators didn't login backup to single FC port after upgrade due to faulty SFP

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

Applies to

  • Ontap 9
  • FC
  • AIX host

Issue

  • Post Ontap upgrade host initiators logged in back to all ports on all nodes except for one port 3b.
  • Login events are seen on all FC ports that these initiators are logged in.
  • But the initiators managed to stay logged in on all FC ports except for one port 3b.
  • Lot of login and missing login initiator events are seen for this affected port 3b.

[?]  Mon Jun 24 06:09:03 -0400 [nodeA: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '3b' by initiator port: 'c0:xx:xx:xx:xx:xx:xx:04' address 0xfxxxfd. The target virtual port is: 'NetApp FC Target Port (LPe16000) SVMFC01:nodeA_FC_3B'.
[?]  Mon Jun 24 06:10:08 -0400 [nodeA: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '3b' by initiator port: 'c0:xx:xx:xx:xx:xx:xx:04' address 0xcxxx1. The target virtual port is: 'NetApp FC Target Port (LPe16000) SVMFC01:nodeA_FC_3B'.
[?]  Mon Jun 24 06:17:27 -0400 [nodeA: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '3b' by initiator port: 'c0:xx:xx:xx:xx:xx:xx:04' address 0xcxxx1. The target virtual port is: 'NetApp FC Target Port (LPe16000) SVMFC01:nodeA_FC_3B'.
[?]  Mon Jun 24 06:19:10 -0400 [nodeA: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '3b' by initiator port: 'c0:xx:xx:xx:xx:xx:xx:04' address 0xcxxx2. The target virtual port is: 'NetApp FC Target Port (LPe16000) SVMFC01:nodeA_FC_3B'.
[?]  Mon Jun 24 06:33:33 -0400 [nodeA: bcomd: san.initiator.login:notice]: Missing login for initiator "c0:xx:xx:xx:xx:xx:xx:04", Vserver "SVMFC01", portset "2A_3B", has been logged on.
[?]  Mon Jun 24 13:18:33 -0400 [nodeA: bcomd: san.initiator.login.missing:notice]: Initiator "c0:xx:xx:xx:xx:xx:xx:04" is not logged in to any LIFs on this node for Vserver "SVMFC01", portset "2A_3B". Access to LUNs might be disrupted if a failover occurs.
[?]  Mon Jun 24 13:26:01 -0400 [nodeA: fct_tpd_work_thread_0: scsitarget.fct.portLogin:notice]: Login at target FC port: '3b' by initiator port: 'c0:xx:xx:xx:xx:xx:xx:04' address 0xcxxx1. The target virtual port is: 'NetApp FC Target Port (LPe16000) SVMFC01:nodeA_FC_3B'.
[?]  Mon Jun 24 13:33:33 -0400 [nodeA: bcomd: san.initiator.login:notice]: Missing login for initiator "c0:xx:xx:xx:xx:xx:xx:04", Vserver "SVMFC01", portset "2A_3B", has been logged on.

  • The last event that is seen for the affected port 3b is missing login initiators.
  • Fc port Rx & Tx are in optimal range

Node nodeA
Adapter 3b
Operational Status online
Extended Status ADAPTER UP
Received Optical Power 577.3 (uWatts)
SFP Transmitted Optical Power    604.7 (uWatts)

  • Port is up and is in connected state

   slot 3: Fibre Channel Target Host Adapter 3b
                (Emulex LPe16000 (LPe16004) rev. 13, <ONLINE>)
                Board Name:        1xcxcx1
                Serial Number:     Fxcxcxc9
                Firmware rev:      12.8.433.0
                Host Port Addr:    0c0e00
                FC Nodename:       5x:xx:xx:xx:xx:xx:xx:x1 (5xcxcxcxcxcxcxc1)
                FC Portname:       5x:xx:xx:xx:xx:xx:xx:x1 (5xcxcxcxcxcxcxc1)
                Connection:        PTP, Fabric
                Switch Port:       SWITCH:14
        SFP Vendor Name:   EMULEX
        SFP Vendor P/N:    AFxcxcxcxX
        SFP Vendor Rev:    
        SFP Serial No.:    ACxcxcxcx61
        SFP Connector:     LC
        SFP Capabilities:  4, 8, 16 Gbit/Sec

  • Rescan of HBA and reboot of host is done which didn't help.
  • Switch ports are healthy which are connected to host and storage.
  • Multiple hosts initiators are connected to this storage using switch and all these initiators are not logged in to this affected port 3b.
  • Same initiators are logged into other working FC ports.

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.