I'm here. Should have posted this Friday but in any case if it still applies...
The last chapter discussed management of network documentation. So let's say you take a new job and the guy you just took over managed THE INTERNET. Well unfortunately for you he didn't document anything thing like VLAN's, hardware, addresses or any of that stuff. Now you have to go through the network and figure it out for yourself and the internet is pretty big... So by doing the guy after you and yourself a favor by documenting everything nobody will be left with large headaches. Some things it mentioned to document but I never realized is baseline stats of servers so you would measure let's say the load on the CPU, RAM and harddisk and then for future reference if the numbers have changed you know that something is wrong.
Optimizing your network. Assuming you run a big network you'll have a lot of different traffic moving through. You wouldn't want people playing video games getting priority over people who are making calls over VOIP. By using QoS (Quality of Service) you determine what packets have a high priority and those that don't. So naturally VOIP would be high on the list. Videos would probably somewhere low so in case of high traffic situations video packets may be dropped. For web-hosting you may want to use load balancing so when millions of people are accessing your website they aren't all punishing one server and instead are spread out over all your web servers. Lastly you want fault-tolerance so if and when a server or hard drive fails customers can still get access to their data.
Something I noticed while reading other peoples blogs, that's what I do at night sitting in front of the glare of the monitor anyways, I read it in their voices. Voices in my head! Also free Portal if I didn't already mention it. Which I did.