[c-nsp] QoS on 837 using PPPoE

[Victor Lyapunov]

Hello I agree with the others, if you have to apply QoS for an ADSL link
(upstream traffic only) you must enforce some sort of queueing / shaping on
a lower layer. The ATM vc that your connection uses is the just right place
for this.

Just that when I tried something similar I could only make CBWFQ
work properly for the ADSL link if instead of vbr-nrt I used cbr for the VC.

This may be dependant on the IOS version but in any case be prepared to
experiment a little bit with the various QoS settings of the ATM VC.

> correct.  vbr-nrt only affects the output not the input.
>
>
> regards
> .siva
>
> On Tue, 7 Jul 2009, Clue Store wrote:
>
> Hi Siva,
>>
>> Your suggestions seem to have to have worked. Just so that I understand,
>> the
>> vbr-nrt shaping is just for the outbound cells and does not affect inbound
>> traffic correct?? This is a 3m/384k and I do not want to affect their
>> inbound. I could only reserve 288k in my policy (which is fine since the
>> upload is only 384k). And the logs did show why it did not take the
>> command
>> and I was able to adjust my policy as the logs suggested.
>>
>> I/f ATM0.1 VC 1/100 class VoIP requested bandwidth 320 (kbps), available
>> only 288 (kbps)
>>
>> This is now what shows up in the config....
>>
>> policy-map Voice
>> class VoIP
>>  priority 288
>>
>> interface ATM0.1 point-to-point
>> pvc 1/100
>>  vbr-nrt 384 384
>>  encapsulation aal5snap
>>  service-policy output Voice
>>  pppoe-client dial-pool-number 1
>>
>>
>>
>> On Tue, Jul 7, 2009 at 4:32 PM, Siva Valliappan <svalliap at cisco.com>
>> wrote:
>>
>> what does the log messages say?  a show log should tell you why it
>>> didn't accept the commands.
>>>
>>>
>>> On Tue, 7 Jul 2009, Clue Store wrote:
>>>
>>> It took the command under the pvc section, but after a "sho run" the
>>> config
>>>
>>>> did not show up. Nor when I did a "show policy-map interface a0.1" did
>>>> anything show up.
>>>>
>>>> I've looked through several docs on the cisco site, but did not come up
>>>> with
>>>> anything that seem'd to work.
>>>>
>>>> Will try to upgrade the IOS later tonight. Anyone else with any ideas??
>>>>
>>>> On Tue, Jul 7, 2009 at 4:06 PM, Siva Valliappan <svalliap at cisco.com>
>>>> wrote:
>>>>
>>>> IIRC you need to apply it on the ATM interface
>>>>
>>>>> e.g.
>>>>>
>>>>> Interface ATM0.1 point-to-point
>>>>> .
>>>>> .
>>>>> pvc 1/100
>>>>>  service-policy output Voice
>>>>>
>>>>> regards
>>>>> .siva
>>>>>
>>>>>
>>>>>
>>>>> On Tue, 7 Jul 2009, Clue Store wrote:
>>>>>
>>>>>  Hi All,
>>>>>
>>>>>
>>>>>>
>>>>>> I am having a hard time trying to figure how to apply a QoS policy on
>>>>>> this
>>>>>> router. I have applied a few typical service-policies on the dialer
>>>>>> interfaces, but a "show policy interface di0" shows packets being
>>>>>> matched
>>>>>> but nothing being dropped and the link is saturated. I believe the
>>>>>> policy
>>>>>> needs to be applied to the virtual-access interface that comes up when
>>>>>> PPP
>>>>>> negotiates, but i'm not quite sure how this would be done since the
>>>>>> use
>>>>>> of
>>>>>> vpdn-groups are no longer used. Relevent config posted. Any
>>>>>> suggestions
>>>>>> are
>>>>>> greatly appreciated. *And yes I know the service-policy is not applied
>>>>>> to
>>>>>> the dialer interface...this was due to it not working.
>>>>>>
>>>>>>
>>>>>> class-map match-any VoIP
>>>>>> match ip rtp 16384 16383
>>>>>> match access-group name VoicePorts
>>>>>> !
>>>>>> !
>>>>>> policy-map Voice
>>>>>> class VoIP
>>>>>>  priority 256
>>>>>> !
>>>>>> !
>>>>>> !
>>>>>> !
>>>>>> !
>>>>>> interface Ethernet0
>>>>>> ip address 192.168.10.1 255.255.255.0
>>>>>> ip nat inside
>>>>>> ip virtual-reassembly
>>>>>> !
>>>>>> interface Ethernet2
>>>>>> no ip address
>>>>>> shutdown
>>>>>> hold-queue 100 out
>>>>>> !
>>>>>> interface ATM0
>>>>>> no ip address
>>>>>> load-interval 30
>>>>>> no atm ilmi-keepalive
>>>>>> dsl operating-mode auto
>>>>>> !
>>>>>> interface ATM0.1 point-to-point
>>>>>> pvc 1/100
>>>>>>  encapsulation aal5snap
>>>>>>  pppoe-client dial-pool-number 1
>>>>>> !
>>>>>> !
>>>>>> interface FastEthernet1
>>>>>> duplex auto
>>>>>> speed auto
>>>>>> !
>>>>>> interface FastEthernet2
>>>>>> duplex auto
>>>>>> speed auto
>>>>>> !
>>>>>> interface FastEthernet3
>>>>>> duplex auto
>>>>>> speed auto
>>>>>> !
>>>>>> interface FastEthernet4
>>>>>> duplex auto
>>>>>> speed auto
>>>>>> !
>>>>>> !
>>>>>> interface Dialer0
>>>>>> ip address negotiated
>>>>>> ip mtu 1492
>>>>>> ip nat outside
>>>>>> ip virtual-reassembly
>>>>>> encapsulation ppp
>>>>>> ip tcp adjust-mss 1412
>>>>>> dialer pool 1
>>>>>> no cdp enable
>>>>>> <ppp info ************>
>>>>>> !
>>>>>> ip forward-protocol nd
>>>>>> ip route 0.0.0.0 0.0.0.0 Dialer0
>>>>>> !
>>>>>> ip http server
>>>>>> no ip http secure-server
>>>>>> !
>>>>>> no ip nat service skinny tcp port 2000
>>>>>> no ip nat service sip udp port 5060
>>>>>> ip nat inside source list 10 interface Dialer0 overload
>>>>>> !
>>>>>> !
>>>>>> ip access-list extended VoicePorts
>>>>>> permit udp any host *.*.*.* range 22026 62025
>>>>>> permit udp any host *.*.*.* range 22026 62025
>>>>>> access-list 10 permit 192.168.10.0 0.0.0.255
>>>>>> _______________________________________________
>>>>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>