in addition to one for each physical interface. Every IP address you assign may need a DNS entry (including virtual IP addresses). Chapter 35: Designing Networks Which interface is primary? Does the server need a default gateway? If so, where does it go? Can the server support multiple defaults? How will this work? Web servers need a default gateway that points to the Internet. This will require your management VLAN to have spe- cific routes on the servers. How many physical network cards do you need in a server to support six Ethernet interfaces? Make sure you have enough. Extra interfaces are even better. Will the servers have both interfaces active in each VLAN, or just one? Some server high-availability solutions require the switches to be configured a certain way, while others require different configurations. Work this out in a lab before you build your network. Will your servers support remote Ethernet consoles? Will you need a dedicated network for this traffic? Switch 1 Switch 2 Trunk Upper layer Upper layer Lower layer Lower layer Server Mgmt VLAN Mgmt VLAN Figure 35-15. Ethernet interfaces in use on a server When you're figuring out your IP scheme, it's a good idea to make the last octet (or octets) the same for every interface on each server. In other words, if your upper network is 10.1.10.0/24 and your lower network is 10.1.20.0/24, make the last octet match for the server on each network. Thus, the upper IP address would be 10.1.10.10, and the lower IP address would be 10.1.20.10. Remember that you must assign an IP address for each interface, SO make the last octet match for each switch. Figure 35-16 shows how such an IP scheme might work. Network Designs Switch 1 Switch 2 Trunk 10.1.10.10 10.1.10.11 Upper layer Upper layer Lower layer Lower layer 10.1.20.10 10.1.20.11 Server Mgmt VLAN Mgmt VLAN 10.1.30.10 10.1.30.11 Figure 35-16. Matching last octet on multiple VLANs and switches Modern Virtual Server Environments Many data centers have migrated away from the rack-mount server scenario in favor o