Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


ID

Test Case Name

Status

D1

CPE PNF Re-registration

Status
colourYellow
title

PARTIALLY TESTED

PENDING

D2

HSIA Service Reconfiguration

NOT YET TESTED

Status
colourYellow
titlePENDING

D3CPE Authentication (after relocation)
NOT YET TESTED

Status
colourYellow
titlePENDING

D4HSIA Service Activation and Service Status Change Notification (after relocation)
NOT YET TESTED

Status
colourYellow
titlePENDING

D5CPE power cycle vs CPE re-registration

Status
colourBlue
titleNOT

YET

TESTED

CPE PNF Re-registration
Anchor
D1
D1

Test Case IDD1
Test Case Name

CPE PNF Re-registration

DescriptionCPE PNF changes location and re-attaches the network in a different OLT. ONAP detects re-location and re-registers the CPE PNF.
ReleaseDublin Casablanca MRFrankfurt (6.0.0)
Preconditions

- BBS E2E service instance and CPE PNF resource object have been created in AAI by SO
- BBS E2E service instance orchestration-status is "active"
- Access SDN M&C IP is configured in SDNC DG in ONAP
-- GENERIC-RESOURCE-API: bbs-access-connectivity-network-topology-operation-create-huawei.json
-- GENERIC-RESOURCE-API: bbs-access-connectivity-network-topology-operation-delete-huawei.json
- There is connectivity between Access SDN M&C and RESTCONF collector

Testing Steps
  1. Unplug CPE PNF
  2. Plug CPE PNF in different location (at least different OLT port)
Expected Results
  1. Access SDN M&C notifies RESTCONF collector with a PNF registration event
  2. VES mapper maps RESTCONF event to VES message and publish the message in DMaaP's unauthenticated.VES_PNFREG_OUTPUT
  3. PRH consumes PNF registration VES event
  4. PRH updates CPE PNF resource object in AAI with new values
  5. PRH detects that CPE PNF belongs to service instance in orchestration-status=active and publishes a PNF_UPDATE event in DMaaP's unauthenticated.PNF_UPDATE topic
  6. BBS uS consumes PNF_UPDATE event
  7. BBS uS compares attachment-point with the one stored in AAI. If different, publishes event in DMaaP's unauthenticated.DCAE_CL_OUTPUT, policyName="Nomadic_ONT"
  8. BBS policy continues with service reconfiguration
Actual Results


Code Block
languagebash
themeMidnight
titleunauthenticated.VES_PNFREG_OPUTPUT
linenumberstrue
collapsetrue
[
    "{\"event\":{\"commonEventHeader\":{\"startEpochMicrosec\":1555076831049,\"eventId\":\"registration_1555076831049\",\"internalHeaderFields\":{\"collectorTimeStamp\":\"Fri, 04 12 2019 04:04:27 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-2\",\"cvlan\":\"11\",\"svlan\":\"101\"},\"pnfRegistrationFieldsVersion\":\"2.0\",\"manufactureDate\":\"\",\"modelNumber\":\"\",\"lastServiceDate\":\"\",\"unitFamily\":\"\",\"vendorName\":\"Huawei\",\"oamV4IpAddress\":\"\",\"oamV6IpAddress\":\"\",\"softwareVersion\":\"v2\"}}}"
]


Code Block
languagebash
themeMidnight
titleunauthenticated.PNF_UPDATE
linenumberstrue
collapsetrue
[
    "{\"additionalFields\":{\"remote-id\":\"AC9.0234.0338\",\"attachment-point\":\"167772165-5-2\",\"cvlan\":\"11\",\"svlan\":\"101\"},\"correlationId\":\"Huawei-HWTCC01B7503\"}"
]


Code Block
languagebash
themeMidnight
titleBBSep uS log
linenumberstrue
collapsetrue
2019-04-12 16:13:23.194 TRACE 1 --- [ctor-http-nio-8] .u.ReRegistrationDmaapConsumerJsonParser : Event from DMaaP to be parsed:
{"additionalFields":{"remote-id":"AC9.0234.0338","attachment-point":"167772165-5-2","cvlan":"11","svlan":"101"},"correlationId":"Huawei-HWTCC01B7503"}
2019-04-12 16:13:23.195 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.p.ReRegistrationPipeline       : Processing Step: Retrieve PNF. Url: (/aai/v14/network/pnfs/pnf/Huawei-HWTCC01B7503?depth=all)
2019-04-12 16:13:23.195  INFO 1 --- [ctor-http-nio-8] o.o.b.e.p.tasks.AaiClientTaskImpl        : Executing task (PNF Retrieval) for retrieving PNF object
2019-04-12 16:13:23.195 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Will issue Reactive GET request to URL (/aai/v14/network/pnfs/pnf/Huawei-HWTCC01B7503?depth=all) for object (org.onap.bbs.event.processor.model.PnfAaiObject)
2019-04-12 16:13:23.197 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Request: GET https://aai.onap:8443/aai/v14/network/pnfs/pnf/Huawei-HWTCC01B7503?depth=all
2019-04-12 16:13:23.197 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : X-FromAppId=bbs
2019-04-12 16:13:23.198 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Accept=application/json
2019-04-12 16:13:23.198 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Authorization=Basic QUFJOkFBSQ==
2019-04-12 16:13:23.198 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Content-Type=application/json
2019-04-12 16:13:23.198 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Real-Time=true
2019-04-12 16:13:23.198 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : X-TransactionId=9999
2019-04-12 16:13:23.309 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Response status 200 OK
2019-04-12 16:13:23.311 DEBUG 1 --- [ctor-http-nio-8] o.o.b.e.p.utilities.AaiReactiveClient    : Response body
{"pnf-name":"Huawei-HWTCC01B7503","pnf-id":"4fca7530-062e-4f8a-9404-496832555c29","equip-type":"","equip-vendor":"Huawei","equip-model":"","sw-version":"v2","in-maint":false,"serial-number":"HWTCC01B7503","resource-version":"1555083285880","nf-role":"","relationship-list":{"relationship":[{"related-to":"service-instance","relationship-label":"org.onap.relationships.inventory.ComposedOf","related-link":"/aai/v14/business/customers/customer/BBSCustomer/service-subscriptions/service-subscription/BBS_E2E_Service/service-instances/service-instance/03b92492-c5c0-487a-b414-d5427ab6f041","relationship-data":[{"relationship-key":"customer.global-customer-id","relationship-value":"BBSCustomer"},{"relationship-key":"service-subscription.service-type","relationship-value":"BBS_E2E_Service"},{"relationship-key":"service-instance.service-instance-id","relationship-value":"03b92492-c5c0-487a-b414-d5427ab6f041"}],"related-to-property":[{"property-key":"service-instance.service-instance-name","property-value":"BBS_E2E_Service"}]}]}}
2019-04-12 16:13:23.312  WARN 1 --- [ctor-http-nio-8] o.o.b.e.p.p.ReRegistrationPipeline       : PNF Huawei-HWTCC01B7503 does not have any logical-links bridged. Stop further processing


Conclusion (Pass/Fail)
Status
colourYellow
titlePARTIALLY TESTED
- Casablanca MR instead of Dublin
- Pair-wise testing RESTCONF Collector (mocked CPE registration message)--> VES mapper --> PRH --> BBSep uS
- Need to create logical-link (attachment point in AAI) before running test for BBSep to complete processing


Testing LabSwisscom LabTesting Date2019.04.12
Tester Name


HSIA Service Reconfiguration
Anchor
D2
D2

Test Case IDD2
Test Case NameHSIA Service Reconfiguration


Description
ReleaseDublinFrankfurt (6.0.0)
Preconditions


Testing Steps


Expected Results


Actual Results


Conclusion (Pass/Fail)

NOT YET TESTED


Testing LabSwisscom Lab
Testing Date
Tester Name

CPE Authentication (after relocation)
Anchor
D3
D3

NOT YET TESTED
Test Case IDD3
Test Case NameCPE Authentication (after relocation)


Description
ReleaseDublinFrankfurt (6.0.0)
Preconditions


Testing Steps


Expected Results


Actual Results


Conclusion (Pass/Fail)


Testing LabSwisscom Lab
Testing Date
Tester Name

HSIA Service Activation and Service Status Change Notification (after relocation)
Anchor
D4
D4

Test Case IDD4
Test Case Name

HSIA Service Activation and Service Status Change Notification (after relocation)

Description
ReleaseDublinFrankfurt (6.0.0)
Preconditions


Testing Steps


Expected Results


Actual Results


Conclusion (Pass/Fail)

NOT YET TESTED


Testing LabSwisscom Lab
Testing Date
Tester Name

CPE  power cycle vs CPE re-registration
Anchor
D5
D5

Test Case IDD5
Test Case Name

CPE power cycle vs CPE re-registration

DescriptionThe customer powers off the CPE and, after some time, powers it on. The CPE registration message (if any) coming from the Access SDN M&C must not be treated as a PNF re-registration in ONAP
ReleaseDublinFrankfurt (6.0.0)
Preconditions


Testing Steps


Expected Results


Actual Results


Conclusion (Pass/Fail)

Status
colourBlue
titleNOT
YET
TESTED

Testing LabSwisscom Lab
Testing Date
Tester Name