D-Release Integration - O-DU on-boarding

Table of Contents

Sub pages

Scope

This wiki describes OAM specific test cases according to 3. O-DU Startup.

OAM-192 - Getting issue details... STATUS

Test cases

Message flow numberTest casePassedComment
5, 6, 7, 8, 10O-DU/https/IPv4/VES:pnfRegistration to message router 
Checked with RestClient on Message Router
5, 6, 7, 8, 10O-DU/https/IPv6/VES:pnfRegistration to message router 
Checked with RestClient on Message Router
9, 11, 12, 13, 14Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/SSH/IPv4
Visible on ODLUX (connected)
9, 11, 12, 13, 14Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/TLS/IPv4
Visible on ODLUX (connected)
9, 11, 12, 13, 14Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/SSH/IPv6
Visible on ODLUX (connected)
9, 11, 12, 13, 14Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/TLS/IPv6
Visible on ODLUX (connected)
25
n/a

automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding

Technical problematic, because OTF needs to know credential and network details to subscribe for OAM controller.

26NETCONF operation <create-subscription/> SSH/IPv4
automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding
26NETCONF operation <create-subscription/> TLS/IPv4
automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding
26NETCONF operation <create-subscription/> SSH/IPv6
automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding
26NETCONF operation <create-subscription/> TLS/IPv
automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding