cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
391
Views
0
Helpful
3
Replies

Why "Not v4 endpoint" on SRv6 Flex-Algo?

Jbr002
Level 1
Level 1

Hi all,

Please give some advise!

 

I am trying Flex-Algo on SRv6.

But the Flex-Algo policy state is "Operational: down".

And I get "No v4 endpoint" debug log.

What is the reason? And how can I fix the issue?

Does IPv4 have relation this issue?


Status is as below.

 

RP/0/RP0/CPU0:xr9kv-4#show segment-routing traffic-eng policy color 101
Fri Jun 28 19:44:06.814 UTC

SR-TE policy database
---------------------

Color: 101, End-point: 2001:10:129::1
  Name: srte_c_101_ep_2001:10:129::1
  Status:
    Admin: up  Operational: down for 00:33:48 (since Jun 28 19:10:18.269)
  Candidate-paths:
    Preference: 105 (configuration) (inactive)
      Name: flex-algo
      Last error: SRv6 SIDs failed verification
      Requested BSID: dynamic
      Constraints:
        Prefix-SID Algorithm: 128
        Protection Type: protected-preferred
        Maximum SID Depth: 13 
      Dynamic (inactive)
      Last error: Unsupported  endpoint
        Metric Type: IGP,   Path Accumulated Metric: 0 
      SRv6 Information:
        Locator: algo128
        Binding SID requested: Dynamic
        Binding SID behavior: uB6 (Insert.Red)
  Attributes:
    Forward Class: 0
    Steering labeled-services disabled: no
    Steering BGP disabled: no
    IPv6 caps enable: yes
    Invalidation drop enabled: no
    Max Install Standby Candidate Paths: 0

RP/0/RP0/CPU0:xr9kv-4#
RP/0/RP0/CPU0:xr9kv-4#debug segment-routing traffic-eng error 
Fri Jun 28 19:48:36.340 UTC
RP/0/RP0/CPU0:xr9kv-4#RP/0/RP0/CPU0:Jun 28 19:48:38.482 UTC: xtc_agent[1288]: DBG-Error:xtc_policy_dynamic_flex_alg:2560 (Policy: srte_c_101_ep_2001:10:129::1 #7)  Not v4 endpoint
RP/0/RP0/CPU0:Jun 28 19:48:38.482 UTC: xtc_agent[1288]: DBG-Error:xtc_policy_dynamic_flex_alg:2680 (Policy: srte_c_101_ep_2001:10:129::1 #7)  Path computation failed
RP/0/RP0/CPU0:Jun 28 19:48:38.482 UTC: xtc_agent[1288]: DBG-Error:xtc_policy_verify_cpath:918  No valid SLs found

 


The node recognizes the SRv6 locators successfully.

 

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:1:: | include locator  
  Known via "isis core", distance 115, metric 11, SRv6-locator, type level-1

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:2:: | include locator
  Known via "isis core", distance 115, metric 11, SRv6-locator, type level-1

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:3:: | include locator
  Known via "isis core", distance 115, metric 11, SRv6-locator, type level-1

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:129:: | include locator
  Known via "isis core", distance 115, metric 31, SRv6-locator (algo 128), type level-1

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:130:: | include locator
  Known via "isis core", distance 115, metric 11, SRv6-locator (algo 128), type level-1

RP/0/RP0/CPU0:xr9kv-4#show route ipv6 2001:10:131:: | include locator
  Known via "isis core", distance 115, metric 21, SRv6-locator (algo 128), type level-1

 

 

I tried explicit path too, this was no problem and packets were forwarded as I intended.

 

RP/0/RP0/CPU0:xr9kv-4#show segment-routing traffic-eng policy color 100 
Fri Jun 28 19:51:56.020 UTC

SR-TE policy database
---------------------

Color: 100, End-point: 2001:10:1::1
  Name: srte_c_100_ep_2001:10:1::1
  Status:
    Admin: up  Operational: up for 00:43:47 (since Jun 28 19:08:08.919)
  Candidate-paths:
    Preference: 100 (configuration) (active)
      Name: 4-to-1
      Requested BSID: dynamic
      Constraints:
        Protection Type: protected-preferred
        Maximum SID Depth: 13 
      Explicit: segment-list 4-to-1A (valid)
        Weight: 1, Metric Type: TE
          SID[0]: 2001:10:2::/48
                  Format: f3216
                  LBL:32 LNL:16 FL:0 AL:80
          SID[1]: 2001:10:3::/48
                  Format: f3216
                  LBL:32 LNL:16 FL:0 AL:80
          SID[2]: 2001:10:1::/48
                  Format: f3216
                  LBL:32 LNL:16 FL:0 AL:80
      SRv6 Information:
        Locator: xr9kv4
        Binding SID requested: Dynamic
        Binding SID behavior: uB6 (Insert.Red)
    Preference: 90 (configuration) (inactive)
      Name: 4-to-1
      Last error: SRv6 SIDs failed verification
      Requested BSID: dynamic
      Constraints:
        Protection Type: protected-preferred
        Maximum SID Depth: 13 
      Explicit: segment-list 4-to-1B (inactive)
      Last error: unresolved first SID (2001:10:2::)
        Weight: 1, Metric Type: TE
          SID[0]: 2001:10:2::/48
          SID[1]: 2001:10:1::/48
      SRv6 Information:
        Locator: xr9kv4
        Binding SID requested: Dynamic
        Binding SID behavior: uB6 (Insert.Red)
  Attributes:
    Binding SID: 2001:10:4:e004::
    Forward Class: Not Configured
    Steering labeled-services disabled: no
    Steering BGP disabled: no
    IPv6 caps enable: yes
    Invalidation drop enabled: no
    Max Install Standby Candidate Paths: 0


RP/0/RP0/CPU0:xr9kv-4#show segment-routing traffic-eng forwarding policy color 100
Fri Jun 28 19:51:28.450 UTC

SR-TE Policy Forwarding database
--------------------------------

Color: 100, End-point: 2001:10:1::1
  Name: srte_c_100_ep_2001:10:1::1
  Binding SID: 2001:10:4:e004::
  Active LSP:
    Candidate path:
      Preference: 100 (configuration)
      Name: 4-to-1
    Segment lists:
      SL[0]:
        Name: 4-to-1A
        SL ID: 0xa000001
        Switched Packets/Bytes: ?/?
        Paths:
          Path[0]:
            Outgoing Interfaces: GigabitEthernet0/0/0/0
            Next Hop: fe80::5054:ff:fe03:0
            FRR Pure Backup: No
            ECMP/LFA Backup: No
            SID stack (Top -> Bottom): {2001:10:2::/48, 2001:10:3::/48}

  Policy Packets/Bytes Switched: ?/?

 

 

I am using XRv9000 on CML.

Configuration is below.

 

Fri Jun 28 20:01:49.106 UTC
!! Building configuration...
!! IOS XR Configuration 7.11.1
!! Last configuration change at Fri Jun 28 20:01:48 2024 by root123
!
hostname xr9kv-4
logging console disable
(snip)
!
vrf L3VPN
 rd 10.255.0.4:20
 address-family ipv4 unicast
  import route-target
   10.255.0.1:20
  !
  export route-target
   10.255.0.4:20
  !
 !
 address-family ipv6 unicast
  import route-target
   10.255.0.1:20
  !
  export route-target
   10.255.0.4:20
  !
 !
!
address-family ipv6 unicast
!
line console
 exec-timeout 0 0
 absolute-timeout 0
 session-timeout 0
!
line default
 exec-timeout 0 0
 absolute-timeout 0
 session-timeout 0
!
call-home
 service active
 contact smart-licensing
 profile CiscoTAC-1
  active
  destination transport-method email disable
  destination transport-method http
 !
!
interface Loopback0
 ipv4 address 10.255.0.4 255.255.255.255
 ipv6 address 2001:10:4::4/128
!
interface Loopback1
 ipv4 address 10.255.0.132 255.255.255.255
 ipv6 address 2001:10:132::4/128
!
interface MgmtEth0/RP0/CPU0/0
 shutdown
!
interface GigabitEthernet0/0/0/0
 ipv6 address 2001:2:4::4/64
!
interface GigabitEthernet0/0/0/1
 ipv6 address 2001:3:4::4/64
!
interface GigabitEthernet0/0/0/2
 shutdown
!
interface GigabitEthernet0/0/0/3
 vrf L3VPN
 ipv4 address 192.168.1.254 255.255.255.0
 ipv6 address 2001:192:168:1::254/64
!
interface GigabitEthernet0/0/0/4
 ipv6 address 2001:1:4::4/64
!
interface GigabitEthernet0/0/0/5
 shutdown
!
interface GigabitEthernet0/0/0/6
 shutdown
!
interface GigabitEthernet0/0/0/7
 shutdown
!
interface GigabitEthernet0/0/0/8
 shutdown
!
extcommunity-set opaque COLOR_EXT_COMMUNITY_SET
  100
end-set
!
route-policy BGP_ROUTE_POLICY_v4
  if destination longer-than (0.0.0.0/0) then
    set extcommunity color COLOR_EXT_COMMUNITY_SET
  endif
  pass
end-policy
!
route-policy BGP_ROUTE_POLICY_v6
  if destination longer-than (::/0) then
    set extcommunity color COLOR_EXT_COMMUNITY_SET
  endif
  pass
end-policy
!
router isis core
 is-type level-1
 net 49.0000.0000.0004.00
 distribute link-state
 affinity-map BLUE bit-position 1
 address-family ipv6 unicast
  metric-style wide
  advertise link attributes
  router-id Loopback0
  segment-routing srv6
   locator xr9kv4
   !
   locator algo128
   !
  !
 !
 flex-algo 128
  priority 250
  advertise-definition
  prefix-metric
  affinity exclude-any BLUE
  address-family ipv4 unicast
  !
  address-family ipv6 unicast
  !
 !
 interface Loopback0
  passive
  address-family ipv6 unicast
  !
 !
 interface Loopback1
  passive
  affinity flex-algo BLUE
  address-family ipv6 unicast
  !
 !
 interface GigabitEthernet0/0/0/0
  point-to-point
  address-family ipv6 unicast
  !
 !
 interface GigabitEthernet0/0/0/1
  affinity flex-algo BLUE
  point-to-point
  address-family ipv6 unicast
  !
 !
 interface GigabitEthernet0/0/0/4
  affinity flex-algo BLUE
  point-to-point
  address-family ipv6 unicast
  !
 !
!
router bgp 100
 segment-routing srv6
  locator xr9kv4
 !
 address-family ipv4 unicast
  segment-routing srv6
   alloc mode per-vrf
  !
 !
 address-family vpnv4 unicast
  vrf all
   segment-routing srv6
    alloc mode per-vrf
   !
  !
 !
 address-family ipv6 unicast
  segment-routing srv6
   locator xr9kv4
   alloc mode per-vrf
  !
 !
 address-family vpnv6 unicast
  vrf all
   segment-routing srv6
    alloc mode per-vrf
   !
  !
 !
 neighbor 2001:10:1::1
  remote-as 100
  update-source Loopback0
  address-family ipv4 unicast
   encapsulation-type srv6
  !
  address-family vpnv4 unicast
   encapsulation-type srv6
   route-policy BGP_ROUTE_POLICY_v4 out
  !
  address-family ipv6 unicast
   encapsulation-type srv6
  !
  address-family vpnv6 unicast
   encapsulation-type srv6
   route-policy BGP_ROUTE_POLICY_v6 out
  !
 !
 vrf L3VPN
  rd 10.255.0.4:20
  address-family ipv4 unicast
   redistribute connected
  !
  address-family ipv6 unicast
   segment-routing srv6
   !
   redistribute connected
  !
 !
!
segment-routing
 traffic-eng
  srv6
   locator xr9kv4 binding-sid dynamic behavior ub6-insert-reduced
  !
  segment-lists
   srv6
    sid-format usid-f3216
   !
   segment-list 4-to-1A
    srv6
     index 10 sid 2001:10:2::
     index 20 sid 2001:10:3::
     index 30 sid 2001:10:1::
    !
   !
   segment-list 4-to-1B
    srv6
     index 10 sid 2001:10:2::
     index 20 sid 2001:10:1::
    !
   !
  !
  policy 4-to-1
   srv6
    locator xr9kv4 binding-sid dynamic behavior ub6-insert-reduced
   !
   color 100 end-point ipv6 2001:10:1::1
   candidate-paths
    preference 90
     explicit segment-list 4-to-1B
     !
    !
    preference 100
     explicit segment-list 4-to-1A
     !
    !
   !
  !
  policy flex-algo
   srv6
    locator algo128 binding-sid dynamic behavior ub6-insert-reduced
   !
   source-address ipv6 2001:10:132::4
   color 101 end-point ipv6 2001:10:129::1
   candidate-paths
    preference 105
     dynamic
      metric
       type igp
      !
     !
     constraints
      segments
       sid-algorithm 128
      !
     !
    !
   !
  !
 !
 srv6
  logging locator status
  encapsulation
   source-address 2001:10:4::4
  !
  locators
   locator xr9kv4
    micro-segment behavior unode psp-usd
    prefix 2001:10:4::/48
   !
   locator algo128
    micro-segment behavior unode psp-usd
    prefix 2001:10:132::/48
    algorithm 128
   !
  !
 !
!
end

 

1 Accepted Solution

Accepted Solutions

Harold Ritter
Cisco Employee
Cisco Employee

Hi @Jbr002 ,

Dynamic path computation is not supported on the headend router for an SRv6 policy. You would need to either configure an explicit path or configure a PCE that would perform the computation on behalf of the headend router.

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

3 Replies 3

Harold Ritter
Cisco Employee
Cisco Employee

Hi @Jbr002 ,

Dynamic path computation is not supported on the headend router for an SRv6 policy. You would need to either configure an explicit path or configure a PCE that would perform the computation on behalf of the headend router.

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Jbr002
Level 1
Level 1

Hi Ritter,

Thank you for your great advise.

I will try the way to use PCE!

You are very welcome @Jbr002 and thanks for the feedback

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México