With a thorough grounding in IP CoS concepts and terminology now under your belt, it’s time to get down to the particular CoS capabilities of Juniper’s enterprise routing products.
Although all Juniper routers run pretty much the same Junos software, the design of the router does lead to some operational differences and capabilities. Fortunately, the vast majority of CoS functionality is shared between all the platforms, and this section is structured accordingly—the common capabilities are covered first, followed by details regarding any specific exceptions or differences.
The discussion of CoS capabilities and default settings is presented in the context of the CoS packet processing steps available for transit traffic. This is done to provide structure and to reinforce your understanding of CoS processing stages within a Juniper router. You should refer back to Figure 10-6 as each CoS processing stage is discussed.
You configure CoS at the
class-of-service] hierarchy, which has quite a few options under
it. The primary CoS configuration options are displayed:
edit class-of-service[edit class-of-service] lab@Bock#
set ?Possible completions: > adaptive-shapers Define the list of trigger types and associated rates + apply-groups Groups from which to inherit configuration data + apply-groups-except Don't inherit configuration data from these groups > classifiers Classify incoming packets based on code point value > code-point-aliases Mapping of ...