If the QFabric controllers can do anything it's scale up the number of MACs that can be learned across the fabric. Their solution was novel before SDN and I guess it's to their credit that they are not trying to market the QFabric that way now ;)
rgds, --r On Jan 2, 2014, at 9:10 AM, Eugeniu Patrascu <eu...@imacandi.net> wrote: > On Thu, Jan 2, 2014 at 4:20 PM, giovanni rana > <superburri...@hotmail.com>wrote: > >> Even in the case you mentioned the node shall be able to keep a table >> where there's an index Made by 1536k entries. I can understand that some >> memory can be saved by using a vpls style approach, but if I got 1536k VMs >> with unique and Mac addresses I'm still able to manage them via qfabric? >> Public docs does not clarify enough this aspects. Thanks for your answer! >> >> > You do realise that you are talking about approximately 1,5000,000 MAC > addresses in your network in a flat any-to-any topology and not about 1,500 > or 15,000 MAC addresses ? > > This is how QFabric does MAC learning and forwarding: > http://blog.ipspace.net/2011/09/qfabric-part-3-forwarding.html > > Regards, > Eugeniu > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
