M7i and J-Series CoS Capabilities
With a thorough grounding of 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, specifically the M7i and J-series service routers.
Although both the M7i and the J-series run pretty much the same JUNOS software, the ASIC-based HW design of the M7i versus the software-based J-series does lead to some operational differences and capabilities. Fortunately, the vast majority of CoS functionality is shared between the two 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 9-6 as each CoS processing stage is discussed.
You configure CoS at the
[edit 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 ...