Changes between Version 10 and Version 11 of INSTOOLSSummary


Ignore:
Timestamp:
05/03/11 16:08:37 (8 years ago)
Author:
griff@netlab.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • INSTOOLSSummary

    v10 v11  
    11= INSTOOLS, Instrumentation Tools =
    22
    3 Instrumentation Tools (INSTOOLS) is a network instrumentation and measurement framework designed to make it easy to deploy network measurement infrastructure into a slice.  Once deployed, INSTOOLs allows the use to "see" the network behavior using a standard web browser. INSTOOLS consists of three basic components:
    4  * Instrumentation: a set of scripts and tools that deploy themselves into a slice to monitor the slice. see [wiki:Instrumentize instrumentize]
    5  * Measurement: data is captured while the system is running.
    6  * Presentation: the processed data is presented to the user. see [wiki:SlicePortal INSTOOLS Portal] and [wiki:INSTOOLSInterface INSTOOLS Live View]
    7 The INSTOOLS framework is designed to make these components easy for the user to specify, configure and deploy. The INSTOOLS user does not need to be an expert in system administration or network management, The goal is not to reinvent the wheel, but, rather develop ways to automatically deploy and leverage existing tools. Network state information is typically more important than packet trace information, therefore many of the tools used measure data such as routing tables, packet counters (e.g., interface counters), cache entries (e.g., ARP, DNS, and NAT tables), processor load averages, memory statistics, host configurations, firewall rules, etc.
     3Instrumentation Tools (INSTOOLS) is a network instrumentation and measurement framework designed to make it easy to deploy network measurement infrastructure into a slice.  Once deployed, INSTOOLs allows the use to "see" the network behavior using a standard web browser.
     4From a user's viewpoint, there are basically two steps required to use INSTOOLs:
     5 * Instrument the Slice: The users runs a script that deploys the necessary network monitoring software into a slice which then begins collecting network traffic measurements for that slice -- see [wiki:Instrumentize instrumentize]
     6 * Visualize/Graph the Collected Measurements: After instrumenting the slice, the user is given a web page to visit in order to "see" a live view of the network traffic flowing through the slice.  Users can either use the Portal View [wiki:SlicePortal INSTOOLS Portal] that shows the slice on a map and allows users to click on any link or node in the slice to see its performance.  A second interface [wiki:INSTOOLSInterface INSTOOLS Live View] provides a very detailed live view of the links and nodes supported by a particular aggregate.
     7The INSTOOLS framework is designed to make configuration, deployment, and visualization of measurement data easy. The INSTOOLS user does not need to be an expert in system administration or network management, The goal is not to reinvent the wheel, but, rather develop ways to automatically deploy and leverage existing tools. Network state information is typically more important than packet trace information, therefore many of the tools used measure data such as routing tables, packet counters (e.g., interface counters), cache entries (e.g., ARP, DNS, and NAT tables), processor load averages, memory statistics, host configurations, firewall rules, etc.
    88
    99Each slice receives its own Measurement Controllers (MCs). These machines are responsible for capturing the data. Currently the slice has at least one MC per aggregate. This ensures scalability and efficiency since each set of instrumentation tools is tailored to capture, record, and display only the desired information associated with that slice.