Table 405: Default Forwarding Classes For Unicast Packets; Table 406: Default Forwarding Classes For Multicast Packets - Juniper JUNOS OS 10.3 - SOFTWARE Manual

Table 405: Default Forwarding Classes for Unicast Packets

Forwarding Class Name
best-effort (be)
expedited-forwarding (ef)
assured-forwarding (af)
network-control (nc)

Table 406: Default Forwarding Classes for Multicast Packets

Forwarding Class Name
multicast best-effort (mcast-be)
multicast expedited-forwarding
(mcast-ef)
multicast assured-forwarding
(mcast-af)
Copyright © 2010, Juniper Networks, Inc.
If desired, you can rename the forwarding classes associated with the queues supported
on your switch. Assigning a new class name to an output queue does not alter the default
classification or scheduling that is applicable to that queue. CoS configurations can be
quite complicated, so unless it is required by your scenario, we recommend that you not
alter the default class names or queue number associations.
Comments
The software does not apply any special CoS handling to packets with 000000 in
the DiffServ field. This is a backward compatibility feature. These packets are usually
dropped under congested network conditions.
The software delivers assured bandwidth, low loss, low delay, and low delay variation
(jitter) end-to-end for packets in this service class. The software accepts excess
traffic in this class, but in contrast to the assured forwarding class, the out-of-profile
expedited-forwarding class packets can be forwarded out of sequence or dropped.
The software offers a high level of assurance that the packets are delivered as long
as the packet flow from the customer stays within a certain service profile that you
define.
The software accepts excess traffic, but it applies a tail drop profile to determine if
the excess packets are dropped and not forwarded.
Up to two drop probabilities (low and high) are defined for this service class.
The software delivers packets in this service class with a high priority. (These packets
are not delay-sensitive.)
Typically, these packets represent routing protocol hello or keep alive messages.
Because loss of these packets jeopardizes proper network operation, packet delay
is preferable to packet discard.
Comments
The software does not apply any special CoS handling to the multicast packets.
These packets are usually dropped under congested network conditions.
The software delivers assured bandwidth, low loss, low delay, and low delay variation
(jitter) end-to-end for multicast packets in this service class. The software accepts
excess traffic in this class, but in contrast to the multicast assured forwarding class,
out-of-profile multicast expedited-forwarding class packets can be forwarded out
of sequence or dropped.
The software offers a high level of assurance that the multicast packets are delivered
as long as the packet flow from the customer stays within a certain service profile
that you define.
The software accepts excess traffic, but it applies a tail drop profile to determine if
the excess packets are dropped and not forwarded.
Up to two drop probabilities (low and high) are defined for this service class.
Chapter 107: Class of Service (CoS)—Overview
3157