02-16-2016 03:39 PM - edited 03-05-2019 03:21 AM
I am trying to prioritize traffic for my PS3 to take priority over the other devices on my LAN. When I try to apply the service-policy to the ATM PVC is it not taking. I have two requirements:
1)Prioritize PS3 traffic to 80 %
2)Police the outbound traffic to 7.2 Mbps due to a bufferfloat issue
Here is my current config for a policer:
policy-map POLICE_OUT
class class-default
police cir 720000
conform-action transmit
exceed-action drop
interface ATM0/0/0.1 point-to-point
pvc 0/32
service-policy output POLICE_OUT
pppoe-client dial-pool-number 1
Here is the config I am trying to use but whenever I apply the service policy, it doesn't take/commit. I don't get any
ip access-list standard PS3
permit 192.168.0.4
class-map match-any PS3
match access-group name PS3
class-map match-all OTHER
match any
policy-map TEST
class PS3
bandwidth percent 79
class OTHER
bandwidth percent 20
class class-default
police cir 720000 bc 22500
conform-action transmit
exceed-action drop
02-16-2016 04:28 PM
It would help to know what the router is, and what software version you are using.
Try putting everything on the one physical interface.
interface ATM0
pvc 0/132
vbr-nrt 500 500
tx-ring-limit 3
dialer pool-member 1
service-policy out POLICE_OUT
...
02-16-2016 04:49 PM
It is a 1841 running 12.4T(13r), put my configs on the physical ATM interface and not the subinterface?
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
bundle en
!
dsl operating-mode auto
!
interface ATM0/0/0.1 point-to-point
pvc 0/32
service-policy output POLICE_OUT
pppoe-client dial-pool-number 1
!
02-16-2016 05:05 PM
Delete the entire sub-interface, and use something more like what I supplied.
You might need to move to a 15.x IOS train to make this work.
02-16-2016 05:16 PM
Ok I put the configs on the physical ATM interface and it took the command. The issue now is that it is not catching the traffic coming from the PS3 or OTHER_TRAFFIC classes, only the class-default.
ChrisRouter#sh policy-map interface
ATM0/0/0
Service-policy output: TEST
Class-map: PS3 (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name PS3
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 79% (704 kbps)
Class-map: OTHER_TRAFFIC (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name OTHER
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
bandwidth 20% (178 kbps)
Class-map: class-default (match-any)
16798 packets, 3150774 bytes
5 minute offered rate 51000 bps, drop rate 0 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
police:
cir 720000 bps, bc 22500 bytes
conformed 16450 packets, 2753004 bytes; actions:
transmit
exceeded 307 packets, 394742 bytes; actions:
drop
conformed 57000 bps, exceed 0 bps
02-16-2016 05:18 PM
Your ATM interface is referencing a policy called POLICE_OUT, while your service policy appears to be called TEST.
02-16-2016 05:21 PM
This is what is configured for:
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
bundle en
!
dsl operating-mode auto
service-policy output TEST
pvc 0/32
pppoe-client dial-pool-number 1
!
end
02-16-2016 05:22 PM
I'm thinking that by the time it is checking your access list the traffic is already NAT'd. Hence no match.
I think you would be better matching on a DSCP QoS marker, and mark the PS3 traffic on the way into the router.
02-16-2016 05:25 PM
so mark it by applying a service policy to the LAN interface as it comes in with DSCP values? I have to do this per IP because the PS3 cannot tag any traffic with DSCP values in the IP header.
02-16-2016 05:31 PM
Yes, exactly.
You may be able to do it on the actual physical port that the PS3 plugs into. This would make it easy, since you would just be tagging every packet.
02-16-2016 06:08 PM
oh ok thanks I'll play with that.. Are you sure this isn't anything to do with how my class-maps are built? Kinda weird how it is being NATed before QoS
02-17-2016 06:11 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Well, I guess one could argue, you want to apply QoS to the packets, as they are, that will be transmitted.
BTW, if your DSL is aDSL, to make your QoS effective, you'll want to shape egress for your logical outbound/upstream bandwidth limit, otherwise, QoS (excluding your policing statement) won't "trigger" until the interface congests.
Oh, and could you explain why you need to police for "bufferfloat"?
Lastly, you might find a simple class-default, using FQ, might well deal with your QoS needs (although you'll still need to shape).
02-16-2016 04:29 PM
I have a ConfigWizard for Cisco 890 series routers. It wont do exactly what you want, but take a look at how it generates the QoS configuration.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide