Port-Channel MDS & UCS with a particular vsan

I am having trouble setting up a  port-channel between MDS & UCS with a particular vsan. I was able to get a port-channel setup on VSAN 1 between and MDS9513 5.0(4d) and UCS 6120 XP 4.2 (1). When I try to do it with a specifc VSAN it fails. I set the VSAN on the 9513 interfaces and created the port-channel but it looks like it still wants to default to VSAN 1 when I do a  sh int. I have added the same VSAN on the UCS side as well. I have tried to see if could set the vsan on the port-channel but it doesn't look like that command is offered. Any ideas?

Hello
Having no exp of UCS switches, this may be a bit off, but....
The vsan the port channel PORTS are in is of no consequence.  The VSAN's that are allowed to traverse the trunk are the important bits.  i.e:
interface port-channel 1
  switchport trunk allowed vsan 1
  switchport trunk allowed vsan add 60
  switchport trunk allowed vsan add 80
Steven

Similar Messages

  • Create port channel between UCS-FI and MDS 9124 (F Mode)

    Dear Team,
    We were trying to create  port channel between UCS FI and MDS 9124
    But the port channel not getting active in F mode on MDS 9124
    FI is in FC End Host Mode
    We have enabled FC uplink trunking on FI
    We have enabled NPIV on MDS
    We have enabled trunk on MDS
    FI and MDS in default VSAN
    To check we changed the FI mode to FC Switching mode and port channels became active but in E mode
    when we enabled FC uplink trunking on FI and FC Switching mode port channels became active in TE mode
    but in both the above cases showflogi database shows WWPN of SAN alone not showing any from FI.
    How to achive this?
    Have read that no need to change the swicthing mode to FC Switching mode and keep as FC Endhost mode
    SO how to achieve Port channel with F mode in MDS and FI ( Mode showing as NProxy)
    Does it has to do anything with MDS NX-OS version? (https://supportforums.cisco.com/thread/2179129)
    If yes how to upgrade as license for ports came along with Device and we do not have any PAC/PAK or license file as it came
    with license
    Also we have seen 2 files availabe for download (m9100-s2ek9-kickstart-mz.5.2.8b.bin and m9100-s2ek9-mz.5.2.8b.bin) which to use
    Thanks and Regards
    Jose

    Hi Jo Bo,
    what version of software if your MDS running?
    On your UCS do connect nxos and show inteface brieft and look at the mac address.
    it is possible that you might be hitting the bug below. if this is the case you might need to upgrade the firmware on your MDS.
    Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty04686
    Symptom:
    Nexus switch unable to connect any other Nexus or other Cisco Switch in NPV mode with a F port-channel.   Issue might be seen in earlier 5.1 releases like
    5.1.3.N1.1a
    but not the latest
    5.1.3.N2.1c
    release. Issue is also seen in
    5.2(1)N1(1)
    and
    6.0(2)N1(1)
    and later releases.
    Conditions:
    Nexus configured for SAN PortChannels or NPIV trunking mode Nexus connected to UCS via regular F port channel where UCS in NPV mode  NPV edge switch: Port WWN OUI from UCS FI  or other Cisco manufactured switch:  xx:xx:00:2a:6a:xx:xx:xx   OR  xx:xx:8c:60:4f:xx:xx:xx
    Workaround:
    Turn-off trunking mode on Nexus 5k TF-port Issue does not happen with standard  F-PORT Remove SAN Portchannel config
    Further Problem Description:
    To verify the issue please collect  show flogi internal event-history errors  Each time the port is attempted OLS, NOS, LRR counters will increment. This can be determined via the following output,  show port internal info all show port internal event-history errors

  • FC Port Channel between UCS and MDS.

    Hi All,
    I am new to Cisco Fabric Concepts. In my enviornment i have a F port channel(8 Port Group) created on MDS 9513 switch and this Fport 
    channel is connected to Cisco UCS 6296 FI. The Cisco UCS Blade servers are connected to the Fabric Interconnect .
    On MDS NPIV is enabled.
    Can anyone explain the below questions.
    1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
    2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
    3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to 
    do the same.Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
    4. What happens when a VSAN on MDS switch is added to the Port Channel.
    Thanks and Regards,
    Santosh surya

    Look at my remarks in
    https://supportforums.cisco.com/discussion/12468266/fc-port-channels-between-mds-and-ucs-fi-best-practice
    1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
    F port channel is proprietary; therefore any such F port channel between UCS FI and Brocade doesn't work.
    2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
    see eg.
    https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
    3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to 
    see eg.
    https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
    Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
    flogi database is on the MDS, not FI; there are however UCS CLI commands, like "show npv ...."
    4. What happens when a VSAN on MDS switch is added to the Port Channel.
    If its not created on UCS, it will just not become the status "up"

  • Port-channel L2 problem with Fabric Interconnect and Nexus 7010

    Hi,
    i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
    but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
    is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
    i attach the topology of N7K with Fabric interconnect.
    regards,
    Berwin H

    Hi Manish,
    the issue was solved, i was fix it last week.
    the solution is:
    i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2)  so i allocate the interface on all module
    /* 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:0cm 5.4pt 0cm 5.4pt;
    mso-para-margin-top:0cm;
    mso-para-margin-right:0cm;
    mso-para-margin-bottom:10.0pt;
    mso-para-margin-left:0cm;
    line-height:115%;
    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-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
    i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
    So here the result of my port-channel :
    SVRN7KFARM-HO-01# show port-channel summary
    Flags:  D - Down        P - Up in port-channel (members)
            I - Individual  H - Hot-standby (LACP only)
            s - Suspended   r - Module-removed
            S - Switched    R - Routed
            U - Up (port-channel)
    Group Port-       Type     Protocol  Member Ports
          Channel
    1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                         Eth1/4(P)    Eth1/25(P)  
    2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                         Eth1/12(P)   Eth1/26(P)  
    3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)  
    4     Po4(SU)     Eth      NONE      Eth10/32(P)  Eth10/34(P)  Eth10/35(P)
                                         Eth10/36(P)
    Thanks.
    Berwin H

  • MDS configuration for port channel

    I've tried to set up the new FC port channel upload to a pair of MDS 9124s, but as I don't know enough about the MDS side I can't get the link to come up. Are there any references available anywhere that tell you blow by blow exactly how to configure the MDS side of the port channel? Or perhaps a sample working config?
    Thanks

    Simon,
    A few items:
    1) You are on 1.4.1i Balboa code
    2) FI's are in FC switch mode as MDS 9124's don't support F-port channel (NPV/NPIV)
    3) It's a lot easier the first time if you have matched speed sfp+ all around. Although, with the correct configs, unmatched speeds can be made to work.
    If the FIs are in switch mode and your MDS is running a minimum 3.3 here are some configs that may help:
    MDS side interfaces 4/11 and 4/12 are plugged into the UCS fc ports. First setup and ensure ISLs are working properly between UCS and MDS, then configure the port-channels
    interface fc4/11
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      no shutdown
    interface fc4/12
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      no shutdown
    The UCS GUI Equipment -> Fabric Interconnects -> FI-A -> Set FC Switching Mode. This will cause both FI's to reboot into FC switch mode. This is VERY DISRUPTIVE, both FI's will reboot.
    On the UCS CLI you should see this on the UCS fc ports connected to the MDS
    cae-sj-ca3-A(nxos)# show running-config interface fc 2/1-2
    !Command: show running-config interface fc2/1-2
    !Time: Wed Oct 20 16:49:39 2010
    version 4.2(1)N1(1.4)
    interface fc2/1
      switchport mode E
      no shutdown
    interface fc2/2
      switchport mode E
      no shutdown
    Until you have VSAN trunks enabled, make sure the ports on the UCS and MDS are in the same VSAN. VSAN 1 for example.
    Once you have working ISLs, then proceed to turn them into port-channels and enable VSAN trunking. Start with the MDS
    Create a channel group, it should look like this
    cae-sj-9506-1# show run interface port-channel 3
    !Command: show running-config interface port-channel 3
    !Time: Wed Oct 20 17:06:01 2010
    version 5.0(1a)
    interface port-channel 3
      channel mode active
      switchport mode E
      switchport rate-mode dedicated
      switchport trunk mode auto  <-- VSAN trunking
    Enable VSAN trunking on the MDS ISL interfaces, it'll look like this:
    cae-sj-9506-1# show run interface fc 4/11-12
    !Command: show running-config interface fc4/11-12
    !Time: Wed Oct 20 17:07:05 2010
    version 5.0(1a)
    interface fc4/11
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      no shutdown
    interface fc4/12
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      no shutdown
    Add the channel group information to the MDS ISL interfaces:
    Enter configuration commands, one per line.  End with CNTL/Z.
    cae-sj-9506-1(config)# interface fc 4/11-12
    cae-sj-9506-1(config-if)# channel-group 3 force
    fc4/11 fc4/12 added to port-channel 3 and disabled
    please do the same operation on the switch at the other end of the port-channel,
    then do "no shutdown" at both ends to bring it up
    cae-sj-9506-1(config-if)# show run interface fc 4/11-12
    !Command: show running-config interface fc4/11-12
    !Time: Wed Oct 20 17:07:39 2010
    version 5.0(1a)
    interface fc4/11
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      channel-group 3 force
      no shutdown
    interface fc4/12
      switchport rate-mode dedicated
      switchport mode E
      switchport trunk mode auto
      channel-group 3 force
      no shutdown
    Create the SAN port channel on the UCS side
    SAN -> SAN Cloud -> Fabric A -> FC Port Channels -> Create Port Channel
    After you create the SAN port channel in UCS, make sure and enable it. I also bounce the MDS port channel at this point.
    If all is correct, in a few agonizing minutes, the port-channel will be formed and passing data.
    cae-sj-ca3-A(nxos)# show interface san-port-channel 1
    san-port-channel 1 is trunking
        Hardware is Fibre Channel
        Port WWN is 24:01:00:0d:ec:d3:5d:c0
        Admin port mode is E, trunk mode is on
        snmp link state traps are enabled
        Port mode is TE
        Port vsan is 1
        Speed is 8 Gbps
        Trunk vsans (admin allowed and active) (1,10,26,50,66,100-101,103,123,222,24
    0)
        Trunk vsans (up)                       (1,10,50,100,103)
        Trunk vsans (isolated)                 (26,66,101,123,222,240)
        Trunk vsans (initializing)             ()
        5 minute input rate 2312 bits/sec, 289 bytes/sec, 2 frames/sec
        5 minute output rate 1440 bits/sec, 180 bytes/sec, 2 frames/sec
          2669 frames input, 194760 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          2677 frames output, 158316 bytes
            0 discards, 0 errors
          0 input OLS, 1 LRR, 0 NOS, 0 loop inits
    Again, make sure you have the ISLs up an running first before configuring the port-channels. It makes troubleshooting much easier.
    Let me know if you need any help.

  • Port-channel issue with FI-N7k using rate-mode share

    Hi Dears,
    I'm trying to using port-channel between Fabric Interconnect (FI) and N7K. in N7K use rate-mode share and LACP but the port-channel in N7K was suspended.
    I was trying :
    1. I using non dedicated port in Nexus 7010.
          - rate-mode share
          - channel-group 1 mode active
          - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    2. I using non dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode on
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
    3. I using dedicated port in Nexus 7010
         - rate-mode share
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was suspended
    4. I using dedicated port in Nexus 7010
         - rate-mode dedicated
         - channel group 1 mode active
         - switchport mode trunk
    when i using this option, the port-channel in Nexus 7010 was came up and running well.
    is any other way to configure port-channel in N7K with rate-mode share and LACP ?
    or it's some of limitation in port-channel when using rate-mode share at N7K ?
    nb: fabric interconnect only support LACP and cannot be configurable.
    regards,
    Berwin H

    HI Mark,
    1. Can you please check your ethernet card ...where this port channel connected..on the server.
        may be there are 2 different card.
    2. from cisco websites:
    Error Message
    Explanation
    This port has different port attributes than other ports within the port channel.
    Recommended Action
    Match the port attributes to that of the port channel.
    Regards
    Please rate if it helps.
    Match the port attributes to that of the port channel.This port has different port attributes than other ports within the port channel.
    EC-5-CANNOT_BUNDLE_LACP: [char] is not compatible with aggregators in
    channel [dec] and cannot attach to them ([char])

  • Port channel is not working proprely with WLC

    Hi,
    Im trying to create port channel between switch and WLC, port channel is up but 2nd link WLC and switch is not coming up.
    Cable is fine and I can see link flaps error on WLC logs.
    Any idea..
    Regards,

    Hi,
    We are using "on" mode, from switch side port channel is up with 1st link but 2nd link status is showing not connect.
    When I check WLC, I can see 2nd link flaps error.We have also verified the cable connectivity
    Am I missing anything.
    Regards,

  • FC Port Channel, Storage Cloud???

    Hi. Cisco gurus:
    May I have the authoritative answers on the following?
    1. What is the Use Case of FC Port Channel under SAN Cloud assuming I have the typical Cisco VSAN setup-1 VSAN tied to 1 SAN Switch and 1 FCoE VLAN and another VSAN with diff. VSAN and FCoE ids, etc?
    1.1 What is the commands needed in MDS switch to match the FC Port Channel in UCS so as to make it works, so to speak.
    1.2 Will it make any differences between the End-Host Mode and Switch Mode?
    2.
    What is the benefits of FC Port Channels? Is it REALLY necessary at all assuming the same as 1 above with 2 Uplink FC Per Fabric Interconnect?
    3.
    What is the Use Case of Storage Cloud? Is it ONLY for direct-attached FC storage to our Fabric Interconnect?
    Thank again. Help me to help Cisco to sell more UCS.
    SiM

    Sim, assuming you aren't using pin groups UCS will automatically re-pin the server vNIC/vHBA in the evnet of a LAN/SAN uplink failure. This re-pinning will take a few seconds but that isn't enough that you would notice the down time.
    With a port channel no re-pinning has to happen as there is only a single logical uplink. When physical connection in a port channels fails there is a sub-second convergence time.
    Port channels offer better band-width utilization because all servers are pinned to a single logical uplink.
    If you do not have MDS FC switches then you can't create a SAN port channel. For non-MDS environments with 2 or more FC uplinks UCS will perform dynamic pinning of server vHBAs to those uplinks in a round-robin fashion. If one of the uplinks fails UCS will re-pin those vHBAs to another uplink.
    Most of our UCS customers don't need VSAN trunking as they ony have 1 VSAN northbound from each fabric but if you did have more the one VSAN on your fabric then you could provision a vHBA to be in that VSAN. For example lets say you had 2 storay arrays on each SAN fabric and each was in its own VSAN. You could create vHBAs in the different VSANs so that you could build a server that has access to LUNs in either array.

  • FabricPath vPC port-channel err-disabled CE Vlan?

    I have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
    Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
    If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
    Thanks

    I have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
    Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
    If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
    Thanks

  • Creating san-port-channel on 6248 using CLI

    I can create the san port channel using UCS manager. But I would like to know the syntax using CLI. So far I was able to figure out the following. One thing missing was moving the port channel from the default VSAN(1) to a different VSAN i.e VSAN 10 in my case. I have looked at the CLI guide, but have not found the commands syntax. Appreciate if anyone can post the syntax
    ### Create Port Channel ###
    scope fc-uplink
    scope fabric a
    create port-channel 1
    enable
    set name port-channel-1
    set adminspeed auto
    commit-buffer
    end
    ### Add interfaces to Port Channel ###
    scope fc-uplink
    scope fabric a
    scope port-channel 1
    create member-port 1 29
    exit
    create member-port 1 30
    commit-buffer
    end

    Thanx Wdey. That's exactly what I was looking for. Here is the syntax which works for me.
    scope fc-uplink
        scope fabric a
            create port-channel 1
            enable
            set name port-channel-1
            set adminspeed auto
        commit-buffer
    end
    scope fc-uplink
        scope fabric a
            enter port-channel 1
                enable
                enter member-port 1 29
                enable
                exit
                enter member-port 1 30
                enable
                exit
                set adminspeed auto
            exit
            enter vsan VSAN10 10 10
                set fc-zoning disabled
                set fcoe-vlan 10
                set id 10
                enter member-port-channel a 1
                exit
                localize
             exit
         end
    commit-buffer

  • Port-Channel Help

    So, I had some trouble yesterday with creating some port-channels and was wondering if anybody has seen this before. I created a port-channel from my 6509 to a 4506 and tried to add two interfaces in an active mode. A couple things happened:
        1. Received an error " %EC-SP-5-CANNOT_BUNDLE_LACP: Gi4/11 is not compatible with aggregators in channel"  which i can't seem to figure out why.
        2. I do have spanning-tree on the interfaces connecting but what happened was the port-channel came up with one interface in it and the other interface came up...both in a forwarding state. This cause a big loop as these were trunk ports and brought down the network. 
        3. Interfaces went down, but never came back up setting leaf switch all over in an errdisable state.
    Can anybody help with any of these? Thanks

    Hi,
    Check whether flow control is on all ports in module 4.if some of the ports are off.kindly make sure to enable on.
    Use below command to check flow control status:
    switch-a#sh int flowcontrol module 4 
    regards
    Moorthy

  • 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

  • Cisco MDS port channel with USC FI

    Hello,
    Can anyone help me to configure/troubleshoot Cisco MDS 9148 with Cisco USC ? M stuck in port channel..i have configured but interfaces are not coming UP.It is showing init state.
    My Topology is like,
    Nexus 5000-->USC FI (single FI) -->Cisco MDS 9148
                                                     --> Two Chassis
    Any help would be highly appreciated...
    Thanx

    TMC-UCSFI-A-A(nxos)# sh interface brief
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/31     1      NP     off     errDisabled      swl    --           --
    fc1/32     1      NP     off     errDisabled      swl    --           --
    Ethernet      VLAN   Type Mode   Status  Reason                   Speed     Port
    Interface                                                                   Ch #
    Eth1/1        1      eth  fabric up      none                        10G(D) --
    Eth1/2        1      eth  fabric up      none                        10G(D) --
    Eth1/3        1      eth  fabric up      none                        10G(D) --
    Eth1/4        1      eth  fabric up      none                        10G(D) --
    Eth1/5        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/6        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/7        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/8        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/9        1      eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1      eth  trunk  up      none                        10G(D) 100
    Eth1/16       1      eth  trunk  up      none                        10G(D) 100
    Eth1/17       1      eth  fabric up      none                        10G(D) --
    Eth1/18       1      eth  fabric up      none                        10G(D) --
    Eth1/19       1      eth  fabric up      none                        10G(D) --
    Eth1/20       1      eth  fabric up      none                        10G(D) --
    Eth1/21       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1      eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1      eth  access down    SFP not inserted            10G(D) --
    output ommitted
    TMC-UCSFI-A-A(nxos)#
    Here it shows that Fc1/31- 32 which are in trunk , status is errdisabled and admin trunk mode is off

  • Port-Channel issue between UCS FI and MDS 9222i switch

    Hi
    I have a problem between UCS FI and MDS switch port-channel. When MDS-A is powered down the port-channel fails but UCS blade vHBA does not detect the failure of the port-chanel on UCS-FI and leaves the vHBA online. However, if there is no port-channel between FI-->MDS it works fine.
    UCS version   
    System version: 2.0(2q)
    FI - Cisco UCS 6248 Series Fabric Interconnect ("O2 32X10GE/Modular Universal Platform Supervisor")
    Software
      BIOS:      version 3.5.0
      loader:    version N/A
      kickstart: version 5.0(3)N2(2.02q)
      system:    version 5.0(3)N2(2.02q)
      power-seq: Module 1: version v1.0
                 Module 3: version v2.0
      uC:        version v1.2.0.1
      SFP uC:    Module 1: v1.0.0.0
    MDS 9222i
    Software
      BIOS:      version 1.0.19
      loader:    version N/A
      kickstart: version 5.0(8)
      system:    version 5.0(8)
    Here is the config from MDS switch
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/1      103    auto   on      trunking         swl    TF      4    10
    fc1/2      103    auto   on      trunking         swl    TF      4    10
    fc1/9      103    auto   on      trunking         swl    TF      4    10
    fc1/10     103    auto   on      trunking         swl    TF      4    10
    This is from FI.
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/29     103    NP     on      trunking         swl    TNP     4    103
    fc1/30     103    NP     on      trunking         swl    TNP     4    103
    fc1/31     103    NP     on      trunking         swl    TNP     4    103
    fc1/32     103    NP     on      trunking         swl    TNP     4    103
    Any thoughts on this?

    Sultan,
    This is a recently found issue and is fixed in UCSM 2.0.3a version .
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCua88227
    which got duped to  CSCtz21585
    It happens only when following conditions are met
    FI in End host mode
    FC uplinks are configured for portchannel + trunking
    Certain link event failures ( such abrupt power loss by upstream MDS switch )
    Padma

  • FC port channels between MDS and UCS FI best practice?

    Hi,
    We would like to create FC port channels between our UCS FI's and MDS9250 switches.
    At the moment we have 2 separate 8Gbps links to the FI's.
    Are there any disadvantages or reasons to NOT do this?
    Is it a best practice?
    Thanks.

    As Walter said, having port-channels is best practice.  Here is a little more information on why.
    Let's take your example of two 8Gbps links, not in a port-channel ( and no static pinning ) for Fibre Channel connectivity:
    Hosts on the UCS get automatically assigned ( pinned ) to the individual uplinks in a round-robin fashion.
    (1)If you have some hosts that are transferring a lot of data, to and from storage, these hosts can end up pinned to the same uplink and could hurt their performance. 
    In a port-channel, the hosts are pinned to the port-channel and not individual links.
    (2)Since hosts are assigned to an individual link, if that link goes down, the hosts now have to log back into the fabric over the existing working link.   Now you would have all hosts sharing a single link. The hosts will not get re-pinned to a link until they leave and rejoin the fabric.  To get them load balanced again would require taking them out of the fabric and adding them back, again via log out, power off, reload, etc...
    If the links are in a port-channel, the loss of one link will reduce the bandwidth of course, but when the link is restored, no hosts have to be logged out to regain the bandwidth.
    Best regards,
    Jim

Maybe you are looking for