[c-nsp] L2TPv3 Tunnel bandwidth and QoS

Tue Jul 28 05:34:35 EDT 2009

Would you give an example for the nested policy?
I do want to put it in the priority queue, the link that ends the xconnect is an interface connected to a Metro-E service that is physically limited to 2Mb so it won't be able to exceed it anyway, that's why I want to limit it on the router too, while also guaranteeing its priority.
Thanks,
Ziv

From: Arie Vayner [mailto:arievayner at gmail.com]
Sent: Tuesday, July 28, 2009 10:43 AM
To: Ziv Leyes
Cc: Arie Vayner (avayner); Cisco-nsp
Subject: Re: [c-nsp] L2TPv3 Tunnel bandwidth and QoS

Ziv,

You need to apply a nested policy...
The parent policy should do shaping to the real link rate, or else the router does not have any way to know how much bandwidth is really out there.
The child policy should have the policy you want for the different classes.

Are you sure you want to put the tunnel in the priority queue?
You could assign it to a regular class, and just assign "bandwidth" to it.
This would allow the tunnel to burst to more than 2M if the BW is available.

Arie
On Tue, Jul 28, 2009 at 10:11 AM, Ziv Leyes <zivl at gilat.net<mailto:zivl at gilat.net>> wrote:
Thanks,
After looking deeper into the scenario and router configs I kinda managed to come up with it.
I still didn't implement it and if we're talking I'd better show you so you can confirm it will do what I need it to do.
The customer has a 13Mb internet link and I need to set 2Mb for the tunnel, this is what I've set:

ip access-list standard CUSTOMER
 ! this is the customer's rtr - xconnect destination ip:
 permit 12.34.56.78
!
class-map match-all CUSTOMER
 match access-group name CUSTOMER
!
!
policy-map CUSTOMER-L2TPV3
 class CUSTOMER
 priority 2000
 police rate 2000000
!

Ziv

-----Original Message-----
From: Arie Vayner (avayner) [mailto:avayner at cisco.com<mailto:avayner at cisco.com>]
Sent: Monday, July 27, 2009 6:12 PM
To: Ziv Leyes; Cisco-nsp
Subject: RE: [c-nsp] L2TPv3 Tunnel bandwidth and QoS

Ziv,

You should be able to match the tunnel by matching it's IP endpoints.
If you could share more info about your QOS requirements, I could assist
with building the policy.

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net>
[mailto:cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net>] On Behalf Of Ziv Leyes
Sent: Monday, July 27, 2009 11:15
To: Cisco-nsp
Subject: [c-nsp] L2TPv3 Tunnel bandwidth and QoS

Hi all,
I'd like to know if there is a feasible way to guarantee QoS for an
L2TPv3 tunnel
My customer has a 13Mb uplink to the internet and we've set a tunnel
between customer's router and one of our routers, we want to perform
some settings on his side that will assure the L2TP tunnel gets always
2Mb
I know that some settings will not only guarantee but also limit it to
2M, and it's ok for us.
My question is what shall I set as a matching setting? The remote tunnel
IP? The inside IPs?
TIA,

Ziv

************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************