Cisco Cisco Prime Performance Manager 1.7 개발자 가이드
Cisco Prime Performance Manager 1.7 REST API Guide
Content-Range: pages 1/8
Cache-Control: no-cache
Cache-Control: no-cache
Device,Interface,Timestamp,Interface Index,Interface Availability Percentage
Down,Interface Availability Percentage Up,Interface Availability Percentage
Timeout
ems3825d,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ems3825j,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ems7606d,GigabitEthernet5/2,2012-10-05T05:00-0400,22,0.0,100.0,0.0
ems7606d,EOBC0/0,2012-10-05T05:00-0400,41,0.0,100.0,0.0
ems7606d,EOBC0/2,2012-10-05T05:00-0400,42,0.0,100.0,0.0
ems7606d,SPAN RP Interface,2012-10-05T05:00-0400,44,0.0,100.0,0.0
ems3825e,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ppm5580a,Adaptive Security Appliance management interface,2012-10-05T05:00-
0400,2,0.0,100.0,0.0
ppm5580a,Adaptive Security Appliance Virtual254 interface,2012-10-05T05:00-
0400,8,0.0,100.0,0.0
. . . .
. . . .
SimLab-30.4.1.90,My_ifAlias_string-GigabitEthernet01,2012-10-05T12:00-
0400,3,0.0,100.0,0.0
Down,Interface Availability Percentage Up,Interface Availability Percentage
Timeout
ems3825d,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ems3825j,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ems7606d,GigabitEthernet5/2,2012-10-05T05:00-0400,22,0.0,100.0,0.0
ems7606d,EOBC0/0,2012-10-05T05:00-0400,41,0.0,100.0,0.0
ems7606d,EOBC0/2,2012-10-05T05:00-0400,42,0.0,100.0,0.0
ems7606d,SPAN RP Interface,2012-10-05T05:00-0400,44,0.0,100.0,0.0
ems3825e,GigabitEthernet0/0,2012-10-05T05:00-0400,1,0.0,100.0,0.0
ppm5580a,Adaptive Security Appliance management interface,2012-10-05T05:00-
0400,2,0.0,100.0,0.0
ppm5580a,Adaptive Security Appliance Virtual254 interface,2012-10-05T05:00-
0400,8,0.0,100.0,0.0
. . . .
. . . .
SimLab-30.4.1.90,My_ifAlias_string-GigabitEthernet01,2012-10-05T12:00-
0400,3,0.0,100.0,0.0
6.4.2 JSONv2
The JSON report format version 2 is a simpler and easier to traverse JSON data structure. It can
be obtained by passing the “outputType=jsonv2” query string parameter or passing the
HTTP Accept header “application/vnd.cisco.ppm+json;v=2”.
be obtained by passing the “outputType=jsonv2” query string parameter or passing the
HTTP Accept header “application/vnd.cisco.ppm+json;v=2”.
Table 55 – JSONv2 Request / Response Sample – “Interface Availability” Network Level Report
Request / Response (JSON) - “Interface Availability” Network Level Report
Request – Notice, the outputType query string parameter is set “
json
”.
GET
/ppm/rest/reports/Application+Traffic/AAA/AAA+Accounting+Dashboard?
/ppm/rest/reports/Application+Traffic/AAA/AAA+Accounting+Dashboard?
outputType
=jsonv2
HTTP/1.1
Host: ppm-clean.cisco.com:4440
Connection: Keep-Alive
User-Agent: RestClient-Tool
Response
HTTP/1.1 206 Partial Content
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 21:18:30 GMT
Connection: Keep-Alive
User-Agent: RestClient-Tool
Response
HTTP/1.1 206 Partial Content
Transfer-Encoding: chunked
Date: Fri, 05 Oct 2012 21:18:30 GMT
Content-Type: application/json;charset=UTF-8
Server: Apache-Coyote/1.1
Content-Range: pages 1/1
Cache-Control: no-cache
Content-Range: pages 1/1
Cache-Control: no-cache
{
"report": {
"name": "AAA Accounting Dashboard",
"header": [
"Device",
"Timestamp",
"Server",
"Protocol",
"Requests Requests",
"report": {
"name": "AAA Accounting Dashboard",
"header": [
"Device",
"Timestamp",
"Server",
"Protocol",
"Requests Requests",