Re: Article on Juniper QFabric

Hi Alexander,

I would say it is a much better architecture for various reasons.

1. With Nexus FEX, the N2K act as line cards & all traffic has to be sent
to the parent N5K whereas the QFnodes have a routing engine to decide where
to send the packet.
2. There is only a single lookup across the whole system. There is a Fabric
Header that is added by the QFnodes to determine which QFnode the packet
should be sent to .
3. The system can scale up to 6,144 10GE ports and still managed as a
single switch.
4. Fully converged I/O in terms of connecting the SAN switches to the
QFnodes.

http://juniper.mwnewsroom.com/press-releases/deutsche-boerse-group-selects-juniper-networks-to--nyse-jnpr-0816396
http://newsroom.juniper.net/press-releases/bell-canada-selects-juniper-networks-single-tier--nyse-jnpr-0811293

Thank You

On Sat, Jun 2, 2012 at 10:54 AM, Alexander Halim <cisco.alexand_at_gmail.com>wrote:

> It seems similar to Nexus FEX but with much higher port density. But has
> anyone deployed QFabric in production?
>
> Regards,
> Alexander Lim
>
> On Jun 2, 2012, at 4:48 AM, Sukhjit Hayre <sukhjit.hayre_at_googlemail.com>
> wrote:
>
> >
> http://m.zimbio.com/Cisco+Systems+Inc./articles/k8ulf-PRjAg/Juniper+QFabric+smashed+Cisco+dreams
> >
> > --
> > BR
> >
> > Tony CCNP CCNA R&S JNCIS-SEC MCSE
> >
> > Sent from my iPhone on 3
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
KJ
Blogs and organic groups at http://www.ccie.net