How to troubleshooting port channel in N7K

 i find N5K
http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116199-technote-stp-00.html
i notice distribution switch has root  guard block log
does it mean that looping has occured yesterday?
i use command below do not have yesterday record
show spanning-tree internal event-history tree 1 brief | in "2015:03:15 10"
first core is root switch
now port channel shutdown in first core and use port channel in second core. How can i see which problem has occurred in port channel ?
how to know which port has problem ?
how to know which vlan caused the problem ?
we notice one of access switch has lost config, will it affect the distribution layer switch?
i remember that yesterday i just get log with filezilla after configure notebook same vlan and same network with the testing access switch

Not sure if youre after the portchannel bandwidth or port-channel speed... If you really want to get an insight on the bandwidth usage, get SNMP on both sides, actively monitor the port channel and interfaces (real time by frequent polling)
And you could get two endpoints @ 10 gb nics that are bundled, then 'thrash' the link, end to end. I use iperf, you could use big ftp transfers to test and see what performance is. You'll get the rate / speed in which the links are operating 'end to end'
It may mean that the ports are @10gb full duplex, but the overall bandwidth is 20gb
Sent from Cisco Technical Support iPhone App

Similar Messages

  • Configuring port-channel on N7K

    Hi there,
    I am trying to build a port-channel from N7K-01 to N7K-02 using a breakout cables (40G interface from N7K-01 to 4x10G interfaces on N7K-02). it didn't work
    is this require a special configuration??? because I have done port-channel configuration between two 40G interfaces and it works.
    appreciate your valuable support if possible to share the needed configuration to accomplish this.
    thanks,
    regards,
    Haitham.

    Hi,
    when I do it directly between cisco ASR9k, the 10g interfaces are up with lights but 40G side is red not up.
    between cisco N7Ks, no lights from both sides. between N7Ks cable is going to patch-panel and then to other nexus.
    thanks,

  • Port-channel Problem between Fabric Interconnect and N7K vPC

    Dear all,
    I have a problem with Port-channel Uplink between Fabric Interconnect with N7K using vPC
    This is my network topology for UCS Deployment
    In N7K I has configured vPC for red link and green link, at Fabric Interconnect A I has configured Port-Channel with member is Port 1 and Port 2, uplink is red link. At Fabric Interconnect B, I has configured Port-Channel with member is Port 1 and Port 2, uplink is green link.
    The show interface port-channel on N7K is good, every port-channel is up and have all member. But At Fabric Interconnnect, when I see on UCS Manager, the status of Port-Channel on Fabic A and Fabric B is fault with Additional Info: No operational member. Although all link is link up and I has status of Port-Channel is enable on UCS Manager. When I see the Properties of Port 1, Port 2 on Port-channel, I see the membership status is : individual. This mean port-channel is not up and no membership in this configuration. I want to using port-channel for load balance and plus more bandwidth for uplink to 20Gig. I don't understand why ?
    Please help me resolve this problem, I has send the capture screen of UCS Manager when I show status of Port-channel and Port-member in port-channel in attach items.
    Anyone can help me to resolve this, thanks you very much. Please reference attach items for more detail about fault.
    Thanks,
    Trung.

    Thanks Matthew very much,
    I has resolved this problem. The reason of problem is miss match protocol of port-channel between N7K and Fabric Interconnect. The Fabric Interconnect always use LACP protocol, but N7K using Port-channel mode on, that why the port-channel failed. I has configured LACP for port-channel in N7K, it has resolved the problems.
    Thanks,
    Trung.

  • 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])

  • 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

  • N7K Port Channel Layer 3 VLAN Question

    I have 2 N7K switches and would like to connect them via port channel and put the channel in VLAN 101. I have the following config, does it make sense? Thanks in advance!
    interface eth 3/1
    switchport
    channel-group 101 mode active
    interface eth 3/2
    switchport
    channel-group 101 mode active
    interface port-channel 101
    switchport
    switchport mode access
    switchport access vlan 10
    spanning-tree network type edge
    interface vlan 10
    ip address 10.1.1.1/24

    Could be something like this in the both sides (if the port numbers match):
    conf t
    feature lacp
    feature interface-vlan
    interface eth 3/1
    switchport
    channel-group 101 mode active
    interface eth 3/2
    switchport
    channel-group 101 mode active
    interface port-channel 101
    switchport
    switchport mode access
    switchport access vlan 101
    spanning-tree port type network
    interface vlan 101
    ip address 10.1.1.1/24
    no shut
    end
    vlan 101
    end
    *(This ip address will be available in only one box, you can use a FHRP as well, to increase the level of reachability)

  • 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

  • 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

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

  • Where/how to troubleshoot external gateway and internal connection brokers etc.??????

    We have gateway.domain.org as our external/internal gateway server.
    It goes from gateway.domain.org to rdbroker.domain.local, rdbroker is the DNS address for two connection broker servers.
    After this it should set up the connection and create a remote desktop to one of the RDS host servers in the RDS host farm.
    Sometimes this works, sometimes it doesn't -- for different user accounts and different computers.
    How to troubleshoot this??
    We know the firewall rules for DMZ etc. etc. are properly configured because everything IS observed to work, just not all the time consistently. We get errors about cannot contact the computer, cannot establish remote desktop connection...
    Thank you, Tom

    Hi Tom,
    Firstly, you need to recheck the DNS entry is well setup for your case. Are you using DNS RR for Load balancing the server or 3rd party load balancer? Have you setup the proper certificate for your case?
    Please check whether required ports is opened? We need to open TCP port 443 and UDP port 3391 and forward them to your RD Gateway server. Also need to specify the external FQDN of your RD Gateway server in deployment properties under RDS server manager. If
    you have RDWeb and RDG on the same server this would be the same FQDN that your users will use for RDWeb. Please see whether you have properly configured RD RAP and RD CAP policy. 
    You can go through beneath article for more details.
    Step by Step Windows 2012 R2 Remote Desktop Services – Part 3
    https://msfreaks.wordpress.com/2013/12/26/windows-2012-r2-remote-desktop-services-part-3/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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

  • Dlsw using port channel

    I have 2 dlsw router at head quater office, named dlswA and dlswB.
    From branches router, dlswA is a primary peer and dlswB is a backup peer.
    Both dlswA and B have 2 fast ethernet interfaces.
    The current configuration of dlswA and dlswB are 1 port as IP port and other port as sna/bridge port.
    With this configuration the problem is when SNA port at dlswA problem, then dlsw circuit will have the problem, because dlsw peer from branches still connected to dlswA.
    if I configure 2 fast ethernet port become a port channel. And configure IP and bridge group at port channel interface (IP and SNA at the same interfaces), so when the port channel is down, then branches will connect to dlswB as a backup peer
    Are the port channel configuration will solve the problem ? How about the stability of this configuration?

    Thank Matthias for your reply.
    Both of head end routers are on the same vlan and the host is using same mac address.
    As far as i know if from branch have 2 active peer with cost setup, there will loops posibility because both head end routers are using ethernet with same vlan and same host mac address.
    I test the port channel within my LAB using netbios, seem works as expected. when single port at port channel down, branch circuit still remain at dlswA router, when all port channel member down, the branch peering move to dlswB.
    Here are the config:
    hostname dlswA
    dlsw local-peer peer-id 192.168.255.1 promiscuous
    dlsw bridge-group 1
    interface Port-channel10
    ip address 192.168.255.1 255.255.255.248
    bridge-group 1
    interface FastEthernet0/0
    no ip address
    duplex auto
    speed auto
    channel-group 10
    interface FastEthernet0/1
    no ip address
    duplex auto
    speed auto
    channel-group 10
    end
    hostname dlswB
    dlsw local-peer peer-id 192.168.255.10 promiscuous
    dlsw bridge-group 1
    interface Port-channel11
    ip address 192.168.255.10 255.255.255.248
    bridge-group 1
    interface FastEthernet0/0
    no ip address
    duplex auto
    speed auto
    channel-group 11
    interface FastEthernet0/1
    no ip address
    duplex auto
    speed auto
    channel-group 11
    end
    Hostname Branch
    dlsw local-peer peer-id 172.16.0.1
    dlsw remote-peer 0 tcp 192.168.255.1
    dlsw remote-peer 0 tcp 192.168.255.10 backup-peer 192.168.255.1 linger 0
    dlsw bridge-group 1
    interface Loopback0
    ip address 172.16.0.1 255.255.255.255
    interface FastEthernet0/1
    no ip address
    duplex auto
    speed auto
    bridge-group 1
    But I'm not sure this scenario will work for sna application like ATM machine, and SNA SAA gateway.
    Please kindly advised, Is there any alternatif ?

  • MDS switch: DCNM: Is there a way to monitor the traffic on every port within a port channel using DCNM?

    I am trying to monitor the load on an 8 port ISL between 2 MDS FC switches, on DCNM. 
    Since it is a plain trunk link, I am able to monitor the stats of every ISL port individually. 
    My question is, since port channel shows up as a single interface on DCNM, is there  a way to monitor the per port utilization in that port channel?

    Thanks for the update! If anyone else has the same question, the answer is that in order to extract the bus log information in the TDMS file, you should use the DIAdem Bus Log Converter tool. It is expected (though confusing) that the file looks mostly empty in the Data Portal until you use this tool to extract the information.
    Also, this is a fantastic tutorial from a very bright engineer on how to correlate data from multiple sources, such as raw frame files, in DIAdem. Highly recommended reading. It also has some data on the bus log converter.
    Jarrod S.
    National Instruments

  • 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

  • WLC LAG Mode and Port Channel

    So I was reading the controller best practices and got this:
    When you use LAG, the controller relies on the switch for the load balancing decisions on traffic that come from the network. It expects that traffic that belongs to an AP always enters on the same port. Use only ip-src or ip-src ip-dst load balancing options in the switch EtherChannel configuration. Some switch models might use unsupported load balancing mechanisms by default, so it is important to verify.
    This is how to verify the EtherChannel load balancing mechanism:
    switch#show etherchannel load-balance
    EtherChannel Load-Balancing Configuration:
    src-dst-ip
    EtherChannel Load-Balancing Addresses Used Per-Protocol:
    Non-IP: Source XOR Destination MAC address
    IPv4: Source XOR Destination IP address
    IPv6: Source XOR Destination IP address
    This is how to change the switch configuration (IOS):
    switch(config)#port-channel load-balance src-dst-ip
    Now Cisco switches by default will do src-mac.  If I make this change obviously this would be a global change.  I don't believe it should cause any performance issues but wanted to get some expert opinions on this.  Switches my controller will be connected to will also have two routers connected as well via Port Channel.
    I'm trying to understand the reasoning behind this.

    I've never seen that command cause any issues in any deployment I've worked on.
    HTH,
    Steve

Maybe you are looking for