The topology is as following, customer want to establish lacp beteen "client switch1" and "client switch 2", but failed. Meanwhile normal ping from "client switch 1" and "client switch 2" is working.
Stay connected! Choose the types of newsletters you want to receive!
Establish LACP via VPLS network failed
Created: Apr 26, 2017 00:32:47Latest reply: Apr 26, 2017 01:57:58
1417
1
0
0
- x
- convention：
1.Checked the configuration on CE/PE and found that the basic configuration of VPLS is working, and the ping test between "client switch 1 " and "client switch 2" is working, which means the basic configuration is correct. 2.As we know LACP protocol packets is a kind of BPDU packets, which will be handled by CPU directly and will not transparant by switch. So we need to chance the mac-address of LACP to another one which will not be recognized as BPDU by switch. A.Set VPLS of Martini and let downlink sub-interface of PE device terminate the assigned VLAN 3023. B.Enable L2-protocol of LACP on downlink of CE and group MAC 0100-0100-0100. On switch clientswitch1: On switch clientswitch2:
C.Set default VLAN of CE downlink to 3023 and enable smart QINQ which will tag LACP packet with 3023.
D.Switches on both sides create eth-trunk with mode LACP to observe the status of LACP. LACP is setup successfully and its status is kept up.
 Root Cause SolutionSolution is to use command "l2protocol-tunnel lacp group-mac 0100-0100-0100" to change the mac-address of LACP to another one which is not BPDU. And the issue was resolved. |
|
Comment
Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
