09-17-2024 01:56 AM
Hi experts,
In an SRv6 network with uSID, I have configured an EVPN-VPWS. Now, I want to enforce this to follow a strict path via SRv6-TE. I’ve assigned a color to the EVPN route through an extended community and created a policy, but it keeps following the IGP path.
I tested the same setup with an L3VPN, and that worked. When I capture the traffic using wireshark, I can see that the destination IPv6 address contains the SID-list. However, with the EVPN-VPWS, I don’t see this.
I have also tried to configure the strict path using both the Node SID and Adjacency SID, but neither works.
In the test environment, I am using IOS-XRv9K version 7.7.1.
09-17-2024 02:54 AM
Hello @hermanjanson851
Ensure that the transport tunnel for the EVPN-VPWS is correctly configured to use SRv6. In some cases, the service may default to using IGP-based routing unless explicitly told to follow the SRv6-TE path.
09-17-2024 04:49 AM - edited 09-17-2024 05:11 AM
Hello M02@rt37
Thank you for your response.
Below i added the configuration and output of the EVPN-VPWS:
l2vpn
SRv6 Local Remote |
Then the route is 'colored' with 10 as shown below:
Route Distinguisher: 10.112.112.112:1000 RP/0/RP0/CPU0:CPE1#show bgp l2vpn evpn rd 10.112.112.112:100 [1][0000.0000.0000.0000.0000][112]/120 PSID-Type:L2, SubTLV Count:1 |
Finally a policy is created to follow a strict-path:
segment-routing traffic-eng segment-lists srv6 sid-format usid-f3216 ! segment-list CPE1-PE1-P1-PE2-CPE2 srv6 index 10 sid fcbb:fa00:11:: index 20 sid fcbb:fa00:1:: index 30 sid fcbb:fa00:12:: ! ! ! policy CPE1-to-CPE2-EVPN-VPWS srv6 locator CLASSIC_IGP binding-sid dynamic behavior ub6-insert-reduced ! source-address ipv6 2a11:b070:be01:999::111:1 color 10 end-point ipv6 2a11:b070:be01:999::112:1 candidate-paths preference 100 explicit segment-list CPE1-PE1-P1-PE2-CPE2 |
09-17-2024 05:47 AM
Thanks @hermanjanson851
The binding SID (fcbb:fa00:111:e006::) is dynamically assigned with the CLASSIC_IGP locator. This may mean that even though the policy is applied, it might still default to an IGP path due to how the locator is set. You could try using a specific SRv6 locator (different from CLASSIC_IGP) to ensure that the policy follows the intended SRv6-TE path.
srv6
locator SRv6_TE
binding-sid dynamic behavior ub6-insert-reduced
This ensures that SRv6-TE locators are used specifically for transport.
09-17-2024 06:52 AM
Hi M02@rt37,
I've tested it with a seperate locator, but with no success.
What i did not mention in my previous post is that it does work with a L3VPN with the CLASSIC_IGP locator.
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