Versions Compared

Old Version 20

changes.mady.by.user Yang Xu

Saved on

compared with

New Version 21

changes.mady.by.user Yang Xu

Saved on

Key

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

...

Test Case IdV00012
Test Case NameClosed loop configuration
DescriptionThis test uses CLAMP to configure closed loop for VoLTE
ReleaseAmsterdam
Preconditions
  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
Testing Steps
  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 reboot healing provisional policy
  4. Save the configuration
Expected Results
  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
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name

...

Test Case IdV00014
Test Case NameVoLTE Auto-healing
DescriptionThis test covers the closed loop with alarm correlation and auto-healing
ReleaseAmsterdam
Preconditions
  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
Testing Steps
  1. Use Robot test script to shutdown standby MPU VM inside SPGW VNF
Expected Results
  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 reboot healing action is sent to VFC
  7. VFC uses SVNFM driver to reboot heal standby MPU VM
  8. Standby MPU is reboothealed
  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 reboot healing action
Actual Results
Conclusion (Pass/Fail)
Testing LabCMCC OpenLab
Testing Date
Tester Name

...