A network configuration table contains accurate, up-to-date records of the
hardware and software used in a network. The network configuration table should
provide the troubleshooter with all the information necessary to identify and
correct the network fault.
When a network configuration table is created
for troubleshooting, the contents will vary depending upon the type of device
that is documented. A minimum amount of data should be included for all
components:

- The type of device, model designation
- The device network hostname
- The location of the device (building, floor, room, rack, panel)
- If it is a modular device, include all the module types and in which module
slot they are located
- Data link layer addresses
- Network layer addresses
- Any additional important information about physical aspects of the device
Due to the complex nature of most networks, there is a great deal of
information that could be recorded. For simplicity and efficiency, network
configuration tables should group information based on the layers of the OSI
networking model.

Network documentation will vary depending on the purpose of the
documentation and the types of devices that are being documented. A
configuration table constructed for budgetary purposes might include serial
number, date of purchase, cost, vendor, and warranty expiration date. These
items would not benefit a troubleshooter and should be maintained in separate
tables.
Configuration table contents will also vary depending on the
features implemented on the devices. The Router ID is an important piece of
information to record about a router running OSPF. However, the Router ID would
not be recorded if only EIGRP was running.
Figure
displays an
example of a network configuration table for a router. Figure
documents an
example of a network configuration table for a switch.