Table of Contents
Advertisement
assigned to the queue explicitly by the user. The SAP ingress policy has optional queue
configuration. The use of queues in the SAP ingress can be specified for any Forwarding Class
(FC) or for all of them. The queue must be provisioned before configuring it under the FC. The
system allocates resources needed for eight queues when the first queue is observed for a SAP and
they are allotted default amount of CBS and MBS buffers, with an option for the user to change it.
In the SAP ingress policy, a FC can use either a meter or a queue (there are some rules listed
below). They are mutually exclusive (i.e. only when the there is no explicit meter configured under
the FC a queue can be specified and vice-versa). A single SAP ingress policy can use a mix of FCs
such that some of them use queues and some of them use meter/policer. The following rules are
applied:
SAP ingress policy will by default use meter 1 to police all unicast traffic and BUM traffic. No
default queues will be in use. Use of queues will need explicit user configuration.
As before, a FC can use all four types of meters i.e, unicast meter, multicast meter, unknown-
unicast meter and broadcast meter. In this case it can use no ingress queues.
•
•
•
7210 SAS-X and 7210 SAS-R6 OS Quality of Service Guide
In an Epipe service and VPRN service all traffic is classified as unicast traffic and hence if
a queue is configured for a FC, all traffic classified to that FC will use the configured
queue.
In a VPLS service (including PBB VPLS), Broadcast, Unknown Unicast and Multicast
(BUM) traffic type for an FC can use meters/policers, while unicast traffic type uses a
queue. Meter cannot be associated with the unicast traffic type, if it's configured to use a
queue. If meters are associated with any of the BUM traffic type of a FC, then that traffic
type will be policed as per the rates specified and then queued up into the shared ingress
multicast queues used for BUM traffic. In other words, BUM traffic type is always queued
into the shared ingress multicast queues and they can optionally use meter/policer. In a
VPLS service, following different combinations are allowed.
→ FC -> unicast uses queue + BUM uses default queues (no meters in use for BUM
traffic)
→ FC -> unicast uses queue + BUM uses default meter and default queues
→ FC -> unicast uses default meter + BUM uses default meter and default queues
→ FC -> unicast uses queue + BUM uses meters and default queues
→ FC -> unicast uses meter + BUM uses default queues (no meters in use for BUM
traffic)
In an IES service all traffic is classified as unicast traffic if PIM is not enabled and hence if
a queue is configured for a FC, all traffic classified to that FC will use the configured
queue. If PIM is enabled, then only unicast traffic will use the queue configured for the
FC. User has an option to use a multipoint meter for the multicast traffic. Additionally, all
multicast traffic will use the shared ingress multicast queues after being policed/meters by
the SAP ingress meter, if a multipoint meter is configured.
Service Ingress QoS Policies
Page 199
Advertisement
Table of Contents
