Cisco D9800 - Page 294

<?xml version="1.0" encoding="ISO-8859-1"
?><response><code>0</code><result>success</result><message1>PING 10.132.24.34 (10.132.24.34):
56 data bytes
64 bytes from 10.132.24.34: seq=0 ttl=61 time=0.819 ms
64 bytes from 10.132.24.34: seq=1 ttl=61 time=1.498 ms
64 bytes from 10.132.24.34: seq=2 ttl=61 time=0.740 ms
64 bytes from 10.132.24.34: seq=3 ttl=61 time=0.687 ms
64 bytes from 10.132.24.34: seq=4 ttl=61 time=0.677 ms
--- 10.132.24.34 ping statistics ---
5 packets transmitted, 5 packets rece</message1><message2>ved, 0 percent packet loss
round-trip min/avg/max = 0.677/0.884/1.498 ms
</message2></response>
JSON format:
HTTP/1.1 200 OK
Date: Mon, 26 Jun 2017 13:02:55 GMT
Server: Hiawatha v9.14
Connection: keep-alive
Transfer-Encoding: chunked
Status: 200
Content-type: application/json
{
"response": {
"code": "0",
"result": "success",
"message1": "PING 10.132.24.34 (10.132.24.34): 56 data bytes\n64 bytes from
10.132.24.34: seq=0 ttl=61 time=0.819 ms\n64 bytes from 10.132.24.34: seq=1 ttl=61 time=1.498
ms\n64 bytes from 10.132.24.34: seq=2 ttl=61 time=0.740 ms\n64 bytes from 10.132.24.34:
seq=3 ttl=61 time=0.687 ms\n64 bytes from 10.132.24.34: seq=4 ttl=61 time=0.677 ms\n\n---
10.132.24.34 ping statistics ---\n5 packets transmitted, 5 packets rece",
"message2": "ved, 0 percent packet loss\nround-trip min/avg/max = 0.677/0.884/1.498
ms\n"
}
}
Expected output (example for Fail case which indicates that IP Diag report retrieval could not be
completed):
Additional failure reason details may be available by calling the IPDIAGSTAT API.Note
You can put unrecognized parameter (for example, /extra) on command line to test this case:
curl -i -k -H "X-SESSION-ID: $token" "https://10.85.163.98/ws/v2/ip_diags/extra"
HTTP/1.1 404 Not Found
Date: Mon, 26 Jun 2017 13:06:33 GMT
Server: Hiawatha v9.14
Connection: keep-alive
Transfer-Encoding: chunked
Status: 404
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
282
API Definitions
IP Diagnostics Commands