Cisco D9800 Reference Manual page 188

PE Configuration Command
Expected output (values are for example purposes only):
{
"pe": {
}
}
POST Method Examples:
Use to Configure PE, XML and JSON are supported from the post file.
XML from file Example:
File contents of temp.xml:
<pe><record><peid>1</peid><chn>801</chn><inp>RF1</inp></record></pe>
Input (POST PE configuration info via file temp.xml):
curl -k -X POST -H "X-SESSION-ID: $token" --header "Content-Type:application/xml" -d
@"C:/projects/temp.xml" "https://192.168.0.1/ws/v2/service_cfg/pe"
Expected output (values are for example purposes only):
<?xml version="1.0" encoding="ISO-8859-1"
?><response><code>10</code><result>success</result><message></message></response>
JSON from file Example:
File contents of temp.js:
{
"pe": {
}
}
Input (POST PE configuration info via file temp.js):
curl -k -X POST -H "X-SESSION-ID: $token" --header "Content-Type:application/json" -d
@"C:/projects/temp.js" "https://192.168.0.1/ws/v2/service_cfg/pe?js=1"
Expected output (values are for example purposes only):
{
"response": {
}
}
To POST a channel change to a specific PE, in this case PE 1 and new channel will be 41 the following CURL
command applies:
Input (POST PE specific peid configuration info via command line):
curl -X POST -i -H "Accept: application/json" -H "X-SESSION-ID: $token" -k "https://
192.168.0.1/ws/v2/service_cfg/pe?peid=1&chn=41"
Expected output (values are for example purposes only):
{
"response": {
}
}
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
176
"record": {
"peid": "1",
"chn": "802"
}
"record": {
"peid": "1",
"chn": "802"
}
"code": "10",
"result": "success",
"message": ""
"code": "10",
"result": "success",
"message": ""
API Definitions