Cisco ACI Troubleshooting with icURL: Faults & Events

Troubleshooting Cisco ACI with icURL

cisco aci icurl
Cisco ACI troubleshooting typically starts with collecting records and analyzing data for anomalies. Using the ACI icURL utility is an alternative to moquery and a quick way to pull down data for review.

Using the Cisco ACI icURL utility is ideal to transfer data  because of its inherent progress indicator that indicates the amount of transferred data, transfer speeds and estimated time left. If you must use the insecure SSL connection option in the lab, the “-k” flag can be used as shown in the examples below.

    • Create directory

      Add a directory in the Cisco ACI filesystem.

      mkdir /tmp/myrecords
      cd /tmp/myrecords

      Collect fault info

      Save Cisco ACI fault information.

      icurl –k 'https://localhost/api/class/faultInfo.xml' > faultInfo.xml

      Collect fault records

      Save Cisco ACI fault records.

      icurl –k 'https://localhost/api/class/faultRecord.xml' > faultRecord.xml

      Collect event records

      Save Cisco ACI event records.

      icurl –k 'https://localhost/api/class/eventRecord.xml' > eventRecord.xml

      Collect change records

      Save Cisco ACI change records.

      icurl –k 'https://localhost/api/class/aaaModLR.xml' > aaaModLR.xml

      Collect auth records

      Save Cisco ACI authentication records.

      icurl –k 'https://localhost/api/class/aaaSessionLR.xml' > aaaSessionLR.xml

      Collect configuration

      Save Cisco ACI configuration to review.

      icurl -k 'https://localhost/api/mo/uni/tn-TenantTest123.xml?rsp-subtree=full&rsp-prop-include=config-only' > TenantTest123

      Archive collected records

      Aggregate Cisco ACI records for further troubleshooting and analysis.

      cd /tmp
      tar cvzf myrecords.tgz myrecords

See also:
Cisco ACI ELAM Packet Capture
Cisco ACI Automation with cURL
Cisco ACI Python Cobra Examples
Cisco ACI Troubleshooting with Moquery