Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

FC link not coming up on target ports

Views:
375
Visibility:
Public
Votes:
1
Category:
fabric-interconnect-and-management-switches
Specialty:
san
Last Updated:

Applies to

  • AFF/FAS Systems
  • Brocade Switches

Issue

  • FC link not coming up on target port.
  • The sysconfig -a output shows as following (highlighted in yellow).

CLI command - system node run -node <node name> -command sysconfig -a

Example:

slot 5: Fibre Channel Target Host Adapter 5b
                (Emulex LPe32000 (LPe32004) rev. 12, <LINK DISCONNECTED>)
                Board Name:        111-03648
                Serial Number:     FP01142277
                Firmware rev:      12.2.390.0
                Host Port Addr:    000000
                FC Nodename:       50:0a:09:80:80:23:6f:90 (500a098080236f90)
                FC Portname:       50:0a:09:82:80:23:6f:90 (500a098280236f90)
                Connection:        No link
                Switch Port:       Unknown
        SFP Vendor Name:   AVAGO
        SFP Vendor P/N:    AFBR-57G5MZ-ELX
        SFP Vendor Rev:    
        SFP Serial No.:    AD2003G02U1
        SFP Connector:     LC
        SFP Capabilities:  8, 16, 32 Gbit/Sec

  • Ensure a supported SFP is used and same can be verified from NetApp Hardware Universe.
  • In the EMS logs, following events are observed:

Thu Mar 04 16:41:01 +0000 [XXXXXXXX_01: fct_tpd_work_thread_0: scsitarget.slifct.linkBreak:error]: Link break detected on Fibre Channel target HBA 5b with event status 1 , topology type 1, status1 0x0, status2 0x0.
Thu Mar 04 16:41:01 +0000 [XXXXXXXX_01: nvmf_master_0: nvmf.spdk.err:debug]: fc_adm_api.c:2263 port link break: HW port 1 already offline. rc = 2 
Thu Mar 04 16:41:22 +0000 [XXXXXXXX_01: fct_tpd_work_thread_0: scsitarget.hwpfct.linkUp:notice]: Link up on Fibre Channel target adapter 5b.

  • Based on the planned cabling schematics, output of portshow indicates that the WWPN of device connected is different than the one which is listed in the sysconfig -a output:

Example:

sysconfig -a output:

slot 5: Fibre Channel Target Host Adapter 5b
                (Emulex LPe32000 (LPe32004) rev. 12, <LINK DISCONNECTED>)
                Board Name:        111-03648
                Serial Number:     FP01142277
                Firmware rev:      12.2.390.0
                Host Port Addr:    000000
                FC Nodename:       50:0a:09:80:80:23:6f:90 (500a098080236f90)
                FC Portname:       50:0a:09:82:80:23:6f:90 (500a098280236f90)
                Connection:        No link
                Switch Port:       Unknown
        SFP Vendor Name:   AVAGO
        SFP Vendor P/N:    AFBR-57G5MZ-ELX
        SFP Vendor Rev:    
        SFP Serial No.:    AD2003G02U1
        SFP Connector:     LC
        SFP Capabilities:  8, 16, 32 Gbit/Sec

portshow output:

switch:admin>  portshow 19
portIndex:  19
portName: port19
portHealth: Fabric vision license not present. Please install the license and retry the operation.
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x24b03       PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType:  18.0
POD Port: Port is licensed
portState: 1    Online
Protocol: FC
portPhys:  6    In_Sync         portScn:   32   F_Port
port generation number:    24
state transition count:    15
portId:    3e1300
portIfId:    43020001
portWwn:   20:13:00:05:33:6a:0b:b0
portWwn of device(s) connected:
        10:00:00:10:9b:96:64:ab
Distance:  normal
portSpeed: N8Gbps

  • As you can see from the above example, the WWPN of the Target Port 5b and the WWPN of the device connected on Switch Port 19 are different, which indicates an incorrect device is plugged in to the switch.

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support