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 to inform the µServices within the SMO, a functionality as at OAM-Controller level should be implemented. This function should send a VES pnfRegistration event to the VES-Collector when a new NetConf Server, which is part of the callhome-allowed-devices list inside the OAM-Controller, sends a Callhome message and 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 via 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)
A couple of VES fields needs to be filled with values from a an Ietf:hardare/compoenent which does not have the leaf "parent". I more than one competent would not have the leaf "parent" then the first component should be used for such fields (e.g. manufacture name).
VES:commonEventHeader
implementation of OpenDaylight Aluminium (link)
domain
Static text "pnfRegistration"
eventId
Value of 'nt:network-topology/nt:topology/nt:node/nt:node-id'.
eventName
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
The value of ietf-hardware (RFC8348) /hardware/component[1]/mfg-name or empty string if not found.
Unter Under discussion: how to identify the "root" component?
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
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.12"
VES:pnfRegistrationFields
If an ieft-hardware component is not identified for the mapping into VES:pnfRegistrationFields or a and optional leaf is not provided, then the VES:pnfRegistrationFields should be part of the message with its default value (e.g. empty string "")
The ietf-hardware component must not have the 'parent' leaf.
additionalFields
not mapped
Note: a mapping of NetConf ports, and NetConf credentials are not required.
In case a fully qualified domain name is used by the O-RU, then the oamFqdn should be added here, The fields 'ves:oamV4IpAddress' and 'oamV6IpAddress' would be not in such ves.pnfRegistration message. Note: such use case is not expected for 2021.
lastServiceDate
Value of ietf-hardware (RFC8348) /hardware/last-changechange or "1970-01-01T00:00:00z" if not found.
macAddress
not mapped
manufactureDate
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/mfg-date or empty string if not found.
modelNumber
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/model-name.name or empty string if not found.
oamV4IpAddress
Value of 'nt:network-topology/nt:topology/nt:node/nt:host', IF in IPv4 format .otherwise an empty string
oamV6IpAddress
Value of 'nt:network-topology/nt:topology/nt:node/nt:host', IF in IPv6 format. otherwise an empty string
pnfRegistrationFieldsVersion
Static text: "2.0"
serialNumber
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/serial-num.num or empty string if not found.
softwareVersion
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/software-rev.rev or empty string if not found.
unitFamily
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/aliasalias or empty string if not found.
unitType
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/classclass or empty string if not found.
vendorName
Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/mfg-namename or empty string if not found.