The connection on downlink port 1 subport b is linked but has failed to login

[James_GR]

Hello,

We have a Synergy frame that was sitting in storage for a while, now that we are installing the system, we encounter the following error. any advice would be appreciated.

• The connection on downlink port 1, subport b is linked but has failed to login to FC fabric.

configuration of parts:

 HPE Synergy 12000 Frame including:
- Composer2 appliance
- 4port FLM as well as all required connections for OOB management
- HPE Virtual connect 100Gb F32 modules in bays 3 and 6 (Fabric 3)
- HPE SY 660 Gen10
- 2x HPE Synergy 6820c 25/50Gb Converged Network Adapter installed on Mezzanine-3

QSFP28 to SFP28 adapter has been installed on port VC3/6:Q5  (also test on Q5:1 as per documentation) and a 32Gb SFP28 FC
transceiver, connected to Brocade 16Gb FC SAN switch (which in turn is connected to the DELL/EMC Unity storages.)

After alot of troubleshooting and  SAN switch logs, it seems that physical connections from
CNA ports to the SAN switches established, since the WWN for VCs and blades are logged in the SAN
switches and shows NPIV works, but SAN storage does not detect any new initiators nor any errors or logs.

Please note that i have upgraded all the firmwares on Synergy side with latest SSP and even tested on diffrent FC switch/Storage with the same result.

Since this doesnt look like a physical compatibility of FC switch and VC, is there any software configuration, solution or workaround for this issue?

Thanks

[Supreeth_B]

Hi @James_GR 

The error message you're seeing, "The connection on downlink port 1, sub-port b is linked but has failed to login to FC fabric," generally indicates a problem with the Fiber Channel (FC) connection or the login process between the device (Synergy frame) and the Fibre Channel fabric. This can be related to several factors, some common causes include port configuration issues, WWN mismatches, zoning problems, or hardware connectivity problems. By checking the configuration, cables, switch, and reviewing logs, you can isolate and resolve the issue.

If you are unable to resolve it, please reachout to the HPE Support team. They will assit you further.

Hope this information has helped you, Please click on the "Thumbs Up/Kudo" icon as a token of appreciation. Also, if this post has helped to solve your issue, consider marking this as an "Accepted Solution".

Regards,
Supreeth.

[James_GR]

@Supreeth_B  Thank you for your response,

For the past few weeks I have checked and double checked all the connections (cables, transceivers) and hardware ( SAN switch/storage), even went as far as taking the frame out of production Fabric network and setup a new SAN switch (IBM SAN-24B) without any special zoning configuration and changed to a new SAN storage. Tested all of this on a different standalone frame with the same exact hardware configuration and got the same result.

Issue doesn't appear to be login process of the Frame(s) to fabric network, since i can see the WWN for VC and (after i assign profile to blades) WWN for blades on the SAN switch console without any issue, OneView even reports the principal switch and neighbor switch as normal. There are no FC packet errors reported on SAN switch ports which generally means no hardware problems. Only problem is the error "The connection on downlink port 1, sub-port b is linked but has failed to login to FC fabric"  and SAN storage can't detect the blades therefore no Initiators to configure.

I have configured few other similar Synergy setups and never had this issue, although the only difference was they used QSFP28 transceivers (not QSFP adapter and SFP28)  and MPO cables for uplink ports. If you have any advice or if you could point me to other configurations/logs/tweaks i could test it would be much appreciated.

Thank you,
James

[Rama2]

Issue: The connection on downlink port 1, subport b is linked but has failed to log in to the FC fabric.

Physical connectivity appears to be good, but the SAN storage does not detect any new initiators.

Action's :

1. Disable and re-enable the port on the SAN switch.
2. After toggling the port, verify if the connection is able to log in.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.