Establish LACP via VPLS network failed

Created: Apr 26, 2017 08:32:47Latest reply: Apr 26, 2017 09:57:58 1094 1 0 0

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.

27cf6d944b5648fdb5fff917ba1ddc44


  • x
  • convention:

ms.america  Visitor   Created Apr 26, 2017 09:57:58 Helpful(0) Helpful(0)

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:

[clientswitch1]l2protocol-tunnel lacp group-mac 0100-0100-0100

[clientswitch1]interface GigabitEthernet0/0/19
[clientswitch1- GigabitEthernet0/0/19] port hybrid pvid vlan 3023
[clientswitch11- GigabitEthernet0/0/19] l2protocol-tunnel lacp enable

On switch clientswitch2:
[clientswitch2]l2protocol-tunnel lacp group-mac 0100-0100-0100

[clientswitch2]interface GigabitEthernet0/0/8
[clientswitch2- GigabitEthernet0/0/8] port hybrid pvid vlan 3023
[clientswitch2- GigabitEthernet0/0/8] l2protocol-tunnel lacp enable

72b3211597874ae2a91ff63ec715c368

C.Set default VLAN of CE downlink to 3023 and enable smart QINQ which will tag LACP packet with 3023.

87b63efc29b6409f948856a519d230a6

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.  7375c6df96c24ef293146cdf68a3d1d6


 

transparent.gif Root Cause
transparent.gif Solution
Solution 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. 

  • x
  • convention:

Reply

Reply
You need to log in to reply to the post Login | Register

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
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

Login and enjoy all the member benefits

Login
Fast reply Scroll to top