Deploy E-LINE Services for Customer 3¶

Preparing The Lab¶

Log into the LabAccess jumpserver:
1. Type labs, or select Option 97 to get to the Additional Labs menu.
2. Type or select the option for mesh-topology-evpn-labs in order to get to the EVPN labs.
3. Type c3eline in this menu to configure the topology with the necessary prerequisites.

Lab Tasks¶

Customer-3 is attached to two Service Provider nodes, EOS1 and EOS4. These will be PE nodes. Since this customer will require a Layer 1 Wire Service, create a local patch and use EVPN to advertise the customers port to other interested PEs.
1. On EOS1 and EOS4, configure the port facing CE devices EOS17 and EOS16 respectively.
  
  Note
  
  For a port-based service (which differs from a VLAN-based service), the CE-facing interface must be configured as a routed interface with the no switchport command. We will also disable LLDP so those frames are not consumed on the interface.
```
interface Ethernet6
    no switchport
    no lldp transmit
    no lldp receive
```
2. On EOS1 and EOS4, create the logical patch name C3-E-LINE between the local CE interface and the Virtual Private Wire Service, or VPWS, that will be created with a VPWS name of CUSTOMER-3 and a pseudowire name of EOS16-EOS17.
  
  Info
  
  As the name implies, the patch-panel configuration allows for stitching together local and remote interfaces using an emulated Layer 1 Service.
```
patch panel
    patch C3-E-LINE
        connector 1 interface Ethernet6
        connector 2 pseudowire bgp vpws CUSTOMER-3 pseudowire EOS16-EOS17
```
3. On EOS1, leverage EVPN to advertise the Layer 1 Service to the Route Reflector using the same VPWS and pseudowire name as the previous step. In addition, use the format of Loopback0 IP:3 as the RD and 3:1617 as the RT. Finally, set the local VPWS ID to 16 and the remote VPWS ID to 17. These values must be unique within the VPWS instance.
  
  Note
  
  These values tie together the previous patch configuration with the received BGP EVPN routes we will see later in this lab.
```
router bgp 100
    !
    vpws CUSTOMER-3
        rd 1.1.1.1:3
        route-target import export evpn 3:1617
        !
        pseudowire EOS16-EOS17
            evpn vpws id local 16 remote 17
```
4. Repeat the previous step on EOS4 while adjusting the variables accordingly to match the other side of the service.
```
router bgp 100
    !
    vpws CUSTOMER-3
        rd 4.4.4.4:3
        route-target import export evpn 3:1617
        !
        pseudowire EOS16-EOS17
            evpn vpws id local 17 remote 16
```
Configure the Customer-3 CE nodes to connect to each other over the emulated LINE service.
1. Since the Service Provider is providing a Layer 1 service, configure the CE on EOS16 and EOS17 interfaces as OSPF peers as if they were attached back to back with a cable.
  
  Info
  
  The IP addressing on the links has already been configured by the base IPv4 configuration template.
```
interface Ethernet1
    ip ospf network point-to-point
!
router ospf 300
    network 0.0.0.0/0 area 0.0.0.0
    max-lsa 12000
```

Testing¶

With all PE and CE nodes configured, verify connectivity between CE nodes EOS16 and EOS17.
1. Verify that all CE interfaces are able to resolve ARP for their peers and are able to see each other as LLDP neighbors.
  
  Note
  
  The Service Provider network is emulating the behavior of a Layer 1 connection and as such should be transparent to the Layer 2 and 3 operations between the CE nodes. Note that depending on the holdtime of the CE LLDP table, the PEs may still be present, but they should age out.
```
show ip arp
show lldp neighbor
```
2. Verify OSPF adjacencies have formed between the CEs and routes have been exchanged.
```
show ip ospf neighbor
show ip route
```
3. Test connectivity between CE Loopback0 interfaces from EOS16 to EOS17.
```
ping 17.17.17.17 source 16.16.16.16
```
Next, verify the EVPN control-plane and MPLS data-plane for the customer E-LINE service.
1. On EOS1, verify the local patch status.
  
  Note
  
  Take note of the MPLS label assigned to the local and remote nodes and that they differ, since the VPN label for the E-LINE service is locally significant.
```
show interface Ethernet6
show patch panel detail
```
2. Display the EVPN routes from EOS4 on EOS1 associated to the VPWS.
  
  Info
  
  The VPWS pseudowire ID is included as part of the EVPN Type-1 route.
```
show bgp evpn route-type auto-discovery rd 4.4.4.4:3 detail
```
3. Verify the forwarding path for traffic on the VPWS towards EOS4 on EOS1.
  
  Note
  
  The In/Out section of the show patch panel forwarding output will show the VPN label for the VPWS and the associated IS-IS SR tunnel index for the destination PE. This tunnel index can then be found in the output of the show isis segment-routing tunnel command.
```
show patch panel forwarding
show isis segment-routing tunnel
```

Success

Lab Complete!