CA2284995C - Method and apparatus for determining frame relay connections - Google Patents
Method and apparatus for determining frame relay connections Download PDFInfo
- Publication number
- CA2284995C CA2284995C CA002284995A CA2284995A CA2284995C CA 2284995 C CA2284995 C CA 2284995C CA 002284995 A CA002284995 A CA 002284995A CA 2284995 A CA2284995 A CA 2284995A CA 2284995 C CA2284995 C CA 2284995C
- Authority
- CA
- Canada
- Prior art keywords
- channels
- data
- amount
- interface
- determining
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
Abstract
A system determines that a frame relay connection exists between an interface on a first interface device and an interface on a second interface device, for example by comparing addresses resident in routing tables of the interface devices. The system then queries each of the first and second interface devices, to determine the amount of traffic that is communicated by each channel of each of the two interfaces. This data is then correlated to determine the relative amount of data by each channel on each of the two interfaces, and the pair of channels having the best correlation are determined to represent an actual connection.
Description
a METHOD AND APPARATUS FOR
DETERMINING FRAME RELAY CONNECTIONS
BACKGROUND OF THE INVENTION
Field of the Invention The invention relates to frame relay communications, and more particularly to a method and apparatus for identifying on which channel a frame relay communication is made.
to 2. Discussion of the Related Art Computer networks~are widely used to provide increased computing power.
sharing of resources and communication between users. One type of network is referred to as a frame relay network -- it complies with an interface standard that provides statistical time division multiplexing and circuit switching, and is typically optimized for the transport of protocol-~ 5 oriented data.
In a typical frame relay network, a communications carrier provides a designated data throughput between two particular entry points (sites) to the network. The data is passed through a "connection," which is also referred to as a "virtual circuit." A permanent virtual circuit (PVC) has one guaranteed data throughput, while a switched virtual circuit (SVC) allows additional 20 throughput in response to a specific demand. Each connection (i.e., virtual circuit) is identified by a data link connection identifier or index (DLCI) number. Many DLCI numbers have local significance only, i.e., a connection identified by a first DLCI number at a first site, may be identified by a different DLCI number at a second site. The connection may be implemented via a set data path, or the data may be re-routed through a different data path depending upon circuit 25 performance. Additional detail on frame relay architectures, protocols, and analysis is described in Analvzin~ Broadband Networks, Mark A. Miller, M&T Books, pp. 31-169 (1994).
In the operation and maintenance of computer networks, a number of issues arise including traffic overload on various parts of the network, optimum placement and interconnection of network resources, security, isolation of network faults, and the like. These 3o issues become increasingly complex and difficult to understand and manage as the network becomes larger and more complex. For example, if a network device is not sending messages, it AI~REPf~cD NEE' may be difficult to determine whether the fault is with the device itself a data communication link, or an intermediate network device between the sending and receiving devices.
Network management systems have been developed to resolve such issues. Older systems typically operated by collecting large volumes of information, which then required evaluation by a network administrator; this placed a tremendous burden on, and required a highly-skilled network administrator. Newer network management platforms systematize the knowledge of the networking expert such that common problems can be detected, isolated and repaired. either automatically or with the involvement of less-skilled personnel. Such a system typically includes a graphical representation of that portion of the network being monitored by the system. An example of the newer automated system is the SpectrumTM network management platform available from Cabletron Systems, Inc., Rochester, New Hampshire.
USA.
It would be desirable to provide a network management system that can determine and display a graphical representation of particular connections which exist in a frame relay network.
However, a single interface device, such as a router, switch, or bridge, may have several t 5 interfaces, each of which communicates with the frame relay network.
Additionally, each interface may communicate over several distinct frame relay connections. Still further. each interface device may not have specific knowledge regarding the other interface devices) with which it is communicating, much less the specific virtual circuits (connections) that exist at any given time. Accordingly. it would be desirable to be able to determine particular connections 2o from data which is available from the interface devices.
SUMMARY OF THE INVENTION
According to one embodiment of the present invention, a network management system is provided which determines that a frame relay connection is coupled between a first interface on a 25 first interface device and a second interface on a second interface device, for example by comparing addresses which reside in routing tables of the first and second interface devices. The system queries the management information base (MIB) of each of the first and second interface devices, to determine the amount of traffic that is communicated by each channel of the two interfaces. This data is then correlated to determine a relative amount of data transmitted on each 3o channel of the two interfaces, and the two channels having the best correlation are determined to represent a particular connection.
.... ~.~..
DETERMINING FRAME RELAY CONNECTIONS
BACKGROUND OF THE INVENTION
Field of the Invention The invention relates to frame relay communications, and more particularly to a method and apparatus for identifying on which channel a frame relay communication is made.
to 2. Discussion of the Related Art Computer networks~are widely used to provide increased computing power.
sharing of resources and communication between users. One type of network is referred to as a frame relay network -- it complies with an interface standard that provides statistical time division multiplexing and circuit switching, and is typically optimized for the transport of protocol-~ 5 oriented data.
In a typical frame relay network, a communications carrier provides a designated data throughput between two particular entry points (sites) to the network. The data is passed through a "connection," which is also referred to as a "virtual circuit." A permanent virtual circuit (PVC) has one guaranteed data throughput, while a switched virtual circuit (SVC) allows additional 20 throughput in response to a specific demand. Each connection (i.e., virtual circuit) is identified by a data link connection identifier or index (DLCI) number. Many DLCI numbers have local significance only, i.e., a connection identified by a first DLCI number at a first site, may be identified by a different DLCI number at a second site. The connection may be implemented via a set data path, or the data may be re-routed through a different data path depending upon circuit 25 performance. Additional detail on frame relay architectures, protocols, and analysis is described in Analvzin~ Broadband Networks, Mark A. Miller, M&T Books, pp. 31-169 (1994).
In the operation and maintenance of computer networks, a number of issues arise including traffic overload on various parts of the network, optimum placement and interconnection of network resources, security, isolation of network faults, and the like. These 3o issues become increasingly complex and difficult to understand and manage as the network becomes larger and more complex. For example, if a network device is not sending messages, it AI~REPf~cD NEE' may be difficult to determine whether the fault is with the device itself a data communication link, or an intermediate network device between the sending and receiving devices.
Network management systems have been developed to resolve such issues. Older systems typically operated by collecting large volumes of information, which then required evaluation by a network administrator; this placed a tremendous burden on, and required a highly-skilled network administrator. Newer network management platforms systematize the knowledge of the networking expert such that common problems can be detected, isolated and repaired. either automatically or with the involvement of less-skilled personnel. Such a system typically includes a graphical representation of that portion of the network being monitored by the system. An example of the newer automated system is the SpectrumTM network management platform available from Cabletron Systems, Inc., Rochester, New Hampshire.
USA.
It would be desirable to provide a network management system that can determine and display a graphical representation of particular connections which exist in a frame relay network.
However, a single interface device, such as a router, switch, or bridge, may have several t 5 interfaces, each of which communicates with the frame relay network.
Additionally, each interface may communicate over several distinct frame relay connections. Still further. each interface device may not have specific knowledge regarding the other interface devices) with which it is communicating, much less the specific virtual circuits (connections) that exist at any given time. Accordingly. it would be desirable to be able to determine particular connections 2o from data which is available from the interface devices.
SUMMARY OF THE INVENTION
According to one embodiment of the present invention, a network management system is provided which determines that a frame relay connection is coupled between a first interface on a 25 first interface device and a second interface on a second interface device, for example by comparing addresses which reside in routing tables of the first and second interface devices. The system queries the management information base (MIB) of each of the first and second interface devices, to determine the amount of traffic that is communicated by each channel of the two interfaces. This data is then correlated to determine a relative amount of data transmitted on each 3o channel of the two interfaces, and the two channels having the best correlation are determined to represent a particular connection.
.... ~.~..
According to a method embodiment of the invention, a method is provided for identifying a connection in a frame relay network. The method comprises the steps of identifying a first plurality of channels of a first interface and a second plurality of channels of a second interface that potentially relate to a frame relay connection, and then selecting, as an identifier for the frame relay connection, a first channel from the first plurality of channels and a second channel from the second plurality of channels based upon a relative amount of data transferred on each of the first and second channels.
Yet another apparatus embodiment includes a data module and a results analyzer. The data module is coupled to a frame relay network and has an output that provides an indication of a first plurality of channels and a second plurality of channels that potentially relate to a frame relay connection. and the results analyzer selects a first channel from the first plurality of channels and a second channel from the second plurality of channels based upon a relative amount of data transferred on each of the first and second channels, in order to identify the frame relay connection.
~ 5 In any of these embodiments, a plurality of correlation factors may be determined, for example by a statistics module, for each potential pair of channels. The correlation factor having a best (e.g., highest) value may be used to determine which of the plurality of potential pairs of channels has the best (e.g., highest] correlation factor. A correlation factor may be related to a similarity between an amount of data transmitted by a first channel and an amount of data 3o received by a second channel during a period of time.
In any of these embodiments, a first interface device may be queried to determine an amount of data that has been transferred by one channel as of a first time.
and the first interface device queried again to determine an amount of data that has been transferred by the one channel as of a second time, wherein the amount of data being transferred is determined to be the 25 difference between these two amounts. A similar set of queries and difference determination may be made for a second interface of the potential pair.
In accordance with at least one embodiment, a determination may be made that a connection exists between an interface of a first interface device and an interface of a second interface device by comparing an address of the first interface with a destination address of data 3o transmitted by the second interface.
These and other features and benefits of the present invention will be more particularly described in the following detailed description.
' ~ ~ V 1 .
~f f . n . a 1 1 f 1 BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a schematic diagram of a network management system that interfaces with elements of a frame relay network;
Fig. 2 is a block diagram of two devices which each interface with a frame relay network, such as the one shown in Fig. 1;
Fig. 3 shows data which may be obtained from the two devices of Fig. 2, in accordance with at least one network protocol standard;
Fig. 4 is a block diagram of a network management system according to one embodiment of the invention, and a frame relay device which communicates therewith;
Fig. 5 is a process flow diagram showing steps of a process in accordance with an embodiment of the invention;
Fig. 6 is a flow diagram with greater detail of a portion of the process shown in Fig. 5;
Fig. 7 is a flow diagram with greater detail of another portion of the process shown in 1 s Fig. 5;
Fig. 8 is an example of a traffic table, for data such as that shown in Fig.
3, wherein the data relates to a first interface;
Fig. 9 is an example of a traffic table, for data that relates to a second interface; and Fig. 10 is an example of a correlation matrix for the data that is shown in Fig. 3.
DETAILED DESCRIPTION
Aspects of the present invention will be described in conjunction with the use of a model-based network management system, such as SpectrumTM, which is described in U.S.
Patent No. 5,261,044, issued November 9, 1993 to R. Dev et al. The SpectrumTM
network management system is commercially available and described in various user manuals and literature available from Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867.
Other commercially available network management systems and related applications include: HP OpenView, Hewlett Packard Corp., 3000 Hanover Street, Palo Alto, CA 94304;
3o LattisNet, Bay Networks, 4401 Great American Pkwy., Santa Clara, CA 95054;
IBM
Netview/6000, IBM Corp., Old Orchard Road, Armonk, N~ 10504; and SunNet l~Ianager, SunConnect, 2550 Garcia Ave, Mountain View, CA 94043. Embodiments of the invention 1T' . v~i~, flJc'J ShEi described herein may be applicable to such other network management systems or portion thereof.
Fig. 1 shows a network management system 10 that monitors a frame relay network 11 and other networks) 12. The other network{s) 12 may be other frame relay networks. or other types of networks, e.g., ethernet. token ring, FDDI, etc. The frame relay network 1 1 is illustrated as connecting three different sites 13 that communicate across the frame relay network - site A
(13A), site B (13B), and site C (13C). The network management system 10 monitors the~frame relay network 11 by communicating with devices within each of the sites 13A-C.
Each device within the sites 13A-C is referred to herein as an "interface device."
Fig. 1 shows one embodiment of the network management system 10, including a network interface and control subsystem 16. a virtual network machine 17, and a user interface 18. The virtual network machine 17 is coupled to both the network interface and control subsystem 16 and the user interface 18. The network interface and control subsystem 16 is coupled to each of the frame relay sites 13A-C by a corresponding one of communication paths t 5 14A-C, and is coupled to the other networks) 12 by communication path 15.
The communication paths 14A-C and 15 may be actual connections. or may represent a virtual access to data that relates to a particular site. For example, the network interface and control subsystem 16 may access a single data repository that stores data for all of the sites 13A-C, instead of directly accessing the interface devices on each site.
2o In one embodiment, the network management system 10 comprises a programmed digital computer, wherein a program is implemented using an object-oriented programming language such as C++, Eiffel, SmallTalk, and Ada. The virtual network machine 17 includes interrelated intelligent models (objects) of network entities and relations between network entities, including a capability for acquiring network data pertaining to a condition of a network entity from the 25 corresponding network entity, and for those entities not capable of being contacted. inferring their status from the status of other communicating entities. The virtual network machine 17 maintains objects which include network data relating to the corresponding network entity and one or more inference handlers for processing the network data. the inference handlers being responsive to changes occurring in the same and/oi a different object. The network data can then 3o be transferred to the user interface 18 for supplying the network data to a user.
The user interface 18 may be resident on a computer that is different from the computer on which subsystem 16 and virtual network machine 17 reside. In such an arrangement. the user interface 18 may be referred to as a client, while the network interface and control subsystem 1 G
and the virtual network machine 17 may be referred to as a server. Several instances of the user interface 18 may exist for a single instance of the virtual network machine 17, so that several users may concurrently view different aspects of the networks being monitored by the network management system 10.
In one embodiment of the invention. the network interface and control subsystem 16 obtains data relating to the frame relay network 11 in accordance with the Simple Network Management Protocol {SNMP). SNMP is a standard that defines common messages and databases to support network management. A group known as the Internet Engineering Task i o Force (IETF) has established several standards in accordance with the SNMP
framework, and in particular a standard known as a Management Information Base (MIB). The MIB
specifies the data items that certain devices must maintain. other data items that are proprietary or optional.
and the operations allowed on such devices. For example. the MIB specifies that Internet Protocol (IP) software must keep a count of all octets (8-bit bytes) that arrive over each network ~ 5 interface. Thus, a network management system is able to transmit a specific query (defined by the MIB} to a network interface device, and receive in response a message providing such count data stored within the network interface device's MIB. A document known as the IETF RFC
(Request for Comments) 1315 defines a portion of the MIB for use with managing frame relay protocols.
2o RFCs such as RFC-1315 are available in both printed and electronic form.
Printed copies may be obtained from Network Solutions, Inc., 505 tluntmar Park Drive, Herndon VA
22070. while electronic copies may be accessed on the Internet. In particular, an Internet user may use an "anonymous" FTP to the host ds.internic.net (residing at 129.20.239.132) and retrieve the desired files from the directory "rfc/".
25 Fig. 2 illustrates detail of two interface devices, site A router 21, and site B router 22, each of which is coupled to the frame relay network 11. Each of routers 21 and 22 may have several interfaces. In particular, site A router 21 has interfaces If7, If8.
and If9, while site B
muter 22 has interfaces Ifl. If2, If3, and If4: Each of these interfaces are coupled to the frame relay network 11.
3o In order for a network management system to effectively monitor and accurately represent the frame relay network 11, it is desirable to determine which interfaces share a connection within the frame relay network. If two devices are performing routing or bridging, _7_ then the network management system 10 can infer a connection between two of the interfaces by reading the route tables or transparent bridge tables (defined within the MIB) of the interface devices 21 and 22. In the example shown in Figs. 2 and 3. the interface devices 21 and 22 are routers that perform routing functions, and therefore the IP routing tables may be read by the network management system 10. Information relating to the IP routing tables is defined within the MIB, and is available from RFC documents such as MIB-II RFC-1213.
In particular, Fig. 3 shows muter information data 30 and routing table entries 31 for the site A router 21. The router information data 30 indicates that device 21 is a frame relay interface, and that information was requested pertaining to interface Ifs, which has an IP address of 13I .124.196. I . The router table information 31 shows that there are three groups of destination addresses (e.g., subnets) for messages to be sent from interface Ifs, two of which had a next hop IP address of I 31.124.196.3, and one of which had a next hop IP
address of 131.124. i 96.2.
Similarly, router information data 32 relates to the site B muter 22, and router table l s entries 33 contain information pertaining to interfaces If2 and If4 of the site B router 22. The muter table information 33 shows that there are three groups of destination addresses (e.g., subnets) for messages to be sent from interface If4 with a next hop IP address of 131.124.196.1.
Because messages are to be sent from interface I~ to interface If4 (as indicated by the next hop IP address 131.124.196.2 in table 31 matching the IP address of interface If4), a network management system can infer that a frame relay connection exists between interface Ift7 and interface If4. This conclusion is further supported by the evidence that messages are to be sent from interface If4 to interface Ifs, as indicated by several of the next hop IP addresses in router table entries 33 (from interface If4) matching the IP address of interface lf~
(131.124.196.1).
Thus, by determining the IP address of a message to be sent from an interface across a frame relay network, and then matching this IP address to the IP address of another interface on the frame relay network, a network management system can determine which two interfaces on a frame relay network share a connection. Similar results may be achieved by querying the transparent bridge tables if the two interface devices are performing bridge functions. The bridge 3o MIB is defined in RFC-1493.
However, each interface may have several "channels", each communicating across a different connection within the frame relay network 11. For example. Fig. 2 shows that interface _$_ Ifs has three channels 211, 212, and 2I3, interface If8 has two channels 2I4 and 215, interface If4 has two channels 221 and 222. interface If3 has one channel 223, and interface If2 has three channels 224, 225, and 226. Thus, even though it may be known which two interfaces share a connection within the frame relay network 1 l, it still may be uncertain which two channels of the two interfaces actually share the connection.
Fig. 4 is a block diagram showing operation of a system to determine the channels that share a frame relay connection. In particular, Fig. 4 depicts a network interface and control subsystem 40 which represents an embodiment of the network management and control subsystem 16 of Fig. 1. The subsystem 40 communicates with a frame relay interface device 41, t o which as described above, may be a muter, switch, network interface card.
or any device that communicates across a frame relay network (not shown in Fig. 4). The network interface and control subsystem 40 includes a data gatherer 42, a statistics module 43, and a results analyzer 44. Traffic tables 45A, 45B, ... 45N are coupled between the data gatherer 42 and the statistics module 43, and correlation matrices 46A, 46B, ..., 46N are coupled between the statistics module ~ 5 43 and the results analyzer 44.
The results analyzer 44 is the portion of the network interface and control module that provides input to the virtual network machine. and the data gatherer 42 interfaces with the interface device 41. As described above, associated with the interface device 41 is a MIB 47. A
portion of the MIB 47 is the frame relay circuit table (frCircuitTable) 48, as defined in RFC-20 1315. The data gatherer 42 communicates with the interface device 41 in the form of queries 49 which request information from the MiB 47, and in response the MIB 47 provides a count of octets sent by a particular channel of an interface of the interface device (frCircuitSent Octets), and a count of octets received by a particular channel of an interface of the interface device (frCircuitReceivedOctets), generally shown as 50 in Fig. 4.
25 Fig. 5 is a high level process flow diagram of operations performed by an embodiment of the network interface and control subsystem 40. In step 51, the data gatherer 42 determines that a frame relay connection exists between a first interface and a second interface (e.g., interface If~
of site A router 21 and interface If4 of site B muter 22). As discussed above, this determination may be made by analyzing the next hop address within a routing table, or by other methods 3o known to those skilled in the art.
In step 52, the data gatherer 42 determines an amount of data that is communicated in each direction by each channel of the first and second interfaces. This step may include _g_ determining which channels are actually active (which may also be determined by querying the MIB 47}, in which case any channels~that are not active may be eliminated from consideration.
Additionally, it is not necessary to determine the amount of data in both directions, although such analysis may result in a more complete solution as described in more detail below.
s In one embodiment, the data gatherer 42 stores the data amounts in the appropriate traffic table 45. One of the traffic tables 45A may be for the analysis of a first interface, while another of the traffic tables 45B may be for the analysis of a second interface.
Once the amount of data has been determined, the statistics module 43 determines the level of correlation between data on each potential channel pair. A potential channel pair is made up of one channel from each interface for which a connection is known to exist. In particular, step 53 indicates that the level of correlation is determined between the amount of data received by each channel of each interface and the amount of data transmitted by each channel of the other interface. In the embodiment shown in Fig. 4, the correlation data is stored in one of the correlation matrices 46A-N (e.g., one for each interface pair). As shown in correlation matrix ~ 5 46A, the matrix includes several rows for interface B, and several columns for interface A. Each row represents one channel on interface B, and each column represents one channel on interface A. Thus. each row-column intersection can store a correlation factor that relates the amount of data traffic on the interface B channel represented by the corresponding row, with the amount of data traffic on the interface A channel represented by the corresponding column. The statistics 2o module 43 fills in the correlation matrix 46A with correlation factors derived from the traffic data stored in the traffic tables 45.
Once the correlation matrix 46A is populated, the results analyzer 44 evaluates the correlation factors to determine the channel of interface A and the channel of interface~B that are communicating via the frame relay connection determined in step 51, more specifically by ?5 inferring that a specific connection exists between highly correlated channels (step 54). Once the specific connection is inferred, the results analyzer 44 may update the virtual network machine l 7 to represent the connection (step 55).
Fig. 6 shows more detail of an implementation of step 52 of Fig. 5. In this implementation, the circuit tables of MIB 47 for each of the first and second interfaces are 3o queried to determine the value of a "frame in counter" and a value of a "frame out counter" for each active channel (step 61 ). As shown in Fig. 4, one example of a "frame in counter" is the MIB variable frCircuitSentOctets, and an example of a "frame out counter" is the MIB variable frCircuitReceivedOctets. These variables each count the total number of octets (8-bit bytes) transmitted or received by a specific channel for which the MIB is queried, including network overhead associated with transferring the data. However, other data may be used to determine the amount of traffic or other relevant statistics, for example a variable that tracks the total s number of frames transmitted or received, or a variable that tracks the total number of errors in transmitted or received data.
In step 62, the values of the "frame in counter'' and the "frame out counter"
are each stored, and a predetermined amount of time is allowed to pass. Once the predetermined amount of time has gassed, the circuit tables are again queried to determine a new value of each of the "frame in counter" and the "frame out counter." Examples of a predetermined amount of time are 30 seconds, or 50 seconds, although highly correlated data may be obtained with even less or significantly more time. The reason that two queries are performed in some embodiments is that the counters of the circuit table typically count the data from the last time that the interface device was initialized. Thus, if the two interface devices were initialized at different times, the 1 s difference between the values from the first query and the values from the second query will account for the different initialization times.
In step 64, each value from the first query (step 61 ) is subtracted from a corresponding value from the second query (step 63), to determine the amount of data communicated by each channel in the amount of time used as a delay in step 62. The resulting values may be stored in 2o traffic table 45A, an example of which is described in more detail below.
Fig. 7 shows more detail of an implementation of steps 53 and 54 of Fig. 5. In this implementation, for each potential channel pair, a correlation factor is calculated which represents the similarity of the amount of data transferred/received by one channel compared with the amount of data transferred/received by the other channel (step 71 ).
In one embodiment, 25 the correlation factor is calculated from the data transferred in both directions, as indicated in Equation ( 1 ):
(abs(Deltaln, - DeltaOut2) + abs(DeltaOut, - DeltaIn~)) * 100 {1) CF,_Z = 100 - .
3o DeltaIn, + DeltaOut, + DeltaIn~ + DeltaOut2 RECTIFIED SHEET (RULE 91) ISAIEP
WO 98144682 PCT/US98/053'70 where:
"abs" is an absolute value function;
DeltaOut; represents a value from column 87 of Fig. 8 or column 97 of Fig. 9;
and DeltaIn; represents a value fcom column 88 of Fig. 8 or column 98 of Fig. 9.
If the two channels for which the CF is calculated are connected, the absolute value of the difference between DeltaIn, and DeltaOut, and the absolute value of the difference between DeltaOut, and DeltaIn, would each ideally be zero, if the frame counters were accessed at precisely the same times. Thus, for ideal data transmission, the correlation factor CF would be equal to 100. However, it is likely that some differences will remain in these access times. The denominator of equation ( 1 ) accounts for the total amount of data transferred by the two channels; in this case. channel "1" and channel "2" for which the correlation factor "CF,_," is calculated. As indicated above, the correlation matrix 46 may then be populated with the correlation factor CF that is calculated for each potential channel pair (step 72).
~ 5 Once the correlation matrix has been populated, then the correlation factors may be compared with one another to determine the potential channel pair that has the highest level of correlation (step 73). Once this comparison is performed, the potential channel pair having the highest Level of correlation is selected as the specif c frame relay connection that exists between the first interface and the second interface (step 74).
2o Fig. 8 shows a specific example of a traffic table 80, which contains eight columns, each populated with data. Column 81 ("Iflndex") identifies the interface for which queries have been performed, in this case interface Ifs. Column 82 ("DLCI") identifies the channel number within the interface. In this example, there are three active channels within interface Ifs: channel 3I, channel 103, and channel 351.
25 Column 83 ("OutFrames-t0") stores the "frame out counter" value for each channel that resulted from the first query, while column 84 ("InFrames-t0") stores the "frame in counter"
value for each channel that resulted from the first query. Similarly, column 85 ("OutFrames-t i ") stores the "frame out counter" value for each channel that resulted from the second query, while column 86 ("InFrames-tl ") stores the "frame in counter" value for each channel that resulted 3o from the second query. From these values, the value for column 87 ("DeltaOut") may be determined by subtracting the value in column 83 from the value in column 85, for each channel.
Similarly. the value for column 88 ("Deltaln") can be determined by subtracting the value in _12_ column 84 from the value in column 86. for each channel. DeltaOut represents the amount of octets transmitted by the associated channel during the time interval between the two queries, while DeltaIn represents the number of octets received by the associated channel during this same time interval.
Fig. 9 is similar to Fig. 8, but represents an example of traffic data compiled for the channels 40 and 56 of interface If4. As in Fig. 8, column 91 identifies the interface, column 92 identifies the particular channel for which data has been gathered, columns 93 and 94 store the counter values from the first query, and columns 95 and 96 store the counter values from the second query. The values for columns 97 and 98 are then determined by subtraction from the to earlier columns.
Fig. 10 shows a specific example of a correlation matrix 100 that contains two columns, one for each of the channels of interface If4 shown in Fig. 2. The correlation matrix 100 further contains three rows, one for each of the channels of interface I~ shown in Fig. 2. The correlation factors have been calculated from equation ( 1 ) using the data from Figs. 8 and 9. For t 5 example, the correlation factor for the potential channel pair: channel 40 of interface If4, and channel 31 of interface Ifi7, has been determined as:
(abs(26,663 - 14.137) + abs(49,24G - 726)) * 100 (2) CF;~-.~~, = 100 - - 32 26,663 + 49,246 + 14,137 + 726 In this example, the highest correlation factor is for the channel pair of channel 56 of interface If4 and channel 31 of interface IfL7, since 99 is the highest correlation factor value in the correlation table 100. Therefore, in this example, the virtual network machine 17 would be 25 updated to represent that a specific frame relay connection exists between channel 31 and channel 56.
Generally, only a single connection will exist between any two interfaces. so the highest value of the correlation factor is selected. If two correlation factors are very close, however, this may be indicative of two specific channels. Such a situation may be resolved by determining the 30 amount of data throughput supported by each of the two suspected channels as compared with the amount of data actually being transmitted across the frame relay network.
Although Fig. 4 shows a particular implementation of elements within the network interface and control subsystem 40, those skilled in the art will realize that other implementations are within the scope of the invention. For example, instead of tables or matrices, the appropriate data may be stored in any number of ways, and the functions of the data gatherer 42, the statistics module 43. and the results analyzer 44 may be re-allocated to a different combination of modules.
The embodiments of the network management system described herein may also be implemented in specially-designed hardware such as a state machine or other digital circuitry, or in any of several programming languages on a general purpose computer, or as a programmed general purpose computer itself.
For example, elements of the network management system shown in Fig. 4 may be implemented as software on a floppy disk, compact disk, or hard drive, which controls a computer, for example a general purpose computer such as a workstation, a mainframe or a personal computer, to perform steps of the disclosed processes or to implement equivalents to the ~ 5 disclosed block diagrams. Such a general purpose computer typically includes a central processing unit (CPU) coupled to random access memory (RAM) and program memory via a data bus. The general purpose computer may be connected to the monitored networks in order to interface with other elements, and may provide commands to devices on the network in order to control the network configuration.
2o Alternatively, the elements of the embodiments described herein may be implemented as special purpose electronic hardware. Additionally, in either a hardware or software embodiment.
the functions performed by these different elements may be combined in varying arrangements of hardware and software.
For example, in at least one embodiment of the invention, the portions of the network 25 interface and control shown in Fig. 4 are supplied as a separate software package known as a "Management Module,'" which may be purchased and integrated with an existing instance of the Spectrum Network Management System.
Having thus described at least one illustrative embodiment of the invention.
various modifications and improvements will readily occur to those skilled in the art and are intended to 30 be within the scope of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting.
Yet another apparatus embodiment includes a data module and a results analyzer. The data module is coupled to a frame relay network and has an output that provides an indication of a first plurality of channels and a second plurality of channels that potentially relate to a frame relay connection. and the results analyzer selects a first channel from the first plurality of channels and a second channel from the second plurality of channels based upon a relative amount of data transferred on each of the first and second channels, in order to identify the frame relay connection.
~ 5 In any of these embodiments, a plurality of correlation factors may be determined, for example by a statistics module, for each potential pair of channels. The correlation factor having a best (e.g., highest) value may be used to determine which of the plurality of potential pairs of channels has the best (e.g., highest] correlation factor. A correlation factor may be related to a similarity between an amount of data transmitted by a first channel and an amount of data 3o received by a second channel during a period of time.
In any of these embodiments, a first interface device may be queried to determine an amount of data that has been transferred by one channel as of a first time.
and the first interface device queried again to determine an amount of data that has been transferred by the one channel as of a second time, wherein the amount of data being transferred is determined to be the 25 difference between these two amounts. A similar set of queries and difference determination may be made for a second interface of the potential pair.
In accordance with at least one embodiment, a determination may be made that a connection exists between an interface of a first interface device and an interface of a second interface device by comparing an address of the first interface with a destination address of data 3o transmitted by the second interface.
These and other features and benefits of the present invention will be more particularly described in the following detailed description.
' ~ ~ V 1 .
~f f . n . a 1 1 f 1 BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a schematic diagram of a network management system that interfaces with elements of a frame relay network;
Fig. 2 is a block diagram of two devices which each interface with a frame relay network, such as the one shown in Fig. 1;
Fig. 3 shows data which may be obtained from the two devices of Fig. 2, in accordance with at least one network protocol standard;
Fig. 4 is a block diagram of a network management system according to one embodiment of the invention, and a frame relay device which communicates therewith;
Fig. 5 is a process flow diagram showing steps of a process in accordance with an embodiment of the invention;
Fig. 6 is a flow diagram with greater detail of a portion of the process shown in Fig. 5;
Fig. 7 is a flow diagram with greater detail of another portion of the process shown in 1 s Fig. 5;
Fig. 8 is an example of a traffic table, for data such as that shown in Fig.
3, wherein the data relates to a first interface;
Fig. 9 is an example of a traffic table, for data that relates to a second interface; and Fig. 10 is an example of a correlation matrix for the data that is shown in Fig. 3.
DETAILED DESCRIPTION
Aspects of the present invention will be described in conjunction with the use of a model-based network management system, such as SpectrumTM, which is described in U.S.
Patent No. 5,261,044, issued November 9, 1993 to R. Dev et al. The SpectrumTM
network management system is commercially available and described in various user manuals and literature available from Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867.
Other commercially available network management systems and related applications include: HP OpenView, Hewlett Packard Corp., 3000 Hanover Street, Palo Alto, CA 94304;
3o LattisNet, Bay Networks, 4401 Great American Pkwy., Santa Clara, CA 95054;
IBM
Netview/6000, IBM Corp., Old Orchard Road, Armonk, N~ 10504; and SunNet l~Ianager, SunConnect, 2550 Garcia Ave, Mountain View, CA 94043. Embodiments of the invention 1T' . v~i~, flJc'J ShEi described herein may be applicable to such other network management systems or portion thereof.
Fig. 1 shows a network management system 10 that monitors a frame relay network 11 and other networks) 12. The other network{s) 12 may be other frame relay networks. or other types of networks, e.g., ethernet. token ring, FDDI, etc. The frame relay network 1 1 is illustrated as connecting three different sites 13 that communicate across the frame relay network - site A
(13A), site B (13B), and site C (13C). The network management system 10 monitors the~frame relay network 11 by communicating with devices within each of the sites 13A-C.
Each device within the sites 13A-C is referred to herein as an "interface device."
Fig. 1 shows one embodiment of the network management system 10, including a network interface and control subsystem 16. a virtual network machine 17, and a user interface 18. The virtual network machine 17 is coupled to both the network interface and control subsystem 16 and the user interface 18. The network interface and control subsystem 16 is coupled to each of the frame relay sites 13A-C by a corresponding one of communication paths t 5 14A-C, and is coupled to the other networks) 12 by communication path 15.
The communication paths 14A-C and 15 may be actual connections. or may represent a virtual access to data that relates to a particular site. For example, the network interface and control subsystem 16 may access a single data repository that stores data for all of the sites 13A-C, instead of directly accessing the interface devices on each site.
2o In one embodiment, the network management system 10 comprises a programmed digital computer, wherein a program is implemented using an object-oriented programming language such as C++, Eiffel, SmallTalk, and Ada. The virtual network machine 17 includes interrelated intelligent models (objects) of network entities and relations between network entities, including a capability for acquiring network data pertaining to a condition of a network entity from the 25 corresponding network entity, and for those entities not capable of being contacted. inferring their status from the status of other communicating entities. The virtual network machine 17 maintains objects which include network data relating to the corresponding network entity and one or more inference handlers for processing the network data. the inference handlers being responsive to changes occurring in the same and/oi a different object. The network data can then 3o be transferred to the user interface 18 for supplying the network data to a user.
The user interface 18 may be resident on a computer that is different from the computer on which subsystem 16 and virtual network machine 17 reside. In such an arrangement. the user interface 18 may be referred to as a client, while the network interface and control subsystem 1 G
and the virtual network machine 17 may be referred to as a server. Several instances of the user interface 18 may exist for a single instance of the virtual network machine 17, so that several users may concurrently view different aspects of the networks being monitored by the network management system 10.
In one embodiment of the invention. the network interface and control subsystem 16 obtains data relating to the frame relay network 11 in accordance with the Simple Network Management Protocol {SNMP). SNMP is a standard that defines common messages and databases to support network management. A group known as the Internet Engineering Task i o Force (IETF) has established several standards in accordance with the SNMP
framework, and in particular a standard known as a Management Information Base (MIB). The MIB
specifies the data items that certain devices must maintain. other data items that are proprietary or optional.
and the operations allowed on such devices. For example. the MIB specifies that Internet Protocol (IP) software must keep a count of all octets (8-bit bytes) that arrive over each network ~ 5 interface. Thus, a network management system is able to transmit a specific query (defined by the MIB} to a network interface device, and receive in response a message providing such count data stored within the network interface device's MIB. A document known as the IETF RFC
(Request for Comments) 1315 defines a portion of the MIB for use with managing frame relay protocols.
2o RFCs such as RFC-1315 are available in both printed and electronic form.
Printed copies may be obtained from Network Solutions, Inc., 505 tluntmar Park Drive, Herndon VA
22070. while electronic copies may be accessed on the Internet. In particular, an Internet user may use an "anonymous" FTP to the host ds.internic.net (residing at 129.20.239.132) and retrieve the desired files from the directory "rfc/".
25 Fig. 2 illustrates detail of two interface devices, site A router 21, and site B router 22, each of which is coupled to the frame relay network 11. Each of routers 21 and 22 may have several interfaces. In particular, site A router 21 has interfaces If7, If8.
and If9, while site B
muter 22 has interfaces Ifl. If2, If3, and If4: Each of these interfaces are coupled to the frame relay network 11.
3o In order for a network management system to effectively monitor and accurately represent the frame relay network 11, it is desirable to determine which interfaces share a connection within the frame relay network. If two devices are performing routing or bridging, _7_ then the network management system 10 can infer a connection between two of the interfaces by reading the route tables or transparent bridge tables (defined within the MIB) of the interface devices 21 and 22. In the example shown in Figs. 2 and 3. the interface devices 21 and 22 are routers that perform routing functions, and therefore the IP routing tables may be read by the network management system 10. Information relating to the IP routing tables is defined within the MIB, and is available from RFC documents such as MIB-II RFC-1213.
In particular, Fig. 3 shows muter information data 30 and routing table entries 31 for the site A router 21. The router information data 30 indicates that device 21 is a frame relay interface, and that information was requested pertaining to interface Ifs, which has an IP address of 13I .124.196. I . The router table information 31 shows that there are three groups of destination addresses (e.g., subnets) for messages to be sent from interface Ifs, two of which had a next hop IP address of I 31.124.196.3, and one of which had a next hop IP
address of 131.124. i 96.2.
Similarly, router information data 32 relates to the site B muter 22, and router table l s entries 33 contain information pertaining to interfaces If2 and If4 of the site B router 22. The muter table information 33 shows that there are three groups of destination addresses (e.g., subnets) for messages to be sent from interface If4 with a next hop IP address of 131.124.196.1.
Because messages are to be sent from interface I~ to interface If4 (as indicated by the next hop IP address 131.124.196.2 in table 31 matching the IP address of interface If4), a network management system can infer that a frame relay connection exists between interface Ift7 and interface If4. This conclusion is further supported by the evidence that messages are to be sent from interface If4 to interface Ifs, as indicated by several of the next hop IP addresses in router table entries 33 (from interface If4) matching the IP address of interface lf~
(131.124.196.1).
Thus, by determining the IP address of a message to be sent from an interface across a frame relay network, and then matching this IP address to the IP address of another interface on the frame relay network, a network management system can determine which two interfaces on a frame relay network share a connection. Similar results may be achieved by querying the transparent bridge tables if the two interface devices are performing bridge functions. The bridge 3o MIB is defined in RFC-1493.
However, each interface may have several "channels", each communicating across a different connection within the frame relay network 11. For example. Fig. 2 shows that interface _$_ Ifs has three channels 211, 212, and 2I3, interface If8 has two channels 2I4 and 215, interface If4 has two channels 221 and 222. interface If3 has one channel 223, and interface If2 has three channels 224, 225, and 226. Thus, even though it may be known which two interfaces share a connection within the frame relay network 1 l, it still may be uncertain which two channels of the two interfaces actually share the connection.
Fig. 4 is a block diagram showing operation of a system to determine the channels that share a frame relay connection. In particular, Fig. 4 depicts a network interface and control subsystem 40 which represents an embodiment of the network management and control subsystem 16 of Fig. 1. The subsystem 40 communicates with a frame relay interface device 41, t o which as described above, may be a muter, switch, network interface card.
or any device that communicates across a frame relay network (not shown in Fig. 4). The network interface and control subsystem 40 includes a data gatherer 42, a statistics module 43, and a results analyzer 44. Traffic tables 45A, 45B, ... 45N are coupled between the data gatherer 42 and the statistics module 43, and correlation matrices 46A, 46B, ..., 46N are coupled between the statistics module ~ 5 43 and the results analyzer 44.
The results analyzer 44 is the portion of the network interface and control module that provides input to the virtual network machine. and the data gatherer 42 interfaces with the interface device 41. As described above, associated with the interface device 41 is a MIB 47. A
portion of the MIB 47 is the frame relay circuit table (frCircuitTable) 48, as defined in RFC-20 1315. The data gatherer 42 communicates with the interface device 41 in the form of queries 49 which request information from the MiB 47, and in response the MIB 47 provides a count of octets sent by a particular channel of an interface of the interface device (frCircuitSent Octets), and a count of octets received by a particular channel of an interface of the interface device (frCircuitReceivedOctets), generally shown as 50 in Fig. 4.
25 Fig. 5 is a high level process flow diagram of operations performed by an embodiment of the network interface and control subsystem 40. In step 51, the data gatherer 42 determines that a frame relay connection exists between a first interface and a second interface (e.g., interface If~
of site A router 21 and interface If4 of site B muter 22). As discussed above, this determination may be made by analyzing the next hop address within a routing table, or by other methods 3o known to those skilled in the art.
In step 52, the data gatherer 42 determines an amount of data that is communicated in each direction by each channel of the first and second interfaces. This step may include _g_ determining which channels are actually active (which may also be determined by querying the MIB 47}, in which case any channels~that are not active may be eliminated from consideration.
Additionally, it is not necessary to determine the amount of data in both directions, although such analysis may result in a more complete solution as described in more detail below.
s In one embodiment, the data gatherer 42 stores the data amounts in the appropriate traffic table 45. One of the traffic tables 45A may be for the analysis of a first interface, while another of the traffic tables 45B may be for the analysis of a second interface.
Once the amount of data has been determined, the statistics module 43 determines the level of correlation between data on each potential channel pair. A potential channel pair is made up of one channel from each interface for which a connection is known to exist. In particular, step 53 indicates that the level of correlation is determined between the amount of data received by each channel of each interface and the amount of data transmitted by each channel of the other interface. In the embodiment shown in Fig. 4, the correlation data is stored in one of the correlation matrices 46A-N (e.g., one for each interface pair). As shown in correlation matrix ~ 5 46A, the matrix includes several rows for interface B, and several columns for interface A. Each row represents one channel on interface B, and each column represents one channel on interface A. Thus. each row-column intersection can store a correlation factor that relates the amount of data traffic on the interface B channel represented by the corresponding row, with the amount of data traffic on the interface A channel represented by the corresponding column. The statistics 2o module 43 fills in the correlation matrix 46A with correlation factors derived from the traffic data stored in the traffic tables 45.
Once the correlation matrix 46A is populated, the results analyzer 44 evaluates the correlation factors to determine the channel of interface A and the channel of interface~B that are communicating via the frame relay connection determined in step 51, more specifically by ?5 inferring that a specific connection exists between highly correlated channels (step 54). Once the specific connection is inferred, the results analyzer 44 may update the virtual network machine l 7 to represent the connection (step 55).
Fig. 6 shows more detail of an implementation of step 52 of Fig. 5. In this implementation, the circuit tables of MIB 47 for each of the first and second interfaces are 3o queried to determine the value of a "frame in counter" and a value of a "frame out counter" for each active channel (step 61 ). As shown in Fig. 4, one example of a "frame in counter" is the MIB variable frCircuitSentOctets, and an example of a "frame out counter" is the MIB variable frCircuitReceivedOctets. These variables each count the total number of octets (8-bit bytes) transmitted or received by a specific channel for which the MIB is queried, including network overhead associated with transferring the data. However, other data may be used to determine the amount of traffic or other relevant statistics, for example a variable that tracks the total s number of frames transmitted or received, or a variable that tracks the total number of errors in transmitted or received data.
In step 62, the values of the "frame in counter'' and the "frame out counter"
are each stored, and a predetermined amount of time is allowed to pass. Once the predetermined amount of time has gassed, the circuit tables are again queried to determine a new value of each of the "frame in counter" and the "frame out counter." Examples of a predetermined amount of time are 30 seconds, or 50 seconds, although highly correlated data may be obtained with even less or significantly more time. The reason that two queries are performed in some embodiments is that the counters of the circuit table typically count the data from the last time that the interface device was initialized. Thus, if the two interface devices were initialized at different times, the 1 s difference between the values from the first query and the values from the second query will account for the different initialization times.
In step 64, each value from the first query (step 61 ) is subtracted from a corresponding value from the second query (step 63), to determine the amount of data communicated by each channel in the amount of time used as a delay in step 62. The resulting values may be stored in 2o traffic table 45A, an example of which is described in more detail below.
Fig. 7 shows more detail of an implementation of steps 53 and 54 of Fig. 5. In this implementation, for each potential channel pair, a correlation factor is calculated which represents the similarity of the amount of data transferred/received by one channel compared with the amount of data transferred/received by the other channel (step 71 ).
In one embodiment, 25 the correlation factor is calculated from the data transferred in both directions, as indicated in Equation ( 1 ):
(abs(Deltaln, - DeltaOut2) + abs(DeltaOut, - DeltaIn~)) * 100 {1) CF,_Z = 100 - .
3o DeltaIn, + DeltaOut, + DeltaIn~ + DeltaOut2 RECTIFIED SHEET (RULE 91) ISAIEP
WO 98144682 PCT/US98/053'70 where:
"abs" is an absolute value function;
DeltaOut; represents a value from column 87 of Fig. 8 or column 97 of Fig. 9;
and DeltaIn; represents a value fcom column 88 of Fig. 8 or column 98 of Fig. 9.
If the two channels for which the CF is calculated are connected, the absolute value of the difference between DeltaIn, and DeltaOut, and the absolute value of the difference between DeltaOut, and DeltaIn, would each ideally be zero, if the frame counters were accessed at precisely the same times. Thus, for ideal data transmission, the correlation factor CF would be equal to 100. However, it is likely that some differences will remain in these access times. The denominator of equation ( 1 ) accounts for the total amount of data transferred by the two channels; in this case. channel "1" and channel "2" for which the correlation factor "CF,_," is calculated. As indicated above, the correlation matrix 46 may then be populated with the correlation factor CF that is calculated for each potential channel pair (step 72).
~ 5 Once the correlation matrix has been populated, then the correlation factors may be compared with one another to determine the potential channel pair that has the highest level of correlation (step 73). Once this comparison is performed, the potential channel pair having the highest Level of correlation is selected as the specif c frame relay connection that exists between the first interface and the second interface (step 74).
2o Fig. 8 shows a specific example of a traffic table 80, which contains eight columns, each populated with data. Column 81 ("Iflndex") identifies the interface for which queries have been performed, in this case interface Ifs. Column 82 ("DLCI") identifies the channel number within the interface. In this example, there are three active channels within interface Ifs: channel 3I, channel 103, and channel 351.
25 Column 83 ("OutFrames-t0") stores the "frame out counter" value for each channel that resulted from the first query, while column 84 ("InFrames-t0") stores the "frame in counter"
value for each channel that resulted from the first query. Similarly, column 85 ("OutFrames-t i ") stores the "frame out counter" value for each channel that resulted from the second query, while column 86 ("InFrames-tl ") stores the "frame in counter" value for each channel that resulted 3o from the second query. From these values, the value for column 87 ("DeltaOut") may be determined by subtracting the value in column 83 from the value in column 85, for each channel.
Similarly. the value for column 88 ("Deltaln") can be determined by subtracting the value in _12_ column 84 from the value in column 86. for each channel. DeltaOut represents the amount of octets transmitted by the associated channel during the time interval between the two queries, while DeltaIn represents the number of octets received by the associated channel during this same time interval.
Fig. 9 is similar to Fig. 8, but represents an example of traffic data compiled for the channels 40 and 56 of interface If4. As in Fig. 8, column 91 identifies the interface, column 92 identifies the particular channel for which data has been gathered, columns 93 and 94 store the counter values from the first query, and columns 95 and 96 store the counter values from the second query. The values for columns 97 and 98 are then determined by subtraction from the to earlier columns.
Fig. 10 shows a specific example of a correlation matrix 100 that contains two columns, one for each of the channels of interface If4 shown in Fig. 2. The correlation matrix 100 further contains three rows, one for each of the channels of interface I~ shown in Fig. 2. The correlation factors have been calculated from equation ( 1 ) using the data from Figs. 8 and 9. For t 5 example, the correlation factor for the potential channel pair: channel 40 of interface If4, and channel 31 of interface Ifi7, has been determined as:
(abs(26,663 - 14.137) + abs(49,24G - 726)) * 100 (2) CF;~-.~~, = 100 - - 32 26,663 + 49,246 + 14,137 + 726 In this example, the highest correlation factor is for the channel pair of channel 56 of interface If4 and channel 31 of interface IfL7, since 99 is the highest correlation factor value in the correlation table 100. Therefore, in this example, the virtual network machine 17 would be 25 updated to represent that a specific frame relay connection exists between channel 31 and channel 56.
Generally, only a single connection will exist between any two interfaces. so the highest value of the correlation factor is selected. If two correlation factors are very close, however, this may be indicative of two specific channels. Such a situation may be resolved by determining the 30 amount of data throughput supported by each of the two suspected channels as compared with the amount of data actually being transmitted across the frame relay network.
Although Fig. 4 shows a particular implementation of elements within the network interface and control subsystem 40, those skilled in the art will realize that other implementations are within the scope of the invention. For example, instead of tables or matrices, the appropriate data may be stored in any number of ways, and the functions of the data gatherer 42, the statistics module 43. and the results analyzer 44 may be re-allocated to a different combination of modules.
The embodiments of the network management system described herein may also be implemented in specially-designed hardware such as a state machine or other digital circuitry, or in any of several programming languages on a general purpose computer, or as a programmed general purpose computer itself.
For example, elements of the network management system shown in Fig. 4 may be implemented as software on a floppy disk, compact disk, or hard drive, which controls a computer, for example a general purpose computer such as a workstation, a mainframe or a personal computer, to perform steps of the disclosed processes or to implement equivalents to the ~ 5 disclosed block diagrams. Such a general purpose computer typically includes a central processing unit (CPU) coupled to random access memory (RAM) and program memory via a data bus. The general purpose computer may be connected to the monitored networks in order to interface with other elements, and may provide commands to devices on the network in order to control the network configuration.
2o Alternatively, the elements of the embodiments described herein may be implemented as special purpose electronic hardware. Additionally, in either a hardware or software embodiment.
the functions performed by these different elements may be combined in varying arrangements of hardware and software.
For example, in at least one embodiment of the invention, the portions of the network 25 interface and control shown in Fig. 4 are supplied as a separate software package known as a "Management Module,'" which may be purchased and integrated with an existing instance of the Spectrum Network Management System.
Having thus described at least one illustrative embodiment of the invention.
various modifications and improvements will readily occur to those skilled in the art and are intended to 30 be within the scope of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting.
Claims (24)
- A method for identifying a frame relay connection in a network, the method comprising the steps of:
identifying a first plurality of channels (211-215) of a first interface (21) and a second plurality of channels (221-226) of a second interface (22) that relate to a frame relay connection between the first and second interfaces; and selecting, as an identifier of the frame relay connection, a first channel from the first plurality of channels and a second channel from the second plurality of channels based upon a relative amount of data transferred on each of the first and second channels. - 2. The method of claim 1, wherein the selecting step includes:
identifying a plurality of different potential pairs of channels, each potential pair including one of the first plurality of channels (211-215) and one of the second plurality of channels (221-220);
determining a plurality of correlation factors (46A-46N), each correlation factor relating to a respective one of the potential pairs of channels; and determining which of the correlation factors (46A-46N) has a best value with respect to others of the correlation factors, in order to determine which of the potential pairs of channels has a best correlation factor. - 3. The method of claim 2, wherein the step of determining a correlation factor includes determining an amount of similarity between an amount of data transmitted by the one of the first plurality of channels (211-215) and an amount of data received by the one of the second plurality of channels (221-226) during a period of time.
- 4. The method of claim 3, wherein the step of determining a correlation factor further includes determining an amount of similarity between an amount of data received by the one of the first plurality of channels (211-215) and an amount of data transmitted by the one of the second plurality of channels (221-226) during the period of time.
- 5. The method of claim 1, including the step of determining an amount of data transferred by each of the first plurality of channels (211-215) and each of the second plurality of channels (221-225); and wherein the step of selecting includes determining the relative amount of data based upon the amount of data transferred by each of the first plurality of channels (211-215)and each of the second plurality of channels (221-226).
- 6. The method of claim 5, wherein the step of determining, for one channel of the first plurality of channels that resides on a first interface device of the frame relay network, includes:
querying the first interface device (41) to determine a first amount of data that has been transferred on the one channel as of a first time;
querying the first interface devices (41) to determine a second amount of data that has been transferred on the one channel as of a second time; and determining a difference between the first and second amounts of data in order to determine the amount of data being transferred by the one channel. - 7. The method of claim 1, wherein the step of identifying includes determining that a connection exists between an interface of a first interface device (21) that is coupled to the frame relay network (11), and an interface of a second interface device (22) that is coupled to the frame relay network;
wherein the interface of the first interface device includes the first plurality of channels (211-215), and the interface of the second interface device includes the second plurality of channels (221-226). - 8. The method of claim 7, wherein the step of determining includes comparing an address of the first interface with a destination address of data transmitted by the second interface.
- 9. An apparatus for identifying a frame relay connection in a network, the apparatus comprising:
means for identifying a first plurality of channels (211-215) of a first interface (21) and a second plurality of channels (221-226) of a second interface (22) that relate to a potential frame relay connection between the first and second interfaces;
and means for selecting a first channel from the first plurality of channels (211-215) and a second channel from the second plurality of channels (221-226) based upon a relative amount of data transferred on each of the first and second channels, to identify the frame relay connection. - 10. The apparatus of claim 9, wherein the means for selecting includes:
means for identifying a plurality of different potential pairs of channels, each potential pair including one of the first plurality of channels (211-215) and one of the second plurality of channels (221-226);
means for determining a plurality of correlation factors, each correlation factor relating to a respective one of the potential pairs of channels; and means for determining which of the correlation factors has a best value with respect to others of the correlation factors, in order to determine which of the potential pairs of channels has a best correlation factor. - 11. The apparatus of claim 10, wherein the means for determining a correlation factor includes means for determining an amount of similarity between an amount of data transmitted by the one of the first plurality of channels and an amount of data received by the one of the second plurality of channels during a period of time.
- 12. The apparatus of claim 11, wherein the means for determining a correlation factor further includes means for determining an amount of similarity between an amount of data received by the one of the first plurality of channels (211-215) and an amount of data transmitted by the one of the second plurality of channels (221-226) during the period of time.
- 13. The apparatus of claim 9, including means for determining an amount of data transferred by each of the first plurality of channels (211-215) and each of the second plurality of channels (221-226);
wherein the means for selecting includes means for determining the relative amount of data based upon the amount of data transferred by each of the first plurality of channels and each of the second plurality of channels. - 14. The apparatus of claim 13, wherein the means for determining, for one channel of the first plurality of channels that resides on a first interface device of the frame relay network, includes:
means for querying the first interface device to determine a first amount of data that has been transferred on the one channel (45) as of a first time;
means for querying the first interface devices to determine a second amount of data that has been transferred on the one channel (45) as of a second time;
and means for determining a difference between the first and second amounts of data in order to determine the amount of data being transferred by the one channel. - 15. The apparatus of claim 9, wherein the means for identifying includes means for determining that a connection exists between an interface of a first interface device that is coupled to the frame relay network, and an interface of a second interface device that is coupled to the frame relay network;
wherein the interface of the first interface device (21) includes the first plurality of channels (211-215), and the interface of the second interface device (22) includes the second plurality of channels (221-226). - 16. The apparatus of claim 15, wherein the means for determining includes means for comparing an address of the first interface with a destination address of data transmitted by the second interface.
- 17. An apparatus for identifying a frame relay connection in a network, the apparatus comprising:
a data module (42, 45A-45N), coupled to the network, having an output that provides an indication of a first plurality of channels (211-215) and a second plurality of channels (221-226) that relate to a potential frame relay connection; and a results analyzer (44), having an input coupled to the output of the data module, the results analyzer selecting a first channel from the first plurality of channels (211-215) and a second channel from the second plurality of channels (221-226) based upon a relative amount of data transferred by each of the first and second channels, to identify the frame relay connection. - 18. The apparatus of claim 17, wherein the indication of the first plurality of channels (211-215) and the second plurality of channels (221-226) includes a plurality of different potential pairs of channels, each of the potential pairs including one of the first plurality of channels (211-215) and one of the second plurality of channels (221-226).
- 19. The apparatus of claim 18, further comprising a statistics module (43), coupled between the output of the data module (42, 45A-45N) and the input of the results analyzer (44), the statistics module (43) determining a plurality of correlation factors, each correlation factor relating to a respective one of the potential pairs of channels.
- 20. The apparatus of claim 19, wherein the results analyzer determines which of the plurality of correlation factors has a best value with respect to others of the plurality of correlation factors, to determine which of the plurality of potential pairs of channels has a best correlation factor.
- 21. The apparatus of claim 19, wherein the statistics module (43, 46A-46N) determines a correlation factor between one of the first plurality of channels (211-215) and one of the second plurality of channels (221-226), the correlation factor being proportional to an amount of similarity between an amount of data transmitted by the one of the first plurality of channels and an amount of data received by the one of the second plurality of channels during a period of time.
- 22. The apparatus of claim 21, wherein the correlation factor is further proportional to an amount of similarity between an amount of data received by the one of the first plurality of channels (211-215) and an amount of data transmitted by the one of the second plurality of channels (221-226) during the period of time.
- 23. The apparatus of claim 17, wherein the data module determines an amount of data transferred by each of the first plurality of channels and each of the second plurality of channels;
the apparatus further comprising a statistics module (43, 46A-46N), coupled between the data module (42, 45A-45N) and the results analyzer (44), the statistics module (41, 46A-46N) determining the relative amount of data based upon the amount of data transferred by each of the first plurality of channels and each of the second plurality of channels. - 24. The apparatus of claim 23, wherein the data module determines the amount of data being transferred by one channel of the first plurality of channels (211-215) based upon a difference between an amount of data that has been transferred by the one channel as of a first time, and an amount of data that has been transferred by the one channel as of a second time.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/827,541 US6115362A (en) | 1997-03-28 | 1997-03-28 | Method and apparatus for determining frame relay connections |
| US08/827,541 | 1997-03-28 | ||
| PCT/US1998/005370 WO1998044682A1 (en) | 1997-03-28 | 1998-03-18 | Method and apparatus for determining frame relay connections |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2284995A1 CA2284995A1 (en) | 1998-10-08 |
| CA2284995C true CA2284995C (en) | 2002-12-31 |
Family
ID=25249485
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002284995A Expired - Fee Related CA2284995C (en) | 1997-03-28 | 1998-03-18 | Method and apparatus for determining frame relay connections |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US6115362A (en) |
| EP (1) | EP0972377A1 (en) |
| AU (1) | AU715918B2 (en) |
| CA (1) | CA2284995C (en) |
| WO (1) | WO1998044682A1 (en) |
Families Citing this family (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11184649A (en) * | 1997-07-25 | 1999-07-09 | Seiko Epson Corp | System and method for printing, and printer |
| US6751226B1 (en) * | 1998-11-25 | 2004-06-15 | Qwest Communications Int'l., Inc. | System and method for providing managed frame relay service |
| US6539540B1 (en) * | 1999-05-24 | 2003-03-25 | 3Com Corporation | Methods and apparatus for optimizing simple network management protocol (SNMP) requests |
| IL130415A (en) * | 1999-06-10 | 2003-07-31 | Eci Telecom Ltd | Method of defining threshold crossing alert profiles for network element performance monitoring |
| US6694362B1 (en) | 2000-01-03 | 2004-02-17 | Micromuse Inc. | Method and system for network event impact analysis and correlation with network administrators, management policies and procedures |
| US7126964B1 (en) * | 2000-02-11 | 2006-10-24 | Microsoft Corporation | Method and apparatus for network analysis, such as analyzing and correlating identifiers of frame relay circuits in a network |
| DE10014462B4 (en) * | 2000-03-23 | 2011-12-08 | Deutsche Telekom Ag | Method and monitoring system for monitoring at least one subscriber line |
| US7752024B2 (en) * | 2000-05-05 | 2010-07-06 | Computer Associates Think, Inc. | Systems and methods for constructing multi-layer topological models of computer networks |
| US7237138B2 (en) * | 2000-05-05 | 2007-06-26 | Computer Associates Think, Inc. | Systems and methods for diagnosing faults in computer networks |
| US7500143B2 (en) * | 2000-05-05 | 2009-03-03 | Computer Associates Think, Inc. | Systems and methods for managing and analyzing faults in computer networks |
| WO2001086775A1 (en) * | 2000-05-05 | 2001-11-15 | Aprisma Management Technologies, Inc. | Help desk systems and methods for use with communications networks |
| WO2001086380A2 (en) * | 2000-05-05 | 2001-11-15 | Aprisma Management Technologies, Inc. | Systems and methods for isolating faults in computer networks |
| US6895440B1 (en) * | 2000-05-25 | 2005-05-17 | Cisco Technology, Inc. | Network component performance testing |
| US6744739B2 (en) | 2001-05-18 | 2004-06-01 | Micromuse Inc. | Method and system for determining network characteristics using routing protocols |
| US7043727B2 (en) | 2001-06-08 | 2006-05-09 | Micromuse Ltd. | Method and system for efficient distribution of network event data |
| US7426553B1 (en) * | 2001-08-02 | 2008-09-16 | At&T Intellectual Property I, L.P. | Provisioning data link connection identifiers in a communications network |
| CN1208980C (en) * | 2001-10-17 | 2005-06-29 | 诺基亚公司 | Informing network about amount of data to be transferred |
| US7363368B2 (en) | 2001-12-24 | 2008-04-22 | International Business Machines Corporation | System and method for transaction recording and playback |
| US6862698B1 (en) * | 2002-01-22 | 2005-03-01 | Cisco Technology, Inc. | Method of labeling alarms to facilitate correlating alarms in a telecommunications network |
| US6744774B2 (en) * | 2002-06-27 | 2004-06-01 | Nokia, Inc. | Dynamic routing over secure networks |
| US7180865B1 (en) * | 2002-06-28 | 2007-02-20 | Bellsouth Intellectual Property Corporation | System and method for analyzing frame relay communications |
| US7200148B1 (en) * | 2002-06-28 | 2007-04-03 | Bellsouth Intellectual Property Corp. | System and method for analyzing asynchronous transfer mode communications |
| US7391739B1 (en) | 2002-06-28 | 2008-06-24 | At&T Delaware Intellectual Property, Inc. | System and method for creating a frame relay port mirror |
| US7636320B1 (en) * | 2002-06-28 | 2009-12-22 | At&T Intellectual Property I, L.P. | System and method for creating an asynchronous transfer mode port mirror |
| US7535910B2 (en) * | 2002-12-13 | 2009-05-19 | At&T Intellectual Property I, L.P. | Method and system for obtaining a permanent virtual circuit map |
| US7869349B2 (en) * | 2008-10-14 | 2011-01-11 | International Business Machines Corporation | Method and system for deducing network routes by querying routers |
| US9185018B2 (en) * | 2010-10-22 | 2015-11-10 | Brocade Communications Systems, Inc. | Path diagnosis in communication networks |
Family Cites Families (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5185860A (en) * | 1990-05-03 | 1993-02-09 | Hewlett-Packard Company | Automatic discovery of network elements |
| EP0474189A3 (en) * | 1990-09-04 | 1996-09-18 | Fujitsu Ltd | Isdn line circuit monitor system |
| US5261044A (en) * | 1990-09-17 | 1993-11-09 | Cabletron Systems, Inc. | Network management system using multifunction icons for information display |
| US5751933A (en) * | 1990-09-17 | 1998-05-12 | Dev; Roger H. | System for determining the status of an entity in a computer network |
| WO1992006547A1 (en) * | 1990-09-28 | 1992-04-16 | Hewlett-Packard Company | Method of ascertaining topology features of a network |
| EP0477448B1 (en) * | 1990-09-28 | 1995-07-12 | Hewlett-Packard Company | Network monitoring device and system |
| US5323389A (en) * | 1992-08-14 | 1994-06-21 | Fore Systems, Inc. | ATM cell interface and method for dispatching an ATM cell |
| US5408469A (en) * | 1993-07-22 | 1995-04-18 | Synoptics Communications, Inc. | Routing device utilizing an ATM switch as a multi-channel backplane in a communication network |
| AU675362B2 (en) * | 1993-09-01 | 1997-01-30 | Cabletron Systems, Inc. | Determination of network topology |
| JP2561022B2 (en) * | 1994-05-25 | 1996-12-04 | 日本電気株式会社 | Transmission channel selection system by destination address |
| JPH0897820A (en) * | 1994-09-29 | 1996-04-12 | Hitachi Ltd | Upc circuit and performance monitoring cell processing circuit |
| US5872928A (en) * | 1995-02-24 | 1999-02-16 | Cabletron Systems, Inc. | Method and apparatus for defining and enforcing policies for configuration management in communications networks |
| US5898674A (en) * | 1995-11-14 | 1999-04-27 | Paradyne Corporation | System and method for performing non-disruptive diagnostics through a frame relay circuit |
| US5684800A (en) * | 1995-11-15 | 1997-11-04 | Cabletron Systems, Inc. | Method for establishing restricted broadcast groups in a switched network |
| US5710885A (en) * | 1995-11-28 | 1998-01-20 | Ncr Corporation | Network management system with improved node discovery and monitoring |
| US5751965A (en) * | 1996-03-21 | 1998-05-12 | Cabletron System, Inc. | Network connection status monitor and display |
| US5809286A (en) * | 1996-05-01 | 1998-09-15 | Mci Communications Corporation | Method and apparatus for emulating a dynamically configured digital cross-connect switch network |
| US5768501A (en) * | 1996-05-28 | 1998-06-16 | Cabletron Systems | Method and apparatus for inter-domain alarm correlation |
| US5867483A (en) * | 1996-11-12 | 1999-02-02 | Visual Networks, Inc. | Method and apparatus for measurement of peak throughput in packetized data networks |
-
1997
- 1997-03-28 US US08/827,541 patent/US6115362A/en not_active Expired - Lifetime
-
1998
- 1998-03-18 CA CA002284995A patent/CA2284995C/en not_active Expired - Fee Related
- 1998-03-18 EP EP98911806A patent/EP0972377A1/en not_active Withdrawn
- 1998-03-18 WO PCT/US1998/005370 patent/WO1998044682A1/en not_active Application Discontinuation
- 1998-03-18 AU AU65676/98A patent/AU715918B2/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| CA2284995A1 (en) | 1998-10-08 |
| AU715918B2 (en) | 2000-02-10 |
| EP0972377A1 (en) | 2000-01-19 |
| WO1998044682A1 (en) | 1998-10-08 |
| AU6567698A (en) | 1998-10-22 |
| US6115362A (en) | 2000-09-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2284995C (en) | Method and apparatus for determining frame relay connections | |
| US6405248B1 (en) | Method and apparatus for determining accurate topology features of a network | |
| US6321264B1 (en) | Network-performance statistics using end-node computer systems | |
| US6415314B1 (en) | Distributed chassis agent for network management | |
| US7007104B1 (en) | Method and apparatus for integrated network management and systems management in communications networks | |
| Meyer et al. | Decentralizing control and intelligence in network management | |
| EP0849909B1 (en) | Communications network monitoring | |
| US5978845A (en) | Network management relay mechanism | |
| US7076688B2 (en) | Failure information management method and management server in a network equipped with a storage device | |
| US5768501A (en) | Method and apparatus for inter-domain alarm correlation | |
| US20050025071A1 (en) | Network management system having a network including virtual networks | |
| US7120678B2 (en) | Method and apparatus for configurable data collection on a computer network | |
| JP2000209201A (en) | Method and system for network management | |
| US20040186903A1 (en) | Remote support of an IT infrastructure | |
| JPH10200529A (en) | Monitoring method and device for communication network | |
| US20030145069A1 (en) | Virtual network configuration verification | |
| CA2221527A1 (en) | Communications network monitoring | |
| KR20010083904A (en) | Management of path selection in a communications network | |
| KR20010080170A (en) | Management of terminations in a communications network | |
| US8572235B1 (en) | Method and system for monitoring a complex IT infrastructure at the service level | |
| KR100507801B1 (en) | Method for managing interface of distributed router and apparatus thereof | |
| Siegel | EFFICIENT NETWORK MIANAGEMENT FOR A HIGHLY DISTRIEUTED) SYSTEMI | |
| Wessels | Developing a generic network planning interface | |
| JP2004260245A (en) | Method, apparatus, and program for generating service path information | |
| AU1253600A (en) | Management of terminations in a communications network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |