CA2061687C - Determining physical topology across repeaters and bridges in a computer network - Google Patents
Determining physical topology across repeaters and bridges in a computer network Download PDFInfo
- Publication number
- CA2061687C CA2061687C CA002061687A CA2061687A CA2061687C CA 2061687 C CA2061687 C CA 2061687C CA 002061687 A CA002061687 A CA 002061687A CA 2061687 A CA2061687 A CA 2061687A CA 2061687 C CA2061687 C CA 2061687C
- Authority
- CA
- Canada
- Prior art keywords
- port
- devices
- network
- hub
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
Abstract
Localized port arrival information is processed for individual hubs and bridges in an extended computer network. A particular device is chosen as a starting reference. Device connections on each port of the particular device are then recursively determined.
Afterwards, device connections for apparent tree nodes attached to the starting reference are determined.
Afterwards, device connections for apparent tree nodes attached to the starting reference are determined.
Description
Title: DETERMINING PHYSICAL TOPOLOGY ACROSS REPEATERS
AND BRIDGES IN A COMPUTER NETWORK
Background of the Invention This invention relates generally to computer networks, and more particularly to different stations in a network inter-connected through bridges and hubs.
For simple computer networks such as a LAN (local area network) located on a small office suite on a single floor of a building, it has been relatively simple to determine the actual network layout by inspection. However, networks now include many stations through the use of 12-port and 48-port repeaters called hubs, and different networks are often joined together by bridges so that data packets are sent across different networks to computer devices located in many different buildings and locations. It is not unusual to remove stations from a network and add other stations without telling the network administrator.
Accordingly, a need has arisen for automatically collecting detailed accurate information about the layout and topology of computer networks.
Brief Summary of the Invention It is an object of an aspect of the invention to provide a method for determining the arrival port of message packets received by an interconnect device such as a hub, obtaining from the message packet an identification of the sender, and then storing for easy accessibility a list of each port on the hub and its associated computer device.
AND BRIDGES IN A COMPUTER NETWORK
Background of the Invention This invention relates generally to computer networks, and more particularly to different stations in a network inter-connected through bridges and hubs.
For simple computer networks such as a LAN (local area network) located on a small office suite on a single floor of a building, it has been relatively simple to determine the actual network layout by inspection. However, networks now include many stations through the use of 12-port and 48-port repeaters called hubs, and different networks are often joined together by bridges so that data packets are sent across different networks to computer devices located in many different buildings and locations. It is not unusual to remove stations from a network and add other stations without telling the network administrator.
Accordingly, a need has arisen for automatically collecting detailed accurate information about the layout and topology of computer networks.
Brief Summary of the Invention It is an object of an aspect of the invention to provide a method for determining the arrival port of message packets received by an interconnect device such as a hub, obtaining from the message packet an identification of the sender, and then storing for easy accessibility a list of each port on the hub and its associated computer device.
An object of an aspect of the invention is to obtain this arrival port information accurately, without acquiring false information based on spurious pulses and without interfering with any management functions which occur at the hub.
An object of an aspect of the invention is to provide a method for selectively listening at many different hubs for the arrival of message packets from a particular sender, and for periodically initiating a change to allow selective listening for the arrival of message packets from another particular sender.
An object of an aspect of the invention is to provide a method for instigating a particular station to send out an announcement packet to all multiple port repeaters such as hubs, and to bridges, with only minimal processing and distribution, and to enable individual hubs and/or bridges to identify which one of their ports is connected to that particular station.
An object of an aspect of the invention is to provide a method of processing the localized port arrival information for individual hubs and bridges in an extended network so as to determine and display the physical topology of the various network segments.
-2a-Accordingly, in one aspect of the present invention there is provided a method for determining physical topology of a plurality of devices in an extended computer network, each device in the plurality of devices having at least one port, the method comprising the steps of:
(a) choosing a particular device from the plurality of devices as a starting reference, and (b) recursively determining network device connections on each 1 o port of the particular device.
According to another aspect of the present invention there is provided a method for determining physical topology of a plurality of devices on a network, each device in the plurality of devices having at least one port, the method comprising the steps of:
15 (a) identifying all the devices on the network;
(b) selecting a first device from the plurality of devices;
(c) determining a connection structure for all devices from the plurality of devices which communicate to the first device through each port of the first device wherein for a first port of the first device, step (c) includes the substeps of 20 (c. l ) determining which devices from the plurality of devices which communicate to the first device through the first port are not directly connected to the first device through the first port, substep (c. l ) including for every second device from the plurality of devices which communicates to the first device through the first port, marking the second device as not directly connected to the first device 25 when any third device from the plurality of devices which communicates to the first device through the first port is detected communicating to the second device through any port of the third device which is different from a first port of the third device through which the third device communicates to the first device, and (c.2) determining which devices are directly connected to the 3o first device through the first port.
In still yet another aspect of the present invention there is provided a method for determining physical topology of a plurality of devices on a network, the method comprising the steps of:
(a) discovering identities of each device in the plurality of devices;
-2b-(b) selecting a first device from the plurality of devices;
(c) determining, by the first device for every other device in the plurality of devices, on which port the first device communicates with each of the other devices; and (d) determining which devices are not directly connected to any port of the first device including the substeps of (d. l ) selecting a second device from the plurality of devices which communicates with the first device through a first port of the first device, and (d.2) for every third device in the plurality of devices to which the first device communicates through the first port, performing the following substeps:
determining whether the second device communicates to the third device through the same port of the second device as the second device communicates with the first device, and when the second device is detected communicating to the third device through a different port of the second device from which the second device communicates with the first device, marking the third device as not connected to the first device.
2o The foregoing and other objects will become apparent to those skilled in the art in view of the drawings and related written description of a presently preferred embodiment of the invention as set forth.
2061~8~
An object of an aspect of the invention is to provide a method for selectively listening at many different hubs for the arrival of message packets from a particular sender, and for periodically initiating a change to allow selective listening for the arrival of message packets from another particular sender.
An object of an aspect of the invention is to provide a method for instigating a particular station to send out an announcement packet to all multiple port repeaters such as hubs, and to bridges, with only minimal processing and distribution, and to enable individual hubs and/or bridges to identify which one of their ports is connected to that particular station.
An object of an aspect of the invention is to provide a method of processing the localized port arrival information for individual hubs and bridges in an extended network so as to determine and display the physical topology of the various network segments.
-2a-Accordingly, in one aspect of the present invention there is provided a method for determining physical topology of a plurality of devices in an extended computer network, each device in the plurality of devices having at least one port, the method comprising the steps of:
(a) choosing a particular device from the plurality of devices as a starting reference, and (b) recursively determining network device connections on each 1 o port of the particular device.
According to another aspect of the present invention there is provided a method for determining physical topology of a plurality of devices on a network, each device in the plurality of devices having at least one port, the method comprising the steps of:
15 (a) identifying all the devices on the network;
(b) selecting a first device from the plurality of devices;
(c) determining a connection structure for all devices from the plurality of devices which communicate to the first device through each port of the first device wherein for a first port of the first device, step (c) includes the substeps of 20 (c. l ) determining which devices from the plurality of devices which communicate to the first device through the first port are not directly connected to the first device through the first port, substep (c. l ) including for every second device from the plurality of devices which communicates to the first device through the first port, marking the second device as not directly connected to the first device 25 when any third device from the plurality of devices which communicates to the first device through the first port is detected communicating to the second device through any port of the third device which is different from a first port of the third device through which the third device communicates to the first device, and (c.2) determining which devices are directly connected to the 3o first device through the first port.
In still yet another aspect of the present invention there is provided a method for determining physical topology of a plurality of devices on a network, the method comprising the steps of:
(a) discovering identities of each device in the plurality of devices;
-2b-(b) selecting a first device from the plurality of devices;
(c) determining, by the first device for every other device in the plurality of devices, on which port the first device communicates with each of the other devices; and (d) determining which devices are not directly connected to any port of the first device including the substeps of (d. l ) selecting a second device from the plurality of devices which communicates with the first device through a first port of the first device, and (d.2) for every third device in the plurality of devices to which the first device communicates through the first port, performing the following substeps:
determining whether the second device communicates to the third device through the same port of the second device as the second device communicates with the first device, and when the second device is detected communicating to the third device through a different port of the second device from which the second device communicates with the first device, marking the third device as not connected to the first device.
2o The foregoing and other objects will become apparent to those skilled in the art in view of the drawings and related written description of a presently preferred embodiment of the invention as set forth.
2061~8~
below.
Brief Description of the Drawings Fig. lA shows a typical computer network layout having multiport repeaters (hubs) connected directly together as well as interconnected through a bridge;
Fig. iB shows a typical LAN hub of Fig. lA having individual devices connected through twisted wire pairs to specific ports on the hub;
Fig. 2A is a schematic representation of the interconnect panel for a 48-port managed hub which incorporates the present invention;
Fig. 2B shows a preferred wiring pattern for interconnecting 8-wire twisted pair cabling with the 48-port managed hub of Fig.
2A;
Fig. 3 shows a LAN layout having 12-port and 48-port managed hubs which incorporates the present invention;
Fig. 4 shows a schematic diagram for the managed hubs of Fig.
3;
Fig. 5 is a timing diagram for a managed hub showing the difficulty of matching the correct port identification with its corresponding packet;
Fig. 6 is a block diagram for a 48-port managed hub featuring a preferred embodiment of the invention;
Figs. 7A-7C are flow charts for the managed hub of Fig. 6 showing how port arrival identification is achieved for computer network packets received by the managed hub of Fig. 6;
2~6168~
Brief Description of the Drawings Fig. lA shows a typical computer network layout having multiport repeaters (hubs) connected directly together as well as interconnected through a bridge;
Fig. iB shows a typical LAN hub of Fig. lA having individual devices connected through twisted wire pairs to specific ports on the hub;
Fig. 2A is a schematic representation of the interconnect panel for a 48-port managed hub which incorporates the present invention;
Fig. 2B shows a preferred wiring pattern for interconnecting 8-wire twisted pair cabling with the 48-port managed hub of Fig.
2A;
Fig. 3 shows a LAN layout having 12-port and 48-port managed hubs which incorporates the present invention;
Fig. 4 shows a schematic diagram for the managed hubs of Fig.
3;
Fig. 5 is a timing diagram for a managed hub showing the difficulty of matching the correct port identification with its corresponding packet;
Fig. 6 is a block diagram for a 48-port managed hub featuring a preferred embodiment of the invention;
Figs. 7A-7C are flow charts for the managed hub of Fig. 6 showing how port arrival identification is achieved for computer network packets received by the managed hub of Fig. 6;
2~6168~
Fig. 8 is an exemplary port arrival matrix for a 12-port managed hub;
Fig. 9 is an exemplary port arrival matrix for a 48-port managed hub;
Fig. 10 is a mapping address search flow chart for multiport repeaters such as the 12-port and 48-port hubs of Fig. 3;
Fig. 11 shows the mapping address objects for the hubs of Fig.
3 which are programmed to listen for packets originating from a network device identified by its address X;
Fig. 12A shows a computer network layout having at least one differently designed hub, with a managed hub and a managed bridge both incorporating the present invention;
Fig. 12B shows how the network topology of Fig. 12A appears to the mapping application;
Fig. 13 shows a typical packet format for extended network mapping announcements sent to devices in an Ethernet-type of computer network;
Fig. 14 is a flow chart for determining the physical topology across repeaters and bridges in an extended computer network;
Fig. 15A is a schematic diagram of an extended network having two LANs;
Figs. 15B and 15C are exemplary tree diagrams used to implement the flow chart of Fig. 14 with respect to the extended network of Fig. 15A; and Fig. 16 is a network topology map display that is produced by the flow chart of Fig. 14.
Detailed Description of Preferred Embodiments and Best Mode Generally speaking, the invention can be implemented in computer networks of various types and configurations, and the particular layouts shown are for purposes of illustration only.
In that regard, the network layout of Fig. lA shows how certain ports 20, 22 of their respective hubs 24, 26 receive packets from multiple senders. In contrast, other ports such as 28, 30 receive packets from one and only one sender (unless there is a configuration change made replacing one device with another or replacing one device with a multiport device such as a hub or bridge). Figure 1B shows a hub with a 12-port modular adapter 32 for connecting individual ports to network devices through twisted-pair cable also known as the IEEE 802.3 10 Baser standard.
Fig. 2A shows the back interconnect panel for a 48-port hub having in addition an AUI port 34 and a BNC (coax) port 36. The manner of hooking up the four pair twisted wire cable to each port such as 38 is shown in Fig. 2B.
In a hub such as shown in Fig. 2A, it is useful to monitor the traffic on each port and keep track of the station address of the node connected to each port, as well as keep track of other detailed information about the traffic on that port. In some implementations of a hub, an off-the-shelf network interface controller (NIC) chip 40 is used for network management functionality and this controller chip is not integrated with the rest of the repeater hardware of the hub. The repeater 42 may tell the firmware 44 the port number of each packet repeated using a special circuit. Essentially such a hub may be structured as shown in the schematic diagram of Fig. 4.
If the NIC chip 40 is run in promiscuous mode (a mode in which it listens to all packets, instead of only those addressed to it), it is possible to correlate the packets received by the NIC with the port numbers for the repeater to obtain detailed per-port network statistics. This correlation can be accomplished by the routine set forth in the following table:
I f~ ~ ~-~ r Q~IIC Interrupt Service Routine>
While tie NIC has a new racket l --' Note the numderof activity indications sent by the rPn~~ter Increment count of consecutive packets If there have been n consecutive packets without getting to the "idle" loop Exit promiscuous mode and only listen for network management packets If the NIC heard a packet, but the repeater did not, do not identify the port If the NIC heard a packet, but the repeater heard >1 packet, do not id port' If the NIC heard a packet and the repeater heard exactly one packet then If the repeater heard exactly one packet for each of the previous packets serviced by this interrupt Identify the packet as coming from this port else ~*) Do not identify the port of this packet _7_ If the network monitoring is overloading the hub and starts to degrade the response time to requests from a network management application, the hub will temporarily exit promiscuous mode and listen only to the network management packets addressed to it.
The method for correlating the port number with packets received by the NIC is complicated by several factors. For example, it is necessary for the firmware to respond to packet interrupts quickly - otherwise it will be overrun with packets and/or port to numbers. Interrupts can be disabled at different times while the firmware is performing other network management related tasks. Further impairing interrupt response time is the relatively low-performance microcontroller which is used to reduce costs.
As an additional example, sometimes the repeater will hear small runt packets which are not heard by the NIC. In other words, there is not always a one-to-one correspondence between packets heard by the NIC and port numbers from the repeater.
Another situation arises with small back-to-back packets and is most common when these packet bursts arrive when interrupts happen to be temporarily disabled. The NIC interrupt occurs slightly after the port number is indicated by the repeater. In the diagram of Fig. 5, the network activity line is high when there is network activity. The 2o NIC Interrupt Service Routine (ISR) line is high when executing the NIC
Interrupt ' Service Routine. In the diagram of Fig. 5, the portion 45 indicates port activity for 20fi168~
packet Rxl and the corresponding portion 46 indicates the dma of the same packet RX1 by the NIC.
At point A in Fig. 5, the port for packet Rxl is not known since the ISR observed two port numbers from the repeater (i.e., the ISR does not know if the extra port number is for a packet or if it is from a tiny runt heard by the repeater but not by the NIC). At point B, the ISR sees exactly one port number and would normally mis-identify the port of packet Rx2 as the port of packet Rx3. The routine of Table I solves this problem.
Fig. 6 shows a presently preferred embodiment for the invention in a managed hub implementation. A bus is used to interconnect the network management microprocessor, an EEPROM for code storage, a RAM, a network interface controller, and port number registers. The RAM includes space for normal data and packet storage, as well as space for implementing various features of the invention. The port arrival matrix of Fig. 9 is stored at one portion, the mapping address search objects of Table II are stored in another portion, and a third portion is used for the NIC
packet receive buffers.
LAN traffic comes into a 50 port repeater causing an entry into a port number register having sufficient bits to identify all the input ports, and also causing an activity indication to the network management microprocessor. If in promiscuous mode (see the flow chart of Figs. 7A, 7B and 7C), then the NIC receives and monitors all incoming packets. Otherwise only the packets addressed to the hub are processed and the other packets are merely 2~~1687 resent. The mapping address search objects are used in both hub and bridge implementations (see the flow charts of Figs. l0A and lOB which depict the map address procedure purely from the device' s point of view. Note the differences between the hub (Fig. l0A) and the bridge (Fig. lOB) implementations. The Map Address Objects themselves are shown in the following table:
9a MAPPING ADDRESS SEARCH OBJECTS
mapAddress OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write DESCRIPTION
"When object is set a map address search begins. If the address is detected on only one port, then the mapPort object is set to the port number on which the address was detected. Bridge:
the search completes immediately. Hub: the search will continue until a new address is placed into mapAddress."
mapState OBJECT-TYPE {
SYNTAX INTEGER
PS_ NONE(0), PS SINGLE(1), PS_MANY(2) ACCESS read-only DESCRIPTION
"It will be set to PS_SINGLE if the map address is detected on one and only one port. If the map address is detected on more than one port, map state is set to PS_l~lANY."
mapPort OBJECT-TYPE
SYNTAX INTEGER (0..65535) ACCESS read-only DESCRIPTION
"The port number on which the map address was detected. If map state is PS_NONE or PS_MANY then this object is not valid."
2a~168~
The various mapping address objects are shown in Fig. 11 wherein each of the devices Q, T and X are programmed to listen for packets coming from the device having an S address.
Hub 1 Hub 2 Segment A I I Segment B
Mapping Application To map a network of hubs, a mapping application needs to know which devices are connected to each of the hubs' ports. The mapping application is able to poll the network and find out the addresses of each hub, but to make a complete map, it must know the ports on which each hub is connected. Some ports may be connected to hundreds of nodes and it is not feasible for each hub to keep a list of node addresses for each port.
To solve this problem, the Map Address object has been created.
The mapping application simply sets the Map Address on a hub and the hub will listen for packets transmitted by the device specified by Map Address. When the Map Address is heard, the hub will record the port number on which the Map Address is heard and the mapping application will use this information to 'Lay out the network map.
In the network specified in Table 3, Hub 2 does not know which LAN segment Hub 1 is attached to, since many nodes are probably on each LAN segment. The mapping application can set the Map Address object on Hub 2 to the address of Hub 1. Later, when Hub 1 transmits a packet, Hub 2 will hear it and identify the port on which Hub 1 is connected.
MAPPING ANNOUNCEMENT
announceAddress OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS write-only DESCRIPTION
"When set to any MAC multi-cast address, the device will transmit three identical packets, each with the MAC source set to the device's MAC address. The MAC destination to the multi-cast address, the DSAP is F8. These packets will traverse bridges, allowing them and devices connected to them to learn the port connectivity of the mufti-casting device."
Hub 1 ~ ~ Bridge ~ ~ Hub 1 M PP g Application To map a network of hubs, a mapping application needs to know which devices are connected to each of the hubs ports. The mapping application is able to poll the network and find out the addresses of each hub, but to make a complete map, it must know the ports on which each hub is connected. Some ports may be connected to hundreds of nodes and it is not feasible for each hub to keep a list of node addresses for each port. The Map Address object previously discussed solves much of this problem, but in Table 5 above, there is a problem with basic use of the Map Address object in that Hub 1 will never hear packets from Hub 2, since all communication between Hub 2 and the mapping application is filtered by the bridge.
The mapping application could look in the address table maintained by the bridge to find out how the hubs are connected, but this does not always work, since not all bridges have an address table which is readable by the mapping application. Also, using information gathered from the hubs is much simpler than incorporating the address table information gathered from bridges. To enable Hub 1 to hear packets from Hub 2 and identify the port on which it is connected the mapping application must make Hub 2 transmit some sort of announcement packet which can be heard by Hub 1. To do this, there are several alternatives:
A) Have Hub 2 broadcast a packet which goes across the entire network. This alternative will accomplish the mapping objective, but almost every single node on the entire network will need to process the packet and this will cause a significant amount of useless broadcast traffic which does not need to be heard by all nodes.
B) Have Hub 2 transmit a packet addressed directly to Hub 1 This alternative will also accomplish the mapping objective, but on a large network, the mapping application would need to tell the hub to transmit a packet to every other hub on the network, adding a significant amount of overhead to the mapping process.
C) Have Hub 2 transmit a multicast packet heard only by hubs This is the ideal alternative, because the packet will go through the bridge and it will only heard by other hubs which listen for that multicast address This is the method by which hub network mapping is done.
This invention solves the problem of determining the physical topology (that is, the interconnection of Ian segments and interconnecting network devices) of a network. This is done automatically and produces a representation of the network which can be used for fault detection and diagnosis, performance characterization, and security.
Without the automatic determination of the physical topology of the network, the onus of mapping out the topology is on the human manager of the network, and is thus highly prone to error.
This invention uses mapping information available from repeaters and bridges to build a representation of the network. These repeaters and bridges are hereafter referred to as "networking devices". A networking devices connects two or more physical networking segments (coax, broadband, twisted-pair, "fiber, etc) through its ports.
A networking device will have two or more ports. Through these ports, the device "hears" others devices and end stations (e.g. personal computers) which are part of the network. A networking device hears other devices and end stations out of one and only one port.
For the following description, assume the following network:
lanl d~ 4 d2 d3 lan2 d5 d6 The algorithm first discovers the existence of bridges and repeaters in the network, resulting in a list of these networking devices:
-->dl-->d2-->d3-->d4-->d5-->d6-->
The algorithm then selects a device arbitrarily from the list (although a simple heuristic could easily be applied to choose a device which would enhance the performance of the algorithm). From that device, the process of determining network topology begins. This is accomplished by determining where all of the other devices in the network are with respect to that device, by hearing out of which port that device is located.
For example, if device d2 is connected to a LAN cable which is connected to dl's port 1, then dl hears d2 on port 1.
The resulting network after this first step (from the point of view of arbitrarily chosen device dl) may look as follows.
dl /I
d2 d3 d4 d5 d6 After this step is accomplished, it is possible to recursively step visit each of the resulting "nodes" of this tree, and to eliminate those devices which are not actually directly connected to the calling device. In the above example, we would descend from dl down to the node which contains d4, d5, d6. The goal here would be to eliminate those devices which are not directly connected to dl.
Looking at the original diagram, one can see chat only d4 is directly connected to dl; d5 and d6 are connected to dl through device d4. Algorithmically, the procedure for eliminating d5 and d6 is as follows:
First, select a device (for this example, we choose d4) and determine the port on which the calling device (d1) is heard. Then, try to eliminate the other nodes by showing that they are heard on a different port than the port on which the calling device is heard.
In the example, and choosing d4 as the "eliminator", if d4 hears dl on port 1, and then hears d5 on port 2, then d5 is eliminated, because we have proven that d4 stands between dl and d5 in the topology.
Applying this process recursively, the resulting hierarchy is a representation of the physical topology of the network. in the example, the resulting hierarchy would look as follows:
d1 /I \
d2 d3 d4 \
d5, d6 This representation of the network can then be used to draw a map of the network which looks like the original picture.
The value of automatically deriving the topology, versus manual attempts, can be easily seen.
Figure 13 shows a typical frame format which has the source address and destination address which are used in practicing this invention. Most packets are about 64 bytes long. Figure 12 makes it clear that a non-managed hub or a managed hub that is of a different design will not be recognized as a true hub (see Fig. 12B).
Figure 16 shows a network layout different from the other layouts in the drawings, and indicates the ability to draw a topology based on the information automatically acquired by practicing the unique procedures of the invention. The numbers indicate the Internet Protocol addresses, and H12 is a 12 port hub, H48 is a 48 port hub, HF is a fiber hub and BRM is a remote bridge which B 10 is a local 10 MB bridge.
Of course, the invention is not limited to the examples shown, but can be modified and varied, all within the scope of the following claims.
Fig. 9 is an exemplary port arrival matrix for a 48-port managed hub;
Fig. 10 is a mapping address search flow chart for multiport repeaters such as the 12-port and 48-port hubs of Fig. 3;
Fig. 11 shows the mapping address objects for the hubs of Fig.
3 which are programmed to listen for packets originating from a network device identified by its address X;
Fig. 12A shows a computer network layout having at least one differently designed hub, with a managed hub and a managed bridge both incorporating the present invention;
Fig. 12B shows how the network topology of Fig. 12A appears to the mapping application;
Fig. 13 shows a typical packet format for extended network mapping announcements sent to devices in an Ethernet-type of computer network;
Fig. 14 is a flow chart for determining the physical topology across repeaters and bridges in an extended computer network;
Fig. 15A is a schematic diagram of an extended network having two LANs;
Figs. 15B and 15C are exemplary tree diagrams used to implement the flow chart of Fig. 14 with respect to the extended network of Fig. 15A; and Fig. 16 is a network topology map display that is produced by the flow chart of Fig. 14.
Detailed Description of Preferred Embodiments and Best Mode Generally speaking, the invention can be implemented in computer networks of various types and configurations, and the particular layouts shown are for purposes of illustration only.
In that regard, the network layout of Fig. lA shows how certain ports 20, 22 of their respective hubs 24, 26 receive packets from multiple senders. In contrast, other ports such as 28, 30 receive packets from one and only one sender (unless there is a configuration change made replacing one device with another or replacing one device with a multiport device such as a hub or bridge). Figure 1B shows a hub with a 12-port modular adapter 32 for connecting individual ports to network devices through twisted-pair cable also known as the IEEE 802.3 10 Baser standard.
Fig. 2A shows the back interconnect panel for a 48-port hub having in addition an AUI port 34 and a BNC (coax) port 36. The manner of hooking up the four pair twisted wire cable to each port such as 38 is shown in Fig. 2B.
In a hub such as shown in Fig. 2A, it is useful to monitor the traffic on each port and keep track of the station address of the node connected to each port, as well as keep track of other detailed information about the traffic on that port. In some implementations of a hub, an off-the-shelf network interface controller (NIC) chip 40 is used for network management functionality and this controller chip is not integrated with the rest of the repeater hardware of the hub. The repeater 42 may tell the firmware 44 the port number of each packet repeated using a special circuit. Essentially such a hub may be structured as shown in the schematic diagram of Fig. 4.
If the NIC chip 40 is run in promiscuous mode (a mode in which it listens to all packets, instead of only those addressed to it), it is possible to correlate the packets received by the NIC with the port numbers for the repeater to obtain detailed per-port network statistics. This correlation can be accomplished by the routine set forth in the following table:
I f~ ~ ~-~ r Q~IIC Interrupt Service Routine>
While tie NIC has a new racket l --' Note the numderof activity indications sent by the rPn~~ter Increment count of consecutive packets If there have been n consecutive packets without getting to the "idle" loop Exit promiscuous mode and only listen for network management packets If the NIC heard a packet, but the repeater did not, do not identify the port If the NIC heard a packet, but the repeater heard >1 packet, do not id port' If the NIC heard a packet and the repeater heard exactly one packet then If the repeater heard exactly one packet for each of the previous packets serviced by this interrupt Identify the packet as coming from this port else ~*) Do not identify the port of this packet _7_ If the network monitoring is overloading the hub and starts to degrade the response time to requests from a network management application, the hub will temporarily exit promiscuous mode and listen only to the network management packets addressed to it.
The method for correlating the port number with packets received by the NIC is complicated by several factors. For example, it is necessary for the firmware to respond to packet interrupts quickly - otherwise it will be overrun with packets and/or port to numbers. Interrupts can be disabled at different times while the firmware is performing other network management related tasks. Further impairing interrupt response time is the relatively low-performance microcontroller which is used to reduce costs.
As an additional example, sometimes the repeater will hear small runt packets which are not heard by the NIC. In other words, there is not always a one-to-one correspondence between packets heard by the NIC and port numbers from the repeater.
Another situation arises with small back-to-back packets and is most common when these packet bursts arrive when interrupts happen to be temporarily disabled. The NIC interrupt occurs slightly after the port number is indicated by the repeater. In the diagram of Fig. 5, the network activity line is high when there is network activity. The 2o NIC Interrupt Service Routine (ISR) line is high when executing the NIC
Interrupt ' Service Routine. In the diagram of Fig. 5, the portion 45 indicates port activity for 20fi168~
packet Rxl and the corresponding portion 46 indicates the dma of the same packet RX1 by the NIC.
At point A in Fig. 5, the port for packet Rxl is not known since the ISR observed two port numbers from the repeater (i.e., the ISR does not know if the extra port number is for a packet or if it is from a tiny runt heard by the repeater but not by the NIC). At point B, the ISR sees exactly one port number and would normally mis-identify the port of packet Rx2 as the port of packet Rx3. The routine of Table I solves this problem.
Fig. 6 shows a presently preferred embodiment for the invention in a managed hub implementation. A bus is used to interconnect the network management microprocessor, an EEPROM for code storage, a RAM, a network interface controller, and port number registers. The RAM includes space for normal data and packet storage, as well as space for implementing various features of the invention. The port arrival matrix of Fig. 9 is stored at one portion, the mapping address search objects of Table II are stored in another portion, and a third portion is used for the NIC
packet receive buffers.
LAN traffic comes into a 50 port repeater causing an entry into a port number register having sufficient bits to identify all the input ports, and also causing an activity indication to the network management microprocessor. If in promiscuous mode (see the flow chart of Figs. 7A, 7B and 7C), then the NIC receives and monitors all incoming packets. Otherwise only the packets addressed to the hub are processed and the other packets are merely 2~~1687 resent. The mapping address search objects are used in both hub and bridge implementations (see the flow charts of Figs. l0A and lOB which depict the map address procedure purely from the device' s point of view. Note the differences between the hub (Fig. l0A) and the bridge (Fig. lOB) implementations. The Map Address Objects themselves are shown in the following table:
9a MAPPING ADDRESS SEARCH OBJECTS
mapAddress OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-write DESCRIPTION
"When object is set a map address search begins. If the address is detected on only one port, then the mapPort object is set to the port number on which the address was detected. Bridge:
the search completes immediately. Hub: the search will continue until a new address is placed into mapAddress."
mapState OBJECT-TYPE {
SYNTAX INTEGER
PS_ NONE(0), PS SINGLE(1), PS_MANY(2) ACCESS read-only DESCRIPTION
"It will be set to PS_SINGLE if the map address is detected on one and only one port. If the map address is detected on more than one port, map state is set to PS_l~lANY."
mapPort OBJECT-TYPE
SYNTAX INTEGER (0..65535) ACCESS read-only DESCRIPTION
"The port number on which the map address was detected. If map state is PS_NONE or PS_MANY then this object is not valid."
2a~168~
The various mapping address objects are shown in Fig. 11 wherein each of the devices Q, T and X are programmed to listen for packets coming from the device having an S address.
Hub 1 Hub 2 Segment A I I Segment B
Mapping Application To map a network of hubs, a mapping application needs to know which devices are connected to each of the hubs' ports. The mapping application is able to poll the network and find out the addresses of each hub, but to make a complete map, it must know the ports on which each hub is connected. Some ports may be connected to hundreds of nodes and it is not feasible for each hub to keep a list of node addresses for each port.
To solve this problem, the Map Address object has been created.
The mapping application simply sets the Map Address on a hub and the hub will listen for packets transmitted by the device specified by Map Address. When the Map Address is heard, the hub will record the port number on which the Map Address is heard and the mapping application will use this information to 'Lay out the network map.
In the network specified in Table 3, Hub 2 does not know which LAN segment Hub 1 is attached to, since many nodes are probably on each LAN segment. The mapping application can set the Map Address object on Hub 2 to the address of Hub 1. Later, when Hub 1 transmits a packet, Hub 2 will hear it and identify the port on which Hub 1 is connected.
MAPPING ANNOUNCEMENT
announceAddress OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS write-only DESCRIPTION
"When set to any MAC multi-cast address, the device will transmit three identical packets, each with the MAC source set to the device's MAC address. The MAC destination to the multi-cast address, the DSAP is F8. These packets will traverse bridges, allowing them and devices connected to them to learn the port connectivity of the mufti-casting device."
Hub 1 ~ ~ Bridge ~ ~ Hub 1 M PP g Application To map a network of hubs, a mapping application needs to know which devices are connected to each of the hubs ports. The mapping application is able to poll the network and find out the addresses of each hub, but to make a complete map, it must know the ports on which each hub is connected. Some ports may be connected to hundreds of nodes and it is not feasible for each hub to keep a list of node addresses for each port. The Map Address object previously discussed solves much of this problem, but in Table 5 above, there is a problem with basic use of the Map Address object in that Hub 1 will never hear packets from Hub 2, since all communication between Hub 2 and the mapping application is filtered by the bridge.
The mapping application could look in the address table maintained by the bridge to find out how the hubs are connected, but this does not always work, since not all bridges have an address table which is readable by the mapping application. Also, using information gathered from the hubs is much simpler than incorporating the address table information gathered from bridges. To enable Hub 1 to hear packets from Hub 2 and identify the port on which it is connected the mapping application must make Hub 2 transmit some sort of announcement packet which can be heard by Hub 1. To do this, there are several alternatives:
A) Have Hub 2 broadcast a packet which goes across the entire network. This alternative will accomplish the mapping objective, but almost every single node on the entire network will need to process the packet and this will cause a significant amount of useless broadcast traffic which does not need to be heard by all nodes.
B) Have Hub 2 transmit a packet addressed directly to Hub 1 This alternative will also accomplish the mapping objective, but on a large network, the mapping application would need to tell the hub to transmit a packet to every other hub on the network, adding a significant amount of overhead to the mapping process.
C) Have Hub 2 transmit a multicast packet heard only by hubs This is the ideal alternative, because the packet will go through the bridge and it will only heard by other hubs which listen for that multicast address This is the method by which hub network mapping is done.
This invention solves the problem of determining the physical topology (that is, the interconnection of Ian segments and interconnecting network devices) of a network. This is done automatically and produces a representation of the network which can be used for fault detection and diagnosis, performance characterization, and security.
Without the automatic determination of the physical topology of the network, the onus of mapping out the topology is on the human manager of the network, and is thus highly prone to error.
This invention uses mapping information available from repeaters and bridges to build a representation of the network. These repeaters and bridges are hereafter referred to as "networking devices". A networking devices connects two or more physical networking segments (coax, broadband, twisted-pair, "fiber, etc) through its ports.
A networking device will have two or more ports. Through these ports, the device "hears" others devices and end stations (e.g. personal computers) which are part of the network. A networking device hears other devices and end stations out of one and only one port.
For the following description, assume the following network:
lanl d~ 4 d2 d3 lan2 d5 d6 The algorithm first discovers the existence of bridges and repeaters in the network, resulting in a list of these networking devices:
-->dl-->d2-->d3-->d4-->d5-->d6-->
The algorithm then selects a device arbitrarily from the list (although a simple heuristic could easily be applied to choose a device which would enhance the performance of the algorithm). From that device, the process of determining network topology begins. This is accomplished by determining where all of the other devices in the network are with respect to that device, by hearing out of which port that device is located.
For example, if device d2 is connected to a LAN cable which is connected to dl's port 1, then dl hears d2 on port 1.
The resulting network after this first step (from the point of view of arbitrarily chosen device dl) may look as follows.
dl /I
d2 d3 d4 d5 d6 After this step is accomplished, it is possible to recursively step visit each of the resulting "nodes" of this tree, and to eliminate those devices which are not actually directly connected to the calling device. In the above example, we would descend from dl down to the node which contains d4, d5, d6. The goal here would be to eliminate those devices which are not directly connected to dl.
Looking at the original diagram, one can see chat only d4 is directly connected to dl; d5 and d6 are connected to dl through device d4. Algorithmically, the procedure for eliminating d5 and d6 is as follows:
First, select a device (for this example, we choose d4) and determine the port on which the calling device (d1) is heard. Then, try to eliminate the other nodes by showing that they are heard on a different port than the port on which the calling device is heard.
In the example, and choosing d4 as the "eliminator", if d4 hears dl on port 1, and then hears d5 on port 2, then d5 is eliminated, because we have proven that d4 stands between dl and d5 in the topology.
Applying this process recursively, the resulting hierarchy is a representation of the physical topology of the network. in the example, the resulting hierarchy would look as follows:
d1 /I \
d2 d3 d4 \
d5, d6 This representation of the network can then be used to draw a map of the network which looks like the original picture.
The value of automatically deriving the topology, versus manual attempts, can be easily seen.
Figure 13 shows a typical frame format which has the source address and destination address which are used in practicing this invention. Most packets are about 64 bytes long. Figure 12 makes it clear that a non-managed hub or a managed hub that is of a different design will not be recognized as a true hub (see Fig. 12B).
Figure 16 shows a network layout different from the other layouts in the drawings, and indicates the ability to draw a topology based on the information automatically acquired by practicing the unique procedures of the invention. The numbers indicate the Internet Protocol addresses, and H12 is a 12 port hub, H48 is a 48 port hub, HF is a fiber hub and BRM is a remote bridge which B 10 is a local 10 MB bridge.
Of course, the invention is not limited to the examples shown, but can be modified and varied, all within the scope of the following claims.
Claims (4)
- We Claim:
A method for determining physical topology of a plurality of devices in an extended computer network, each device in the plurality of devices having at least one port, the method comprising the steps of:
(a) choosing a particular device from the plurality of devices as a starting reference, and (b) recursively determining network device connections on each port of the particular device. - 2, A method for determining physical topology of a plurality of devices on a network, each device in the plurality of devices having at least one port, the method comprising the steps of:
(a) identifying all the devices on the network;
(b) selecting a first device from the plurality of devices;
(c) determining a connection structure for all devices from the plurality of devices which communicate to the first device through each port of the first device wherein for a first port of the first device, step (c) includes the substeps of:
(c.1) determining which devices from the plurality of devices which communicate to the first device through the first port are not directly connected to the first device through the first port, substep (c.1) including for every second device from the plurality of devices which communicates to the first device through the first port, marking the second device as not directly connected to the first device when any third device from the plurality of devices which communicates to the first device through the first port is detected communicating to the second device through any port of the third device which is different from a first port of the third device through which the third device communicates to the first device, and (c.2) determining which devices are directly connected to the first device through the first port. - 3. A method as in claim 2 wherein step (c) additionally includes the substep of:
(c.3) determining a connection structure for all devices from the plurality of devices connected to a first port of a fourth device from the plurality of devices, wherein there is not direct connection to the first device from the first port of the fourth device and the fourth device is determined in substep (c.2) to be directly connected to the first device through the first port of the first device. - 4. A method for determining physical topology of a plurality of devices on a network, the method comprising the steps of:
(a) discovering identities of each device in the plurality of devices;
(b) selecting a first device from the plurality of devices;
(c) determining, by the first device for every other device in the plurality of devices, on which port the first device communicates with each of the other devices; and (d) determining which devices are not directly connected to any port of the first device including the substeps of (d.1) selecting a second device from the plurality of devices which communicates with the first device through a first port of the first device, and (d.2) for every third device in the plurality of devices to which the first device communicates through the first port, performing the following substeps:
determining whether the second device communicates to the third device through the same port of the second device as the second device communicates with the first device, and when the second device is detected communicating to the third device through a different port of the second device from which the second device communicates with the first device, marking the third device as not connected to the first device.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/693,980 US5297138A (en) | 1991-04-30 | 1991-04-30 | Determining physical topology across repeaters and bridges in a computer network |
US693,980 | 1991-04-30 |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2061687A1 CA2061687A1 (en) | 1992-10-31 |
CA2061687C true CA2061687C (en) | 2000-02-29 |
Family
ID=24786930
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002061687A Expired - Fee Related CA2061687C (en) | 1991-04-30 | 1992-02-21 | Determining physical topology across repeaters and bridges in a computer network |
Country Status (5)
Country | Link |
---|---|
US (1) | US5297138A (en) |
EP (1) | EP0511851B1 (en) |
JP (1) | JP3323228B2 (en) |
CA (1) | CA2061687C (en) |
DE (1) | DE69225637T2 (en) |
Families Citing this family (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5727157A (en) * | 1990-09-17 | 1998-03-10 | Cabletron Systems, Inc. | Apparatus and method for determining a computer network topology |
GB9109609D0 (en) * | 1991-05-03 | 1991-06-26 | D2B Systems Co Ltd | System of signal processing apparatuses,and apparatuses for use in such a system |
US5574869A (en) * | 1992-03-30 | 1996-11-12 | Intel Corporation | Bus bridge circuit having configuration space enable register for controlling transition between various modes by writing the bridge identifier into CSE register |
DE4322249A1 (en) * | 1992-10-23 | 1994-04-28 | Marquardt Gmbh | Bus switch |
US5550802A (en) * | 1992-11-02 | 1996-08-27 | National Semiconductor Corporation | Data communication network with management port for isochronous switch |
US5550836A (en) * | 1992-11-06 | 1996-08-27 | Hewlett-Packard Company | High speed data transfer over twisted pair cabling |
AU675362B2 (en) * | 1993-09-01 | 1997-01-30 | Cabletron Systems, Inc. | Determination of network topology |
US5430730A (en) * | 1993-09-14 | 1995-07-04 | Rolm Company | Method for building a sub-network in a distributed voice messaging system |
US5708772A (en) * | 1994-04-29 | 1998-01-13 | Bay Networks, Inc. | Network topology determination by dissecting unitary connections and detecting non-responsive nodes |
WO1996007139A1 (en) * | 1994-09-01 | 1996-03-07 | Mcalpine Gary L | A multi-port memory system including read and write buffer interfaces |
US5796738A (en) * | 1995-03-13 | 1998-08-18 | Compaq Computer Corporation | Multiport repeater with collision detection and jam signal generation |
US5742607A (en) * | 1995-12-20 | 1998-04-21 | Intel Corporation | Method and apparatus for controlling two way communication via disparate physical media |
US6233623B1 (en) | 1996-01-11 | 2001-05-15 | Cabletron Systems, Inc. | Replicated resource management system for managing resources in a distributed application and maintaining a relativistic view of state |
IL119062A0 (en) * | 1996-08-13 | 1996-11-14 | Madge Networks Israel Ltd | Apparatus and method for detecting a layout of a switched local network |
US6188675B1 (en) | 1996-08-23 | 2001-02-13 | International Business Machines Corporation | System and method for self-identifying and configuring the nodes of a network |
US5802319A (en) * | 1996-10-23 | 1998-09-01 | Hewlett-Packard Company | Method and apparatus for employing an intelligent agent to cause a packet to be sent to update a bridge's filtering database when a station is moved in a network |
US6038600A (en) * | 1997-07-16 | 2000-03-14 | Hewlett-Packard Company | Method and system for automatic detection of bridged and repeated network device connections |
US6003074A (en) * | 1998-02-24 | 1999-12-14 | Hewlett-Packard Company | Method and apparatus for mapping the physical topology of a subnetwork |
JP4759135B2 (en) * | 1998-05-02 | 2011-08-31 | エミュレックス デザイン アンド マニュファクチュアリング コーポレーション | Distributed switch and connection control configuration and method for digital communication network |
US6205122B1 (en) * | 1998-07-21 | 2001-03-20 | Mercury Interactive Corporation | Automatic network topology analysis |
US6166653A (en) * | 1998-08-13 | 2000-12-26 | Motorola Inc | System for address initialization of generic nodes in a distributed command and control system and method therefor |
US6108702A (en) | 1998-12-02 | 2000-08-22 | Micromuse, Inc. | Method and apparatus for determining accurate topology features of a network |
US6243746B1 (en) * | 1998-12-04 | 2001-06-05 | Sun Microsystems, Inc. | Method and implementation for using computer network topology objects |
US6697338B1 (en) | 1999-10-28 | 2004-02-24 | Lucent Technologies Inc. | Determination of physical topology of a communication network |
JP3696023B2 (en) * | 2000-01-31 | 2005-09-14 | 日立ソフトウエアエンジニアリング株式会社 | Network configuration automatic recognition method and system having intelligent network relay device |
WO2001076194A1 (en) * | 2000-03-31 | 2001-10-11 | British Telecommunications Public Limited Company | Apparatus and method of determining network address usage and allocation |
US6667960B1 (en) * | 2000-04-29 | 2003-12-23 | Hewlett-Packard Development Company, L.P. | Protocol for identifying components in a point-to-point computer system |
US7752024B2 (en) * | 2000-05-05 | 2010-07-06 | Computer Associates Think, Inc. | Systems and methods for constructing multi-layer topological models of computer networks |
AU2001261275A1 (en) * | 2000-05-05 | 2001-11-20 | Aprisma Management Technologies, Inc. | Systems and methods for isolating faults in computer networks |
US7237138B2 (en) * | 2000-05-05 | 2007-06-26 | Computer Associates Think, Inc. | Systems and methods for diagnosing faults in computer networks |
AU2001261258A1 (en) * | 2000-05-05 | 2001-11-20 | Aprisma Management Technologies, Inc. | Help desk systems and methods for use with communications networks |
US7500143B2 (en) * | 2000-05-05 | 2009-03-03 | Computer Associates Think, Inc. | Systems and methods for managing and analyzing faults in computer networks |
GB2364851B (en) * | 2000-07-15 | 2002-07-31 | 3Com Corp | Identifying an edge switch and port to which a network user is attached |
DE10046312B4 (en) * | 2000-09-19 | 2004-02-26 | Siemens Ag | Procedure for determining network topologies |
US7039696B1 (en) * | 2000-10-31 | 2006-05-02 | Hewlett-Packard Development Company, L.P. | Method and system for processing data for network connections |
US7002926B1 (en) | 2000-11-30 | 2006-02-21 | Western Digital Ventures, Inc. | Isochronous switched fabric network |
GB2377118B (en) * | 2001-06-27 | 2003-06-25 | 3Com Corp | Method and apparatus for determining unmanaged network devices in the topology of a network |
US6826162B2 (en) * | 2001-09-28 | 2004-11-30 | Hewlett-Packard Development Company, L.P. | Locating and mapping wireless network devices via wireless gateways |
US20030064718A1 (en) * | 2001-09-28 | 2003-04-03 | Haines Robert E. | Selective communication in a wireless network based on peer-to-peer signal quality |
US20030093509A1 (en) * | 2001-10-05 | 2003-05-15 | Li Raymond M. | Storage area network methods and apparatus with coordinated updating of topology representation |
US7421466B2 (en) * | 2001-10-29 | 2008-09-02 | Hewlett-Packard Development Company, L.P. | Dynamic mapping of wireless network devices |
US7656903B2 (en) * | 2002-01-30 | 2010-02-02 | Panduit Corp. | System and methods for documenting networks with electronic modules |
US7512703B2 (en) * | 2003-01-31 | 2009-03-31 | Hewlett-Packard Development Company, L.P. | Method of storing data concerning a computer network |
WO2005053230A2 (en) | 2003-11-28 | 2005-06-09 | Insightix Ltd. | Methods and systems for collecting information relating to a communication network and for collecting information relating to operating systems operating on nodes in a communication network |
US20070297349A1 (en) * | 2003-11-28 | 2007-12-27 | Ofir Arkin | Method and System for Collecting Information Relating to a Communication Network |
EP1762094A4 (en) * | 2003-12-08 | 2007-11-14 | Silicon Image Inc | Integrated adressing scheme for use in a system having a tree structure |
US20050152283A1 (en) * | 2004-01-08 | 2005-07-14 | David Ritzenthaler | Wireless device discovery |
US20050240874A1 (en) * | 2004-04-22 | 2005-10-27 | Alcatel | Bookmarks used for map navigation |
CN101809934B (en) * | 2007-06-19 | 2014-07-02 | 北卡罗来纳科姆斯科普公司 | Methods, systems, and computer program products for using managed port circuitry |
US20090327563A1 (en) * | 2008-06-30 | 2009-12-31 | Ilia Greenblat | Connecting between data-handling circuits of an integrated circuit |
EP2159959B1 (en) | 2008-08-26 | 2013-06-19 | Siemens Aktiengesellschaft | Method for calculating a topology, network components and central unit |
WO2011074492A1 (en) | 2009-12-18 | 2011-06-23 | 株式会社 村田製作所 | Thin film forming method and quantum dot device |
US8996692B2 (en) | 2009-12-18 | 2015-03-31 | International Business Machines Corporation | Forming configuration information about components of systems which include components for which acquisition of configuration information is restricted |
US20140108000A1 (en) * | 2012-10-11 | 2014-04-17 | Cisco Technology, Inc. | Generate, Edit, and Automated Use of a Machine-Readable Cable Specification to Audit Cabling of a Converged Infrastructure |
CN114520765A (en) * | 2022-01-13 | 2022-05-20 | 锐捷网络股份有限公司 | Automatic configuration method and device of equipment |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4827411A (en) * | 1987-06-15 | 1989-05-02 | International Business Machines Corporation | Method of maintaining a topology database |
EP0352883B1 (en) * | 1988-07-25 | 1995-09-13 | Digital Equipment Corporation | Network topology control method and apparatus |
US4864559A (en) * | 1988-09-27 | 1989-09-05 | Digital Equipment Corporation | Method of multicast message distribution |
US5140585A (en) * | 1990-07-19 | 1992-08-18 | Kabushiki Kaisha Toshiba | Star local-area network system |
JP3315404B2 (en) * | 1990-09-28 | 2002-08-19 | ヒューレット・パッカード・カンパニー | How to detect network topological features |
-
1991
- 1991-04-30 US US07/693,980 patent/US5297138A/en not_active Expired - Lifetime
-
1992
- 1992-02-21 CA CA002061687A patent/CA2061687C/en not_active Expired - Fee Related
- 1992-04-28 JP JP13576792A patent/JP3323228B2/en not_active Expired - Fee Related
- 1992-04-29 DE DE69225637T patent/DE69225637T2/en not_active Expired - Lifetime
- 1992-04-29 EP EP92303873A patent/EP0511851B1/en not_active Expired - Lifetime
Also Published As
Publication number | Publication date |
---|---|
CA2061687A1 (en) | 1992-10-31 |
DE69225637D1 (en) | 1998-07-02 |
US5297138A (en) | 1994-03-22 |
EP0511851B1 (en) | 1998-05-27 |
JP3323228B2 (en) | 2002-09-09 |
JPH05183549A (en) | 1993-07-23 |
EP0511851A3 (en) | 1993-06-16 |
DE69225637T2 (en) | 1998-09-24 |
EP0511851A2 (en) | 1992-11-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2061687C (en) | Determining physical topology across repeaters and bridges in a computer network | |
US5321695A (en) | Port arrival identification for computer network packets | |
US5421024A (en) | Detection of a relative location of a network device using a multicast packet processed only by hubs | |
US5293635A (en) | Detection on a network by a mapping application of a relative location of a first device to a second device | |
US6041042A (en) | Remote port mirroring system and method thereof | |
US6538997B1 (en) | Layer-2 trace method and node | |
US5088090A (en) | Routing system to interconnect local area networks | |
EP0637415B1 (en) | System and method for automatic segment resolution on a local area network | |
US6944130B1 (en) | Method and apparatus for determining a layer 2 path in a switched network | |
US7684416B2 (en) | System for automatically identifying the physical location of network end devices | |
US20040184407A1 (en) | Operations, administration, and maintenance data packet and related testing methods | |
JPH08503821A (en) | Method for assigning priority to traffic between local area networks interconnected by a central network | |
JPH08116334A (en) | Method and device for monitoring/fault analysis in network constituted of plural lans | |
JPH07245614A (en) | Method for measuring inter-equipments distance on lan and equipment therefor | |
US6658012B1 (en) | Statistics for VLAN bridging devices | |
Christensen et al. | Local area networks—evolving from shared to switched access | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Interface Configuration and Support | |
Cisco | Network Management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |