Overview

An access ingress QoS policy is applied to the physical port instead of the SAP. It applies to all SAPs configured on the specific access port. To configure a port-based access ingress QoS policy, the access-ingress-qos-mode command must be configured with the port-mode option specified.

At ingress, the access ingress QoS policy uses dot1p, DEI with dot1p, or IP DSCP values to assign a forwarding class and profile to traffic, which facilitates the classification of traffic received on the access port. The user can assign a profile using DEI configured with a dot1p classification policy. The forwarding class is associated with meters or policers at ingress. The FC meters for unicast and multicast traffic and meter characteristics (for example, the CIR and PIR) are defined in the policy.

An access ingress QoS policy supports the definition of up to one (1) meter per forwarding class for unicast traffic, and up to one (1) meter per forwarding class for multipoint traffic (that is, broadcast, multicast, and unknown-unicast) for multipoint services. The definition of a maximum of 16 meters per access ingress QoS policy is supported.

For VPLS, the following four forwarding types (not to be confused with forwarding classes) are supported: unicast, multicast, broadcast, and unknown. The multicast, broadcast, and unknown traffic types are flooded to all destinations in the service and use the multipoint meter associated with the forwarding class. The unicast traffic type is handled in a point-to-point manner in the service and uses the unicast meter associated with the forwarding class.