Specifications

25-4
Cisco MWR 2941 Mobile Wireless Edge Router Release 3.5 Software Configuration Guide, Cisco IOS Release 15.1(3)MR
OL-26895-01
Chapter 25 Configuring Quality of Service
Configuring Quality of Service
The show policy-map command displays inaccurate output for QoS counters due to ingress counter
limitations on the router. The command displays a summary of QoS activity on the MWR 2941 that
is limited as follows:
The number of packets displayed below the Class-map name includes the number of packets
matched and marked on the router.
The Packets marked number for each QoS value always displays as 0.
The following example shows output for the show policy-map command:
Router# show policy-map interface gigabitethernet0/0 in
GigabitEthernet0/0
Service-policy input: INPUT-POLICY
Class-map: DSCP-IN (match-any)
2857393 packets
Match: ip dscp af43 (38) ef (46) cs6 (48) 62
QoS Set
cos 5
Packets marked 0
qos-group 5
Packets marked 0
Output MLPPP interfaces support QoS statistics.
Output service policies on the GigabitEthernet interface do not support statistics.
Propagation Limitations
The Cisco MWR 2941 has the following limitations when propagating QoS values between interfaces:
The following limitations apply when traffic ingresses through a GigabitEthernet interface and
egresses through a GigabitEthernet interface:
When traffic is routed at layer 3, the router maps the CoS bits to the QoS group value. The QoS
group is not propagated through the L3 network processor.
When traffic is switched at layer 2, the QoS group is propagated through the router.
The following limitations apply when traffic ingresses through any other interface type
(host-generated, MLPPP, or HWIC) and egresses through the GigabitEthernet interface.
The Precedence bit value is propagated to the CoS bit. The CoS bit value is mapped 1:1 to the
QoS group value.
See Sample QoS Configuration, page 25-8 for a sample QoS configuration that accounts for propagation
limitations on the Cisco MWR 2941.
Note For more information about QoS restrictions for individual interface cards, see the
documentation for Cisco Interface Cards.