vSmart policy behavior | originator attribute

[ggomez]

Hi.

I was study Catalyst sdwan solution on my own lab and im trying to figured out an extrange behavior regarding the control policy.

Basically, i want to influentiate the prefference on CSR1 routes to reach the routes on the "Data Center" side trought cEdgeDC-2 (sys-ip 1.1.2.105), and keep all the other routes preffering cEdgeDC-1. This is an hub&spoke topology actually.

I tryed achieve this using the sequence 16 on the control policy. But on the routing table of CSR1 is still preffering cEdgeDC-1

When i check the omp routes details output, i dont see the omp prefference; i think its because CSR1 (and vSmart) is receiving the route from DC only with originator attribute 1.1.1.105 (even if cEdgeDC-2 is anuncing the route too). So the sequence 16 is no taking any effect.

someone know what is happening and how to solve this?

[ivances]

Could you please show us the entire central policy?

[MHM Cisco World]

as I see the Seq 10 is run before seq 16 and this make all prefic learn from DC1 is prefer,
you need to push Seq 16 before seq 10 (sure you need to change it number) and match tloc and route (with originator ) set preference with prefer value 
MHM

[Kanan Huseynli]

Hi,

seq 10 & 12  and 16 & 20 are two different things.

In your case, seq 16 change OMP preference if originator is 1.1.2.105. Whatever you shared is output of 1.1.1.105 routes.

You don't need both match tloc and match route.

You need two route sequences:

1) match DC-prefixes (via prefix-list or any other method origin-type / community / tag depending on your service-side config) and match originator 1.1.2.105 > set preference (which is OMP route preference) to be 200

2) match prefixes ANY and match originator 1.1.1.105 > just accept or set preference 150 (any value lower than 200)

[ggomez]

CSR1#show sdwan omp routes vpn 1 10.1.1.0/24 deta
Generating output, this might take time, please wait ...

---------------------------------------------------
omp route entries for vpn 1 route 10.1.1.0/24
---------------------------------------------------
RECEIVED FROM:
peer 1.1.1.30
path-id 41
label 1002
status C,I,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 1.1.1.105
type installed
tloc 1.1.1.105, mpls, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 105
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 1.1.1.30
path-id 42
label 1002
status C,I,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 1.1.1.105
type installed
tloc 1.1.1.105, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 105
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 1.1.1.30
path-id 43
label 1002
status R
loss-reason tloc-preference
lost-to-peer 1.1.1.30
lost-to-path-id 41
Attributes:
originator 1.1.1.105
type installed
tloc 1.1.2.105, mpls, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 105
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 1.1.1.30
path-id 44
label 1002
status R
loss-reason tloc-id
lost-to-peer 1.1.1.30
lost-to-path-id 43
Attributes:
originator 1.1.1.105
type installed
tloc 1.1.2.105, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 105
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
community not set
unknown-attr-len not set

CSR1#

when i add the sequence 18 the behavior changes

Now the originator matches

[MHM Cisco World]

cedge#show sdwan omp routes vpn x x.x.x.x/x <<- without data keyword 

share it here 

MHM

[Kanan Huseynli]

Did you check my approach?