Service SAP QoS Policy Command Reference
284 Quality of Service Guide
no egress-fc
Context config>qos>sap-ingress>fc
Description This command configures the forwarding class to be used by the egress QOS processing. It overrides
the forwarding class determined by ingress classification but no0t the QOS Policy Propagation via
BGP.
The forwarding class and/or forwarding sub-class can be overridden.
The new egress forwarding class is applicable to both SAP egress and network egress.
Default no egress-fc
Parameters fc-name — Specifies the forwarding class name to be used by the egress QOS processing.
Default None. The fc name must be specified.
Values be, l2, af, l1, h2, ef, h1, nc
in-remark
Syntax in-remark dscp dscp-name
in-remark prec ip-prec-value
no in-remark
Context config>qos>sap-ingress>fc
Description This command is used in a SAP ingress QoS policy to define an explicit in-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 (i.e., Epipe or VPLS), the remarking
definitions are silently ignored.
In the case where the policy is applied to a Layer 3 SAP, the in-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 in-profile marking.
The in-remark command is only applicable to ingress IP routed packets that are considered in-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 in-remark command on received SAP ingress packets. Within the in-profile IP packet’s ToS
field, either the six DSCP bits or the three precedence bits are remarked.
SAP Ingress Packet State ‘in-remark’ Command Effect
Non-Routed, Policed In-Profile No Effect (non-routed packet)
Non-Routed, Policed Out-of-Profile No Effect (non-routed packet)
Non-Routed, Explicit In-Profile No Effect (non-routed packet)
To Next Page
Loading...
