User Space SMO/Non-RT RIC Framework O-CU O-DU O-RU Tester Tester «INT»OTF «INT»OTF «OAM»Message-Router «OAM»Message-Router «SMO»VES-Collector «SMO»VES-Collector «OAM»OAM-Controller «OAM»OAM-Controller «NonrtRIC»Link Monitor «NonrtRIC»Link Monitor «SMO»DHCP «SMO»DHCP «INT»CA «INT»CA O-CU-CP O-CU-CP O-DU-High O-DU-High O-DU-Low O-DU-Low O-RU O-RU ODU Initialization Deferred from Release "D" 1Request IP Assigments 2IP Assignments, VES Server, CA Server 3Get Certificate 4Client Certificate 5«O1» PNP Event for O-DU 6  7Publish PNP Event 8Get Event (PNP) 9Get Event (PNP) 10PNP Notify Event 11PNP Notify Event Element not mounted; mount and discover capabilities 12«O1» SSH Using the TCP Connection,the NETCONF client initiatesan SSH session to the NETCONF Server/O-DU 13«O1» NETCONF Hello/Capabilities Using the SSH connection,the NETCONF client initiatesa NETCONF session to the NETCONF Server/O-DU 14«O1» NETCONF Hello/Capabilities OAM will publish some form of VES event we need to identify this event.OTF will need to subscribecan in startup ando GET here thenOTF will know to move to the next step in the test strategy 15ODU Config 16«O1» edit-config (initConfig) CUS Link Establishment The following sequences are only representative of a much larger conversationBetween the OCUCP and the ODU-High as part of the F1 Setup and Link Establishment 17«F1» F1 Setup Request 18F1 Setup Response 19«FAPI» link config 20«FHCUS» CUS establishment 21«FAPI» Link Status 22«F1c» Cell Status 23Config Complete 24200 OK 25ORU Alarm Subscription 26«FHMP» Alarm Subscription 27«FHMP» Config Complete 28200 OK

  • No labels

2 Comments

  1. David Kinsey

    Martin Skorupski We need to know what the event is after message 14 so OTF can susbcribe to that message! I could not find it in the flows I received.

    1. Martin Skorupski

      The related jira: https://jira.onap.org/browse/SDNC-889

      Ravi Pendurty : could you please provide the related topic and an example json here- many thanks...


      Thanks Ravi to the details:

      David Kinsey : OTF needs to subscribe for topic: unauthenticated.VES_NOTIFICATION_OUTPUT


      Here is an example of the content:

      {
  "event": {
    "commonEventHeader": {
    "domain": "notification",
    "eventId": "<identifier of the O-DU>_<connection-status>_<sequence-number>",
    "eventName": "<identifier of the O-DU>_<connection-status>_<sequence-number>",
    "eventType": "",
    "lastEpochMicrosec": 161337345785800,
    "nfcNamingCode": "",
    "nfNamingCode": "",
    "nfVendorName": "",
    "priority": "Normal",
    "reportingEntityName": "ONAP SDN-R",
    "sequence": 9,
    "sourceId": "",
    "sourceName": "<identifier of the O-DU>",
    "startEpochMicrosec": 161337345785800,
    "timeZoneOffset": "+00:00",
    "version": "4.1",
    "vesEventListenerVersion": "7.1.1"
  },
  "notificationFields": {
    "arrayOfNamedHashMap": [],
   "changeIdentifier": "<identifier of the O-DU>",
   "changeType": "ConnectionState",
   "newState": "Connected",
   "notificationFieldsVersion": "2.0"
  }
 }
}