Port-channel / Trunking / VSAN

Hi all,
I have a quick question...
I enabled trunking for all vsans and created a port-channel. I want to use this port-channel for all my vsans.
Does it matter in which vsan I add my port-channel?
If it doesn't matter why can I assign a port-channel to a vsan?
Cheers,
Mike

Mike,
It should be the same configuration on both sides for the port-channel to come up. The reason why you can assign a port-channel to a VSAN is that if you are using an E port then it depends on the matching port-channel VSAN to come up.
TE Port functionality is specific to MDS for enhanced ISL capabilities. E ports can be used for non-cisco switches to make the trunk work seamlessly as an E port.
You can refer to the following for more info:
http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/trnk.html
http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/pc.html
Hope this helps.
- Nikhil

Similar Messages

  • Fabric Interconnect To MDS 9148 FC Port Channel/Trunks

    Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
    Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
    These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
    Thanks

    Hello,
    Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
    Padma

  • 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

  • FC Port Channel & Trunking

    Hi, Cisco Experts:
    Can I have a definitive answer to the following?
    q1.
    EMC mentioned that they do not support FC Port Channel & Trunking with regard to our UCS Fabric Interconnects/MDS/VNX5300?
    Is that any truth in that?
    We are trying a Cisco UCS solutions with MDS and EMC VNX in the mix-SAN Boot basically, ESXi 5.1 and all others.
    q2.
    From MDS all the ways up to EMC VNX, is there such concept too-FC Port Channel & Trunking, assuming we are doing FC Port Channel & Trunking from FInterconnect to MDS?
    Please let me know.
    Appreciate it.
    SiM

    Hi Sim,
    We support FC port channel and trunking between UCS FI and MDS.
    Is EMC saying about the port channel between the MDS and VNX? Is there any document EMC pointed out?
    With respect to booting from SAN, yes, you can boot from SAN with MDS and EMC VNX as long as the OS is supported in the UCS system. You can refer to
    http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html for the supported OS versions.
    Hope this answers your question.
    -Ganesh

  • F-port-channel-trunk disruptive or not?

    Hi,
    We have a N5K with NPIV configured and and MDS9148 we're gonna setup a port channel and have come to the conclusion that we need the F-port-channel-trunk feature enabled on the MDS side.
    Question: Is enabling the F-port-channel-trunk feature on the MDS disruptive or non-disruptive?
    --M

    It's too late; I would say it is disruptive; however, the disruption is so short, that you didn't notice it. Similar without non F-port trunking channeling: using a link: the lost sessions are simply redistributed over the remaining links; new flogi is necessary.

  • 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

  • Xconnect 20Gb Port-channel over MPLS Possible?

    Can anybody confirm if you can establish an Xconnect between two 20Gb port-channels (2x 10Gig bundle).  The core is 40Gig and running MPLS.  We have many gigabit pseudowires running over it already.
    Our intention is to terminate 10Gig server traffic on 4900M's and then have a 20Gb Port channel trunk link into a 6500 (which is part of the MPLS cloud).   We would then issue the xconnect directly on the 20Gig port channel in order to traverse the MPLS Core.
    Has anyone configured this before?  Are there any caveats to watch out for?  What sort of performance hit (if any does) xconnect functionality have on 10Gig Traffic.

    Hi,
    Yes it's supported but test it first (as always ;-) )
    HTH
    Laurent.

  • 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

  • How to configure a port channel with VLAN trunking (and make it work..)

    We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack.  We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
    We want the same ports to be able to allow multiple vlans to communicate. (trunked)
    These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
    What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
    We are only able to configure an IP on one of the vlans.
    When we configure an IP from another vlan for the data lif, it does not respond to a ping.
    Does anyone have any idea what I'm doing wrong on the Cisco switch?
    interface GigabitEthernet4/0/12
    description Netapp2-e0a
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet4/0/13
    description Netapp2-e0c
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/12
    description Netapp2-e0b
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface GigabitEthernet6/0/13
    description Netapp2-e0d
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    channel-protocol lacp
    channel-group 20 mode active
    end
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    spanning-tree portfast
    spanning-tree bpduguard enable
    end

    Our problem was fixed by the storage people.  They changed the server end to trunk, and the encapsulation / etherchannel.
    I like all the suggestions, and they probably helped out with the configuration getting this to work.
    Thanks!
    interface Port-channel20
    description Netapp2-NFS
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    interface GigabitEthernet4/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet4/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/12
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active
    interface GigabitEthernet6/0/13
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 10,20,511,519
    switchport mode trunk
    channel-protocol lacp
    channel-group 20 mode active

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

  • Difference between Trunk links and port channel

    Hi 
    Can anyone please explain me the difference between the Trunk links and Ether channel ?

    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
    As the other posters have already described, in Cisco parlance, a "trunk" is a link that carries VLAN tagged frames.  (Note, Cisco has two technologies for these, ISL [old/proprietary] and IEEE 802.1Q [vendor independent].)  An Etherchannel (also called a port-channel) is one logical link that includes one or more physical links.  (Note, although Etherchannel can run across just one link, normally more than one link is configured.  Older and most Cisco implementations support up to 8 links in one channel bundle.  There's also multiple Cisco technologies that support Etherchannels, such as manual/PAgP[Cisco/old]/LACP[IEEE 802.3ad].)
    Trunk links might also be configured on an Etherchannel link.

  • SGE2010 port-channel and trunking config question

    I have port-channels configured and working for the native VLAN on multiple SGE2010s. I now want to add multiple VLANs and enable trunking for the port-channel. I am not clear on the appropriate way to enable trunking as it can be enabled on the port and on the port-channel. The ports and port-channel are currently in access mode. If anyone can provide the correct configuration, I would appreciate the guidance. I also need to get the port-channels and trunking working with 3Com 4500 & 4200s. If you know of any configuration issues, again any guidance would be appreciated

    Hi Jacqueline,
    Sorry Juans answer needs some correction, but I am grateful for Juans participation.
    The SGE2010 does not support a CLI.
    There is a unsupported CLI,  that someone plastered somehwere on this community, but i must admit i still like to use the GUI.
    The software on the SGE2XXX was recently updated so you can find that on the cisco.com website.
    I have created a link below  to a recording i just made,  regarding Link aggregation on the SGE2XXXX, i thnk if you see the 11 minute recording a couple of times, maybe pause it, play with your switch, it  will start to make sense.
    you can't breat the switch by configuring it
    click here to see a recording of me creating a Link aggregation between two switches
    regards Dave

  • Do I configure spanning-tree port type ed trunk on LACP port-channels

    Hello,
    Can't seem to see a clear answer and wondering if something could offer some advice please?
    We are using LACP aggregation across all our 10 gig attached servers and also trunking them.  We're running a VPC pair of 5596 Nexus.
    For a standard trunk port I always add the spanning-tree port type edge trunk to the interface config.
    However I think I should be adding this to the overiding port-channel config.  At present a colleague has configured the VPC below omitting the spanning-tree port type config.
    interface port-channel100
      description a-server
      switchport mode trunk
      switchport trunk allowed vlan 100
      vpc 100
    The port member configs are these which do contain the spanning tree port type:
    interface Ethernet1/1
      description a-server(1)
      switchport mode trunk
      switchport trunk allowed vlan 100
      spanning-tree port type edge trunk
      channel-group 100 mode active
    I always try to keep the overiding port channel config the same as its members and obviously for most config, you can't have disparate configs anyway.
    However for the spanning tree config the NexOS allows you to have the members with spanning tree port types and not have to reflect that in the port-channel.
    However I have this issue with STP:
    Switch1# show spanning-tree interface po100
    Vlan             Role Sts Cost      Prio.Nbr Type
    VLAN0100         Desg BKN*200       128.4996 (vPC) Network P2p *BA_Inc
    Is this due to the inconsistency with my port channel to member configs?
    Any advice would be gratefully accepted.
    Thanks!

    Hi Paul, there are some parameters you can define on individual ports and there are some of them that will be inherited from the port-channel configuration no matter what has been configured under the infidividual ports. Spanning-tree configuration is one of the inherited ones. As soon as the port joins into a port-channel, it will start to use spanning-tree settings under the port-channel. When it leaves the channel, then it can continue to use the individual configuration.
    There is a nice summary here under NX-OS Interface Conf Guide > Port-Channel Conf:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/interfaces/configuration/guide/if_portchannel.html#wp1798338
    Evren

  • Port Channel and VLAN trunking

    When configuring trunking of VLANS accross a Port Channel, do we need to configure vlan pruning on both the port-Channel port and the physical ports ???
    E.g. do I need to apply the "switchport trunk allowed vlan add " command under each physical port and the port channel port ? Or only under the port channel port ?
    Thanks

    In short, yes. Configure the port channel interface exactly as you do the physical interfaces and both ends should be an exact match. otherwise you will have problems getting the channel to come up or stay up.
    -Mark

  • Port-channel question on 9148

    hey I have a question about  port-channel.
    we have a port-channel 10 which contains 4 interfaces as below.
    my question is how the port-channel associated with the servers?  I mean the output "sh flogi database" as below........
    do we need to add port-channel as a zone member ? I think the answer is no since I don;t see the port-channel as a zone member....
    =================================================================
    tormds01# sh interface port-channel  10
    port-channel 10 is up
        Hardware is Fibre Channel
        Port WWN is 24:0a:54:7f:ee:a0:d5:48
        Admin port mode is auto, trunk mode is on
        snmp link state traps are enabled
        Port mode is F
        Port vsan is 510
        Speed is 32 Gbps
        5 minutes input rate 124316072 bits/sec, 15539509 bytes/sec, 9919 frames/sec
        5 minutes output rate 2205921104 bits/sec, 275740138 bytes/sec, 141424 frames/sec
          43540499847 frames input, 70772376296224 bytes
            0 discards, 0 errors
            0 CRC,  0 unknown class
            0 too long, 0 too short
          237450525827 frames output, 442040501099476 bytes
            0 discards, 0 errors
          0 input OLS, 0 LRR, 0 NOS, 0 loop inits
          0 output OLS, 0 LRR, 0 NOS, 0 loop inits
        Member[1] : fc1/1
        Member[2] : fc1/5
        Member[3] : fc1/9
        Member[4] : fc1/13
        Interface last changed at Tue Apr  8 22:16:49 2014
    tormds01# sh flogi database
    INTERFACE        VSAN    FCID           PORT NAME               NODE NAME      
    fc1/3            510   0x860000  50:06:01:64:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                               [torvnx01_spa0]
    fc1/7            510   0x860100  50:06:01:6c:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                               [torvnx01_spb0]
    fc1/11           510   0x860200  50:06:01:60:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                               [torvnx01_spa2]
    fc1/15           510   0x860300  50:06:01:68:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                               [torvnx01_spb2]
    port-channel 10  510   0x860400  24:0a:54:7f:ee:92:3e:80 21:fe:54:7f:ee:92:3e:81
    port-channel 10  510   0x860401  20:01:04:25:b5:3a:00:8f 20:01:00:25:b5:30:00:8f
                               [mcvhes0101hba0]
    port-channel 10  510   0x860402  20:01:04:25:b5:3a:00:9f 20:01:00:25:b5:30:00:9f
                               [mcvhes0102hba0]
    port-channel 10  510   0x860404  20:01:04:25:b5:3a:00:6f 20:01:00:25:b5:30:00:6f
                               [mcvhes0103hba0]
    port-channel 10  510   0x860408  20:01:04:25:b5:3a:00:7f 20:01:00:25:b5:30:00:7f
                               [mcvhes0104hba0]
    port-channel 10  510   0x86040f  20:01:04:25:b5:3a:00:4f 20:01:00:25:b5:30:00:4f
                               [mcvhes0105hba0]
    port-channel 10  510   0x860410  20:01:04:25:b5:3a:00:5f 20:01:00:25:b5:30:00:5f
                               [mcvhes0106hba0]
    port-channel 10  510   0x860417  20:01:04:25:b5:3a:00:2f 20:01:00:25:b5:30:00:2f
                               [mcvhes0107hba0]
    port-channel 10  510   0x860418  20:01:04:25:b5:3a:00:0f 20:01:00:25:b5:30:00:0f
                               [mcvhes0109hba0]
    port-channel 10  510   0x86041b  20:01:04:25:b5:3a:00:bf 20:01:00:25:b5:30:01:bf
                               [mcvhes0110hba0]
    port-channel 10  510   0x86041d  20:01:04:25:b5:3a:00:1f 20:01:00:25:b5:30:00:1f
                               [mcvhes0111hba0]
    port-channel 10  510   0x86041e  20:01:04:25:b5:3a:00:3f 20:01:00:25:b5:30:00:3f
                               [mcvhes0108hba0]
    port-channel 10  510   0x86041f  20:01:04:25:b5:3a:00:ff 20:01:00:25:b5:30:01:ff
                               [mcvhes0112hba0]
    port-channel 10  510   0x860423  20:01:04:25:b5:3a:00:df 20:01:00:25:b5:30:01:df
                               [mcvhes0113hba0]
    port-channel 10  510   0x860425  20:01:04:25:b5:3a:00:ef 20:01:00:25:b5:30:01:ef
                               [mcvhes0114hba0]
    port-channel 10  510   0x860426  20:01:04:25:b5:3a:00:cf 20:01:00:25:b5:30:01:cf
                               [mcvhes0115hba0]
    port-channel 10  510   0x860427  20:01:04:25:b5:3a:00:8e 20:01:00:25:b5:30:01:8f
                               [MCDBWS0200hba0]
    port-channel 10  510   0x860429  20:01:04:25:b5:3a:00:9e 20:01:00:25:b5:30:01:9f
                               [MCDBWS0201hba0]
    port-channel 10  510   0x86042a  20:01:04:25:b5:3a:00:7e 20:01:00:25:b5:30:01:7f
                               [mcvhes0118hba0]
    port-channel 10  510   0x86042b  20:01:04:25:b5:3a:00:af 20:01:00:25:b5:30:01:af
                               [mcvhes0116hba0]
    port-channel 10  510   0x86042c  20:01:04:25:b5:3a:00:6e 20:01:00:25:b5:30:01:6f
                               [mcvhes0117hba0]
    port-channel 10  510   0x86042d  20:01:04:25:b5:3a:00:4e 20:01:00:25:b5:30:01:4f
                               [mcvhes0119hba0]
    port-channel 10  510   0x86042e  20:01:04:25:b5:3a:00:5e 20:01:00:25:b5:30:01:5f
                               [mcvhes0120hba0]
    port-channel 10  510   0x860431  20:01:04:25:b5:3a:00:2e 20:01:00:25:b5:30:01:2f
                               [awotorprodsql01hba0]
    port-channel 10  510   0x860432  20:01:04:25:b5:3a:00:3e 20:01:00:25:b5:30:01:3f
                               [awotorprodsql02hba0]
    port-channel 10  510   0x860435  20:01:04:25:b5:3a:00:fe 20:01:00:25:b5:30:00:ef
                               [dbcactv01n3hba0]
    port-channel 10  510   0x860436  20:01:04:25:b5:3a:00:de 20:01:00:25:b5:30:00:bf
                               [dbcactv01n4hba0]
    port-channel 10  510   0x860439  20:01:04:25:b5:3a:00:ce 20:01:00:25:b5:30:00:8e
                               [mcvhes0123hba0]
    port-channel 10  510   0x86043a  20:01:04:25:b5:3a:00:be 20:01:00:25:b5:30:00:af
                               [mcvhes0122hba0]
    port-channel 10  510   0x86043c  20:01:04:25:b5:3a:00:ae 20:01:00:25:b5:30:00:9e
                               [mcvhes0124hba0]
    port-channel 10  510   0x860443  20:01:04:25:b5:3a:00:8d 20:01:00:25:b5:30:00:6e
                               [mcvhes0125hba0]
    port-channel 10  510   0x860445  20:01:04:25:b5:3a:00:ee 20:01:00:25:b5:30:00:cf
                               [mcvhes0121hba0]
    port-channel 10  510   0x860446  20:01:04:25:b5:3a:00:9d 20:01:00:25:b5:30:00:7e
                               [mcvhes0126hba0]
    port-channel 10  510   0x860447  20:01:04:25:b5:3a:00:6d 20:01:00:25:b5:30:00:4e
                               [mcvhes0127hba0]
    port-channel 10  510   0x860449  20:01:04:25:b5:3a:00:7d 20:01:00:25:b5:30:00:5e
                               [mcvhes0128hba0]

    I think what you do is F-Port trunking channeling !
    port-channel as a zone member ? I assume you will do pwwn based zoning; in which case the answer is NO !

Maybe you are looking for