Epipe

An Epipe service is a Layer 2 point-to-point service that encapsulates and transports customer data across a service provider's IP or MPLS network. This service is completely transparent to the customer data and protocols. The Epipe service does not perform any MAC learning. A local Epipe service comprises two SAPs on the same node, whereas a distributed Epipe service consists of two SAPs on different nodes. SDPs are not used in local Epipe services.

See "Ethernet pipe service" in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide for detailed information about Epipe.

See Epipe for information about relevant show commands.

The following figure shows the Epipe topology used in this example.

Figure 1. Epipe topology used in this example

An Epipe will be created to establish communication between the two CE devices. LDP will be used as the tunneling protocol.

See LDP for information about LDP configuration.

Configuration

CE-facing port configuration on PE1 and PE3:

/configure port 1/1/c10/1 admin-state enable
/configure port 1/1/c10/1 ethernet mode access
/configure port 1/1/c10/1 ethernet encap-type dot1q
/configure port 1/1/c10/1 ethernet mtu 5000

SDP configuration on PE1:

/configure service sdp 510 admin-state enable
/configure service sdp 510 delivery-type mpls
/configure service sdp 510 ldp true
/configure service sdp 510 far-end ip-address 10.10.10.3

SDP configuration on PE3:

/configure service sdp 511 admin-state enable
/configure service sdp 511 delivery-type mpls
/configure service sdp 511 ldp true
/configure service sdp 511 far-end ip-address 10.10.10.1

ACL configuration on PE1:

/configure filter ip-filter "Epipe-ACL" filter-id 101
/configure filter ip-filter "Epipe-ACL" entry 10 match protocol icmp
/configure filter ip-filter "Epipe-ACL" entry 10 match dst-ip address 192.168.10.2
/configure filter ip-filter "Epipe-ACL" entry 10 match dst-ip mask 255.255.255.255
/configure filter ip-filter "Epipe-ACL" entry 10 action accept

Epipe configuration on PE1:

/configure service epipe "Epipe-VLAN100" admin-state enable
/configure service epipe "Epipe-VLAN100" description "Epipe-CEA1-VLAN100-CEZ1-VLAN100"
/configure service epipe "Epipe-VLAN100" service-id 10
/configure service epipe "Epipe-VLAN100" customer "1"
/configure service epipe "Epipe-VLAN100" spoke-sdp 55:100 { }
/configure service epipe "Epipe-VLAN100" sap 1/1/c10/1:100 ingress qos sap-ingress policy-name "CE-ingress-QoS"
/configure service epipe "Epipe-VLAN100" sap 1/1/c10/1:100 ingress filter ip "Epipe-ACL"
/configure service epipe "Epipe-VLAN100" sap 1/1/c10/1:100 egress qos sap-egress policy-name "CE-egress-QoS"

Epipe configuration on PE3:

/configure service epipe "Epipe-VLAN100" admin-state enable
/configure service epipe "Epipe-VLAN100" description "Epipe-CEA1-VLAN100-CEZ1-VLAN100"
/configure service epipe "Epipe-VLAN100" service-id 10
/configure service epipe "Epipe-VLAN100" customer "1"
/configure service epipe "Epipe-VLAN100" spoke-sdp 511:100 { }
/configure service epipe "Epipe-VLAN100" sap 1/1/c10/1:100 { }

See QoS for information about respective QoS configuration.

Customer verification

docker exec -it cea bash

Ping CEZ VLAN 100 from CEA:

└──> ping -c 100 -Q 34  192.168.10.2
PING 192.168.10.2 (192.168.10.2) 56(84) bytes of data.
64 bytes from 192.168.10.2: icmp_seq=1 ttl=64 time=10.3 ms
64 bytes from 192.168.10.2: icmp_seq=2 ttl=64 time=5.03 ms
64 bytes from 192.168.10.2: icmp_seq=3 ttl=64 time=5.07 ms

--- 192.168.10.2 ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 5.030/6.805/10.316/2.482 ms

While the ping is in progress, check the SAP, ACL, and QoS statistics.