Leverage SR-TE to Steer VPN Traffic

Steer Customer 1 Layer 3 VPN Traffic

1. Use Segment Routing Traffic Engineering (SRTE) to manipulate L3VPN traffic for Customer-1. Configure the Service Provider network so that traffic from EOS15 to EOS12 follows the path pictured above.

   • Use a BGP Color Community value of 12.
   • The Binding SID for the TE policy should be 1000X12 (X = destination Node-ID)
   • Only traffic for EOS12’s Loopback should be matched.
   • Traffic should still be ECMP load balanced between PEs EOS1 and EOS6.

Steer Customer 2 Layer 2 VPN Traffic

1. Use SR-TE to manipulate L2VPN traffic for Customer-2. Configure the Service Provider network so that traffic from EOS9 to EOS10 follows the path pictured above.

   • Use a BGP Color Community value of 10.
   • The Binding SID for the TE policy should be 1000X12 (X = destination Node-ID)
   • Only L2 traffic for EOS10 should be matched.
   • Traffic ingressing on EOS3 or EOS4 should be sent via the pictured path.

Steer Customer 3 E-LINE Traffic

1. Use SR-TE to manipulate VPWS traffic for Customer-3. Configure the Service Provider network so that traffic between EOS16 and EOS17 follows the path pictured above.

   • Use a BGP Color Community value of 1617.
   • The Binding SID for the TE policy should be 1001617 (X = destination Node-ID)
   • Only VPWS traffic for EOS16 and EOS17 should be matched.
   • Traffic should follow the pictured path bidirectionally.
   Limitation

   Due to a limitation in software forwarding in vEOS-lab, forwarding of VPWS traffic into SR-TE tunnels does not function and as such, we cannot verify functionality via ICMP, etc. All control-plane functions should be verified using the commands above. Steering of VPWS traffic in hardware platforms functions as expected.

Success

Lab Complete!