The default forwarding class defined in the SAP-egress policy.

The forwarding class inherited from network ingress classification.

Best Effort.

If there is no match, packets will be dropped.

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

Change the CIR-level value for the best-effort queue to 8.

Do not change anything; it is already guaranteed to receive its CIR

Change the CIR-level value for the best-effort queue to 1.

Change the CIR-weight value of the AF queue to 0.

BGP IPv4 routes for all PE system addresses in AS 5000.

VPN-IPv4 routes for all PE system addresses in AS 5000.

BGP labeled IPv4 routes for all PE system addresses in AS 5000.

LDP labeled routes for all PE system addresses in AS 5000.

The policy should be placed in a " shutdown " state before changes are made.

A new network policy should be created and applied to the interface, overwriting the previous policy.

The policy must first be removed from the interface, then modified and re-applied to the interface.

Before the policy can be changed, it must be deleted with the no network qos < policy-id > command.

Before any changes are made to the policy, all network interfaces where the policy is applied have to be shut down.

All out-of-profile traffic will be dropped before that of any in-profile traffic.

The discard probability slope of an in-profile traffic is steeper than that of an out-of-profile traffic.

When the shared buffer utilization reaches 55%, both in-profile and out-of-profile packets may be dropped.

The maximum probability with which an out-of-profile packet can be dropped is higher than that of an in-profile packet.

When the shared buffer utilization is at 61%, only in-profile packets are currently in the shared buffer pool.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

Real-time

Assured

Non-conforming

High priority

In-profile

A device that provides no differentiation between customer traffic flows.

A device that classifies and marks customer traffic.

A device that uses MPLS EXP bits to differentiate between traffic flows.

A device that creates macroflows towards the core from multiple customer sites.

A device that passes macroflows while optionally changing QoS markings.

Service labels are assigned based used on label blocks.

BGP-AD, RADIUS and Management are used for auto-discovery.

Service labels are signaled using MP-BGP.

Hierarchical VPLS is loosely defined in the standards.

To utilize memory resources efficiently

To avoid Head of Line blocking

To achieve more granularity of QoS control

To make hierarchical scheduling/policing possible

AF

EF

H2

H1

BE

The slope-policy

The SAP-ingress policy

The SAP-egress policy

The network-queue policy

The scheduler-policy

Uses standard Ethernet dot1q and QinQ encapsulation.

Requires IS-1S as the protocol to carry control information.

Ethernet Ring APS is a defined ITU standard.

Standard Ethernet forwarding, learning, and flooding rules apply.

Queue 2 in " policer-output-queues, " the default queue group used by policers on egress, because there are no queues in the " qg-10 " queue-group template.

The local SAP ' s queue 1, because there is no queue in the " qg-10 " queue-group template for EF traffic.

Queue 1 in the " qg-10 " queue-group, because it exists by default and all traffic is mapped to it.

EF traffic is dropped because there are no queues in the " qg-10 " queue-group template.