Study guide

10.2 Layer 2 Services: VPWS/VLL and VPLS

Nokia Network Routing Specialist I NRS I, 4A0-100

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: OSI and TCP/IP Networking Models

1.1 OSI Reference Model and Layer Functions 1.2 TCP/IP Protocol Stack and Data Encapsulation 1.3 Network Architecture and Device Planes

2 Chapter 2: Ethernet Technology and LAN Switching

2.1 Ethernet Framing and Physical Standards 2.2 Bridging, Switching, and Collision/Broadcast Domains 2.3 VLANs and IEEE 802.1Q Tagging 2.4 Ethernet Redundancy, Spanning Tree, and LAGs

3 Chapter 3: IP Addressing and Subnetting

3.1 IPv4 Addressing Architecture and Classes 3.2 IPv4 Subnetting, CIDR, and VLSM 3.3 IPv6 Addressing Fundamentals 3.4 IP in Homes and Small Businesses

4 Chapter 4: IP Forwarding and Host Resolution

4.1 IPv4 Header Architecture and Packet Forwarding 4.2 Address Resolution Protocol (ARP) and IPv6 Neighbor Discovery 4.3 ICMP and Network Troubleshooting

5 Chapter 5: Nokia Service Router Hardware and Management

5.1 Nokia Service Router Hardware Architecture 5.2 SR OS Classic CLI Navigation and Operations 5.3 Model-Driven CLI (MD-CLI) and Datastore Management 5.4 Boot Process and Configuration Recovery

6 Chapter 6: Routing Fundamentals and Static Routing

6.1 Routing Concepts, RIB vs FIB, and Route Preference 6.2 Static Route Configuration and Next-Hop Resolution 6.3 Dynamic Routing Protocols Overview

7 Chapter 7: Interior Gateway Protocols: OSPF and IS-IS

7.1 OSPF Fundamentals and Adjacency Formation 7.2 OSPF Multi-Area Architecture and LSA Types 7.3 IS-IS Protocol Architecture and Operations

8 Chapter 8: BGP and Internet Architecture

8.1 BGP Architecture and Peering 8.2 BGP Path Attributes and Route Selection 8.3 IBGP Split-Horizon and Scaling Solutions 8.4 Internet Components, Peering, and Transit

9 Chapter 9: MPLS Architecture and Signaling

9.1 MPLS Concepts and Label Operations 9.2 Label Distribution Protocol (LDP) 9.3 RSVP-TE and Traffic Engineering

10 Chapter 10: Nokia VPN Services: Layer 2 and Layer 3

10.1 Nokia Service Architecture and Building Blocks 10.2 Layer 2 Services: VPWS/VLL and VPLS 10.3 Layer 3 Services: IES and VPRN

10.2 Layer 2 Services: VPWS/VLL and VPLS

Key Takeaways Explain This Topic AI

Epipe is point-to-point Ethernet transport without VPLS-style destination MAC learning.

VPLS bridges multiple attachments using a per-service FDB.

A VC-ID is 32 bits; an MPLS service label value is 20 bits.

Mesh split horizon requires end-to-end logical pseudowires, not direct physical cables between every PE.

A control word and label stack add overhead that must fit actual path and service MTUs.

Last updated: October 2026

Point-to-point or multipoint Ethernet?

Virtual Private Wire Service (VPWS) provides point-to-point service. Nokia's Virtual Leased Line terminology includes Epipe for Ethernet transport. Virtual Private LAN Service (VPLS) provides multipoint Ethernet bridging.

The customer determines the choice. Two attachment points needing a virtual Ethernet wire fit Epipe. Several sites needing one bridged Ethernet domain fit VPLS. A customer wanting the provider to route between site IP networks may instead need VPRN.

An Ethernet VPN service is not automatically encrypted. The provider must correctly separate services and apply suitable policies. Its forwarding model also determines whether customer MAC addresses are learned.

Epipe forwarding

A basic Epipe has two active attachment endpoints. It forwards frames between them without selecting among multiple destinations through a learned VPLS-style FDB. A local Epipe connects two local SAPs. A distributed Epipe connects a local SAP to a remote attachment through a pseudowire.

Other VLL names exist for different client technologies, such as Apipe for ATM and Cpipe for circuit emulation, with support depending on platform. Ipipe interworks supported access encapsulations. These names are not interchangeable Ethernet service choices.

For a distributed MPLS Epipe, targeted LDP can exchange pseudowire parameters and service labels between PEs. The VC-ID is a 32-bit identifier, while the MPLS label value is 20 bits inside a 32-bit stack entry. Labels need not have equal numeric values in the two directions.

  • An Epipe MD-CLI fragment
  • Use the supporting LabCustomer, access port, and SDP 10 from the preceding lesson: configure private
  • /configure service epipe "Epipe-A" service-id 100
  • /configure service epipe "Epipe-A" customer "LabCustomer"
  • /configure service epipe "Epipe-A" admin-state enable
  • /configure service epipe "Epipe-A" sap 1/1/3:100
  • /configure service epipe "Epipe-A" spoke-sdp 10:100
  • compare
  • validate
  • commit

At the remote PE, create the corresponding customer service, its access SAP, and a local SDP pointing back to the first PE. Bind the pseudowire using the same VC-ID 100 and compatible VC type, MTU, and control-word behavior. The remote local SDP ID and service name need not equal those on the first PE.

This fragment is illustrative and does not prove an operational end-to-end service. Check actual binding state and packet counters after configuring both endpoints.

Label stack and control word

A common distributed Epipe packet carries an outer transport label and an inner service label. The outer label reaches the egress PE; the inner label selects the egress pseudowire/service handling. Core transport termination can pop the outer label while leaving the service label.

An optional pseudowire control word sits between the service-label stack and customer payload when the service negotiates and uses it. It helps avoid mistaking the payload for IP during core hashing and can support sequencing mechanisms. It does not universally prevent all packet reordering.

Count overhead explicitly. Two MPLS entries add eight bytes; a four-byte control word adds another four. Customer Ethernet framing and the outer core link add other bytes. Compare actual service and path MTU definitions rather than copying one universal “required MTU.”

VPLS learning and flooding

VPLS emulates a distributed Ethernet bridge. Each service has its own Forwarding Database (FDB) mapping learned source MAC addresses to SAPs or remote attachments.

Known destination MACs use the relevant forwarding entry. Unknown unicast, broadcast, and applicable multicast traffic can be replicated to eligible attachments. Flooding still obeys ingress exclusion, split-horizon, filtering, and multicast optimizations.

Dynamic MAC entries age according to configured local and remote timers. A remembered MAC is not an ARP entry: the FDB maps MAC to attachment, while ARP maps an on-link IPv4 address to a MAC.

Mesh split horizon

In a conventional VPLS core mesh, a frame received over a mesh-SDP is not forwarded over another mesh-SDP in that service. Consequently, each participating core PE needs a logical pseudowire relationship to every other participating PE.

Four PEs require 4 × 3 / 2 = 6 pairwise pseudowires. This is a count of relationships, not physical core cables. Each LSP can cross multiple routers.

Spoke attachments can extend the service hierarchically, but redundant customer or spoke links can introduce loops. Do not disable all spanning-tree or access protection merely because the core mesh uses split horizon.

A VPLS MD-CLI fragment

Assume a separate provisioned access port 1/1/4 is configured in access mode with dot1q encapsulation. Reuse the customer and transport SDP: configure private

  • /configure service vpls "VPLS-A" service-id 200
  • /configure service vpls "VPLS-A" customer "LabCustomer"
  • /configure service vpls "VPLS-A" admin-state enable
  • /configure service vpls "VPLS-A" sap 1/1/4:200
  • /configure service vpls "VPLS-A" mesh-sdp 10:200
  • compare
  • validate
  • commit

The remote VPLS uses a matching VC-ID 200 for this relationship and its own local access attachment. Additional PEs require the appropriate mesh relationships, not simply another SAP on one existing PE.

Inspect show service id 100 sdp for the Epipe binding and show service id 200 fdb for VPLS learning. If a source MAC appears on an unexpected attachment, check cabling, SAP mapping, and loops. If service labels exist but traffic fails, check transport, MTU, access tags, and filters.

Primary references

Nokia VPLS documentation and pseudowire control protocol , checked October 20, 2026.

Compare the forwarding models

  • Property Epipe VPLS
  • Basic topology Two active attachment endpoints Multiple bridged attachments
  • MAC-learning decision No VPLS-style FDB lookup Per-service source learning and destination lookup
  • Remote attachment Spoke pseudowire in this model Mesh or hierarchical spoke design
  • Key failure evidence SAP, binding, transport, MTU Those dependencies plus FDB learning and loop controls