Determining a path through a managed network

Details Determining a path through a managed network Determining a path through a managed network

1999-11-12

2003-06-10

Vu, Viet D. (Department: 2154)

Electrical computers and digital processing systems: multicomput

Computer-to-computer data routing

Routing data updating

C709S220000, C709S249000, C370S238000, C370S401000

Reexamination Certificate

active

06578087

ABSTRACT:

FIELD OF THE INVENTION
The present invention generally relates to management of computer networks, and relates more specifically to determining a path through a managed network.
BACKGROUND OF THE INVENTION
A computer network generally includes a number of devices, including switches, routers and hubs, connected so as to allow communication among the devices. The devices within a network are often categorized into two classes: end stations such as workstations, desktop PCs, printers, servers, hosts, fax machines, and devices that primarily supply or consume information; and intermediate network devices such as gateways, switches and routers that primarily forward information between the other devices. A network management station may be used to monitor and manage the network. Typically, the network management station is a workstation that runs a network management software program. An example of a network management software program is CiscoWorks 2000, commercially available from Cisco Systems, Inc.
Sometimes, the configuration of the network or an error in the network can prevent information from being forwarded correctly. For example, an end-station such as a desktop PC may send data to a specified printer in the computer network but the data does not reach the specified printer due to the configuration of the network or an error in the network or because the printer does not support the same network protocol as that of the desktop PC. In order to determine the problem in the network, tools and techniques are needed to gather information about errors and configuration. One technique of gathering information about computer networks that use Internet Protocol is path tracing (“IP path tracing”). IP path tracing involves tracing the path that a packet would take starting at a source end-station, such as the desktop PC, to reach its destination such as the printer.
An example of a tool for IP path tracing is the “traceroute” software program that is supported by UNIX-based network computers. Windows-based network computers support a similar software program called “tracert”. Both traceroute and tracert record the path or route comprising specific gateway computers or routers at each “hop” through the computer network between a source computer and the destination computer. In a packet-switching network, a hop is the next intermediate gateway that a packet visits on its way to its destination. The traceroute program works by sending a small packet of data using Internet Control Message Protocol to the destination end-station. The packet includes a time limit value known as “time to live” that is designed to be exceeded by the first gateway that receives the packet. In turn, the gateway returns a Time Exceeded message. The traceroute program increases the time limit value and resends the packet so that it will reach the next gateway in the path to the packet's destination.
However, while many routers and network management stations support either the source-routed traceroute or source-routed tracert program, most end-stations do not. Examples of devices that neither support source-routed tracert nor source-routed traceroute are most end-stations and IP telephony equipment. IP telephony devices are devices that use Internet Protocol packet-switched connections to exchange voice, fax, and other information that have traditionally been carried over dedicated circuit-switched connections of the public switched telephone network. For those end-stations that do not support source-routed traceroute or source-routed tracert programs and are located remotely from the network management stations, IP path tracing is done by performing a direct tracert from the end-station to the packet's destination. Performing a direct tracert from the end-station is usually inconvenient for a network manager who is remotely located from the end-station.
To illustrate, consider the following scenario. Susan, in the accounting department of ACME Company, would like to print a document on printer (“D”) from her desktop personal computer (“S”) but is unable to do so because S and D are not connected to the same network or are configured improperly. The computer network management department of ACME uses a Network Management Station (“N”) in an attempt to find the error. Assume that N is at a location remote from S and D. Further assume that S does not support the tracert program. In order for N to find the error in connectivity between S and D, N needs to perform IP path tracing between S and D using a source-routed tracert even if S does not support the source-routed tracert.
Based on the foregoing, there is a clear need for a mechanism allowing management of computer networks to determine a network path from a first device to a second device without relying on existing path tracing approaches.
In particular, there is a need for a method and mechanism that provides IP path tracing in a managed network using either source-routed traceroute or source-routed tracert program even though the source devices in the managed network neither support the source-routed traceroute nor the source-routed tracert program.
SUMMARY OF THE INVENTION
The foregoing needs, and other needs and objects that will become apparent for the following description, are achieved in the present invention, which comprises, in one aspect, a method for determining a path of a data packet in a managed network. In an embodiment, the method involves determining that a first subnet associated with a source node and a second subnet associated with a destination node are different subnets; determining a first gateway used by the source node to reach a network management node; determining a second gateway based on the first gateway and the destination node; determining whether the first subnet associated with the source node and a third subnet associated with the second gateway are identical subnets; and using the second gateway as a first hop from the source node to the destination node when the first subnet associated with the source node and the third subnet associated with the second gateway are identical.
One feature of this aspect is determining that the destination node is one hop away when the first subnet associated with the source node and the second subnet associated with the destination node are identical. According to another feature, the first gateway is used as the first hop from the source node to the destination node when the first subnet associated with the source node and the third subnet associated with the second gateway are not identical subnets.
In another feature, determining that the first subnet and second subnet are different subnets further involves determining a subnet mask associated with the source node; performing a Bitwise AND operation on the subnet mask and a first IP address associated with the source node to produce a first result; performing the Bitwise AND operation on the subnet mask and a second IP address associated with the destination node to produce a second result; and determining that the first subnet and the second subnet are different subnets when the first result is different from the second result.
In another feature, determining a subnet mask associated with the source node further involves determining a router that has an interface on the first subnet; and determining the subnet mask associated with the source node from a routing table of the router that has the interface on the first subnet. According to still another feature, determining a router further involves performing an IP path tracing operation from the network management node to the source node.
In another feature, the method further involves performing a PING operation with a record route option from the network management node to the source node. Also, performing an IP path tracing operation from the network management node to the source node further involves using a source-routed traceroute computer program to trace the IP path from the network management node to the source node. In another feature, determining the subnet mask

Affiliated with

Also associated with

Rating

Determining a path through a managed network does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Determining a path through a managed network, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Determining a path through a managed network will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-3149038