Subtitles of the Movie

This may seem very ironic to say since this is all about networks and it's all about computers and since Network Administrators have computers around them all day long. But the best documentation for your servers and for your networks will probably be on pencil and paper. It will probably be the blue notebook or the red notebook that sits on the shelf and that way we know where it is. And any other Network Administrator that comes in can quickly look over that information. Now we may have backups up and we will certainly have information, that we pulled often the network itself, but we will probably also have a book that has information in it. And the information that we should have documented somewhere about our network should include all of the following and probably more - should include the Network Operating System and its version and any updates that we have applied, and these are Service Packs and Service Patches. Then we should include RAID configurations if we are using RAID. We should also include all the Server names that are in the network. And a note on Server names, don't use the name of the Server based on what the Server does - in other words don't name servers by what they do. Because if you do, then you are going to end up naming some servers like Web Server or DNS Server, and that is a security issue. Hackers would just love to have that information. So rather than provide it to them, name the Server by some type of a number code or letter code that only you know what that means - you and the other people that help around the network. Documentation should also include Anti-Virus software and the version of the Anti-Virus software, backup software and its version. The network address for each network interface card that has a static address, that way we can work with those addresses, and make sure that any static addresses are setup differently than any scopes that are setup with our DHCP. In other words, static addresses need to be kept out of the scope that a DHCP Server could use. DHCP (Dynamic Host Configuration Protocol) servers automatically issue IP addresses. We need to make sure that the static addresses that we are using, are not in any scopes that are the ranges of addresses the DHCP servers can issue. We also need to have a location and size of the swap file, the virtual memory that we are going to use. We need to have as much memory in the system RAM in the system as possible. SNMP community name - I am able to change that from public to something else, Server monitoring agents installed. Anything that we have installed as third party; anything that we have installed that is gathering information. System BIOS version and finally the Server Baseline measurements - those measurements of processor and memory and disk subsystem and network subsystem that we are going to use to compare the network when it is not functioning properly with the Server Baseline measurements, so that we can get an idea of what we might need to change. And sometimes, it is not that we did anything wrong and it is not really that anything is broken, maybe we are just outgrowing the network. As we said the only thing constant is change, and maybe we just need to upgrade the network. Maybe that is what our Baseline versus where we are at some point is telling us - that we are not really looking at exactly the same network as we where when we took that Baseline, because it has grown so much and so much has changed. So we need to understand upgrading, and we need to have an idea about how to upgrade the network both in real life as well as for the test. So we will discuss upgrading in our next chapter.