Versions Compared

Old Version 1

changes.mady.by.user Martin Skorupski

Saved on

compared with

New Version 2

changes.mady.by.user Martin Skorupski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Martin Skorupski TO BE DONE 

In order to convert a NetConf notification into a VES7.1.1 format a mapping between a specific YANG set of YANG modules and the VES:commonEventHeader and its domain "notification. In the example below we need the BBF-TR069 implemented in the OAM-TR069-Adapter for such mapping.


VES:commonEventHeader

implementation of TR069 yang

domain

Static text "notification"

eventId

Concatenation of:

  • "ConfigurationChange-"
  • Value of: notification VALUECHANGE/device/device-info/serial-number
  • "-"
  • value of an increasing sequence number (uint64; even so, please implement wrap around)

eventName

Static text: "ConfigurationChange"

eventType

Static text: "OAM-TR069_RAN_notification"

internalHeaderFields

not mapped

lastEpochMicrosec

TimeStamp of the NetConf notification header in unix time format - as microseconds elapsed since 1 Jan 1970 not including leap seconds.

nfcNamingCode

not mapped

nfNamingCode

not mapped

nfVendorName

Value of: notification VALUECHANGE/device/device-info/manufacturer

priority

Static text "Normal"

reportingEntityId

not mapped

reportingEntityName

TODO add definition of SDN-R node id here (fqdn?)

sequence

An per NetConf notification increasing sequence number as unsigned integer 64 bits. The value is reused in the eventId field.

sourceId

Value of: notification VALUECHANGE/device/device-info/serial-number

sourceName

Value of: notification VALUECHANGE/device/device-info/x-0005b9-operator-name


startEpochMicrosec

not mapped

timeZoneOffset

Static text: "+00:00" - Please note that times from NetConf Notification Header may need to be converted to UTC.

version

Static text: "7.1.1"

vesEventListenerVersion

Static text "7.1.1"