CF vs. FCoE

Similar Questions

• Intel X 710 Ncdb FCOE support?

  Hello world

  Now I am installing system for my customer with Dell blade, in my server blade have an intel x 710 ncdb map, I can not set up fcoe for her, when I in the bios does not display CF, I can show only ethernet. Can you help me check x 710 ncdb support FCOE.

  I just looked through the technical card for this map, and I can't mention FCOE anywhere.

  http://Dell.to/2awQMY5

• Then a Force10 MXL blade handle no FCoE traffic?

  Hello.  I inherit a M1000e with few blades of the Force10 MXL switch installed.  The chassis has no other 10GBASE-T switches.  Since I have no plans on using FCoE, a Force10 MXL can be used for standard Ethernet (non-FCoE) traffic?  Or do I have to buy another switch?

  Thank you.

  Absolutely, to see the second page of the data sheet. It contains additional information about the available modules, how internal traffic is manipulated and external.

  http://Dell.to/1Q5fUo9

  The manuals are a great place to start. There is that a starter guide to help set up initial, and then a CLI and user guide to help configure additional features.

  http://Dell.to/1IIq8r2

  Let us know if you have any other questions.

• Reference Dell blade Intel X 710 the Ncdb FCOE support

  Now, I'm installing system on dell blade for my client, but when I configure the Intel X 710 Ncdb not to see the CF can show only Ethernet, anyone knows this FCOE support or not? Please help me!.

  Hello

  I show that the network version of the 710 X daughter card supports FCOE. There are versions of expansion card the X 710 that support other protocols and mezzanine, but the NDC version for systems not converged ethernet.

  http://www.Dell.com/learn/us/en/04/business~large-business~en/documents~Intel-x710-dual-or-Quad-Port-10-GbE-BNDC-can.PDF

  Thank you

• Start from the Port of FCoE storage

  If I directly attach an array of NetApp fabric using new storage interconnection FCoE ports, the blades allows SAN boot in this scenario?

  Simon,

  It shouldn't be a problem with that.  Assuming the initators can achieve the goal of direct attach, you should be able to SAN start your blades.  I did not set it up myself, but in theory there should be nothing preventing it.

  Kind regards

  Robert

• Topology of Nexus 5 k / FCoE extending between 2 campus

  Hello

  I need help to answer the following questions related to the interconnection of 2 campuses (top and bottom in the attached diagram) using the ports of FCoE Nexus 5 K:

  Please check the attached topology.

  QUESTIONS RELATING TO THE:

  Multi-hop FCoE:

  ·         The link (10G, SFP +) between pairs of N5k, interconnecting 2 campuses, carry FCoE traffic (Ethernet and FC on the same link):

  ·         Can servers with the adapters of the ANC in the lower Campus, store access the CF in the upper Campus?

  ·         Can the server with HBA FC adapters in the lower Campus, store access the CF in the upper Campus?

  ·         Can expand us the tissue 2fc between the 2 sites using this link of FCoE?

  ·         This link can carry the traffic of Ethernet between 2 LANs (between Upper and Lower campus)

  Thank you.

  It is therefore 3km for FCoE traffic. "but in the case of traffic FC (via FCoE)(, ce que je veux dire si nous avons deles de serveurs avec deles de adaptateurs HBA FC dans le Campus inférieur, accès àle stockage FC dans le Campus supérieur) binding, is it always 3 km limitation? or less?

  -> 3 km, independent how the initiators and targets are connected. (Limitation is for a single jump of FCoe)

  About using the native CF option to extend this link (of course withouth ethernet), to go for an MDS switch? or module of the simple use of the CF to the Nexus 5 k 2?

  -> You can do it directly using CF Module if you run the N5K in switching mode (not in NPV Mode)

  do you have a referral link, mentioning these distances?

  -> Sorry I also had this information via Cisco SE

  Hubert

• Connect FI two directly attach FCoE storage and SAN switches

  Nobody tells me if I can connect FI two directly attach FCoE and SAN storage switches also, as you can see in the diagram of connected network?

  If so, should I FC Switch function Mode? Any concerns should I consider?

  Or the best solution would be appreciated. Thanks in advance.

  The UCS will be in Switch Mode FC, which means that it has a default area.  We cannot make a Zone merge with Brocade because we have no control to set up specific items such as domain and other articles CF IDS that need to be changed when you connect a Cisco FC switch to a Brocade.

  Usually in this situation with a 5 k or a MDS you might be placed in mode of interoperability, which changes the default settings and we will talk to them together - in this case, you can't change these settings, so the only supported configuration is CF Cisco at Cisco.

  See you soon,.

  Greg Scarlett.

• 6200 FCoE in the direction of the North

  I have a quick question that I have not been able to get a definitive right answer to (in literature)-regarding the new 6200 FI and FCoE in the direction of the North...

  Anyway, my question: with the function UP on the 6200 (with UCS 2.0) - can we now do FCoE in the north direction (in this case a nexus 5548UP)? Or do we still need out in separate eth and FC rising?

  I see of the configuration Guide, we can configure ports such as FCoE ports - and options for eth uplinks and CF uplinks are still there too. I was not able to determine if the FCoE port type can be used for uplink.

  Thanks in advance!

  Hi Daniel,.

  * You can always northbound FCoE connectivity of the UCS YEW which in your case, you can not uplink between 62xx FCoE and the 5548UP.

  * You must always have seprate FC rising and uplinks Eth.

  * The feature to have FCoE uplink will be available in a future release (on request at the end of the year).

  * the FCoE ports that you see are to use when you want to direct fix storage of FCoE for FI (limited support model).

  I hope this helps!

  . / Afonso

• FCoE directly connect to VNX5300 with no switch zoning

  I was wondering if anyone has any experience with this unit or a similar facility. I find no decent documentation to help us decide if it is a legitimate set upward for a production of about 16 servers 3 chassis environment. Our expert Cisco has ever put up a UCS environment with a direct connection to the San via FCoE and intuitively is against it, as we do not expect to use a switch to zoning.  Is there a real risk in the present? It will support in the future?

  Hi Henry,.

  If you look at the following document:

  http://www.Cisco.com/en/us/docs/switches/Datacenter/MDS9000/interoperability/matrix/Matrix8.html

  See point number 3, the direct model to support tethering still requires a SDM or N5k upstream to provide this information.

  . / Afonso

• FCoE storage direct connect in 1.4?

  Hi all

  I see the previous discussions that UCSM 1.4 should introduce support for stare directly into a Bay in the 6100 FC storage s. What is FCoE? A storage array with a frontal FCoE card (the new controller Compellent series 40 in particular) will be able to connect directly to the 6100 s?

  See you soon,.

  Simon

  Hi Simon,.

  Yes, in version 1.4, we will be able to connect FCoE targets to the Ethernet ports of the interconnection of fabric FC switch mode (61XX).

  Thank you

  ÖZDEN

• FCOE-basic questions

  My understanding is that the traffic from the blades in the chassis or a rack of series C contains FCOE and Ethernet frames.

  But what about the traffic of a UTA Netapp? Glancing at the NExus switch configuration, it seems that all the ports in use are Ethernet ports. then we configure the FCOE ports on the Ethernet ports for FCOE traffic top. Like this:

  interface vfc7
  link interface Ethernet1/7
  no downtime

  interface vfc8
  link interface Ethernet1/8
  no downtime

  But what about traffic from UTA? It does not contain both types, and then only a single protocol to disappear on the port? Or what is happening here? I think I know a UTA 2 ports map can contain 2-port of FCOE and IP, IE. 4 ports altogether.

  Someone has a document explaining the UTA and FCOE?

  UTA will use FC IP addresses and at the same time that each port.  It's a similar logic to the way the N5K works for the last 5 years.

  Yes, a Nexus 5 K port can understand two FCoE & Ethernet at the same time.  This is the basis for the Consolidation of IO with the nexus platform.  On the side of 5 K, all Ethernet traffic is received and changed accordingly.  For FCoE, packets are received, the package of FCoE is encapsulated off and pure CF payload within the FCoE package framework is then logically received on the VFC interface associated with the physical interface of N5K.  FC traffic is so forward as usual on the switch.

  Robert

• UCS/Nexus and FCoE Question

  Hi all:

  Can we connect a FCoE target directly to an interconnection of fabric or a Nexus 5xxx CWF in NPV mode and not connected to an FC switch for power and tissue services continue to have the initiator see the target and be able to supply storage as a result?

  Thus, the scenario would be the following:

  a server rack with an ANC connected to a Nexus 5xxx CWF in NPV mode

  OR

  a server blade a NON related to interconnection of UCS fabric (which is also a CWF) in VAN mode

  AND

  In the above cases, there is NO CONNECTION between the RTC and an FC switch.

  I will be able to have the ANC (FCoE initiator) see table of Strorage (FCoE target)?

  Thank you

  Hello

  Yes you are right. For the direct-attached storage work, you need the FI in FC switch mode. Your explanation is good and you can not storage direct-attached mode/npv end FC host mode. With FI in npv mode, it can just transfer CF applications to an NPIV switch and cannot process any request CF as FLOGI etc...

  In addition, in the UCS versions under 2.1 you need a SAN switch connected to a FI running in mode switching and storage directly connected to it, which can push the FI database zoning. Thanks to 2.1, you can have storage direct-attached without the need for any SAN switch upstream as we have zoning capabilities in UCS now.

  In short, for all direct-attached storage, you must have FI FC Switching mode.

  -Ganesh

• Storage on FIs FcoE ports

  Hi, we live from Netapp for the FIs storage configured as storage fcoe ports, the FIs are FC switch mode. I see the netapp in FIs flogied so the CF part looks good. I was creating a KEEN on the Netapp side and CE marking on these ports connected to the FIs to use for ethernet/nfs traffic. I need to tag vlan 100 side FI, but it seems that there is no way I can do this. The config on made them is as below.

  FI - A (nxos) # sh run int eth1/23

  interface Ethernet1/23

  F: FcoeStorage description

  PIN border

  switchport mode trunk

  switchport trunk vlan native 4049

  switchport trunk allowed vlan 2000,4049

  no downtime

  FI - A (nxos) # sh run int vfc745

  interface vfc745

  link interface Ethernet1/23

  switchport trunk allowed vsan 2000

  no downtime

  The NXOS running on the FIs is read-only. How to allow to vlan 100 int eth1/23?

  You also need to configure the port as a port of the device.  This will make a "Unified storage" port rather than simply FCoE_Storage port.  When you add the role of 'Port' the device it allows you to select the trunk VLAN you want to allow.  The FI should then tag the traffic accordingly.

  E.g.

  interface Ethernet1/1

  Description AF: UnifiedStorage

  No server pinning sticky

  pinning of pinning-down server drop down link

  No cdp enable

  switchport mode trunk

  switchport trunk vlan native 4049

  switchport trunk allowed vlan 1,240,4048-4049

  no downtime

  Kind regards

  Robert

• Performance issue with multiple jumps of FCoE

  At at - it implemented FCoE multihop on the new firmware 2.1? I moved my UCS lab he and storage performance stagnated. Here's what I have in my lab.

  2 nexus 5500 s - used for LAN and FC switch

  EMC CX4-120 - connected to the 5500 s Nexus 2

  UCS 6120/FEX 2104 - Pre-FCoE to installation has been a port-channel 2 SAN ports in every tissue of the Nexus 5ks.

  6 servers B200 M1

  ESXi 5

  I wired to the top a twinax addition on a fabric of interconnection to 5548 Nexus in FC fabric

  I wired to the top a twinax addition on interconnection fabric Nexus 5548 FC fabric b B

  Configured interfaces such as FCoE uplink in UCS

  Placed the FCoE interfaces in the proper VSAN

  A tissue at the same time, I have disabled port-channel SAN FC to force the vHBAs to connect to the uplink of FCoE. Didn't have any problems with this and vHBAs appeared in the table flogi to the couple of 5ks on the interface correct vfc.

  Reloaded my ESXi (SAN boot) hosts and guests restarted very well using uplink of FCoE to Nexus 5ks.

  When I turned on a virtual machine, it took more than 20 minutes for it to start and he was to the point where it was usable.

  No drops or errors on the FCoE interfaces or the fabric of interconnections vfc and Nexus 5ks.

  As soon as I have reactivated the CF port-channel SAN using 4 GB SFP modules and disable the performance of uplink FCoE was fine again.

  I hope that it is something to do with the older hardware of the generation 1 6100 s and the IOM s 2100 and not a bug.

  I have 2 other servers HP rack mount with CNAs Qlogic FCoE on the VMFS LUNS even without any problem.

  Case ID: 624922297

  The Nexus switches as well as technical support UCSM are attached.

• Storage circuits and dot1q FCoE

  We have live from Netapp for the FIs storage configured as storage fcoe ports, the FIs are in mode switch CF. I see the netapp in FIs flogied so the CF part looks good. On the side of netapp, we have a 10 g interface, e1a, with an IP on this subject.  We have another interface of 10g, e1b, with VLAN attached to it for this interface sends and receives frames dot1q tag.

  Documentation seems to imply that the ip traffic does not at all on an FCOE storage port.  Yet, e1a works very well is not the case of e1b.

  Question 1: My theory is the plain ethernet on e1a works well but the dot1q tagging on e1b, is what actually does work on the FCOE storage port.  Am I wrong?

  Question 2: I think to operate dot1q that I need to change to change the type of port FI FCOE destocking at the port of the unit.  Is it as simple as chaning the port enter through the UCS Manager?  Who takes the FCOE link offline or anything?

  Hi Tod,

  Please make sure you have dot1q on Netapp and necessary FCoE VLAN are marked as native on FI and Netapp.

  Below the docs can serve as a reference.

  Guide to zoning Local UCS

  http://www.Cisco.com/en/us/products/ps10281/products_configuration_example09186a0080c09983.shtml

  Flexpod Deployment Guide (instead of connecting to N5K, we are Netapp directly to UCS FI connection. NetApp configuration would be similar)

  http://www.Cisco.com/en/us/docs/solutions/Enterprise/Data_Center/virtualization/flexpod_deploy.html

  Padma

• FCoE Multihop EMC VNX 5300 to Cisco UCS FI / Series Blade B

  Hi all

  Having a performance problem with FCoE multihop of UCS.

  The presentation is as follows:

  UCS 5108 chassis--> 6248UP FI--> pair of N5k (5548)--> 10gig FCoE EMC VNX 5300 2 x 2 port card

  Everything is functional - I can't ping from tissues to the pwwn EMC n5k cf.

  I can see the paths in vmware on the vhbas everything is in place and active. The VMware is set to round robin and the side EMC ALUA 4.

  I'm at a loss on how to solve it more. The SAN is connected to the fabric with om3 fiber LC + 10 GB SR SFP. UCS has a pair separated from fcoe port fabric channels k 5 down to YEW (the help of twinax cables). The data are separated on its OWN virtual machine. Essentially, I followed the guide from cisco on how to proceed:

  http://www.Cisco.com/en/us/products/ps9670/products_configuration_example09186a0080c13e92.shtml

  The hosts are not boot from SAN for now, they are started from storage USB flash on the blade.

  The show on the 5ks flogi shows all connected, and as I said before, I can see the LUNS on the blades. When howerver I try uplod a file ISO DIS 2.5 GB in size in a data store takes about 2 ½ hours.

  I have the most recent UC 2.1 (2) a firmware installed. The N5ks have NX - OS 6.x. The blades have ESXi 5.1 with the latest drivers enet and installed cisco fnic.

  The default qos for n5k is configured.

  Any ideas would be greatly appreciated!

  -Nick

  Hi Nick,

  Interesting observation. We have an IP hsrp in catalyst 4500 as a router for network management with ip redirects on a reason any. I have disabled ip forwarding as well and currently I do 30K iops with fabric RR double active path and no error in the CPNI on esxi logs.

  I'll have to do additional tests to see the weather, that it is a coincidence or a fix, by activating the ip redirects again. But it looks promising.

  As my e/s load is done with the network management of e/s generator (http://labs.vmware.com/flings/io-analyzer) should have no effect on the routed network FCOE...  He latest even came to my mind to check network Ethernet side.

  Thank you Nick for a great tip.

  concerning

  Mikko