QoS and QoS Policies
70
Quality of Service Guide
3HE 11014 AAAC TQZZA Edition: 01
3.2 Access Ingress
This section contains the following topics for traffic flow in the access ingress
direction:
• Access Ingress Traffic Classification
• Access Ingress Queues
• Access Ingress Queuing and Scheduling
• Access Ingress Per-SAP Aggregate Shapers (Access Ingress H-QoS)
• Ingress Shaping to Fabric (Access and Network)
• Configurable Ingress Shaping to Fabric (Access and Network)
• Fabric Shaping on the Fixed Platforms (Access and Network)
3.2.1 Access Ingress Traffic Classification
Traffic classification identifies a traffic flow and maps the packets belonging to that
flow to a preset forwarding class, so that the flow can receive the required special
treatment. Up to eight forwarding classes are supported for traffic classification.
Refer to Table 2 for a list of these forwarding classes.
For TDM channel groups, all of the traffic is mapped to a single forwarding class.
Similarly, for ATM VCs, each VC is linked to one forwarding class. On Ethernet ports
and VLANs, up to eight forwarding classes can be configured based on 802.1p
(dot1p) bits or DSCP bits classification. On PPP/MLPPP, FR (for Ipipes), or cHDLC
SAPs, up to eight forwarding classes can be configured based on DSCP bits
classification. FR (for Fpipes) and HDLC SAPs are mapped to one forwarding class.
Once the classification takes place, forwarding classes are mapped to queues as
described in the sections that follow.
Note:
• If an Ethernet port is set to null encapsulation, the dot1p value has no meaning and
cannot be used for classification purposes.
• If a port or SAP is set to qinq encapsulation, use the match-qinq-dot1p top | bottom
command to indicate which qtag contains the dot1p bits that are used for classification
purposes. The match-qinq-dot1p command is found under the config>service
context. Refer to the 7705 SAR Services Guide, “VLL Services Command Reference”,
for details.
To Next Page
Loading...
