No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Trunk Interface Enabled with LACP Cannot Forward Packets Because of the Crossed Pair on the ME60

Publication Date:  2013-09-03 Views:  24 Downloads:  0
Issue Description
Version: V600R002C02SPC700
Symptom: The ME60 connects to the downstream switch through three GE interfaces that are bound into a trunk interface. After LACP is enabled on the trunk interface, two member interfaces do not forward packets.
Handling Process
1. Check status of the three interfaces. The result shows that the three interfaces are all in Up state and their optical power is normal.
2. Check status of the trunk interface. The result shows that two member interfaces are in Down state. It is suspected that LACP cannot detect peer member interfaces. Run the dis lacp statistics eth-trunk x command to check LACP statistics. The command output shows that the number of LACP packets that are received and sent increases.
Eth-Trunk2's PDU statistic is:
------------------------------------------------------------------------------
Port                    LacpRevPdu   LacpSentPdu  MarkerRevPdu MarkerSentPdu
GigabitEthernet3/0/9    367968       367984       0            0           
 GigabitEthernet2/0/2    8063         7171         0            0           
 GigabitEthernet2/0/8    371405       371408       0            0           
 
 
<ME60>dis lacp statistics eth-trunk 2
Eth-Trunk2's PDU statistic is:

------------------------------------------------------------------------------
Port                    LacpRevPdu   LacpSentPdu  MarkerRevPdu MarkerSentPdu
GigabitEthernet3/0/9    367977       367993       0            0           
 GigabitEthernet2/0/2    8066         7172         0            0           
 GigabitEthernet2/0/8    371414       371417       0            0         

LACP packets are properly exchanged.
3. Run the debug trunk lacp-pdu command.
Aug 30 2012 12:13:09.490.11+08:00 ME60 TRUNK/7/LACPDU:Slot=3;
 
--------------------LACP    PDU     DEBUG    MSG--------------------
Port:
GigabitEthernet3/0/9                                Type: Sent
 
Actor System Priority:           32768
Actor System Mac Address:        00-25-9e-db-5a-ff
Actor Port Key:                  561
Actor Port Priority:               32768
Actor Port :                      777--------
Sending interface
Actor State :                    1-1-1-1-0-0-0-0
Partner System Priority:         32768
Partner System Mac Address:      00-d0-d0-9d-5f-4c
Partner Port Key:                259
Partner Port Priority:             32768
Partner Port:                    112
Partner State:                   1-0-1-0-0-0-0-0
Actor Aggregation Delay:         0
-------------------------------------------------------------------
.
Aug 30 2012 12:13:09.490.12+08:00 ME60 TRUNK/7/MSG:Slot=3;Leaving function LAG_AGENT_ReceiveLacpFromMainBoard().
Aug 30 2012 12:13:09.590.1+08:00 ME60 TRUNK/7/MSG:Slot=3;Entering function LAG_SH_PKT_ReceiveLacpPacket().
Aug 30 2012 12:13:09.590.2+08:00 ME60 TRUNK/7/LACPDU:Slot=3;
 
--------------------LACP    PDU     DEBUG    MSG--------------------
Port:
GigabitEthernet3/0/9                             Type: Received
 
Actor System Priority:           32768
Actor System Mac Address:        00-d0-d0-9d-5f-4c
Actor Port Key:                  259
Actor Port Priority:               32768
Actor Port :                     112
Actor State :                    1-0-1-1-0-0-0-0
Partner System Priority:         32768
Partner System Mac Address:      00-25-9e-db-5a-ff
Partner Port Key:                561
Partner Port Priority:             32768
Partner Port:                    520---------
Receiving interface
Partner State:                   1-1-1-0-0-0-0-0
Actor Aggregation Delay:         0
-------------------------------------------------------------------

The sending interface is different from the receiving interface on the trunk interface.
4. Check the onsite optical path. The result shows that crossed pairs are connected on two Down member interfaces. The problem is solved after adjusting the crossed pairs.
Root Cause
The optical fibers are crossed on the interfaces.
Solution
Correctly connect optical fibers.

END