Top Banner
USING PACKET HISTORIES TO TROUBLESHOOT NETWORKS Presented by: Yi Gao Emnets Seminar 2014-4-6
20

Using Packet Histories to Troubleshoot Networks

Feb 18, 2016

Download

Documents

Niyati Ghodke

Using Packet Histories to Troubleshoot Networks. Presented by: Yi Gao Emnets Seminar 2014-4-6. Operating Networks is Hard. Existing network troubleshooting tools traceroute , ping, SNMP, NetFlow , sFlow , … We are still far from an era of automated troubleshooting - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Using  Packet Histories  to Troubleshoot  Networks

USING PACKET HISTORIES TO TROUBLESHOOT NETWORKS

Presented by: Yi GaoEmnets Seminar2014-4-6

Page 2: Using  Packet Histories  to Troubleshoot  Networks

Operating Networks is Hard• Existing network troubleshooting tools

• traceroute, ping, SNMP, NetFlow, sFlow, …• We are still far from an era of automated troubleshooting

• What we want to ask the network

Page 3: Using  Packet Histories  to Troubleshoot  Networks

Packet History• The route a packet takes through a network plus the switch state and header modifications it encounters at each hop

Page 4: Using  Packet Histories  to Troubleshoot  Networks

Basic Idea• Send a control message (postcard) at each hop• In each postcard

• A copy of the packet header• The switch ID• The output ports• A version number for the switch forwarding state

• Collect and analyze postcards at a server

Page 5: Using  Packet Histories  to Troubleshoot  Networks

NetSight Architecture

Page 6: Using  Packet Histories  to Troubleshoot  Networks

Outline• Life of a postcard• History assembly• Postcard compression• Use packet histories• Evaluation

Page 7: Using  Packet Histories  to Troubleshoot  Networks

Life of a Postcard

Page 8: Using  Packet Histories  to Troubleshoot  Networks

Life of a Postcard (Cnt.)• Step 1:

• From switch to server

Page 9: Using  Packet Histories  to Troubleshoot  Networks

Life of a Postcard (Cnt.)• Step 2:

• From servers to servers

Page 10: Using  Packet Histories  to Troubleshoot  Networks

Life of a Postcard (Cnt.)• Step 3:

• From servers to disks

Page 11: Using  Packet Histories  to Troubleshoot  Networks

History Assembly• Step 3 in the life of a postcard• From multiple postcards to assemble a packet history, in case of reordering

• Solution • Packet ID hash• Topological sort

Page 12: Using  Packet Histories  to Troubleshoot  Networks

Postcard Compression• Step 2&3 in the life of a postcard• In step 2: Intra-flow compression• In step 3: Inter-flow compression

Page 13: Using  Packet Histories  to Troubleshoot  Networks

Use Packet Histories• Packet history filter• Applications

• ndb• netwatch• netshark• nprof

Page 14: Using  Packet Histories  to Troubleshoot  Networks

Use Packet Histories - PF• Postcard Filters (PF)

• A filter to match a packet at a hop (a postcard)

• A PF for a packet with source IP A, entering switch S at any input port other than port P

Page 15: Using  Packet Histories  to Troubleshoot  Networks

Use Packet Histories - PHF• Packet History Filter (PHF)

• To express interest in packet histories

• Let X be a PF• start at X: ^{{X}}• end at X: {{X}}$• go through X: {{X}}

Page 16: Using  Packet Histories  to Troubleshoot  Networks

Use Packet Histories - Applications• Network Profiler

• Profile a particular link• {{--dpid X --outport p}}

• Reachability Error• a PHF to specify packets from A destined for B that

never reach the intended final hop• ^{{--bpf "ip src A and dst B" --dpid X --inport p1}}[^{{--

dpid Y --outport p2}}]*$

Page 17: Using  Packet Histories  to Troubleshoot  Networks

Evaluation – PHF matching latency

Page 18: Using  Packet Histories  to Troubleshoot  Networks

Evaluation - Overhead

• Without compression• 31%

• With compression• 3% ~ 7%

Page 19: Using  Packet Histories  to Troubleshoot  Networks

Summary• Language

• Packet History Filter concisely represents packet histories of interest

• Applications• A suite of network diagnosis apps built atop the

NetSight API• Platform

• The design, implementation, and evaluation of NetSight

Page 20: Using  Packet Histories  to Troubleshoot  Networks

Thanks!