1. All VNF vendor's EMS have been installed and configured

1. Register all vendors' EMSs using ONAP ESR GUI with the needed information (IP, port, authentication information, etc)

1. All EMSs are registered successfully with ONAP
2. All EMSs information is stored correctly in ONAP

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?

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 created, V00011 has passed
2. Closed loop has been configured, V00012 has passed
3. PEs have been configured and integrated with corresponding SDN WAN controller
4. DC GWs have been configured and integrated with corresponding SDN local controller

1. ONAP user uses Usecase UI GUI to start VoLTE service instantiation
2. Usecase UI will guide the user to deploy each of vEPC VNFs. User needs to choose data center location for each VNF and fill in input parameters defined in TOSCA template
3. Usecase UI will guide the user to deploy each of vIMS VNFs. User needs to choose data center location for each VNF and fill in input parameters defined in TOSCA template
4. Usecase UI will guide the user to deploy WAN service. User needs to input necessary PEs and DC GWs info, fill in WAN underlay and overlay parameters

1. vEPC service is instantiated successfully, including all vEPC VNFs and VLs
2. vIMS service is instantiated successfully, including all vIMS VNFs and VLs
3. WAN service is instantiated successfully, including underlay and overlay networks
4. Holmes analytics container is brought up correctly by DCAE

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 shutdown standby MPU VM inside SPGW VNF

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