Content

| 1.3 |  | Building-Block Approach |
| 1.3.1 |  | Identifying the components of an end-system configuration table |

Network documentation can be a valuable tool for troubleshooting. However, a network is not complete without end-systems. An incorrectly configured end-system can have a negative impact on the overall performance of a network. This section discusses the creation of configuration documentation for the purposes of troubleshooting end-systems connected to a network. The information contained in this section assumes a scenario where network devices have already been documented but the network administrator is unfamiliar with the configuration. Therefore the end-system portion of the network documentation will need to be created from scratch.

End-system devices such as servers, network management consoles, and desktop workstations play a large role in the way a network operates and, therefore, should not be ignored. Maintaining relevant documentation about the configuration of end-systems provides a complete picture of the network and allows intelligent decisions about any modifications or upgrades that end-systems may require. The inclusion of end-system network configuration information in the baseline will enable troubleshooting of problems in a timely and efficient manner.

An end-system network configuration table is baseline documentation that shows accurate records of the hardware and software used in end-systems.

When creating an end-system network configuration table for troubleshooting, the following should be documented:

- Device Name (Purpose)
- Operating System/Version
- IP Address
- Subnet Mask
- Default Gateway, DNS Server, and WINS Server Addresses
- Any High-Bandwidth Network Applications that the End-System Runs

An end-system network configuration table will contain different components based on its use. Some tables are used administratively for inventory. Some simply list the physical location of the device and perhaps a note about when it needs to be backed up, while others are used as a tool for troubleshooting.

An end-system network configuration table used for troubleshooting typically varies, depending on the device being recorded. There are many different types of end-systems and, therefore, there is quite a bit of information that can be recorded. To simplify things, it can be helpful to divide the recorded information into categories based on the relationship the component has with the layers of the TCP/IP model. It is important to find out what the most useful pieces of information are for troubleshooting particular end-systems.

Recording network applications that are available on an end-system is also useful information to include on an end-system network configuration table. Additionally, record any high-bandwidth network applications that are running on the end-system, because they can have a large impact on network performance. Examples of high-bandwidth applications are streaming video, such as QuickTime, and multicast applications, such as IP/TV.

Figure provides an example of an end-system configuration table using the following categories to document the network-related properties of a device:

- Device Name (Purpose)
- Operating System/Version
- IP Address/Subnet Mask
- Default Gateway Address
- DNS Server Address
- WINS Server Address
- Network Applications
- High-Bandwidth Applications