CCIE Voice Training, Environment the DSCP or TOS Field
January 13th,2012 by NicholasThe answer to this difficulty depends upon the sort of site traffic distinctions you choose to produce, in addition the version of IOS you will be running in your own routers. CCIE Voice Training
There have to be a thing that defines the various varieties of site visitors that you want to prioritize. Normally, the more simple the distinctions are to help make, the higher. It's because each of the exams take router assets and introduce processing delays. The most prevalent guidelines for distinguishing around customers sorts use the packet's input interface and straight forward IP header facts these types of as TCP port numbers. The next examples display find out how to set an IP Precedence price of fast (2) for all FTP handle site traffic that arrives through the serial0/0 interface, and an IP Precedence of concern (1) for all FTP knowledge website traffic. This distinction is feasible due to the fact that FTP manage site traffic uses TCP port 21, and FTP knowledge employs port twenty.
The new methodology for configuring this employs course maps. Cisco 1st launched this characteristic in IOS Model twelve.0(5)T. This method earliest defines a class-map that specifies how the router will detect this kind of site traffic. It then defines a policy-map that truly helps make the adjustments with the packet's TOS discipline:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#class-map match-all ser00-ftpcontrol
Router(config-cmap)#description branch ftp control traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 101
Router(config-cmap)#exit
Router(config)#class-map match-all ser00-ftpdata
Router(config-cmap)#description branch ftp data traffic
Router(config-cmap)#match input-interface serial0/0
Router(config-cmap)#match access-group 102
Router(config-cmap)#exit
Router(config)#policy-map serialftppolicy
Router(config-pmap)#description branch ftp traffic policy
Router(config-pmap)#class ser00-ftpcontrol
Router(config-pmap-c)#set ip precedence immediate
Router(config-pmap-c)#exit
Router(config-pmap)#class ser00-ftpdata
Router(config-pmap-c)#set ip precedence priority
Router(config-pmap-c)#exit
Router(config-pmap)#exit
Router(config)#interface serial0/0
Router(config-if)#ip route-cache policy
Router(config-if)#service-policy input serialftppolicy
Router(config-if)#exit
Router(config)#end
Router#
For previously IOS variations, where exactly class-maps were not offered, you will have to utilize policy-based routing to alter the TOS subject in a packet. Applying this coverage to your interface tells the router to use this policy to check all incoming packets on this interface and rewrite the ones that match the route map:Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#access-list 101 permit any eq ftp any
Router(config)#access-list 101 permit any any eq ftp
Router(config)#access-list 102 permit any eq ftp-data any
Router(config)#access-list 102 permit any any eq ftp-data
Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 101
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#exit
Router(config)#route-map serialftp-rtmap permit 20
Router(config-route-map)#match ip address 102
Router(config-route-map)#set ip precedence priority
Router(config-route-map)#exit
Router(config)#interface serial0/0
Router(config-if)#ip policy route-map serialftp-rtmap
Router(config-if)#ip route-cache policy
Router(config-if)#exit
Router(config)#end
Router#
Right before you are able to tag a packet for particular procedure, you could have to obtain an extremely distinct idea of what forms of targeted traffic need particular treatment, and exactly what kind of wonderful procedure they will absolutely need. Around the instance, we have now made a decision to give a special concern to FTP site visitors obtained on a specific serial interface. We clearly show simple methods to try this employing equally the previous and new configuration approaches.
This will likely look to get a rather synthetic case in point. Right after all, why would you treatment about tagging inbound visitors that you simply have previously received from a low-speed interface? In fact, one of the many most vital principles for applying QoS inside a network is the fact you need to constantly tag the packet as early as is possible, preferably at the edges in the network. Then, as it passes in the network, just about every router only has to take a look at the tag, and isn't going to ought to do any added classification. In this instance, we would be certain which the FTP site traffic returning inside other direction is tagged by to start with router that gets it. And so the outbound customers has by now been tagged, and it is a waste of router sources to reclassify the outbound packets.
Numerous organizations in fact just take this idea of marking with the edges just one stage even more, and remark each received packet. This can help to make sure that customers are not requesting particular QoS privileges which they are not allowed to acquire. Even so, you ought to be thorough of this mainly because it could every now and then disrupt reputable markings. For example, a real-time software could use RSVP to reserve bandwidth from the network. Its essential the packets for this software hold the correct Expedited Forwarding (EF) DSCP marking or even the network might not cope with them effectively. Even so, you also don't desire to allow other non-real-time apps from this same exact supply have the exact same EF concern amount. So, when you're going to configure your routers to remark all incoming packets with the edges, be sure you realize what incoming markings are reputable.
In that situation, the routers are working DLSw to bridge SNA site visitors through an IP network. Therefore the routers themselves actually generate the IP packets. This creates an extra problem because there is no incoming interface. To ensure that recipe makes use of community policy-based routing. The fact which the router creates the packets also provides it a vital benefit seeing that it doesn't have to consider any DLSw packets which may just transpire to go through.
The advantages belonging to the more recent class-map technique aren't evident in such a illustration, but one of several number one huge features appears in order for you to use the more contemporary DSCP tagging scheme. Since the more mature policy-based routing procedure doesn't specifically support DSCP, you may have to pretend it by environment the two the IP Precedence as well as the TOS separately as follows.
Router(config)#route-map serialftp-rtmap permit 10
Router(config-route-map)#match ip address 115
Router(config-route-map)#set ip precedence immediate
Router(config-route-map)#set ip tos max-throughput
In this case, the packet will wind up with an IP Precedence value of immediate, or 2 (010 in binary), and TOS of max-throughput, or 4 (0100 in binary).
Doing the same thing with the class-map method is much more direct:
Router(config)#policy-map serialftppolicy
Router(config-pmap)#class serialftpclass
Router(config-pmap-c)#set ip dscp af21
Class-maps will likely be invaluable afterwards within this chapter when we speak about class-based weighted truthful queuing and class-based page views shaping.
It is necessary to notice that all the way through this whole instance, now we have only place a specific price to the packet's TOS or DSCP field. This, by by itself, won't affect how the packet is forwarded by the network. To accomplish that, you need to make sure that as every single router inside network forwards these marked packets, the interface queues will react appropriately to this facts.
At last, we must always be aware that although this recipe shows two helpful approaches of marking packets, implementing Dedicated Accessibility Charge (Car) functions. Autobus tends to be significantly more reliable on greater pace interfaces.