network

scheduling

slope

SAP-ingress

network-queue

Using dot1p bits of the 802.1q Ethernet frame header

Using DSCP bits within the ToS field of the IP packet header.

Using the IP precedence bits within the ToS field of the IP packet header.

Using the CLP bit of the ATM cell header.

Using the EXP bits of the MPLS transport label header.

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.

All buffer space is initially allocated to access pools, and some of it is reallocated to network pools if network interfaces are configured on it.

All buffer space is initially allocated to network pools, and some of it is reallocated to access pools if service SAPs are configured on it.

Buffer space is allocated 50% for access pools and 50% for network pools.

Buffer space is allocated 25% for access pools and 75% for network pools.

The three most significant (first) bits define 8 forwarding classes.

The three least significant (last) bits of the DSCP specify the drop probability.

The full 8 bits of the TOS field are used for DSCP.

To convert DSCP to IP precedence, the three most significant (first) bits are matched.

DSCP provides for eight drop probabilities.

Network ingress port

Epipe ingress SAP

ES egress SAP

Ingress MDA

VPRN ingress interface

Shared buffer space

Packets corresponding to a layer-2 service can be pre-marked on SAP-ingress.

Packets corresponding to a layer-2 service can be pre-marked on network-ingress.

Packets corresponding to a layer-3 service can be pre-marked on SAP-ingress.

Packets corresponding to a layer-3 service can be pre-marked on network-ingress.

All incoming packets belonging to forwarding class “l2” are stored in the reserved buffer space.

All incoming packets belonging to forwarding class “af” are stored in the reserved buffer space.

All incoming packets belonging to forwarding class “l1” are stored in the reserved buffer space.

In-profile packets in the shared buffer space are being dropped.

An arbiter can adjust the CIR of its child policers.

An arbiter rate-limits the collective output of several policers towards each egress FFPC.

An arbiter can adjust the bandwidth assigned to its child arbiters and child policers.

An arbiter does not need to honor the configurations of its child policers.

The larger the configured MBS value, the lower the amount of shaping performed.

When policing is enabled on the SAP-ingress, all traffic is considered as in-profile.

Setting the CIR to 1000 and the PIR to max will enable shapeless policing at 1 Mbps within the SAP-egress policy.

Configuring MBS to equal CBS will disable shaping.

Setting the CIR and PIR to equal values disables soft-policing.