es, many of them seem to have some pretty significant limitations. For example, as of version 5.0 of NX-OS, the 5010 and 5020s don't support SVIs or routing, and support only 512 VLANs. These limitations can seem maddening, and rightly SO. Still, the switches were designed for one purpose, and that is to connect many servers to the switching (and storage) fabric in a data center. For this purpose, they work very well. Just don't think you' 'll use a pair of 5000s as the core in your Enterprise LAN, as they simply aren't designed for that purpose. The newer 5548 does support L3 with the addition of a field-upgradable daughter card. It also supports over 4,000 VLANs, 16 ports per port channel, and a variety of other enhancements. My advice, if you're looking at Nexus 5000s, is to go for the newer models. The 5000 series of switches marks a serious departure from traditional 1 RU switches in the Cisco lineup; they must be mounted in a server rack. Though the previous photos do not make it readily apparent, these switches are very deep and will fill the entire Nexus Hardware depth of a server cabinet. These switches simply cannot be mounted in standard two- post telecom racks. Remember, they were designed for use in a data center, and that's really where they belong. Figure 18-5 shows a Nexus 5010 underneath a Catalyst 2950 for scale. Notice the depth of the 5010. The 5010 is about three times deeper than the 2950. The 5000-series switch contains four RJ-45 connectors on the left side. These are la- beled Mgmt-0, Mgmt-1, L1, and L2. The only port that is configurable at this time is the Mgmt-0 interface. The rest are there for future expansion. The console port works as you'd expect. These four ports are found on the opposite end of the 5548 switch. Figure 18-5. Catalyst 2960 on top of a Nexus 5010 The Nexus line is designed to be highly available. To that end, the dual power supplies and single fan tray are hot-swappable. Figure 18-6 shows a Nexus 5510 with its power supplies and fan trays removed. Nexus 2000 The Ne