Test cases
| Message flow number | Test case | Passed | Comment |
|---|---|---|---|
| 5, 6, 7, 8, 10 | O-DU/https/IPv4/VES:pnfRegistration to message router | Checked with RestClient on Message Router | |
| 5, 6, 7, 8, 10 | O-DU/https/IPv6/VES:pnfRegistration to message router | Checked with RestClient on Message Router | |
| 9, 11, 12, 13, 14 | Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/SSH/IPv4 | Visible on ODLUX (connected) | |
| 9, 11, 12, 13, 14 | Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/TLS/IPv4 | Visible on ODLUX (connected) | |
| 9, 11, 12, 13, 14 | Create mountpoint based on VES:pnfRegistration and get connected - NETCONF/SSH/IPv6 | Visible on ODLUX (connected) | |
| 9, 11, 12, 13, 14 | Create 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. | |
| 26 | NETCONF operation <create-subscription/> SSH/IPv4 | automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding | |
| 26 | NETCONF operation <create-subscription/> TLS/IPv4 | automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding | |
| 26 | NETCONF operation <create-subscription/> SSH/IPv6 | automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding | |
| 26 | NETCONF operation <create-subscription/> TLS/IPv | automatically done by O-RU NF-Manager (device-manager) in context of O-RU on-boarding |