UCS 5108 Blade not recognized by 6332 FI's

[eran94]

Hi all,

I recently purchased a 6332 FI, Nexus n9k switch, and a 5108 chassis with 8 b200 m5 servers. I have 4 of the breakout cables that were used by the school when they had it deployed for training, and those I am running from Port 1 and 2 on the FI to ports 1-8 on the back of the IOM module in the chassis. However it doesn't look like the blade chassis is getting recognized by the FI whatsoever. Any idea what could be causing this? I have FI A and B off of a fresh erasure so they don't have any old configurations on them. 

If i set port 1& 2 to breakout mode, it completes, reboots, then when it comes back online, it shows those as scalability ports, but the chassis still isnt available to acknowledge. If I try to set port 1/1/1, 1/2/1, 1/3/1, 1/4/1 to server mode, it restarts the FI and goes back to the old settings. 

The cable for reference is the QSFP-4SFP10G-CU5M, which breaks out into the 4 SFP cables.

[Steven Tardy]

Everything I can see on the spec sheet and the tgmatrix and release notes looks like this combination should work.

There have been scenarios where longer copper cables (5M, 7M 10M) won't work.
Don't know if this is one of those scenarios or not.

Do the links come up (turn green) ever or do the ports stay down?
What UCSM version on the FIs?
I'd upgrade to the latest-greatest, but can't point out a specific bug/CDET which may cause this.

Configuring Ethernet Breakout Ports on UCS 6300 Fabric Interconnects  

[eran94]

So what is strange here is that on the IOM 2208XP, all the link lights go green when the breakout cable is connected. When the QSFP+ is connected to the FI, the link light goes out on the FI, and only on the FI. This happens on both FI's(I tested by having it in standalone, then cluster, then standalone again but erasing the config and having each standalone as the primary).

On the FI's, I updated the firmware to 4.3.6h

When I configure the breakout port option(I've tested on all the applicable ones that the 6332 supports), but lets say for explanation sake, I configured on port 1 and 2, the FI reboots. Once the FI comes back up, I see those ports showing up under ethernet ports as "Scalability ports". If I choose the sub port 1/2/3/4 under port 1 as server ports, the FI reboots and erases that entire configuration.

[BrianSekleckiGE]

I concur: OSI layer troubleshooting.  Keep us in the loop.

Try validating the [ QSFP-4SFP10G-CU5M ] externally, by testing on a normal Cisco Nexus 9K (nexus 9272 with QSFPs, etc.).

Try using a USB<->10GB-SFP ethernet adapter to validate the SFP side of each breakout cable; that: 1) The link establishes at 10GB 2) Wireshark to verify that the FI is sending LLDP/CDP discovery.