Trouble Ticket 2 Documentation

Baselining and documentation are very important prerequisites to supporting and continuing to support networks. Add any additional notes to your drawings and tables and take time to redraw them if necessary. Often colored pens/pencils enable you to highlight different encapsulations, protocols, addres se s, settings, and such.

Logg ing and time stamps are extgemely helpful for documentation purposes. Tools such as Network Time Protocol (NTP), syslog, TFTP, FTP, and Simple Network Management Protocol (SNMP) are quite valuable when it comes to supporting internetworks. Put some of these tools to practical use as you perform the following tasks:

• Set up the duck router as the master timekeeper and have the other devices get their time from duck.

• Configure the devices so that they display log and debug output with a time and date stamp in milliseconds.

• Set up a syslog server such as the free 3CDaemon on hosta and configure the other devices to se nd their informational logs to the syslog server.

• Increase the size of your logging buffers.

• Perform a show tech-support and other baseline commands on your routers.

• Sav e a ll configure tions. Send them to a TFTPcFTP server of your choice. Thi s could be part of the 3 CDa emon that is renning on hosta. Alternatively, you can set up one of your routers as a TFTP server.

• Make sure you know where to locate specific data on Cisco's website to properly support all of your devices. Go back ang review C hapte r 2, "What's i n Your Tool Bag?" for more specifics. For no w, research the differences between a manual memory dump and an exception dump. Manually generate a memory dump from the duck router to the existing "ITTP serv en

• Don't forget about your hosts and servers. Make sure you know Layer 2 and Layer 3

add resses, gateways, routes, frame typeo, protocols, and so on . Refbr back to the previous chapters to assist you with this. Add this information to your diagram or create a separate "able.

• (Optional) Use a protocol analyzer such as Sniffer for your baseline. Use the Sniffer as well asshow and debug commands where you can to analyze all background traffic on your network. You need to know what normal is for your environment. Refer back to Chapter 2 for a ref^seer on protocol analysis with Sniffer Pro.

Look at the "Trouble Ticket 2 Documentation Lab Solution." Can you spot the issues? Better yet, can you fi x the Issues ? MaPe a li st of each issue that yo tt fix to compare it to the iss ue list and ending confignrarion i n the sFmole solutions. ojx everything you identify, anC use ping and trace to test all conngctivity. For example, m y 80-4 teingme rou ter) is a good ping tagget on the backbone, but use what you have. If1 you are really struggli ng, this Tcouble Ticket include s oamdi e output in a file named tf2 testing, and so does the next. Use this as a last resort. Now is your chance to apply methods and tools on your own.

Was this article helpful?

0 0

Post a comment