Hi Keegan, > They are saying that the new 16G RE's can handle 250M routes. How is this > possible if none of the daemons are 64bit?
The only real practical scaling use case I am aware of in the range of 5M routes today is for vpnv4 route reflectors. Another possible scaling point would be perhaps in poorly implemented IX route server functionality where you would need to copy entire table to each RS peer in order to execute per peer policy. So indeed if you have 500K of v4 routes and 500 peers it would indeed result in 250M prefixes to be handled. Other then that just from routing point of view I am not sure what's the practical use of such RE or 250M of routes on a real router. I think control plane can scale and 64bit routing stacks migration is already in progress (or even completed and shipping few years back on some other platforms), but forwarding I am afraid is far from that range. So you are left there using either simple-va like approach, come back to old good caching or worse process switching on the RE ;-) Cheers, R. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp