100 5599k 0 5599k 0 0 4691k 0 --:--:-- 0:00:01 --:--:-- 4693k
File name for retrieved file will be as per the –o parameter string (eg. file is
called "diagnostics" in this example) in the command invokation.
Expected output (example for fail case, which indicates that Diag Package Retrieval could not be
completed):
Additional failure reason details may be determined by calling the DIAGSTAT API.
<?xml version="1.0" encoding="ISO-8859-1" ?><SESSIONINFO><STATUS>response failure,
rc=192512</STATUS></SESSIONINFO>
Note
Status API
This section describes the commands used to obtain input, output, and decode status information on the D9800
receiver.
RF Input Status Command
Table 14: Command Details
DescriptionCommand Detail
https://192.168.0.1/ws/v2/status/inputCommand URL
Return information about RF input.Command Information
GETHTTP Method
ReadAccess Type
Guest, User, AdminAccess Level
GET "https://192.168.0.1/ws/v2/status/input/rf?js=1"Syntax
URI Parameters (extension to the Command URL separated by /): N/A
Table 15: URI Query/Set Arguments (possible fields and values preceded by ? and separated by &)
DescriptionURI Argument
Input port status to be returned.
Type: Integer
Values: 1..16 [NFE1 : 1..4, NFE2: 5..8, NFE3: 9..12, NFE4: 12..16]
This does not refer to the NTC Ethernet ports, it refers
specifically to the RF ports.
Note
port (Key)
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
25
API Definitions
Status API
To Next Page
Loading...
Need help?
General
