FEX 2232 Question

The FEX 2232's are the 10G FEX ToR devices.
As I understand it, the ports on the 2232 are called  Host ports, which means that the set up necessary is for one CNA per  Host port. So, this means you cannot connect a switch/FIP snooping  bridge between the CNA and the Fex Host port - in other words, the  traffic CANNOT be aggregated. Basically, you need straight-through connections directly between a CNA and the Host port.
Is this true in both an FCoE implementation as well as  a straight Ethernet implementation, where the servers just have 10G  NICs - no CNAs?
Thanks!

Hello,
Since there has been no activity on this post, it is being moved to our data center team for better visibility.
Thank you,
Fabienne

Similar Messages

  • FEX-2232 FCoE Port channel limitation

    Hi all,
    i havea single FEX 2232 single homed to nexus 5020 via port-channel. at the FEX 2232, i connected a server which have 2 X CNA and running two vlans: vlan 200 for ethernet and vlan 300 for FCoE.
    i connected the server to the single fex via port-channel and allowed vlan 200 & 300. at the N5K i bounded single vfc interface to this port-channel.
    when i am issuing the show flogi database i see only single PWWN.
    as i understand, a single vfc interface can only see single PWWN, is this correct ?
    if it does, how can i have my setup running in a way that ethernet traffic  will used port-channel and for fcoe traffic i will see two PWWN ?
    please advise,
    Avi.

    It is not necessary to create another FCoE Vlan if the logins are coming on the same n5k. If there is a requirement for multiple fcoe logins on the same n5k, then it will need to be single link port channels instead of multiple links in the port channel. That way we acquire the ability to bind each physical port via port-channel into a separate vfc. In your case ideally you can have two n5ks with two n2232s single homed to each n5k and the server dual homed with 1 port each connected to two separate 2232s in active-active teaming. That way you can bind the physical interfaces into single virtual port channel on the respective n5ks. at that point, you can separate the san traffic into different vsan/vlan and make sure you dont trunk the fcoe vlan over the vpc peer link.
    Hope this helps, Vinayak.

  • FEX 2232 as uplink for 6248 FI?

    hi,
    have a customer who wants to connect their UCS FI's to their N7K using 2232's ("because a 10G port on the FEX is cheaper").
    anyone want to suggest why this might be a bad (or good) idea?
    thanks,
    R.

    Rob,
    This is not a supported topology and overall a very BAD idea.  The FEX was designed for host connectivity to each port. The device uses a shared buffer system and the queue depths are not at a high enough level to support the type of traffic that would be coming from a multi-host system like UCS. 
    Steve McQuerry
    UCS - Technical Marketing

  • Fex 2000 connecting to nexus 7k/5k

    Hello All,
     We are connecting one fex 2000 to two nexus 5k. I have prepared a simple configuration after consulting the various cisco pages on this.
    On first nexus 5k:-
    int Po100
     des FEX-2232-1
     vpc 100
     switchport mode fex-fabric
     fex associa 100
     no shut
    int eth1/1
     des FEX-2232-1
      switch mode fex-fabr
      fex associ 100
      channe-gr 100
      no shut
    ================
    On second nexus 5k:-
    int Po100
     des FEX-2232-1
     vpc 100
     switchport mode fex-fabric
     fex associa 100
     no shut
    int eth1/1
     des FEX-2232-1
      switch mode fex-fabr
      fex associ 100
      channe-gr 100
      no shut
    Is the above configuration correct?
    The other doubt is; when configuring is it required to create the Po100 first before applying the channel-group command on the physical interfaces?
    Or can the channel-group be directly applied to physical interface ( without the Po being created )?
    Appreciate help on this please. Thanks in advance.

    suthomas1,
    The config is correct. I'm using the same config here so stable and resilient.
    No, its not required to create the po100 before applying the channel-group command on the phy-int.
    Be careful with bpdu in fex access ports.
    Reagards,
    Gus Magno

  • Nexus 56K and FEX 2232TM - connect a router to the FEX?

    Hi I know the recommendation a couple of years back was only to connect servers to FEX ports. Is this still the case? Is anyone connecting devices other than servers to FEX ports? Is there any good reason I could not connect a router to my FEX 2232 TM and form a layer 3 adjacency with an SVI on the parent 5K?
    (going to post this in DC as well as it is relevant to both)
    Any assistance would be great,
    Thanks
    Rays

    Hi Rays,
    The function should be the same for all FEXs regardless of what parent switch they connect to. to.
    if you are referring to this comment:
    You can connect any edge switch that leverages a link redundancy mechanism not dependent on spanning tree such as Cisco FlexLink or vPC
    FelxLink is a different technology that does not use STP, but not every switch platform supports FelxLink. FlexLink is not used very often, as other technologies like VSS, VPC and stacking has emerged.
    HTH

  • Nexus 5548UP FCoE to C series UCS

    Ok here is the scenario
    nexus 5548 switch ---- fex 2232 --- UCS C series (C220)
    snippets of the configuration:
    vlan 1100
    fcoe vsan 1100
    vlan database
    vsan 1100
    fex 100
    description 2232-A
    fcoe
    int ethernet100/1/1
    switchport
    switchport mode trunk
    switchport trunk allowed vlan 10,1100           
    interface vfc100
    bind interface ethernet100/1/1
    switchport trunk allowed vsan 1100
    no shut
    so it is configured above, the vfc interface won't trunk unless I do the following:
    vsan database
    vsan 1100 interface vfc100
    I found this document that describes mapping VSANs to VLANs example configuration (page 8)

    Each fc and/or vfc interface must be member of a VSAN; by default, they belong all initially to VSAN 1.

  • Nexus 7000 with VPC and HSRP Configuration

    Hi Guys,
    I would like to know how to implement HSRP with the following setup:
    There are 2 Nexus 7000 connected with VPC Peer link. Each of the Nexus 7000 has a FEX attached to it.
    The server has two connections going to the FEX on each Nexus 7k (VPC). FEX's are not dual homed as far as I now they are not supported currently.
    R(A)              R(S)
    |                     |
    7K Peer Link 7K
    |                     |
    FEX              FEX
    Server connected to both FEX
    The question is we have two routers connected to each of the Nexus 7k in HSRP (active and one is standby). How can I configure HSRP on the nexus switches and how the traffic will routed from the Standby Nexus switch to Active Nexus switch (I know HSRP works differently here as both of them can forward packets). Will the traffic go to the secondary switch and then via the peer link to the active switch and then to the active router ? (From what I read the packet from end hosts which will go via the peer link will get dropped)
    Has anyone implemented this before ?
    Thanks

    Hi Kuldeep,
    If you intend to put those routers on a non-vpc vlan, you  may create  a new inter-switch trunk between the N7K and allow that non-vpc vlan . However if those will be on a VPC vlan, best to create two links to the N7K pair and create a VPC, otherwise configure those ports as orphan ports which will leverage the VPC peer link .
    HTH
    Jay Ocampo

  • Nexus 5548 with FET-10G problem

    hi,
    i have single 5548 NX-OS 5.0.2N1(1) version connected to single fex 2232 via 4 X FET-10G. on the 5548 it is the first ports, at the 2232 it is at the last 8 ports.
    after configuring appropriate FEX configuration i cannot see any link between them. when i am changing from FET to SFP-10G i get a link.
    what could be the problem ?, do i need specific configuration ?
    thanks,
    Avi.

    Hi,
    Yes, you need to configure the 5548 ports as " switchport mode fex-fabric " before you connect the FET SFP's in the ports.
    The FET is supported on N5k only when connected to the uplink of a FEX, however, the SFP will be non accepted
    if the port on the 5k is not configured with:
    "switchport mode fex-fabric"
    Could you make sure that you have that configuration and that check again?
    HTH,Please rate if it does.
    Cheers,
    -amit singh

  • Active-Active config from N5k to N2k

    On the N5k-B set at priority 105, I cannot see interface 101 of the fex, but can see inter 101 on "priority 110, n5k-A" why is that? when I do a sh vpc brief, adj is up alive. I went ahead and powerdown the N5k-A and now N5k-B has inter 101....so can I assum this is normal behavior?
    vpc domain 200
      role priority 105 while the other N5k is set to 110
      peer-keepalive destination 192.168.1.1
      peer-config-check-bypass
    fex 101
      pinning max-links 1
      description FEX0101
    interface port-channel101
      description ****TO-N2K-ROW-1****
      switchport mode fex-fabric
      untagged cos 0
      fex associate 101
      speed 10000
    interface Ethernet1/7
      description ****TO-N2K-ROW-1****
      switchport mode fex-fabric
      fex associate 101
      channel-group 101
    interface Ethernet1/8
      description ****TO-N2K-ROW-1****
      switchport mode fex-fabric
      fex associate 101
      channel-group 101

    Hi,
    If you are looking at configuring the N2K for so that both uplink are active-active toward the vPC peer devices, then you need to configure the interface port-channel 101 with a common vPC identifier.  For example configure both interface port-channel 101 on the N5Ks to be in say 'vpc 101', without this they are not logically bound.
    If you run a 'show interface fex' or 'show fex' not sure from the top of my head, but it should show the status of the fex in question from the N5K which you are unable to see the interface.
    Regards
    Allan.
    Hope this helps, pls rate helpful posts.

  • Jumbo MTU on Nexus 2232 FEX

    Hi,
    This is related to bug CSCum09831  - jumbo MTU does not work on 2232 FEXes unless it is configured globally. Currently we have several qos groups with jumbo MTU enabled on only one of them and this setup works fine on 2148 FEXes but not on the 2232.
    Now I want to enable Jumbo MTU on all qos groups but I'm not sure that this will solve the problem, any suggestions would be highly appreciated.
    Thanks,
    Adrian

    Hi Adrian,
    I checked the BUG and for 22XX Fex the Jumbo Frame configuration has to be done globally. This is part of the design for these series of Fex.
    So i would suggest to enable Jumbo frames globally and see if the issue gets resolved. Else you can reach out to me i will be more than happy to assist.
    Regards,
    Seemab

  • In depth UCS FEX questions

    With regard to the 2100 FEX module on the UCS....what exactly does it do besides simply act as a mux?
    Does it have any buffers (ingress and egress)?
    Does it have any switching intelligence at all?
    How does it handle the reception of DCB packets (PFC, ETS, etc) from the 6100 or the VIC on the other side? Does it just pass it on?
    What does it do with regard to FIP and FIP snooping?
    Need answers ASAP!
    Thank you!

    Ex,
    The 2100 operate identically to the FEX 2000 series for N5K.  I know you've asked quite a bit of detail on that device already, same applies to the 2104XP IOM for UCS.
    Did you have any other specific questions on the UCS IOM (FEX)?
    Regards,
    Robert

  • VM-FEX questions

    I am new in UCS , so there are some questions
    1) Do I understand correctly that this feature is supported only on UCS bladecenters at the moment?
    2) What is the use for VM-FEX on Nexus 5k without FI modules?  Does anybody plug UCS straight into Nexus 5k without use of FI modules?
    Where do they run UCS manager then?
    Thanks.

    1-UCS C-series support VM-Fex.
    2-The 5k series don't support F1 card.  F1, M1, M2, etc.. are supported on the 7ks.
    UCS manager runs on the 6100 and 6200 series fabric interconnect devices.
    here is more info:
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/layer2/513_n1_1/b_Cisco_n5k_layer2_config_gd_rel_513_N1_1/b_Cisco_n5k_layer2_config_gd_rel_513_N1_1_chapter_010101.html#concept_6A0DA0AE4323414E8FE667CAB20C1234
    UCS manager:
    http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-b-series-blade-servers/data_sheet_c78-520522.html
    HTH

  • Question re. behaviour of single homed FEX with vPC

    Hi Folks,
    I have been looking at configuring Nexus 5Ks with FEX modules.  Referring to the Cisco documentation;
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/layer2/513_n1_1/b_Cisco_n5k_layer2_config_gd_rel_513_N1_1_chapter_01001.html
    In figure 3. showing a single homed FEX with vPC topology, I'm curious what happens if one of the 5Ks fail.  For example if the 5K on the left hand side of the diagram fails do the ports on the attached FEX that the server is attached to drop? If not I would assume that the server has no way of knowing that there is no longer a valid path through those links and will continue to use them?
    Many thanks in advance,
    Shane.

    Hello Shane.
    Depending of type of the failureboth n5k can tace corrective actions and end host will always know that one of the port-channel members is down.
    For example if one 5k will crash or will be reloaded - all connected fexes alre will go offline. FEX are not standalone switches and cannot work without "master" switch.
    Also links which will go from fex to the end-host will be in vpc mode which means that all vpc redundancy features/advantages will be present.
    HTH,
    Alex 

  • Odd power supply fault callhome emails on Cisco 2232 FEXs?

    We recently enabled smtp callhome for our ucs pod a few days ago. Since then, we've received more than a dozen email bursts about power supply failures in each of the four Cisco Nexus 2232TP FEXs in our pod. In each case, we get a "Recovered" email within a minute or two, and we're not seeing power supply failure emails for any other devices within the UCS pod.
    Here's a sample email burst from this morning, showing the subject lines within my email inbox:
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:01:27 GMT-00:00 Recovered : Power supply 2 in fex 6 power: error
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 operability: inoperable
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 power: error
    System Notification from atl01-ucsf01a-A - environment:major - 2012-10-23 06:00:58 GMT-00:00 Power supply 2 in fex 6 power: error
    If we were seeing this from just one fex, I'd suspect a hardware issue. If any of the other UCS devices (rackmount/blade servers, fabric interconnects, etc) reported similar issues, I'd suspect a power feed problem within the DC.
    But this has me baffled. If it helps, the UCS pod is running firmware 2.0.3c
    Cheers,
    Paul

    Thanks Paul,
    It is known ( cosmetic ) issue with power supply model. 
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtz84683
    The above is resolved in recent version of Nexus 5K switch software. New defect to port the fix to UCSM has been submitted today
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCuc87547
    It will take a while to get published on web site.
    Even though they are cosmetic, I would suggest you open a TAC SR with UCSM, FEX tech support and above bug IDs so that we can track the resolution.
    HTH
    Padma

  • 6200 Fabric Interconnect licensing with 2232 FEX

    I have searched and searched but can't find the document to answer this.  I know that every port on a 6248 or 6296 needs to be licensed to work whether it's Ethernet, FC, or FCoE. 
    We know it's supported and we want to connect a pair of 2232PP FEX up to our 6200 FI for C-series server connectivity.
    When connecting a 2232PP FEX up to a 6200 FI, there are a potential of 8 uplink ports from the FEX to the FI.  Do all 8 of those ports need to be licensed to work?  Do any of the new 32 ports that show up once the FEX is connected need to be licensed as well?
    Thanks!
    Chris

    Hello Chris,
    The ports on FI connecting to FEX ( Server ports ) needs to have licenses. The ports on FEX connecting to hosts ( rack servers - backplane ports  ) is not counted for licenses.
    You can use all of those back plane ports without worrying about licenses.
    HTH
    Padma

Maybe you are looking for