Cisco Cisco Evolved Programmable Network Manager 2.0 开发者指南
Cisco Evolved Programmable Network Manager 2.0.1 RESTCONF API Guide
151
<
p:network-interface
>
<
p:name
>
TestZUNI238
</
p:name
>
<
p:operation
>
add
</
p:operation
>
<
p:ce-data
>
<
p:description
>
TestUNI
</
p:description
>
<
p:qos-profile-
ref
>
MD=CISCO_EPNM!PROFILE_QOS=MyUniProfile1
</
p:qos-profile-ref
>
<
p:mtu
>
1522
</
p:mtu
>
<
p:speed
>
5
</
p:speed
>
<
p:mode
>
FULL DUPLEX
</
p:mode
>
<
p:ce-vlanid
>
10
</
p:ce-vlanid
>
<
p:service-multiplexing
>
true
</
p:service-multiplexing
>
<
p:enable-oam
>
false
</
p:enable-oam
>
</
p:ce-data
>
</
p:network-interface
>
</
p:network-interface-list
>
</
p:service-order-data
>
</
p:provision-service-request
>
7.27.1.2
Response
HTTP/1.1 201 Created
Server: <epnm-host>
Content-Type: application/yang.operation+xml
{
"customer": "MD=CISCO_EPNM!CUSTOMER=Infrastructure",
"service-id": "7f52d296-ad73-4d0e-891c-2aceab5e2687",
"service-name": "TestEPlService123",
"service-type": "carrier-ethernet-vpn",
"circuit-type": "EPL",
"deploy-action": "Deploy",
"operation-type": "ProvideService",
"request-time": "Tue May 17 16:29:50 PDT 2016",
"completion-status": "SUBMITTED",
"generic-notification-url": "http://storm-dev-lnx46.cisco.com/restconf/streams/v1/service-activation",
"request-specific-notification-url": "http://storm-dev-lnx46.cisco.com/restconf/streams/v1/service-
activation/7f52d296-ad73-4d0e-891c-2aceab5e2687"
}
Server: <epnm-host>
Content-Type: application/yang.operation+xml
{
"customer": "MD=CISCO_EPNM!CUSTOMER=Infrastructure",
"service-id": "7f52d296-ad73-4d0e-891c-2aceab5e2687",
"service-name": "TestEPlService123",
"service-type": "carrier-ethernet-vpn",
"circuit-type": "EPL",
"deploy-action": "Deploy",
"operation-type": "ProvideService",
"request-time": "Tue May 17 16:29:50 PDT 2016",
"completion-status": "SUBMITTED",
"generic-notification-url": "http://storm-dev-lnx46.cisco.com/restconf/streams/v1/service-activation",
"request-specific-notification-url": "http://storm-dev-lnx46.cisco.com/restconf/streams/v1/service-
activation/7f52d296-ad73-4d0e-891c-2aceab5e2687"
}
7.27.1.3
Notification
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<push-change-update xmlns="urn:cisco:params:xml:ns:yang:yang-push:v1"
xmlns:ns2="urn:cisco:params:xml:ns:yang:service:activation:v1">
<subscription-id>-437627140558950385</subscription-id>
<topic>/streams/v1/service-activation</topic>
<time-of-update>Tue May 17 16:30:27 PDT 2016</time-of-update>
<operation>configure</operation>
<update-data>
<ns2:provision-service-response>
<ns2:cfs-ref>MD=CISCO_EPNM!CFS=TestEPlService123</ns2:cfs-ref>
<ns2:customer>MD=CISCO_EPNM!CUSTOMER=Infrastructure</ns2:customer>
<push-change-update xmlns="urn:cisco:params:xml:ns:yang:yang-push:v1"
xmlns:ns2="urn:cisco:params:xml:ns:yang:service:activation:v1">
<subscription-id>-437627140558950385</subscription-id>
<topic>/streams/v1/service-activation</topic>
<time-of-update>Tue May 17 16:30:27 PDT 2016</time-of-update>
<operation>configure</operation>
<update-data>
<ns2:provision-service-response>
<ns2:cfs-ref>MD=CISCO_EPNM!CFS=TestEPlService123</ns2:cfs-ref>
<ns2:customer>MD=CISCO_EPNM!CUSTOMER=Infrastructure</ns2:customer>