Hi, sorry, but 88% used does not mean you really have 12% you can use. 3 years ago we were at similar situation, one of our 3BXL had 92 or 93% usage and restarted the bgp process because it was unable to allocate more memory. We thought to have a few more months and waited to long to replace it. So 88% mean "disable one session" and not "add another one".
If you want to use 6500/7600, go for the Sup2T (XL was around 9k Euro - before Brexit) + 4Gig memory. You can still built a up to 80GBit throughput box with a great router port amount per money if you use 6700 linecards with CFC (WS-X6748-GE-TX below 200Euro, WS-X6704-10GE below 500Euro) and can live with the risk that 1M routes could become an issue in a few years. kind regards Rolf > 15.7.2016, 17:13, Nick Hilliard wrote: >> TCAM is fine for the time being, but RP RAM is definitely a problem on >> this platform. The RP has 1G of RAM, non-upgradable. A DFZ will work >> for the time being if you run 12.2SX. If you run 15S, there's less >> space and it will not run unless you disable inbound soft reconfig. In >> either case, it's not going to be viable in the long term. >> > Yes, with 15.X IOS you will be at 90% in memory usage. We have one box > (15.1(2)SY4a IOS) with two full feeds and a lot of features enabled - > the memory usage is 88%. There is still room for a third full BGP feed. > I'm not concerned about this, since even with an empty config the memory > usage is quite high. However, it's stable and doesn't vary much. > > But yeah, 6500 is not the best choice for the future. > > zzif > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/