No, queueing (be it custom, class-based, or priority) is what you need. Rate-limiting will not order traffic for you, it simply sets a ceiling for the amount of traffic that can be sent. So, let's say you use rate-limiting and set your "limit" to be 500K. Then, 400K of FTP traffic needs to be sent, followed by 200K of Oracle. The 400K of FTP would be sent, but then only 100K of Oracle would be sent. The other 100K would be dropped. Thus, you have not achieved your goal.
When you use queueing, the router will get the 400K of FTP and the 200K of Oracle and send the Oracle first. After the Oracle traffic has been sent, the FTP traffic will be sent. Now, you have achieved your goal.
If there is a need to "limit" the traffic, you can use queuing and rate-limiting. First, queue the traffic correctly so the Oracle and telnet goes first, but limit the overall traffic to a certain bandwidth. So, back to our example, you can still rate-limit to 500K, but queue the traffic so the 200K of Oracle traffic goes first, then 300K of FTP traffic is sent. The remaining 100K of FTP traffic will be dropped and re-transmitted by the server, but this is ok since it's not mission critical traffic.
Here is a good link to start reading about Cisco QoS
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...