cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1504
Views
0
Helpful
7
Replies

Nexus 2348UPQ with Bi-Di uplink question

jgardner150
Level 4
Level 4

Hello all,

We just purchased some 2348UPQ's with QSFP-Bidi's for the uplink option. They will be attached to a set of 6004's with Bi-Di on both sides. The one outstanding question I have is in regard to the up-link configuration that is need on the 6004's.

I want to know if the interfaces on the 6004's that are being used to attach the FEX's need to be broken out into 4x10gig interfaces. I already have a number of interfaces set up link this:

DC-6K-A# show run | in break
interface breakout slot 1 port 4-12 map 10g-4x
interface breakout slot 2 port 4-12 map 10g-4x

I know this is a requirement to up-link the 2248PQ's (using QSFP-40G-FE) I have in my environment already, but not sure on the 2348UPQ's with Bi-Di's...

 

Any help on this would be appreciated.

 

Thanks!

7 Replies 7

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

Have not used the Bi-Di cable yet, but I would say yes, you need to break out the 40Gig port on the 6k to 4 10Gig regardless of what type of cable you use.

HTH

jgardner150
Level 4
Level 4

Just wanted to post an update on this. I have physically installed the 2348's in the the environment and have tried to configure them on the 6K's however I am not able to get them to come online. I have tried using a native 40 gig port and also tried a 4x10gig port with the BiDi transceivers. After configuring them like any other FEX in my environment I show the interfaces as "down (Link not connected)" on the interfaces.

 

Through physical troubleshooting I found that the transceiver on the 6K side is not sending any light for some reason (6K see the transceiver and the interface is no shut).

I have a TAC case open to see what else I might be missing. Will update this once we find the resolution.

After working with TAC we came to the conclusion that we are hitting this bug:

CSCus89890 - Link state will not change after ISSU to 7.0 from 6.0(2)

 

Back in March I did an ISSU from 6.0(2)N2(4) to 7.0(3)N1(1) and then during the same maintenance window did another ISSU from 7.0(3)N1(1) to 7.0(5)N1(1). The bug title doesn't match exactly, but the behavior we are seeing in the same.

 
I have not tried the work around yet. As soon as we get through this I will be able to see if I can get the BiDi's working on either 1x40gig or 4x10gig....

Did you get the 2348UPQ to connect finally as I am having the same problem.

Thanks

 

I never got an offical answer on if it "should" work in 4x10gig mode from TAC, they told me they could not get it working that way in their lab environment. I did try to bring the FEXs up with 4x10gig after I worked around the bug I was hitting and no matter what I did I could not get it to work. I happened to have just enough ports in 40 gig mode so thats what I ended up using and they worked with no issue.

When it came online at 40gig were you able to support fcoe on 40 or is it still only capable on 10gig?

Thanks for the info.

I am opening a TAC case today and I will let you know what i find out.

We don't run FCoE in our environmnt so I can't answer to that. Hopefully TAC has good news for you.

Review Cisco Networking for a $25 gift card