[c-nsp] OSPF and access prefixes

[Rodney Dunn]

Are you handing out static addresses so you could summarize
in a POP or are you saying you need /32's redistributed
in to OSPF everywhere?

I've seen this before with OSPF:

IP routing table name is Default-IP-Routing-Table(0)
Route Source    Networks    Subnets     Overhead    Memory (bytes)
connected       0           985         63176       157600
static          1           767         49280       122880
ospf 100        13          5334        837632      855520
  Intra-area: 1 Inter-area: 96 External-1: 25 External-2: 5225
  NSSA External-1: 0 NSSA External-2: 0
Total           99122       53581       10162184    26359260

All static routes to customers are redistributed in to OSPF.

Not that I would advise that but that's the way they had it
set up.  It was leased line aggregation.

Rodney


On Fri, Sep 03, 2004 at 02:56:45PM -0400, James Hampton wrote:
> I am with a Broadband provider, and we are in the process of migrating
> to ospf. Our current plan is to use ospf for all interior routing and
> BGP on our edges. I know it is better to use the IBGP/route reflector
> model for access prefixes, but I'm weighing the complexity and
> engineering time it would take to set this up vs. using ospf
> exclusively and switching to IBGP at a later date. I'm really under
> the gun and time is a factor. Does anyone have a similar set up?
> Advice welcome.
> 
> James
> _______________________________________________
> 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/