Browse Prior Art Database

Network performance analysis through recursive remote execution

IP.com Disclosure Number: IPCOM000015062D
Original Publication Date: 2001-Sep-25
Included in the Prior Art Database: 2003-Jun-20
Document File: 1 page(s) / 41K

Publishing Venue

IBM

Abstract

Current network analysis tools do a good job of measuring network performance between two points. But that makes analyzing a network a very tedious process. There are two basic aspects to this design that work together to provide the funciton that we need. The first basic function is a GUI based upon a Network diagram (or we might just stage the function in as a hierarchy first) of the network. The second basic function is a "recursive crawling" analysis program.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 1

Network performance analysis through recursive remote execution

   Current network analysis tools do a good job of measuring network performance between two points. But that makes analyzing a network a very tedious process. There are two basic aspects to this design that work together to provide the funciton that we need. The first basic function is a GUI based upon a Network diagram (or we might just stage the function in as a hierarchy first) of the network. The second basic function is a "recursive crawling" analysis program.

We are aware that some current network analysis tools give a GUI that provides a view of the network. But the tools that we have seen all show the network nodes from the point of view of the analysis tool. In our design, the GUI will show the network from a perspective of what connections are of interest. Not necessarily the physical network. For example, in a LAN of 6 nodes (a, b, c, d, e, f) all nodes may be attached in (token) ring, or switched. Logically each one can connect to all of the others. A typical network analysis tool is capable of being installed on any one of these nodes and measuring the performance between it and all the others. So if you installed a network analyis tool on A, you can see the performance between A and any of the others, but not between B and C. etc.

Our GUI would allow the user to indicate which connections between systems are of interest. For example a and b may both send request to c. c in turn may send some requests to d, and some to e, e may send them to f. Physically any node can communicate with any other, but in any given network, only certain paths are likely to be of interest. Our GUI would provide the user with a way ot spec...