Hello Rarylson
Thanks for sharing your results! I’ve created a NetworkLessons note on the subject for future reference.
Thanks again!
Laz
1 Like
having a bandwidth of 90 Mbps.
Having two LAN POOL: DATA: 192.168.1.0/29 & VC: 192.168.1.8/29.
90 Mbps of Bandwidth is overutilized by DATA Pool.
Need to configure Priority Bandwidth if VC is connected then 30Mbps must be used for VC Network & 60Mbps for DATA Network.
If VC Traffic is not established, then DATA Pool can use of 90 Mbps.
Highly appreciate it if you will help in that case.
Hello Pratik
From what I understand, you have an interface with a bandwidth of 90 Mbps, and you want to reserve 30 Mbps for use with VC. This can be achieved using queuing and classification. If you classify your packets coming from the VC LAN, you can then apply the bandwidths you want to that traffic. Take a look at this lesson that describes how it can be done:
Queueing prioritizes traffic and can ensure that your VC traffic will have guaranteed bandwidth even under the most congested situations.
Take a look at this and if you have more questions about it, let us know!
I hope this has been helpful!
Laz
We attempted this, but the router does not support a few commands.
Priority base bandwidth allocations are desired. Like voice (25%), video (25%), and default (50%), for inbound and outbound.
If voice and video are not used, then 100% must be used.
Hello Pratik
Can you let us know a little bit more about your specific implementation? What platform and IOS are you using? Have you checked Cisco’s feature navigator to see if your platform/IOS combination supports the appropriate QoS features that you’re trying to employ?
Let us know so that we can help you further!
I hope this has been helpful!
Laz
Hello, everyone!
The OCG says, that we can implement a hierarchical QoS policy map, meaning that we apply a service-policy to another policy-map
What is the benefit of this? And also does that change our processing order? Does anyone please have an example where this could be used?
Thank you.
David
Hello David!
The main benefit of implementing a hierarchical QoS policy map is that it provides more granular control over traffic management. It allows you to nest policy maps within other policy maps, essentially creating a hierarchy of policies. This can be particularly useful in complex networks where you need to manage different types of traffic with different QoS requirements.
The processing order is indeed affected. The policies are processed from the top down, starting with the parent policy map and then moving to the child policy. If a packet matches a class in the parent policy map, the actions defined in that class are taken, and then the child policy map (if any) associated with that class is evaluated.
Here is a simple example of how this hierarchy could be used:
Say you have a business network where you need to prioritize video conferencing traffic over other types of traffic (like web browsing), but within the video conferencing traffic, you also need to prioritize traffic from your CEO’s device. You could create a parent policy map that prioritizes video conferencing traffic, and then a child policy map within that parent policy map that further prioritizes traffic from your CEO’s device.
Here’s a simplified configuration example:
! Define the child policy
policy-map CEO-VIDEO-POLICY
class CEO-VIDEO-CLASS
priority percent 50
! Define the parent policy
policy-map VIDEO-POLICY
class VIDEO-CLASS
priority percent 70
service-policy CEO-VIDEO-POLICY
In this example, the parent policy map (VIDEO-POLICY) prioritizes all video conferencing traffic, dedicating 70% of the available bandwidth to it. Then, within that prioritized video conferencing traffic, the child policy map (CEO-VIDEO-POLICY) further prioritizes traffic from the CEO’s device, dedicating half of the video conferencing bandwidth to it.
I hope this has been helpful!
Laz
1 Like
Hello, for people learning this for the first time, wouldn’t it be easier to understand by naming the access list and class map differently? It seems like you’re applying the access list to the map.
Hello Gregory
In the lesson, Rene names the class-map “TELNET” and the ACL “TELNET”. That can be confusing since the same name is being used for two different entities. I will let Rene know to consider making the change. Thanks for your suggestion!
I hope this has been helpful!
Laz
1 Like
thank you for confirming Laz!
1 Like
In LLQ lesson, where did we mark the packets ? I could not understand it. All i see is the dscp ef and cs3 were given priority according to their classes. Did i miss something ?
Hello Girish
I believe you’re talking about the QoS LLQ (Low Latency Queueing) on Cisco IOS lesson, correct? In this lesson, R1 is configured with the CBWFQ using LLQ using policy maps, and it only responds to the marked packets. In other words, it employs the QoS mechanism on packets that are already marked. No marking takes lace on this router.
In the verification section, you can see that R1 generates pings that are sent through R2 to reach R3. The policy map is triggered for all such traffic.
Now, to your question, where are the packets marked? If you notice the ping command that is used to send the traffic:
R1#ping 192.168.23.3 tos 184 repeat 100
and
R1#ping 192.168.23.3 tos 96 repeat 200
This command sets the Type of Service or the ToS in the header of the IP packet. This is the field where the DSCP values live. More info can be found at this NetworkLessons note. So by using a value of 184 for the ToS, this corresponds to DSCP EF, and a value of 96 corresponds to a DSCP value of CS3.
So the packets are marked at their source, during the ping itself. Does that make sense?
I hope this has been helpful!
Laz