[c-nsp] 2 full BGP feeds on 3750?

Peter Salanki peter.salanki at bahnhof.net
Tue Sep 5 16:51:22 EDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I agree on that solution. I believe that the meaning of having full  
table in a small-sp environment is highly overrated, usually only a  
small part of the internet represents 60-90% of your traffic

Sincerely

Peter Salanki
Chief Network Engineer
Bahnhof AB (AS8473)
www.bahnhof.se
Office: +46855577132
Cell: +46709174932


5 sep 2006 kl. 22.40 skrev Anton Kapela:

>
>
>> Anybody successfully multi-homing using a 3750 with a full
>> BGP table from each provider? I'm thinking no, but ...
>
> On 3550/3750/$low_end_l3_switch you cannot ever hope to receive &
> install a full table of routes.
>
> With that said (and after eyeballing
> http://bgp.potaroo.net/rv-index.html for a while), you could probably
> put your switch into the 'routing' sdm profile (11k unicast l3  
> entries),
> filter all prefixes longer than /15 and probably not overflow the  
> tcam.
> This would get you some reasonable directivity (used loosely) toward
> your largest destination netblocks given your platform. Set a 0/0
> towards some upstream, and you're good to go.
>
> -Tk
>
> _______________________________________________
> 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/




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFE/eNLiQKhdiFGiogRAuudAJ0euzpk5acij89PFTrgsJA0ZqI0HACfcPR7
n4yHOpPcCpK9tlJOIyRGW84=
=TyxP
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list