The latest O-RAN Alliance WG4 OpenFronthaul Management Plane (OFHM) Spec (v11) (https://orandownloadsweb.azurewebsites.net/specifications) - see O-RAN.WG4.MP.0-R003-v11.00 - defines VES as option.

Idea: the existing mapping of the O-RU device manager should be aligned with the specification.
flow: [O-RU] -NETCONF-Notification -> [SDN-R] -> VES -> [VES-Collector]

The VES massage are of ves-domain 'stndDefined' in the ves-body the ietf-restconf-header is added augmented by the OFHM specific and yang-defined notification syntax.

The proper configuration of the VES collector can be found in O-RAN-SC OAM:

• https://gerrit.o-ran-sc.org/r/gitweb?p=oam.git;a=tree;f=solution/smo/oam/ves-collector

Related O-RAN-SC OAM Jira:

• https://jira.o-ran-sc.org/browse/OAM-327

In addition to the already existing NETCONF to VES translation by the O-RU deviceManger - the translation of the 'o-ran-supervision:supervision-notification' notification would be of interest for use SDN-R as "O-RU-Controller".

The full set of OFHM NETCONF-Notification can be found here: https://wiki.o-ran-sc.org/download/attachments/75104359/ofhm-v11-ves.xlsx?api=v2