IP Router Configuration
Router Configuration Guide 23
When the qos-route-lookup command with the destination parameter is applied to an IP
interface and the destination address of an incoming IP packet matches a route with QoS
information the packet is classified to the fc and priority associated with that route, overriding
the fc and priority/profile determined from the sap-ingress or network qos policy associated
with the IP interface (see section 5.7 for further details). If the destination address of the
incoming packet matches a route with no QoS information the fc and priority of the packet
remain as determined by the sap-ingress or network qos policy.
Similarly, when the qos-route-lookup command with the source parameter is applied to an IP
interface and the source address of an incoming IP packet matches a route with QoS
information the packet is classified to the fc and priority associated with that route, overriding
the fc and priority/profile determined from the sap-ingress or network qos policy associated
with the IP interface. If the source address of the incoming packet matches a route with no
QoS information the fc and priority of the packet remain as determined by the sap-ingress or
network qos policy.
Currently, QPPB is not supported for ingress MPLS traffic on network interfaces or on CsC
PE’-CE’ interfaces (config>service>vprn>nw-if).
QPPB When Next-Hops are Resolved by QPPB Routes
In some circumstances (IP VPN inter-AS model C, Carrier Supporting Carrier, indirect static
routes, etc.) an IPv4 or IPv6 packet may arrive on a QPPB-enabled interface and match a
route A1 whose next-hop N1 is resolved by a route A2 with next-hop N2 and perhaps N2 is
resolved by a route A3 with next-hop N3, etc. In release 9.0 the QPPB result is based only on
the forwarding-class and priority of route A1. If A1 does not have a forwarding-class and
priority association then the QoS classification is not based on QPPB, even if routes A2, A3,
etc. have forwarding-class and priority associations.
Note: QPPB based on a source IP address is not supported for ingress subscriber
management traffic on a group interface.
To Next Page
Loading...
