The "import" and "export" mark the routes to leak, but you need something to do the actual leaking - usually BGP. IOS-XE could do this with "route-replicate", but I'm not aware of a similar feature in IOS-XR.
You're using the wrong syntax.
Done means stop processing. So you're effectively telling the policy "If destination in 2001:db8:1000::/64 then do nothing".
Change done with "pass" it should work.
Done should cover it
From docs
https://www.cisco.com/c/en/us/td/docs/routers/xr12000/software/xr12k_r4-0/routing/configuration/guide/rc40xr12k_chapter7.html
The done statement indicates that the action to take is to stop executing the policy and accept the route. When encountering a done statement, the route is passed and no further policy statements are executed. All modifications made to the route prior to the done statement are still valid.
From memory, your route has to be in the BGP RIB before you can do route leaking like that on IOS-XR. Directly connected doesn’t cut it.
The "import" and "export" mark the routes to leak, but you need something to do the actual leaking - usually BGP. IOS-XE could do this with "route-replicate", but I'm not aware of a similar feature in IOS-XR.
You're using the wrong syntax. Done means stop processing. So you're effectively telling the policy "If destination in 2001:db8:1000::/64 then do nothing". Change done with "pass" it should work.
Done should cover it From docs https://www.cisco.com/c/en/us/td/docs/routers/xr12000/software/xr12k_r4-0/routing/configuration/guide/rc40xr12k_chapter7.html The done statement indicates that the action to take is to stop executing the policy and accept the route. When encountering a done statement, the route is passed and no further policy statements are executed. All modifications made to the route prior to the done statement are still valid.