Page History

...

1. SDC/CLAMP Portal design and activate policy.
2. SDC/CLAMP config and activate the policy.
3. SDC/CLAMP distribute the DCAE config.
4. SDC/CLMAP distribute the alarm correlation rules to Holmes.
5. 3rd party SOTN controller report link down alarm to DCAE
6. DCAE will do data cleaning and filtering for the alarms
7. DCAEk keep track the datas.
8. Holmes do analysis for the alarms.
9. Holmes notify the reroute event.
10. Policy matching the reroute rules.
11. Policy call SO to delete the old services and create the new services. For the creation flow, a variable route will be recalculated.

CLAMP  (TBD)

...

CLAMP  

Currently collector’s are not deployed on-demand, they are pre-deployed in DCAE and used by all the mS and all control loops. So the

collector’s, currently, are not deployed via CLAMP and there is no cloudify blueprint available to do so anyway. The collector box you see

in CLAMP GUI is just a virtual box to show the control loop flow, in reality there is no configuration made by CLAMP for the collector (at

least at this stage of ONAP, it might change in the future).

DCAE

DCAE  Flow

1. RestConf Collector (RC)subscribes for remote failure alarm to SOTN Controller (SC) 
2. RC requests to set up a long term tunnel with the 3rd party SC
3. SC responses with OK upon successful tunnel setting
4. SC pushes service route status data to the collector
5. RC receives alarm data, converts it into JSON format and publishes on DMAAP with topic of ROUTE_ALARM_OUTPUT
6. UVA consumes the alarm message
7. UVA requests the RestConf2VES mapping
8. UVA converts json alarm into VES  event
9. UVA publishes the VES event on DMAAP for further correlation 

...

{
“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
    }
}

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

...

UVA subscribes RESTCONF_ALARM_TOPIC on DMAAP.

Route Down Alarm 

{
    "event": {
        "commonEventHeader": {
            "sourceId": "example-sotn-controller-id-val-51834", // The value should be the same as what you set to the VM you just mocked.
            "startEpochMicrosec": 1413378172000000,
            "eventId": "ab305d54-85b4-a31b-7db2-fb6b977766",
            "sequence": 0,
            "domain": "fault",
            "lastEpochMicrosec": 1413378172000033,
            "eventName": "Fault_Route_Failure",
            "sourceName": "example-SOTN-Controller-name-val-5470", // The value should be the same as what you set to the VM you just mocked.
            "priority": "High",
            "version": 3.0,
            "reportingEntityName": "Domain_Contorller"
        },
        "faultFields": {
            "eventSeverity": "CRITICAL",
            "alarmCondition": "Route_Down",
            "faultFieldsVersion": 2.0,
            "specificProblem": "Fault_SOTN_Service_Failure",
            "alarmAdditionalInformation": [{
                    "name": "service-instancec-id",
                    "value": "service-instance-01"
                },
                 {
                    "name": "remote-nodeId",        // ... might not be needed
                    "value": "example-node-id"
                }
            ]
            "eventSourceType": "other",
            "vfStatus": "Active"
        }
    }
}

...

These alarms are published to the unauthenticated.SEC_FAULT_OUTPUT topic of DMaaP.

DCAE Blueprint

HOLMES

CCVPN Close Loop requires Holmes to correlate route down alarms from SOTN Controllers from different sites. (Refer to this page on Holmes installation,)

...