Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

vpls-id-list (protocols vpls mesh-group)

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
vpls-id-list vc-id-numbers;

Hierarchy Level

content_copy zoom_out_map
[edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor address]

Description

The vpls-id-list option allows you to configure multiple pseudowires under LDP-VPLS neighbor by creating one pseudowire per virtual circuit id. This combination of neighbor and virtual circuit ID must be unique across the l2circuit and all local LDP-VPLS instances. The pseudowire will terminate in the specified mesh-group.

As with other pseudowires, the pseudowires created here will signal the remote PE via LDP label mapping message. For each pseudowire created under a neighbor, VPLS will create a VT/LSI interface and add both it and the and label route to the mpls.0 table. Note that you can create multiple pseudowires between the same pair of PEs in LDP-VPLS for a single routing instances only.

Enable local-switching along with vpls-id-list to allow local switching of traffic (including BUM traffic) between multiple pseudo wires. This can also eliminate the need to have a dedicated mesh-group for each LDP spoke pseudo wire (which has a limit of 14), and provide support for H-VPLS in EVP-LAN and EP-LAN topologies.

Options

vc-id-numbers—The virtual circuit ID for the PE pair. This ID can be any number in the range of 1 to 4294967295.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 14.2 .

footer-navigation