Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

mesh-group (Protocols VPLS)

Syntax

Hierarchy Level

Description

Specify the virtual private LAN service (VPLS) mesh group. The statement options allow you to specify each provider edge (PE) device that is a member of the mesh group. This statement is also used in the configuration of inter-autonomous system (AS) VPLS with media access control (MAC) operations.

When you configure mesh groups on the ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024X routers, you must also enable the system profile by including the set system packet-forwarding-options system-profile vpls-meshgroups statement on the ACX router. Upon issue of this command, the packet forwarding engine (PFE) restarts.

The ACX7000 routers have the following limitations when you configure hierarchical VPLS (H-VPLS) mesh groups:

  • Control word for EVPN MPLS multihoming is not supported.

  • Penultimate Segment Pop (PSP) on SRv6 is not supported.

  • VXLAN stitching is not supported.

  • Up to 3 mesh-groups with no-local switching in a single VPLS routing instance.

  • A total maximum of 14 mesh-groups with either local switching or no-local switching per routing instance.

When you configure hot-standby redundant pseudowires in an H-VPLS hub-and-spoke network, we recommend that you also enable vpls-hot-standby-convergence. With VPLS hot-standby convergence, the device advertises two different labels (L1 and L2 ) to its neighbors. The device sends the L1 advertisement to the primary neighbor and the L2 advertisement to the backup neighbor. This allows a spoke device to differentiate between messages sent by the primary pseudowire node from messages sent by the backup pseudowire node. This reduces traffic sent and improves network convergence when there is a transition from the primary pseudowire to the backup pseudowire. To enable VPLS hot-standby convergence, include vpls-hot-standby-convergence at the [edit routing-options forwarding-table] hierarchy level on all the spoke devices.

Note:

You can configure the no-local-switching option at the [edit routing-instances routing-instance-name] or the [edit logical-systems logical-system-name routing-instances routing-instance-name] hierarchies to disable local switching in a routing instance with VPLS.

If you set this option, you can’t set the local-switching option under a VPLS mesh group to enable local switching only for a particular VPLS mesh group. The instance-level no-local-switching statement overrides the per-mesh-group local-switching setting.

Options

mesh-group-name—Name of the VPLS mesh group.

The remaining statements are explained separately. See CLI Explorer.

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 9.0.

local-switching, mac-tlv-receive, mac-tlv-send, and peer-as options introduced in Junos OS Release 9.3.

pseudowire-status-tlv and mac-flush options introduced in Junos OS Release 10.0.

route-distinguisher, vrf-export, vrf-import, and vrf-target options introduced in Junos OS Release 11.2.

hot-standby-vc-on and interface interface-name options introduced in Junos OS Release 15.1R2.

Support for this statement was introduced in Junos OS Evolved Release 24.1R1 for ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024 Routers.