You may actually want to look at summarizing this. The best practice would be to have a per-LNS pool (either locally managed or from RADIUS) and advertise the summary from the LNS up to the network. You may need to redistribute also connected routes for "fixed IP" services where a user may have a custom IP from the RADIUS.
Not summarizing means that every connection (and disconnection) is a BGP update driving your CPU utilization across the BGP domain... Arie -----Original Message----- From: cisco-nsp [mailto:[email protected]] On Behalf Of Mike Sent: Monday, August 18, 2014 09:23 To: [email protected] Subject: Re: [c-nsp] LNS question asr 1002 On 08/17/2014 08:24 PM, Edwardo Garcia wrote: > Secondly, how does one handle running two LNS servers? How does the > border router know which edge (LNS) to forward too for a particular > IP? I do it with iBGP where my router is advertising individual /32's. Yes it makes the route tables longer but it works well in my environment. YMMV. Mike- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
