...
# | Component(s) | Test Case | Status | Remarks | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IT#017 | SDN-R | Upon receiving message from Policy, SDN-R sends netconf message to RAN-Sim. |
| Will be completed when CCSDK-1399 and CCSDK-1400 are delivered.
The DMaaP listener docker with the code fix is not yet deployed in SB-00 where the testing is done. The code, fix however, is already merged on to Dublin and Master branches. So, once the latest docker is deployed, we will continue and complete the test case at Windriver.
| ||||||||||||||||||||||||||
| IT#019 | SDNR (DMAAP Listener) | SDNR is able to receive DMAAP message from Policy |
| |||||||||||||||||||||||||||
IT#020 | SDNR | SDNR is able to receive a DMAAP message to configure PCI value (Action: ModifyConfig) and invoke RPC: configure-phy-cell-id |
| |||||||||||||||||||||||||||
IT#021 | SDNR | SDNR is able to receive a DMAAP message to configure PCI value and/or blacklisted flag of neigbor cell/s (Action: ModifyConfigANR) and invoke RPC: generic-neighbor-configuration |
| |||||||||||||||||||||||||||
IT#022 | SDNR & RAN simulator | RPC execution (configure-phy-cell-id): Verify if Restconf transactions against the Netconf mounted RAN simulator succeed in configuring PCI value of a cell |
| This can be verified by reviewing either SDNR/DG logs (/opt/opendaylight/current/data/log/configuration-phy-cell-id.log) or executing GET Restconf transaction from the SDNR Restconf API explorer | ||||||||||||||||||||||||||
IT#023 | SDNR & RAN simulator | RPC execution (generic-neighbor-configuration): Verify if Restconf transactions against the Netconf mounted RAN simulator succeed in configuring PCI value and/or blacklisted flag of neighbor cell/s |
| This can be verified by reviewing either SDNR/DG logs (/opt/opendaylight/current/data/log/generic-neighbor-config.log) or executing GET Restconf transaction from the SDNR Restconf API explorer | ||||||||||||||||||||||||||
IT#024 | SDNR & RAN simulator | RAN simulator generates Netconf notification to indicate neighbor list change notification |
| Prerequisite: RAN simulator is configured and Netconf mounted onto SDNR | ||||||||||||||||||||||||||
IT#025 | SDNR & RAN simulator | SDNR after receiving Netconf notification invokes RPC handle-nbrlist-change-notif |
| Prerequisite: RAN simulator is configured and Netconf mounted onto SDNR | ||||||||||||||||||||||||||
IT#026 | SDNR & ConfigDB | RPC execution (handle-nbrlist-change-notif): Update configDB by adding new neighbors per NETRCONF notification |
| Verify ConfigDB is updated by executing GET transaction from Postman Verify neighbor additions are aligned with neighbor list change Netconf notification | ||||||||||||||||||||||||||
IT#027 | SDNR/DMAAP message | RPC execution (handle-nbrlist-change-notif): DMAAP message ( PCI-NOTIF-TOPIC-NGHBR-LIST-CHANGE-INFO) is published from SDNR to be consumed by SON MS |
| Verify DMAAP message is published onto message router Verify payload of the DMAAP message aligns with the original neighbor list change Netconf notification | ||||||||||||||||||||||||||
| IT#028 | SDNR & ConfigDB | RPC execution (configure-phy-cell-id): Verify if ConfigDB is updated after respective RAN simulator nodes are configured using Restconf/Netconf |
| This can be verified by reviewing either SDNR/DG logs (/opt/opendaylight/current/data/log/configuration-phy-cell-id.log) or executing GET API against ConfigDB | ||||||||||||||||||||||||||
| IT#029 | SDNR & DMAAP Publication | RPC execution (configure-phy-cell-id): Verify if DMAAP message confirming success or failure is published to be consumed by Policy as confirmation of its requested action |
| DMAAP message is published to Topic SDNR-CL-RSP. Verify the DMAAP message payload is as expected per requirement 1.5: PCI Changes response from SDNR to Policy | ||||||||||||||||||||||||||
| IT#030 | SDNR & ConfigDB | RPC execution (generic-neighbor-configuration): Verify if ConfigDB is updated after respective RAN simulator nodes are configured using Restconf/Netconf |
| This can be verified by reviewing either SDNR/DG logs (/opt/opendaylight/current/data/log/generic-neighbor-config.log) or executing GET API against ConfigDB | ||||||||||||||||||||||||||
| IT#031 | SDNR & DMAAP Publication | RPC execution (generic-neighbor-configuration): Verify if DMAAP message confirming success or failure is published to be consumed by Policy as confirmation of its requested action |
| DMAAP message is published to Topic SDNR-CL-RSP. Verify the DMAAP message payload is as expected per requirement 2.5: ANR Changes response from SDNR to Policy | ||||||||||||||||||||||||||
...