support hundreds of users. Such a network design is shown in Figure 35-10. Configuration concerns I'm not going to go through the detailed steps of configuring a corporate network here. Instead, I'll point out some elements you should consider when designing such a network, and try to point you in the right direction. I will be using a collapsed-core model with no distribution layer as an example. You can use Figure 35-9 as a reference. Trunks. Trunks may be necessary anywhere switches are interconnected. The obvious points are between the two core switches and the links connecting the access switches to the core. And don't forget the links between each pair of access switches. Network Designs Internet Server farm 00000 Users, printers, etc. Figure 35-10. Collapsed-core network consisting of only one layer You may choose to design your network such that the links between switches are IP links, not trunks. This is perfectly valid, and can make the network easier to understand for many people. If you do choose a Layer-3 network design, you will need fewer trunks. EtherChannels. I like to link my switches together with a minimum of two connections bound together by an EtherChannel. This provides a bit of resiliency and increases the bandwidth between the switches. Depending on your network, you may want to in- crease the size of the bundles to three, four, or even more. You may have servers that require EtherChannels as well. Check with your server group to see if this feature is required and, if so, how it should be configured. Check Chap- ter 18 for details on Virtual Port Channels (vPCs) that can span multiple devices using Nexus switches. Similarly, the 6500 VSS system can support Multichassis Etherchannel (MEC). If your core switches will have modules such as FWSMs that require dedicated links between failover pairs, you may need to design EtherChannels for these as well. For more information on EtherChannels, refer to Chapter 7. Spanning tree. Determine which ports will be user or server ports, and configure t