Epipe

Ethernet Pipe (Epipe)

It is a layer 2 point-to-point virtual leased line (VLL) service for ethernet frames. This is similar to what is commonly known as L2VPN.

Before I proceed with the configuration there are a few definitions which need to be understood.

Terms: Source Nokia Documentation

SDP: Service Distribution Point

A service distribution point (SDP) acts as a logical way to direct traffic from one router to another through a uni-directional (one-way) service tunnel. The SDP terminates at the far-end device which directs packets to the correct service egress SAPs on that device. A distributed service consists of a configuration with at least one SAP on a local node, one SAP on a remote node, and an SDP binding the service to the service tunnel.

  • An SDP has the following characteristics:
  • An SDP is locally unique to a participating routers. The same SDP ID can appear on other Alcatel-Lucent routers.
  • An SDP uses the system IP address to identify the far-end edge router.
  • An SDP is not specific to any one service or any type of service. Once an SDP is created, services are bound to the SDP. An SDP can also have more than one service type associated with it.
  • All services mapped to an SDP use the same transport encapsulation type defined for the SDP (either GRE or MPLS).
  • An SDP is a management entity. Even though the SDP configuration and the services carried within are independent, they are related objects. Operations on the SDP affect all the services associated with the SDP. For example, the operational and administrative state of an SDP controls the state of services bound to the SDP.

SAP: Service Access Point

A SAP identifies the customer interface point for a service on an ­Alcatel-Lucent/Nokia router. The SAP configuration requires that slot, XMA/MDA, and port/channel information be specified. The slot, XMA/MDA, and port/channel parameters must be configured prior to provisioning a service. Each customer is configured with at least one service access point.

Lab Diagram

7750%20Epipe

Objective

In this lab we will create a EPIPE between N1 and N6. All interfaces have been configured, IS-IS routing protocol is configured, LDP is also enabled on all the participating interfaces.

From N1 point of view we have reachability to N6.

*A:N1# show router route-table protocol isis 

===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags]                            Type    Proto     Age        Pref
      Next Hop[Interface Name]                                    Metric   
-------------------------------------------------------------------------------
2.2.2.2/32                                    Remote  ISIS      00h44m30s  18
       10.1.2.2                                                     5000
3.3.3.3/32                                    Remote  ISIS      00h34m35s  18
       10.1.2.2                                                     10000
4.4.4.4/32                                    Remote  ISIS      00h34m35s  18
       10.1.2.2                                                     15000
5.5.5.5/32                                    Remote  ISIS      00h34m35s  18
       10.1.2.2                                                     20000
6.6.6.6/32                                    Remote  ISIS      00h34m35s  18
       10.1.2.2                                                     25000
10.2.3.0/28                                   Remote  ISIS      00h44m30s  18
       10.1.2.2                                                     10000
10.3.4.0/28                                   Remote  ISIS      00h34m36s  18
       10.1.2.2                                                     15000
10.4.5.0/28                                   Remote  ISIS      00h34m36s  18
       10.1.2.2                                                     20000
10.5.6.0/28                                   Remote  ISIS      00h34m36s  18
       10.1.2.2                                                     25000
-------------------------------------------------------------------------------
No. of Routes: 9
Flags: n = Number of times nexthop is repeated
       B = BGP backup route available
       L = LFA nexthop available
       S = Sticky ECMP requested
===============================================================================

A ping from N1 to N6
*A:N1# ping 6.6.6.6 
PING 6.6.6.6 56 data bytes
64 bytes from 6.6.6.6: icmp_seq=1 ttl=60 time=14.5ms.
64 bytes from 6.6.6.6: icmp_seq=2 ttl=60 time=8.60ms.
64 bytes from 6.6.6.6: icmp_seq=3 ttl=60 time=20.3ms.
64 bytes from 6.6.6.6: icmp_seq=4 ttl=60 time=34.8ms.
64 bytes from 6.6.6.6: icmp_seq=5 ttl=60 time=26.7ms.

---- 6.6.6.6 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 8.60ms, avg = 21.0ms, max = 34.8ms, stddev = 9.16ms

LDP bindings for all the prefixes in the LSP
*A:N1# show router ldp bindings prefixes 

===============================================================================
LDP Bindings (IPv4 LSR ID 1.1.1.1:0)
             (IPv6 LSR ID ::[0])
===============================================================================
Legend: U - Label In Use,  N - Label Not In Use, W - Label Withdrawn
        WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
===============================================================================
LDP IPv4 Prefix Bindings
===============================================================================
Prefix                                      IngLbl                    EgrLbl
Peer                                        EgrIntf/LspId             
EgrNextHop                                                            
-------------------------------------------------------------------------------
1.1.1.1/32                                  131071U                     --
2.2.2.2:0                                     --                      
  --                                                                  

2.2.2.2/32                                    --                      131071
2.2.2.2:0                                   1/1/1                     
10.1.2.2                                                              

3.3.3.3/32                                  131068N                   131065
2.2.2.2:0                                   1/1/1                     
10.1.2.2                                                              

4.4.4.4/32                                  131067N                   131064
2.2.2.2:0                                   1/1/1                     
10.1.2.2                                                              

5.5.5.5/32                                  131066N                   131063
2.2.2.2:0                                   1/1/1                     
10.1.2.2                                                              

6.6.6.6/32                                  131065N                   131062
2.2.2.2:0                                   1/1/1                     
10.1.2.2                                                              

-------------------------------------------------------------------------------
No. of IPv4 Prefix Bindings: 6
===============================================================================

===============================================================================
LDP IPv6 Prefix Bindings
===============================================================================
Prefix                                      IngLbl                    EgrLbl
Peer                                        EgrIntf/LspId             
EgrNextHop                                                            
-------------------------------------------------------------------------------
No Matching Entries Found
===============================================================================

For the above output we can see that the Ingress label of N1 is being signaled to N2 which now knows that it is the egress label. Similarly N2 will generate an ingress label and specify an operation which will be SWAP and signal it to N3 which will store it in its Data Plane (LFIB) and it so goes on till N6.

The configuration

Now lets move to the configuration

Configuration on N1

*A:N1# configure service 
*A:N1>config>service# info 
----------------------------------------------
        sdp 87 mpls create
            far-end 6.6.6.6
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        customer 1 create
            description "Default customer"
        exit
        customer 10 create
            description "KAIMTech Inc."
            contact "admin@SubA.com"
            phone "647-299-9999"
        exit
        epipe 87 customer 10 create
            description "Subscriber A, Inc's Epipe"
            sap 1/1/5:10 create
            exit
            spoke-sdp 87:87871 create
                no shutdown
            exit
            no shutdown
        exit
----------------------------------------------

Configuration on N6

A:N6# configure service 
A:N6>config>service# info 
----------------------------------------------
        sdp 87 mpls create
            far-end 1.1.1.1
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit
        customer 1 create
            description "Default customer"
        exit
        customer 10 create
            description "KAIMTech Inc"
            contact "admin@SubA.com"
            phone "647-299-9999"
        exit
        epipe 87 customer 10 create
            sap 1/1/5:10 create
            exit
            spoke-sdp 87:87871 create
                no shutdown
            exit                      
            no shutdown
        exit
----------------------------------------------

Now let's check the Epipe status

*A:N1# show service service-using 

===============================================================================
Services 
===============================================================================
ServiceId    Type      Adm  Opr  CustomerId Service Name
-------------------------------------------------------------------------------
65           VPLS      Down Down 20         VPLS Instance for Subscriber B. In*
87           Epipe     Up   Up   10         
2147483648   IES       Up   Down 1          _tmnx_InternalIesService
2147483649   intVpls   Up   Down 1          _tmnx_InternalVplsService
-------------------------------------------------------------------------------
Matching Services : 4
-------------------------------------------------------------------------------
===============================================================================
* indicates that the corresponding row element may have been truncated.

As you can see that the service-id 87 is the EPIPE that I have configured and it is showing Admin UP and Operationally it is UP.

Validation:

To validate our configuration I have configured a sub-interface on R1 and R2 with encapsulation dot1q 10, have configured an IP 10.0.0.1/24 on R1 and 10.0.0.2/24 on R2. SW-1 and SW-2 interface is configured with vlan 10 and the physical interfaces connecting to R1 and N1 is configured as trunk, similarly on SW-2 the interface connected to R2 and N6 is configured as trunk allowing vlan 10 only.

A:N1# configure port 1/1/5 
A:N1>config>port# info 
----------------------------------------------
        ethernet
            mode access
            encap-type dot1q
        exit
        no shutdown
----------------------------------------------

!-- Similar configuration is done on N6 port 1/1/5

R1#ping 10.0.0.2      
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/14/20 ms

!-- A traceroute shows that 10.0.0.2 is one hop away.

R1#traceroute 10.0.0.2
Type escape sequence to abort.
Tracing the route to 10.0.0.2
VRF info: (vrf in name/id, vrf out name/id)
  1 10.0.0.2 15 msec 12 msec 11 msec

!-- I will shutdown this port on R1 Eth0/0 and ping from R2 to 10.0.0.1

R1(config)#interface ethernet 0/0
R1(config-if)#shutdown 

R2#ping 10.0.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

This test validates the end to end connectivity and that our L2 Epipe is working as intended.

I will unshut the port Eth0/0 on R1 and ping again from R2.

R1(config)#interface ethernet 0/0
R1(config-if)#no shut

R1#show arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.0.0.1                -   aabb.cc00.0400  ARPA   Ethernet0/0.10

R2#ping 10.0.0.1 repeat 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds:
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 10/14/26 ms

R1#show arp
Protocol  Address          Age (min)  Hardware Addr   Type   Interface
Internet  10.0.0.1                -   aabb.cc00.0400  ARPA   Ethernet0/0.10
Internet  10.0.0.2                0   aabb.cc00.0500  ARPA   Ethernet0/0.10

Sweeeeeet!

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License