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.

Similar Messages

  • FCoE Port Channels on Single Nexus 5K - possible?

    I'm looking for information regarding FCoE on a single Nexus 5548. I'm trying to set up a port channel from a Netapp filer's CNA adapters (2 twinax cables). I was told that for some reason port channels do not work on a single Nexus 5K design (i.e. no vPC), but I didn't know if that meant simply without the use of LACP. I've configured it in both fashions, and it seems that the VFCs do not want to come up, meaning that my filers cannot log in to the SAN. This behavior is what was described to me as what would happen if I tried doing a port channel in this way - basically I've bound the VFCs to the port channels, and since the port channels are composed of ports on the same switch, it just doesn't work. Seems odd that this would bet the case, though it would normally force me to simply buy a second N5K (sneaky sneaky).
    Any tips?

    That's not my issue. I'm using only one Nexus 5K, meaning that if I want to have a port channel running between the 5K and the Netapp filers, I have to bind the virtual fibre channel interfaces to that port channel. I believe that in doing so, when there are more than one links as a member of that port channel, the VFCs simply go down by design and will not come up. For some reason VFCs require to be bound to a single physical interface, whether that interfaces is a single phyiscal port or a port channel that's only configured to have one port in it.
    Either way, I had to configure the Netapp side to be active/passive. I've bound the VFCs to each port (total of 4, so 4 VFCs as well). No port channels are being used on the Nexus side. This is not ideal but it works.
    I would still like to see some documentation regarding the behavior of the VFCs when presented with multiple links in this way. Has anyone seen any documentation regarding this?

  • SG500x Port-channel limited bandwidth

    Good Day All,
    I have 2 Cisco SG500X-48 setup as Master/Slave using SFP-H10GB-CU1M (10GB Twinax cable).
    First question is with the twinax cables
    Since on the SG500x's you can not configure the 2*10GE Stacking Combo ports. If I put two cables in for redundancy will this cause a network loop, or will STP/RSTP catch this?
    Next question is limited bandwidth.
    I setup 4 Interfaces to Port channel with LACP. On the Server(HP Proliant Gen8 server(s)) end have the NIC Team with 4 NICs. When I run a network stress tool, it seems to cap at around 68MBs. Each port should being 1Gb, shouldn't I be getting closer to 4 GB?
    My Configuration would read much like this:
    VLANs setup:
    ##1-RF System
    ##2-VOIP
    ##3-LAN
    interface Port-channel 3
    spanning-tree portfast
    switchport trunk allowed vlan add ##1,##2
    switchport trunk native vlan ##3
    interface gigabitethernet2/1/5
    spanning-tree portfast
    channel-group 3 mode auto
    switchport mode access
    interface gigabitethernet2/1/6
    spanning-tree portfast
    channel-group 3 mode auto
    switchport mode access
    interface gigabitethernet2/1/7
    spanning-tree portfast
    channel-group 3 mode auto
    switchport mode access
    interface gigabitethernet2/1/8
    spanning-tree portfast
    channel-group 3 mode auto
    switchport mode access
    I dont have much under standing on QOS yet, I assuming this would be based on setting up this?
    Any direction or help would be greatly appreciated
    Chris,

    Hello Chris,
    The way the stacking cables works is it detects when you are using two of them and switches over to what is called 'ring' mode.  It doesn't use both links at once, but if one of those links fails it will immediately use the second one, usually not even dropping one packet.  STP isn't an issue on the stack ports because it doesn't really use it, the stacking is a proprietary protocol that handles all of this for you.  So go ahead and plug up your second set of cables, you should see a log message saying you have moved from 'chain' to 'ring'.
    As for LAGs, this is a common misconception with link aggregation.  I understand the logic, you have 4 gig links, why can't you get 4 gigs of throughput?  It has to do with how LAGs actually work.
    When a packet arrives at the switch and needs to go out the LAG the switch runs a calculation on the source and destination IP (or source and destiantion MAC depending on your settings).  From this calculation it comes up with a number, in your case from 1-4.  That determines the link that it uses to get across that LAG.  There is no way to make one conversation use more than one link, it just isn't how it works.  So when you run a speed test from one IP to one other IP, the result of the switch's calculation will always be the same number, hence all the traffic for that stream goes down the same link in the LAG.
    There isn't any spillover, so even if one link is much busier then the rest it doesn't move them over to one of the other links.
    On some enterprise switches you can use a load balancing algorithm that uses source and destination port, which can result in multiple conversations between the same two clients to use multiple links, but on the Small Business switches we only have IP or MAC.
    Basically any one conversation will always be limited to whatever the speed of 1 link in the LAG is.
    It is possible to utilize the link more, but you would need several different computers talking to the server to really see that.  QoS would not change this.
    As for your speed, it is a bit low, the max for a gigabit link is about 118MB/s (lab max, your mileage may vary) if you are using normal sized frames.  This is assuming two devices directly connected to the with no routing required.  How are you testing the speed?  I like to use a program called Tamosoft throughput tester for this, which is available free on the web.
    Hope that helps a bit,
    Christopher Ebert - Advanced Network Support Engineer
    Cisco Small Business Support Center
    *please rate helpful posts*

  • ASA5550 port channel configuration ERROR: nameif not allowed on empty etherchannel interface

    Hi All,
    I am having problem when configure port channel on asa5550 
    IOS ver asa914-k8.bin also in ver 9.02   and 8.47.
    Please let me know how can I solve this problem.
    UK-LON-FW(config)# int port-channel 3
    UK-LON-FW(config-if)# vlan 245
                           ^
    ERROR: % Invalid input detected at '^' marker.
    UK-LON-FW(config-if)# nameif secure
    ERROR: nameif not allowed on empty etherchannel interface.
    UK-LON-FW(config-if)#
    here is my interfaces configuration:
    interface GigabitEthernet0/0
    description fw1:G0/0 to uk-lon-gw1:e1/8 fw2:G0/0 to uk-lon-gw2:e1/9 outside zone
    channel-group 1 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/1
    description fw1:G0/1 to uk-lon-gw2:e1/8 fw2:G0/1 to uk-lon-gw1:e1/9 outside zone
    channel-group 1 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/2
    description fw1:G0/2 to uk-lon-sw1a:1 fw2:G0/2 to uk-lon-sw1a:2 dmz
    channel-group 2 mode on
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet0/3
    description fw1:G0/3 to uk-lon-sw1b: fw2:G0/3 to uk-lon-sw1b:2 dmz
    channel-group 2 mode on
    no nameif   
    no security-level
    no ip address
    interface Management0/0
    management-only
    nameif management
    security-level 0
    ip address 10.10.51.18 255.255.254.0
    interface GigabitEthernet1/0
    description fw1:G1/0 to uk-lon-sw1a:3 fw2:G1/0 to uk-lon-sw1a:4 secure zone
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/1
    description fw1:G1/1 to uk-lon-sw1b:3 fw2:G1/1 to uk-lon-sw1b:4 secure zone
    no nameif
    no security-level
    no ip address
    interface GigabitEthernet1/2
    description LAN Failover Interface
    no nameif   
    no security-level
    no ip address
    interface GigabitEthernet1/3
    description STATE Failover Interface
    no nameif
    no security-level
    no ip address
    interface Port-channel1
    description outside zone
    no nameif
    no security-level
    no ip address
    interface Port-channel1.5
    description outside zone Bundle FW:G0/0-G0/1 connect to GW1:e1/8-GW2:e1/8
    vlan 5
    nameif outside
    security-level 0
    ip address 216.239.105.5 255.255.255.128 standby 216.239.105.6
    interface Port-channel2
    description dmz Bunlde uk-lon-fw:G0/2-3 to sw1a:1-2 sw1b:1-2
    no nameif
    no security-level
    no ip address
    interface Port-channel2.105
    description dmz
    vlan 105
    nameif dmz
    security-level 50
    ip address 216.239.105.193 255.255.255.192 standby 216.239.105.194
    interface Port-channel3
    description secure zone Bunlde uk-lon-fw:G1/0-1 to sw1a:3-3 sw1b:3-4
    no nameif
    security-level 100
    ip address 10.254.105.1 255.255.255.0 standby 10.254.105.2
    UK-LON-FW(config-if)# 

    Hi Marvin,
    Thank you for your answer.  I did everything but it did not work. Turn out it is a bug ver 8.45 will let you created the sub logical interface but actually it did not work right.  Verson 9.x  doesn't let you create more than 2 port channel (limitation of ASA5550 hardware).
    https://tools.cisco.com/bugsearch/bug/CSCtq62715/?reffering_site=dumpcr 
    Also, you can see the 8.4 release notes were you can see that it is not supported:
    http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/release/notes/asarn84.html#pgfId-522232
    Interface Features
    EtherChannel support (ASA 5510 and higher)
    You can configure up to 48 802.3ad EtherChannels of eight active interfaces each.
    Note You cannot use interfaces on the 4GE SSM, including the integrated 4GE SSM in slot 1 on the ASA 5550, as part of an EtherChannel.
    We introduced the following commands: channel-group , lacp port-priority , interface port-channel , lacp max-bundle , port-channel min-bundle , port-channel load-balance , lacp system-priority , clear lacp counters , show lacp , show port-channel .

  • UCS FI 6248 to Nexus 5548 San port-channel - not working

    Hi all,
    I'm sure I am missing something fairly obvious and stupid but I need several sets of eyes and help.
    Here is the scenario:
    I want to be able to create san port-channels between the FI and Nexus.  I don't need to trunk yet as I can't even get the channel to come up.
    UCS FI 6248:
    Interfaces fc1/31-32
    Nexus 5548
    interfaces fc2/15-16
    FI is in end-host mode and Nexus is running NPIV mode with fport-channel-trunk feature enabled.
    I'm going to output the relevants configurations below.
    Nexus 5548:
    NX5KA(config)# show feature | include enabled
    fcoe                  1         enabled
    fex                   1         enabled
    fport-channel-trunk   1         enabled
    hsrp_engine           1         enabled
    interface-vlan        1         enabled
    lacp                  1         enabled
    lldp                  1         enabled
    npiv                  1         enabled
    sshServer             1         enabled
    vpc                   1         enabled
    interface san-port-channel 133
      channel mode active
      no switchport trunk allowed  vsan all
      switchport trunk mode off
    interface fc2/15
      switchport trunk mode off
      channel-group 133 force
    no shutdown
    interface fc2/16
      switchport trunk mode off
      channel-group 133 force
    no shutdown
    NX5KA# show vsan membership
    vsan 1 interfaces:
        fc2/13            fc2/14          
    vsan 133 interfaces:
        fc2/15            fc2/16            san-port-channel 133
    vsan 4079(evfp_isolated_vsan) interfaces:
    vsan 4094(isolated_vsan) interfaces:
    NX5KA# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc2/15(D)    fc2/16(D)   
    UCS Fabric Interconnect outputs:
    UCS-FI-A-A(nxos)# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc1/31(D)    fc1/32(D)   
    UCS-FI-A-A(nxos)#
    UCS-FI-A-A(nxos)# show run int fc1/31-32
    !Command: show running-config interface fc1/31-32
    !Time: Fri Dec 20 22:58:51 2013
    version 5.2(3)N2(2.21b)
    interface fc1/31
      switchport mode NP
      channel-group 133 force
      no shutdown
    interface fc1/32
      switchport mode NP
      channel-group 133 force
      no shutdown
    UCS-FI-A-A(nxos)#
    UCS-FI-A-A(nxos)# show run int san-port-channel 133
    !Command: show running-config interface san-port-channel 133
    !Time: Fri Dec 20 22:59:09 2013
    version 5.2(3)N2(2.21b)
    interface san-port-channel 133
      channel mode active
      switchport mode NP

    !Command: show running-config interface san-port-channel 133
    !Time: Sat May 16 04:59:07 2009
    version 5.1(3)N1(1)
    interface san-port-channel 133
      channel mode active
      switchport mode F
      switchport trunk mode off
    Changed it as you suggested...
    Followed the order of operations for "no shut"
    Nexus FC -> Nexus SAN-PC -> FI FC -> FI SAN-PC.
    Didn't work:
    NX5KA(config-if)# show san-port-channel summary
    U-Up D-Down B-Hot-standby S-Suspended I-Individual link
    summary header
    Group  Port-      Type    Protocol               Member Ports
           Channel
    133    San-po133  FC      PCP      (D)  FC       fc2/15(D)    fc2/16(D)
    NX5KA(config-if)#
    Here is the output as you requested:
    NX5KA(config-if)# show int san-port-channel 133
    san-port-channel 133 is down (No operational members)
        Hardware is Fibre Channel
        Port WWN is 24:85:00:2a:6a:5a:81:00
        Admin port mode is F, trunk mode is off
        snmp link state traps are enabled
        Port vsan is 133
        1 minute input rate 1256 bits/sec, 157 bytes/sec, 0 frames/sec
        1 minute output rate 248 bits/sec, 31 bytes/sec, 0 frames/sec
          3966 frames input, 615568 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          2956 frames output, 143624 bytes
            0 discards, 0 errors
          46 input OLS, 41 LRR, 73 NOS, 0 loop inits
          257 output OLS, 189 LRR, 219 NOS, 0 loop inits
        last clearing of "show interface" counters never
        Member[1] : fc2/15
        Member[2] : fc2/16
    NX5KA(config-if)#
    NX5KA(config-if)# show int brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc2/13     1      auto   on      sfpAbsent        --     --           --
    fc2/14     1      auto   on      sfpAbsent        --     --           --
    fc2/15     133    F      off     init             swl    --           133
    fc2/16     133    F      off     init             swl    --           133

  • 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

  • ASA 5585 port-channels

    I want to create a port-channel with 2 10Gbs interfaces on 2 ASA 5585 firewalls, and set them up in a failover pair.
    In order to do this, do I simply put two 10Gbs interfaces into a channel and then configure the IP addressing and failover address on the logical port-channel interface? (aka interface po1).
    Any limitations with this?

    Yes, that is exactly what you do..
    Create portchannel on switch and ASA
    Trunk the vlan on switch side
    Create logical interfaces on ASA

  • Load-balancing Algorithm for NX-OS Port Channels

    Hi, all
    I do not understand description of port-channel load-balance ethernet command.
    switch(config)# port-channel load-balance ethernet ?
      destination-ip         Destination IP address
      destination-mac        Destination MAC address
      destination-port       Destination TCP/UDP port
      source-dest-ip         Source & Destination IP address (includes l2)
      source-dest-ip-only    Source & Destination IP addresses only
      source-dest-mac        Source & Destination MAC address
      source-dest-port       Source & Destination TCP/UDP port (includes l2 and l3)
      source-dest-port-only  Source & Destination TCP/UDP port only
      source-ip              Source IP address
      source-mac             Source MAC address
      source-port            Source TCP/UDP port
    Please tell me what the following descriptions mean.
      Source & Destination IP address (includes l2)
      Source & Destination TCP/UDP port (includes l2 and l3)
    What are the meaning of "includes l2" and "includes l2 and l3" ?
    Thank you for your cooperation in advance.

    Hi Satoru,
    On the Nexus 5000/6000 platforms, all FEXs will inherit the global hashing algorithm from the parent device.
    On the Nexus 7000 platform, hashing algorithms can be assigned on a per FEX basis (all load balancing changes must be made from the Admin VDC):
    N7K-A(config)# port-channel load-balance src-dst ip-l4port fex 134
    Any FEX without a hashing algorithm configured with inherit the global hash. Making changes to the modular/global hash will not alter FEX specific hashing algorithms.
    To verify the configuration applied you can use this command:
    N5K_A# show port-channel load-balance
    On the Nexus 7000, the per FEX algorithm can be checked by appending the ‘fex <#>’ to the end of the command in the Admin VDC or the FEX’s respective VDC:
    N7K-A(config)# show port-channel load-balance fex 134
    Regards,
    Richard

  • About n1000v with port channel

    there is a n1000v connected to multiple upstream switches in the customer's production environment.
    the following is from the Cisco Nexus 1000V Interface Configuration Guide, Release4.2(1)SV2(2.1).
    You use vPC-HM mode to create a port channel when the switch is connected to multiple upstream switches
    that are not clustered.
    my question is,
    can I use LACP with multiple upstream switches that are not clustered?
    can I use LACP with multiple upstream switches that are stacked?
    if I stack multiple upstream switches,does it mean clustered?
    thanks.

    Hi,
    See some of the guidelines:
    Guidelines and Limitations
    Port channeling has the following guidelines and restrictions:
    •All ports in the port channel must be in the same Cisco Nexus 1000V module; you cannot configure port channels across Cisco Nexus 1000V modules.
    •Port channels can be formed with multiple upstream links only when they satisfy the compatibility requirements and under the following conditions:
    –The uplinks from the host are going to the same upstream switch.
    –The uplinks from the host going to multiple upstream switches are configured with vPC-HM.
    •You can configure multiple port channels on a device.
    •After you configure a port channel, the configuration that you apply to the port channel interface affects the port channel member ports. The configuration that you apply to the member ports affects only the member port where you apply the configuration.
    •You must remove the port security information from a port before you can add that port to a port channel. Similarly, you cannot apply the port security configuration to a port that is a member of a channel group.
    •You can configure ports that belong to a port channel group as PVLAN ports.
    •Any configuration changes that you apply to the port channel is applied to every member interface of that port channel.
    •Channel member ports cannot be a source or destination SPAN port.
    That said LACP should work on switches that are not clustered and meet the conditions above.
    A stack is treated as one unit which means that would be like you have just one big chassis.
    Stacking does not the same as clustering it works different. so if you stack them that would be a stack not a cluster
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1270746
    Hope this helps.

  • Determine NIF port used by VIF when configured in a port-channel

    I have recently just watched an excellent Cisco Live video on UCS performance troubleshooting which demonstrated how to trace network traffic within Cisco UCS. The speaker made a comment though, in order to determine which NIF is used by a VIF when port-channels are used between the FEX and FI there are different commands to run. Have to review the hash result or something he said. Unfortunately he never went into what these commands were.
    So when we have veths pinned to port-channels instead of HIFs and NIFs, what commands will show which path is being used?

    Duplicate of https://supportforums.cisco.com/discussion/12313436/determine-nif-port-used-vif-when-configured-port-channel

  • Layer 2 port-channel flood

    Hi all,
    I was wondering if you may be able to help me, hopefully I will provide enough information.
    The background to my problem is this. Every Tuesday morning around 10AM we were experiencing network slowdowns, after many weeks fault finding I have narrowed it down to two backup jobs and two vlans. These are quite substantial backup jobs each 100GB in size.
    The servers that are being backed-up are behind an ISA server which is controlling the routing for the subnets that these servers use. The ISA servers are load balanced using Microsoft NLB. It is thought by our security expert that this is the best way to secure these servers.
    On our core switch (6513) we have a static route pointing to these subnets and the vlans are defined. Here is the basic config of one of the vlans:-
    interface Vlan121
     description DB vlan
     no ip address
     ip flow ingress
     ip flow egress
    end
    ip route 192.168.221.0 255.255.255.0 192.168.219.10
    I have managed to stop the flooding going to the user switches by denying the 121 vlan on the port-channels. The issue is still apparent however on our top of rack switches (server switches). The reason for this is, there are servers that require vlan 121 on nearly every top of rack switch.
    If anyone can recommend a solution to this problem other than limiting vlans, I would greatly appreciate it.
    If you require any further information, please let me know.
    Kind regards,
    Jamie.

    Hi Jon, let me see if I can answer your questions.
    There are four VLANs that reside behind the ISA VLAN -121, 122, 123 and 124. Any traffic that requires access to these VLANs have to pass through the ISA because the ISA dcontrols all the routing for the subnets associated with these VLANs.
    The server that we are backing up lives on a VLAN 124 and the actual backup server lives on a VLAN outside of the protected VLANs. For the sake of argument lets say that the backup server is shown as the PC on VLAN 156. 
    When the 90GB backup is initiated, the traffic propagates to all trunk ports throughout the network. I see traffic running at 500Mbps and it can last for up to 20 hours.
    I have managed to stop the flood to all the user switches by denying the VLANs stated above. The problem is, I can't deny those VLANs to other top of rack switches because there is at lease one server in each switch that requires one of the VLANs.
    In a nutshell, when large amounts of traffic pass through VLAN 666 (ISA) we see it flood to all trunk ports. We think this could be due to the nature of MLB forming a virtual MAC address. The core doesn't know about the MAC address so it sends a unicast flood to find out where it is.
    If you have any ideas please let me know.
    J.

  • MDS Code Level for UCS FC Port Channel/Trunking

    What is the required MDS code level needed to support FC Port-Channeling/Trunking on a 9222i, 9148, or 9509/9513 w/ Gen2 line cards to UCS 1.4(3)?
    I know the fport-channel-trunk feature is needed and was released in MDS 4.2 code but I have seen documents that this level of code wont support these features when used to connect to Cisco UCS. 
    Can someone confirm?  Is NXOS 5.0(4) or higher required?

    Doug,
    I wrote the doc almost a year ago and it doesn't have the latest interop matrix support information. The current MDS NX-OS support is located in this doc: http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx.html
    While, I wish this was also duplicated in UCS docs, they are more or less taking the stance that 3rd party (Cisco MDS is this case) interop is maintained by the 3rd party. EMC, Netapp, or even Cisco.
    It would be a nightmare updating UCS docs with 3rd party qualifications and support.
    The short answer to your question is:
    UCS 1.4(1), 1.4(2), 1.4(3) Is supported by MDS9000: 3.3(4a), 3.3(5), 4.2(1a), 4.2(1b), 4.2(3a), 4.2(5), 5.0(1a), 5.0(4), 5.0(4c)
    NPV was introduced in MDS 3.3. f port-channel/trunk was introduced in MDS 4.2.
    As Ram mentioned above, 4.2(5) is what I would recommend if I wanted to implement f port-channel and/or f port-trunk. I have also had recent experience with 4.2(5) and it worked great with a large UCS f port-channel/trunk implementation
    The specific switch limitations I mentioned in my doc still exist. Only certain models of MDS will support f port-trunk. Almost all models will support f port-channel.
    Dave

  • 20gbit Port-channels using sfp+ ports

    Hi,
    I am hoping to implement a cost affective solution that can utilise the uplinks ports on the 2960-X & XR series switch and the appropriate up/downlink modules for the 3750-X series switch
    Would anyone know if it is possible to bundle the 10gbit sfp+ ports into a 20gbit port-channel?
    Has anyone done this or could they point me in the right direction for documentation?
    Thanks

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    BTW, don't forget, you only have two 10g ports per 3750X.

  • Multiple vsan traffic over single port-channel

    Hi -
    Scenario - 2 interface uplink (port-channel - Po10 ) from NetApp FAS-A to N5548-A & B. Po10 is currently configured with vPC10 and vFC10 at N5k end. single vfc currently mapped with a single vsan (vfc10 with vsan 1011).
    Q - Is it possible to make the Port-channel to pass multiple vsan (vsan 1011 & 1012). If yes, then how (over same vfc or by separate vfc on same port-channel)
    Subhankar      

    This router’s capability is only limited and dependent on the services that your ISP has given or allowed for you to use. I think it really has to be a one is to one configuration, not only with this router because I haven’t noticed any router that has this feature so far. This is really another idea for Linksys can work on.

  • Fiber Port Channel

    A bit of a noob question, but I can't seem to google (or bing) an answer.
    In the switching world (where I have more experience), if I create a bundle of 5 x 1Gb connections in an LACP port channel, I get 5Gb of bandwidth, but none of the individual 'conversations' can be more than 1Gb.   
    I am now looking at creating a Port Channel group between an MDS9148 and and MDS9134. If I bundle 5 of the 4Gb connections, I presumably get 20Gb of bandwidth. What I can't seem to find an answer on, is am I limited to 4Gb conversations again, or can a single source/destination pair use all 20Gb of the bandwidth?
    YP.        

    The single src-id/dst-id/ox-id conversation is limied to 4Gb.
    Port channel provides failover & exchange-based loadbalancing while reconvergence is not triggered in a case of single link failure.

Maybe you are looking for