Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

L2VPN connection between MX and EX is up but not forwarding traffic



Article ID: KB30709 KB Last Updated: 22 Jan 2016Version: 1.0

This article describes the Layer 2 virtual private network (L2VPN) connection problem between MX Series routers and EX Series switches in a BGP-signaled L2VPN network.


An L2VPN connection between an MX480 and EX4550 is up, but not forwarding the data traffic between CE to CE.

> ping mpls l2vpn instance L2VPN local-site-id 1 remote-site-id 2
 --- lsping statistics ---
 5 packets transmitted, 0 packets received, 100% packet loss

The BGP-signaled L2VPN control plane is up in both the MX and EX devices, but the ping fails between CE to CE, which points to a forwarding plane issue.


To resolve this issue, configure the no-control-word knob under VPLS instances on the EX switch and MX router.

On networks with equipment that does not support the control word, you can disable it by including the no-control-word statement:

set routing-instances L2VPN protocols l2vpn no-control-word

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search