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!
Hi Experts , We are facing an communication issue during replication(backup) between 2 servers SERVER-01 and SERVER-02 .SERVER-01 is a production server and SERVER02 is backup server . May be during the backup the communication fails . We ...
Hi Experts , We have 10Gig interface which is connected to the server , We would like to know the send and receive buffer size of this interface say Eth1/47 ? Is there any command to know the buffer value ?
I'm having an issue with BGP sessions expiring. This issues seems to resolve itself after hours/days then works solidly for weeks before the issue then re-occurs and i'm drawing up a blank. All the iBGP sessions work without issues jus...
I'm trying to find out or work out what determines the logging level into the logging buffer, specifically I'd like to include IP SLA and Object Tracking Up and Down events. As far as I can determine Object Tracking events are classed as "notification...