Change the Default Queuing and Marking of Host Outbound Traffic

Host Outbound Traffic Classification Overview

TCP-related packets, such as BGP or LDP, use queue 3 (network control) for retransmitted traffic. Changing the defaults for Routing Engine sourced traffic does not affect transit or incoming traffic. The changes apply to all packets relating to Layer 3 and Layer 2 protocols, but not MPLS EXP bits or IEEE 802.1p bits. This feature applies to all application-level traffic such as FTP or ping operations as well.

The forwarding class selected is global to the device. That is, the traffic is placed in the selected forwarding class on all egress interfaces. In the case of a restricted interface, the Routing Engine sourced traffic flows through the restricted queue.

The forwarding class selected must be properly configured on all interfaces.

To change the default forwarding class and DSCP bits for Routing Engine sourced traffic, include the host-outbound-traffic statement at the [edit class-of-service] hierarchy level:

The following example places all Routing Engine sourced traffic into the network control forwarding class (assigned to queue 3 by default) with a DSCP value of 101010:

You can also modify the queue assignment of the forwarding class. For example:

Platform-Specific Host Outbound Traffic Classification Behavior

Use Feature Explorer to confirm platform and release support for host outbound traffic classification.

Use the following table to review platform-specific behaviors for your platform:

Platform	Difference
ACX7000 Series Routers	ACX7000 Series Routers support only the forwarding-class class-name option.