There is a class called class-default that will get anything that is not committed to anything else. There is no need to configure one since you can put any options in that class.
I suspect the example you give will not work as you intend. The percent keyword works off the bandwidth statement. This will cause in your case 1024k to be reserved. The issue is this is really only 10% if a fast ethernet interface. The bandwidth statement does not have any effect on how much data actually passes though a interface.
To avoid issues with routing protocols like OSPF and to not get confusing reports from tools that use this number to calculate utilization I would always set the bandwidth correctly and make my QoS setting correspond.
If you intention was to limit the traffic using the bandwidth statement you will need to use a traffic shaper to limit the traffic to 4 m and then apply the QoS within the shaping.
Other than a small amount of router traffic that is not in any class all traffic that does not fall in another class goes into the default class.
In your case it is confusing to say 75% but in a very broad sense it will. Since the ethernet port can run at 100m and you have reserved 1m (ie 25% of 4096k) the remaining 99m goes into class default which is 99%. So you reserved 1m which is 1% of the interface but 25% of the declared bandwidth. I tend to use explict reservations when I do priority queueing rather than percent to avoid someone changing my bandwidth to try to influence the routing and screwing up the QoS.
In your case as long your MPLS provider will honor you EF markings and you have at least 1m of guarenteed low latency in your contract it will work. If you were to send 10m of traffic for a sustained time the provider should always pass the 1m voice traffic and drop up to 7m of the other. If your MPLS provider limits you to 4m before it looks at the packet markings you could have issues.
I tend to like to control which traffic is dropped myself so I would shape the traffic to 4m before it left my router.
To limit the traffic to 4m you would do
shape average 4000000
service policy MPLS-EDGE
You would apply the shape01 to the fast ethernet interface.
Even the above example is using the class-default which since there are no other class statements is 100%.
With the shaping in place your priority class still has 1m but the class-default within your MPLS-EDGE policy is now limited to 3m which is correctly corresponds to 75% if you want to look at the number that way.
That was a typo.. i would shape the traffic via a policy & a Class.
Mostly when i read about shaping it mentioned as to be used for non real time traffic. so if i use priority as well as the shape command, would it affect my VoIP traffic if the interafce starts queuing the voice packets
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.