1. Author: Rodrigo Fonseca, George Porter, Randy H. Katz, Scott Shenker, Ion Stoica Presenter :Yinzhi Cao

2. Outline  Background  Origin  X-Trace Vector Flowing Vector God OverHead  Usage Scenarios  Potential Problems

3. Background(1)  Network Diagnosis  Scenarios One (Accessing Website)

4. Background(2)  Scenario Two (Distributed File System)

5. Background(3)  Existing Method White Box X-Trace Black Box Wap5 Sherlock  Comparison of White Box and Black Box WhiteBo x BlackBo x OverheadLargeSmall Modification to ProgramYesNo Notification of ProgramNoYes AccuracyHighLow

6. Origin of X-Trace  How to Diagnosis a Person? 1. Radioactive Material Implies: We need a vector flowing in our body. 2. X-Ray Detector Implies: We need a collector to monitor activities. 3. Overhead Implies: There is no free lunch.

7. X-Trace(Vector)  Vector: X-Trace Metadata

8. X-Trace(Flowing Vector)  Flowing Vector Only Vectors are of no use. We make it flow and we get the info. The following is an entity we want to diagnosis.

9. X-Trace(Flowing Vector) Continued  Let Vectors Flow. Two Ways: pushNext() and pushDown()

10. X-Trace(Collector)  Like diagnosing a person, we need a god to collect all the data and reconstruct offline trees.  The question is how to?

11. X-Trace(Overhead)  Modification of Existing Program

12. X-Trace(Overhead) Continued  Influence on Current Network Flow 1. Metadata is very small which brings little additional flow to the network. 2. Reports are sent in different channels which doesn’t occupy current network flow

13. Usage Scenarios of X-Trace(1)  Web Request and Recursive DNS queries

14. Usage Scenarios of X-Trace(2)  A Web Hosting Site

15. Usage Scenarios of X-Trace(3)  An Overlay Network

16. Potential Problems Mentioned by Author  Report Loss  Managing Report Traffic  Non-Tree Request Structures  Partial Deployment  Security Consideration

17. We have examined White Box. So let’s come to some other approach, which may not be that accurate but may cost less overhead. First, we need some models.

18. Author: Victor Bahl, Ranveer Chandra, Albert Greenberg, Srikanth Kandula, David A. Maltz, Ming Zhang Presenter: Yinzhi Cao

19. Outline  Models Node Model Network Model Relationship Model  How to use Our Model  Algorithm Efficiency  Evaluation

20. Models  The main idea of this paper is to establish a model of network and use this model to diagnose.  We have three levels of Model: Node, Network and Relationship.

21. Node Model  Node has three status: down, up and troubled.

22. Network Model  Graph  What’s more? Inference Graph.

23. Relationship Model(1)  Noisy-Max

24. Backup Slides 1  First, we use the model below. The circle means with x probability the output is the input, and with 1-x probability the output is up.  Let’s use unordered pair {x,y} to represent node status. {1,1} = {1} up {0,1} troubled {0,0} = {0} down

25. Backup Slides 2  So the status of Child can be represented as follows. Status(Child) = |Status(Parent)Status(Parent)| means outer product. And we define |(x,y)| = = xy.

26. Relationship Model(2)  Selector

27. Relationship Model(3)  Failover

28. Backup Slides 3  We use definition before.  Status(Parent1)={x1,x2}, Status(Parent2)={y1,y2}.  Status(Child)={(x1+x2)x1+not(x1+x2)y1, (x1+x2)x2+not(x1+x2)y2} + means and, * means or which is skipped.

29. How to Use Model?  Fault Localization on the Inference Graph

30. Algorithm Efficiency(1)  Calculations inside Inference Graph ( noisy max relationship )  Reduce time complexity from O(3 n ) to O(n)

31. Algorithm Efficiency(2)  Comparison of Multiple Input and Observation  Two Methods to Use 1. Examine Data Sets with High Probability and Ignore Small Ones 2. Dynamic Programming (Reduce Redundancy)

32. Algorithm Efficiency(3)  Author conclude two observations using these two methods. 1. It is very likely that at any point in time only a few root-cause nodes are troubled or down. 2. Since a root-cause is assigned to be up in most assignment vectors, the evaluation of an assignment vector only requires re- evaluation of states at the descendants of rootcause nodes that are not up.

33. Evaluation  Inference Graph Established

34. Accuracy Compared with others

35. Time to Localize Faults

36. Impact of Errors in Inference Graph

37. Open Issues  The Node Model is very simple, which only has three status. Can we have a continuous model of it?  Can we take some stochastic process concept like Markov-Chain into this model?