...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# original imagination { “service_status”: { “external_domain”: { “remote-nodeid” : “ example-remote-nodeid”, “remote-tpid” : “ example-remote-tpid” }, “source”? {“source-tpid”: “example-source-tpid”}, “oper-status”: “down”, “mapping-id” : “restconf2ves-001, “service-instance-id”: service-instance-01 } } #closer to the real one { “restconf-notification”: { # for common header: “sourceId” : "$ietf-restconf:notification.datastore-changes.itef-yang-patch:yang-patch.edit.target”, #.... could be mapped in Restconof2VES.xml “startEpocMicrosec”: “$eventTime”, “lastEpocMicrosec”: “$eventTime”, “eventName”: “Fault_Route_Failure”, #.... could be mapped in Restconof2VES.xml “targetName”: “$datastore-changes.itef-yang-patch.edit.target”, #.... could be mapped in Restconof2VES.xml “Priority”: “High”, “reportingFrom”: “Domain_Controller", #.... for fault fields: “eventSeverity” : “CRITICAL”, “alarmCondition”: “Routedown”, #.... could be mapped in Restconof2VES.xml “specificProblem”: “Fault_SOTN_Server_Failure”, #.... could be mapped in Restconof2VES.xml #... the following could be mapped in Restconof2VES.xml “varbinds:”: [{ “name”: “network-ref”, “value”: “$network-ref” }, { “name” : “node-ref", “value”: “$node-ref” }, { “name”: “tp-ref”, “value”:“$tp-ef”, }, { “name”: “te-tp-id”, “value”: “$te-tp-id” }, { “name”: “tp-id”, “value”: “$tp-id” }, { “name”: “inter-domain-plug-id”, “value”: “$inter-domain-plug-id” } ] } } |
VES MAPPER
The Restconf2VES.xml could be uploaded to DCAE at the closed loop deployment from DCAE Designer. For now, it will be manually uploaded to the mapper at the closed loop instantiation.
...