Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello Community,I've got Catalyst Center running version 2.3.7.7 monitoring our devices with Assurance, handling SWIM, doing traditional networking CLI templates and integrated with ISE 3.3 (not managing policies, just setup in Network Settings for N...
Hello Everyone!Curious if anyone else is automating the configuration and maintaining of Tags/Host Groups in Secure Network Analytics (formerly Stealthwatch) via the API. I've been working on automation that would sync this information utilizing our...
Has anyone else experienced an issue deleting a site/building from DNA 2.3.5.5 using the API? I've tested using Postman and an Ansible Playbook using the Cisco.DNA Collection and get the same results from both. The API call is successful and I get ...
Hi everybody,Issue 1:I'm playing around with my first DNA in a lab environment before deciding to put into production and am currently working on Event Notifications for Assurance. I understand that alerting into a Webex Teams Space is builtin now, ...
Hey everyone, New to DNA and setting up my first. I've got our Enterprise Interface configured as well as Management Interface that we'll be using to access GUI and manage. My question is, what interfaces is the IP Access Control list applied to? ...
Hi Balaji,No template provisioning involved. DNAC just randomly changes the IP in ISE for these 2 devices. I tried starting fresh and deleted the devices from DNAC, left the NADs in ISE as is with Gi0/0 IP and then added the devices back into DNAC ...
I'm experiencing this same issue with various endpoints (printers, ip phones, etc) with a site I just converted to IBNS2.0. I've got the same log messages occurring roughly every 1-3 minutes (it varies) and in 1 day, ISE shows 47,640 hits on my poli...
Disregard. Was due to my own stupidity. I failed to wrap my variable in curly brackets, so my API call was sending the literal word siteId rather than the actual siteId.
