Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Table of Contents |
|---|
Objective
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'.
(under discussion)
VES:commonEventHeader
implementation of OpenDaylight Aluminium (link)
domain
Static text "pnfRegistration"
eventId
The value Value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
eventName
The value 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
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.
priority
Static text "Normal"
priority
Static text "Normal"
reportingEntityId
The OAM-Controller identifier with in the SMO - e.g. the fully qualified domain name or IP-Address.
If a VES:pnfRegistration event is fetched from the Message-Router, then this VES:pnfRegistration event must not processed and must be ignored, avoiding double registration by NetConf Callhome and VES:pnfRegistration
reportingEntityName
as configured by helm charts for the OpenDaylight cluster name
sequence
As per NetConf notification increasing sequence number as unsigned integer 32 bits. The value is reused in the eventId field.
sourceId
Value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
sourceName
Value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
startEpochMicrosec
Current OAM-Controller Node timestamp in unix time format - as microseconds elapsed since 1 Jan 1970 not including leap seconds.
Q: is it possbile to read a timestemp from the NetConf Callhome message?
timeZoneOffset
Static text: "+00:00" - Please note, the time format in all related OAM controller times is in UTC time format - a mapping to other time formats happens in presentation layer only (e.g. on user settings, bowser settings, ...)
version
Static text: "4.1"
vesEventListenerVersion
Static text "7.1.1"
VES:pnfRegistrationFields
additionalFields
not mapped
lastServiceDate
not mapped
macAddress
manufactureDate
modelNumber
oamV4IpAddress
oamV6IpAddress
pnfRegistrationFieldsVersion
Static text: "2.0"
serialNumber
softwareVersion
unitFamily
unitType
vendorName
The value of ietf-hardware (RFC8348) /hardware/component[1]/mfg-name.