Segment routing for L2VPN

[Lorenso391]

HEllo all,

iam trying on PE router create Police map for L2VPNs which will tel them via which interface they should go to P router..

This is working. But how I can tie this type of communication to Flex-algo and traverse it via nodes which I need ?

[Harold Ritter · Accepted solution]

Hi @Lorenso391 ,

If you already have flex algo configured throughout your network, you can set an on demand segment routing policy on the PEs to forward the l2vpn traffic to the flex algo SID of the egress PE.

The policy would look something like this:

segment-routing
 traffic-eng
  on-demand color 20
   dynamic
    metric
     type igp
    !
   !
   constraints
    segments
     sid-algorithm 128
    !

You would also need to set the color extended community accordingly on all the PEs when advertising the l2vpn information between themselves via BGP.

Regards,

[Lorenso391]

Hello I tried Simple flexalgo but tunnel for flexalgo not coming up : L2VPNS  are good but not going via glexalgo path

hostname01

router isis 12345
address-family ipv4 unicast
segment-routing mpls
!
flex-algo 128
!
interface Loopback0
address-family ipv4 unicast
prefix-sid index 253
prefix-sid algorithm 128 absolute 20253
!
!
!

segment-routing
global-block 16000 23999
traffic-eng
on-demand color 128
dynamic
metric
type igp
!
!
constraints
segments
sid-algorithm 128
!
!
!
policy SECURE_PATH
color 128 end-point ipv4 10.20.30.250
candidate-paths
preference 200
constraints
segments
sid-algorithm 128
!
!
!
!
!
!
l2vpn
!
pw-class secure-128-flexalgo
encapsulation mpls
preferred-path sr-te policy srte_c_128_ep_10.20.30.250
!
!
xconnect group EVPN-XYZ
p2p XX-XX-1456
interface TenGigE0/0/0/4
neighbor evpn evi 1456 service 1456
pw-class secure-128-flexalgo

!

hostname02

router isis 12345
address-family ipv4 unicast
segment-routing mpls
!
flex-algo 128
!
interface Loopback0
address-family ipv4 unicast
prefix-sid index 250
prefix-sid algorithm 128 absolute 20250
!
!
!

segment-routing
global-block 16000 23999
traffic-eng
on-demand color 128
dynamic
metric
type igp
!
!
constraints
segments
sid-algorithm 128
!
!
!
policy SECURE_PATH
color 128 end-point ipv4 10.20.30.253
candidate-paths
preference 200
constraints
segments
sid-algorithm 128
!
!
!
!
!
!

l2vpn
pw-class secure-128-flexalgo
encapsulation mpls
preferred-path sr-te policy srte_c_128_ep_10.20.30.253
!
!
xconnect group EVPN-XYZ
p2p XX-XX-1456
interface TenGigE0/0/0/3
neighbor evpn evi 1456 service 1456
pw-class secure-128-flexalgo
!

Tunnels not comming UP :

Group EVPN-XYZ, XC XX-XX-1456, state is up; Interworking none
AC: TenGigE0/0/0/4, state is up
Type Ethernet
MTU 9286; XC ID 0x1; interworking none
Statistics:
packets: received 2906, sent 2604
bytes: received 477414, sent 328050
EVPN: neighbor 10.20.30.250, PW ID: evi 1456, ac-id 1456, state is up ( established )
XC ID 0xc0000001
Encapsulation MPLS
Encap type Ethernet, control word enabled
Sequencing not set
Preferred path Inactive : SR TE srte_c_128_ep_10.20.30.250 (BSID:None, IFH:0x200080e4), Statically configured, fallback enabled
Ignore MTU mismatch: Enabled
Transmit MTU zero: Enabled
Tunnel : Down
LSP : Up

EVPN Local Remote
------------ ------------------------------ -----------------------------
Label 26068 26057
MTU 9300 unknown
Control word enabled enabled
AC ID 1456 1456
EVPN type Ethernet Ethernet

------------ ------------------------------ -----------------------------

[Lorenso391]

Hello, Thank you for your time. All is working now. Problem on P router - Overload Bit on ISIS :).

[Harold Ritter]

I am glad you got it working and thanks for the feedback @Lorenso391