Re: [c-nsp] Cisco Nexus and HP Flexfabric
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.orgwrote: 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 serverIf 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Actually, FCoE is Single-Hop by standart. Nonsense, the standards have been done for years. What constitutes a FC hop is an ISL (FCF VE_Port to FCF VE_Port)... and yes that is standardized for FCoE. See FC-BB-5. Also if you already have non-Cisco FC Fabric, using Cisco Extenders should be done with care. Sure, every network design should be done with care. Now please go spread your FUD somewhere else. -A ___ 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Any experience on the operations side of things for the B22HP route? More specifically, feedback on how TAC (HP and Cisco) would look, day to day provisioning (risk to reloading an B22HP to the rest of the HP Blade?)...etc Support (functionality, troubleshooting) for the fabric extender is through Cisco TAC (via the N5K parent switch). If you need an RMA, that's via HP (as the B22HP is an HP product). If you reload the B22HP (or upgrade it from the parent N5K), the Servers of cause lose connectivity on that fabric. Of cause, if you run both types of traffic on the same network, it hurts to lose that network... But few applications actually benefit from being able to reach the storage when the network is down or vice versa. Plus, you can build the level of redundancy that you want. I think the biggest change may be software upgrades: LAN people often try to keep relatively 'current' with software, while SAN people may be used to installing something and then 'never' touch the software version again. -A ___ 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Do you know what the limit to vlans on flexfabric is? It depends on the software version, which may be why you see different values different places. The maximum in a FlexFabric module is 320 VLANs with VC 3.18. There are other limits as to the number of VLANs in the VC domain, but that is an it depends value, based on the design. -A ___ 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Well, If you carefully read FC-BB-5 ver. 1.03, you may see that each Enode should be connected to Fibre Channel Forwarder. That is what I mean. Only FIP version 1 should remove this limitation. On Wed, Dec 28, 2011 at 3:03 PM, Asbjorn Hojmark - Lists li...@hojmark.orgwrote: Do you know what the limit to vlans on flexfabric is? It depends on the software version, which may be why you see different values different places. The maximum in a FlexFabric module is 320 VLANs with VC 3.18. There are other limits as to the number of VLANs in the VC domain, but that is an it depends value, based on the design. -A ___ 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
On Wed, 28 Dec 2011 15:25:10 +0200, you wrote: Well, If you carefully read FC-BB-5 ver. 1.03, you may see that each Enode should be connected to Fibre Channel Forwarder. That is what I mean. Yeah, that's exactly what you get with multi-hop FCoE from Cisco (N5K - N5K or N5K - N7K). So yes, multi-hop FCoE is standardized. You are correct, of cause, that you can't connect a N2K (or B22HP) to 'any switch' or 'any SAN'. You have to connect it to a N5K. But that's like complaining that the standards aren't done when you can't use a Cisco MDS line card in a Brocade switch. (The N2K is, in effect, a line card of the N5K). And that has nothing to do with multi-hop FCoE. My point was this: If you use FlexFabric, you get FCoE from the server to the FlexFabric, but you have to run multiple cables (both Ethernet and FC) from the chassis to the LAN and the SAN. You basically only save the HBA. With N2K (or B22HP), you can use a single cable from the chassis (carrying both LAN and SAN) and save both HBA, cables, and FC ports. -A ___ 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Thanks Asbjorn Any experience on the operations side of things for the B22HP route? More specifically, feedback on how TAC (HP and Cisco) would look, day to day provisioning (risk to reloading an B22HP to the rest of the HP Blade?)...etc thanks p- On Thu, Dec 15, 2011 at 4:41 PM, 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 serverIf 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
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 serverIf 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/
Re: [c-nsp] Cisco Nexus and HP Flexfabric
Do you know what the limit to vlans on flexfabric is? As we seem to be running into an issues with Vlan limits right now and depending on which person/website I ask depends on the limit. -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Asbjorn Hojmark - Lists Sent: Friday, 16 December 2011 10:42 AM To: 'Pablo Espinosa' Cc: 'cisco-nsp' Subject: Re: [c-nsp] Cisco Nexus and HP Flexfabric 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 serverIf 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/ Stuck for gift ideas? Check out racq.com/shop where you are sure to find something for everyone. Please Note: If you are not the intended recipient, please delete this email as its use is prohibited. RACQ does not warrant or represent that this email is free from viruses or defects. If you do not wish to receive any further commercial electronic messages from RACQ please e-mail unsubscr...@racq.com.au or contact RACQ on 13 19 05. Please Note: If you are not the intended recipient, please delete this email as its use is prohibited. RACQ does not warrant or represent that this email is free from viruses or defects. If you do not wish to receive any further commercial electronic messages from RACQ please e-mail unsubscr...@racq.com.au or contact RACQ on 13 19 05. ___ 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/
[c-nsp] Cisco Nexus and HP Flexfabric
Hey all - Looking for some un-biased feedback; and I will get it here. :) As an alternative to a ToR design within our data center, I've been asked to consider the HP Flexfabric product with an integrated Cisco Nexus 2K built into it. I'm not a fan of converged infrastructure as this, but the reduction in cable management and cost is attractive. However, I'd love to know if anyone has deployed such a solution and if so, how has it impacted (good or bad) your day to day operations and provisioning? Architecturally, it makes sense to consider convergence when the opportunity arises, but I'm not 100% sold on this solution. cheers pablo ___ 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/
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 serverIf anyone has deployed either solution, I would love some feedback thanks p- On Tue, Dec 13, 2011 at 2:00 PM, Pablo Espinosa espinosa.pa...@gmail.com wrote: Hey all - Looking for some un-biased feedback; and I will get it here. :) As an alternative to a ToR design within our data center, I've been asked to consider the HP Flexfabric product with an integrated Cisco Nexus 2K built into it. I'm not a fan of converged infrastructure as this, but the reduction in cable management and cost is attractive. However, I'd love to know if anyone has deployed such a solution and if so, how has it impacted (good or bad) your day to day operations and provisioning? Architecturally, it makes sense to consider convergence when the opportunity arises, but I'm not 100% sold on this solution. cheers pablo ___ 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/
