assign tags to port in DNAC 2.2.3

[andy!doesnt!like!uucp]

hi Gents

anyone here to give a clue how do we make subject? according to amazing hint from Assurance deployment guide "

Note	For a link to be considered a WAN link, you must manually assign the system-generated WAN tag to the required port. See "Assign Tags to Ports" in the Manage Your Inventory chapter of the Cisco DNA Center User Guide.

" i've read Cisco DNA Center User Guide, Release 2.2.3 - Manage Your Inventory [Cisco DNA Center] - Cisco but there is 0 about this need... no hints w/ just google search as well (facepalm)

[sandhmoh]

Hi Andy, Go to Inventory>Click on the Device>View Device Details>Interfaces> Ethernet Ports>>Choose the WAN Port>Click on TAG and Choose "WAN" in there and Apply. Screenshot Attached. Hope this helps.

[junyi]

@sandhmoh can you explain me a bit more regarding the usage of the port tag? 

Within the DNAC template's system variables, there appears to be no mention of an interface tag. Could it be that certain provisioning operations rely on system-generated tags? If so, what then is the intent of a customer-created tag?

[sandhmoh]

Once you have the port tag, you can call this on template for reference and make changes to the config. Just an example.

hostname $hostname
#foreach($interface in __interface) >>> __interface is a system variable
interface $interface.name
description nothing
#if($interface.getTag("testingTag")) >>>> notice getTag
interface $interface.name
description testingTag
exit
#end
#end

[mcmaro]

@sandhmoh 
Is the .getTag function really exist or has different syntax ?
I tested your code but the interface.getTag("test") doesn't work neither interface.getTag == "test"