The DSCP value will be set to af21.

The DSCP value will be set to af23.

The DSCP value will remain as ef.

The EXP value, in the MPLS headers, will be set to 4.

The EXP value, in the MPLS headers, will be set to 3.

The slope-policy

The SAP-ingress policy

The SAP-egress policy

The network-queue policy

The scheduler-policy

Shapeless policing at SAP-ingress only.

Shapeless policing at SAP-ingress and egress.

Biased round robin queuing at ingress only.

Soft shaping at all network interfaces.

Soft shaping at network ingress only.

To have control over the amount of the low priority packets that enter the queue.

To control any traffic flowing through the shared buffer space of the queue.

To limit the number of the TCP sessions that go into slow start during congestion.

To force the TCP algorithm to increase its transmission window upon detecting a congestion.

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as " discard eligible. "

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are not being dropped on ingress.

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are being dropped on ingress.

A commercial builder has requested numerous dot1Q epipes, VPRNs, and VPLS services to a business park and is only paying up to a maximum 200Mbps.

An equipment manufacturer has requested a NULL epipe service that will transparently pass dot1Q between the new location and national headquarters.

Profile-mode and priority-mode queues can only be configured on SAP ingress.

For network egress, egress re-classification can change the profile marked at ingress.

For SAP egress, the profile marked at ingress may change based on the scheduling loop.

For network ingress, the network policy can classify the packet as either in-profile, or out-of-profile.

DSCP

PREC

Dot1p

ToS

Q-in-Q

A network policy for every network interface configured on the port.

A slope policy for the port on ingress.

A network queue policy for the corresponding MDA on ingress.

A network queue policy for the port on egress.

All AF traffic will be marked " in-profile " at the SAP-ingress.

All TCP traffic will be mapped to forwarding class EF.

UDP traffic is placed in queue 3 while ICMP traffic is placed in queue 5.

EF traffic will receive higher scheduling priority than H2 traffic.

Traffic that does not match any of the IP criteria will be placed in queue 3.