Configuring a VPWS

• This module will offer an introduction to configuring a VPWS on the Nokia

7750 SR platform.

• This module assumes the reader is familiar with the SR platform’s service
architecture.

• This module also assumes the reader is familiar with switching, label-
switching, and routing.

• RFC 4447 - Pseudowire Setup and Maintenance Using the Label Distribution
Protocol (LDP)
• https://tools.ietf.org/html/rfc4447
 • Subscriber not shown – The end user.
• SAP (Service Access Point) not shown – The interface that connects the subscriber to
the Service Provider.
• Customer ID – A unique value used to group services together.
• Service ID – A unique value used to identify the service.
• SDP (Service Distribution Point) – A logical representation of the transport tunnel
emulating a direct connection to a far-end PE router.
• Transport Tunnel – The LSP used to transport service data; labels signaled by L-LDP.
• Service Tunnel – Represented by service labels; labels signaled by T-LDP or BGP-LU.
• Demultiplex – The act of decapsulating data arriving at the egress PE router;
Customer ID typically a ‘POP’ operation of MPLS.

Service Tunnel
(Demultiplex) (Signaled
via T-LDP or
SDP
BGP-LU/MP-BGP) Transport
Tunnel
Service (e.g. VPWS, VPLS) (Signaled via
L-LDP, RSVP-
TE, or GRE)
Service Tunnel
(Signaled
Service ID SDP SDP
via T-LDP or
VCID BGP-LU/MP-BGP)
 Subscriber Network
Demarcation Point
(Subscriber vs. Service Provider)
N1

SW1
Fa1/0
(802.1q Trunk) 1/1/5:10
R1
Gi0/0.10 Fa1/15
10.0.0.0/31 (802.1q Trunk)

Service Provider
IP/MPLS
N6

SW2

Fa1/0
(802.1q Trunk) 1/1/5:10
R2
Gi0/0.10 Fa1/15
10.0.0.1/31 (802.1q Trunk)
 Service Provider Network

SD Service Service SD
Transpor Tunnel Tunnel Transpor
P Service (epipe) P
t Tunnel VC-ID: VC-ID: t Tunnel
87 87871
87
87871

N1 N6
Service Tunnel … SDP 87

Transpo
Transport Transport Transport Transport
rt
Tunnel Tunnel Tunnel Tunnel
Tunnel

N2 N3 N4 N5
 Multiplex Demultiplex

Transport Service Customer Transport Service Customer

Label: 101 Label: 87 Payload Label: 505 Label: 87 Payload

N1 N6 Customer
Payload

1/1/5:10 N2 N5 1/1/5:10
R1 R2
Gi0/0.10 Gi0/0.10

Customer
Payload

Transport Service Customer Transport Service Customer

Label: 202 Label: 87 Payload Label: 404 Label: 87 Payload

N3 N4
 VPWS Configuration (from the persepective of N1)

configure port 1/1/5 1. Configure the subscriber’s SAP. Physical port

shutdown “1/1/5” is configured as an access port, accepting
ethernet mode access vlan tags (or 802.1q encapsulation).
ethernet encap-type dot1q
no shutdown

configure service customer 10 create 2. Configure the Customer ID. All of this
contact admin@SubA.com subscriber’s services will be grouped by the
description “Subscriber A, Inc." Customer ID of “10.”
phone 864-999-9999

configure service sdp 87 create mpls
far-end 6.6.6.6
ldp
no shutdown
configure service epipe 87 customer 10 create
description “Epipe service for Subscriber A,
Inc."
sap 1/1/5:10 create no shutdown
spoke-sdp 87:87871 create no shutdown
3. Configure the SDP. SDP “87” represents the T-LDP
session. We specify “MPLS” as the delivery method,
and enable LDP-signalled LSPs.
4. Configure the Service. Service ID “87” will represent
the epipe for the subscriber configured with the
Customer ID of “10.”
5. Bind the SAP. This service will utilize physical port
“1/1/5,” with a service-delimiting vlan tag of “10.”
6. Configure the psuedowire. The spoke-sdp is our
psuedowire, in the format of <SDP-ID:VC-ID>. The
VC-ID of “87871” must match on both ends.
 Goals
• Create a subscriber network connecting to the Service Provider.
• R1: 10.0.0.0/31
• R2: 10.0.0.1/31
• 802.1q: 10
• Create a Customer to host the Subscriber’s service.
• Create a SDP between Provider Edge routers (N1 and N6).
• Create an epipe Service for the Subscriber.
• Bind the Subscriber’s SAP to their service.
• Create a psuedowire through the SDP.
• Verify the service label’s redistribution.
• Verify the service’s operational status through the following OAM commands:
• oam sdp-ping
• oam sdp-mtu
• oam svc-ping
• oam vccv-ping
• oam vccv-trace
• Ping R2, from R1; ensure R1 has a valid entry for R2’s MAC address in its ARP table.