03-11-2022 12:23 AM
I configured the Policy to choose the path followed by traffic between 100.100.100.100 and 100.100.100.101 but there is a problem
Solved! Go to Solution.
03-11-2022 06:03 AM
Hi @username11 ,
As @balaji.bandi indicated, it is one thing to define a policy, but you also need to direct traffic into that policy. This is referred to as traffic steering. There are many ways to steer traffic into a policy. For testing you could use a static route to do that.
Please refer to the following documentation to see how to steer the traffic into the policy, using a static route.
Regards,
03-16-2022
07:33 AM
- last edited on
03-16-2022
02:20 PM
by
Translator
Hi @username11 ,
You are missing the following traffic engineering configuration.
! Enable traffic-eng globally
mpls traffic-eng tunnels
! Enable traffic-eng on all core interfaces
int gi1
mpls traffic-eng tunnels
! Enable traffic-eng at the isis level
router isis SR
mpls traffic-eng router-id lo0
mpls traffic-eng level-1
You need to add this to all routers in the core network.
Regards,
03-11-2022 01:18 AM
that is confiuration of TE policy, how about routing config, how you want to take which patch to reach 100.100.100.100 to 100.100.100.101
below example help you configuring routing :
03-11-2022 02:29 AM
almost the same but I did not know the problem
03-11-2022 03:56 AM
Can you attachedconfig of all the device required config(not screenshots).
03-11-2022 04:39 AM
sorry l can only screenshots
03-11-2022 06:03 AM
Hi @username11 ,
As @balaji.bandi indicated, it is one thing to define a policy, but you also need to direct traffic into that policy. This is referred to as traffic steering. There are many ways to steer traffic into a policy. For testing you could use a static route to do that.
Please refer to the following documentation to see how to steer the traffic into the policy, using a static route.
Regards,
03-14-2022 04:25 AM
the same problem (with static route) I repeat the configuration and the same problem
03-14-2022 06:59 AM
maybe because there are two interface,and the router don't know the interface of source
03-14-2022 03:14 PM
Hi @username11 ,
This should not be happening. This message will go away once you fixed the other issues.
Regards,
03-14-2022
07:39 AM
- last edited on
03-16-2022
02:16 PM
by
Translator
Hi @username11 ,
Can you check the following two things:
1. Make sure you add the following configuration to your policy POL1:
policy POL1
candidate-paths
preference 200
constraints
segments
dataplane mpls
2. Make sure all your core interfaces are configured as point to point under your routing protocol.
3. What IOS-XE version are you using?
Regards,
03-14-2022 08:37 AM
03-14-2022
03:06 PM
- last edited on
03-16-2022
02:17 PM
by
Translator
Hi @username11 ,
You should also make sure you use the following command under your core routing protocol:
router ospf xxx
distribute link-state
or
router isis xxx
distribute link-state
Can you also join a new
show segment-routing traffic-end pol all
output after making the changes I suggested.
Regards,
03-15-2022 09:08 AM
hi Mr @Harold Ritter
03-15-2022
09:29 AM
- last edited on
03-16-2022
02:18 PM
by
Translator
Hi @username11 ,
Could you please provide the configuration for PE-SR1 and the output from
show segment-routing traffic-eng topology ipv4?
Regards,
03-16-2022 12:45 AM
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