TLOC Extension static default routes with Configuration Groups

[gladpark]

Hello, 

I'm trying to convert my template-based configuration to use Configuration Groups. It's a two-router site with several TLOC extensions between the routers. With the template-based configuration, I add a static route in VPN0 to the other side of the P2P TLOC extension subnet for those 'extended TLOCs' to get out. The problem I'm finding with Configuration Group deployment is that when I create the static routes in VPN0, it applies those same static routes to both WAN routers. So when I go to deploy it, it fails because one of the static routes is to a local IP on one of the routers.

Is there a way to add a static router in VPN0 to just one router? Or should I take another approach here? 

Thanks, 
Brad

[MHM Cisco World]

If you use same interface in both vedge use defualt route with egress interface dont specify next-hop in this case template will be accept by both vedge

MHM

[gladpark]

Thank for the response @MHM Cisco World 

But I don't see an option to specify an interface, only nexthop, dhcp or null0 

Thanks

[MHM Cisco World]

If that so then you need two separate templates one for each vedge

MHM

[gladpark]

Are you saying not to use configuration groups and use device templates instead? From the options in the 'wizard' it looks like TLOC extensions are supported. But it doesn't make it clear how the routers point to each other. 

[MHM Cisco World]

Check this link

https://www.cisco.com/c/en/us/support/docs/routers/xe-sd-wan-routers/220614-configure-tloc-extension-using-vmanage-f.html

MHM

[gladpark]

Thanks again for the feedback MHM. But I know how to create TLOCs with feature templates. The goal was to use Configuration Groups. 

[HannesHeinrich]

@gladpark Have you found a solution? I have the same problem

[Jeongjun Park]

Why dont we use "device specific" so that you can make it as a variable

[HannesHeinrich]

@Jeongjun Park  Thank you for your answer. In my case, these are values that are really the same for every router pair. It makes no sense for the technician to re-enter this “variable” (which is always the same) for every router.

I think that the VPN0 profile always applies to both routers is a bad design of the software.