[c-nsp] QoS on LNS virtual-template

[Clue Store]

Some more info, i'm looking at the Feaure Navigator and see that "QoS:
Classification, Policing, and Marking on LAC" is available on the same
feature set that I would like to move to. Does anyone know if this this
also means "QoS: Classification, Policing, and Marking on LNS" as well??
Anyone from Cisco care to chime in???? I'm gonna lab up some gear later and
test this feature set and see if the policy actually works on the virtual
template.

Clue

On Mon, Nov 30, 2009 at 3:42 PM, Clue Store <cluestore at gmail.com> wrote:

> Sorry, should have included the importants as well.
>
> Im running a little older code 12.3 mainline on NPE-G1. Gonna check to see
> if this is a bug or not a feature, which I also read in another thread.
>
> Clue
>
>   On Mon, Nov 30, 2009 at 3:37 PM, Reuben Farrelly <
> reuben-cisco-nsp at reub.net> wrote:
>
>> Hi,
>>
>> What version of code are you running?
>>
>> I have found 12.4 mainline worked ok, but somewhere along the 12.4T series
>> and including 15.0(M) I cannot apply any QoS policies to Virtual-Access
>> interfaces - policies just don't apply.  I have a TAC case open for this
>> now...
>>
>> Reuben
>>
>>
>> Clue Store wrote:
>>
>>>  Hi All,
>>>
>>> I went through the archives and couldn't find specifically what I was
>>> looking for and of course, most of the Cisco links are broken now, but I
>>> noticed that QoS is applied to my virtual-template interface in my
>>> config,
>>> but when I do a "show policy-map interface virtual-access xx", I get
>>> nothing
>>> as if the policy wasn't inhereted. When I look at my policy-maps, I also
>>> noticed that I do not have parent/child policies configured (which I am
>>> to
>>> understand how you have to configure QoS like this on this type of
>>> interface). Here's an example of what I have on our LNS boxes....
>>>
>>> First question, do I need a child/parent policy to attach the
>>> service-policy
>>> to the virtual-template?
>>>
>>> Second question, do I need to have the "qos pre-classify" command on the
>>> virtual-template??
>>>
>>> Third question, does anyone see anything wrong with the way this is
>>> configured??
>>>
>>>
>>>
>>> class-map match-all VOIP
>>>  match access-group name VoicePorts
>>>  match ip rtp 16384 16383
>>>  match ip dscp ef
>>>
>>>
>>> policy-map DSL
>>>  class VOIP
>>>   priority percent 75
>>>  class class-default
>>>   fair-queue
>>>   random-detect
>>>
>>>
>>> interface Virtual-Template2
>>>  mtu 1460
>>>  ip unnumbered Loopback2
>>>  service-policy output DSL
>>>  ip route-cache flow
>>>  ip tcp adjust-mss 1420
>>>  ip policy route-map clear-df
>>>  qos pre-classify
>>>  peer default ip address dhcp
>>>  ppp authentication pap
>>>  ppp ipcp mask 255.255.255.0
>>>  ppp ipcp address accept
>>>
>>> ip access-list extended VoicePorts
>>>  permit udp host x.x.x.x range 22026 62025 any
>>>  permit udp host x.x.x.x range 22026 62025 any
>>>
>>>
>>> TIA,
>>> Clue
>>> _______________________________________________
>>> 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/
>>>
>>
>