nanog mailing list archives
Prefix filtering for Cisco SUP2
From: "Henry Futzenburger" <henryfutz () gmail com>
Date: Fri, 29 Feb 2008 13:15:10 -0500
I am hoping to help an ISP keep a couple of Cisco 6500's with SUP2's in production for a while longer. They are currently just about at the FIB limit of 250,000 entries, mostly composed of BGP routes. I'm considering two alternatives to reduce the number of entries. 1. Accept only default and partial routes from upstream. a. Accept directly-connected routes, reject everything else and rely on the default route. b. Assume a reduction to about 30,000 unique routes per upstream ISP (currently 3). 2. Accept only default and RIR minimum routes from upstream. a. Filter based on RIR minimums, rely on default for unaggregated routes. b. Assume a reduction of about 50,000-100,000 total routes. Does anyone have any opinions as to whether one option is better than the other? Are there options that would be better than either of these? Are there serious risks to either option? My sense is that either of these would be a fairly benign change, only having a marginal impact on routing efficiency in either case. It seems like the better option is the one that retains the greater number of routes within some margin of safety. What do you think?
Current thread:
- Prefix filtering for Cisco SUP2 Henry Futzenburger (Feb 29)
- Re: Prefix filtering for Cisco SUP2 Andy Dills (Feb 29)
- Re: Prefix filtering for Cisco SUP2 Manolo Hernandez (Feb 29)
- Re: Prefix filtering for Cisco SUP2 Suresh Ramasubramanian (Feb 29)