fice, or even three, but the offices are small, and the net- works are simple. Even some larger companies do not have elaborate networks. No matter the size or complexity of the network, every aspect of it should be thoroughly documented. Chapter 33: Designing Networks 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 33- - -17. Matching last octet on multiple VLANs and switches Network Designs CHAPTER 34 IP Design When a network or group of networks is designed well, the payoff can be substan- tial. The payoff, however, is in hours not spent, which can be very hard to quantify. Believe me, though-designing IP space the right way, the first time, can save literally thousands of man-hours over the lifetime of the network. IP address allocation is rarely done properly, and many unlucky network administra- tors end up inheriting a mess of IP networks that's just been thrown together over time. In many cases, small networks are built with no vision of where the companies might end up, resulting in massive undertakings when the IP networks need to be changed. And even the best of IP address schemes can be rent asunder by a merger or acquisition. Think about how long it takes to put an IP address, subnet mask, and default gate- way on a server. Not long at all, when you're installing the server. Now think about what is involved when the IP address, subnet mask, or default gateway needs to be changed. The server must be taken offline, which usually involves a change control. In many environments, the change needs to happen during a change-control win- dow, which may involve you coming into the office or data center at 2:00 a.m. Now imagine that your company has 100, 200, or 1,000 servers. Don't forget that DNS and/or WINS and Active Directory will need to be updated, too. IP network design is not a glamorous project. It is not something that the CTO will slap you on the back for in a meeting. IP netw