Actually, FCoE is Single-Hop by standart. Creating extenders from
Cisco-side is a trick to go from this limitation.
Also if you already have non-Cisco FC Fabric, using Cisco Extenders should
be done with care.

On Fri, Dec 16, 2011 at 2:41 AM, Asbjorn Hojmark - Lists
<li...@hojmark.org>wrote:

> We have customers running the Nexus B22HP (Cisco/HP FEX) and it works
> pretty
> well.
>
> Flex-Whatever sucks. Bowling balls through straws. It's a switch, but not a
> switch. It doesn't do QoS. (Flex-NIC bandwidth-limitations work only in one
> direction). It doesn't do multi-hop FCoE (no FCoE out of the rack), and
> thus
> requires more FC ports = more expensive, it is limited in number of VLANs.
> Management sucks. Server admins configure networking.
>
> From my experience I'd say
>
> 1st prio: B22HP -> N5500 (limited market exposure, but cool tech)
> 2nd prio: Pass-Through -> N2232 -> N5500
> ...
> 5th prio: CBS-3120X -> N5500
> ...
> 8th prio: barbed wired
> ...
> Cth prio: VC FlexFabric -> N5500
> ...
> Fth prio: VC Flex-10 -> N5500
>
> Seriously.
>
> -A
>
> -----Original Message-----
> From: cisco-nsp-boun...@puck.nether.net
> [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Pablo Espinosa
> Sent: Tuesday, December 13, 2011 11:10 PM
> To: cisco-nsp
> Subject: Re: [c-nsp] Cisco Nexus and HP Flexfabric
>
> Actually, I mis-spoke on the HP Flexfabric question.
>
> I've been asked to consider the HP Flexfabric product OR the
> integrated Cisco Nexus 2K within an HP Blade server....If anyone has
> deployed either solution, I would love some feedback
>
> thanks
> p-
>
>  _______________________________________________
> cisco-nsp mailing list  cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to