1. All PNFs (PE, DC gateway) resources have been defined in SDC
2. All required network connection types (VLAN, BGP MPLS L3VPN, VXLAN, etc) are defined in SDCWAN underlay network template (.yaml) has been defined and packaged in a CSAR file
3. WAN overlay network template (.yaml) has been defined and packaged in a CSAR file

1. In SDC create a new WAN service
2. In service composition, pull in 2 PE routers, namely PE1 and PE2
3. In service composition, pull in 2 data center gateways, namely DC GW1 and DC GW2
4. Create underlay network as following:
   1. DC GW1 → PE1 as vlan
   2. DC GW2 → PE2 as vlan
   3. PE1 → PE2 as BGP MPLS L3VPN
5. Create overlay network DC GW1 → DC GW2 as VXLAN

1. Underlay WAN network created successfully
2. Overlay WAN network created successfullyVL resource and upload WAN underlay network CSAR file. Make sure controllerInfo property is set to SDNC in the template
3. In SDC create a VL resource and upload WAN overlay network CSAR file. Make sure controllerInfo property is set to SDNC

1. WAN underlay network resource onboarded successfully and shown in catalog
2. WAN overlay network resource onboarded successfully and shown in catalog

This test uses CLAMP to configure closed loop for VoLTE. There are 4 configurations:

1. Provisional rules for Policy
2. Correlation rules for Holmes
3. Holmes microservice Blueprint for DCAE
4. VES configuration ?(in R1, there is no configuration needed)

1. DCAE template has been imported (R1 SDC doesn't support DCAE template design)
2. Holmes blueprint has been imported
3. Holmes correlation rules have been defined

1. In CLAMP, choose VNF SPGW and events (VNF Fault and VM Fault) to monitor
2. Bring up CLAMP configuration policy GUI and copy Holmes correlation rules in it
3. Bring up CLAMP provisional policy GUI and define healing provisional policy
4. Save the configuration

1. Closed loop template and blueprint for Holmes are distributed to DCAE
2. Configuration policy has been distributed to DCAE
3. Provisional policy has been distributed to Policy engine

1. VoLTE service has been instantiated
2. Closed loop for VoLTE has been configured and started

1. ONAP user uses Usecase UI GUI to check system performance, such as CPU, memory and disk usage
2. ONAP user views the VNF alarms collected by ONAP

1. System performance (including system CPU, memory and disk usage) is shown on ONAP Usecase UI GUI
2. VNF alarms, specified in CLAMP for the closed loop, are shown in Usecase UI GUI

1. VoLTE service has been instantiated
2. VoLTE closed loop has been configured and started
3. SPGW VNF supports event generation
4. VNF guest OS supports event generation
5. MultiVIM supports event collection from guest OS and event forwarding

1. Use Robot test script to Manually shutdown standby MPU VM inside SPGW VNF. This should trigger the VNF and VIM to generate alarms

1. EMS collects standby MPU offline event from SPGW VNF and sends the event to VFC
2. MultiVIM doesn't receive heartbeat event from standby MPU guest OS for a period of time and triggers alarm which is sent to DCAE VES collector
3. Holmes receives MPU offline events
4. Holmes receives MPU guest OS heartbeat missing events
5. Holmes does correlation of the two types of events and generate one signature event and sends it to Policy
6. Policy triggers provisional policy and healing action is sent to VFC
7. VFC uses SVNFM driver to heal standby MPU VM
8. Standby MPU is healed
9. Clear event is sent from SPGW VNF about standby MPU back online
10. Heartbeat from standby MPU VM is received by MultiVIM and clear event is sent by MultiVIM about heartbeat recovery
11. Holmes does the event correlation and sends Clear signature event to Policy
12. Policy stops the healing action