This chapter contains configurations for Virtual Private LAN Service (VPLS).

The examples show the minimum configuration required for enabling a VPLS Mesh peer between PE1, PE2, and PE3 in raw mode.

Verify VPLS Session

Verify VPLS Mesh Peer

The examples show the minimum configuration required for enabling a VPLS Mesh peer between PE1, PE2, and PE3 in Tagged Mode. In the below example PE1 and PE2 uses VLAN 10 for binding the VPLS instance to the attachment circuit and PE3 used VLAN 20 where it shows that VLAN swapping is supported.

This is to validate the multiple match criteria support in a service template. When multiple match statements are configured only rewrite push is supported, rewrite translate and pop are not supported.

Verify VPLS Session:

Verify VPLS Mesh Peer:

This example below shows number of configured VPLS instances.

The example below shows the Count of VPLS from LDP standpoint

The example below shows the number of MAC addresses learned by VPLS.

In VPLS Hierarchy, multiple attachment circuits (AC) can be configured per few VPLS instances and AC-AC traffic blocking is not supported.Thus,when the PE router receives a broadcast, multicast, or unknown unicast packet on an AC.It sends the packet out on all other attachment circuits to all other CE devices participating in that VPLS instance.

To avoid this problem of a packet looping in the provider core, the PE devices enforce a "split-horizon" principle for the VPLS instances. That means the traffic will not flood if AC1 and AC2 are in same split horizon group.

The examples show the minimum configuration required for enabling a VPLS Mesh peer between PE-1, PE-2 with split horizon group. In the below example PE-1 and PE-2 uses split horizon groups where traffic can't be forwarded between the ACs if they are part of same access groups.But can send/receive from network ports.

Virtual Private LAN Service (VPLS) LDP signaling is a mechanism used to establish and manage pseudowires (PWs) in a VPLS network. VPLS allows geographically dispersed sites to share a common Ethernet broadcast domain, enabling any-to-any communication between the sites as if they were all connected to the same local area network (LAN).

VPLS LDP signaling occurs when each PE has discovered the endpoints of the VPLS instance. PWs are established over MPLS tunnels between VPN sites to transparently transmit Layer 2 packets. With the ability to configure the VPLS type per peer, and with the VPLS type configured being forwarded to LDP only when there is a change in the VPLS type at the VPLS instance or per peer level, signaling behavior is more efficient. Previously, the VPLS type at the VPLS instance was significant across all PEs involved in the VPLS instance.

If there is a change in the VPLS type at the VPLS instance or per peer level, NSM will update LDP, triggering LDP signaling. If there is no change, there is no need for re-signaling, and the VPLS session remains in the same state. The VPLS type configured on PEs at both ends of a pseudowire must match; otherwise, negotiation is required, and the VPLS session will be inactive until resolved.

Provide the ability to configure the VPLS type on a per-peer basis, in addition to the VPLS type set across all PEs in the VPLS instance. The VPLS type configured on PEs at both ends of a pseudowire must match; otherwise, negotiation should occur. The per-peer VPLS type should take priority when both the VPLS instance type and the per-peer type are configured.

The examples show the minimum configuration required for enabling a VPLS Mesh peer between PE1, PE2, and PE3 in per peer VPLS-type Signaling.

The VPLS BGPSignaling feature enables you to use BGP as the control plane protocol for both auto discovery and signaling in accordance with RFC 4761

Use this command to validate the Per peer VPLS-type signaling.

Verify VPLS Mesh Peer

Virtual Private LAN Service (VPLS) is a Layer 2 VPN technology that allows geographically dispersed sites to share an Ethernet broadcast domain by connecting them through a service provider's MPLS network. This effectively creates a single, bridged Ethernet LAN across multiple sites.

VPLS with Tunnel-IDs provides a robust solution for extending Ethernet LAN services over a wide area network. The use of Tunnel-IDs ensures efficient and reliable delivery of Ethernet frames across the MPLS core, enabling service providers to offer high-quality, scalable, and flexible VPN services to their customers.

Tunnel-IDs in VPLS are essential for efficient and reliable operation due to their unique identification, support for scalability, dynamic allocation by protocols like LDP or BGP, and compatibility with various signaling methods. They enable precise traffic engineering and load balancing, enhance resilience through fast reroute mechanisms and redundancy, and improve security with traffic isolation and access control. Additionally, Tunnel-IDs facilitate network management and monitoring by providing visibility into network paths and performance metrics, and they ensure compatibility with existing infrastructure for seamless integration of new services.

The examples show the minimum configuration required for enabling a VPLS Tunnel-ID between PE1, PE2, and PE3.

The VPLS Tunnel-ID feature enables you to use BGP as the control plane protocol for both auto discovery and signaling in accordance with RFC 4761

Use this command to validate the Per peer VPLS-type signaling.

Verify VPLS Mesh Peer

Virtual Private LAN Service (VPLS) is a Layer 2 VPN technology that allows geographically dispersed sites to share a common Ethernet broadcast domain, functioning as if they were all connected to the same LAN. This setup enables any-to-any communication between sites, providing the appearance of a single, cohesive LAN across multiple locations.

VPLS - Tunnel-Name is a configuration element within a VPLS network that is used to identify and manage MPLS tunnels. When configuring a VPLS instance on a network device, the Tunnel-Name is assigned to each MPLS tunnel. This can typically be done in the device’s CLI under the VPLS configuration mode.

The "VPLS - Tunnel-Name" is a vital element in the configuration and management of VPLS networks. By providing unique identifiers for MPLS tunnels, it enhances the organization, management, and troubleshooting of VPLS instances, ultimately leading to more efficient and reliable network operations.

The VPLS - Tunnel-Name feature in a VPLS network enhances functionality, manageability, and efficiency by providing unique identification for MPLS tunnels, simplifying network management, and improving troubleshooting. It allows granular control over configurations and policies, supports scalability and future network expansions, enhances security through controlled access and traffic isolation, and ensures redundancy and reliability by managing backup tunnels effectively. Additionally, it streamlines operations and reduces configuration errors, making it an essential tool for maintaining robust and reliable VPLS networks.

The examples show the minimum configuration required for enabling a VPLS Tunnel-Name between PE1, PE2, and PE3.

The VPLS Tunnel-Name feature enables you to use BGP as the control plane protocol for both auto discovery and signaling in accordance with RFC 4761

Use this command to validate the Per peer VPLS-type signaling.

Verify VPLS Mesh Peer