Interface without outside traffic at LACP

[Jalmeida]

Guys, I didn't see any configuration problems with the LACP, the SFP or the link/fiber.
But I have a topology with a LACP between 9500 x 9400, and I use 4 10G-SR interfaces.

One of these interfaces is passing TX input traffic, but not RX output.

I removed the portchannel interface, configured a static IP, and I see traffic passing in both directions, however, when I return to the portchannel, it has no traffic.

There is no CRC, and I also didn't see any difference in voltage, current, or tx/rx in the tranceiver detail.
It seems to be something from LACP, but I haven't seen any bugs, and the equipment is not supported.

As there are 2 interfaces, I recommended the customer to disconnect one that is functional, and place it in the position of the ones that are not receiving traffic, however, as I said, it seems to be something in the lacp.

any other tips?

Below I compare the particularities of a functional transceiver, and another with an interface with a problem:

9500:

SW-WAN-01#show interface Twe1/0/37 | inc rate
Queueing strategy: fifo
30 second input rate 14488000 bits/sec, 6898 packets/sec
30 second output rate 3863000 bits/sec, 4057 packets/sec
SW-WAN-01#show interface Twe1/0/36 | inc rate
Queueing strategy: fifo
5 minute input rate 27002000 bits/sec, 3303 packets/sec
5 minute output rate 3475000 bits/sec, 3429 packets/sec
SW-WAN-01#show interface Twe2/0/37 | inc rate
Queueing strategy: fifo
30 second input rate 20007000 bits/sec, 2843 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
SW-WAN-01#show interface Twe2/0/36 | inc rate
Queueing strategy: fifo
30 second input rate 25204000 bits/sec, 3618 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec

High Alarm High Warn Low Warn Low Alarm
Temperature Threshold Threshold Threshold Threshold
Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
--------- ----------------- ---------- --------- --------- ---------
Twe2/0/37 22.6 75.0 70.0 0.0 -5.0

High Alarm High Warn Low Warn Low Alarm
Voltage Threshold Threshold Threshold Threshold
Port (Volts) (Volts) (Volts) (Volts) (Volts)
--------- ----------------- ---------- --------- --------- ---------
Twe2/0/37 3.32 3.63 3.46 3.13 2.97

High Alarm High Warn Low Warn Low Alarm
Current Threshold Threshold Threshold Threshold
Port Lane (milliamperes) (mA) (mA) (mA) (mA)
--------- ---- --------------- ---------- --------- --------- ---------
Twe2/0/37 N/A 4.1 10.0 8.5 3.0 2.6

Optical High Alarm High Warn Low Warn Low Alarm
Transmit Power Threshold Threshold Threshold Threshold
Port Lane (dBm) (dBm) (dBm) (dBm) (dBm)
--------- ---- --------------- ---------- --------- --------- ---------
Twe2/0/37 N/A -2.2 1.7 -1.3 -7.3 -11.3

Optical High Alarm High Warn Low Warn Low Alarm
Receive Power Threshold Threshold Threshold Threshold
Port Lane (dBm) (dBm) (dBm) (dBm) (dBm)
--------- ---- --------------- ---------- --------- --------- ---------
Twe2/0/37 N/A -3.1 2.0 -1.0 -9.9 -13.9

9400

COE-CRP-01#show interface T2/1/0/3 | inc rate
Queueing strategy: fifo
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 22741000 bits/sec, 3218 packets/sec
COE-CRP-01#show interface T2/1/0/6 | inc rate
Queueing strategy: fifo
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 18305000 bits/sec, 2629 packets/sec
COE-CRP-01#show interface T1/1/0/3 | inc rate
Queueing strategy: fifo
5 minute input rate 3683000 bits/sec, 3510 packets/sec
5 minute output rate 25529000 bits/sec, 3196 packets/sec
COE-CRP-01#show interface T1/1/0/6 | inc rate
Queueing strategy: fifo
5 minute input rate 3910000 bits/sec, 3720 packets/sec
5 minute output rate 12504000 bits/sec, 3834 packets/sec
COE-CRP-01#show running-config interface po101

High Alarm High Warn Low Warn Low Alarm
Temperature Threshold Threshold Threshold Threshold
Port (Celsius) (Celsius) (Celsius) (Celsius) (Celsius)
--------- ----------------- ---------- --------- --------- ---------
Twe1/0/37 21.9 75.0 70.0 0.0 -5.0

High Alarm High Warn Low Warn Low Alarm
Voltage Threshold Threshold Threshold Threshold
Port (Volts) (Volts) (Volts) (Volts) (Volts)
--------- ----------------- ---------- --------- --------- ---------
Twe1/0/37 3.33 3.63 3.46 3.13 2.97

High Alarm High Warn Low Warn Low Alarm
Current Threshold Threshold Threshold Threshold
Port Lane (milliamperes) (mA) (mA) (mA) (mA)
--------- ---- --------------- ---------- --------- --------- ---------
Twe1/0/37 N/A 4.5 10.0 8.5 3.0 2.6

Optical High Alarm High Warn Low Warn Low Alarm
Transmit Power Threshold Threshold Threshold Threshold
Port Lane (dBm) (dBm) (dBm) (dBm) (dBm)
--------- ---- --------------- ---------- --------- --------- ---------
Twe1/0/37 N/A -2.2 1.7 -1.3 -7.3 -11.3

Optical High Alarm High Warn Low Warn Low Alarm
Receive Power Threshold Threshold Threshold Threshold
Port Lane (dBm) (dBm) (dBm) (dBm) (dBm)
--------- ---- --------------- ---------- --------- --------- ---------
Twe1/0/37 N/A -2.9 2.0 -1.0 -9.9 -13.9

[alancelliott]

Hello,

It may just be the load balancing algorithm pinning the rx traffic to the other link. The "port-channel load-balance ?" In global config should show you the available load balancing options. See here for relevant commands to configure the hash algorithm: 

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/cether/command/ce-cr-book/ce-m1.html#wp1124464550

Hope that helps,

Alan 

[MHM Cisco World]

Share 

Show port-channel load 

Of both SW let compare the algorithm use in both SW

MHM

[Jalmeida]

Hello @alancelliott  and @MHM Cisco World 

Thank you very much!
Now with this information, I'm going to study a little more to understand what is leading to this strange behavior.

Anyway, thank you very much.

9500

SW-WAN-01#show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-mixed-ip-port

EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address and TCP/UDP (layer-4) port number
IPv6: Source XOR Destination IP address and TCP/UDP (layer-4) port number

SW-WAN-01#show run interface port-channel 101
Building configuration...

Current configuration : 270 bytes
!
interface Port-channel101
description [MON]CORE01 - PO101
switchport trunk allowed vlan 13,14,100,101,156,210,224,251,1266,2240 ,2340
switchport trunk allowed vlan add 2638,3000,3924,3962,4007
switchport mode trunk
load-interval 30
speed nonegotiate

9400

CRP-01#show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-ip

EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address

CRP-01#show run interface port-channel 101
Building configuration...

Current configuration : 258 bytes
!
interface Port-channel101
description [MON]SW-WAN-01 - PO101
switchport trunk allowed vlan 13,14,100,101,156,210,224,251,1266,224 0,2340
switchport trunk allowed vlan add 2638,3000,3924,3962,4007
switchport mode trunk
load-interval 30

[alancelliott · Accepted solution]

No problem,

Looks like the 9500 will have more entropy hashing on the 5-tuple, I'd config the 9400 to match the 9500 hash load-balance as of now it just hashes based on d-mac and d-ip which might be causing what you're seeing. The more tuples we match on the more entropy for hashing across your etherchannel link. Once you do that check your int counters again and see if the traffic is rx/txing where/how you expect.

Cheers

[MHM Cisco World]

sorry I see your reply today 
mixed is advance feature from cisco to for load balance 
so match both Hash in both SW and check load in links

MHM