Service SAP QoS Policy Command Reference
286 Quality of Service Guide
The multicast forwarding type includes the unknown unicast forwarding type and the broadcast
forwarding type unless each is explicitly defined to a different multipoint queue. When the unknown
and broadcast forwarding types are left as default, they will track the defined queue for the multicast
forwarding type.
The no form of the command sets the multicast forwarding type queue-id back to the default queue for
the forwarding class. If the broadcast and unknown forwarding types were not explicitly defined to
a multipoint queue, they will also be set back to the default multipoint queue (queue 11).
Parameters queue-id — The queue-id parameter specified must be an existing, multipoint queue defined in the
config>qos>sap-ingress context.
Values Any valid multipoint queue-ID in the policy including 2 through
32.
Default 11
group queue-group-name — This optional parameter is used to redirect the forwarding type
within the forwarding class to the specified queue-id within the queue-group-name. When the
policy is applied, all packets matching the forwarding class and forwarding type will be
redirected to the queue within the specified queue group. The queue-group-name are
configured in the config>qos>queue-group-templates egress and ingress contexts.
out-remark
Syntax out-remark dscp dscp-name
out-remark prec ip-prec-value
no out-remark
Context config>qos>sap-ingress>fc
Description This command is used in a SAP ingress QoS policy to define an explicit out-of-profile remark action
for a forwarding class or sub-class. While the SAP ingress QoS policy may be applied to any SAP, the
remarking functions are only enforced when the SAP is associated with an IP or subscriber interface
(in an IES or VPRN). When the policy is applied to a Layer 2 SAP (for example, Epipe or VPLS), the
remarking definitions are silently ignored.
In the case where the policy is applied to a Layer 3 SAP, the out-of-profile remarking definition will
be applied to packets that have been classified to the forwarding class or sub-class. It is possible for a
packet to match a classification command that maps the packet to a particular forwarding class or sub-
class only to have a more explicit (higher priority match) override the association. Only the highest
priority match forwarding class or sub-class association will drive the out-of-profile marking.
The out-remark command is only applicable to ingress IP routed packets that are considered out-of-
profile. The profile of a SAP ingress packet is affected by either the explicit in-profile/out-of-profile
definitions or the ingress policing function applied to the packet. The following table shows the effect
of the out-remark command on received SAP ingress packets. Within the out-of-profile IP packet’s
ToS field, either the six DSCP bits or the three precedence bits are remarked.
To Next Page
Loading...
