Chris,
I couldn't agree with you more wholeheartedly - and apparently the developers at Juniper are also of similar mindset. Basically, the control plane services are provided by the QF/Director, QF/Node, and the QF/Interconnect devices in the QFabric architecture. This is a highly distributed system which actually consists of redundant control planes (fully independent so as to eliminate fate-sharing mind you) and redundant components within each control plane. The distributed nature of this implementation provides tremendous reliability since it eliminates any single point of failure in the system. Hope that helps to clarify things a bit more. There is a tremendous amount of information which can be found in the whitepapers, I would suggest reading them if you want to learn more about the QFabric architecture. Best Regards, Stefan Fouant, CISSP, JNCIEx2 <http://www.shortestpathfirst.net/> www.shortestpathfirst.net GPG Key ID: 0xB4C956EC From: Chris Evans [mailto:[email protected]] Sent: Thursday, February 24, 2011 12:15 AM To: Stefan Fouant Cc: juniper-nsp; Keegan Holley Subject: Re: [j-nsp] Qfabric We are deploying nexus kit at this point as it meets our needs. Vpc concepts brings fully active forwarding paths to all links just in a different way. Being able to manage a fabric from a single control plane has its positives but also has huge negatives. Having a single control plane for the whole dc reduces you to one fault, one change and one risk domain.. all can bring very bad consequences. This is why I'd like to see a smaller fabric offering so that I can build the same solution just on a smaller scale without having to waste the space the current interconnect requires.. tiers are not a bad thing.. The new fabric topologies are very interesting and will bring design changes i'm sure.. On Feb 23, 2011 9:04 PM, "Stefan Fouant" <[email protected]> wrote: _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
