Anerror has ocurred on connection X, interconecct MX., interconnect 3 port 18 subport is..

[NicolasQ]

Hello everyone,

We are experiencing an issue with an HPE Synergy 12000 chassis configured with a Virtual Connect 3. The servers HPE SYNERGY 480 G10 located in bays 4, 5, and 6 are having connectivity problems: the assigned network ports are in an unlinked state, even after several profile adjustments and manual port unlocks via HPE OneView.

THE ERROR: AN ERROR HAS OCURRED  ON CONNECTION 3. INTERCONNECT MX.. INTERCONNECT 3, PORT X SUBPORT X IS UNLINKED. LOCKED

It’s worth noting that we do not have an active support contract with HPE, and the current firmware version on the servers is 6.30.

Actions Taken:

1. Adjusted profiles by assigning a network adapter to Virtual Connect 3.
2. Attempted manual port unlocks through HPE OneView.
3. Moved the servers from bays 4 and 5 to bays 7 and 8. We didnt move the other server in bay because is in production.

Results:

• In bays 7 and 8, the servers are operating normally, and the ports are in a linked state, suggesting the servers and Virtual Connect 3 are functional in these positions.
• In bays 4, 5, and 6, the ports remain unlinked, which points to a potential physical issue with the backplane or a logical problem with the Virtual Connect 3 ports assigned to these bays.

Questions:

1. Has anyone experienced a similar issue where specific bays fail to link network ports in HPE Synergy systems?
2. Could this be related to a hidden configuration or firmware issue affecting the problematic bays?
3. What additional steps would you recommend before considering hardware intervention, especially given the lack of an active support contract?

Any guidance or shared experiences would be greatly appreciated. Thank you in advance!

[MV3 · Accepted solution]

Hello,

The link failures on specific bays require an LE dump analysis. Were these hosts removed and reseated multiple times? This will help rule out any potential physical damage to the midplane.

Please check if there are any errors reported on ICM Bay 3 and verify if the ICM in Bay 3 is reporting as configured.

The most effective approach to resolve this issue is to engage HPE for log analysis.

Best regards,

[support_s]

Hello,

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

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

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