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

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 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

  • Nexus 2232 TM uplink ports are they only for uplink use?

    We have upgraded our N5K to support the new 2232TM, but now we face the issue that the 8 SFP+ ports are not visible in our config:
    Nexus5010_1# sh  fex 103 det
    FEX: 103 Description: 2KSRV02   state: Online
      FEX version: 5.0(3)N2(2a) [Switch version: 5.0(3)N2(2a)]
      FEX Interim version: 5.0(3)N2(2a)
      Switch Interim version: 5.0(3)N2(2a)
      Extender Model: N2K-C2232TM-10GE,  Extender Serial: FOC15262P7Q
      Part No: 73-13626-03
      Card Id: 164, Mac Addr: 30:e4:db:66:12:02, Num Macs: 64
      Module Sw Gen: 21  [Switch Sw Gen: 21]
      post level: complete
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth1/9
      Fabric interface state:
        Po103 - Interface Up. State: Active
        Eth1/9 - Interface Up. State: Active
        Eth1/10 - Interface Up. State: Active
      Fex Port        State  Fabric Port
           Eth103/1/1  Down       Po103
           Eth103/1/2  Down       Po103
           Eth103/1/3  Down       Po103
           Eth103/1/4  Down       Po103
           Eth103/1/5  Down       Po103
           Eth103/1/6  Down       Po103
           Eth103/1/7  Down       Po103
           Eth103/1/8  Down       Po103
           Eth103/1/9  Down       Po103
          Eth103/1/10  Down       Po103
          Eth103/1/11  Down       Po103
          Eth103/1/12  Down       Po103
          Eth103/1/13  Down       Po103
          Eth103/1/14  Down       Po103
          Eth103/1/15  Down       Po103
          Eth103/1/16  Down       Po103
          Eth103/1/17  Down       Po103
          Eth103/1/18  Down       Po103
          Eth103/1/19  Down       Po103
          Eth103/1/20  Down       Po103
          Eth103/1/21  Down       Po103
          Eth103/1/22  Down       Po103
          Eth103/1/23  Down       Po103
          Eth103/1/24  Down       Po103
          Eth103/1/25  Down       Po103
          Eth103/1/26  Down       Po103
          Eth103/1/27  Down       Po103
          Eth103/1/28  Down       Po103
          Eth103/1/29  Down       Po103
          Eth103/1/30  Down       Po103
          Eth103/1/31  Down       Po103
          Eth103/1/32  Down       Po103
    They are not visible: neither with the "show fex" neither with the "show int status", we cannot configure them....?
    Do you think it's possible to access these ports by another way and configure them to allow some hosts to connect on it or is their purpose exclusively UPLINK?
    best regards,
    Eric Gillis

    Do you mean the Fabric interfaces? If yes, you cannot use those for any host connectivities.
    HTH,
    jerry

  • Configuration Guide for 6248 and 5548 and VNX 5500

    Hi,
    Need help here to configure the FCoE Uplink + Ethernet Uplink in Port channel
    Following is the connectivity details from 6248, 5548 and VNX5500.
    I have configured Port Channel in following way on Both Fabric Interconnect
    After Configuring above things I am getting following Faults on Servers
    For NetApp3240 ENM source pinning failed, I have allowed VLAN ID 21 in Uplink manager then too this Link state is  not showing UP and Same thing go for both FC_vHBA
    Kinldy help me to configure the setup
    -Amit

    Below is the ouput for two commands "show run int port-channel membership" and "sh int port-channel "
    ===========================================================================
    primary# sh run int po2 membership
    !Command: show running-config interface port-channel2 membership
    !Time: Wed Feb 25 07:55:31 2009
    version 5.2(1)N1(1b)
    interface port-channel2
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      spanning-tree port type edge
      spanning-tree bpdufilter enable
    interface Ethernet1/3
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    interface Ethernet1/4
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    interface Ethernet1/5
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    ===========================================================================
    primary# sh run int po3 membership
    !Command: show running-config interface port-channel3 membership
    !Time: Wed Feb 25 07:57:14 2009
    version 5.2(1)N1(1b)
    interface port-channel3
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      spanning-tree port type edge
      spanning-tree bpdufilter enable
    interface Ethernet1/8
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    interface Ethernet1/9
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    interface Ethernet1/10
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    ===========================================================================
    primary# sh int po2
    port-channel2 is up
      Hardware: Port-Channel, address: 002a.6a0a.4caa (bia 002a.6a0a.4caa)
      Description: ***Link to FI-A in R17***
      MTU 1500 bytes, BW 30000000 Kbit, DLY 10 usec
      reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
      Input flow-control is off, output flow-control is off
      Switchport monitor is off
      EtherType is 0x8100
      Members in this channel: Eth1/3, Eth1/4, Eth1/5
      Last clearing of "show interface" counters never
      30 seconds input rate 504 bits/sec, 0 packets/sec
      30 seconds output rate 2256 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 456 bps, 0 pps; output rate 656 bps, 0 pps
      RX
        22208045 unicast packets  747374 multicast packets  27634234 broadcast packets
        50589653 input packets  49083144072 bytes
        21411174 jumbo packets  0 storm suppression bytes
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        2801196 unicast packets  353162904 multicast packets  549464 broadcast packets
        356513564 output packets  25978572978 bytes
        101325 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble 0 output discard
        0 Tx pause
      35 interface resets
    ===========================================================================
    primary# sh int po3
    port-channel3 is up
      Hardware: Port-Channel, address: 002a.6a0a.4caf (bia 002a.6a0a.4caf)
      Description: ***Link to FI-B in R18***
      MTU 1500 bytes, BW 30000000 Kbit, DLY 10 usec
      reliability 48052/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
      Input flow-control is off, output flow-control is off
      Switchport monitor is off
      EtherType is 0x8100
      Members in this channel: Eth1/8, Eth1/9, Eth1/10
      Last clearing of "show interface" counters never
      30 seconds input rate 104 bits/sec, 0 packets/sec
      30 seconds output rate 1704 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 448 bps, 0 pps; output rate 1.08 Kbps, 0 pps
      RX
        9070 unicast packets  288523 multicast packets  143322 broadcast packets
        440915 input packets  72677230 bytes
        7 jumbo packets  0 storm suppression bytes
        0 runts  0 giants  36 CRC  0 no buffer
        2161727821137838086 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        62914 unicast packets  74425404 multicast packets  14434365 broadcast packets
        88922683 output packets  7182753461 bytes
        14 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble 0 output discard
        0 Tx pause
      17 interface resets
    ===========================================================================
    secondary# sh run int po2 mem
    !Command: show running-config interface port-channel2 membership
    !Time: Wed Feb 25 07:56:41 2009
    version 5.2(1)N1(1b)
    interface port-channel2
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      spanning-tree port type edge
      spanning-tree bpdufilter enable
    interface Ethernet1/8
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    interface Ethernet1/9
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    interface Ethernet1/10
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 2 mode active
    ===========================================================================
    secondary# sh run int po3 mem
    !Command: show running-config interface port-channel3 membership
    !Time: Wed Feb 25 07:58:30 2009
    version 5.2(1)N1(1b)
    interface port-channel3
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      spanning-tree port type edge
      spanning-tree bpdufilter enable
    interface Ethernet1/3
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    interface Ethernet1/4
      description ***Link to FI-A in R17***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    interface Ethernet1/5
      description ***Link to FI-B in R18***
      switchport mode trunk
      switchport trunk allowed vlan 12-13,21,101-600
      channel-group 3 mode active
    ===========================================================================
    secondary# sh int po2
    port-channel2 is up
      Hardware: Port-Channel, address: 002a.6a0a.4d6f (bia 002a.6a0a.4d6f)
      Description: ***Link to FI-A in R17***
      MTU 1500 bytes, BW 30000000 Kbit, DLY 10 usec
      reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
      Input flow-control is off, output flow-control is off
      Switchport monitor is off
      EtherType is 0x8100
      Members in this channel: Eth1/8, Eth1/9, Eth1/10
      Last clearing of "show interface" counters never
      30 seconds input rate 1752 bits/sec, 0 packets/sec
      30 seconds output rate 1016 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 832 bps, 0 pps; output rate 496 bps, 0 pps
      RX
        76009142 unicast packets  544440 multicast packets  228999 broadcast packets
        76782581 input packets  146179423660 bytes
        68566412 jumbo packets  0 storm suppression bytes
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        192711593 unicast packets  154928956 multicast packets  31420967 broadcast packets
        379061516 output packets  385914168860 bytes
        179761364 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble 0 output discard
        0 Tx pause
      24 interface resets
    ===========================================================================
    secondary# sh int po3
    port-channel3 is up
      Hardware: Port-Channel, address: 002a.6a0a.4d6a (bia 002a.6a0a.4d6a)
      Description: ***Link to FI-B in R18***
      MTU 1500 bytes, BW 30000000 Kbit, DLY 10 usec
      reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is trunk
      full-duplex, 10 Gb/s
      Input flow-control is off, output flow-control is off
      Switchport monitor is off
      EtherType is 0x8100
      Members in this channel: Eth1/3, Eth1/4, Eth1/5
      Last clearing of "show interface" counters never
      30 seconds input rate 456 bits/sec, 0 packets/sec
      30 seconds output rate 1784 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 456 bps, 0 pps; output rate 912 bps, 0 pps
      RX
        75986748 unicast packets  490267 multicast packets  124569 broadcast packets
        76601584 input packets  146159548726 bytes
        68566413 jumbo packets  0 storm suppression bytes
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        192585042 unicast packets  190939131 multicast packets  13399201 broadcast packets
        396923374 output packets  386206869311 bytes
        179761514 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble 0 output discard
        0 Tx pause
      24 interface resets
    ===========================================================================
    We have removed vPC configuration as we are facing same problem as i said in my previous post
    id     Port        Status Consistency Reason                     Active vlans
    2      Po2         up     failed      vpc port channel           -
                                          mis-config due to vpc
                                          links in the 2 switches
                                          connected to different
                                          partners
    Do let me know if anything else is required from my end
    -amit

  • 10Gb module uplink for 3750x switch issues

    Hi All,
    We build a network consists of 3 x 48 ports 3750X switches and this network is uplink to the Core with 10GB uplink.
    We bought 3 x 48 port 3750x with 10GB modules  plus enough10GB SFPs.
    The problem is for the 10GB module , we can only have 2 x 10GB SFP connections or 4 x 1GB sfp uplinks.
    How do we get around with the 3rd switch which need an extra  10GB uplink to the core ?
    we do not want to buy another 3750x switch and stack to the third switch to give it more 10GB ports.
    Any solution is much appreciated.
    Thanks
    PLe

    Hi,
    Can u shar the BOM which includes 10Gig module part  code and a proposed digram which u wanted to deploy.
    Vivek

  • Uplink Trunking - 6248

    So getting my head around enabling FC Uplink Trunking all this means is all VSANs will run over any configured FC Port-Channels. Correct? Of course running in End-Host Mode will disable all VSANs with the IDs between 3840-4078.
    I am planning to FC Port-Channel 4 links from the Fabric Interconnect to the upstream MDS 9148's and all VSANs will traverse this FC Port-Channel.
    Thanks

    HX,
    These are two different features.  FC trunking is one, FC Port Channeling (ie. SAN Port Channeling) is another.  You can definately use both together or separately.
    FC Port Channeling  - aggregates FC uplinks
    FC Trunking - carries multiple VSAN on FC Uplinks (or Port Channels)
    FC trunking is a Cisco specific concept.
    Robert

  • Uplink-ID 0 in Nexus 5500 with FEX 2248.

    Hi all,
    I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
    On the log of the first Nexus 5500 I see this:
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    On the log of the second nexus 5500, I see this:
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
    Thanks in advace for your assistance.

    Hi Sonu,
    I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
    sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
    Did you find the fix7workaround of this problem ?
    Regards,
    Umair

  • Fcoe for ethernet AND san

    I'm having a bit of a brain fart....
    I see that you can create an "unified" uplink from the 6248s to an upstream Nexus 5k.  Can I use this single uplink for both VSAN and VLAN traffic, or si the best practice to separare them into an Ethernet uplink and a FCOE San uplink?
    Thanks in advance.

    I'm not sure of any immediate disadvantages.  A lot of design related inputs to separate LAN and SAN are related to pacing the integrating of the two networks. 
    If your already running FCoE and your not migrating from a pure LAN and Fibre channel environment to FCoE - then I'd run both on a unified link.
    Please rate helpful posts.

  • Uplink failover scenarios - The correct behavior

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    Hello Dears,
    I’m somehow confused about the failover scenarios related to the uplinks and the Fabric Interconnect (FI) switches, as we have a lot of failover points either in the vNIC , FEX , FI or uplinks.
    I have some questions and I hope that someone can clear this confusion:
    A-     Fabric Interconnect failover
    1-      As I understand when I create a vNIC , it can be configured to use FI failover , which means if FI A is down , or the uplink from the FEX to the FI is down , so using the same vNIC it will failover to the other FI via the second FEX ( is that correct , and is that the first stage of the failover ?).
    2-      This vNIC will be seen by the OS as 1 NIC and it will not feel or detect anything about the failover done , is that correct ?
    3-      Assume that I have 2 vNICs for the same server (metal blade with no ESX or vmware), and I have configured 2 vNICs to work as team (by the OS), does that mean that if primary FI or FEX is down , so using the vNIC1 it will failover to the 2nd FI, and for any reason the 2nd vNIC is down (for example if uplink is down), so it will go to the 2nd vNIC using the teaming ?
    B-      FEX failover
    1-      As I understand the blade server uses the uplink from the FEX to the FI based on their location in the chassis, so what if this link is down, does that mean FI failover will trigger, or it will be assigned to another uplink ( from the FEX to the FI)
    C-      Fabric Interconnect Uplink failover
    1-      Using static pin LAN group, the vNIC is associated with an uplink, what is the action if this uplink is down ? will the vNIC:
    a.       Brought down , as per the Network Control policy applied , and in this case the OS will go for the second vNIC
    b.      FI failover to the second FI , the OS will not detect anything.
    c.       The FI A will re-pin the vNIC to another uplink on the same FI with no failover
    I found all theses 3 scenarios in a different documents and posts, I did not have the chance it to test it yet, so it will be great if anyone tested it and can explain.
    Finally I need to know if the correct scenarios from the above will be applied to the vHBA or it has another methodology.
    Thanks in advance for your support.
    Moamen

    Moamen
    A few things about Fabric Failover (FF)  to keep in mind before I try to address your questions.
    FF is only supported on the M71KR and the M81KR.
    FF is only applicable/supported in End Host Mode of Operation and applies only to ethernet traffic. For FC traffic one has to use multipathing software (the way FC failover has worked always). In End Host mode, anything along the path (adapter port, FEX-IOM link, uplinks) fails and FF is initiated for ethernet traffic *by the adapter*.
    FF is an event which is triggered by vNIC down i.e a vNIC is triggered down and the adapter initiates the failover i.e it sends a message to the other fabric to activate the backup veth (switchport) and the FI sends our gARPs for the MAC as part of it. As it is adapter driven, this is why FF is only available on a few adapters i.e for now the firmware for which is done by Cisco.
    For the M71KR (menlo's) the firmware on the Menlo chip is made by Cisco. The Oplin and FC parts of the card, and Intel/Emulex/Qlogic control that.
    The M81KR is made by Cisco exclusively for UCS and hence the firmware on that is done by us.
    Now to your questions -
    >1-      As I understand when I create a vNIC , it can be configured to use FI failover , which means if FI A is down , or the uplink from the FEX to the >FI is down , so using the same vNIC it will failover to the other FI via the second FEX ( is that correct , and is that the first stage of the failover ?).
    Yes
    > 2-      This vNIC will be seen by the OS as 1 NIC and it will not feel or detect anything about the failover done , is that correct ?
    Yes
    >3-      Assume that I have 2 vNICs for the same server (metal blade with no ESX or vmware), and I have configured 2 vNICs to work as team (by the >OS), does that mean that if primary FI or FEX is down , so using the vNIC1 it will failover to the 2nd FI, and for any reason the 2nd vNIC is down (for >example if uplink is down), so it will go to the 2nd vNIC using the teaming ?
    Instead of FF vNICs you can use NIC teaming. You bond the two vNICs which created a bond interface and you specify an IP on it.
    With NIC teaming you will not have the vNICs (in the Service Profile) as FF. So the FF will not kick in and the vNIC will be down for the teaming software to see on a fabric failure etc for the teaming driver to come into effect.
    > B-      FEX failover
    > 1-      As I understand the blade server uses the uplink from the FEX to the FI based on their location in the chassis, so what if this link is down, > >does that mean FI failover will trigger, or it will be assigned to another uplink ( from the FEX to the FI)
    Yes, we use static pinning between the adapters and the IOM uplinks which depends on the number of links.
    For example, if you have 2 links between IOM-FI.
    Link 1 - Blades 1,3,5,7
    Link 2 - Blades 2,4,6,8
    If Link 1 fails, Blade 1,3,5,7 move to the other IOM.
    i.e it will not failover to the other links on the same IOM-FI i.e it is no a port-channel.
    The vNIC down event will be triggered. If FF is initiated depends on the setting (above explanation).
    > C-      Fabric Interconnect Uplink failover
    > 1-      Using static pin LAN group, the vNIC is associated with an uplink, what is the action if this uplink is down ? will the vNIC:
    > a.       Brought down , as per the Network Control policy applied , and in this case the OS will go for the second vNIC
    If you are using static pin group, Yes.
    If you are not using static pin groups, the same FI will map it to another available uplink.
    Why? Because by defining static pinning you are purposely defining the uplink/subscription ratio etc and you don't want that vNIC to go to any other uplink. Both fabrics are active at any given time.
    > b.      FI failover to the second FI , the OS will not detect anything.
    Yes.
    > c.       The FI A will re-pin the vNIC to another uplink on the same FI with no failover
    For dynamic pinning yes. For static pinning NO as above.
    >I found all theses 3 scenarios in a different documents and posts, I did not have the chance it to test it yet, so it will be great if anyone tested it and >can explain.
    I would still highly recommend testing it. Maybe its me but I don't believe anything till I have tried it.
    > Finally I need to know if the correct scenarios from the above will be applied to the vHBA or it has another methodology.
    Multipathing driver as I mentioned before.
    FF *only* applies to ethernet.
    Thanks
    --Manish

  • 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

  • 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

  • Can't define PVE Uplink with srw224g4

    Hi,
    I tried to  setup sample usage of PVE with Linksys  SRW224G4 withot success. I successfully set PVE g1 for ports 1 to 5 but I can't setup uplink port for this PVE group. I can't find place where can define PVE mapping an PVE upllink in web view. When I googled about this  I find that in "Port config" section in firmware version befor 1.2.2 have "pve mapping", but there is not such link. How can i define Uplink for particular PVE group in firmware version before 1.2.2?
    Thanks in advance

    Huh,
    Even though i am using older software here, it seems straight forward.
    Can I humbly suggest, that you contact the SBSC  to get some phone help, if this switch is still under phone support warranty.
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    regards Dave

  • Max users for a AIR-LAP1142-A-K9

    I work at a small University where are are moving from a hitspot infrastructure (just provide wireless access)  to dense user support model in order to use wireless during classrrom instruction.  It have a request to provide wirless coverage in a classroom for up to 30 users.  I have installed a Lap-1142 in the hall just overisde of the classroom last semister which provided wireless access for about 12 students.  The class enrollment has grown and now will need to support up to 30 users.  I just install a C3560G-POE to provide 1GB uplink for the switch. The instructed stated she will require students to download pdf files and some streaming media during class and I was asked if the wireless will be able to support this requirement.
      I am not sure how many concurrent users a LAP-1142 can support and if it can can it support streaming media for 30 users.  How would I go about testing this senairio? How can one test AP throughput?  How do I ensure it will work during class with having to place another AP within the classroom?
    Thank you for your help.
    Mike

    Where could I located Cisco's 25 user limit recommendation
    If you have an autonomous AP, then there's no need to worry.  It's just a rule-of-thumb.  If it's controller-based then it's:
    Wireless > 802.11a/n (or 802.11b/g/n) > General and look at "Clients (1 to 75)". 

  • How to pre-provisioned N2K FEX(N2K-C2248TP-E-1GE) with Nexus 9372

    HI Team,
    Kindly assist for pre-provisioning the N2K(N2K-C2248TP-E-1GE) FEX with Nexus 9372.
    Tried using the below commands just similar to/with Nexus 5K, but no luck with Nexus 9372
    In case of 9K,
    Nexus 9372# sh fex
      FEX         FEX           FEX                       FEX              
    Number    Description      State            Model            Serial    
    103  Row C_Rack11_N2248TP                Online   N2K-C2248TP-E-1GE  
    105  Row D_Rack10_N2248TP                Online   N2K-C2248TP-E-1GE 
    Nexus 9372(config)# slot ?
    *** No matching command found in current mode, matching in (exec) mode ***
      <1>  The slot number (aka module number)
    Nexus 9372# slot ?
      <1>  The slot number (aka module number)
    In case of 5K,
    Nexus 5548(config)# slot ?
      <1-199>  Enter a slot number

    Hello GN
    2248/2224 FEX does auto-negotiate speed to either 100Mbps or 1000Mbps depending on what the far end is advertising. For duplex, the FEX only supports full duplex.
    So if you hard code speed to 100 on the FEX and auto-negotiating on the far end, the far end autonegotiating device would do 100/half.
    24-10-4948-1#sh run int gigabitEthernet 1/1
    Building configuration...
    Current configuration : 193 bytes
    interface GigabitEthernet1/1
    description ***used by prkrishn***
    no switchport
    ip address 1.1.1.100 255.255.255.0
    logging event link-status
    end
    24-10-4948-1#sh int gigabitEthernet 1/1 status
    Port      Name               Status       Vlan       Duplex  Speed Type
    Gi1/1     ***used by prkrish connected    routed     a-half  a-100 10/100/1000-TX
    24-10-4948-1#
    GC-TAC-EFT-5596-A(config-if)# sh run int eth109/1/1
    !Command: show running-config interface Ethernet109/1/1
    !Time: Wed May 23 08:41:15 2012
    version 5.2(1)N1(1)
    interface Ethernet109/1/1
      spanning-tree bpdufilter enable
      speed 100
    GC-TAC-EFT-5596-A(config-if)#
    GC-TAC-EFT-5596-A(config-if)# sh int ethernet 109/1/1 counters errors
    Port          Align-Err    FCS-Err   Xmit-Err    Rcv-Err  UnderSize OutDiscards
    Eth109/1/1         4          1          0          5          0           0
    Port         Single-Col  Multi-Col   Late-Col  Exces-Col  Carri-Sen       Runts
    Eth109/1/1         0          0          0          0          0           4
    Port          Giants SQETest-Err Deferred-Tx IntMacTx-Er IntMacRx-Er Symbol-Err
    Eth109/1/1         0          --           0           0           0          0
    TDR is not supported on any interface on the Nexus 5000 and the message you see when you try it for FEX interfaces is misleading for sure.

Maybe you are looking for

  • Backing up iPhoto Library on external hard drive through Time Machine

    Hi - I was advised by the folks at the Genius Bar to move my iPhoto Library to an external hard drive (drive 1), and then buy a separate 1TB external hard drive (drive 2) for all of my Time Machine backups. They said I could back up the Library in dr

  • Xml editor code

    hi all,, i am doing a project of devolping an xml editor.could anyone provide me the code for it. very urgent plzzz....

  • Help With LightRoom Aspect Ratio Settings

    I have created some custom Aspect Ratio settings to the crop tool but I now want to delete them as I entered them wrong. Can anyone tel me how I can delete the custom ones I have made or reset back to defaults. I am guessing they are written out to a

  • HT1229 Can I Transfer iPhoto Pics From A Old Computer To A New Computer?

    About to get a new computer soon and I want to transfer my pictures from iPhoto from computer A to computer B.  Anyway it can be done?  I need to get this resolved within a week if possible.  Any help I will be grateful.

  • How to delete tag and link in webcenter spaces .

    After logging into the webcenter spaces i am getting tags and link on the hight hand corner of the page . Can anyone provide some idea how can i delete or make it invisible . Thanks , Arun.