You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

status: to be specified 2021-02-10 - not ready

Objective

In order to process O-RU NetConf alarm-notif events in a common way on SMO level, the OAM controller converts such NetConf Notification into a VES:fault message..


Sequence Diagram

OpenFronthaul Alarm to to VES-fault SMO O-RU Message-Router Message-Router VES-Collector VES-Collector OAM-Controller OAM-Controller NetConf-Server-OFH NetConf-Server-OFH init [01]NETCONF Callhome SSH [02]NETCONF <hello/>Exchange capabilitiesincluding YANG modules for OpenFronthauland <create-subscription/> RPC [03]NETCONF Notification Subscription [04]GET ietf-hardware [05]RESPONSE ietf-hardware use case [06]NETCONF Notificationo-ran-fm:alarm-notify(fault-id: 30 (Interface Fault) ) [07]map o-ran-fm:alarm-notifyinto VES:fault (see below) [08]VES:domain=fault [09]publish eventThanks to PlantUml!License: Apache 2.02021-02-10 | o-ran-sc.org


Implementation

It is assumed that the existing generic NetConf-Notification to ves:notification service could be enhanced for a specific fault notification implementation. 

Mapping to VES fault fields

The following mapping table bases on the capabilities of OpenDaylight version Aluminum and maps them to the VES 7.2 fields for domain 'fault'.



(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 "fault"

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: "O-RAN-RU-Fault"

internalHeaderFields

not mapped

lastEpochMicrosec

TimeStamp represented by <eventTime> field in NetConf notification header in unix time format - as microseconds elapsed since 1 Jan 1970 not including leap seconds.

nfcNamingCode

always ""

nfNamingCode

always ""

nfVendorName

The value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/mfg-name or empty string if not found. 

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

Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/uuid or 'nt:network-topology/nt:topology/nt:node/nt:node-id' if ietf component not found.

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.2"

VES:fault

dont read below this line (wink)


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-change  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 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  or empty string if not found. 

softwareVersion

Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/software-rev or empty string if not found. 

unitFamily

Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/alias or empty string if not found. 

unitType

Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/class or empty string if not found. 

vendorName

Value of ietf-hardware (RFC8348) /hardware/component[not(parent)][1]/mfg-name or empty string if not found. 

  • No labels