This page captures the details of the updated FM message (alarm) reported by RAN (Sim) towards ONAP over VES, and the associated processing.
Assumptions
- A separate alarm will be sent for each collision and each confusion.
- An explicit alarm_off condition will be sent by RAN to ONAP (severity: NORMAL).
- An alarm on/off shall be sent only once by RAN-Sim. We don't cover cases of alarm message getting "lost".
- Though the alarm itself shall contain sufficient information for triggering OOF, we shall not make updates to CPS based on it. CPS updates for neighbor list changes shall be done only by SDN-R and only upon reception of CM-Notify and a Control Loop message from Policy.
Updated FM message
{ "event":{ "commonEventHeader":{ "version":"4.0.1", "vesEventListenerVersion":"7.0.1", "domain":"fault", "eventName":"Fault_RansimAgent-Wipro_RanPCIProblem", "eventId":"fault000001", "sequence":1, "priority":"High", "reportingEntityId":"de305d54-75b4-431b-adb2-eb6b9e546014", "reportingEntityName":"ncserver2", "sourceId":"cc305d54-75b4-431b-adb2-eb6b9e541234", "sourceName":"Chn0025", //denotes the cell experiencing the issue, this can continue to be the same "startEpochMicrosec":1451772223000000, "lastEpochMicrosec":1451772403000000, "timeZoneOffset":"UTC-05:30", "nfNamingCode":"RansimAgent", "nfVendorName":"Wipro" "eventCategory: "PCICollision" (or) "PCIConfusion" }, "faultFields":{ "faultFieldsVersion":"4.0", "alarmCondition":"RanPciCollisionConfusionOccurred", "eventSourceType":"other", "specificProblem”: “<Cell-id(s) of the cell(s) causing the problem, separated by commas>” "eventSeverity":"CRITICAL", //NORMAL for clearing "vfStatus":"Active", "alarmAdditionalInformation":{ //This is not needed now "networkId":"NTWK005", "collisions":"1", "confusions":"1" } } } }