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.
One detail I’d check first is the direction of the connection. A ping from the border router through NAT to Catalyst Center doesn’t prove Catalyst Center can initiate discovery back to the device’s management IP. Which IP are you entering in Discover...
I’d split the testing into two questions: did the API request succeed, and did the network end up in the state you intended? Those aren’t always the same thing. In an isolated lab, I’d capture a baseline, make one small change, then check the routes,...
That helps, thanks. So trimming the tool list isn't enough if the agent can still reach an account with more rights. I'd give it its own read-only account and keep every other credential out of its reach. For the audit side, where would you look to s...
I’d start with troubleshooting: pull device health and client details into one place so I can review them, without letting the AI make changes.I saw in the Catalyst Center README that the MCP server uses the account’s permissions and doesn’t enforce ...
HTTP 200 and DNS success are separate here: a valid DoH response can carry a DNS error. RFC 8484 §4.2.1 explains that distinction: https://www.rfc-editor.org/rfc/rfc8484.html#section-4.2.1 To narrow it down, does the same query from the same network ...