If you’ve spent any time with the ACI interface, you’ve probably realized that herding a mouse around a browser is fine for small/one-time operations, but does not scale when you have a large quantity of repetitive operations.
Maybe you started using Postman to run API queries, but you want to build a succession of queries and roll them up in a script. If you’re competent with Python, you might even be using the Cobra SDK or ACI Toolkit to develop anything from simple scripts to integration with other infrastructure components.
On the other hand, maybe you like pain and suffering and have a preference for simple shell scripts. If this is you, you’ll be using curl.
In this series, we’ll explore using curl on the command line and in simple shell scripts for quick, repeatable operations.
If you’re not familiar with curl, it’s an excellent utility for interacting with HTTP servers, especially for performing CRUD operations against an API. Further, you can connect to other Unix tools by using conventional STDIN/STDOUT interfaces. This can help you quickly prototype applications by connecting components to repeat frequently-used tasks.
Anatomy of a curl request.
You’ve probably used curl to download a file from a webpage, like this:
Secondly, while the full curl manual page (“man curl” at your Unix/Linux prompt) is quite comprehensive, it can be challenging to find the exact switch you need among all the options available to you. A good online reference is useful. I personally find this Gist to be a good intro/quick reference for the most common curl options and usage.
Finally, parsing the XML output can be an adventure in formatting. Useful tools include json_pp and xmllint are common formatting utilities when working with raw curl output, while standard Unix tools like grep, sed, cut, etc will be indispensable.
In order to interact with the API, we will need to authenticate.
An authentication POST request will require a username/password, expressed using the aaaUser object. The XML version looks like this:
Substitute your username, password, and IP address/hostname as needed. The leading $ sign indicates a command prompt, and should not be typed.
The response will include a session token and a number of attributes. We can use the token to pass subsequent requests, but extracting the token programmatically can be painful when you just want to run a quick command or two.
We’ll use curl’s -c switch to save the info in a cookie file, named “COOKIE”:
Then, you simply use “-b COOKIE” in subsequent requests, such as retrieving a list of tenants:
You can pass XML output through the xmllint utility to format (indent) it:
Don’t forget that trailing hyphen! The pipe | character tells the shell to take the output of the curl command and use it as input to xmllint. The trailing hypen tells the xmllint program to read from input rather than a file.
Another way to do this is to save the output to a file, and then read the file using xmllint (or your favorite XML editor).
If you’re using JSON, you can use a tool called json_pp (“pretty print”) to get nice formatting:
We’ll dive more into using curl to interact with the APIC API in upcoming posts. But that wraps up today’s blog!
More blogs regarding ACI are yet to come right here on the ACI Board on Cisco Community. Make sure to drop a comment and let us know if this piece focused on “Curl” was helpful!
And as always, we’d love to know what other topics you’d like us to write about in future ACI blogs. Help us, help you!
Hello,We have one fabric composed by only 1 MDS 9148 switches, and now, we want to add a new 9148 S MDS switch to this fabric.one VSAN (100) and one zone set activated on this switch.Now, we need to add a new switch in fabric. This new switch is also one ...
Hi All, Spine Leaf designs I have seen so far show a single link from Leaf to each Spine and the recommended solution to increase aggregate fabric throughput is to add another Spine. Is it a valid design to have multiple links from Leaf to Spine to a...
I found two different theory to handle l3 traffic for unknown IP in ACI one is stated below which is from White Paper 739989 and in other cisco live document I have seen that this will be treated via spine proxy method. "For (L3) routed traffic to an...
I found below note in cisco white paper i.e 739989 - end point learning but unable to understand it. "An exception exists for remote MAC address learning when a packet is incoming from L3Out to Cisco ACI. If ARP traffic is coming from an L3Out SVI ra...
Dears ,Please check as the ACI sandbox does not accept any simple action on it from yesterday ? even creation of a tenant returns "Error: 400 - the messaging layer was unable to deliver the stimulus (connection error, Connection refused)"