Virtual Private Wire Service (VPWS) Configuration Step by Step [GNS3 Lab]

VPWS Topology


VPWS Configuration

In this Lab, we assume that the Configuration of the MPLS Backbone is done. Please refer to This Article that covers the MPLS Configuration Step by Step guide.


In our topology, we will configure VPWS to cover the need of 2 separate Clients:

  • Customer A needs the subnet 192.168.1.0/24 to be layer 2 extended between its 2 branch sites through the ISP MPLS Backbone.
  • Customer B needs the subnet 192.168.2.0/24 to be layer 2 extended between its 2 branch sites through the ISP MPLS Backbone.


VPWS Configurations Occur on the MPLS LSR Edges (all Called PE, Provider EDGE).

The configuration is done in two-part:

  • Definition of the pseudoWire Class.
  • Configuration of the interfaces facing the clients devices.


I- Definition of the pseudoWire Class


On PE-1:

pseudowire-class CE1_CE2_CustA
 encapsulation mpls
 interworking ethernet

pseudowire-class CE1_CE2_CustB
 encapsulation mpls
 interworking ethernet


On PE-2:

pseudowire-class CE1_CE2_CustA
encapsulation mpls
interworking ethernet

pseudowire-class CE1_CE2_CustB
encapsulation mpls
interworking ethernet




II- Configuration of the interfaces facing the clients devices


On PE-1:

int f0/0
xconnect 10.10.14.1 310 encapsulation mpls pw-class CE1_CE2_CustA
no sh

!

int f1/0
xconnect 10.10.14.1 320 encapsulation mpls pw-class CE1_CE2_CustB
no sh


On PE-2:

int f0/1
xconnect 10.10.13.1 310 encapsulation mpls pw-class CE1_CE2_CustA
no sh

!

int f1/0
xconnect 10.10.13.1 320 encapsulation mpls pw-class CE1_CE2_CustB
no sh




VPWS Verificatins

on PE-1:

PE-1#show mpls l2transport vc

Local intf     Local circuit              Dest address    VC ID      Status
-------------  -------------------------- --------------- ---------- ----------
Fa0/0          Ethernet                   10.10.14.1      310        UP
Fa1/0          Ethernet                   10.10.14.1      320        UP

--------------

PE-1#show mpls l2transport binding
  Destination Address: 10.10.14.1,VC ID: 310
    Local Label:  21
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
    Remote Label: 21
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
  Destination Address: 10.10.14.1,VC ID: 320
    Local Label:  22
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
    Remote Label: 22
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]



on PE-2:


PE-2#show mpls l2transport vc

Local intf     Local circuit              Dest address    VC ID      Status
-------------  -------------------------- --------------- ---------- ----------
Fa0/1          Ethernet                   10.10.13.1      310        UP
Fa1/0          Ethernet                   10.10.13.1      320        UP

-------------------

PE-2#show mpls l2transport binding
  Destination Address: 10.10.13.1,VC ID: 310
    Local Label:  21
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
    Remote Label: 21
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
  Destination Address: 10.10.13.1,VC ID: 320
    Local Label:  22
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]
    Remote Label: 22
        Cbit: 1,    VC Type: Ethernet,    GroupID: 0
        MTU: 1500,   Interface Desc: n/a
        VCCV: CC Type: CW [1], RA [2], TTL [3]
              CV Type: LSPV [2], BFD/Raw [5]



We can check ping between Customers Branches:

  • Customer A:
PC1> show ip

NAME        : PC1[1]
IP/MASK     : 192.168.1.1/24
GATEWAY     : 0.0.0.0
DNS         :
MAC         : 00:50:79:66:68:00
LPORT       : 10060
RHOST:PORT  : 127.0.0.1:10061
MTU:        : 1500

PC1> ping 192.168.1.2
84 bytes from 192.168.1.2 icmp_seq=1 ttl=64 time=120.703 ms
84 bytes from 192.168.1.2 icmp_seq=2 ttl=64 time=136.476 ms
84 bytes from 192.168.1.2 icmp_seq=3 ttl=64 time=123.387 ms
  • Customer B:
PC3> show ip

NAME        : PC3[1]
IP/MASK     : 192.168.2.1/24
GATEWAY     : 0.0.0.0
DNS         :
MAC         : 00:50:79:66:68:02
LPORT       : 10062
RHOST:PORT  : 127.0.0.1:10063
MTU:        : 1500

PC3> ping 192.168.2.2
84 bytes from 192.168.2.2 icmp_seq=1 ttl=64 time=120.093 ms
84 bytes from 192.168.2.2 icmp_seq=2 ttl=64 time=121.173 ms

Bilel Ameur

Enthusiastic Network Engineer specializing in Cisco ACI, passionate about solving challenges. A lifelong learner who loves gaining and sharing knowledge. Profile: https://www.linkedin.com/in/bilel-ameur-71116b2b5
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x