Hi Muhammed,
Yes you are right Nexus 2000 devices need N5K or N7k to be worked.
Cisco Nexus 2000 Series Fabric Extenders are designed to provide connectivity for rack and blade servers, as well as converged fabric deployments. You gain a consistent, unified server access platform that scales across a range of connectivity solutions, including:
- 100 Megabit Ethernet
- 1 Gigabit Ethernet
- 10 Gigabit Ethernet (copper and fiber)
- 40 Gigabit Ethernet
With a broad range of configurations, Cisco Nexus 2000 Series Fabric Extenders offer:
- Architectural flexibility
- Highly scalable server access
- Simplified operations
- Business agility
Cisco Nexus 5000, Cisco Nexus 6000 and Nexus 7000 Series Switches, as well asCisco UCS Fabric Interconnect, act as parent switches for the fabric extenders.
The Nexus 5000 is Layer 2 only. That means any server VLAN to VLAN traffic between two different VLANs will need to be routed by another box, probably your Core and / or Aggregation Nexus 7000. You'll want some darn big pipes from the N5K to the N7K, at least until the N5K can do local routing (if ever).
The Nexus 2000 does no local switching. Traffic from one port on a 2K to another on the same 2K goes via the N5K. There should be enough bandwidth. That's why the Nexus 2000 is referred to as a fabric extender, not a switch.
The Nexus 2148 T is a Gigabit-only blade, 48 ports of Gig (not 10/100/1000) with up to 4 x 10 G fabric connections. Use the new 2248 TP if you need 100/1000 capability (the data sheet does NOT list 10 Mbps...).
You'll probably want to use PortChannel (LACP) for the fabric connections. Otherwise, you're pinning ports to uplinks, and if the uplink fails, your ports pinned to it don't work. (Like a module failure in a 6500?) You can now do the PortChannel to two N5K's running Virtual Port Channel (vPC). See the above link for some pictures.
HTH
Regards
Inayath
*Plz rate all usefull posts.
