Subtitles of the Movie

Newer computer installations use a Server rack so that all the components are kept safe and can be worked on in a much easier fashion then if we had separate boxes for each type of Server, or each component for the network. When we purchase a Server rack, we need to follow all of the instructions that are provided by the rack manufacturer if we are the one who are going to install it. In some cases when we purchase the Server rack, the installation of the rack itself is provided by the vendor. If we are going to install the rack, then we need to make sure that we follow all of the instructions for that particular rack. Because we are going to be putting some very expensive equipment on the rack and we want to make sure that it's anchored properly, and that it is safe and secure for that equipment. There are also special components and cable managers that are provided for the future management of that rack. In other words, it's possible to swing a door and be able to get to electronics or to slide a drawer out and be able to change our cards. There are some really nice Server racks and very nice easy to manage components that can go into Server racks. So we need to setup our Server with the realization and the assumption that we are going to be working on things and making changes in the future. So we want to take our time, do the installation properly so that we make sure that all of the components can be reached without having to pull cables out and without having to take one component out to get to another one. There is the easy way and there is the hard way. We also want to check for all the components to make sure that everything is working right the next time that we do a power-on self-test. In other words, a power-on self-test recognizes all of the components that are connected to a computer, that are inside a computer in the case of a workstation. But in the case of a Server, if they are connected so that they can be seen by BIOS, then we want to take a look at the power-on self-test to make sure that all of the components that are supposed to be seen are in fact seen. And then document all of the configurations. If we have got something and we've got it installed and it's working, then we need to write that down as to how things are connected. Write it down on paper so that if we decide later on to make a change and we take things apart and then our new plan doesn't workout quite like we thought it would, then we got the documentation as to how it was setup in the first place and we can go back to where we were. That may seem like commonsense, but unfortunately commonsense isn't used commonly. Because in many cases when we try to upgrade our network, which we will talk about later on, we end up taking steps away from something that worked. And not leaving us a trail of breadcrumbs that we can follow. In other words, not leaving ourselves a map back to where we were, in case what we are thinking about doing doesn't work out. So we want to document all the configurations, so that we know how things were setup and how that was working for us. Because we are going to make changes and we are not done when we do the installation, because the next step is to configure everything so that it does what it was intended to do. And we will start discussing configuration in our next chapter.