Network QoS Policies
Quality of Service Guide 79
• IP ToS precedence mapping
• IP ToS DSCP mapping
• MPLS LSP EXP mapping
The default QoS mapping always exists on an ingress IP interface and every received packet
will be mapped to this default if another explicitly defined matching entry does not exist.
A tunnel that terminates on the ingress IP interface (the node is the last hop for the tunnel) is
evaluated based on the type of tunnel, IP GRE or MPLS LSP. An IP tunneled packet may
match a dot1p entry, IP ToS precedence entry or IP ToS DSCP entry when defined in the
applied policy. An MPLS LSP may match a dot1p entry or MPLS EXP entry when defined.
The internal tunnel encapsulated packet is never evaluated for QoS determination when
operating in normal mode.
Network Ingress IP Match Criteria
IP match criteria classification is supported in the ingress section of a network QoS policy.
The classification only applies to the outer IPv4 header of non-tunneled traffic, consequently
the use of an ip-criteria statement in a network QoS policy is ignored for received traffic when
the network QoS policy is applied on the ingress network IP interface in the following cases:
• Mesh SDPs in VPLS services
• Spoke SDPs in VPLS and Xpipe services
• Spoke SDP under an IP interface in an IES or VPRN service
• Spoke SDPs in a VPRN service
• Automatically created bindings using the auto-bind-tunnel command in a VPRN
service
• IPv6 over IPv4 tunnels
• VXLAN bindings (egress VTEP, VNI)
The only exception is for traffic received on a Draft Rosen tunnel for which classification on
the outer IP header only is supported.
Attempting to apply a network QoS policy containing an ip-criteria statement to any object
except a network IP interface will result in an error.
An example configuration is shown below:
network 10 create
ingress
ip-criteria
To Next Page
Loading...
