CCNA Class Of Service Questions

The network-control forwarding class carries control plane traffic, including routing protocol messages and management access, and is mapped to a queue with strict-high priority by default. This matches the stem's requirement for the standard class reserved for routing and management traffic.

Junos applies behaviour aggregate classifiers first, then multi-field classifiers, which can override the BA result. This ordering satisfies the stem's scenario of both classifier types on one ingress interface, letting MF classification take precedence for finer-grained matching.

A behavior aggregate (BA) classifier maps a single field, such as the DSCP value in the IP header, directly to a forwarding class and loss priority. Because the uplink traffic already carries DSCP markings from the core and you must classify solely on those bits, a BA classifier applied to the interface is exactly the right tool for this scenario.

The exp classifier matches the MPLS experimental bits, the three-bit field in the label stack header used for QoS marking. Specifying exp lets the classifier inspect those bits directly, satisfying the requirement to classify traffic by MPLS EXP value rather than by IP DSCP or 802.1p.

A forwarding class is an internal queue abstraction that groups packets sharing the same CoS treatment. Classifiers map traffic into forwarding classes, and schedulers then apply bandwidth and drop behaviour per class, controlling how each group is processed.

Junos permits one rewrite rule per type per logical interface, so a DSCP rule and an ieee-802.1 rule coexist without conflict. Remarking errors therefore stem from elsewhere, since these two rule types operate on different header fields simultaneously.

A drop-profile defines the drop behaviour applied by a scheduler, specifying drop probabilities at given buffer-occupancy thresholds. It controls when packets are discarded and in what proportion as queue depth rises, delivering weighted random early detection rather than simple tail drop.

A behavior aggregate classifier maps specific DSCP code points to forwarding classes and loss priorities in a single lookup. Defining entries for AF11, AF21, and AF31 lets the router classify each packet on ingress by its DSCP value alone, which is precisely what the customer requires for assured forwarding with distinct per-class treatment.

Aggregate level shaping caps the combined bandwidth consumed by every queue beneath that scheduler node, rather than policing individual queues. This satisfies the requirement to limit total traffic across all queues associated with the scheduler map on the MX Series interface.

A single-rate two-color policer uses a token bucket with a committed burst size. Traffic can burst up to the burst size without being dropped, as long as the average rate does not exceed the committed information rate. The short periods of exceeding 100 Mbps are within the burst allowance, so packets are not dropped. This behavior is expected and matches the scenario.

A two-color policer classifies each packet against a single rate and burst threshold, marking it either green (within the committed rate, forwarded) or red (exceeding it, discarded or re-marked). No yellow state exists without a three-color policer.

transmit-rate sets the assured bandwidth a scheduler guarantees to its queue, expressed as an absolute rate or percentage. It is a valid scheduler parameter, defining the minimum throughput allocated to traffic mapped to that forwarding class.

The transmit-rate 10m configuration sets a guaranteed minimum bandwidth of 10 Mbps for the best-effort queue. When other queues are idle, the scheduler allows this queue to use additional bandwidth up to the interface capacity or the shaping rate, satisfying the requirement to allow bursting. This is the correct way to provide a guaranteed rate with excess sharing.

A strict-high queue is serviced first, but its effective rate can still be constrained by an interface-level shaper or by other strict-high queues competing for the same bandwidth. If the interface shaper or another strict-high queue consumes the available bandwidth, voice packets can be delayed even though the queue is marked strict-high.

A DSCP rewrite rule contains a table keyed by forwarding class and loss priority. Packets whose forwarding class and loss priority do not appear in that table are not rewritten and retain their original DSCP, which explains why some packets still leave with their original values on the WAN interface.

The graph maps drop probability versus fill level percentage.

The shaping-rate statement on a scheduler enforces a maximum transmission rate for a queue, effectively capping how much bandwidth it can consume. Applying shaping-rate to the strict-high voice queue limits its usage so it cannot starve other queues, which directly addresses the requirement to cap the voice queue while preserving its priority treatment.

The EXP classifier maps MPLS Experimental bits to forwarding classes and packet-loss priorities, satisfying the stem's requirement for natively supported Junos CoS classifiers. Junos supports exp, inet-precedence, and dscp classifiers; exp specifically handles MPLS label headers, unlike dscp or inet-precedence, which read IP header fields.

Policers enforce a rate limit and mark or drop excess traffic. Binding a firewall filter containing a policer to the loopback interface as an input filter applies the rate limit to traffic destined to the Routing Engine, which is exactly the control-plane protection described. This is the standard Junos approach for protecting the RE.

A Junos drop profile is a table of queue fill-level percentages mapped to drop probabilities. As the average queue depth crosses each configured fill level, the associated probability determines the likelihood that an arriving packet is discarded. This is the core mechanism that makes WRED gradual rather than a hard tail drop, and it is exactly what must be verified when tuning congestion behaviour.

A behaviour aggregate classifier inspects only the CoS marking already present in the packet header — DSCP for IP or EXP for MPLS — and maps it to a forwarding class and loss priority, without any multifield inspection of source, destination or port.

Junos policers support actions beyond discard: they can set the packet's loss priority (for example, to high) on traffic exceeding the configured rate. This satisfies the statement's claim, letting downstream congestion controls drop marked packets preferentially.

The `drop-profile-map` statement inside a scheduler maps each loss priority (low, medium-low, high) to a specific drop profile, satisfying the requirement to assign three distinct profiles within one forwarding class. Junos uses this hierarchy under the scheduler's `drop-profile-map` to bind PLP values to profiles.

A transmit-rate guarantees the critical queue its minimum share during congestion, while a shaping-rate caps the guest queue's maximum throughput at 200 Mbps regardless of idle capacity. Together they satisfy both the guaranteed-minimum and maximum-limit requirements on the congested uplink interface.

Custom forwarding classes are defined under the [edit class-of-service forwarding-classes] hierarchy, where each class is mapped to a queue number. This stanza lets you name and assign up to eight classes, satisfying the requirement to define them explicitly rather than rely on default best-effort, expedited, assured and network-control classes.

Assigning a guaranteed transmit-rate ensures the network control class always has bandwidth reserved, while high priority causes it to be serviced ahead of lower-priority data queues. Together they protect routing protocol updates during congestion without the starvation risk of strict-high priority. This is the recommended approach for the network control forwarding class.

The EXP field is the three-bit MPLS header field that Junos rewrite rules can mark, satisfying the requirement for valid CoS rewrite targets. Rewrite rules map forwarding classes to EXP bits on egress label-switched interfaces, so exp qualifies alongside inet-precedence and dscp as a supported header marker.

The `show class-of-service scheduler-map` command lists every configured scheduler map alongside its forwarding-class associations, satisfying the requirement to display both mappings together. Unlike `show class-of-service scheduler-map <name>`, which requires a specific map name, this form enumerates all maps, directly answering the stem's request for configured scheduler maps and their forwarding-class associations.

The show class-of-service interface command displays the CoS configuration applied to a specific interface, including the classifier, rewrite rule, scheduler map, and the forwarding class to queue mapping. This directly provides the information the administrator needs to verify how forwarding classes map to queues on the interface in question.

Shaping delays packets rather than dropping them, so it must be applied where the device controls transmission scheduling. Egress interfaces allow the router to queue and meter outbound traffic, whereas ingress shaping is impractical because the upstream sender controls the rate.

`show class-of-service interface` displays per-interface forwarding-class-to-queue mappings, scheduler associations and queue counters, directly satisfying the stem's requirement to verify operational state on a specific interface. Unlike CoS configuration output, it reports live queue assignment and statistics, confirming that classification and scheduling behave as intended.

A rewrite rule is used to mark CoS bits on outgoing packets. To mark expedited-forwarding packets with DSCP EF (46), you configure a DSCP rewrite rule that maps the expedited-forwarding forwarding class to code point 46, and then apply that rewrite rule to the egress interface. This is the correct configuration.

A policer's discard action drops excess traffic immediately at the interface, enforcing the committed rate without buffering. This satisfies the stem's requirement for actions triggered when traffic exceeds the specified rate, since discarding is one of the three standard policer outcomes alongside rate-limiting and marking.

Configuring priority high on the voice forwarding class places it in a strict-priority queue, which is serviced before all other queues until empty. This satisfies the stem's requirement that delay-sensitive voice traffic be serviced ahead of every other queue.

A policer with a discard action discards non-conforming packets at ingress, which matches the observed immediate loss. To remark excess traffic and let the egress drop profile handle selective discarding, the policer must use loss-priority high or a similar remark action. Checking the policer action is therefore the correct first step in diagnosing this behaviour.

A BA classifier maps a single CoS field such as DSCP, IP precedence, or MPLS EXP into a forwarding class and loss priority without examining other packet fields. Because the requirement is to classify solely on the DSCP bits in the IP header with no firewall filter, the BA classifier applied to the ingress interface is exactly the right tool.

The transmit-rate parameter sets the minimum guaranteed bandwidth for a queue, ensuring the best-effort queue receives its allocated share even under congestion. Configuring transmit-rate prevents starvation by reserving capacity, whereas other scheduler parameters only influence excess-bandwidth distribution or buffer behaviour.

A strict-high priority scheduler services the video queue ahead of all other queues whenever packets are present, giving the multicast stream the lowest possible latency and jitter even under congestion. Junos guarantees the strict-high queue is drained before other queues are scheduled, which directly satisfies the requirement without dropping the other classes entirely.

Rewrite rules that remark DSCP on egress are configured under [edit class-of-service interfaces] on the outbound interface, where the scheduler maps forwarding classes to rewrite values. Applying it at the interface level ensures the remarking occurs as packets leave.