Thanks for any insight.
I want to use MPLS L3VPN over SR-TE Policy on ASR9000.
So I configured SR-TE Policy on Ingress PE and configured vpnv4 route-policy on Egress PE.
---
<Ingress PE>
segment-routing
traffic-eng
segment-list AP14
index 1 mpls label 15014
!
segment-list AP154
index 1 mpls label 15015
index 2 mpls label 15054
!
policy EV14_BLACK
color 1001 end-point ipv4 1.1.1.4
candidate-paths
preference 10
explicit segment-list AP154
!
!
!
policy EV14_GREEN
color 1002 end-point ipv4 1.1.1.4
candidate-paths
preference 10
explicit segment-list AP14
!
--
<Egress PE>
extcommunity-set opaque BLACK
1001
end-set
!
extcommunity-set opaque GREEN
1002
end-set
!
route-policy L3_color
if destination in (74.1.1.0/24) then
set extcommunity color BLACK
set next-hop 1.1.1.4
elseif destination in (74.2.1.0/24) then
set extcommunity color GREEN
set next-hop 1.1.1.4
endif
pass
end-policy
!
router bgp 65001
neighbor-group iBGP
remote-as 65001
update-source Loopback0
address-family vpnv4 unicast
!
!
neighbor 1.1.1.1
use neighbor-group iBGP
address-family vpnv4 unicast
route-policy L3_color out
!
!
---
Ingress PE received vpnv4 prefix information with color community.
---
RP/0/RSP1/CPU0:ASR9904-1#show bgp vrf RED 74.1.1.0/24
BGP routing table entry for 74.1.1.0/24, Route Distinguisher: 1:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 64 64
Last Modified: Jan 10 10:34:35.451 for 00:04:04
Paths: (1 available, best #1)
Advertised to CE peers (in unique update groups):
11.1.111.11
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
11.1.111.11
14
1.1.1.4 (metric 20) from 1.1.1.4 (1.1.1.4)
Received Label 68104
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate, imported
Received Path ID 0, Local Path ID 1, version 64
Extended community: Color:1001 RT:1:1
Source AFI: VPNv4 Unicast, Source VRF: RED, Source Route Distinguisher: 1:1
--
RP/0/RSP0/CPU0:ASR9904-1#show bgp vrf RED 74.2.1.0/24
BGP routing table entry for 74.2.1.0/24, Route Distinguisher: 1:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 63 63
Last Modified: Jan 10 10:34:35.452 for 00:05:51
Paths: (1 available, best #1)
Advertised to CE peers (in unique update groups):
11.1.111.11
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
11.1.111.11
14
1.1.1.4 (metric 20) from 1.1.1.4 (1.1.1.4)
Received Label 68105
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate, imported
Received Path ID 0, Local Path ID 1, version 63
Extended community: Color:1002 RT:1:1
Source AFI: VPNv4 Unicast, Source VRF: RED, Source Route Distinguisher: 1:1
---
But L3VPN traffic didn't use SR-TE Policy.
---
RP/0/RSP0/CPU0:ASR9904-1#show segment-routing traffic-eng forwarding policy
Policy Segment Outgoing Outgoing Next Hop Bytes
Name List Label Interface Switched
------------- --------------- ----------- ------------------- --------------- ------------
EV14_BLACK AP154 15054 Gi0/0/0/0.15 11.1.15.5 0
EV14_GREEN AP14 Pop Gi0/0/0/0.14 11.1.14.4 0
---
Anything missing here in the configuration?
Or does SR-TE Policy still not support MPLS L3VPN?
As additional information, EVPN-VPWS over SR-TE Policy has succeeded.
Thanks,
Soushi
