Patent Grant
7443870
The present invention relates to methods for ensuring network traffic data for at least a minimum number of network nodes of a number of logical groups of such nodes is stored at each of several time scales.
Packet-switched networks such as those that utilize the Internet protocol are essential tools of many of today's businesses. Hence, it is essential that these networks be monitored to ensure the network traffic encounters minimal delays and other problems during transport. Such monitoring, however, involves the collection and storage of significant amounts of data. This presents several challenges, among them the problem of how to ensure data is collected for at least a minimum number of network nodes of a number of logical groups of such nodes at each of several time scales.
Nodes of a network may be allocated to a number of logical groups thereof, and storage space within a network traffic monitoring device coupled to the network then allocated so as to ensure network traffic data for at least a minimum number of the nodes of each of the logical groups is stored. This allocation scheme may be replicated at each of a number of time scales for the network traffic data. In one embodiment of the present invention, the storage space is allocated such that each logical group is permitted storage space for up to a minimum number of nodes determined by a ratio of a total number of nodes of the network and the number of logical groups of said nodes. Any excess storage space resulting from an absence of at least the minimum number of nodes in one or more of the logical groups of nodes may then be reallocated to those of the logical groups of nodes having more than the minimum number of nodes (e.g., on a round-robin, traffic volume, or number of nodes per group basis).
Described herein are methods for ensuring network traffic data for at least a minimum number of network nodes of a number of logical groups of such nodes is stored at each of several time scales at a network traffic monitoring device.
In a typical configuration, the network traffic monitoring device is coupled to an enterprise network (e.g., at an edge of such a network) and configured in such a way as to collect statistics regarding traffic (e.g., packets) flowing into, out of and within that network. In some cases, the network traffic monitoring device may be configured to group data so collected according to logical groups of network nodes within the enterprise network. For example, such groupings may be made at a business unit or other logical level. However, because the storage capacity of the network monitoring device is not infinite, and because some enterprise networks can consist of thousands of nodes, the network traffic monitoring device cannot collect and store data regarding all nodes of such logical groupings.
Because it is desirable to have at least some data collected for each of the various logical groupings of network nodes, for example to allow users to monitor traffic conditions affecting all such groupings, some decision regarding the allocation of the finite network traffic monitoring device's storage capacity must be implemented. In accordance with the present invention, the storage capacity is allocated so as to ensure that network traffic data for at least a minimum number of network nodes of each logical group of such nodes is stored at each of several time scales. Any excess storage capacity may then be allocated to those logical groups of nodes that need or might benefit from same.
By way of example, at block 110, consider a network that includes “n” logical groupings of network nodes. Each group includes at least one network node, but the groups need not include the same number of nodes each. The rationale behind the logical groupings of nodes is not critical to the present invention, but for purposes of this example assume that the logical groupings correspond to business units of the enterprise utilizing the network.
Each node of the network has an associated Internet protocol (IP) address. This is a unique node identifier that, among other things, acts as an address for other nodes to send traffic to, much in the same way as a post office address is used to ensure that mail is properly delivered. Collectively, the entire enterprise network has a total of “M” IP addresses associated therewith. M is the maximum number of IP addresses for which data needs to be collected by the network traffic monitoring device.
As indicated above, for a network of any substantial M, the network traffic monitoring device cannot store data for all M IP addresses. Hence, at block 120, some minimal allocation of this limited storage space is needed to ensure that for each of the n logical groupings of the IP addresses (i.e., the nodes associated therewith), some data is stored. In one embodiment of the present invention, this minimal number is determined by the ratio of M to n (M/n=y). That is, for each logical group, the network traffic monitoring device will initially allocate storage space for at least y IP addresses of such group.
Some logical groups will, however, have fewer than y IP addresses associated therewith. Hence, there will be excess storage space available at the network traffic monitoring device. At block 130, rather than allow this excess space to go unused, the network traffic monitoring device will allocate it to those logical groups consisting of more than y IP addresses. Such allocation can be made in any of several ways, including but not limited to round-robin allocation, allocation based on traffic volume, allocation based on number of IP addresses per group, etc.
Thus, the above allocation scheme ensures that for each logical grouping of nodes of the enterprise network, the network traffic monitoring device will store data for at least some IP addresses (nodes) of each group. A further refinement of this allocation technique involves maintaining this same strategy across multiple time scales. That is, for network traffic data grouped according to different time scales, the same allocation scheme may be employed.
At block 140, consider that the network traffic monitoring device may collect traffic statistics at any of a variety of time scales. Minute-by-minute collection is typical. However, a user may not want to view the data at such a low level of granularity. Instead, the use may wish to view the data at a higher level of granularity, such as an hour-by-hour or even day-by-day basis. At block 150, in accordance with an embodiment of the present invention, These higher-level statistical compilations may be pre-computed by the network traffic monitoring device so that when called for by the user there is no appreciable delay in presenting the results. In order to ensure that the limited storage space of the network traffic monitoring device is not overwhelmed by such additional storage requirements, the same allocation scheme as discussed above may be applied to the data compilations for these higher-level results.
Thus, methods for ensuring network traffic data for at least a minimum number of network nodes of a number of logical groups of such nodes is stored at each of several time scales at a network traffic monitoring device have been described. In the foregoing description, various examples were set forth in order to aid in the understanding of the present invention. These examples, however, should not be read to limit the scope of the present invention, which instead should only be measured in terms of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5948055 | Pulsipher et al. | Sep 1999 | A |
| 6282570 | Leung et al. | Aug 2001 | B1 |
| 6633835 | Moran et al. | Oct 2003 | B1 |
| 7218639 | Matsufuru | May 2007 | B2 |
| 7225223 | McCarthy et al. | May 2007 | B1 |
| 20040196788 | Lodha | Oct 2004 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20060039394 A1 | Feb 2006 | US |
