Day One: Finishing Junos Deployments

When you are almost done with a deployment and see the straightaway to the finish dead ahead - when you begin racing towards the cutover - that's exactly when you need to take a deep breath and concentrate on the finishing touches.

"Is there anything important I neglected to do?" Experience has taught you that while it's probably a good deployment, you still need to consider whether anything is stopping it from becoming a great deployment.

Day One: Finishing Junos Deployments is a twofold book: first, it serves as a reminder for those all-important finishing touches that should be applied to any Junos OS deployment, and second, it describes how to implement those finishing touches on a network device running Junos OS.

"Martin Brown takes post-Junos deployments to another level in this excellent Day One book! We sometimes forget about attention to detail in routine configuration deployments and this book goes to great lengths to ensure that no configuration item, big or small, is overlooked. This book is a time saver, headache reliever, and the pre-deployment checklist is a must!"
- Scott Ware, Network Security Engineer, ITS Security Technologies

Sample Pages

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)

Martin Brown is a Network Security Engineer for a major telco based in the UK, and a Juniper Ambassador with knowledge that covers a broad range of network devices. Martin started his career in IT 20 years ago supporting Macintosh computers, became an MCSE in 1999, and has since progressed to networking, supporting most of the major manufacturers including Cisco, F5, Checkpoint, and of course, Juniper.

Author Q & A

What got you started on this book?

When I first started my career in networking, I found myself looking for information and getting frustrated that the information I was finding was very high level when what I really wanted was something that gave a brief overview keeping it simple and then examples of how it's done. Now I understand the technologies more I thought to myself that if it was frustrating for me, then surely others must be feeling the same, therefore I thought it was about time i did something about it. From that this book was born.

Who is this book for?

I've tried to aim this book towards network professionals who've not long started on their career path and who maybe have been asked to complete their first real deployment and they need a little extra help in some of the finishing touches.

After reading this book, what's the take away?

I hope that what readers will be able to take away from this book is confidence, not only that their deployment was a success but also confidence knowing that when they begin their next deployment this will be just as successful.

What are you hoping that people will learn from this book?

It is my hope that what engineers will learn from this book will be not only a better understanding of how network devices are typically monitored and how they are secured in an enterprise but that the reader will be able to gain practical experience too by following the examples on live equipment and then feel the need to experiment thus enhancing their experience further.

What do you recommend as the next item to read after this book?

This Week: Hardening Junos Devices. I feel security is important in any deployment and this book will help to make your devices more secure.

What's your inspiration?

The students I've helped mentor over the years, as silly as that may sound. I enjoy mentoring and teaching students and I do love standing in front of a class and teaching but sometimes it hits me that these future engineers are listening intently to me because they have a thirst for knowledge. They want to learn, they are incredibly keen and at that point would give anything to be standing where I am imparting their knowledge. I feel it's important to share what I have learnt and as long as there are engineers out there wanting to learn, then I am more than happy to share my experiences either face to face, in a classroom or in this case, in a book. After all, I was in their position once and even now, I am still learning.

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

SNMP. It took me a while to understand SNMP and I could never get it to work when I first started an engineer. This section is really a statement to say "It didn't beat me".