Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Restconf Notification 

This is the Service Down Alarm message Route/LinkId sttatus notification example from SOTN Controller.

Code Block
languagetext
titleService Down Alarm
collapsetrue
  
  "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": :{
          "ietf-yang-patch:yang-patch": {
             "remotepatch-nodeidid": "x.x.x.xd1d08ce8-b24d-4efb-a0e7-7b835642f2f1",
             "remote-tp"edit": y [
          },
          "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
languagetext
titleRestconf Collector Output (JSON)
collapsetrue
# 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": {
                      },    "transparent": "true"
           “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” "ietf-te-topology:te": {
#       for common header:
           “sourceId”  "admin-status": "$ietf-restconf:notification.datastore-changes.itef-yang-patch:yang-patch.edit.target”,up",
     #....  could be mapped in Restconof2VES.xml
           “startEpocMicrosec”"interface-switching-capability": “$eventTime”,[
           “lastEpocMicrosec”:  “$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
      "te-bandwidth": {
    “Priority”: “High”, 
           “reportingFrom”: “Domain_Controller",
#....   for fault fields:
         "ietf-eth-te-topology:eth-bandwidth": "1000000"
    “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”"switching-capability":  “network-ref”,"switching-l2sc"
                 “value”:  “$network-ref”
     }
             },
         ],
         {
                  “name” : “node-ref"oper-status": "up",
                  “value”:  “$node-ref”
  "inter-domain-plug-id": "51000"
                    },
                  {   "ietf-te-topology:te-tp-id": "1",
                  “name”: “tp-ref”,  "tp-id": "1"
                  “value”:“$tp-ef”,}
                  }, ]
              }
    {
        }
          “name”:]
  “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
languagetext
titleRestconf Collector Output (JSON)
collapsetrue
{
  "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,
  “value”:  “$te-tp-id” 
                  },           "datastore-changes": {
        "ietf-yang-patch:yang-patch": {
          "patch-id": "d1d08ce8-b24d-4efb-a0e7-7b835642f2f1",
       {
   "edit": [
            {
  “name”:  “tp-id”,
                  “value”:  “$tp-id”"edit-id": "0",
                  }"operation": "merge",
                  {"target": "/network=providerId%2F5555%2FclientId%2F6666%2FtopologyId%2F11/node=example-node/ietf-network-topology:termination-point=14",
                  “name”:  “inter-domain-plug-id”,"value": {
                "ietf-network-topology:termination-point": [
                “value”:  “$inter-domain-plug-id”{
                  }
  "supporting-termination-point": [
               ]
       }{
}       
                 "network-ref": "providerId/5555/clientId/6666/topologyId/33",
           

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

...

languagetext
titleRestconf2VES.xml
collapsetrue
             "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
languagetext
titleRestconf2VES.xml
collapsetrue


UVA subscribes RESTCONF_ALARM_TOPIC on DMAAP.

Route Down Alarm 

Code Block
languagetext
titleRoute Down Alarm (VES/CEDM)
collapsetrue
{
    "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",
            "alarmAdditionalInformation": [

UVA subscribes RESTCONF_ALARM_TOPIC on DMAAP.

Route Down Alarm 

Code Block
languagetext
titleRoute Down Alarm (VES/CEDM)
collapsetrue
{
    "event": {
        "commonEventHeader": {
            "sourceIdname": example-linkeid"inter-domain-id", // 'target' from the restconf notification.
            "startEpochMicrosec": 1413378172000000,
   
         "eventId": "ab305d54-85b4-a31b-7db2-fb6b977766",
            "sequencevalue": 0,"service-instance-01"
            "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"
        }
    }
}

...