Day One: Deploying Basic QoS

This book is part of the Day One Fundamentals Series, a growing library of network fundamentals that welcome engineers to the Junos OS and Juniper Networks.

The demands being placed upon today’s networks are growing at an incredible rate. Given the rapid increase in the number of attached devices, the explosion in traffic generated by these devices, and the convergence of legacy networks designed to carry a single type of traffic in isolation – the old approach of simply overprovisioning to support the potential peaks of data is no longer commercially or technically feasible.

To stop this perfect storm of a log jam, “Day One: Deploying Basic QoS” gives you an overview of Quality of Service (QoS) concepts and then provides tools and techniques from the Junos operating system toolbox to implement a comparatively simple class-of-service configuration. It’s a start, it works, and it can be done in your test bed on day one. And true to the principles of Day One network instruction, you’ll be guided through a set of basic requirements and configuration tools using multiple templates and examples from which you can derive your own valid configurations.

“This book is a must have for anyone seeking to configure QOS in any Juniper device due to its clarity, precision, and ease of use. It’s applicable to a wide range of engineers, from the Junos novice all the way to the expert. Guy can’t help but share his immense knowledge and practical experience, adding extra value to the topic and the book as a whole.”
- Miguel Barreiros, Senior Professional Services Consultant, Juniper Networks

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)

Guy Davies is a Senior Solutions Consultant in the Global PS Mobile Core Networks organization at Juniper Networks. He has worked for Juniper Networks for five years in the EMEA and Global PS organizations, helping Service Providers and large enterprises to build networks delivering large scale, high availability, and granular quality of service to their customers. Prior to Juniper Networks, Guy spent six years working for Telin- dus, a Systems Integrator, and prior to that five years at UUNET in the UK. In these roles Guy has delivered large scale MPLS and IP core and provider edge networks, subscriber management platforms, and AAA platforms, all of which have placed an ever increasing emphasis on differentiated Quality of Service. Guy is JNCIE-M #20.

Author Q & A

What got you started on this book?

I’ve always found that customers with whom I’ve worked have found QoS (and Junos CoS) to be one of the trickiest areas to understand and to implement well. It is probably one of the most changed aspects of each new Juniper Networks platform, so it can be challenging to follow the changes and variations, even for an employee. I knew that Miguel and Peter were writing a book on the subject that covered it in depth from a completely vendor agnostic perspective. With this book, I hoped to provide a more high level approach to get people to understand the steps to build a simple but functional CoS configuration in Junos.

Who is this book for?

This book is for Network Engineers and Architects who are new to QoS and/or new to Junos. It provides them with the basic tools and an explanation of what those tools are for. Equally, it is a useful high level explanation for anyone who may have inherited a network and wants to understand how the existing CoS should behave.

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

The reader should understand what behaviours they are trying to achieve and what tools are available to them to implement those desired behaviours.

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

I hope that the reader will gain an understanding of what QoS can and can’t do, what are the functions of QoS in general and the Junos operating system’s implementation in particular. I would also hope that the reader understands more clearly the generic aspects of Juniper Networks hardware architecture and how that impacts upon the QoS implementation. Ultimately, I hope that they go away and try this out in their labs and use the templates and examples to build a CoS configuration that enables them to operate their own networks more efficiently, offer new and innovative services and provide a great customer experience for their users.

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

Without question, once you’ve read this book there should be more questions in your mind :-) Many of the answers to those questions are likely to be in Miguel Barreiros and Peter Lundqvist’s book “QoS Enabled Networks: Tools and Foundations” published by John Wiley and Sons. They take a much deeper look into many of the issues upon which I’ve merely touched.

What’s your inspiration?

I love to learn more “stuff”. I work with an amazing group of people who are so smart and dedicated and by working with them, I am inspired to improve myself. I am very lucky to have been given the opportunity to expand into new technologies and to move outside my areas of traditional expertise while remaining at Juniper. I find being slightly uncomfortable or slightly out of your depth is a great way to avoid stagnation. Finding people who are better or stronger or smarter than you are and being able to learn from them is a fantastic way to learn and I’m always able to do that in my job here at Juniper.

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

Hmm, that’s tricky. I tend to be hypercritical of my own work because there’s nothing there I don’t know. I guess if there’s one tip that I use over and over with customers, it’s to use behaviour names, not application names for forwarding-classes :-) It seems like a trivial little point, but it is one of those things that can cause (or save) huge confusion later on for those maintaining the configuration.