My 2c: The obvious thing for me is if people are running a full ipv4 route table on a box only just capable of handling one single table of that size, then really now is the time to asses if you really need to hold that table or just drop to default +internal+peers. If you have multiple up streams and you are using the route tables to do your route selection then great, but that means you need at least 1M capability now, and really 2+ should be your target. In my experience people running a full table on a small capability box normally don't actually need to carry it, or they just need a bigger box.
- Re: Getting pretty close to default IPv4 ... Jimmy Hess
- Re: Getting pretty close to default IPv4 route maximu... Daniel Suchy
- RE:Getting pretty close to default IPv4 route maximum for ... Darin
- Re: Getting pretty close to default IPv4 route maximum for... Larry Sheldon
- Re: Getting pretty close to default IPv4 route maximu... Irwin, Kevin
- Fwd: Getting pretty close to default IPv4 route m... Shawn L
- Re: Getting pretty close to default IPv4 rout... Alex Lesser
- Re: Getting pretty close to default IPv4 rout... Pete Lumbis
- RE: Getting pretty close to default IPv4 rout... Tony Wicks
- RE: Getting pretty close to default IPv4 ... Tony Wicks
- RE: Getting pretty close to default ... John van Oppen
- Re: Getting pretty close to default IPv4 rout... Nikolay Shopik
- Re: Getting pretty close to default IPv4 ... Irwin, Kevin
- Re: Getting pretty close to default ... Mark Tinka
- Re: Getting pretty close to default ... Nikolay Shopik
- Re: Getting pretty close to defa... Mark Tinka
- Re: Getting pretty close to default IPv4 ... Michael Dikkema
- Re: Getting pretty close to default ... Pete Lumbis
- RE: Getting pretty close to default IPv4 route ma... Vitkovský Adam
- Re: Getting pretty close to default IPv4 rout... Dobbins, Roland