Network QoS Policies
164
Quality of Service Guide
3HE 11014 AAAC TQZZA Edition: 01
• ingress criteria — the DSCP to forwarding class mapping for all GRE and IP
packets and the MPLS EXP bits to forwarding class mapping for all labeled
packets
− default-action — the default action to be taken for packets that have
undefined DSCP or MPLS EXP bits set. The default-action specifies the
forwarding class to which such packets are assigned. The default-action is
automatically created when the policy is created.
− DSCP — a mapping between the DSCP bits of the network ingress traffic
and the forwarding class. Ingress traffic that matches the specified DSCP
bits will be assigned to the corresponding forwarding class.
− LSP EXP — a mapping between the LSP EXP bits of the network ingress
traffic and the forwarding class. Ingress traffic that matches the specified
LSP EXP bits will be assigned to the corresponding forwarding class.
• ring criteria — the dot1p-to-queue mapping for all packets arriving on a bridging
domain port (that is, a ring port or the add/drop port)
− default-action — the default action to be taken for packets that have
undefined dot1p bits set. The default-action specifies the queue to which
such packets are assigned and the profile state of the packets. The default-
action is automatically created when the policy is created.
− dot1p — a mapping of the dot1p bits of the ingress traffic to the queue and
the profile state
4.2.2 Creating a Network QoS Policy
Configuring and applying network QoS policies other than the default policy is
optional.
Use the following CLI syntax to create a network QoS policy for router interfaces
(ip-interface type) and ring port (ring type).
The ip-interface keyword is optional for router interface network policies.
Use the ring keyword to create a network QoS policy that can be applied to a
bridging domain port (that is, a ring port or the add/drop port). Up to eight dot1p-to-
queue and profile mappings can be defined under the ring command.
To Next Page
Loading...
