Cisco IOS Wide-Area Networking Configuration Guide - Free Books

• Egress queueing is determined according to the IP precedence values configured for classes ofL2TPv3 Frame Relay traffic using the match ip precedence command, instead of on aper-DLCI basis.For an example, see Configuring QoS on a Frame Relay Interface in a TSC-Based L2TPv3 TunnelSession, page 101.Edge Engine (ISE/E5) InterfaceOn the Cisco 12000 series, a QoS policy is supported in native L2TPv3 tunnel sessions on ISE/E5interfaces (see Table 2 and Table 3 on page 16 for a list of supported line cards) with the followingrestrictions:• On a Frame Relay or ATM ISE/E5 interface, traffic policing supports only the following conform,exceed, and violate values for the action argument of the police command:conform-action actions:set-prec-tunnelset-dscp-tunneltransmitexceed-action actions:dropset-clp (ATM only)set-dscp-tunnelset-dscp-tunnel and set-clp (ATM only)set-dscp-tunnel and set-frde (Frame Relay only)set-frde (Frame Relay only)set-prec-tunnelset-prec-tunnel and set-clp (ATM only)set-prec-tunnel and set-frde (Frame Relay only)transmitviolate-action actions:drop• On a Frame Relay ISE/E5 interface:– FECN and BECN configuration are not supported.– Marking the Frame Relay discard eligible (DE) bit using a MQC set command is not supported.To set (mark) the DE bit, use the police exceed-action actions command in policy-mapconfiguration mode.– Configuring Tofab MDRR or WRED using legacy QoS (not MQC) commands is supported andis based on the tunnel precedence value.– Egress queueing on a Packet-over-SONET ISE/E5 interface is class-based when configuredusing MQC.– Egress queueing on a per-DLCI basis is not supported.27