VPWS (Virtual Private Wire Service) – Fpipe, Apipe and Cpipe Configuration

VPWS Configuration Examples

In the previous articles, we have seen Epipe Configuration Examples,  Local Epipe and Distributed Epipe Configurations. Here, we will focus on another VPWS types, Fpipe, Apipe and Cpipe.

Fpipe Configuration

VPWS Fpipe Configuration is similar to Epipe Configuration with some differences. These differences are given below:

• Configured Service Type is “Fpipe”
• SAP encapsulation is SONET for “Frame Relay”
• SAP configuration form is like port:DLCI (1/1/1 : 30)

DLCI is a specific Frame-Relay term that refer to the Frame-Relay virtual circuit.

Fpipe Configuration Example

As an example, for a Distributed configuration topology, VPWS Fpipe Configuration will be like below:

Router # configure service

Apipe Configuration

VPWS Apipe Configuration is also similar to Epipe Configuration with some differences. These differences are given below:

• Configured Service Type is “Apipe”
• SAP encapsulation is SONET for “ATM”
• SAP configuration form is like port:VP/VC (1/1/1 : 0/100)

VP/VC is a specific ATM term that refer to the ATM virtual circuit.

Apipe Configuration Example

As an example, for a Distributed configuration topology, VPWS Apipe Configuration will be like below:

Router # configure service

Cpipe Configuration

VPWS Cpipe Configuration is also similar to Epipe Configuration with some differences. These differences are given below:

• Configured Service Type is “Cpipe”
• SAP encapsulation is SONET for “TDM” (BCP-null OR BPC-dot1q)
• SAP configuration form is changes depending on the vc-type used like: 1/1/1:2.16.1

One more type is Ipipe. This is the interworking of diferent types each other. One node is one type and the other is another. This type will be discussed in a different article.

This article series are the overview of the configuration of VPWS services. I hope this artciles will be helpful for you.