Edge router TLOC selection preference

[Inkmouse]

I'm looking for a solution to be able to shift traffic across multiple wan links on individual edges on an over arching HUB Spoke topology.

Example HUB A has a singular transport however Spoke B and C have multiple transports such as LEO, cellular/LTE, and terrestrial. I would like to be able to select the preference in which those wans links on those spokes are used and do so in a manner that gives me the most flexibility to then shift those preferences quickly at any given time.

I've explored matching by site-ID and color to set the TLOC preference in the central policy. However only being able to have one central policy active as well as not being able to edit the currently active central policy. Having to clone, edit the clone, and then set the clone as active make this a somewhat unattractive method.

I've also explored hard setting the TLOC preference value on the template of the edge device itself under the tunnel interface. This method works however long term scaling wise isn't optimal as it means every edge device needs it's own template in order to be able to shift those value and not effect all the other edge routers.

This would leave me to believe the route I need to use would be somehow applying this via a localized policy. But I can't seem to find anyway to do something similar like i did in the centralized policy of matching colors to specify a preference value.

any input from someone with experience in cisco SDWAN policy's would be helpful. Thank you.

[MHM Cisco World]

can you more elaborate with topology 

MHM 

[Kanan Huseynli · Accepted solution]

Hi,

TLOC preference change in centralized policy is easy. You don't need to copy&edit policy each time. Centralized policy contains sub-policies (AAR, Data policy ,Control policy etc.). You can import any sub-policy and use (these sub-policies you can consider like route-map in traditional router).

Secondly, for any template parameter, you can make it "variable" and not to type anything inside feature template itself. Then while you attach device template which has feature template with variable value, system will ask you to provide specific - exact variable for exact router. By this way, you can have few templates (or even one) with just variable based value.

Localized policies will not work. Local control policy is just for LAN side routing (OSPF, BGP etc.). Local data policy is for sdwan-access list which can policer/ queuer/ block traffic. They are not related to TLOC/OMP etc.

[Inkmouse]

Kanan's information was super helpful and I didn't realize that when playing around in the centralized policy that I could use multiple (sub-policies). In the end I used a (topology -> HUB and Spoke policy combined with a topology -> custom route & tloc policy). In the route and tloc policy I matched based off a color list and site list to influence inbound tloc preference values. I created multiple tloc policies (one for each tloc) and then created multiple matches to different site lists under each one. These site lists are specific to each tloc and there are 3 for each tloc that allow to shift preference values between three different values (high, medium, low). This made it easy to be able to have control and shift traffic to a specific tloc from an edge by simple modifying which site was in which lists which would then update to the vsmart policy.