Tuc, I think it is the same everywhere: filter our routes that you don't need.
If you have two upstreams, probably just filter out everything with a AS path of three or longer. And ask both of your upstreams to inject a default route (if they are not already doing so). This will result in basically the same traffic distribution (routes with paths or 3 or longer are probalby the same for each upstream anyways), but probably less than 20,000 routes. It depends somewhat on your upstreams though, as a tier1 provider will have a much bigger table of one and two AS hop routes. Tom On Mon, 7 Aug 2006, Tuc at T-B-O-H.NET wrote: > Hi, > > Turns out that I went over my "system-max ip-route 200000" :-/ > > Is there a document somewhere how to run BGP with limited > amounts of memory/routes? > > Thanks, Tuc > >> Hi, >> >> I have a colo customer at a remote site that rebooted his >> box and lost his default route. Short of going onsite to fix it, >> he said if I could forward port 5800 from another IP in the subnet >> he might be able to gain control over the server. Is there some >> way I can do this easily? >> > > _______________________________________________ > foundry-nsp mailing list > foundry-nsp at puck.nether.net > http://puck.nether.net/mailman/listinfo/foundry-nsp >
