how to set cv tags for a evpn l3ls based campus fabric

[kmueller68]

Hello.

I am currently testing the avd preview feature CloudVision Tags for Campus deployments.

This is based on a more classic campus topology spine and leaf/member-leaf, which was called routing core and access in the old days.
The avd feature sets the role tag for the routing cores as spine and the access switches as leaf.
The cvp campus dashboard and network hierarchy displaye the switches based on these tags.

We are running a standard evpn l3 spine - l3leaf and l2leaf evpn fabric for the campus, which does not match the cvp campus v2 design and default device role tags.

Do you have any advise or suggestion, which cv tags we should assign as role and topology_hint_type for these three level of devices?
We have

• typical l3ls spine
• l3ls l3leafs = routing distribution switches (equivilant to the campusv2 role: spine)
• l3ls l2leafs = layer2 access switches

I fail to assign an appropriate cv role and topology_hint_type tag to the l3ls spines, to be meaningful displayed in the campus health dashboard and the network hierarchy.

Any hints would be helpful.

Thank you
Karlheinz

[ClausHolbechArista]

@jrecchia1029 do you know the answer here?

@kmueller68 we do have override options for the device type in various places, so you can steer the exact type per device instead of relying on the builtin mapping from AVD device type. Hopefully Joe can tell us the value you need for the core layer.