Nexus 7000 F2 Series Module Implementation

gdevos · ‎06-21-2012

What would the the step and concerns be when introducing the F2 series modules to my current chassis?

Do I need the fabric 2 module installed first before the installing I/O module?
After inserting the I/O module do the ports go to vdc 0 for allocation?
What else should I be considering?

Thanks in advance.

Oleksandr Nesterov · ‎06-21-2012

Hello

1. You can insert F2 modules with Fab1- they are interoperable. But to get maximum throughoutput you will need to install Fab-2

2. If you have other non-F2 modules in the chassis - you won't see F2 ports in the show-run as F2 requires separate F2-VDC

http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/60_nx-os_release_note.html#wp423808

3. You need to use at least NX-OS 6.0.1 release to have F2 support

HTH,

Alex

Leo Laohoo · ‎06-21-2012

Hey Alex,

Do you have the "logic" behind the reasoning that you can't mix F1, M1, and M2 cards with an F2?

Oleksandr Nesterov · ‎06-22-2012

Currently I would say it's hardware limitations between previous modules and F2.

Regars,

Alex

Leo Laohoo · ‎06-22-2012

Currently I would say it's hardware limitations between previous modules and F2.

Thanks Alex but it doesn't make sense since you can't mix the 2nd generation card, like the M2, with the F2 cards.

I am curious to know why because I don't want to respond to a question like this with the answer "Because Cisco said so" It makes me look stupid.

Oleksandr Nesterov · ‎06-23-2012

Hi

Number 2 in names M2 and F2 - means only generation number. But both these cards have ompletely different hardware realization.

Reason why F2 is not compatible with all other modules is that it has different forwarding engine which is not compatible with engines of other cards while communicating through the fabric. So that's why F2 modules should be placed in separate VDC whete they will talk only with other F2 cards.

Regards,

Alex

Leo Laohoo · ‎06-23-2012

Reason why F2 is not compatible with all other modules is that it has different forwarding engine which is not compatible with engines of other cards while communicating through the fabric. So that's why F2 modules should be placed in separate VDC whete they will talk only with other F2 cards.

Thanks for the explanation, Alex.

Was the design intentional to make the F2's forwarding card incompatible to the F1, M1 and M2?

Oleksandr Nesterov · ‎06-23-2012

Unfortunately I'm not aware about this details.

Leo Laohoo · ‎06-23-2012

Ok. Thanks Alex.

icox · ‎07-17-2012

There is a specific design issue on the ASIC used on the F2 module that prevents it from working with F1, M1 and M2.

Sent from Cisco Technical Support iPhone App

Leo Laohoo · ‎07-17-2012

There is a specific design issue on the ASIC used on the F2 module that prevents it from working with F1, M1 and M2.

So I guess Cisco won't try to remedy this "design issue" via NX-OS?

Rafael Mendes · ‎07-10-2013

Hello Guys,

I have this problem here.

I Have two nexus 7009 witch 2* N7K-M148GT-11L and 2 * N7K-F248XP-25.

While trying to allocate am getting the below error:

"ERROR: 1 or more interfaces are from a module of type not supported by this vdc"

To have all modules in a single VDC I would have to have all modules of type F2? There module F2 UTP 48 ports?

Example:

7K-1

N7K-F248XP-25

N7K-F2(Exists F2 module 48 UTP ports ????)

7K-2

N7K-F248XP-25

N7K-F2(Exists a F2 module 48 UTP ports ????)

Tks!

Leo Laohoo · ‎07-10-2013

To have all modules in a single VDC I would have to have all modules of type F2? There module F2 UTP 48 ports?

The legacy F2 card needs to be in a separate vDC. The legacy F2 cannot co-habitate in the same vDC with the F1, M1, M2. The legacy F2 can be in the same vDC with another legacy F2 or the newly-release F2e card.

Rafael Mendes · ‎07-11-2013

Hi Leo,

Ok, tks.