North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: Prefix filtering for Cisco SUP2
- From: Manolo Hernandez
- Date: Fri Feb 29 14:19:09 2008
In my past experience with the SUP2/MSFC2 combo you are best off with
option 2. Minimize the FIB entry of what you control like BGP route
entries. You never know what can happen to cause the FIB to run up again
and cause the CPU to spike.
Henry Futzenburger wrote:
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
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?