[j-nsp] Qfabric

[Chris Evans]

I need hundreds of switches per data center. That doesn't scale.  Small
shops sure. Big ones that would push this system to its limits, no.
On Feb 23, 2011 10:01 PM, "Darren Bolding" <darren at bolding.org> wrote:
> To be fair, the EX switches offer flavors that virtual
chasis/cluster/stack
> nicely, and are managed via one IP.
>
> The stacking can be done both by proprietary VC cables or over 10G links,
> allowing rows of cabinets to have a redundant loop via a 10G connection
> between the first and last cabinets.
>
> May still justifiably be called a hack, but perhaps less than one
requiring
> a separate IP/Switch per cabinet. This is true with or without QFabric in
> the equation.
>
> --D
>
> On Wed, Feb 23, 2011 at 5:05 PM, Chris Evans <chrisccnpspam2 at gmail.com
>wrote:
>
>> I think its a sexy solution however it falls short in areas to meet our
>> needs. I think Juniper has something going for them, however its misses
on
>> a
>> lot of contexts so far.
>>
>> 1. We no longer install structured copper in our data centers as we have
>> gone fully top of rack. The edge Qfabric devices require a copper
>> connection
>> back to the routing engine complex. It needs to option to use sfp optics
so
>> we can do fiber for this link.
>>
>> 2. We still like most people deploy 90% GigE and will for the next year
or
>> so at least. Stratus needs a copper GigE offering. Even if we went full
>> 10Gig for production interfaces, servers still need management
connectivity
>> which iare copper based and also 100Meg most times. Our account team
>> suggested that we deploy EX devices to meet these needs, however that is
a
>> hack solution and something we won't entertain. Deploying EX's gets us
back
>> to the original issue of having remote devices all managed individually.
>>
>> 3. Stratus needs a smaller fabric offering. Scaling a network
>> infrastructure
>> with such a large risk, fault, change domain brings big concerns. It'd be
>> nice to have a smaller fabric offering to compartmentalize the network a
>> bit.
>>
>>
>> Doug it'd be nice if you could comment on my comments above if you have
>> some
>> insider info :) It'd also be nice if you could take this feedback to the
>> engineering teams for their input. We already have our account team doing
>> so, but another path of contact is always beneficial.
>>
>>
>> On Feb 23, 2011 7:35 PM, "Doug Hanks" <dhanks at juniper.net> wrote:
>> > First phase of Stratus. It's awesome.
>> >
>> > -----Original Message-----
>> > From: juniper-nsp-bounces at puck.nether.net [mailto:
>> juniper-nsp-bounces at puck.nether.net] On Behalf Of Keegan Holley
>> > Sent: Wednesday, February 23, 2011 4:10 PM
>> > To: juniper-nsp
>> > Subject: [j-nsp] Qfabric
>> >
>> > Does anyone know what Qfabric is yet? After the video where Pradeep
>> Sindhu
>> > spends 1:45 talking about how they are going to change the world and
0:45
>> > talking about the technology I gave up trying to cut through the
>> marketing
>> > buffer. It sounds like their implementation or answer to trill with
some
>> of
>> > the virtual chassis stuff you see from the nexus thrown in. Anyone else
>> get
>> > more than that?
>> > _______________________________________________
>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>> >
>> > _______________________________________________
>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
> --
> -- Darren Bolding --
> -- darren at bolding.org --