Why do we need QoS?
1. Network devices are best efforts to transmit data, providing services to maximize network is called the network's best effort service.
In the best effort service network, all data are seen as equally important, the user's data may not be guaranteed, so at some point, have to let the network to ensure user by giving up relatively unimportant data transmission and transmission of important data. Accordingly, it is desirable to implement Quality of Service in the network, i.e., the QOS
2. Any actual traffic information to all occupied resources, so that maximum use of network resources.
3. The network integration, various communication networks are used to pass traffic.
Telecommunications networks, radio networks, Internet
Qos model
Best-Effort Service: best-effort service model
Integrated Service: Integrated Services model, referred to as Intserv
Differentiated Service: differentiated service model, referred to as Diffserv
Best-Effort Service: best-effort service model
in best effort service model, all network devices are all doing their best to transfer data, although all data transfer, without permission, how many how many pass, any data can not be We are assured that the delay can not be expected, so the best effort service model, in fact, did not implement any QOS, the default network working under this model.
Integrated Service: Integrated Services model, referred to as Intserv
in the implementation of a comprehensive service model QOS in the network, the application before sending the data, must first apply for network bandwidth.
But if some programs before connecting to the network not apply bandwidth, it can only get traffic best-effort service.
In the integrated service model, it is important to ensure that data can be obtained by applying bandwidth, but must apply before the transfer, it takes extra time to.
When applying for bandwidth protocol used for the Resource Reservation Protocol (RSVP) in the existing network, QOS Integrated Services model are not usually used.
Differentiated Service: DiffServ, referred Diffserv
in the embodiment of the DiffServ QOS network, the network will provide different services based on different data, and therefore, all data are divided into different categories, or set to a different priority in the network when congestion occurs, the network always to ensure the transmission of high-priority data, thus abandoning the transmission of low-priority data, but when the network is not congested, all data transmission as usual.
Now the network is generally employed when implementing DiffServ QOS.
Way to achieve the QoS policy
1.CLI
2.MQC
3.autoQoS VoIP (Voice Qos)
CLI: conventional methods (for the present equipment can only take effect) can not be non-modular flow separation defined policy
interface multilink1
IP address 255.255.255.0 10.1.61.1
IP-TCP header compression IPHC the format the TCP header compression-
Load-interval The 30
Custom- . 1-List Queue
PPP Multilink
PPP Multilink the fragment Delay-10
PPP Multilink interleave
Multilink-Group. 1
IP RTP-header-compression the format the RTP header compression IPHC
Use embodiment the QoS MQC
MQC: Modular the QoS
MQC specific configuration data can take specific action
is divided into three steps: 1. Define traffic policy settings 2. 3. Application Policy
class-map VoIP-RTP
match access-group 100
class-map VoIP-Control
match access-group 101
!
policy-map QoS-Policy
class VoIP-RTP
priority 100
class VoIP-Control
bandwidth 8
class class-default
fair-queue
!
interface serial 0/0
service-policy output QoS-Policy
!
access-list 100 permit ip any any precedence 5
access-list 101 permit tcp any host 10.1.10.20 range 2000 2002
Use autoQoS implement QoS
AutoQoS VoIP support deployment in LAN and WAN environments
AutoQoS Enterprise supports WAN interfaces deployed
router can be deployed enterprise application QoS policy processing voice, video and data traffic
switches can deploy QoS policies through a single command
usage, trimming, development time, support for modular. ,
