Hello Alex,
thanks for taking time to answer.
As I mentioned in initial post, I'm testing this on vMX 19.3 so these features should be available.
> show version
Model: vmx
Junos: 19.3R1.8
Dynamic policies are working, I had varios types of configuration and kind of missed that combination of tunnel-end + compute works too, thanks 🙂
For ODN i'm interested in flavor #2 as you desscribed it. I read doc which you referenced before but based on that it's still not clear to me how configuration should be crafted, here are steps I followed:
1) dyn tunnels are defined with/out color, SR PATH TEMPLATE and destination networks -> both mandatory argument
[edit routing-options dynamic-tunnels]
+ SRTE-ODN {
+ spring-te {
+ source-routing-path-template {
+ SRTE-PATH-TEMPLATE color 22222;
+ }
+ destination-networks {
+ 10.0.0.0/24;
+ }
+ }
+ }
2) then SR TEMPLATE has to be defined with mandatory argument -> primary SR-LIST
[edit protocols source-packet-routing]
+ source-routing-path-template SRTE-PATH-TEMPLATE {
+ primary {
+ SRTE-LIST-ODN;
+ }
+ }
3) last SR-LIST must be defined where <hop-list> is mandatory, dynamic only can't be used here
[edit protocols source-packet-routing]
+ segment-list SRTE-LIST-ODN {
+ dynamic;
+ ## Warning: missing mandatory statement(s): <hop-list>
+ }
I'm not sure what I'm missing here but for ODN triggered by BGP route I don't want to define explicit hops. even docs says dynamic LSP , so tunnel-end (BGP route NH) should be enough to compute dynamic LSP. Is this doc complete or have I missed something obvious?
thanks