Virtual Private LAN Service (VPLS) is one of the most widely deployed Layer 2 VPN technologies in service provider networks. While EVPN has become the modern successor, VPLS remains in active production across thousands of service provider deployments worldwide. Understanding how to configure and verify VPLS on OcNOS is essential for network engineers working in brownfield SP environments.
This guide builds a complete VPLS deployment from the ground up: OSPF underlay, LDP label distribution, and VPLS pseudowire configuration, with verification commands at each stage.
Network Topology

Step 1: Configure OSPF Underlay
OSPF provides the IP reachability between PE routers. On OcNOS, enable OSPF with network statements under the process, set the core links to point-to-point (this eliminates DR/BDR election), and mark the loopback passive. The core interface also carries MPLS, so label-switching and per-interface LDP are enabled on it as well.
! OcNOS: OSPF underlay on R1 (all PEs use the same config pattern)
!
router ospf 1
router-id 10.10.100.1
passive-interface lo enable
network 10.10.100.1/32 area 0.0.0.0
network 192.168.12.0/24 area 0.0.0.0
network 192.168.13.0/24 area 0.0.0.0
!
interface ce0
ip address 192.168.12.1/30
mtu 9216
label-switching
mpls ldp-igp sync ospf holddown-timer 30
ip ospf network point-to-point
enable-ldp ipv4
!
interface lo
ip address 127.0.0.1/8
ip address 10.10.100.1/32 secondary
ipv6 address ::1/128
!
commit
!
! Verify OSPF neighbors:
show ip ospf neighbor
! Expected: R2 and R3 in FULL state
!
! Verify loopback reachability to the remote PEs:
show ip route ospf
Step 2: Enable LDP for Label Distribution
LDP binds MPLS labels to OSPF-learned prefixes, building the Label Switched Paths (LSPs) that VPLS pseudowires ride over. On OcNOS the LDP process is configured under router ldp, and LDP is turned up on each core link with enable-ldp ipv4 alongside label-switching (both already shown on interface ce0 in Step 1).
! OcNOS: LDP configuration on R1
!
router ldp
router-id 10.10.100.1
transport-address ipv4 10.10.100.1
!
commit
!
! Per-interface LDP is enabled on the core links (see interface ce0 in Step 1):
! label-switching
! enable-ldp ipv4
!
! Verify LDP session state (R2 and R3 should be OPERATIONAL):
show ldp session
!
! Verify the label-switched paths to the PE loopbacks:
show mpls forwarding-table
Step 3: Configure VPLS
VPLS creates a virtual Ethernet switch across the MPLS network. Each PE maintains LDP-signaled pseudowires to all other PEs in the VPLS instance, forwarding frames based on MAC learning, exactly like a physical Ethernet switch, but over MPLS. On OcNOS the instance is defined globally with mpls vpls <name> <vpls-id>, LDP signaling and each remote PE are declared inside it, and the CE-facing access port is bound with mpls-vpls <name>.
! OcNOS: VPLS configuration on R1
! VPLS-ID 100 connects CE-A (R1), CE-B (R3) and CE-C (R2) in one L2 broadcast domain
!
mpls vpls VPLS100 100
signaling ldp
!
! Pseudowire to R2 (PE2)
vpls-peer 10.10.100.2
!
! Pseudowire to R3 (PE3)
vpls-peer 10.10.100.3
!
! Bind the CE-facing access port into the VPLS instance
interface ce2
access-if-vpls mpls-vpls VPLS100
!
commit
!
! Verify the VPLS instance and pseudowire status:
show mpls vpls
! Expected: both peers UP (VC Type: Ethernet)
!
! Verify the VC table and assigned VC labels:
show mpls vc-table
Step 4: Verify End-to-End Connectivity
! OcNOS: End-to-end VPLS verification
!
! Confirm the MPLS forwarding entry toward a remote PE:
show mpls forwarding-table
!
! Confirm the VPLS instance and both pseudowires are up:
show mpls vpls
!
! Confirm the VC table shows both peers with assigned VC labels:
show mpls vc-table
!
! Confirm the LDP-signaled L2 circuit to each remote PE:
show ldp mpls-l2-circuit
VPLS vs. EVPN: When to Use Each
| Capacità | VPLS | EVPN |
|---|---|---|
| MAC learning | Data plane (flooding) | Control plane (BGP) |
| Multi-homing | Complex (H-VPLS) | Native (EVPN MH) |
| BUM traffic | Flood-and-learn | Selective multicast |
| Fast convergence | Limited | Mass withdrawal + aliasing |
| L3 integration | Separate L3VPN needed | EVPN IRB (native) |
| Brownfield fit | Excellent | Good (with SR underlay) |
VPLS remains the right choice for brownfield deployments where EVPN migration is not yet planned. For new deployments, EVPN-ELAN delivers the same multipoint L2 service with superior scalability and faster convergence.
- EVPN-ELINE: Point-to-Point L2VPN over ISIS-SR
- EVPN-ELAN: Multipoint L2VPN over ISIS-SR
- LDP to SR Migration Guide
- OcNOS-SP Product Page
- Contatta IP Infusion
IP Infusion Engineering Team
Approfondite. Portatelo con voi.
Il datasheet di prodotto e download tecnici e sintetici che vanno oltre questa pagina.
Datasheet OcNOS-SP
Specifica completa di OcNOS-SP: il set di funzionalità access, cell site e aggregazione, gli SKU software, le piattaforme hardware supportate e la guida all'ordine della soluzione.
Ottieni il datasheetUpgrade SR-MPLS con OcNOS
Migri SR-MPLS su OcNOS con hardware open: Flex-Algo, TI-LFA e un percorso di cutover comprovato come alternativa a Cisco.
Scarica il briefTrasporto WAN cloud & service provider
Trasporto WAN per cloud e service provider su hardware aperto: SR-MPLS, EVPN e forwarding testato su scala.
Scarica il briefDatasheet OcNOS-SP
Modulo rapido. Il suo PDF si apre in una nuova scheda subito dopo l'invio.
✓ Apertura del suo PDF in una nuova scheda…
Se non si è aperto, utilizzi il link qui sotto.
Upgrade SR-MPLS con OcNOS
Modulo rapido. Il suo PDF si apre in una nuova scheda subito dopo l'invio.
✓ Apertura del suo PDF in una nuova scheda…
Se non si è aperto, utilizzi il link qui sotto.
Trasporto WAN cloud & service provider
Modulo rapido. Il suo PDF si apre in una nuova scheda subito dopo l'invio.
✓ Apertura del suo PDF in una nuova scheda…
Se non si è aperto, utilizzi il link qui sotto.