Etherchannel

Hello:) We are considering setting up etherchannel between two cisco 3550 switches using a wireless ptp connection that manages about 20mbit each..
How will this work? I guess the switch wont know what speed the link is and will asume it's a 100mbit on each ptp connection.. Will the bandwidh setting on the port change this? By that i mean setting the bandwidth on the port to 20mbit..
Or will I(and that's what i think) get only a redundant connection by doing this?
Hope somebody knows :)
Jo Christian

I don't know if this will work or not , it's a pretty unconventional setup , best bet is to set it up in a lab situation to see if the etherchannel will come up . If it does come up don't know how stable it will be across a wireless link.

Similar Messages

Link outage in Etherchannel causes interface down and failover Secondary Faild

Hi,
I have configured port-channel Firewall ASA5515-X and stacking switch WS-3750X. Also firewall configured as failover mode. Problem is that my active firewall connected switch port show green and working but standby firewall connected switch port shows orange color. When i inpute show failover command on firewall, secondary is faild. Please assist. Here is the below show command.
mdbl-int-fw-01# sho port-channel 10
Ports: 2   Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
mdbl-int-fw-01# sho interface port-channel 10
Interface Port-channel10 "inside", is up, line protocol is up
Hardware is EtherChannel/LACP, BW 2000 Mbps, DLY 10 usec
        Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
        Input flow control is unsupported, output flow control is off
        Description: *** Connected to CORE-SW ***
        MAC address 4c00.821d.511f, MTU 1500
        IP address 10.98.8.97, subnet mask 255.255.255.248
Traffic Statistics for "inside":
        56859 packets input, 3419130 bytes
        148709 packets output, 16063580 bytes
        56858 packets dropped
      1 minute input rate 0 pkts/sec, 46 bytes/sec
      1 minute output rate 2 pkts/sec, 216 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 0 pkts/sec, 46 bytes/sec
      5 minute output rate 2 pkts/sec, 216 bytes/sec
      5 minute drop rate, 0 pkts/sec
Members in this channel:
      Active:   Gi0/1 Gi0/2
mdbl-int-fw-01# sho port
mdbl-int-fw-01# sho port-channel sum
mdbl-int-fw-01# sho port-channel summary
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        U - in use      N - not in use, no aggregation/nameif
        M - not in use, no aggregation due to minimum links not met
        w - waiting to be aggregated
Number of channel-groups in use: 1
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
10     Po10(U)           LACP    Gi0/1(P)   Gi0/2(P)
mdbl-int-fw-01#
mdbl-int-fw-01# sho port-channel ?
<1-48>    Channel group number
brief     Brief information
detail    Detail information
port      Port information
protocol protocol enabled
summary   One-line summary per channel-group
|         Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel bri
mdbl-int-fw-01# sho port-channel brief
                Channel-group listing:
Group: 10
Ports: 2   Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
mdbl-int-fw-01# sho port-channel ?
<1-48>    Channel group number
brief     Brief information
detail    Detail information
port      Port information
protocol protocol enabled
summary   One-line summary per channel-group
|         Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel pro
mdbl-int-fw-01# sho port-channel protocol
                Channel-group listing:
Group: 10
Protocol: LACP
mdbl-int-fw-01# sho port-channel ?
<1-48>    Channel group number
brief     Brief information
detail    Detail information
port      Port information
protocol protocol enabled
summary   One-line summary per channel-group
|         Output modifiers
<cr>
mdbl-int-fw-01# sho port-channel det
mdbl-int-fw-01# sho port-channel detail
                Channel-group listing:
Group: 10
Ports: 2   Maxports = 16
Port-channels: 1 Max Port-channels = 48
Protocol: LACP/ active
Minimum Links: 1
Maximum Bundle: 8
Load balance: src-dst-ip
                Ports in the group:
Port: Gi0/1
Port state    = bndl
Channel group =   10        Mode = LACP/ active
Port-channel = Po10
Flags: S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
        A - Device is in active mode.        P - Device is in passive mode.
Local information:
                             LACP port     Admin     Oper    Port        Port
Port      Flags   State      Priority      Key       Key     Number      State
Gi0/1     SA      bndl       32768         0xa       0xa     0x2         0x3d
Partner's information:
          Partner Partner    LACP Partner Partner   Partner Partner     Partner
Port      Flags   State      Port Priority Admin Key Oper Key Port Number Port State
Gi0/1     SA      bndl       32768         0x0       0xa      0x118       0x3d
Port: Gi0/2
Port state    = bndl
Channel group =   10        Mode = LACP/ active
Port-channel = Po10
Flags: S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
        A - Device is in active mode.        P - Device is in passive mode.
Local information:
                             LACP port     Admin     Oper    Port        Port
Port      Flags   State      Priority      Key       Key     Number      State
Gi0/2     SA      bndl       32768         0xa       0xa     0x3         0x3d
Partner's information:
          Partner Partner    LACP Partner Partner   Partner Partner     Partner
Port      Flags   State      Port Priority Admin Key Oper Key Port Number Port State
Gi0/2     SA      bndl       32768         0x0       0xa      0x119       0x3d
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho port-channel ?
<1-48>    Channel group number
brief     Brief information
detail    Detail information
port      Port information
protocol protocol enabled
summary   One-line summary per channel-group
|         Output modifiers
<cr>
mdbl-int-fw-01# sho fail
mdbl-int-fw-01# sho failover st
mdbl-int-fw-01# sho failover state
               State          Last Failure Reason      Date/Time
This host -   Primary
               Active         None
Other host -   Secondary
               Failed         Ifc Failure              22:03:03 UTC Jan 8 2014
                              outside: No Link
                              dmz: No Link
                              mgt: No Link
                              inside: No Link
====Configuration State===
        Sync Done
====Communication State===
        Mac set
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet0/3 (up)
Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
Interface Poll frequency 500 milliseconds, holdtime 5 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
failover replication http
Version: Ours 8.6(1)2, Mate 8.6(1)2
Last Failover at: 02:16:48 UTC Jan 8 2014
        This host: Primary - Active
                Active time: 74479 (sec)
                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                  Interface outside (118.179.139.4): No Link (Waiting)
                  Interface dmz (10.98.56.3): No Link (Waiting)
                  Interface mgt (10.10.11.1): Unknown (Waiting)
                  Interface inside (10.98.8.97): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                  IPS, 7.1(4)E4, Up
        Other host: Secondary - Failed
                Active time: 0 (sec)
                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                  Interface outside (118.179.139.6): No Link (Waiting)
                  Interface dmz (10.98.56.2): No Link (Waiting)
                  Interface mgt (0.0.0.0): No Link (Waiting)
                  Interface inside (10.98.8.98): No Link (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                  IPS, 7.1(4)E4, Up
Stateful Failover Logical Update Statistics
        Link : failover GigabitEthernet0/3 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         12665      0          9929       0
        sys cmd         9929       0          9929       0
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        0          0          0          0
        UDP conn        0          0          0          0
        ARP tbl         2735       0          0          0
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKEv1 SA    0          0          0          0
        VPN IKEv1 P2    0          0          0          0
        VPN IKEv2 SA    0          0          0          0
        VPN IKEv2 P2    0          0          0          0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Route Session   0          0          0          0
        User-Identity   1          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       7       9930
        Xmit Q:         0       30      99581
mdbl-int-fw-01#
mdbl-int-fw-01#
mdbl-int-fw-01# sho failover state
               State          Last Failure Reason      Date/Time
This host -   Primary
               Active         None
Other host -   Secondary
               Failed         Ifc Failure              22:03:03 UTC Jan 8 2014
                              outside: No Link
                              dmz: No Link
                              mgt: No Link
                              inside: No Link
====Configuration State===
        Sync Done
====Communication State===
        Mac set
mdbl-int-fw-01# sho failover ?
descriptor Show failover interface descriptors. Two numbers are shown for
              each interface. When exchanging information regarding a
              particular interface, this unit uses the first number in messages
              it sends to its peer. And it expects the second number in
              messages it receives from its peer. For trouble shooting, collect
              the show output from both units and verify that the numbers
              match.
exec        Show failover command execution information
history     Show failover switching history
interface   Show failover command interface information
state       Show failover internal state information
statistics Show failover command interface statistics information
|           Output modifiers
<cr>
mdbl-int-fw-01# sho failover inter
mdbl-int-fw-01# sho failover interface
        interface failover GigabitEthernet0/3
                System IP Address: 10.98.8.89 255.255.255.248
                My IP Address    : 10.98.8.89
                Other IP Address : 10.98.8.90
mdbl-int-fw-01# sho failover stati
mdbl-int-fw-01# sho failover statistics
        tx:995725
        rx:980617
mdbl-int-fw-01# sho failover hi
mdbl-int-fw-01# sho failover history
==========================================================================
From State                 To State                   Reason
==========================================================================
02:16:40 UTC Jan 8 2014
Not Detected               Negotiation                No Error
02:16:48 UTC Jan 8 2014
Negotiation                Just Active                No Active unit found
02:16:48 UTC Jan 8 2014
Just Active                Active Drain               No Active unit found
02:16:48 UTC Jan 8 2014
Active Drain               Active Applying Config     No Active unit found
02:16:48 UTC Jan 8 2014
Active Applying Config     Active Config Applied      No Active unit found
02:16:48 UTC Jan 8 2014
Active Config Applied      Active                     No Active unit found
==========================================================================
mdbl-int-fw-01# sho failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet0/3 (up)
Unit Poll frequency 200 milliseconds, holdtime 800 milliseconds
Interface Poll frequency 500 milliseconds, holdtime 5 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
failover replication http
Version: Ours 8.6(1)2, Mate 8.6(1)2
Last Failover at: 02:16:48 UTC Jan 8 2014
        This host: Primary - Active
                Active time: 74554 (sec)
                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                  Interface outside (118.179.139.4): No Link (Waiting)
                  Interface dmz (10.98.56.3): No Link (Waiting)
                  Interface mgt (10.10.11.1): Unknown (Waiting)
                  Interface inside (10.98.8.97): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                  IPS, 7.1(4)E4, Up
        Other host: Secondary - Failed
                Active time: 0 (sec)
                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)2) status (Up Sys)
                  Interface outside (118.179.139.6): No Link (Waiting)
                  Interface dmz (10.98.56.2): No Link (Waiting)
                  Interface mgt (0.0.0.0): No Link (Waiting)
                  Interface inside (10.98.8.98): No Link (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/7.1(4)E4) status (Up/Up)
                  IPS, 7.1(4)E4, Up
Stateful Failover Logical Update Statistics
        Link : failover GigabitEthernet0/3 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         12676      0          9938       0
        sys cmd         9938       0          9938       0
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        0          0          0          0
        UDP conn        0          0          0          0
        ARP tbl         2737       0          0          0
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKEv1 SA    0          0          0          0
        VPN IKEv1 P2    0          0          0          0
        VPN IKEv2 SA    0          0          0          0
        VPN IKEv2 P2    0          0          0          0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Route Session   0          0          0          0
        User-Identity   1          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       7       9940
        Xmit Q:         0       30      99677

Hi Ganesan,
I am proposing a design like this. You can have the STP in pvst mode and have a different priority set for the core switch to make it core a as root bridge. There is nothing wrong with your design you have made you core switch which will be physically down to your firewall... but in real it comes on the top of your firewall as well... But spanning tree conf should be done properly to achieve this... I have proposed my design which is pretty simple but easy for troubleshoot....
You can have your firewalls connected to core switch on the down and can directly connected to router on outside... always core a -->py fw--rtra will be the primary path... if anything goes wrong then secondary line will come in to picture....
make sure that your hsrp will have high priority to ur core a vlan conf for the access switches.....
Please do rate for the helpful posts.
By
Karthik

Etherchannel showing down (SD) and ports are in "I" stand alone state

Hi,
Netapp server is connected to switch 6500 via trunk.
I configured a portchannel but it showing as down.take a look ar below output..
interface Port-channel248
description Netapp-server-1 po248
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 903
switchport mode trunk
switchport nonegotiate
no ip address
no shut
interface GigabitEthernet3/33
description server-1
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 903
switchport mode trunk
switchport nonegotiate
no ip address
speed 1000
udld port aggressive
spanning-tree portfast
channel-group 248 mode active
no shut
interface GigabitEthernet4/33
description cnndcfasp002a-e5d
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 903
switchport mode trunk
switchport nonegotiate
no ip address
speed 1000
udld port aggressive
spanning-tree portfast
channel-group 248 mode active
no shut
Switch-6500#sh etherchannel summary
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        M - not in use, minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
Number of channel-groups in use: 5
Number of aggregators:           5
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
248    Po248(SD)       LACP      Gi3/33(I) Gi4/33(I)
#sh etherchannel detail
Group: 248
Group state = L2
Ports: 2   Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol:   LACP
Minimum Links: 0
                Ports in the group:
Port: Gi3/33
Port state    = Up Sngl-port-Bndl Mstr Not-in-Bndl
Channel group = 248         Mode = Active      Gcchange = -
Port-channel = null        GC   =   -         Pseudo port-channel = Po248
Port index    = 0           Load = 0x00        Protocol =   LACP
Flags: S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
        A - Device is in active mode.        P - Device is in passive mode.
Local information:
                            LACP port     Admin     Oper    Port        Port
Port      Flags   State     Priority      Key       Key     Number      State
Gi3/33    SA      indep     32768         0xF8      0xF8    0x321       0x7D
Age of the port in the current state: 0d:02h:04m:58s
Port: Gi4/33
Port state    = Up Sngl-port-Bndl Mstr Not-in-Bndl
Channel group = 248         Mode = Active      Gcchange = -
Port-channel = null        GC   =   -         Pseudo port-channel = Po248
Port index    = 0           Load = 0x00        Protocol =   LACP
Flags: S - Device is sending Slow LACPDUs   F - Device is sending fast LACPDUs.
        A - Device is in active mode.        P - Device is in passive mode.
Local information:
                            LACP port     Admin     Oper    Port        Port
Port      Flags   State     Priority      Key       Key     Number      State
Gi4/33    SA      indep     32768         0xF8      0xF8    0x421       0x7D
Age of the port in the current state: 0d:02h:04m:58s
                Port-channels in the group:
Port-channel: Po248    (Primary Aggregator)
Age of the Port-channel   = 7d:16h:30m:16s
Logical slot/port   = 14/3          Number of ports = 0
Port state          = Port-channel Ag-Not-Inuse
Protocol            =   LACP
Any one please let me know what is the issue here...
Thanks
Gautham

Exactly, the 6500 config is fine, probably the NETAPP is not active or passive and it's just ON that won't work
show lacp 248 neighbor will show if you have a neighbor and if the LACP id is the same on both ports
Core1#sh lacp 2 neighbor
Flags: S - Device is requesting Slow LACPDUs
        F - Device is requesting Fast LACPDUs
        A - Device is in Active mode       P - Device is in Passive mode
Channel group 2 neighbors
Partner's information:
          Partner Partner   LACP Partner Partner   Partner Partner     Partner
Port      Flags   State     Port Priority Admin Key Oper Key Port Number Port State
Gi1/7/10 SA      bndl      32768         0x0       0x1      0x11A       0x3D
Gi2/7/10 SA      bndl      32768         0x0       0x1      0x31D       0x3D
cheers

Fundamental question on etherchannel hashing.

Folks,
I had some very basic questions on the way hashing takes place on Cisco switches connected to each other over a port channel.
Considering that 2 links are used between the switch, namely port Gi 0/1 and Gi 0/2.
1) By default I understand that this could be a L2 etherchannel or L3 etherchannel, the default mode of hashing is still the Source and destination MAC id, am I correct?
2) So now if the source IP of 1.1.1.1 needs to reach to 1.1.1.2 how would the hashing calculation take place? Again I understand that this is on the basis of the last 3 bits from the IP address field. 001 and 010 come to 011 which is 3. So based on the number of ports it will select which interface to assign.
I still do not understand what has the below output got to do with the selection:
Core-01#sh interfaces port-channel 40 etherchannel
Age of the Port-channel   = 204d:07h:40m:10s
Logical slot/port   = 14/3          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Passive port list   = Te1/4 Te2/4
Port state          = Port-channel L3-Ag Ag-Inuse
Protocol            =    -
Port security       = Disabled
Fast-switchover     = disabled
Fast-switchover Dampening = disabled
Load share deferral = disabled
Ports in the Port-channel:
Index   Load      Port          EC state       No of bits
------+------+------------+------------------+-----------
0      E4            Te1/4                 On   4
1      1B            Te2/4                 On   4
Time since last port bundled:    204d:07h:19m:44s    Te2/4
Time since last port Un-bundled: 204d:07h:19m:54s    Te1/4
Core-01#
What does that load-value mean? and how is that calculated? and does that have a role to play in the selection of the port?
Thanks,
Nik

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
So it looks like how to divide the bits is decided by the switch.
Ah, yea, reread my original post for answer to your second question. ;)
An actual hashing algorithm can be rather complicated. What they try to do is to "fairly" divide the input value across the number of hash buckets. For example, if you have two Etherchannel links, they will try to hash the hash attribute such that 50% goes to one link and 50% to the other link.
For example, assuming you hash on source IP, how do you hash 192.168.1.1, .2, .3 and .4? A very simple hash algorithm could just go "odd"/"even", but what if your IPs were .2, .4, .6 and .8? A more complex algorithm would try to still hash these IPs equally across your two links.
Again, hashing algorithms can get complex, search the Internet on the subject, and you may better appreciate this.
Because of the possibility of such complexity, one vendor's hashing might be better than another vendor's, so they often will keep their actual algorithm secret.
No matter, though, how good a hashing algorithm might be, they all will hash the same attribute to the same bucket. For example, if you're still using source IP, and only source IP, as your hash attribute, all traffic from the same host is going to use the same link. This is why what attributes are used are important. Choices vary per Cisco platform. Normally, you want the hash attributes to differ between every different traffic flow.
Etherchannel does not analyze actual link loading. If there are only two active flows, and both hash to the same link, that link might become saturated, while another link is completely idle.
Short term Etherchannel usage, unless you're dealing with lots of flows, is often not very balanced. Longer term Etherchannel usage, should be almost balanced. If not, most likely you're not using the optimal hash attributes for your traffic.

Etherchannel between 2960 switches

Hello All,
I configured etherchannel between two 2960 switches.
Both the switches have SVI with subnet 192.168.2.3 and 192.168.2.4
I have another vlan3 on one of the switch.
so when i created etherchannel between two Gig ports and allowed both the vlans,it gave me an error messg,
Nov 3 12:41:07.332 KSA: %EC-5-CANNOT_BUNDLE2: Gi1/0/19 is not compatible with Gi1/0/20 and will be suspended (vlan mask is different)
Nov 3 12:41:07.339 KSA: %EC-5-CANNOT_BUNDLE2: Gi1/0/19 is not compatible with Po1 and will be suspended (vlan mask is different)
Nov 3 12:41:07.339 KSA: %EC-5-CANNOT_BUNDLE2: Gi1/0/19 is not compatible with Po1 and will be suspended (vlan mask is different)
Nov 3 12:41:07.339 KSA: %EC-5-CANNOT_BUNDLE2: Gi1/0/20 is not compatible with Po1 and will be suspended (vlan m
May i know why....
Thanks

Hello Mudasir
This will be a problem of allowed vlan mismatch. All the interfaces which are going to add in the etherchannel must have same allowed vlan on both sides.
You can check for the allowed vlan on all the interfaces as well as on Port-channel.
You can see the below forum having the same problem:
https://supportforums.cisco.com/discussion/9757346/etherchannel-prob
Regards,
Mukesh Kumar
Network Engineer
Spooster IT Services

Multi-context active-active etherchannel failover

Hi All,
Is there a way to monitor individual interfaces on a box doing multicontext etherchannel failover?
I can understand on an individual box you can add monitor-interface to the physical interface, but in multi context mode, there is only one interface (the logical etherchannel subinterface) pushed through from the system context to each of the other contexts. I've been looking around and can't work out how to get a context failover to fail if only one of the etherchannel fails.
If the other box has more active etherchannels then that's the one I want active, but can't see it at the moment.
Possibly missed something somewhere. Any ideas?
Thanks,
Gaz

monitor-interface will only work on "named" interfaces. So, what you are looking to do is not possible.
The member interfaces on a port-channel will not have "nameif" associated with them.
-Kureli

Layer 3 etherchannel - load 0x00

folks
i have a quick question i'm hoping you can help with
i have a layer 3 etherchannel between 2 * 3750G stacks, both clusters use gi1/0/25 and gi/2/0/25 for the etherchannel and both are set as 'on'
i have traffic passing over the link but i get the following output from a show etherchannel detail
there are no bits being recorded and the load is 0x00
can someone help to explain this please?
thanks to anyone taking the time to reply
Group: 10
Group state = L3
Ports: 2   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
Minimum Links: 0
                Ports in the group:
Port: Gi1/0/25
Port state    = Up Mstr In-Bndl
Channel group = 10          Mode = On              Gcchange = -
Port-channel = Po10        GC   =   -             Pseudo port-channel = Po10
Port index    = 0           Load = 0x00            Protocol =    -
Age of the port in the current state: 10d:01h:43m:57s
Port: Gi2/0/25
Port state    = Up Mstr In-Bndl
Channel group = 10          Mode = On              Gcchange = -
Port-channel = Po10        GC   =   -             Pseudo port-channel = Po10
Port index    = 0           Load = 0x00            Protocol =    -
Age of the port in the current state: 10d:01h:43m:54s
                Port-channels in the group:
Port-channel: Po10
Age of the Port-channel   = 10d:01h:45m:24s
Logical slot/port   = 10/10          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Passive port list   = Gi1/0/25 Gi2/0/25
Port state          = Port-channel L3-Ag Ag-Inuse
Protocol            =    -
Port security       = Disabled
Ports in the Port-channel:
Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
0     00     Gi1/0/25 On                 0
0     00     Gi2/0/25 On                 0
Time since last port bundled:    10d:01h:43m:54s    Gi1/0/25

Hi,
I guess this is just a hardware limitation on the 3k platforms (ASICs).

Layer 3 Etherchannel and MPLS MTU

Greetings,
If two 7609 are connected through layer 3 giga etherchannel and 7609-1 sends a frame with 1514 bytes plus two MPLS header to 7609-2, does the command mpls mtu 1522 under the giga etherchannel interface on both routers is enough?
Or it is necessary to add the global command system jumbomtu 1522 and the interface command mtu 1522 under physical gigainterfaces participating on the channel?
Cisco docs say many platforms will accept frames higher than 1500 bytes (up to 24 bytes) to accommodate control flags; that is why I am considering just mpls mtu xxx is enough.
Also, reading Cisco doc I understood that system jumbomtu xxxx and mtu xxxx should be used together. I tested sending frames higher than 1514 bytes (without MPLS tags) and system jumbomtu xxxx alone was not enough, ping failed; it was necessary to add mtu xxxx under the interface. Do you have a different experience?
Thanks,
Alaerte Gladston Vidali
IBM Global Services - SO
Tel.55+11+2121-2879 Fax:55+11+2121-2449

Hi
We had some peculiar exp with 7600 (7609/7606) boxes in which we did change the physical mtu of the interface instead of mpls mtu.
Again that did the trick for us even in 7200 where we monitored the same kinda behaviour..
regds

Etherchannel and HP teaming software- one, the other or both?

I have servers that I want to bundle the gigabit NIC's together for both load balancing and redundancy. Do I use the HP teaming software to bundle the NIC's, use etherchannel on the 4506 that they are plugged into, or both? What are the advantages to each, and any links or documentation that can be supplied would be appreciated.
Thanks.

Both. On the Cisco switch you would configure the ports to be part of an etherchannel while the NICs themselves need to be teamed using HP teaming software.

Output errors on an interface of etherchannel

Hi all,
I have 2 interfaces which are a part of an etherchannel link from Core switch 2 to back up servers These 2 interfaces are displaying output errors
This core switch 2 has an connection to a 3550 to which a linux server is attached
Backup is been performed from linux server to the backup servers everyday and we see a network performance issue as backup take way too long.
Lnx server is attached to 3550 at 100/ full connection on port fa0/17 and there is no duplex mismatch issues, port fa0/17 has underrun errors (see attachment)
Core switch 2 has port gi5/15 and gi5/16 in the etherchannel and are on 1000/full connection (see attachment)
Can anybody provide me a solution for this problem
Thanks

Hi all,
I
have 2 interfaces which are a part of an etherchannel link from Core
switch 2 to back up servers These 2 interfaces are displaying output errors
This core switch 2 has an connection to a 3550 to which a linux server is attached
Backup is been performed from linux server to the backup servers everyday and we see a network performance issue as backup take way too long.
Lnx server is attached to 3550 at 100/ full connection on port fa0/17 and there is no duplex mismatch issues, port fa0/17 has underrun errors (see attachment)
Core switch 2 has port gi5/15 and gi5/16 in the etherchannel and are on 1000/full connection (see attachment)
Can anybody provide me a solution for this problem
Thanks
Attachments:
Core 2.txt.zip (1.0 K)
3550.txt.zip (869 bytes)
Hi,
Following are the observation of interface logs of 3550:-
There have been 8414 'output buffer failures' reported. If outgoing interface buffers are not available, an output buffer failure is reported.If an interface buffer is available but the Transmit Queue Limit is reached, the packet is dropped. However, if 'transmit-buffers backing-store' is enabled, the packet is placed in a System Buffer (which has to be obtained from an appropriate Free-List), and enqueued in the Output Hold queue for future transmission at the Process level, and an Output Buffer Swap is reported.
and 8414 'underruns' have been reported, which amounts to 0.00514% of the total input traffic. This is because, the far-end transmitter runs faster than
the receiver of the near-end router can handle.
Check out this:- Monitor the level of underruns over time. If they continue increasing, consider buffer and queue tuning or upgrading hardware.
Check out the below link for buffer tuning
http://www.cisco.com/en/US/customer/products/hw/routers/ps133/products_tech_note09186a00800a7b80.shtml
Hope to help !!
Ganesh.H
Cisco are currently donating money to the Haiti earthquake appeal for every rating so please consider rating all helpful posts.

5508 WLC-6500 Series Switch Etherchannel

Hi,
I have a 5508 controller connected to a 6500 VSS pair. Below is the port channel configuration and port configuration. I am just wondering whether we still have to configure a load balancing method as cisco recommends “port-channel load-balance src-dst-ip” as best practice.
Does this still applicable for 5508 controller-6500 Series uplink as the etherchannel is L2 etherchannel?
Port Channel Config:
interface Port-channel1
description To 5508 WLC
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 9
switchport trunk allowed vlan 10,11,12
switchport mode trunk
mls qos trust dscp
end
Interface Config:
interface GigabitEthernet1/1/42
description To 5508 WLC
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 9
switchport trunk allowed vlan 10,11,12
switchport mode trunk
wrr-queue bandwidth 5 25 70
wrr-queue queue-limit 5 25 40
wrr-queue random-detect min-threshold 1 80 100 100 100 100 100 100 100
wrr-queue random-detect min-threshold 2 80 100 100 100 100 100 100 100
wrr-queue random-detect min-threshold 3 50 60 70 80 90 100 100 100
wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100
wrr-queue random-detect max-threshold 2 100 100 100 100 100 100 100 100
wrr-queue random-detect max-threshold 3 60 70 80 90 100 100 100 100
wrr-queue cos-map 1 1 1
wrr-queue cos-map 2 1 0
wrr-queue cos-map 3 1 4
wrr-queue cos-map 3 2 2
wrr-queue cos-map 3 3 3
wrr-queue cos-map 3 4 6
wrr-queue cos-map 3 5 7
mls qos trust dscp
channel-group 1 mode on
end

Hello,
Please check to following link regarding load balancing between 5508 and WLC 6500:
http://www.learnios.com/viewtopic.php?f=5&t=34555

EtherChannel and LAN Design for new buildiing(s)

What is the recommended best practice for EtherChannel size for a 3750G-12S stack? Will I benefit from stacking these with the StackWise cable on the backplane, or would it be better to run these independently back to the 4006 with individual EtheChannels?
The 3750G-12S stack will likely be 1 or 2 devices at distribution layer for upwards of 18 - 20 2960G-48 access layer switches and approximately 20 1242LAP AP's in addition to max capacity of end users attached to the switches.
I am considering implementing a 4 gig EtherChannel between the 3750's to the 4006 for this load. My limit is the number of available ports on the 4006 and obviously the max load of links on the EtherChannel.

Unsure there's a single "best practice" for stacking or not. Some advantages/disadvantages to both. Part of the decision might rest on whether the 3750s will be L2 or L3.
Stackwise could be a performance bottleneck if you believe there would be much traffic between switch ports, but if most will transit your 4006, your links to it would be the bottleneck.
What you might consider, a single 3750G-12S (four?) that can handle 2 links from each access switch, that are Etherchanneled and not connected to the same 3750 stack member. This with the 4 gig Etherchannel to the 4006, which again should be spread across stack members.

Pvlan (promiscuous port) not permitted on etherchannel

This is probably an often-asked question: I've read in the 7K v5.0(2) NX-OS docs, the 6500 12.2SXF/SXH IOS docs and the 5K docs that the pvlan feature cannot co-exist with etherchanneling on the same uplink. This would assumedly include promiscuous trunk ports.
This seems so counter-productive and self-defeating. Especially where the 7K vPC feature is cfg'd requiring LACP etherchannels from the single switch into both 7Ks.
What am I missing here? Is there a work-around short of new dedicated links? The cost of the 10G optics for that approach is prohibitive. Is it possibly on the road-map for some future upgrades?
Maybe I could configure an unconditional port-channel with no protocol, no negotiation? I'm waiting on the vDC licensing to let me direct-connect the lab 5Ks.
Thank you,
Ken Johnson

Required info:
system image file is: bootflash:///n5000-uk9.6.0.2.N2.2.bin
system compile time: 10/4/2013 12:00:00 [10/04/2013 22:23:49]
interface port-channel4001
description SERVER1
switchport mode trunk
switchport access vlan 201
switchport trunk native vlan 201
storm-control broadcast level 1.00
storm-control multicast level 1.00
storm-control unicast level 1.00
vpc 4001
interface Ethernet107/1/47
description SRV1
no lldp transmit
no cdp enable
switchport mode trunk
switchport access vlan 201
switchport trunk native vlan 201
storm-control broadcast level 1.00
storm-control multicast level 1.00
storm-control unicast level 1.00
channel-group 4001 mode active
no shutdown

Etherchannel sequence

Hi Experts,
I would like to know the Etherchannel sequence.
If I have 2 ports in EtherChannel, for example, port 1 and port 2. Source and destination mac is my load balance method. I would like to know when the first packet goes to the Etherchannel, which port that the 1st packet will go, port 1 or port 2.
I am sure it would only go by one port for each session, and I wonder which port it would take when the first packer arrives.
Thank you,
Aries

Hi Aries,
Nice question.
I just now did three experiments on this and at the three times... the first frame has passed throught the port with the lowest number.
For ex:
My first port-channel has Fa0/1 and Fa0/2 ,,, the first frame passed through Fa0/2.
My second port channel ex: There were two ports already in channel they were Fa0/14,Fa0/15... fa0/15 was first added to the channel... but the frame chose Fa0/14 for the first time.
My third ex: There were Fa0/15 and Fa0/14 channels... then after i added Fa0/1... the first frame chose Fa0/1.
Regards,
Chandu

Etherchannel two cisco 3750 stacks for iscsi?

I have two sites connected by 96 strands of fibre. At each site I have an IBMv7000 relicating to the other one. For iSCSI traffic I have two Cisco 3750 switches, each are in 2 switch stack.
SAN A                         Fibre Link                          SAN B
        |                                                                        |
Cisco Stack A =========================Cisco Stack B
        |                                                                        |
        |                                                                        |
iSCSI Clients                                                       iSCSI Clients
My question: Is it ok to connect the the two stacks with etherchannel using the fibre links? Will is provide the necessary redundancy, if one of the interfaces goes down?

What model numbers of 3750 are you using?
What is the distance between the stacks as this will dictate your fiber run modules.

Etherchannel between 2 pair of APs

Hi,
Any one configured etherchannel at a single switch across 2 pairs of AP with 5Ghz as backhaul? Does it work?
Topology
switch ----- AP1 --------- backhaul 5Ghz ---- AP3 ---- switch 2
(etherchannel) ------AP2 --------- backhaul 5Ghz ---- AP4 ---- (etherchannel)

Theoretically but throughput also depends on your wireless backhaul since packets can only go over one bridge link. Will you get 300mbps connection. Maybe or maybe not. Wireless is half duplex so really 150mbps actual throughput per wireless link so theoretical 300mbps.
Sent from Cisco Technical Support iPhone App

Etherchannel

Similar Messages

Maybe you are looking for