Typically network-functions supporting NetConf Callhome do not support at the same time the VES event 'pnfRegistration'. In order inform the µServices within the SMO, a functionality as OAM-Controller level should be implemented. This function should send a VES pnfRegistration event to the VES-Collector when a new mount-point is created which is listed in the allowed devices.
As the OAM controller is listening to VES.pnfRegistration to establish NetConf sessions for "O-RAN O1 nodes" the VES:pnfRegistration invoked by the OAM-Controller must be ignored.
Sequence Diagram
Implementation
It is assumed that the existing "MountPoint-Registrar" functionality could be enhanced.
Please note that the ODL version Aluminum does not support NetConf Callhome for TLS. It should be checked, if the OpenDaylitght version Silicon (R0 March 2021) could be used instead.
Mapping to VES pnfRegistration fields
The following mapping table bases on the capabilities of OpenDaylight version Aluminum and maps them to the VES 7.2 fields for domain 'pnfRegistration'.
The value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
eventName
The value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
eventType
Static text: "NetConf Callhome Registration"
internalHeaderFields
not mapped
lastEpochMicrosec
Time of OAM-Controller
nfcNamingCode
always ""
nfNamingCode
always ""
nfVendorName
Static text "O-RAN Alliance"
alternative: The value of ietf-hardware (RFC8348) /hardware/component[1]/mfg-name. The synchronization with the inventory of the device would delay the PNF registration event.