sdwan data-prefix-list

[yoav-shneor]

Hello team .

Is there a way to see data-prefix-list configured on vManage as CLI ? 

is there a way to see counters for a "match" like you do on a regular router  by show ip access list ? 

[Kanan Huseynli]

Hi,

centralized policy elements are pushed from vManage to vSmart. Then it is pushed from vSmart to v Edge.

But Localized policy elements are directly pushed from vManage to vEdges.

On vEdge you can check for these lists (add sdwan keyword after show keyword for cEdge):

show policy from-vsmart lists

show running-config policy lists

On vManage, there is no CLI option.

On routers, you can use "show policy access-list-counters " to see counters. (add sdwan keyword for cEdge)

[yoav-shneor]

Thank you very much for these commands they help.
I'll try to pinpoint the problem I'm having. I have traffic in packet capture that it is marked with DSCP EF46, but I am not the one who marks it in my centralized policy.
The customer claims that he does not mark either.
I want to search for these addresses within all the Data Prefix that is in the centralized policy->define list view.

Maybe I'm missing it within some range

TNX 

[Kanan Huseynli]

HI,

EF46 is well-known DSCP for most voice traffic. I can be directly marked on voip systems.

Regarding how to check in centralized policy, use " show running-config policy" in vSmart.

[yoav-shneor]

Hi ,

I have Voip & Video on that solution and i am mrking  that traffic to 46 but its another vlan and other prefixes .
Again my problem is marked data packets that no body knows who is marking them to 46.

I think ill have to do some sniffing beyond the sdwan domain , maybe on customers switches 

Thanks Kanan

[Kanan Huseynli]

Hi,

how did you notice this value? If you captured somehow, you should have IP address also, and you can begin from there.

By the way, in SD-WAN there may be explicit (admin configured) DSCP via access-list too. Check for access-lists on routers (acl applied to interface are directly pushed from vmanage to router via localized policy).