Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring LDP Signaling for VPLS

    Like other Layer 2 VPNs, you must enable a VPLS instance to isolate VPLS traffic from other network traffic. An important element of a VPLS instance is the signaling protocol. You can configure BGP signaling, LDP signaling, or both BGP and LDP signaling in a VPLS instance.

    To configure LDP signaling, you must first enable a VPLS instance to isolate VPLS traffic from other network traffic. To enable a VPLS instance, include the instance-type vpls statement at the [edit routing-instances instance-name] hierarchy level. To configure LDP signaling within the instance, identify the virtual circuit with the vpls-id statement and specify the PE routers participating in the instance with the neighbor statement:

    [edit]
    routing-instances {instance-name {instance-type vpls; interface ge-0/1/0.0;protocols {vpls {vpls-id id-name;neighbor neighbor-id; # The neighbor-id should be the loopback address of # the remote PE router.}}}}

    To fully enable LDP signaling on a PE in a VPLS instance, you must also enable LDP on the loopback interface of the router. To enable LDP on the loopback interface, include the interface lo0.0 statement at the [edit protocols ldp] hierarchy level:

    [edit]
    protocols {ldp {interface lo0.0;}}

    For LDP signaling within a VPLS routing instance, the Junos OS supports the following values only:

    • FEC—FEC 128 and FEC 129
    • Control bit—0
    • Ethernet pseudowire type—0x0005
    • Ethernet tagged mode pseudowire type—0x0004

    Modified: 2017-03-10