Day One: Monitoring and Troubleshooting

This Day One booklet advocates a process for monitoring and troubleshooting your network. The goal is to give you an idea of what to look for before you even type in a show command. By book’s end, you should know not only what to look for but also where to look.

(Day One: Junos Monitoring and Troubleshooting) shows you how to identify the root causes of a variety of problems and advocates a common approach to isolate the problems with a best practice set of questions and tests. Moreover, it includes the instrumentation to assist in root cause identification and the configuration know-how to solve both common and severe problems before they ever begin.

Download Book

Day One books are a free download for our J-Net members*. If you’re not a J-Net member, create a user account now. It’s fast and there’s no commitment or spam. Once you’re a member you can come back and download any of the Day One books.

Download: J-Net Member
Download: Not a J-Net Member

* If you have an existing Juniper user account, you can use it to login to J-Net

About the Author(s)

Jamie Panagos is a Senior Network Consultant for Juniper Networks and specializes in the design, implementation, and operation of datacenter, enterprise, and service provider networks.

Author Q & A

What got you started on this book?

I got started on this book because I craved the opportunity to provide guidance and assistance to those new to Junos and networking. I got started on this book because I craved the opportunity to provide guidance and assistance to those new to Junos and networking.

Who is this book for?

This book is targeted to the new network operator and those with experience in networking, but who are new to Junos.

After reading this book, what will the reader learn or know?

After reading this book, the user will be able to develop a ground-up approach to troubleshooting based on the OSI model, harness the power of Junos to more accurately and efficiently monitor and troubleshoot their network and most importantly, reduce downtime.

What do you recommend as the next item to read after this book? What are your plans for more?

After reading this book, I would recommend the Junos Cookbook.

What was your inspiration?

One of the advantages of working in a Professional Services environment is exposure to many different networks, many different operators and many different management methods. This exposure, in conjunction with years of network operation and engineering, inspired a book that would assist in efficient and accurate network monitoring and troubleshooting.

What’s your favorite bit/part in the book?

My favorite part of the book is the constant reminder that monitoring and troubleshooting should be based on the OSI model. Too much time is wasted attempting to identify and fix layer-2 problems at layer-3. This concept alone can save network operators significant time and money.

How hard was it to write? Tell us how and when you wrote it?

The content itself was not too difficult and after discussions with other authors, was in-line with my expectations. What was difficult was the editing process. With all of the iterations of editing, it becomes difficult to continue reviewing the material both thoroughly and fairly. Additionally, specific to the Day One series, writing in a concise, yet effective and meaningful manner proved to be more challenging than I expected. I was lucky enough to get a lot of on-hours time to work on the book, though a significant amount of the development and editing was completed on off-time and planes.

Did you create a test bed for the book? How much set up did it take?

Yes, I utilized a test-bed to collect all of the configuration and instrumentation discussed in the book. The most difficult part was accessing all of the different hardware and connection types to meet the needs of the book. The setup itself was fairly minimal as few of the examples referenced complex systems.

Who tech reviewed your book?

Nathan Alger, Lionel Ruggeri, and Zach Gibbs provided valuable technical feedback several times during the development of this booklet. Thank you! Your assistance was greatly appreciated.

Who would you like to thank?

I would like to thank Cathy Gadecki and Patrick Ames for guidance, patience and support. Like all of the other authors, I have a day job, and their understanding of this factor makes the entire process less stressful and much more attainable. I would also like to thank my reviewers, Lionel Ruggeri (Juniper), Nathan Alger (Juniper), Zach Gibbs (Juniper), Mike Peterson (Level3) and Phil Heller (Verne Global). Finally, my manager Craig Sirkin understood the value and importance of this book and afforded me as much time as possible to work on it and deserves great thanks.