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 7
Next »
Recovery after HSIA Service Instantiation Timeout
Test Case ID | C1 |
---|
Test Case Name | Recovery after HSIA Service Instantiation Timeout |
---|
Description | During service instantiation, SO waits for CPE PNF to be registered. There is a 14-day timeout. After timeout service instantiation is rolled back. |
---|
Release | Dublin |
---|
Preconditions |
|
---|
Testing Steps |
|
---|
Expected Results |
|
---|
Actual Results | |
---|
Conclusion (Pass/Fail) | |
---|
Testing Lab | Swisscom Lab |
---|
Testing Date |
|
---|
Tester Name |
|
---|
CPE Registration
Test Case ID | C2 |
---|
Test Case Name | CPE Registration
|
---|
Description | CPE PnP |
---|
Release | Dublin Casablanca MR |
---|
Preconditions | - BBS E2E service instance and CPE PNF resource object have been created in AAI by SO - BBS E2E service instance orchestration-status is "assigned" - SO is waiting for PNF_READY event in order to continue with the BBS E2E service orchestration - Access SDN M&C is registered in ONAP as 3rd party controller and there is connectivity with RESTCONF collector |
---|
Testing Steps | - Attach CPE PNF to OLT
|
---|
Expected Results | - Access SDN M&C notifies RESTCONF collector with a PNF registration event
- VES mapper maps RESTCONF event to VES message and publish the message in DMaaP's unauthenticated.VES_PNFREG_OUTPUT
- PRH consumes PNF registration VES event
- PRH updates CPE PNF resource object in AAI with new values
- PRH publishes PNF_READY event in DMaaP's unauthenticated.PNF_READY topic
- SO consumes PNF_READY event and proceeds with service orchestration
|
---|
Actual Results |
[
"{\"event\":{\"commonEventHeader\":{\"startEpochMicrosec\":1555076831049,\"eventId\":\"registration_1555076831049\",\"internalHeaderFields\":{\"collectorTimeStamp\":\"Fri, 04 12 2019 03:34:44 UTC\"},\"eventType\":\"pnfRegistration\",\"priority\":\"Normal\",\"version\":\"4.0.1\",\"reportingEntityName\":\"VESMapper\",\"sequence\":0,\"domain\":\"pnfRegistration\",\"lastEpochMicrosec\":1555076831049,\"eventName\":\"pnfRegistration\",\"vesEventListenerVersion\":\"7.0.1\",\"sourceName\":\"Huawei-HWTCC01B7503\"},\"pnfRegistrationFields\":{\"unitType\":\"\",\"serialNumber\":\"HWTCC01B7503\",\"additionalFields\":{\"remote-id\":\"AC9.0234.0338\",\"attachment-point\":\"167772165-5-1\",\"cvlan\":\"11\",\"svlan\":\"101\"},\"pnfRegistrationFieldsVersion\":\"2.0\",\"manufactureDate\":\"\",\"modelNumber\":\"\",\"lastServiceDate\":\"\",\"unitFamily\":\"\",\"vendorName\":\"Huawei\",\"oamV4IpAddress\":\"\",\"oamV6IpAddress\":\"\",\"softwareVersion\":\"v2\"}}}"
]
[
"{\"additionalFields\":{\"remote-id\":\"AC9.0234.0338\",\"attachment-point\":\"167772165-5-1\",\"cvlan\":\"11\",\"svlan\":\"101\"},\"correlationId\":\"Huawei-HWTCC01B7503\"}"
]
|
---|
Conclusion (Pass/Fail) | |
---|
Testing Lab | Swisscom Lab |
---|
Testing Date | 2019.04.12 |
---|
Tester Name | |
---|
CPE Authentication
Test Case ID | C3 |
---|
Test Case Name | CPE Authentication
|
---|
Description |
|
---|
Release | Dublin |
---|
Preconditions |
|
---|
Testing Steps |
|
---|
Expected Results |
|
---|
Actual Results | |
---|
Conclusion (Pass/Fail) | |
---|
Testing Lab | Swisscom Lab |
---|
Testing Date |
|
---|
Tester Name |
|
---|
HSIA Service Activation and Service Status Change Notification
Test Case ID | C4 |
---|
Test Case Name | HSIA Service Activation and Service Status Change Notification |
---|
Description |
|
---|
Release | Dublin |
---|
Preconditions |
|
---|
Testing Steps |
|
---|
Expected Results |
|
---|
Actual Results | |
---|
Conclusion (Pass/Fail) | |
---|
Testing Lab | Swisscom Lab |
---|
Testing Date |
|
---|
Tester Name |
|
---|