Professional Documents
Culture Documents
Cisco Quality Measures
Cisco Quality Measures
Legacy CLI
AutoQoS VoIP
AutoQoS Enterprise
QoS Policy Manager (QPM)
Used for Administration & Monitoring multiple interfaces provisioned for
QoS across the Network (not just on individual devices like AutoQoS
does).
AutoQoS
AutoQoS VOIP
Creates a QoS policy to prioritize Voice Over IP traffic ONLY, cannot be
used to discover and implement QoS for other traffic types.
AutoQoS Enterprise
Uses Network-Based Application Recognition (NBAR) to discover traffic
types on the Network and create a QoS Policy based on best-
practices for each flow.
Steps for implementing QoS
IP Precedence
IP ToS Byte
8-Bit Field within the IP Header of a packet, mainly used for marking packets
with IP Precedence values.
Classification & Marking
What is Classification?
The ability for a network device to identify different traffic types and
divide them into different classes based on Business
Requirements. Classification occurs on a devices inbound
(Ingress) interface.
Classification Tools
IP Precedence
In best practices you should limit the number of traffic classes for
provisioning QoS to about 4 or 5 classes. If more is needed,
usually no more than 11 different classes are necessary.
What is CoS?
Turning on bits in the 802.1P (user priority) field within the 802.1Q
Header (or Cisco ISL Header) of an Ethernet Frame.
Supported values are 0-5, 7 and 6 are reserved and typically are
not used to classify traffic. CoS 5 should be treated for high
priority (i.e: Voice) traffic.
Class of Service (COS)
Limitation of COS
Devices that receive packets on non-trunking or Ethernet ports will
not preserve the L2 headers and the 802.1Q (or ISL) field, by
stripping them of their priority markings. Therefore, CoS Markings
should be mapped to mechanism which preserves the CoS as it
transits other network devices, such as mapping CoS Values at
Layer 2 to IP Precedence or DSCP values within header of packets
at Layer 3 (IP).
Marking with MQC
set ip precedence
AF Classes:
For example, If the router receives two packets of class AF1, it will
check which packet has a higher drop preference set and
discard that one in favor of the packet with the lower preference.
Drop Preference is ignored between packets of different classes.
If a packet marked with AF11 (Low Drop) and a packet with AF43 (High Drop)
arrive at the router, the first one will be dropped because it is in the lower
class, even though the other packet has a higher Drop Preference.
For example, we tell the router to mark incoming packets with CS5
(101000), Non-DiffServ compliant devices that receive theses
packets only read the first 3 bits of 101, which it interprets as
IP Precedence 5.
PDLMs
ip nbar protocol-discovery
Inspects packets and discovers the traffic types that go in or out of the interface
Network-Based Application
Recognition (NBAR)
Verifying Configuration
show ip nbar protocol-discovery
Display statistics of discovered applications
show ip nbar port-map
Display the current protocol/port mappings
By default, Cisco IOS devices that use Tunnel interfaces copy the ToS byte from
the IP header of Packets and attach them to the ToS byte of the Tunnel
Headers before put on the VPN.
QoS Preclassify: Used when you want to classify traffic not based on the ToS
Byte / DSCP markings as they traverse a tunnel. A Device uses a QoS policy
on the original IP Header of the packet rather than the Tunnel Header.
qos pre-classify
Queuing Mechanisms:
Finish Time
Used by the WFQ Algorithm, pckets with larger Finish Times are more likely to
be discarded during congestion.
fair-queue <cdt>
Sets the Congestive Discard Threshold on an interface.
fair-queue <dynamic-queues>
Sets total queues that can be created by the WFQ system.
fair-queue <reservable-queues>
Sets limit of queues used for RSVP
queue-limit <limit>
bandwidth
bandwidth percent
bandwidth remaining percent
These commands are used for bandwidth reservations
for a traffic class.
NOTE: Once bandwidth is reserved to a class using
kbps, the bandwidth percent command cannot be
applied to other classes within that same policy-map.
This would confuse the router and make improper
calculations when reserving bandwidth.
Class-Based WFQ
max-reserved-bandwidth
AKA: CBWFQ + PQ
TCP Starvation
However, because RED actively drops flows that are only TCP-
based, a large UDP packet can quickly fill the queue and prevent
the router from buffering possibly more critical traffic.
Random Early Detection (RED)
The Three RED Modes
Allows the ability to drop the less important traffic (i.e: BE)
earlier and minimize congestion for more important traffic.
random-detect ecn
show policy-map
show policy-map interface <int>
Conform-Action
When a bucket has enough Tokens to send the packet. The
necessary amount of Tokens are subtracted from the total and
the packet is transmitted out the interface.
Exceed-Action
When there are not enough Tokens in the first bucket to send the
packet, so it is either dropped or re-marked with a lower priority
(depending on the policy configured).
Violate-Action
When there are insufficient Tokens in either bucket.
Dual-Metering
Bandwidth for a class of traffic can be policed in bits per second (bps) or allocated a
fraction of bandwidth from the link. The default is to use bits per second.
using bits
police <bps> conform-action <action> exceed-action <action> violate-action <action>
using percentage
police percent <percentage> conform-action <action> exceed-action <action> violate-action <action>
By using percentage rather than bps, this same policy can be applied to multiple
interfaces regardless of what their link capacity is.
Defaults
The default unit used in configuring policing is bits per second
the default conform-action is transmit
and the default exceed-action is drop.
Changing the default exceed-action
Payload Compression
Shrinks the total size of the entire frame
Ideal for transmitting large frames via slow links
Header Compression
Saves link bandwidth
Reduces packet size and serialization delay
Suppresses IP & Layer 4 redundant addresses
Implemented on a per-link basis
Ideal for low-bandwidth traffic (Voice,Telnet,etc)
cRTP reduces IP/UDP/RTP headers down to 2-4 Bytes
cTCP reduces TCP/IP overhead down to 3-5 Bytes
Link Efficiency - Compression
cRTP Configuration
compression header ip rtp
cTCP Configuration
compression header ip tcp
compression header ip
Enables both cRTP and cTCP by default
Link Efficiency - LFI
Serialization Delay
The lower the capacity of a network link the longer it takes for a
frame to be placed on the physical media.
Serialization Delay is calculated based on the formula
Delay = (frame size in bits) / capacity of link
A 1500 byte frame takes 187.5 ms to put on a 64kbps link
(1500 * 8) / 64 = 187.5
Link Efficiency - LFI
What is LFI?
Link Fragmentation & Interleaving are techniques used to reduce delay
& jitter when serializing frames onto the WAN. Large frames are
chopped into smaller fragments so that Voice and other delay bound
traffic can be placed in between them.
On a slow link Without LFI, a large frame must be transmitted in its
entirety before frames behind it can be sent.
Voice cannot survive in this scenario!
Link Efficiency - LFI
LFI Mechanisms
Multilink PPP LFI (MLP LFI)
VoIP over Frame Relay (FRF.12)
FRF.11 Annex C - Voice over Frame Relay (VoFR)
ppp multilink
Turns on multilink ppp on a point-to-point interface
Configuration
map-class frame-relay <map name>
Creates a frame relay map-class for specifying QoS parameters
Verifying Configuration
show frame-relay fragment
Displays FRF.12 statistics for all interfaces and DLCIs
show frame-relay fragment <interface or dlci>
Outputs the statistics for the specific circuit
show frame-relay pvc
Also displays information related to FRF.12
Calculating bandwidth for Voice
IP Header: 20 Bytes
UDP Header: 8 Bytes
RTP Header: 12 Bytes
Conclusion
One G.711 call consumes 80kbps of bandwidth