...
Restconf Notification
This is the Service Down Alarm message Route/LinkId sttatus notification example from SOTN Controller.
Code Block |
---|
language | text |
---|
title | Service Down Alarm |
---|
collapse | true |
---|
|
"ietf-network-topologyrestconf:linknotification": {
"eventTime": "2018-07-28T09:15:03.924Z",
{ "ietf-yang-push:push-change-update": {
"linksubscription-id": "teNodeId/0.5.0.12/telinkId/1",
"externaldatastore-domainchanges" :
{
"remote-nodeid": "x.x.x.x","ietf-yang-patch:yang-patch": {
"remote-tp": y"patch-id": "d1d08ce8-b24d-4efb-a0e7-7b835642f2f1",
"edit": [
}, "source": {
"sourceedit-nodeid" : "0.5.0.12",
"source-tpoperation" : "1merge",
} "ietf-te-topology:te" : {"target": "/network=providerId%2F5555%2FclientId%2F6666%2FtopologyId%2F11/node=example-node/ietf-network-topology:termination-point=14",
"oper-statusvalue": "down", {
"te-link-attributesietf-network-topology:termination-point": {[
"max-link-bandwidth" : {
"tesupporting-termination-bandwidthpoint" : "1000000"[
}, {
"max-resv-link-bandwith" : { "network-ref": "providerId/5555/clientId/6666/topologyId/33",
"te-bandwidth" : "1000000"node-ref": "node-ref-example",
"tp-ref": "33488898"
}, }
... ... } |
Route Alarm Message
This is the message definition at output of Restconf collector to DMAAP with topic of RESTCONF_ALARM_TOPIC.
Code Block |
---|
language | text |
---|
title | Restconf Collector Output (JSON) |
---|
collapse | true |
---|
|
# original imagination {
“service_status”: {],
“external_domain”: { "ietf-eth-te-topology:svc": {
“remote-nodeid” : “ example-remote-nodeid”, "client-facing": "true",
“remote-tpid” : “ example-remote-tpid” "supported-classification": {
}, “source”? {“source-tpid”: “example-source-tpid”}, "transparent": "true"
“oper-status”: “down”, }
“mapping-id” : “restconf2ves-001, “service-instance-id”: service-instance-01
}
}},
#closer to the real one { “restconf-notification”: { # for common header "ietf-te-topology:te": {
“sourceId” : "$ietf-restconf:notification.datastore-changes.itef-yang-patch:yang-patch.edit.target”, #.... could be mapped in Restconof2VES.xml "admin-status": "up",
“startEpocMicrosec”: “$eventTime”, “lastEpocMicrosec”"interface-switching-capability": “$eventTime”,[
“eventName”: “Fault_Route_Failure”, {
"encoding": "lsp-encoding-ethernet",
"max-lsp-bandwidth": [
#.... could be mapped in Restconof2VES.xml “targetName”: “$datastore-changes.itef-yang-patch.edit.target”, {
"priority": "7",
#.... could be mapped in Restconof2VES.xml “Priority”: “High”, "te-bandwidth": {
“reportingFrom”: “Domain_Controller", #.... for fault fields: “eventSeverity” : “CRITICAL”, "ietf-eth-te-topology:eth-bandwidth": "1000000"
}
“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”, "switching-capability": "switching-l2sc"
“value”: “$network-ref” }
}, ],
{ “name” "oper-status": “node-ref"up",
“value” "inter-domain-plug-id": “$node-ref”"51000"
},
{"ietf-te-topology:te-tp-id": "1",
“name”"tp-id": “tp-ref”,"1"
“value”:“$tp-ef”,}
]
}, }
{ }
]
“name”: “te-tp-id”, }
}
}
“value”: “$te-tp-id”
} |
Route Alarm Message
This is the message definition at output of Restconf collector to DMAAP with topic of RESTCONF_ALARM_TOPIC.
Code Block |
---|
language | text |
---|
title | Restconf Collector Output (JSON) |
---|
collapse | true |
---|
|
{
"notify_oid" : "example-mappingfile-id.x.1",
"ietf-restconf:notification": {
}"eventTime": "2018-07-28T09:15:03.924Z",
"ietf-yang-push:push-change-update": {
"subscription-id": 1,
"datastore-changes": {
"ietf-yang-patch:yang-patch": {
“name”: “tp-id”"patch-id": "d1d08ce8-b24d-4efb-a0e7-7b835642f2f1",
"edit": [
“value”: “$tp-id” {
}"edit-id": "0",
"operation": "merge",
{ “name”: “inter-domain-plug-id”"target": "/network=providerId%2F5555%2FclientId%2F6666%2FtopologyId%2F11/node=example-node/ietf-network-topology:termination-point=14",
"value": {
“value”: “$inter"ietf-domainnetwork-plug-id”topology:termination-point": [
{
} "supporting-termination-point": [
] } } {
|
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.
Mapping XML
...
language | text |
---|
title | Restconf2VES.xml |
---|
collapse | true |
---|
UVA subscribes RESTCONF_ALARM_TOPIC on DMAAP.
Route Down Alarm
Code Block |
---|
language | text |
---|
title | Route Down Alarm (VES/CEDM) |
---|
collapse | true |
---|
|
{
"event": {"network-ref": "providerId/5555/clientId/6666/topologyId/33",
"node-ref": "node-ref-example",
"tp-ref": "33488898"
}
],
"ietf-eth-te-topology:svc": {
"client-facing": "true",
"supported-classification": {
"transparent": "true"
}
},
"ietf-te-topology:te": {
"admin-status": "up",
"interface-switching-capability": [
{
"encoding": "lsp-encoding-ethernet",
"max-lsp-bandwidth": [
{
"priority": "7",
"te-bandwidth": {
"ietf-eth-te-topology:eth-bandwidth": "1000000"
}
}
],
"switching-capability": "switching-l2sc"
}
],
"oper-status": "up",
"inter-domain-plug-id": "51000"
},
"ietf-te-topology:te-tp-id": "1",
"tp-id": "1"
}
]
}
}
]
}
}
}
}
} |
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.
Mapping XML
Code Block |
---|
language | text |
---|
title | Restconf2VES.xml |
---|
collapse | true |
---|
|
|
UVA subscribes RESTCONF_ALARM_TOPIC on DMAAP.
Route Down Alarm
Code Block |
---|
language | text |
---|
title | Route Down Alarm (VES/CEDM) |
---|
collapse | true |
---|
|
{
"event": {
"commonEventHeader": {
"sourceId": example-linkeid", // 'target' from the restconf notification.
"startEpochMicrosec": 1413378172000000,
"eventId": "ab305d54-85b4-a31b-7db2-fb6b977766",
"sequence": 0,
"domain": "fault",
"lastEpochMicrosec": 1413378172000033,
"eventName": "Fault_Route_Failure",
"sourceName": "example-linkid", // 'Target' from the restconf notification.
"priority": "High",
"version": 3.0,
"reportingEntityName": "Domain_Contorller"
},
"faultFields": {
"eventSeverity": "CRITICAL",
"alarmCondition": "Route_Down",
"faultFieldsVersion": 2.0,
"specificProblem": "Fault_SOTN_Service_Failure",
"commonEventHeaderalarmAdditionalInformation": [{
"sourceId "name": example-linkeid", // 'target' from the restconf notification."inter-domain-id",
"startEpochMicrosec": 1413378172000000, "eventIdvalue": "ab305d54service-85b4-a31b-7db2-fb6b977766",
instance-01"
"sequence": 0, },
"domain": "fault", {
"lastEpochMicrosec": 1413378172000033, "eventNamename": "Fault_Route_FailurelinkId", "sourceName": "example-linkid", // 'Target' from the restconf notification.
"priorityvalue": "Highexample-linkId",
"version": 3.0, "reportingEntityName": "Domain_Contorller"},
}, {
"faultFields": { "eventSeverityname": "CRITICALnodeId", "alarmCondition": "Route_Down",
"faultFieldsVersion": 2.0, "specificProblemvalue": "Fault_SOTN_Service_Failure",example-linkId"
"alarmAdditionalInformation": [{ },
{
"name": "inter-domain-id", "name": "topologyId", // This is used by Holmes for alarm correlation
"value": "serviceexample-instance-01topologyId"
}
]
"eventSourceType": "other",
"vfStatus": "Active"
}
}
} |
...