Managing Services and Networks Using a Peer-to-peer Approach

1. Managing Services and Networks Using a Peer-to-peer Approach Henning Schulzrinne (with Vishal Singh and other IRT members) Dept. of Computer Science Columbia University July 2007

2. Overview • The transition in IT cost metrics • End-to-end application-visible reliability still poor (~ 99.5%) • even though network elements have gotten much more reliable • particular impact on interactive applications (e.g., VoIP) • transient problems • Lots of voodoo network management • Existing network management doesn’t work for VoIP and other modern applications • Need user-centric rather than operator-centric management • Proposal: peer-to-peer management • “Do You See What I See?” • Using VoIP as running example -- most complex consumer application • but also applies to IPTV and other services • Also use for reliability estimation and statistical fault characterization

3. Network management  transition in cost balance • Total cost of ownership • Ethernet port cost  $10 • about 80% of Columbia CS’s system support cost is staff cost • about $2500/person/year  2 new PCs/year • much of the rest is backup & license for spam filters  • Does not count hours of employee or son/daughter time • PC, Ethernet port and router cost seem to have reached plateau • just that the $10 now buys a 100 Mb/s port instead of 10 Mb/s • All of our switches, routers and hosts are SNMP-enabled, but no suggestion that this would help at all

4. VoIP user experience • Only 95-99.5% call attempt success • “Keynote was able to complete VoIP calls 96.9% of the time, compared with 99.9% for calls made over the public network. Voice quality for VoIP calls on average was rated at 3.5 out of 5, compared with 3.9 for public-network calls and 3.6 for cellular phone calls. And the amount of delay the audio signals experienced was 295 milliseconds for VoIP calls, compared with 139 milliseconds for public-network calls.” (InformationWeek, July 11, 2005) • Mid-call disruptions common • Lots of knobs to turn • Separate problem: manual configuration

5. Issues in automated VoIP diagnosis • Increasingly complex and diverse network elements • Complex interactions & relationships between different network elements • Different run time bindings for each application usage instance • e.g., different calls may use different DNS, SIP proxy servers, media path • Problem in one network element may manifest itself as user perceived failure of another element

6. Circle of blame probably packet loss in your Internet connection  reboot your DSL modem ISP probably a gateway fault  choose us as provider OS VSP must be a Windows registry problem  re-install Windows app vendor must be your software  upgrade

7. Diagnostic undecidability • symptom: “cannot reach server” • more precise: send packet, but no response • causes: • NAT problem (return packet dropped)? • firewall problem? • path to server broken? • outdated server information (moved)? • server dead? • 5 causes  very different remedies • no good way for non-technical user to tell • Whom do you call?

8. VoIP diagnosis • What is automated VoIP diagnosis? • Determining failures in network: when, where • Automatically finding the root cause of the failure: why • Why VoIP diagnosis? • networks are complex --> difficult to troubleshoot problems • automatic fault diagnosis reduces human intervention • Issues in VoIP diagnosis • Detecting failures/faults • Finding the cause of failure, determining dependency relationships among different components for diagnosis • Solution steps and approaches

9. Traditional network management model X SNMP “management from the center”

10. Old assumptions, now wrong • Single provider (enterprise, carrier) • has access to most path elements • professionally managed • Problems are hard failures & elements operate correctly • element failures (“link dead”) • substantial packet loss • Mostly L2 and L3 elements • switches, routers • rarely 802.11 APs • Problems are specific to a protocol • “IP is not working” • Indirect detection • MIB variable vs. actual protocol performance • End systems don’t need management • DMI & SNMP never succeeded • each application does its own updates

11. Management what causes the most trouble? network understanding fault location we’ve only succeeded here configuration element inspection

12. Managing the protocol stack protocol problem authorization asymmetric conn (NAT) media echo gain problems VAD action RTP SIP protocol problem playout errors UDP/TCP TCP neg. failure NAT time-out firewall policy IP no route packet loss

13. Types of failures • Hard failures • connection attempt fails • no media connection • NAT time-out • Soft failures (degradation) • packet loss (bursts) • access network? backbone? remote access? • delay (bursts) • OS? access networks? • acoustic problems (microphone gain, echo)

14. Examples of additional problems • ping and traceroute no longer works reliably • WinXP SP 2 turns off ICMP • some networks filter all ICMP messages • Early NAT binding time-out • initial packet exchange succeeds, but then TCP binding is removed (“web-only Internet”) • policy intent vs. failure • “broken by design” • “we don’t allow port 25” vs. “SMTP server temporarily unreachable”

15. Fault localization • Fault classification – local vs. global • Does it affect only me or does it affect others also? • Global failures • Server failure e.g. SIP proxy, DNS failure, database failures • Network failures • Local failures • Specific source failure, e.g., node A cannot make call to anyone • Specific destination or participant failure, e.g., no one can make call to node B • Locally observed but global failures, e.g., DNS service failed, but only B observed it

16. Proposal: “Do You See What I See?” • Each node has a set of active and passive measurement tools • Use intercept (NDIS, pcap) • to detect problems automatically • e.g., no response to HTTP or DNS request • gather performance statistics (packet jitter) • capture RTCP and similar measurement packets • Nodes can ask others for their view • possibly also dedicated “weather stations” • Iterative process, leading to: • user indication of cause of failure • in some cases, work-around (application-layer routing)  TURN server, use remote DNS servers • Nodes collect statistical information on failures and their likely causes

17. Architecture “not working” (notification) request diagnostics orchestrate tests contact others inspect protocol requests (DNS, HTTP, RTCP, …) ping 127.0.0.1 can buddy reach our resolver? “DNS failure for 15m” notify admin (email, IM, SIP events, …)

18. Solution approach • Store context information of past failures experienced by each node • E.g., specific server that was acting as the proxy server (for my call which failed) • Store location of past failures instances • LAN, domain, subnet • First hop at each layer • e.g., switch (MAC), default gateway (IP), domain’s proxy (application layer), • Failure count for each network element (statistical) • Last failure timestamp for each network element • Last known-good timestamp for each network element • why do I need to test the proxy for you, my call just went through • Temporal correlation of past failures • “proxy seems to be failing after DNS fails” • Each node has a runtime dependency list based on past failures and diagnostic tests

19. Solution architecture P6 P2P P2P PESQ Test P5 P7 P2P Service Provider 1 Service Provider 2 P2P P8 P4 P2P P2P DNS Test SIP Test P2 SIP Server DNS Server P3 P2P P2P P1 Call Failed at P1 Domain A Nodes in different domains cooperating to determine cause of failure

20. Solution architecture: logical view Dependencies encoded as decision tree, static and dynamic rules Alerts Admin input Failures in Network Dependency graph generation [Bayesian network based, Inference, other models ] Test results Decision Tree updates Triggers to perform TESTS. (Peer selection and Probe selection. [Dependency relationships and tests (XML) ] The above figure shows logical entities and separation of dependency graph generation and distributed diagnostic infrastructure (enclosed in blue).

21. Solution requirements • Request-response protocol between the node which experiences the failure and the peer nodes • Nodes needto perform diagnostic tests (probes), probe selection based on cost/result • Encoding the dependency relationship into a decision tree • from an expert e.g., as XML • Peer node discovery, based on • Location (local network, domain) • Capability to perform tests (based on specific tests) • Dependency graph generation and updation, based on • Network failure events • Diagnostic test results correlated with failures

22. Failure detection tools • STUN server • what is your IP address? • ping and traceroute • Transport-level liveness and QoS • open TCP connection to port • send UDP ping to port • measure packet loss & jitter • TBD: Need scriptable tools with dependency graph • initially, we’ll be using ‘make’ • TBD: remote diagnostic • fixed set (“do DNS lookup”) or • applets (only remote access) media RTP UDP/TCP IP

23. Test & probe selection • Which diagnostic probe to run? • network layer or application layer and for what kind of failures. • A probe covering broad range of failures can give faster but less accurate results • e.g., ping vs. TCP connect vs. SIP OPTIONS tests • Cost of probing • messages • CPU overhead

24. Dependency classification • Functional dependency • At generic service level • e.g., SIP proxy depends on DB service, DNS service • Structural dependency • Configuration time • e.g., Columbia CS SIP proxy is configured to use mysql database on host metro-north • Operational dependency • Runtime dependencies or run time bindings • e.g., the call which failed was using failover SIP server obtained from DNS which was running on host a.b.c.d in IRT lab

25. Dependency classifications: layered approach • Vertical and lateral dependencies • application depends on other application layer services • e.g., SIP service depends on DB, DNS service as well as lower layer services • OSI layers as service dependency layers • Application layer service also depends on transport layer service which in turn depends on network layer service • MAC layer: access point, switch • Network layer: router • Application layer: DNS, SIP, database • Topology-based dependency • e.g., calls from CS domain depends on specific SIP server • calls from lab phones depends on specific switches and routers

26. Dependency Graph

27. Dependency Graph Encoded to Decision Tree A A A Failed, Use Decision Tree D B C C Yes No Invokes Decision Tree for C B No Yes A = SIP Call C = SIP Proxy B = DNS Server D = Connectivity D Invokes Decision Tree for B Yes No Cause Not Known Report, Add new Dependency Invokes Decision Tree for D

28. Diagnostic tests - a bit more detail • SIP proxy • Proxy server availability • SIP PING • Call routing availability • INVITE tests • Call path determination • SIP TraceRoute • Media path • Quality related • Speech quality degradation - MOS • Echo • jitter- MOS, PESQ • QoS – RTCP • NAT/Firewall • Checking binding expiration. • Firewall failure to open a port - One way media. • which firewall in the path? SIP signaling ?

29. VoIP example • Call failure – possible causes • SIP proxy server • database • authentication • Media path failure • Gateway • Specific call legs – ERL, authentication, etc. • DNS server failure • End station failure • Network failure, e.g., router, switch failure • Different calls will have different run time dependencies

30. Diagnostic tests, cont’d • DNS tests • DHCP • Switch/router • ARP/RARP/multicast • BGP failures • Conference mixers • Gateway • Echo return loss- readings- analysis • DB • XCAP server tests • Presence service availability tests

31. Current work • Building decision tree system • Using JBoss Rules (Drools 3.0)

32. Future work • Learning the dependency graph from failure events and diagnostic tests • Learning using random or periodic testing to identify failures and determine relationships • Self healing • Predicting failures • Protocols for labeling event failures --> enable automatically incorporating new devices/applications to the dependency system • Decision tree (dependency graph) based event correlation

33. Failure statistics • Which parts of the network are most likely to fail (or degrade) • access network • network interconnects • backbone network • infrastructure servers (DHCP, DNS) • application servers (SIP, RTSP, HTTP, …) • protocol failures/incompatibility • Currently, mostly guesses • End nodes can gather and accumulate statistics

34. Conclusion • Hypothesis: network reliability as single largest open technical issue  prevents (some) new applications • Existing management tools of limited use to most enterprises and end users • Transition to “self-service” networks • support non-technical users, not just NOCs running HP OpenView or Tivoli • Need better view of network reliability