HT03 - End-to-End Fault Correlation

From NFVwiki
Revision as of 13:27, 11 August 2015 by Almagia (talk | contribs) (Created page with "= Description = Understanding of multi-level fault correlation techniques for NFV fault identification, localization, and root cause analysis. These goals may be met in a P...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

Understanding of multi-level fault correlation techniques for NFV fault identification, localization, and root cause analysis. These goals may be met in a PoC whose focus is testing, or as additional goals for a PoC primarily addressing another topic.

HT#3 (REL) End-to-End Fault Correlation

Status

ACTIVE

What is expected to be learnt from the NFV PoCs

Points to prove/refute

• What architectural choices for fault correlation exist and what are their benefits? • Where (in which components) to place local correlation entities? • What are the main limitations? • What has been made in the PoC(s) to overcome those limitations? • Updates to suggest to NFV architectural framework if any?


Criterion of success

• Fault localization and identification of various challenges on the different layers of the NFV reference architecture within a pre-defined time limits

Technical information to be provided by the PoC Team

• What faults and challenges on the various levels have been addressed by the PoC? • Does the solution require active, passive or hybrid monitoring? • What extensions are required for the existing NFV components to propagate fault notifications and alarms for effective fault correlation?

PoC Teams shall follow the HT#3-Feedback Template on their contributions to Hot Topic#3

Concerned WGs/WI

REL004 - Report on Active Monitoring and Failure Detection - [Latest draft]

Coordinator

REL004 Rapporteur: Gurpreet Singh (Spirent) Gurpreet.Singh@spirent.com

Contributions (feedback) deadline

Q2 2016