01-26-2026 02:14 PM
I've been leveraging the command runner API to gather data on our network for analysis/parsing via python. In most instances I am able to use piped commands "show run | inc interface | description" or similar to retrieve data, pass into python, and parse for other actions such as template provisioning. I'm currently working on a script to identify ports that are not 802.1X compliant. I already have a template setup that will fix the problem, but I want a script that will identify who/what we will break before implementing.
At this time, I will not paste the script as I am still developing it and need to overcome the command "blacklist" issue but know that I can pipe commands as I have a separate command-runner script that I use for pre-parsing activities.
Question: Does Catalyst Center have a limit on the number of pipes a command can contain or a character limit?
Example command throwing errors: Show run | inc interface | description| switchport mode access| authentication open| authentication port-control auto|!
Thank you in advance.
Solved! Go to Solution.
01-26-2026 02:32 PM
Catalyst center does not like to show details on authentication (this appears to be the no no word). This may be due to FIPS being enabled or is a safeguard in general.
In case anyone else runs into the issue- a successful workaround is
"show run | inc interface| description| switchport mode access| open| port-control|!"
01-26-2026 02:32 PM
Catalyst center does not like to show details on authentication (this appears to be the no no word). This may be due to FIPS being enabled or is a safeguard in general.
In case anyone else runs into the issue- a successful workaround is
"show run | inc interface| description| switchport mode access| open| port-control|!"
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide