Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 5 Next »

Table of Contents

Sub pages

Scope

This wiki describes OAM specific test cases according to 4. O-RU closed loop recovery.

OAM-194 - Getting issue details... STATUS

Test cases

Message flow numberTest casePassedComment
1, 2, 6, 7NETCONF/SSH/IPv4/yang/hello-world.yang/administrative-state=locked 
Triggered with ONAP SDN-R ODLUX ConfigApp
1, 2, 6, 7NETCONF/TLS/IPv4/yang/hello-world.yang/administrative-state=locked 
Triggered with ONAP SDN-R ODLUX ConfigApp
1, 2, 6, 7NETCONF/SSH/IPv6/yang/hello-world.yang/administrative-state=locked 
Triggered with ONAP SDN-R ODLUX ConfigApp
1, 2, 6, 7NETCONF/TLS/IPv6/yang/hello-world.yang/administrative-state=locked 
Triggered with ONAP SDN-R ODLUX ConfigApp
8, 9, 10, 11NETCONF/SSH/IPv4 notification/alarm-notify/fault-id=30
is-clear: false, severity: CRITICAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
8, 9, 10, 11NETCONF/TLS/IPv4 notification/alarm-notify/fault-id=30
is-clear: false, severity: CRITICAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
8, 9, 10, 11NETCONF/SSH/IPv6 notification/alarm-notify/fault-id=30
is-clear: false, severity: CRITICAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
8, 9, 10, 11NETCONF/TLS/IPv6 notification/alarm-notify/fault-id=30
is-clear: false, severity: CRITICAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
13same as 11

14, 15, 16, 17NETCONF/SSH/IPv4/yang/hello-world.yang/administrative-state=unlocked 
Triggered with ONAP SDN-R ODLUX ConfigApp
14, 15, 16, 17NETCONF/TLS/IPv4/yang/hello-world.yang/administrative-state=unlocked 
Triggered with ONAP SDN-R ODLUX ConfigApp
14, 15, 16, 17NETCONF/SSH/IPv6/yang/hello-world.yang/administrative-state=unlocked 
Triggered with ONAP SDN-R ODLUX ConfigApp
14, 15, 16, 17NETCONF/TLS/IPv6/yang/hello-world.yang/administrative-state=unlocked 
Triggered with ONAP SDN-R ODLUX ConfigApp
18, 19, 20, 21NETCONF/SSH/IPv4 notification/alarm-notify/fault-id=30
is-clear: true, severity: NORMAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
18, 19, 20, 21NETCONF/TLS/IPv4 notification/alarm-notify/fault-id=30
is-clear: true, severity: NORMAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
18, 19, 20, 21NETCONF/SSH/IPv6 notification/alarm-notify/fault-id=30
is-clear: true, severity: NORMAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
18, 19, 20, 21NETCONF/TLS/IPv6 notification/alarm-notify/fault-id=30
is-clear: true, severity: NORMAL
NTS-NG-O-RU sim configured to automatically send alarm. Event read from Message router by OAM-Controller and visualized in ONAP SDN-R ODLUX FaultApp
23same as 21

24done as part of 18, 19, 20, 21

  • No labels