HT03 - End-to-End Fault Correlation: Difference between revisions

From NFVwiki
(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...")
 
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Description =
= Description =
Understanding of multi-level fault correlation techniques for NFV fault identification, localization, and root cause analysis.   
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.


[https://docbox.etsi.org/ISG/NFV/REL/05-CONTRIBUTIONS/2015//NFVREL(15)000083r2_REL_Hot_Topic.zip HT#3 (REL) End-to-End Fault Correlation]
[https://docbox.etsi.org/ISG/NFV/REL/05-CONTRIBUTIONS/2015//NFVREL(15)000083r2_REL_Hot_Topic.zip HT#3 (REL) End-to-End Fault Correlation]
Line 11: Line 10:


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


==Criterion of success==
==Criterion of success==
Line 22: Line 20:


= Technical information to be provided by the PoC Team=
= Technical information to be provided by the PoC Team=
What faults and challenges on the various levels have been addressed by the PoC?
* What faults and challenges on the various levels have been addressed by the PoC?
Does the solution require active, passive or hybrid monitoring?
* 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?  
* What extensions are required for the existing NFV components to propagate fault notifications and alarms for effective fault correlation?  


PoC Teams shall follow the [[Media:HT_3_FB_Template.doc | HT#3-Feedback Template]] on their contributions to Hot Topic#3
PoC Teams shall follow the [[Media:HT_3_FB_Template.doc | HT#3-Feedback Template]] on their contributions to Hot Topic#3


=Concerned WGs/WI=  
=Concerned WGs/WI=  
[http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46041 REL004 - Report on Active Monitoring and Failure Detection] - [Latest draft]
[http://webapp.etsi.org/WorkProgram/Report_WorkItem.asp?WKI_ID=46041 REL004 - Report on Active Monitoring and Failure Detection] - [http://docbox.etsi.org/ISG/NFV/Open/Drafts/REL004_Active_monitoring_and_failure_detection/ Latest draft]
 
[https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=49496 REL008 - Report on Error Handling – Detection, Correlation, Notification] - [http://docbox.etsi.org/ISG/NFV/Open/Drafts Latest draft]


=Coordinator=
=Coordinator=Stegan Arntzen (Huawei) [mailto:Stefan.Arntzen@huawei.com Stefan.Arntzen@huawei.com]
REL004 Rapporteur: Gurpreet Singh (Spirent) [mailto:Gurpreet.Singh@spirent.com Gurpreet.Singh@spirent.com]


=Contributions (feedback) deadline=
=Contributions (feedback) deadline=
Q2 2016
Q4 2016

Latest revision as of 14:05, 23 February 2016

Description

Understanding of multi-level fault correlation techniques for NFV fault identification, localization, and root cause analysis.

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

REL008 - Report on Error Handling – Detection, Correlation, Notification - Latest draft

=Coordinator=Stegan Arntzen (Huawei) Stefan.Arntzen@huawei.com

Contributions (feedback) deadline

Q4 2016