Lacp port channel shows down on one 5k

I got one side of my lacp port channel down.
the topology is shown but the left side is showing down
20    Po20(SD)    Eth      LACP      Eth1/5(s)    Eth1/6(s) 
# sh int port-channel 20
port-channel20 is down (No operational members)
  Hardware: Port-Channel, address: 547f.eebb.644d (bia 547f.eebb.644d)
  Description: **To-VA-7004**
  MTU 1500 bytes, BW 100000 Kbit, DLY 10 usec
  reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA
  Port mode is trunk
  auto-duplex, 10 Gb/s
  Input flow-control is off, output flow-control is off
  Switchport monitor is off 
  EtherType is 0x8100 
  Members in this channel: Eth1/5, Eth1/6
  Last clearing of "show interface" counters never
  30 seconds input rate 80 bits/sec, 0 packets/sec
  30 seconds output rate 176 bits/sec, 0 packets/sec
  Load-Interval #2: 5 minute (300 seconds)
    input rate 112 bps, 0 pps; output rate 288 bps, 0 pps
  RX
    4286 unicast packets  785765 multicast packets  1493093 broadcast packets
    2283144 input packets  248607161 bytes
    13 jumbo packets  0 storm suppression bytes
    0 runts  0 giants  0 CRC  0 no buffer
    0 input error  0 short frame  0 overrun   0 underrun  0 ignored
    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
    0 input with dribble  0 input discard
    0 Rx pause
  TX
    0 unicast packets  3397636 multicast packets  0 broadcast packets
    3397636 output packets  399463036 bytes
    0 jumbo packets
    0 output errors  0 collision  0 deferred  0 late collision
    0 lost carrier  0 no carrier  0 babble 0 output discard
    0 Tx pause
  2 interface resets
sh run interface port-channel 20 membership 
!Command: show running-config interface port-channel20 membership
!Time: Mon Feb  2 23:04:37 2015
version 5.1(3)N2(1b)
interface port-channel20
  description **To-VA-7004**
  switchport mode trunk
  switchport trunk allowed vlan 1,200-202,251
interface Ethernet1/5
  description **TO-VA-7004-ETH3/45**
  switchport mode trunk
  switchport trunk allowed vlan 1,200-202,251
  channel-group 20 mode active
interface Ethernet1/6
  description **To-VA-7004-ETH4/46**
  switchport mode trunk
  switchport trunk allowed vlan 1,200-202,251
  channel-group 20 mode active
but on the right side everything is up, 
20    Po20(SU)    Eth      LACP      Eth1/5(P)    Eth1/6(P) 

It seems have a problem on interfaces => 20    Po20(SD)    Eth      LACP      Eth1/5(s)    Eth1/6(s) 
Can you share us the status about interfaces 1/5 - 6 & 3/45, 4/45 of 7k?
Do you have configured per Ethernet interfaces or on the Po ?

Similar Messages

  • LACP port-channel configs

    Hi,
    I currently have Nexus 1000v and vSphere 5.1 and want to convert my port-channel uplink port (ESX to Catalyst 3750 stack) from static to LACP; The configs below are what I have now, and I added in BOLD what I think I need to change on both my VSM and Catalyst 3750 stack to make LACP work. Can someone confirm if the configs below are right?
    Thanks you for your Help!
    conf t
    feature lacp
    port-profile type ethernet uplink
    vmware port-group
    feature lacp
    mtu 1500
    switchport mode trunk
    switchport trunk allowed vlan 10,988-989
    switchport trunk native vlan 900
    channel-group auto mode on
    no shutdown
    system vlan 10,988-989
    description uplink
    state enabled
    And here is what I have configured on my Cisco 3750 at the other end;
    interface Port-channel8
    description Etherchannel connection to ESX
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 900
    switchport trunk allowed vlan 10,988,989
    switchport mode trunk
    switchport nonegotiate
    spanning-tree portfast trunk
    interface GigabitEthernet3/0/24
    description 22 - nic2
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 900
    switchport trunk allowed vlan 10,988,989
    switchport mode trunk
    switchport nonegotiate
    channel-group 8 mode on (need to change to active)
    spanning-tree portfast trunk
    end
    interface GigabitEthernet2/0/24
    description 22 - nic3
    switchport trunk encapsulation dot1q
    switchport trunk native vlan 900
    switchport trunk allowed vlan 10,988,989
    switchport mode trunk
    switchport nonegotiate
    channel-group 8 mode on (need to change to active)
    spanning-tree portfast trunk
    end

    I would like to use LACP port channel instead of a static port channel, because LACP will shut down a link in case of a faulty nic (dead, driver issue, etc), instead of trying to send traffic through that link.  With static port channel, one side goes down (ESX NIC) the other side (3750) does not see the link go down and still tries to send traffic, instead of hashing the address to another link.

  • Customs alerts when a port-channel is down.

    Hi,
    I want to receive syslog alerts when a  port-channel is down, or when a interface from the port-channel is down  or if is possible to know when a neighbors is unreacheable or lost.
    Is  possible?? I have tried to configure Automated Actions in the tool  syslogs on RME (LMS 3.2) when a interface is down (LINK-*-3-UPDOWN:*  LINK-*-5-CHANGED:* LINK-*-5-UPDOWN:*), but I received alerts messages  from others interfaces when only I want the interfaces that form the  port-channels.
    Thanks,

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Well if it's the only remaining channel link, the port-channel goes down.  If not the only remaining channel link, the port-channel continues without it.  As you note, you lose bandwidth and I believe traffic will be rehashed across the remaining channel links, which can result in less optimal load distribution.
    Protocols like STP or a routing protocol shouldn't see a link outage or flap.

  • LACP port-channel down but Individual ports up

    I have setup an active LACP consisting of two members in each port-channel. As it is configured now the individual ports are operational but not participating as members of the LACP. Not finding any reference to exactly why this is. From what I can gather this may be related to the host configuration? 
    If anyone can enlighten me to such a situation it would be greatly appreciated. Would be even better if anyone had experience with the Oracle Database Appliance requirements for network configuration on the Cisco side.
    Group Port-       Type     Protocol  Member Ports
          Channel
    210   Po210(SD)   Eth      LACP      Eth107/1/11(I)  Eth108/1/12(I)
    211   Po211(SD)   Eth      LACP      Eth107/1/12(I)  Eth108/1/11(I)
    interface port-channel210
      description pdxodaprod-node0
      switchport access vlan 48
    interface Ethernet107/1/11
      description pdxodaprod-node0-net0
      switchport access vlan 48
      speed auto
      channel-group 210 mode active
    interface Ethernet108/1/12
      description pdxodaprod-node0-net1
      switchport access vlan 48
      speed auto
      channel-group 210 mode active
    interface port-channel211
      description pdxodaprod-node1
      switchport access vlan 48
    interface Ethernet108/1/11
      description pdxodaprod-node1-net0
      switchport access vlan 48
      speed auto
      channel-group 211 mode active
    interface Ethernet107/1/12
      description pdxodaprod-node1-net1
      switchport access vlan 48
      speed auto
      channel-group 211 mode active

    Hi,
    Putting the EtherChannel to the "on" mode will force the ports to become bundled unconditionally but the true problem, then, is truly seeing if it works. The Cisco switch will happily keep the ports bundled and will even transmit data over these ports but how do we know if Oracle is happy with that and does the same?
    Personally, I would not recommend using the "on" mode precisely because of lack of any indication that things are operating just as they should, unless it can be shown without doubts that Oracle runs without LACP and uses a static EtherChannel.
    Best regards,
    Peter

  • 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

  • LACP port channel between 6509 and Nexus 7K

    We are in the process of migrating from dual 6509's to dual 7010's.  We have moved our 5k/2K's behind the 7K and have layer 2 up between the 6509 and 7K.  This link is configured as a port channel with 2 1gig links using LACP.  The port channel is up and working and traffic is passing but it doesn't appear the load it equally distributed between the links.  Both the 7K and 6K are setup for src-dst-ip for the load balancing.  The links have been in place for over 12 hours and I would have expected them to "equal" out.  Has anyone had this issue in or is this to be expected?  For clarification there is not VPC inolved in this configuration it is simply a port-channel between one 6509 and a 7010.
    Thanks,
    Joe

    We are in the process of migrating from dual 6509's to dual 7010's.  We have moved our 5k/2K's behind the 7K and have layer 2 up between the 6509 and 7K.  This link is configured as a port channel with 2 1gig links using LACP.  The port channel is up and working and traffic is passing but it doesn't appear the load it equally distributed between the links.  Both the 7K and 6K are setup for src-dst-ip for the load balancing.  The links have been in place for over 12 hours and I would have expected them to "equal" out.  Has anyone had this issue in or is this to be expected?  For clarification there is not VPC inolved in this configuration it is simply a port-channel between one 6509 and a 7010.
    Thanks,
    Joe

  • Port channel issue

    Hello 
    I need help plz , i have 2X stacking Cisco core switch 3850 and access switches 2960X over the floors. I did the configuration but port channel still down , kindly check the below config:-
    3850
    interface Port-channel1
     switchport mode trunk
    inter gi1/0/1
    switchport trunk allowed vlan 85,90,95
     switchport mode trunk
     channel-group 1 mode active
    inter gi1/0/2
    switchport trunk allowed vlan 85,90,95
     switchport mode trunk
     channel-group 1 mode active
    2960
    interface Port-channel1
     switchport mode trunk
    inter Tengi1/0/1
    switchport trunk allowed vlan 85,90,95
     switchport mode trunk
     channel-group 1 mode active
    inter Tengi2/0/1
    switchport trunk allowed vlan 85,90,95
     switchport mode trunk
     channel-group 1 mode active
    The goal that i have access switch should connect to my two core switches using two uplinks and i need to merge the uplinks speed.
    Any idea

    Hello
    Kindly find the below 
    Core_switch#show etherchannel summary
    Number of channel-groups in use: 6
    Number of aggregators:           6
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    3      Po3(SD)         LACP      Gi1/0/5(I)  Gi2/0/5(I)
    ACCESS_Floor_3#show etherchannel summary
    Number of channel-groups in use: 1
    Number of aggregators:           1
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    3      Po3(SD)         LACP      Te1/0/1(D)  Te2/0/1(D)
    I need to connect my stack switches which located on 1st floor to core switch using two uplinks one uplink teng1/0/1 to 1st core port 1/0/5 in stack and other uplink 2/0/1 to 2nd core on the stack port. 2/0/5.
    thanks

  • Port Channel in Nexus

    Hi All,
    I have a scenario where I have two nexus 5596 as upstream and have vPC  in between. downstream is the server hooking to the upstrean both nexus  devices.
    On Both the Nexus switch the port channel is down and the VPC is also  down. The physical interfaces are up and passing traffic to the server.
    My understanding is if the server NIC's are teamed, even the switches should also have the portchannle to work properly.
    But since portchannel and vpc both are down in both the switches
    1. how the switch is passing traffic.
    2. I checked the configs for portchannel formation on phy ports which looks good to me still po is down. Why?
    3. I understand as port channel is down so vPC is down ( correct me if I am wrong).
    I have attached the diagram & below are the logs for ur reference:
    The output on Nexus5596 2 device is same as on Nexus5596 1
    Nexus5596 1#Sh vpc
    Legend:
                    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id                   : 106
    Peer status                     : peer adjacency formed ok
    vPC keep-alive status           : peer is alive
    Configuration consistency status: success
    Per-vlan consistency status     : success
    Type-2 consistency status       : success
    vPC role                        : primary
    Number of vPCs configured       : 29
    Peer Gateway                    : Disabled
    Dual-active excluded VLANs      : -
    Graceful Consistency Check      : Enabled
    vPC Peer-link status
    id   Port   Status Active vlans
    1    Po4    up     1-2,713-718,999
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    9      Po9         up     success     success                    2,713-718
    701    Po701       down*  success     success                    -
    702    Po702       down*  success     success                    -
    Nexus5596 1# sh port-channel su
    Group Port-       Type     Protocol  Member Ports
          Channel
    4     Po4(SU)     Eth      LACP      Eth1/27(P)   Eth1/28(P)
    9     Po9(SU)     Eth      LACP      Eth1/29(P)   Eth1/30(P)   Eth1/31(P)
                                                        Eth1/32(P)
    701   Po701(SD)   Eth      LACP      Eth1/1(I)
    702   Po702(SD)   Eth      LACP      Eth1/2(I)
    Nexus5596 1#sh run int e1/1
    interface Ethernet1/1
      description snrkdc1285_1/0
      switchport mode trunk
      switchport trunk native vlan 713
      switchport trunk allowed vlan 713-718
      spanning-tree port type edge trunk
      no snmp trap link-status
      channel-group 701 mode active
    Nexus5596 1# sh int e1/1 status
    Port          Name               Status    Vlan      Duplex  Speed   Type
    Eth1/1        snrkdc1285_1/0     connected trunk     full    10G     10Gbase-SR
    Thanks,
    Sagar

    Reza - My bad I mistakenly mentioned e1/10 in diagram but it is e1/1 for po701
    Since these are L2 switches SH IP INT BR shows only mgmt Ip
    Please find the requested outputs as below.
    nexus5596 1#sh run int po701
    interface port-channel701
      description snrkdc1285
      switchport mode trunk
      switchport trunk native vlan 713
      switchport trunk allowed vlan 713-718
      spanning-tree port type edge trunk
      speed 10000
      no snmp trap link-status
      vpc 701
    nexus5596 2# sh run int po701
    interface port-channel701
      description snrkdc1285
      switchport mode trunk
      switchport trunk native vlan 713
      switchport trunk allowed vlan 713-718
      spanning-tree port type edge trunk
      speed 10000
      no snmp trap link-status
      vpc 701
    nexus5596 1#sh int br
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        713     eth  trunk  up      none                        10G(D) --
    Eth1/2        713     eth  trunk  up      none                        10G(D) --
    Port-channel VLAN    Type Mode   Status  Reason                    Speed   Protocol
    Interface
    Po4          1       eth  trunk  up      none                       a-10G(D)  lacp
    Po9          2       eth  trunk  up      none                       a-10G(D)  lacp
    Po701        713     eth  trunk  down    No operational members       10G(D)  lacp
    Po702        713     eth  trunk  down    No operational members       10G(D)  lacp
    nexus5596 2#sh int br
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        713     eth  trunk  up      none                        10G(D) --
    Eth1/2        713     eth  trunk  up      none                        10G(D) --
    Port-channel VLAN    Type Mode   Status  Reason                    Speed   Protocol
    Interface
    Po4          1       eth  trunk  up      none                       a-10G(D)  lacp
    Po9          2       eth  trunk  up      none                       a-10G(D)  lacp
    Po701        713     eth  trunk  down    No operational members       10G(D)  lacp
    Po702        713     eth  trunk  down    No operational members       10G(D)  lacp

  • OSPF load balancing across multiple port channels

    I have googled/searched for this everywhere but haven't been able to find a solution. Forgive me if I leave something out but I will try to convey all relevant information. Hopefully someone can provide some insight and many thanks in advance.
    I have three switches (A, B, and C) that are all running OSPF and LACP port channelling among themselves on a production network. Each port channel interface contains two physical interfaces and trunks a single vlan (so a vlan connecting each switch over a port channel). OSPF is running on each vlan interface.
    Switch A - ME3600
    Switch B - 3550
    Switch C - 3560G
    This is just a small part of a much larger topology. This part forms a triangle, if you will, where A is the source and C is the destination. A and C connect directly via a port channel and are OSPF neighbors. A and B connect directly via a port channel and are OSPF neighbors. B and C connect directly via a port channel and are OSPF neighbors. Currently, all traffic from A to C traverses B. I would like to load balance traffic sourced from A with a destination of C on the direct link and on the links through B. If all traffic is passed through B, traffic is evenly split on the two interfaces on the port channel. If all traffic is pushed onto the direct A-C link, traffic is evenly balanced on the two interfaces on that port channel. If OSPF load balancing is configured on the two vlans from A (so A-C and A-B), the traffic is divided to each port channel but only one port on each port channel is utilized while the other one passes nothing. So half of each port channel remains unused. The port channel on B-C continues to load balance, evenly splitting the traffic received from half of the port channel from A.
    A and C port channel load balancing is configured for src-dst-ip. B is a 3550 and does not have this option, so it is set to src-mac.
    Relevant configuration:
    Switch A:
    interface Port-channel1
    description Link to B
     port-type nni
     switchport trunk allowed vlan 11
     switchport mode trunk
    interface Vlan11
     ip address x.x.x.134 255.255.255.254
    interface Port-channel3
    description Link to C
     port-type nni
     switchport trunk allowed vlan 10
     switchport mode trunk
    interface Vlan10
     ip address x.x.x.152 255.255.255.254
    Switch B:
    interface Port-channel1
     description Link to A
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 11
     switchport mode trunk
    interface Vlan11
     ip address x.x.x.135 255.255.255.254
    interface Port-channel2
     description Link to C
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 12
     switchport mode trunk
    interface Vlan12
     ip address x.x.x.186 255.255.255.254
    Switch C:
    interface Port-channel1
     description Link to B
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 12
     switchport mode trunk
    interface Vlan12
     ip address x.x.x.187 255.255.255.254
    interface Port-channel3
     description Link to A
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10
     switchport mode trunk
    interface Vlan10
     ip address x.x.x.153 255.255.255.254

    This is more FYI. 10.82.4.0/24 is a subnet on switch C. The path to it is split across vlans 10 and 11 but once it hits the port channel interfaces only one side of each is chosen. I'd like to avoid creating more vlan interfaces but right now that appears to be the only way to load balance equally across the four interfaces out of switch A.
    ME3600#sh ip route 10.82.4.0
    Routing entry for 10.82.4.0/24
      Known via "ospf 1", distance 110, metric 154, type extern 1
      Last update from x.x.x.153 on Vlan10, 01:20:46 ago
      Routing Descriptor Blocks:
        x.x.x.153, from 10.82.15.1, 01:20:46 ago, via Vlan10
          Route metric is 154, traffic share count is 1
      * x.x.x.135, from 10.82.15.1, 01:20:46 ago, via Vlan11
          Route metric is 154, traffic share count is 1
    ME3600#sh ip cef 10.82.4.0
    10.82.4.0/24
      nexthop x.x.x.135 Vlan11
      nexthop x.x.x.153 Vlan10
    ME3600#sh ip cef 10.82.4.0 internal       
    10.82.4.0/24, epoch 0, RIB[I], refcount 5, per-destination sharing
    sources: RIB 
    ifnums:
    Vlan10(1157): x.x.x.153
    Vlan11(1192): x.x.x.135
    path 093DBC20, path list 0937412C, share 1/1, type attached nexthop, for IPv4
    nexthop x.x.x.135 Vlan11, adjacency IP adj out of Vlan11, addr x.x.x.135 08EE7560
    path 093DC204, path list 0937412C, share 1/1, type attached nexthop, for IPv4
    nexthop x.x.x.153 Vlan10, adjacency IP adj out of Vlan10, addr x.x.x.153 093A4E60
    output chain:
    loadinfo 088225C0, per-session, 2 choices, flags 0003, 88 locks
    flags: Per-session, for-rx-IPv4
    16 hash buckets             
    < 0 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 1 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 2 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 3 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 4 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 5 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 6 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 7 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 8 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 9 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <10 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <11 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <12 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <13 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <14 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <15 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    Subblocks:                                                                                  
    None

  • 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

  • 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

  • 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

  • Nexus 5k port channel

    I want to create a port channel on my nexus switch which will be connected to my server.
    will someone please share with me the configuration for the same ?

    Hi,
    From server side create LACP port-channel and same from switch end.
    Nexus-SW
    =======
    interface Ethernet1/1-2
      description [connection to SRV-01]
      switchport
      switchport access vlan 10
      channel-group 20 mode active
      no shutdown
    interface port-channel20
      description [connection to SRV-01]
      switchport
      vpc 20
      switchport access vlan 10

  • Fiber Port Channel

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

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

Maybe you are looking for