"A separate VDC is needed when deploying the N7K-F248XP-25 modules in a chassis that also contains other families of modules (i.e. N7K-M1xxx and N7K-F1xxx).The VDC feature is enabled by the N7K-ADV1K9 license. A separate VDC is NOT required when the chassis contains only N7K-F248XP-25 modules."

F2 architecture is also based on SOC (switch on chip). It has a single Fabric ASIC though in comparison to F1 32-port 10g card. It also has all port wire rate with local switching. Also all ports wire rate through Fabric - but only with 2nd generation Fabric modules which Luciano talked in the begining.

It also should have improved L2 latency in comparison even with F1 module.

The F2 module is L2 and L3 capable. It is quite a step up from F1 as it has no L3 capabilites, plus adding FEX to the F2 is a great improvement. As far as F2 vs M1, the M1 still has larger L3 tables and can hold more routes in hardware as well as run OTV. So the two types of modules are for different locations in your data center. M1 is a great fit for your routing edge due to this.

Lucinao,

For fabric 2 on 7010 and 7018 you must have NX-OS 6.

As far as the new VDC requirement for F2. Since the Nexus 7000s modules all have their own forwarding engines they must all run in a compatible mode. Think of it like mixing a 6500 with sup2 and a module with a DFC3...you can't do it.

So instead of just saying your chassis can only contain F2 or F1/M1 we are able to seperate the "generations" up by VDCs within the same chassis.

The F2 module is L2 and L3 capable. It is quite a step up from F1 as it has no L3 capabilites, plus adding FEX to the F2 is a great improvement. As far as F2 vs M1, the M1 still has larger L3 tables and can hold more routes in hardware as well as run OTV. So the two types of modules are for different locations in your data center. M1 is a great fit for your routing edge due to this.

Lucinao,

For fabric 2 on 7010 and 7018 you must have NX-OS 6.

As far as the new VDC requirement for F2. Since the Nexus 7000s modules all have their own forwarding engines they must all run in a compatible mode. Think of it like mixing a 6500 with sup2 and a module with a DFC3...you can't do it.

So instead of just saying your chassis can only contain F2 or F1/M1 we are able to seperate the "generations" up by VDCs within the same chassis.

F2 architecture is also based on SOC (switch on chip). It has a single Fabric ASIC though in comparison to F1 32-port 10g card. It also has all port wire rate with local switching. Also all ports wire rate through Fabric - but only with 2nd generation Fabric modules which Luciano talked in the begining.

It also should have improved L2 latency in comparison even with F1 module.

Yes it supports FCoE (but Nx-Os to support that is subject for verification ) and multiple VDCs so what you thought of - is possible. The thing is that M1 will still stay there for adavanced IOS features like MPLS, OTV and LISP. Those will not be supported by F2. But F2 as I said adding Fabric Path and FCoE support in comparison to M1.

One thing - F2 will not work with M1 in same VDC - thus the new peer-link will be needed for F2.

Forgot to mention numbers before - with F2 fabric (all 5 fabric cards used) F2 card can do line rate - 48*10=480. Fabric is 550 capable. Though M1 still have more memory for L3 prefixes.

I have some wonder about do N7K-F248XP-25 require to use with FAB-2 or not? I try to do on Configuration Tool with FAB-1 and N7K-F248XP-25, no any error found. I also try to check for all DS, but no any reference about N7K-F248XP-25 require FAB-2 or not?