Port Channel Flag Details

All,
I created an etherchannel between a cat3750G and a cat6509. I ran a show etherchannel 5 detail and I noticed for my flags I got SC. Is this okay, I am wondering because I looked it up and it doesn't sound good but I could be reading it wrong. Thanks
Group state = L2
Ports: 2 Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol: PAgP
Ports in the group:
Port: Gi1/0/25
Port state = Up Mstr In-Bndl
Channel group = 1 Mode = Desirable-NonSl Gcchange = 0
Port-channel = Po1 GC = 0x00010001 Pseudo port-channel = Po1
Port index = 0 Load = 0x00 Protocol = PAgP
Flags: S - Device is sending Slow hello. C - Device is in Consistent state.
A - Device is in Auto mode. P - Device learns on physical port.
d - PAgP is down.
Timers: H - Hello timer is running. Q - Quit timer is running.
S - Switching timer is running. I - Interface timer is running.
Local information:
Hello Partner PAgP Learning Group
Port Flags State Timers Interval Count Priority Method Ifindex
Gi1/0/25 SC U6/S7 H 30s 1 128 Any 5001
Partner's information:
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Gi1/0/25 CAT_6509_HQ 000c.cfd0.dc00 Gi2/4 7s SC 10001
Age of the port in the current state: 01d:08h:58m:36s
Port: Gi1/0/26
Port state = Up Mstr In-Bndl
Channel group = 1 Mode = Desirable-NonSl Gcchange = 0
Port-channel = Po1 GC = 0x00010001 Pseudo port-channel = Po1
Port index = 0 Load = 0x00 Protocol = PAgP
Flags: S - Device is sending Slow hello. C - Device is in Consistent state.
A - Device is in Auto mode. P - Device learns on physical port.
d - PAgP is down.
Timers: H - Hello timer is running. Q - Quit timer is running.
S - Switching timer is running. I - Interface timer is running.
Local information:
Hello Partner PAgP Learning Group
Port Flags State Timers Interval Count Priority Method Ifindex
Gi1/0/26 SC U6/S7 H 30s 1 128 Any 5001
Partner's information:
Partner Partner Partner Partner Group
Port Name Device ID Port Age Flags Cap.
Gi1/0/26 CAT_6509_HQ 000c.cfd0.dc00 Gi2/3 6s SC 10001
Age of the port in the current state: 01d:09h:04m:31s
Port-channels in the group:
Port-channel: Po5
Age of the Port-channel = 01d:09h:25m:21s
Logical slot/port = 10/1 Number of ports = 2
GC = 0x00010001 HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = PAgP
Ports in the Port-channel:
Index Load Port EC state No of bits
------+------+------+------------------+-----------
0 00 Gi1/0/25 Desirable-NonSl 0
0 00 Gi1/0/26 Desirable-NonSl 0

Looks perfect , both are up , master in bundle and they see each and have negotiated the etherchannel properly . You can also do a show etherchannel summary to I believe which gives you a compact reading on the channel.

Similar Messages

JMS Adapter Fail - Receiver channel. Details: Receive timed out

Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
However in Adapter monitoring, JMS adapter is in red.
The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
However i would like to know, if there is something else that i should look into?

Following are the error messages in RWB audit log for the message sent.
Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
what might be the problem?

FWSM Default port channel?

I'm doing some L2 cleanups across mutliple 6509E environments and I've found something consistent that I can't find in documentation.
On all my pairs of 6509s where I have FWSMs bundled (6509-A has FWSM-1 is Slot 1 and 6509-B has FWSM-2 in Slot 1) I also have a port channel 305. Obviously when I do a "show run" or "show int desc" I don't see anything in slot one. It's a service module. But the port channel is referencing ports 1/1-6. And it's all in service/up. I was about to delete this as I thought it was some leftover config (TEST 6509s) until I went and saw the same things on our PROD 6509s. Can anyone explain this or provide some documentation on it? Is it cosmetic? Necessary? Can I delete it as part of my audit cleanup? Don't want to mess with it even in TEST without some information. Nothing on google that's clear and I can't find anything on CCO.
6509-1#sho etherch 305 summ
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      N - not in use, no aggregation
        f - failed to allocate aggregator
        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port
        w - waiting to be aggregated
Number of channel-groups in use: 11
Number of aggregators:           11
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
305    Po305(SU)        -        Gi1/1(P)       Gi1/2(P)       Gi1/3(P)
                                 Gi1/4(P)       Gi1/5(P)       Gi1/6(P)
Last applied Hash Distribution Algorithm:   -
6509-1#sho etherch 305 det
Group state = L2
Ports: 6   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
Minimum Links: 0
                Ports in the group:
Port: Gi1/1
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 0           Load = 0x41        Protocol =    -
Age of the port in the current state: 46d:06h:53m:39s
Port: Gi1/2
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 1           Load = 0x02        Protocol =    -
Age of the port in the current state: 46d:06h:53m:39s
Port: Gi1/3
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 2           Load = 0x04        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/4
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 3           Load = 0x88        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/5
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 4           Load = 0x10        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/6
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 5           Load = 0x20        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
                Port-channels in the group:
Port-channel: Po305
Age of the Port-channel   = 46d:06h:55m:56s
Logical slot/port   = 14/11          Number of ports = 6
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -
Fast-switchover     = disabled
Load share deferral = disabled
Ports in the Port-channel:
Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
0     41     Gi1/1    On    2
1     02     Gi1/2    On    1
2     04     Gi1/3    On    1
3     88     Gi1/4    On    2
4     10     Gi1/5    On    1
5     20     Gi1/6    On    1
Time since last port bundled:    46d:06h:53m:41s    Gi1/6
Last applied Hash Distribution Algorithm:   -
NOC-SW-ITEST-AGG1#

The connection between the FWSM and the switch is a 6-GB 802.1Q trunking EtherChannel. This EtherChannel is automatically created when you install the FWSM.
http://cisconetwork.org.ua/1587051893/ch04lev1sec1.html
http://www.cisco.com/en/US/docs/security/fwsm/fwsm23/configuration/guide/switch.pdf
Thanks
Ajay

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

Port channel WLC 5508 and 3750

Hi All,
I want to configure Port channel for WLC 5508 and cisco 3750 Stack Switch. What changes I need to make on WLC and where?
Thanks
Jagdev

Thanks Chris,
LAG is enable on WLC, and Port channel is configured on 3750, Please see the configration and Port channel status below:-
(Cisco Controller) >show lag summary
LAG Enabled
interface Port-channel14
description Port Channel to WLC001
switchport trunk encapsulation dot1q
switchport mode trunk
end
sh etherchannel 14 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
        d - default port
Number of channel-groups in use: 14
Number of aggregators:           14
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
14     Po14(SD)        LACP      Gi1/0/22(I) Gi2/0/22(I)
sh run int g1/0/22
Building configuration...
Current configuration : 209 bytes
interface GigabitEthernet1/0/22
description Trunk to WLC001 DistPort1
switchport trunk encapsulation dot1q
switchport trunk native vlan 254
switchport mode trunk
channel-group 14 mode active
end
sh run int g2/0/22
Building configuration...
Current configuration : 209 bytes
interface GigabitEthernet2/0/22
description Trunk to WLC001 DistPort2
switchport trunk encapsulation dot1q
switchport trunk native vlan 254
switchport mode trunk
channel-group 14 mode active
end

What is the maximum number of physical link we can bind to a ether-channel and port-channel

Hi,
I was studying about port-channel & ether-channel and found that, it can be bind up-to 8 ports. So maximum number, we can have of 8 ports or more ?
For binding we should have minimum of 2 ports or 1 ports will work ? For load-balancing purpose, is the port no. would be in a bundle of 2,4 and 8 ?
Thanks

Hi Kathik,
I have gone through one document. It's saying the below mentioned things :
Jun 7, 2012 9:36 PM (in response to Sarabjit)
Re: What is the maximum number of etherchannels we can have?
The maximum number of Etherchannels varies from platform to platform. The maximum number of ports in an etherchannel is either 8 ro 16 depending on the platform. The minimum number of ports in an etherchannel bundle is 1.
Jun 8, 2012 1:27 AM (in response to Sarabjit)
Re: What is the maximum number of etherchannels we can have?
Etherchannels is a Cisco term. Other vendors call them 802.3ad trunks. It's common to see something like this in datasheets:
48 ports 10/100/1000 Mbit/s
802.3ad:
Maximum of 32 groups
Maximum of 8 ports per group
The document url is https://learningnetwork.cisco.com/thread/43680
The another document says the below mentioned things :
Matrix of Load Balancing Methods
This matrix consolidates the load balancing methods that this document describes:
Platform
Address Used in XOR
Source-Based?
Destination-Based?
Source-Destination-Based?
Load Balancing Method—Configurable/Fixed?
6500/6000
Layer 2, Layer 3 addresses, Layer 4 information, or MPLS information2
Yes
Yes
Yes
Configurable
5500/5000
Layer 2 address only
Yes
Cannot change the method
4500/4000
Layer 2, Layer 3 addresses, or Layer 4 information
Yes
Yes
Yes
Configurable
2900XL/3500XL
Layer 2 address only
Yes
Yes
Configurable
3750/3560
Layer 2 or Layer 3 address only
Yes
Yes
Yes
Configurable
2950/2955/3550
Layer 2 address only1
Yes
Yes
—1
Configurable
1900/2820
These platforms use a special method of load balancing. See theCatalyst 1900/2820 section for details.
8500
Layer 3 address only
Yes
Cannot change the method
1 For the 3550 series switch, when source-MAC address forwarding is used, load distribution based on the source and destination IP address is also enabled for routed IP traffic. All routed IP traffic chooses a port based on the source and destination IP address.
2 For the 6500 series switches that run Cisco IOS, MPLS layer 2 information can also be used for load balancing MPLS packets.
The document url is http://www.cisco.com/c/en/us/support/docs/lan-switching/etherchannel/12023-4.html
Another document says the below mentioned things for load-balancing :
inally, here is full list of valid load-distribution methods:
•dst-ip—Load distribution on the destination IP address
•dst-mac—Load distribution on the destination MAC address
•dst-port—Load distribution on the destination TCP/UDP port
•src-dst-ip—Load distribution on the source XOR destination IP address
•src-dst-mac—Load distribution on the source XOR destination MAC address
•src-dst-port—Load distribution on the source XOR destination TCP/UDP port
•src-ip—Load distribution on the source IP address
•src-mac—Load distribution on the source MAC address
•src-port—Load distribution on the source port
The document url is https://learningnetwork.cisco.com/thread/63064
Please suggest.

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.

Nexus port channel load balance

Hi
I just want to clarify one setting for the port channel load balance on Nexus 6k switch. If I use the load balance option source-dest-ip-only, will following four converstions be load balanced?
10.10.10.1 -> 192.168.1.1
10.10.10.2 -> 192.168.1.1
10.10.10.1 -> 192.168.1.1
10.10.10.1 -> 192.168.1.2
Thanks. Leo

Hi Leo,
I think there may be typo in your question as I only see three conversations and not four. That aside I've not seen the Nexus port-channel load balancing sufficiently well documented to be able to give you the exact answer.
In their configuration guides Cisco only include the following statement:
Cisco NX-OS load balances traffic across all operational interfaces in a port channel by reducing part of the binary pattern formed from the addresses in the frame to a numerical value that selects one of the links in the channel.
There is other documentation that states the load balancing algorithm uses a CRC-8 based polynomial, but as we don't know exactly which parts of the frame are used in the calculation, I don't see it's possible to calculate the answer and so derive the link that will be used for a given conversation.
While I've not seen full documentation regarding the science used in the calculation, what Cisco have done is provide a command on the switch CLI that will allow you to determine which link of a port-channel will be used.
If you run the command show port-channel load-balance forwarding-path interface port-channel vlan src-ip dst-ip then one of the parts of the output is the member link of the port-channel that will be used for that flow.
You can find full details of the options for the show port-channel load-balance command in the command reference.
One other point to remember is that the load balancing across a port-channel is unidirectional, and the hashing might be completely different for the return flow of a conversation. For example it is entirely possible that traffic from A to B could use one link of a port-channel, while the return traffic from B to A for the same conversation could use a different link.
In general I would use the source-dest-port option for load balancing on the Nexus switches as this will obviously include the Layer-4 port numbers in the calculation, and so give you a better distribution of flows across all member links.
Regards

Fabric Interconnect Uplink port channeling...

Hi,
We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
Thank you

Hello,
You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
-------- NXOS output -----------------
FI-A(nxos)# sh run int port-channel 1
interface port-channel1
description U: Uplink
switchport mode trunk
speed 10000
FI-A(nxos)# show int port-channel 1
port-channel1 is up
Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
Description: U: Uplink
MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 10 Gb/s
FI-A(nxos)# sh int bri
Port-channel VLAN Type Mode   Status Reason                    Speed Protocol
Interface
Po1          1     eth trunk up      none                       a-10G(D) lacp
There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
FI-A /eth-uplink/fabric # show port-channel detail
Port Channel:
    Port Channel Id: 1
    Name: FIA
    Admin State: Enabled
    Oper State: Up
   Speed: 10 Gbps
    Oper Speed: 10 Gbps
    State Reason:
    flow control policy: default
HTH
Padma

Nexus - port-channel load balancing

Port-channel load balancing is a global command or interface command in Nexus switch?
Thanks,
Manu

Hi,
It's a global command; port-channel load-balance ethernet.
You can find details in the Configuring Load Balancing Using Port Channels section of the Nexus 5500 Series NX-OS Interfaces Configuration Guide.
Regards

Port channel fsps weight counting

How will FSPF counts path weight in port chanal case? For example - there is two fisical lincks with different speeds - 2 and 1 gig. What fspf count i'll have?

Sorry but you can't mix 1g with 2g. All members of a port-channel must be the same speed. See the output of command "show port-channel compatibility-parameters" for more detail.
Now lets say you have 5 x 2gbps links in a port-channel. The bandwidth sum will be 10gbps. The cost for a a 1gbps link is 1000, so therefore the cost for a 10gbps port-channel will be one tenth of 1000, ie cost=100.

Pppoe over port-channels on ios xe

has the ability to do pppoe and QinQ over port-channels been added to IOS XE? as of 2.6 it was not but I cannot find any documentation on 3.1-3.3 to say that it has or hasn't
Does any one use a asr1000 as a BRAS and if so how do you handle redundancy in case of the loss of a primary interface handling your pppoe sessions?

Hi Artyom,
Try removing "ipv6 nd managed-config-flag" and see if it helps.
Regards

Port channel Statistics

Hi ,
I have configured ether channel between two Cisco switches. When I look at the statistics on both switches port channel I am not very sure why they are different in terms of Load and No of bits. One end is showing for load 55 and AA, No of bit -4. Whereas the other end both are 0. Can someone please clarify this.
I tried to replicate the same in a Lab, but I see 0 on both ends.
Below is the details:
Switch 1
Port-channels in the group:
Port-channel: Po1
Age of the Port-channel   = 588d:04h:38m:36s
Logical slot/port   = 10/1          Number of ports = 2
GC                  = 0x00010001      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =   PAgP
Port security       = Disabled
Ports in the Port-channel:
Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
0     00     Gi1/1/1 Desirable-Sl       0
0     00     Gi1/1/2 Desirable-Sl       0
Switch 2
Port-channel: Po3
Age of the Port-channel   = 596d:05h:08m:01s
Logical slot/port   = 14/3          Number of ports = 2
GC                  = 0x00030001      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =   PAgP
Fast-switchover     = disabled
Load share deferral = disabled
Ports in the Port-channel:
Index   Load      Port          EC state       No of bits
------+------+------------+------------------+-----------
1      55          Gi7/5       Desirable-Sl   4
0      AA          Gi7/6       Desirable-Sl   4
Time since last port bundled:    0d:01h:59m:59s    Gi7/5
Time since last port Un-bundled: 0d:02h:00m:02s    Gi9/10
Thanks

this works quite well as it turns out, I put the data on a Linux box and was able to add a date/time to each line, it then charts quite well in excel

Port channel failure / lacp_switch_get_new_agg_id: secondary l3 agg are not supported

hi,
hope that someone can help.
I ran into port channel issue when trying to add 4 port Quantum Dxi server into a port channel in 3750 stack.
Configs looks ok:
interface Port-channel6
description qdx-server
switchport access vlan 3
switchport mode access
spanning-tree portfast
spanning-tree bpduguard enable
end
all four ports configured as follows
interface GigabitEthernet1/0/7 , 1/0/5 , 2/0/7 and 2/0/8
description qdx-server-ethx
switchport access vlan 3
switchport mode access
spanning-tree portfast
spanning-tree bpduguard enable
channel-protocol lacp
channel-group 6 mode active
end
all ports joined the channel except Gi 1/0/5 - it got suspended once joined the port channel
From the debug I got the following:
Dec 16 13:36:43.082 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:46.823 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_first_associated_port_from_agg_id: found port Gi2/0/8 associated to Po6
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_next_agg_id_from_admin_oper_keys: aggregator next to Po6 not found for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:56.838 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_first_associated_port_from_agg_id: found port Gi2/0/8 associated to Po6
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_next_agg_id_from_admin_oper_keys: aggregator next to Po6 not found for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:37:06.837 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:37:07.080 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:37:07.080 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Checked and compared the config from another server, all looks OK.. I tried to search the error message in bold, but can't find any.
Can anyone shed a light?
Many thanks.

we have the same issue with asa5525 and 3750E etherchannel.
The same error
lacp_switch_get_new_agg_id: secondary l3 agg are not supported on the SWITCH side
we are using LACP active from noth sides

Port-Channel Issue: SP-5-CANNOT_BUNDLE_LACP

I'm having an issue with the port-channel coming up. Right now it's "down down". I'm not really sure why. All other port-channels on the 6500's in VSS work fine. This one seems to be giving me an issue though.
-Both interfaces that are using this port-channel are "up up".
-I've done "shut's, no shut's" on all interfaces involved.
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      N - not in use, no aggregation
        f - failed to allocate aggregator
        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port
Po4(SD)         LACP      Gi1/1/4(I)     Gi2/1/4(I)
interface Port-channel4
switchport
switchport access vlan (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
end
interface GigabitEthernet1/1/4
switchport
switchport access vlan   (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
channel-protocol lacp
channel-group 4 mode active
end
interface GigabitEthernet2/1/4
switchport
switchport access vlan (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
channel-protocol lacp
channel-group 4 mode active
end
sh log
149886: Jul 3 15:20:34 CDT: %EC-SW1_SP-5-CANNOT_BUNDLE_LACP: Gi2/1/4 is not compatible with aggregators in channel 4 and cannot attach to them (flow control receive of Gi2/1/4 is desired, Gi1/1/4 is on)
149887: Jul 3 15:20:35 CDT: %EC-SW2_SPSTBY-5-CANNOT_BUNDLE_LACP: Gi2/1/4 is not compatible with aggregators in channel 4 and cannot attach to them (flow control receive of Gi2/1/4 is desired, Gi1/1/4 is on)
Thank you for your help.

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

Port Channel Flag Details

Similar Messages

Maybe you are looking for