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

Tracking BGP IPv6 Route not working

David F
Level 1
Level 1

Hi,

I need to create a tracked object based on a specific IPv6 route which I learn through BGP on a 6in4 Tunnel interface (HE BGP 6in4 Tunnel).

This is the definition of my tracked object:

track 61 ipv6 route 2001:470::/32 reachability

I would now expect this tracked object 61 to be up as soon as there is a valid route for 2001:470::/32 in my IPv6 routing table.

And indeed there is a valid IPv6 route for that network.

#show bgp ipv6 u 2001:470::/32 
BGP routing table entry for 2001:470::/32, version 12
Paths: (1 available, best #1, table default)
  Advertised to update-groups:
     1
  Refresh Epoch 1
  6939
    2001:470:12:xxx::1 (FE80::D842:xxxx) from 2001:470:12:xxx::1 (72.52.92.xxx)
      Origin IGP, localpref 100, valid, external, best
      rx pathid: 0, tx pathid: 0x0
#show ipv6 route 2001:470::/32
Routing entry for 2001:470::/32
  Known via "bgp xxx", distance 20, metric 0, type external
  Route count is 1/1, share count 0
  Routing paths:
    2001:470:12:xxx::1
      Last updated 00:18:09 ago
#show ipv6 route 2001:470:12:xxx::1
Routing entry for 2001:470:12:xxx::/64
  Known via "static", distance 1, metric 0
  Route count is 1/1, share count 0
  Routing paths:
    directly connected via Tunnel1
      Last updated 00:20:36 ago
#show ipv6 cef 2001:470::/32
2001:470::/32
  nexthop 2001:470:12:xxx::1 Tunnel1

But the tracked object itself remains down.

#show track 61 
Track 61
  IPv6 route 2001:470::/32 reachability
  Reachability is Down (BGP)
    1 change, last change 00:23:25
  First-hop interface is unknown
  Tracked by:
    Static IPv6 Routing 0

Debug track:

track-tim (61) Delay timer allocate 
track-cfg (61) ipv6 route 2001:470::/32 reachability (added)
track-sta (61) New IPv6 route 2001:470::/32, no ipv6 route->BGP, reachability Down
track-que (61) Queuing ADDED client event for all clients
track-que (61) Unqueuing ADDED client event for all clients
track-cli (61) Start tracking by Static IPv6 Routing
track-err (61) ipv6 route_assert_threshold: != TRACK_IPV6_ROUTE_METRIC_THRESHOLD

Does anybody have a idea why the tracked object reports "no ipv6 route->BGP" / "Down (BGP)" even though the is a valid route present? Are there any other constraints which must be fulfilled for tracked route objects to work?

Of course all further actions bound to this tracked object won't work either.

I am running recent IOS Version 15.5(3)M2.

best regards

David

0 Replies 0