09-11-2019 03:01 AM
Intention:
Forwarding traffic destined for vrf A & traffic destined for R6 l01(66.66.66.66/32) based on SRTE explicit path
My SR Policy on head-end router is UP, receiving prefix from remote PE with proper next-hop and color ext community
I am new to SRTE and trying to explore it.
my understanding traffic should automatically choose the SRTE policy if the next-hop matches the policy endpoint and prefix match the color.
but in my case it interested traffic not using the SRTE path.
Am I missing something ?
R6 configuration:(End Point)
Setting color for interested traffic one vpnv4 route and one ipv4 route
extcommunity-set opaque RED
10
end-set
!
route-policy SETCOLOR
if extcommunity rt matches-any (100:20) then
set extcommunity color RED
endif
if destination in (66.66.66.66/32) then
set extcommunity color RED
endif
pass
end-policy
!
router bgp 100
address-family ipv4 unicast
network 66.66.66.66/32
!
address-family vpnv4 unicast
!
neighbor 1.1.1.1
remote-as 100
update-source Loopback0
address-family ipv4 unicast
route-policy SETCOLOR out
!
address-family vpnv4 unicast
route-policy SETCOLOR out
!
Head end configuration on R1
ipv4 unnumbered mpls traffic-eng Loopback0
!
segment-routing
global-block 16600 16699
traffic-eng
segment-list SLIST1
index 10 address ipv4 2.2.2.2
index 20 address ipv4 4.4.4.4
index 30 address ipv4 3.3.3.3
index 40 address ipv4 5.5.5.5
index 50 address ipv4 6.6.6.6
!
policy 100
binding-sid mpls 111
color 10 end-point ipv4 6.6.6.6
candidate-paths
preference 100
explicit segment-list SLIST1
!
!
!
!
!
!
Tunnel is UP
RP/0/0/CPU0:R-1#show mpls forwarding tunnels detail
Wed Sep 11 00:02:19.600 UTC
Tunnel Outgoing Outgoing Next Hop Bytes
Name Label Interface Switched
------------- ----------- ------------ --------------- ------------
100 (SR) 16204 Gi0/0/0/0 10.1.2.2 0
Updated: Sep 10 23:15:57.840
Version: 699, Priority: 2
Label Stack (Top -> Bottom): { 16204 16403 16305 16506 }
NHID: 0x0, Encap-ID: N/A, Path idx: 0, Backup path idx: 0, Weight: 0
MAC/Encaps: 14/30, MTU: 1500
Outgoing Interface: GigabitEthernet0/0/0/0 (ifhandle 0x00000040)
Packets Switched: 0
Interface:
Name: 100 (ifhandle 0x00000050)
Local Label: 24005, Forwarding Class: 0, Weight: 0
Packets/Bytes Switched: 0/0
RP/0/0/CPU0:R-1#
RP/0/0/CPU0:R-1#show segment-routing traffic-eng policy detail
Wed Sep 11 00:04:17.602 UTC
SR-TE policy database
---------------------
Name: 100 (Color: 10, End-point: 6.6.6.6)
Status:
Admin: up Operational: up for 00:48:19 (since Sep 10 23:15:57.711)
Candidate-paths:
Preference 100:
Explicit: segment-list SLIST1 (active)
Weight: 0, Metric Type: IGP
16602 [Prefix-SID, 2.2.2.2]
16204 [Prefix-SID, 4.4.4.4]
16403 [Prefix-SID, 3.3.3.3]
16305 [Prefix-SID, 5.5.5.5]
16506 [Prefix-SID, 6.6.6.6]
Attributes:
Binding SID: 111
Allocation mode: explicit
State: Programmed
Policy selected: yes
Forward Class: 0
Head end receving BGP prefixes with proper colors
RP/0/0/CPU0:R-1#show bgp vpnv4 un vrf A 20.200.200.1
Wed Sep 11 00:03:19.856 UTC
BGP routing table entry for 20.200.200.0/24, Route Distinguisher: 100:20
Versions:
Process bRIB/RIB SendTblVer
Speaker 932 932
Last Modified: Sep 10 23:57:54.918 for 00:05:25
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Not advertised to any peer
Local
6.6.6.6 (metric 40) from 6.6.6.6 (6.6.6.6)
Received Label 24006
Origin incomplete, metric 2, localpref 100, valid, internal, best, group-best, import-candidate, imported
Received Path ID 0, Local Path ID 1, version 932
Extended community: Color:10 OSPF route-type:0:1:0x0 OSPF router-id:20.0.2.1 RT:100:20
Source AFI: VPNv4 Unicast, Source VRF: A, Source Route Distinguisher: 100:20
RP/0/0/CPU0:R-1#
RP/0/0/CPU0:R-1#show bgp ipv4 unicast 66.66.66.66
Wed Sep 11 00:07:30.079 UTC
BGP routing table entry for 66.66.66.66/32
Versions:
Process bRIB/RIB SendTblVer
Speaker 112 112
Last Modified: Sep 10 23:57:54.918 for 00:09:35
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Not advertised to any peer
Local
6.6.6.6 (metric 40) from 6.6.6.6 (6.6.6.6)
Origin IGP, metric 0, localpref 100, valid, internal, best, group-best
Received Path ID 0, Local Path ID 1, version 112
Extended community: Color:10
RP/0/0/CPU0:R-1#
But traffic is using IGP PATH
RP/0/0/CPU0:R-1#traceroute vrf A 20.200.200.1
Wed Sep 11 00:12:15.379 UTC
Type escape sequence to abort.
Tracing the route to 20.200.200.1
1 10.1.2.2 [MPLS: Labels 16206/24006 Exp 0] 79 msec 19 msec 19 msec
2 10.2.3.2 [MPLS: Labels 16306/24006 Exp 0] 19 msec 19 msec 19 msec
3 10.3.6.2 [MPLS: Label 24006 Exp 0] 19 msec 19 msec 19 msec
4 20.0.2.2 19 msec * 9 msec
RP/0/0/CPU0:R-1#traceroute 66.66.66.66
Wed Sep 11 00:12:41.347 UTC
Type escape sequence to abort.
Tracing the route to 66.66.66.66
1 10.1.4.2 [MPLS: Label 16406 Exp 0] 0 msec 0 msec 0 msec
2 10.3.4.1 [MPLS: Label 16306 Exp 0] 0 msec 0 msec 0 msec
3 10.3.6.2 0 msec * 0 msec
RP/0/0/CPU0:R-1#
09-12-2019 10:10 AM
Hi Samarjit,
What version of XR are you using on R-1?
Regards,
09-12-2019 12:28 PM
I am also using 6.4.2.
I saw your reply on the other discussion ...
https://community.cisco.com/t5/mpls/mpls-l3vpn-over-sr-te-policy/m-p/3777357
Need to try it on 6.5.2 or higher.
thanks for looking into it.
09-12-2019 12:30 PM
You are very welcome. I am glad I could help.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide