Cisco D9800 Reference Manual page 125

API Definitions
URI Argument
js (optional)
Table 101: Output Field Descriptions
Output Field
link
speed
duplex
xover
Input example (request XML output format for data for all Ethernet ports):
curl -k -H "X-SESSION-ID: $token" "https://192.168.0.1/ws/v2/status/device/eth"
Expected output (values are for example purposes only):
<?xml version="1.0" encoding="ISO-8859-1" ?>
<device><eth><port>1</port><link>Link Up</link><speed>1
Gbps</speed><duplex>Full</duplex><xover>N/A</xover></eth><eth><port>2</port><link>Link
Down</link><speed>N/A</speed><duplex>N/A</duplex><xover>N/A</xover></eth><eth><port>3</port><link>Link
Down</link><speed>N/A</speed><duplex>N/A</duplex><xover>N/A</xover></eth></device>
Input example (get status of Ethernet port 1 in JSON format):
curl -k -H "X-SESSION-ID: $token" "https://192.168.0.1/ws/v2/status/device/eth?port=1&js=1"
Expected output (values are for example purposes only):
{
"device": {
"eth": {
"port": "1",
"link": "Link Up",
"speed": "1 Gbps",
"duplex": "Full",
"xover": "N/A"
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
Description
Format output using JSON standard.
Type: exist
Values: any value or empty (any of js=1, js, js=0, or js=9999 are
valid)
Omitting this argument formats the output by default in XML
Description
Ethernet link status
Type: String
Value: "Link Up" or "Link Down"
Ethernet link speed
Type: String
Value: "10 Mbps", "100 Mbps", "1 Gbps", or "N/A"
Ethernet link speed
Type: String
Value: "Half", "Full", or "N/A"
Ethernet MDI status (crossover)
Type: String
Value: "MDI", "MDIX", or "N/A"
Device Status Command
113