A Web Based Network Monitoring Tool by xiangpeng

VIEWS: 3 PAGES: 37

									Developing the Web100 Based
Network Diagnostic Tool (NDT)

       Internet2 piPEs Tutorial


            Rich Carlson
      RCarlson@internet2.edu
      Demo




http://ndt.chic.net.internet2.edu:7123




                                   11/9/04   2
Duplex Mismatch Detected




                           11/9/04   3
Normal operation in campus




                         11/9/04   4
Low throughput from remote host




                            11/9/04   5
Increase TCP buffer size




                           11/9/04   6
       Motivation for work


Measure performance to users desktop
Develop “single shot” diagnostic tool that
doesn’t use historical data
Combine numerous Web100 variables to
analyze connection
Develop network signatures for ‘typical’
network problems
                                       11/9/04   7
          Web100 Project

Joint PSC/NCAR project funded by NSF
‘First step’ to gather TCP data
 • Kernel Instrument Set (KIS)

Requires patched Linux kernel
Geared toward wide area network
performance
Future steps will automate tuning to improve
application performance
                                       11/9/04   8
         Web Based Performance tool


Operates on Any client with a Java
enabled Web browser
What it can do
 • Positively state if Sender, Receiver, or Network is
   operating properly
 • Provide accurate application tuning info
 • Suggest changes to improve performance



                                                    11/9/04   9
       Web base Performance tool

What it can’t do
 • Tell you where in the network the problem is
 • Tell you how other servers perform
 • Tell you how other clients will perform




                                                  11/9/04   10
      Internet2 piPEs Project

Develop E2E measurement
infrastructure capable of finding network
problems
Tools include
 • BWCTL: Bandwidth Control wrapper for NLANR
   Iperf
 • OWAMP: One-Way Active Measurement
 • NDT: Network Diagnostic Tool



                                           11/9/04   11
piPEs Integration
                   Internet2 Detective
                                            Network
                          “Detective”                    Detect
                                           Monitoring
                            Applet


 Discovery   Analysis                                   Interface
                                 Web Service
  Module     Module
                                Measurement
                               Domain Interface         Authorize
                                   (MDI)
 Performance Measurement
       Domain (PMD)
                                Performance
                                Measurement             Schedule
                               Controller (PMC)



                 Performance Measurement Point (PMP)      Test
             BWCTL      OWAMP TraceRoute          NDT



                                   Database              Store




                                                                    11/9/04   12
              Bottleneck Link Detection

 What is the slowest link in the end-2-
 end path?
     • Monitors packet arrival times using libpcap routine
     • Use TCP dynamics to create packet pairs
     • Quantize results into link type bins (no fractional or
       bonded links)




Cisco URP grant work



                                                        11/9/04   13
              Duplex Mismatch Detection

  Developed analytical model to describe
  how Ethernet responds (no prior art?)
  Expanding model to describe UDP and
  TCP flows
  Develop practical detection algorithm
  Test models in LAN, MAN, and WAN
  environments
NIH/NLM grant funding


                                          11/9/04   14
      Future enhancements

WiFi detection
Faulty Hardware detection
Congestion modification
Full/Half duplex detection




                             11/9/04   15
       Additional Functions and Features

Provide basic tuning information
Basic Features
 • Basic configuration file
 • FIFO scheduling of tests
 • Simple server discovery protocol
 • Federation mode support
 • Command line client support

Created sourceforge.net project page

                                      11/9/04   16
            Availability


Open Source Development project
 • http://www.sourceforge.net/projects/ndt
Tools available via from
 • http://e2epi.internet2.edu/ndt/download.html
 • Contains source code
Email discussion list ndt-users@internet2.edu
 • Goto http://e2epi.internet2.edu/ndt web site and click
    – ndt-users – General discussion on NDT tool
    – ndt-announce – Announcements on new features

                                                       11/9/04   17
            NDT Flow Chart

                      Well Known
                      NDT Server
NDT - Server                                  Client
    Web                                        Web
                      Web Page Request        Browser
   Server
                          Web page response

    Testing                                     Java
                              Test Request
    Engine                                     Applet

        Spawn child
      Child
   Test Engine




                                                        11/9/04   18
                          NDT servers
Location         Host                                     Interface     Online Stats
Chicago          http://ndt.chic.net.internet2.edu:7123   GigEtherent   http://ndt.chic.net.internet2.edu:7123/admin.html


New York         http://ndt.newy.net.internet2.edu:7123   GigEtherent   http://ndt.newy.net.internet2.edu:7123/admin.html


Washington DC    http://ndt.wash.net.internet2.edu:7123   GigEtherent   http://ndt.wash.net.internet2.edu:7123/admin.html


Houston          http://ndt.hous.net.internet2.edu:7123   GigEtherent   http://ndt.hous.net.internet2.edu:7123/admin.html


Los Angles       http://ndt.losa.net.internet2.edu:7123   GigEtherent   http://ndt.losa.net.internet2.edu:7123/admin.html


Kansas City      http://ndt.salt.net.internet2.edu:7123   GigEtherent   http://ndt.salt.net.internet2.edu:7123/admin.html


Salt Lake City   http://ndt.salt.net.internet2.edu:7123   GigEtherent   http://ndt.salt.net.internet2.edu:7123/admin.html




                                                                                                      11/9/04   19
      Results and Observations

Changing desktop effects performance
Faulty Hardware identification
Mathis et.al formula fails




                                  11/9/04   20
    Different Host, Same Switch Port


10 Mbps NIC
 • Throughput 6.8/6.7 Mbps send/receive
 • RTT 20 ms
 • Retransmission/Timeouts 25/3

100 Mbps NIC
 • Throughput 84/86 Mbps send/receive
 • RTT 10 ms
 • Retransmission/Timeouts 0/0


                                          11/9/04   21
            LAN Testing Results
100 Mbps FD
Ave Rtt       %loss               Speed
   5.41       0.00                94.09
   1.38       0.78                22.50
   6.16       0.00                82.66
   14.82      0.00                33.61

10 Mbps
    72.80     0.01                6.99
    8.84      0.75                7.15




                                          11/9/04   22
              LAN Testing Results


100 Mbps FD

Ave Rtt       %loss   loss/sec   Speed
   5.41       0.00     0.03      94.09   Good
   1.38       0.78     15.11     22.50   Bad NIC
   6.16       0.00     0.03      82.66   Bad reverse
   14.82      0.00     0.10      33.61   Congestion


10 Mbps
    72.80     0.01     0.03      6.99    Good
    8.84      0.75     4.65      7.15    Bad NIC


                                             11/9/04   23
            Mathis et.al Formula fails


Estimate = (K * MSS) / (RTT * sqrt(loss))
 • old-loss = (Retrans - FastRetran) / (DataPktsOut - AckPktsOut)
 • new-loss = CongestionSignals / PktsOut




Estimate < Measured (K = 1)
 • old-loss 91/443 (20.54%)
 • new-loss 35/443 (7.90%)



                                                                    11/9/04   24
       NDT Hardware Requirements
Minimum requirements
 • 500 MHz Intel or AMD CPU
 • 64 MB of RAM
 • Fast Ethernet
Buying something now
 • 2 GHz or better processor
 • 256 MB of RAM
 • Gigabit Ethernet
Disk space for executables and log files
 • No disk I/O involved during test

                                      11/9/04   25
          NDT Software Requirements

Web100 enhancements
 • Linux kernel
 • User library

Other 3rd party SW needed to compile
source
 • Java SDK
 • pcap library
 • Client uses Java JRE (beware of version mismatch)

NDT source file
 • Test engine (web100srv) requires root authority
                                                     11/9/04   26
       Recommended Settings
There are no settings or options for the
Web based java applet.
 • It allows the user to run a fixed set of tests for a
   limited time period
Test engine settings
 • Turn on admin view (-a option)
 • If multiple network interfaces exist use –i option
   to specify correct interface to monitor (ethx)
Simple Web server (fakewww)
 • Use –l fn option to create log file

                                                     11/9/04   27
       Potential Risks

Non-standard kernel required
 • GUI tools can be used to monitor other ports

Public servers generate trouble reports
from remote users
 • Respond or ignore emails

Test streams can trigger IDS alarms
 • Configure IDS to ignore NDT server




                                                  11/9/04   28
         Possible Alternatives

Other tools that can perform client testing
 • Several web sites offer the ability for a user to check
   PC upload/download speed.
 • Internet2/Surfnet Detective
 • NCSA Advisor




                                                     11/9/04   29
Supplemental information




                           11/9/04   30
       NDT’s Web100 Based Approach

Simple bi-directional test to gather E2E
data
Gather multiple data variables from server
Compare measured performance to
analytical values
Translate network values into plain text
messages
Geared toward campus area network
                                       11/9/04   31
      NDT Benefits

End-user based view of network
Can identify configuration problems
Can identify performance bottlenecks
Provides some ‘hard evidence’ to users
and network administrators to reduce
finger pointing
Doesn’t rely on historical data

                                      11/9/04   32
      NDT methodology

Identify specific problem(s) that affect
end users
Analyze problem to determine ‘Network
Signature’ for this problem
Provide testing tool to automate
detection process



                                       11/9/04   33
      IEEE 802.11 (WiFi) Detection

Detect when host is connected via
wireless (wifi) link
 • Radio signal changes strength
 • NICs implement power saving features
 • Multiple standards (a/b/g/n)


Some data has been collected



                                          11/9/04   34
       Faulty Hardware/Link Detection
Detect non-congestive loss due to
 • Faulty NIC/switch interface
 • Bad Cat-5 cable
 • Dirty optical connector


Preliminary works shows that it is
possible to distinguish between
congestive and non-congestive loss


                                     11/9/04   35
       Full/Half Link Duplex setting

Detect half-duplex link in E2E path
 • Identify when throughput is limited by half-duplex
   operations



Preliminary work shows detection
possible when link transitions between
blocking states


                                                  11/9/04   36
       Normal congestion detection

Shared network infrastructures will
cause periodic congestion episodes
 • Detect/report when TCP throughput is limited by
   cross traffic
 • Detect/report when TCP throughput is limited by
   own traffic




                                                11/9/04   37

								
To top