Mailing List Archive

Hi Simon,

You don't need to have a contiguous IP block in an IP Pool. You can simply
do something like this:

TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255

Hope this helps,

Nasser

-----Original Message-----
From: cisco-bba [mailto:cisco-bba-bounces@puck.nether.net] On Behalf Of
Simon Lockhart
Sent: Tuesday, July 4, 2017 3:45 PM
To: cisco-bba@puck.nether.net
Subject: [cisco-bba] Using more than one IP Local Pool

All,

We've got a rapidly increasing userbase on xDSL, terminating on a couple of
ASR1001X's as LNS's. The majority are on dynamic IP.

Currently, we're using one "ip local pool" per LNS, and specifying this via
a radius attribute:

Cisco-AVPair += "ip:addr-pool=dynamic-dsl"

Each time we've run out of space in the pool, we've just replaced it with a
bigger contiguous subnet.

However, we're now at the point where we can't keep growing a contiguous IP
address range, so need to specify multiple ranges.

Without partitioning our users, is there a way to use multiple address
ranges for dynamic users like this?

Or are we doing it all wrong? :)

Simon
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

On Tue Jul 04, 2017 at 04:17:22PM +0430, Nasser Heidari wrote:
> You don't need to have a contiguous IP block in an IP Pool. You can simply
> do something like this:
>
> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255

D'Oh! Don't know why we didn't try that :) Yup, works just fine :)

lns-01#show ip local pool

Pool Begin End Free In use
test-dsl 192.168.1.0 192.168.1.255 256 0
192.168.2.0 192.168.2.255 256 0

Many thanks!

Simon
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

Hi Simon,

I personally haven't looked at this in ages and can't remmeber. Can
you add subnets to the IP/DHCP pool on the LNS?

If not, can you set up multiple tries and try to make them option;

Cisco-AVPair += "ip:addr-pool*dynamic-dsl-pool-1"
Cisco-AVPair += "ip:addr-pool*dynamic-dsl-pool-2"

This "*" makes the AV pair optional.

Cheers,
James.
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

> You don't need to have a contiguous IP block in an IP Pool. You can simply
> do something like this:
>
> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255

Remember that there exists an special IPv4 Address-range for "Carrier Grade
NAT".

Why not assign fixed (real) IPv4/32 for each dial-up account ?

Just my 0.01 $

Juergen.

_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

On 4 July 2017 at 22:41, Juergen Marenda <cnsp@marenda.net> wrote:
>> You don't need to have a contiguous IP block in an IP Pool. You can simply
>> do something like this:
>>
>> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
>> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
>> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255
>
> Remember that there exists an special IPv4 Address-range for "Carrier Grade
> NAT".
>
> Why not assign fixed (real) IPv4/32 for each dial-up account ?
>
> Just my 0.01 $
>
> Juergen.

We use static IPs for all xDSL customers/sites, one problem we have
from this is that each LNS (depending on which one the customer
connects to) is announcing loads of /32's into our iBGP that aren't
aggregatable/summary routes, which they would be if we had a unique
pool per LNS. We have thousands of extra routes in our iBGP because of
this, it's not a major issues but still not ideal.

Cheers,
James.
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

On Wed, 2017-07-05 at 08:23 +0100, James Bensley wrote:
> On 4 July 2017 at 22:41, Juergen Marenda <cnsp@marenda.net> wrote:
> >> You don't need to have a contiguous IP block in an IP Pool. You can simply
> >> do something like this:
> >>
> >> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
> >> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
> >> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255
> >
> > Remember that there exists an special IPv4 Address-range for "Carrier Grade
> > NAT".
> >
> > Why not assign fixed (real) IPv4/32 for each dial-up account ?
> >
> > Just my 0.01 $
> >
> > Juergen.
>
> We use static IPs for all xDSL customers/sites, one problem we have
> from this is that each LNS (depending on which one the customer
> connects to) is announcing loads of /32's into our iBGP that aren't
> aggregatable/summary routes, which they would be if we had a unique
> pool per LNS. We have thousands of extra routes in our iBGP because of
> this, it's not a major issues but still not ideal.
>
> Cheers,
> James.

You can have each LNS aggregate part of the address space, then when a
customer with IP that matches the aggregate lands on this LNS
customers /32 won't be advertised, but when the customer lands on a
different LNS /32 will go into your iBGP. Depending on luck you could
cut in half the number of /32 in your iBGP.

_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

Cisco has an interesting feature called ODAP (On Demand Address Pools). The
idea is that the router will go and request additional pools from a DHCP
server whenever a utilization threshold has been hit. It also has the
capablity to release pools back (on router restart or if utilization went
down).

I do not think it is widely implemented, but I have implemented it in the
past and it works.

http://www.cisco.com/c/en/us/td/docs/net_mgmt/access_registrar/1-7/user/guide/odap.html
https://youtu.be/V7Qc25B-51I

Tnx
Arie

On Wed, Jul 5, 2017 at 3:35 AM Krzysztof Adamski <k-list@adamski.org> wrote:

> On Wed, 2017-07-05 at 08:23 +0100, James Bensley wrote:
> > On 4 July 2017 at 22:41, Juergen Marenda <cnsp@marenda.net> wrote:
> > >> You don't need to have a contiguous IP block in an IP Pool. You can
> simply
> > >> do something like this:
> > >>
> > >> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0 192.168.255.255
> > >> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0 172.31.255.255
> > >> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0 10.255.255.255
> > >
> > > Remember that there exists an special IPv4 Address-range for "Carrier
> Grade
> > > NAT".
> > >
> > > Why not assign fixed (real) IPv4/32 for each dial-up account ?
> > >
> > > Just my 0.01 $
> > >
> > > Juergen.
> >
> > We use static IPs for all xDSL customers/sites, one problem we have
> > from this is that each LNS (depending on which one the customer
> > connects to) is announcing loads of /32's into our iBGP that aren't
> > aggregatable/summary routes, which they would be if we had a unique
> > pool per LNS. We have thousands of extra routes in our iBGP because of
> > this, it's not a major issues but still not ideal.
> >
> > Cheers,
> > James.
>
> You can have each LNS aggregate part of the address space, then when a
> customer with IP that matches the aggregate lands on this LNS
> customers /32 won't be advertised, but when the customer lands on a
> different LNS /32 will go into your iBGP. Depending on luck you could
> cut in half the number of /32 in your iBGP.
>
> _______________________________________________
> cisco-bba mailing list
> cisco-bba@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-bba
>

I would like to say thank you for sharing this information. I've been
looking for a way to hold all my pools in a central location instead of
having to double/triple up on pool sizes in order to account for an LNS
failure.

Andrew.


On 7/5/2017 11:29 AM, Arie Vayner wrote:
> Cisco has an interesting feature called ODAP (On Demand Address
> Pools). The idea is that the router will go and request additional
> pools from a DHCP server whenever a utilization threshold has been
> hit. It also has the capablity to release pools back (on router
> restart or if utilization went down).
>
> I do not think it is widely implemented, but I have implemented it in
> the past and it works.
>
> http://www.cisco.com/c/en/us/td/docs/net_mgmt/access_registrar/1-7/user/guide/odap.html
> https://youtu.be/V7Qc25B-51I
>
> Tnx
> Arie
>
> On Wed, Jul 5, 2017 at 3:35 AM Krzysztof Adamski <k-list@adamski.org
> <mailto:k-list@adamski.org>> wrote:
>
> On Wed, 2017-07-05 at 08:23 +0100, James Bensley wrote:
> > On 4 July 2017 at 22:41, Juergen Marenda <cnsp@marenda.net
> <mailto:cnsp@marenda.net>> wrote:
> > >> You don't need to have a contiguous IP block in an IP Pool.
> You can simply
> > >> do something like this:
> > >>
> > >> TestBNG(config)# ip local pool dynamic-dsl 192.168.0.0
> 192.168.255.255
> > >> TestBNG(config)# ip local pool dynamic-dsl 172.16.0.0
> 172.31.255.255
> > >> TestBNG(config)# ip local pool dynamic-dsl 10.0.0.0
> 10.255.255.255
> > >
> > > Remember that there exists an special IPv4 Address-range for
> "Carrier Grade
> > > NAT".
> > >
> > > Why not assign fixed (real) IPv4/32 for each dial-up account ?
> > >
> > > Just my 0.01 $
> > >
> > > Juergen.
> >
> > We use static IPs for all xDSL customers/sites, one problem we have
> > from this is that each LNS (depending on which one the customer
> > connects to) is announcing loads of /32's into our iBGP that aren't
> > aggregatable/summary routes, which they would be if we had a unique
> > pool per LNS. We have thousands of extra routes in our iBGP
> because of
> > this, it's not a major issues but still not ideal.
> >
> > Cheers,
> > James.
>
> You can have each LNS aggregate part of the address space, then when a
> customer with IP that matches the aggregate lands on this LNS
> customers /32 won't be advertised, but when the customer lands on a
> different LNS /32 will go into your iBGP. Depending on luck you could
> cut in half the number of /32 in your iBGP.
>
> _______________________________________________
> cisco-bba mailing list
> cisco-bba@puck.nether.net <mailto:cisco-bba@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-bba
>
>
>
> _______________________________________________
> cisco-bba mailing list
> cisco-bba@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-bba