WO1997023974A1 - Method and apparatus for determining the status of a device in a communication network - Google Patents
Method and apparatus for determining the status of a device in a communication network Download PDFInfo
- Publication number
- WO1997023974A1 WO1997023974A1 PCT/US1996/020081 US9620081W WO9723974A1 WO 1997023974 A1 WO1997023974 A1 WO 1997023974A1 US 9620081 W US9620081 W US 9620081W WO 9723974 A1 WO9723974 A1 WO 9723974A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- ofthe
- model
- state
- control module
- maintaining
- Prior art date
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/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
Definitions
- This invention relates generally to communications networks, and more particularly to monitoring the status of manageable network devices.
- Communications networks provide a capability for one element, referred to as a source, to transmit data to another element, referred to as a destination.
- the data may be transmitted along a path that includes several devices. Examples of such devices are repeaters, switches, routers, bridges, and hubs.
- each ofthe devices may be characterized as manageable, self-managing, or a combination of manageable and self-managing.
- a manageable device is one which receives control from an extemal manager.
- an extemal manager may reside in another device, separate from the manageable device and coupled to the same network as the manageable device.
- the extemal manager which typically controls several manageable devices, may perform functions such as: setting connections from an ingress port to an egress port ofthe manageable device; removing connections of the manageable device; and retrieving information used for the extemal manager to control the manageable devices under the extemal manager's control.
- a self-managing device is one which does not use an extemal manager for control.
- a device may also have some aspects which are controlled by an extemal manager and some aspects which are self-managed.
- the extemal manager In order for the extemal manager to effectively control a device, it is useful for the extemal manager to have information regarding the state ofthe device.
- the term "device- manager synchronization" refers to a situation in which the extemal manager is able to determine the state of devices under control by the extemal manager.
- extemal managers retrieve information regarding the status of each ofthe devices under control by the extemal manager.
- the external manager determines, from the retrieved information, that each device is in one of only two possible states - either "up” (i.e. operable) or "down” (i.e. not operable). If no information can be retrieved from a particular device, the extemal manager determines that particular device is "down.”
- a disadvantage to this approach is that a device may actually be in one of more than only two possible states. For example, a device may be in a "busy" state, in which the device is operable but not able to provide status information to the extemal manager at a particular time. In such a situation, an extemal manager would determine that the device is "down," even though the device may be able to perform network functions in the near future. As a result of this determination, the existing extemal manager may perform certain actions to provide a path for network data without using the "down" device, even though the "down" device may be available for such use. Thus, in the prior art, a network may have an inefficient arrangement resulting in adverse effects such as increased cost, increased data latency and decreased network reliability.
- a network is monitored for status information indicative ofthe status of a manageable device within the network.
- a network manager receives the status information, and updates or initializes a device model in accordance with the status information.
- a state machine may be used to determine a new state for the device model, and to enable or disable the device model.
- the network manager may also take action to inquire as to the status ofthe manageable device, for example by polling the manageable device or by initiating a discovery process.
- the device model may be used by the network manager as a basis by which to control the manageable device, and thus control aspects ofthe communications within the network.
- An embodiment ofthe invention is directed to a method for determining a status of a device in a communications network, comprising the steps of receiving a status report including information regarding the device, determining a previous state ofthe device, and maintaining a model ofthe device based upon a combination ofthe previous state ofthe device and the information regarding the device.
- the method may further comprise a step of querying the device to provide additional information, and the step of maintaining may include maintaining the model ofthe device based upon a combination ofthe previous state of the device, the information regarding the device, and the additional information.
- Another embodiment ofthe invention is directed to an apparatus for determining a status of a device in a communications network, comprising means for receiving a status report including information regarding the device, means for determining a previous state ofthe device, and means for maintaining a model ofthe device based upon a combination ofthe previous state ofthe device and the information regarding the device.
- Yet another embodiment ofthe invention is directed to an apparatus for determining a status of a device in a communications network, comprising a model of the device containing information regarding a previous state ofthe device, and a model control module coupled to the model ofthe device.
- the model control module has an input that receives a status report including information regarding the device, and an output that maintains the model ofthe device based upon a combination ofthe previous state ofthe device and the information regarding the device.
- the status report may be a message indicative of a hard reboot ofthe device, results of a discovery process performed on the communications network, or results of a polling process. Additionally, a discovery process, a polling process, or a reset process may be performed in response to the state ofthe model ofthe device.
- the model ofthe device may be maintained in an enabled state indicative that the device is ready to be controlled by a network manager, or a disabled state indicative that the device is not ready to be controlled by a network manager.
- the model ofthe device may be maintained in one of a predetermined plurality of states that includes more than two states, for example an unknown state indicative that there is insufficient information to determine a capability ofthe device, an initialized state indicative that the device has been discovered and is ready to be controlled by a network manager, a lost state indicative that the device was previously ready to be controlled but did not respond to a status inquiry, and an established after lost state indicative that a successful discovery has not yet been performed with respect to the device.
- a state machine may be provided which receives the previous state ofthe device and the information regarding the device, and provides an output based upon which the model ofthe device is maintained.
- FIG. 1 illustrates a network having some manageable devices under control of a network manager in accordance with one embodiment ofthe invention
- Fig. 2 depicts detail of an embodiment ofthe synchronization module ofthe network manager illustrated in Fig. 1 ;
- Fig. 3 is a flow diagram of a process performed by the synchronization module of Fig. 2;
- Fig. 4 is a flow diagram showing more detail ofthe process of Fig. 3;
- Fig. 5 is a diagram ofthe state machine within the synchronization module shown in Fig. 2;
- Fig. 6 is a table illustrating more detail ofthe state machine of Fig. 5; and Fig. 7 illustrates a general purpose computer which may be used in one embodiment of the network manager illustrated in Fig. 1.
- Fig. 1 shows a network 10 having manageable devices, and a network manager 11 for providing control to the manageable devices 100 ofthe network 10.
- the network 10 may also include self-managing devices 102 as well as manageable devices 100. Additionally, the manageable devices 100 may be self-managing in some respects and manageable in other respects.
- SpectrumTM model-based network management system
- U.S. Patent No. 5,261,044 issued November 9, 1993 to R.Dev et al., and hereby inco ⁇ orated by reference in its entirety.
- the SpectrumTM network management system is commercially available and also described in various user manuals and literature available from Cabletron Systems, Inc., Rochester, New Hampshire.
- the network manager includes a synchronization module 12 for determining the status ofthe manageable devices 100, and a control module 14 for providing appropriate control as described above.
- the synchronization module 12 receives status information 17 from the network, and provides status inquiries 18 to the network 10.
- the synchronization module 12 determines the status ofthe manageable devices of the network 10, and provides this status information to the control module 14.
- the control module 14 determines appropriate action to take, and provides the appropriate control 19 to the manageable devices ofthe network 10.
- the synchronization module may also provide control 19 to the devices ofthe network if such control is advantageous to achieving device-manager synchronization.
- Fig. 2 depicts detail of an embodiment ofthe synchronization module 12 ofthe network manager illustrated in Fig. 1.
- the synchronization module 12 includes a model control module 20 coupled to a network model 21 that includes device models 210A, 210B, 210C . . . 2 ION.
- the model control module 20 is also coupled to each of a state machine 22, a polling manager 23, a discovery mechanism 25, and a reset mechanism 27.
- the model control module creates and maintains device models 210 that represent the status of manageable devices 100 ofthe network 10.
- the network model 21 may contain additional information, such as connectivity information with respect to the devices ofthe network 10. When the state of network model 21 matches the state ofthe actual network 10, the synchronization has been achieved.
- the control module 14 may then read the status ofthe device models 21 in order to determine appropriate control 19 to be provided to the network 10.
- the synchronization module 12 may be implemented as a software module, for example an object-oriented software module.
- the device models 210 may include an object representation for each device, wherein the object representation is indicative ofthe status ofthe device.
- the different sub-elements ofthe synchronization module 12 are implemented as software on a floppy 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 ofthe disclosed processes such as those of Fig. 3 and Fig. 4.
- a general purpose computer 70 as shown in Fig. 7 typically includes a central processing unit 72 (CPU) coupled to random access memory 74(RAM) and program memory 76 via a data bus 78.
- the general purpose computer 70 may be connected to the network 10 in order to receive reports, and may provide commands to devices on the network in order to control the network configuration.
- the sub-elements ofthe synchronization module 12 may be implemented as special purpose electronic hardware. Additionally, in either a hardware or software embodiment, the functions performed by the different elements within the synchronization module 12 may be combined in varying arrangements of hardware and software.
- the network manager 11 receives status information 17 from the network 10 and provides a monitoring capability to determine the status of manageable devices within the network 10.
- the status information 17 may include a hardboot message, sent from a manageable device when the manageable device is initialized. This message, also called a "HELLO" message, may be sent to the network manager 10 from the manageable device's signaling mechanism only following a hard boot ofthe device.
- the receipt of such a message by the synchronization module 12 may be referred to as an initialization event (HE) with respect to the device 100 that sends the "HELLO" message.
- HE initialization event
- Such an initialization event (HE) facilitates the capability ofthe synchronization module 12 to distinguish between a hard boot of a device and a temporary loss of contact due to the device being too busy to respond to the manager 11.
- Another type of status information 17 includes a response by a device to a poll request by the synchronization module 12.
- the model control module 20 is coupled to a polling manager 23.
- the polling manager 23 provides poll requests 24 to devices ofthe network 10 to query the status of these devices.
- the polling manager may include an internal clock or timer to trigger the transmission of a poll request 24.
- the polling frequency is approximately 10 seconds.
- a device may retum a message indicative of contact being established between the network manager 12 and the device.
- the receipt by the synchronization module 12 of a message indicative of such a situation may be referred to as a "contact established" (CE) event.
- CE contact established
- the status information 17 may also include results from a discovery process. Discovery, in this context, refers to querying the appropriate devices or ports ofthe devices directly to obtain information regarding their connectivity or other status.
- the discovery mechanism 25 may also include an entirely separate interface from that ofthe other status information 17 and status inquiries 18, and may use a standard management protocol such as SNMP (Simple Network Management Protocol).
- the SNMP standard defines a set of variables that a device must keep to comply with SNMP, and includes adjacency information regarding other devices adjacent to the device being discovered.
- SNMP information typically includes three parts: structure of management information (SMI); management information base (MIB); and the SNMP protocol itself.
- SMI and MIB define and store the set of managed entities as defined by the discovery mechanism 25, while the SNMP protocol enables information to be conveyed to and from the managed devices.
- the discovery mechanism 25 may exist as a separate off-the-shelf package.
- the model control module 20 may control the discovery mechanism 25 to perform such a discovery process.
- the discovery mechanism 25 provides discovery commands 26 to the appropriate devices ofthe network 10, and receives responses (as status information 17) to the discovery commands 26.
- the discovery mechanism 25 may also provide further discovery commands 26 based upon the results of earlier discovery commands. Accordingly, a discovery process may result in a "discovery successful" (DS) event in which the discovery mechanism 25 was able to acquire the desired information regarding a device, or a “discovery failure” (DF) event, in which a discovery process was not successfully completed with respect to a particular device.
- DS discovery successful
- DF "discovery failure"
- poll requests 24 and discovery commands 26 are included in the status inquiries 18 shown in Fig. 1. Additionally, other techniques may be used to acquire information regarding the status of devices within the network 10, and are meant to be within the scope ofthe term "status information.”
- a reset mechanism 27 may be controlled by the model control module 20 to provide a reset command 28 to a particular device.
- the reset command 28 is typically a control message sent to the device, and the device contains hardware and software that performs the reset.
- a reset in this context, refers to an initialization, for example an initialization of control parameters within the device. This is typically different from a hard reboot ofthe device, which sets all of the hardware and software ofthe device to a predetermined state. For example, a hard reboot typically results in a loss of data stored in random access memory (RAM), while a reset may maintain some of this data.
- RAM random access memory
- the model control module 20 receives status information 17.
- the status information 17 may include a polling result, a discovery result, a hard reboot message (e.g., "HELLO"), as well as other information.
- the actual reports that make up the status information 17 may be received directly by the polling manger 23 and the discovery mechanism 25, which in turn may provide appropriate messages to the model control module 20 to initiate the events, for example those described above (HE, CE, CL, DS, DF).
- the model control module 20 updates or initializes a device model 21 in accordance with the status information received in step 30.
- step 34 the model control module 20 initiates action, when appropriate, for example to gain more information regarding the status of a device.
- Fig. 4 shows more detail of steps 32 and 34 of Fig. 3.
- the previous state of a device is determined. Step 40 may be achieved by accessing a memory location that stores the status information of a device, or by querying a model such as the object- oriented model of the device models 210 described above.
- the new state ofthe device is determined based upon the previous state and the status information received in step 30.
- the new state may be one of a plurality of states that include an "unknown" state, an "initialized” state, a "lost” state, and an "established after lost" state.
- the plurality of states may include a different set of states, for example "up,” “down,” and “unknown.”
- the synchronization module 12 may more accurately represent the status of each device 100, and be less subject to lost messages or devices that are too busy to respond to queries.
- the "unknown" state of a device is indicative that the synchronization module 12 has no information regarding the status of the device. Often, in such a case, invoking the discovery mechanism may be the most effective manner in which to determine the status of such a device.
- the "initialized" state of a device is indicative that the device has been discovered and is ready to be controlled by the control module 14. This is typically the most common state of a device, because it is a state in which the device may be controlled by the control module 14. If a device is in the "lost" state, the device usually cannot be contacted. The device may have been too busy to respond to a status inquiry, or the device may have failed or been recently rebooted. Generally, actions are taken by the network manager 11 to work around the lost device, until information is received from the lost device indicative ofthe lost device changing status.
- a device In an "established after lost” state, a device may be contacted and is ready to be controlled by the control module 14. This state is similar to the "initialized” state, but is indicative that a successful discovery has not yet been performed with respect to the device.
- Step 42 may be performed through the use ofthe state machine 22 shown in Fig. 2.
- the state machine 22 may be implemented as a hardware machine as discussed earlier, or may be implemented in software as predetermined logic, as predetermined memory locations, or as a lookup table.
- the model control module 20 provides the previous state determined in step 40 and the status information received in step 30 to the state machine, and the state machine provides in response a new state that represents the current status ofthe device.
- Fig. 5 shows four different states including the unknown state 50, the initialized state 52, the lost state 54, and the established after lost state 56.
- Fig. 5 also shows the events described earlier (HE, DF, DS, CE, and CL), and the state change that takes place, if any, as a result of a particular event being received for a device that is in a particular state.
- the device model 21 is updated in accordance with the new state, or if the new state is the same as the old state, then no action may be taken.
- the device model 210 may be enabled or disabled. Enabling and disable a device model 210 are actions which allow the control module 14 to know whether certain actions may be performed with respect to the device represented by the particular device model. When a device model 210 is disabled, for example, the control module 14 may avoid attempting to set up a connection through the device represented by the disabled device model 210. Instead, the control module 14 may instead attempt to use another device, for example, in order to provide an appropriate path for data.
- a disabled device model is indicative that the device is not usable by the control module 14, while an enabled device model is indicative that the device is usable by the control module 14.
- Steps 46 and 48 illustrate more detail of step 34 of Fig. 3.
- an appropriate action is determined based upon the previous state of a device and the status information received in step 30.
- This action includes action related to the synchronization ofthe device, and is typically different from the control of a device which is for the purposes of network control.
- the actions which may be taken include: initiating polling; triggering discovery; and providing a reset command. Each of these actions are described above with reference to Fig. 2.
- the state machine 22 may also be used to determine the action to take with respect to a device. As with the state change function ofthe state machine 22 described above, this function ofthe state machine 22 may be implemented in several ways, including accessing memory locations or lookup tables, for example.
- Fig. 6 is a state table 60 which indicates the action to be taken in response to the synchronization module 12 receiving new device information about a device having a previous state.
- Four previous states are defined in the four columns, the four states being similar to the four states shown in Fig. 5.
- the rows ofthe state table 60 are indicative ofthe event, for example one ofthe events HE, DF, DS, CE, and CL.
- the intersection between the column representing the previous state of a device model 210 and the row representing the event indicated by the information received in step 30 shows the appropriate action.
- a device For example, if a device was previously in an unknown state and a discovery successful (DS) event is received with respect to the device, then the device would be reset and the model for that device would be enabled, so that the corresponding device in the network 10 could be controlled by the control module 14. Additionally, as shown in Fig. 5, in such a case the state of the device model would be changed from "unknown" to "initialized.”
- DS discovery successful
- a first example is how a network manager 11 synchronizes, during initialization, with the network devices 100 controlled by the network manager 11.
- the network manager 11 typically has information regarding at least one network device before initializing, so that the network manager 1 1 can perform discovery on this network device to leam about the remainder ofthe network 10.
- the network manager 11 When the network manager 11 is presented with a new device (the device could be a network address), it creates a device model 210 for that device and sets the device model 210 to the "unknown" state.
- the network manager 11 then invokes the discovery mechanism 25 on the device.
- the network manager 11 also registers the device with the polling mechanism 23 so it can appropriately monitor the device.
- the polling can be asynchronous with the discovery mechanism 25 so it is not guaranteed which event may be received from the manager's mechanisms first - the contact established (CE), or a discovery successful (DS) or discovery failure (DF).
- the model control module 20 only the success from the discovery mechanism 25 (e.g., a DS event) will cause the model control module 20 to reset the device 100 and enable the device model 210, and transition the device model 210 to the "initialized” state.
- This state is the most common running state ofthe device model, and is indicative that the device 100 is now ready to be manipulated by the network manager 11.
- the only event which can remove the device model from the initialized state is a contact lost (CL) event.
- CE contact established
- a second example is a situation in which a network manager 1 1 is in synchronization with the manageable devices 100 ofthe network 11, but then one ofthe devices, for example a switch, hard resets for some reason.
- the device model ofthe device may be in the "initialized" state prior to the hard reset.
- the network manager's polling mechanism 23 discovers that it can not contact the device (because the device has recently had a hard reset), and thus sends a contact lost (CL) event to the model control module 20.
- the model control module 20 disables the model ofthe switch and transitions the model state to "lost."
- the synchronization module 12 may rediscover the switch because the devices adjacent to the switch may have changed from the time that the switch had a hard reset.
- the switch will be active, and the polling manager 23 will send a contact established (CE) event to the model control module 20.
- CE contact established
- the synchronization module 12 resets the switch so that the switch is initialized properly.
- the synchronization module 12 then enables the model ofthe switch, and sets the model state to "established after lost.”
- the switch will likely send the "HELLO" message, letting the synchronization model know that the switch was successfully reset, and may now be rediscovered.
- the model control module 20 disables the model ofthe switch and triggers the discovery mechanism 25.
- the device model 210 is disabled because after discovery is complete, the switch might be reset again for any of a number of reasons, for example by the control module 14. In such a situation, there should be no manipulation ofthe switch until after the reset, because all ofthe information that was just programmed into the switch by the control module 14 will be lost when it is reset.
- the switch model state is set to "initialized.”
- a device becomes too busy to respond and as a result, the polling mechanism 22 reports that it has lost contact with the particular network device by providing a CL event. Similar actions are performed as in the second example, but this time a "HELLO" message will not be received, because the device was not hard reset, and the associated device model will thus remain in the "established after lost” state. As was noted before, this state is similar to the "initialized” state, so that the device may be manipulated by the control module 14.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP96944845A EP0868800B1 (en) | 1995-12-22 | 1996-12-19 | Method and apparatus for determining the status of a device in a communication network |
AT96944845T ATE222672T1 (en) | 1995-12-22 | 1996-12-19 | METHOD AND DEVICE FOR DETERMINING THE STATE OF A DEVICE IN A COMMUNICATIONS NETWORK |
AU13359/97A AU700957B2 (en) | 1995-12-22 | 1996-12-19 | Method and apparatus for determining the status of a device in a communication network |
DE69623127T DE69623127T2 (en) | 1995-12-22 | 1996-12-19 | METHOD AND DEVICE FOR DETERMINING THE STATE OF A DEVICE IN A COMMUNICATION NETWORK |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/577,429 US5734642A (en) | 1995-12-22 | 1995-12-22 | Method and apparatus for network synchronization |
US08/577,429 | 1995-12-22 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO1997023974A1 true WO1997023974A1 (en) | 1997-07-03 |
WO1997023974A9 WO1997023974A9 (en) | 1997-09-25 |
Family
ID=24308686
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1996/020081 WO1997023974A1 (en) | 1995-12-22 | 1996-12-19 | Method and apparatus for determining the status of a device in a communication network |
Country Status (6)
Country | Link |
---|---|
US (1) | US5734642A (en) |
EP (1) | EP0868800B1 (en) |
AT (1) | ATE222672T1 (en) |
AU (1) | AU700957B2 (en) |
DE (1) | DE69623127T2 (en) |
WO (1) | WO1997023974A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2319937A (en) * | 1996-11-29 | 1998-06-03 | Nec Corp | Multi-integrated agent system |
US6308174B1 (en) | 1998-05-05 | 2001-10-23 | Nortel Networks Limited | Method and apparatus for managing a communications network by storing management information about two or more configuration states of the network |
DE10251906A1 (en) * | 2002-11-07 | 2004-05-19 | Siemens Ag | Making inventory of components connected to network involves sending inventory request message from requesting component to all other connected components, which send inventory response messages |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6236654B1 (en) * | 1997-02-14 | 2001-05-22 | Advanced Micro Devices, Inc. | Method and apparatus for managing learning in an address table in memory |
US6633924B1 (en) | 1997-10-02 | 2003-10-14 | Charles Wu | Object synchronization between objects stores on different computers |
US6125369A (en) * | 1997-10-02 | 2000-09-26 | Microsoft Corporation | Continuous object sychronization between object stores on different computers |
JPH11122244A (en) * | 1997-10-20 | 1999-04-30 | Fujitsu Ltd | Managing device for large scaled network |
JP3604898B2 (en) * | 1998-03-31 | 2004-12-22 | キヤノン株式会社 | Network device management apparatus and method, recording medium |
US6353612B1 (en) * | 1998-06-19 | 2002-03-05 | Brocade Communications Systems, Inc. | Probing device |
US6360255B1 (en) * | 1998-06-25 | 2002-03-19 | Cisco Technology, Inc. | Automatically integrating an external network with a network management system |
JP4105293B2 (en) * | 1998-06-30 | 2008-06-25 | 富士通株式会社 | Network monitoring system, monitoring device and monitored device |
US6839757B1 (en) * | 1999-04-28 | 2005-01-04 | 2Wire, Inc. | System and method for automatically discovering accessible services on a computer network and providing automatic access thereto |
US6584503B1 (en) | 1999-07-07 | 2003-06-24 | International Business Machines Corporation | Method, system and program for establishing network contact |
JP4218152B2 (en) * | 1999-10-28 | 2009-02-04 | ソニー株式会社 | Communication method and communication system |
JP4178697B2 (en) * | 1999-11-18 | 2008-11-12 | ソニー株式会社 | Portable information processing terminal, information input / output system, and information input / output method |
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 |
US6748445B1 (en) | 2000-02-01 | 2004-06-08 | Microsoft Corporation | System and method for exchanging data |
US8396950B1 (en) * | 2000-03-02 | 2013-03-12 | Rockstar Consortium Us Lp | Method and apparatus for the fast detection of connectivity loss between devices in a network |
US7752024B2 (en) * | 2000-05-05 | 2010-07-06 | Computer Associates Think, Inc. | Systems and methods for constructing multi-layer topological models of 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 |
US7237138B2 (en) | 2000-05-05 | 2007-06-26 | Computer Associates Think, Inc. | Systems and methods for diagnosing faults in computer networks |
AU2001261275A1 (en) * | 2000-05-05 | 2001-11-20 | Aprisma Management Technologies, Inc. | Systems and methods for isolating faults in computer networks |
US7272644B1 (en) * | 2000-09-29 | 2007-09-18 | Intel Corporation | Internet based network topology discovery |
US20070294409A1 (en) * | 2000-09-29 | 2007-12-20 | Arvind Kumar | Internet based network topology discovery |
US20050157654A1 (en) * | 2000-10-12 | 2005-07-21 | Farrell Craig A. | Apparatus and method for automated discovery and monitoring of relationships between network elements |
US7383191B1 (en) * | 2000-11-28 | 2008-06-03 | International Business Machines Corporation | Method and system for predicting causes of network service outages using time domain correlation |
US20020141351A1 (en) * | 2000-12-07 | 2002-10-03 | Maltz David A. | Method and system for validating network transformation instructions |
US7797409B1 (en) * | 2001-01-26 | 2010-09-14 | Sobha Renaissance Information Technology | System and method for managing a communication network utilizing state-based polling |
US20040044762A1 (en) * | 2001-02-22 | 2004-03-04 | Peacock Kimberly Roseanne | Methods and apparatus for controlling internet protocol traffic in a wan or lan |
US6966015B2 (en) * | 2001-03-22 | 2005-11-15 | Micromuse, Ltd. | Method and system for reducing false alarms in network fault management systems |
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 |
US7516208B1 (en) | 2001-07-20 | 2009-04-07 | International Business Machines Corporation | Event database management method and system for network event reporting system |
US20030076809A1 (en) * | 2001-08-03 | 2003-04-24 | Coaxmedia, Inc. | Methods for detecting and polling downstream modems |
US20050286685A1 (en) * | 2001-08-10 | 2005-12-29 | Nikola Vukovljak | System and method for testing multiple dial-up points in a communications network |
US7139823B2 (en) * | 2001-08-23 | 2006-11-21 | International Business Machines Corporation | Dynamic intelligent discovery applied to topographic networks |
US7085830B1 (en) | 2001-10-18 | 2006-08-01 | Network Equipment Technologies, Inc. | System and method to manage inconsistency problems between network management systems and network elements |
US7363368B2 (en) | 2001-12-24 | 2008-04-22 | International Business Machines Corporation | System and method for transaction recording and playback |
US7676606B1 (en) * | 2002-04-24 | 2010-03-09 | Cisco Technology, Inc. | Method and system for monitoring and controlling status of programmable devices |
US7339484B2 (en) * | 2002-06-27 | 2008-03-04 | Hewlett-Packard Development Company, L.P. | Event-driven discovery method and apparatus |
US20040162898A1 (en) * | 2003-02-14 | 2004-08-19 | Rich Jason H. | Dedicated networked device monitoring system |
US20060005232A1 (en) * | 2004-06-30 | 2006-01-05 | Wilson Richard A Jr | Path utilization device discovery |
US20060050716A1 (en) * | 2004-09-03 | 2006-03-09 | Intel Corporation | Generic flow control state machine for multiple virtual channel types in the advanced switching (AS) architecture |
JP4576249B2 (en) * | 2005-01-27 | 2010-11-04 | 株式会社クラウド・スコープ・テクノロジーズ | Network management apparatus and method |
US8060592B1 (en) * | 2005-11-29 | 2011-11-15 | Juniper Networks, Inc. | Selectively updating network devices by a network management application |
JP4727715B2 (en) * | 2008-12-12 | 2011-07-20 | 株式会社日立製作所 | Stream data processing method and system |
US9456356B2 (en) * | 2009-10-15 | 2016-09-27 | Apple Inc. | Methods for synchronizing data in a network |
US8345660B2 (en) | 2010-05-06 | 2013-01-01 | Digi International Inc. | Wireless mesh network controller synchronization |
US9684499B2 (en) * | 2013-06-30 | 2017-06-20 | Dropbox, Inc. | Systems and methods for facilitating installation of software applications |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1993010495A1 (en) * | 1991-11-22 | 1993-05-27 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable devices in a computer network |
US5226120A (en) * | 1990-05-21 | 1993-07-06 | Synoptics Communications, Inc. | Apparatus and method of monitoring the status of a local area network |
US5299207A (en) * | 1991-03-15 | 1994-03-29 | Fujitsu Limited | Centralized supervisory system for transmission network elements and method of supervising transmission network elements |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3159979B2 (en) * | 1990-05-01 | 2001-04-23 | 株式会社日立製作所 | Network management display processing system and method |
US5261044A (en) * | 1990-09-17 | 1993-11-09 | Cabletron Systems, Inc. | Network management system using multifunction icons for information display |
JP3160017B2 (en) * | 1991-08-28 | 2001-04-23 | 株式会社日立製作所 | Network management display device |
US5535335A (en) * | 1992-12-22 | 1996-07-09 | International Business Machines Corporation | Method and system for reporting the status of an aggregate resource residing in a network of interconnected real resources |
US5485455A (en) * | 1994-01-28 | 1996-01-16 | Cabletron Systems, Inc. | Network having secure fast packet switching and guaranteed quality of service |
US5590120A (en) * | 1995-10-31 | 1996-12-31 | Cabletron Systems, Inc. | Port-link configuration tracking method and apparatus |
-
1995
- 1995-12-22 US US08/577,429 patent/US5734642A/en not_active Expired - Lifetime
-
1996
- 1996-12-19 AT AT96944845T patent/ATE222672T1/en not_active IP Right Cessation
- 1996-12-19 WO PCT/US1996/020081 patent/WO1997023974A1/en active IP Right Grant
- 1996-12-19 DE DE69623127T patent/DE69623127T2/en not_active Expired - Fee Related
- 1996-12-19 EP EP96944845A patent/EP0868800B1/en not_active Expired - Lifetime
- 1996-12-19 AU AU13359/97A patent/AU700957B2/en not_active Ceased
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5226120A (en) * | 1990-05-21 | 1993-07-06 | Synoptics Communications, Inc. | Apparatus and method of monitoring the status of a local area network |
US5299207A (en) * | 1991-03-15 | 1994-03-29 | Fujitsu Limited | Centralized supervisory system for transmission network elements and method of supervising transmission network elements |
WO1993010495A1 (en) * | 1991-11-22 | 1993-05-27 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable devices in a computer network |
Non-Patent Citations (1)
Title |
---|
STINSON W ET AL: "A STATE-BASED APPROACH TO REAL-TIME TELECOMMUNICATIONS NETWORK MANAGEMENT", PROCEEDINGS OF THE NETWORK OPERATIONS AND MANAGEMENT SYMPOSIUM (NOM, MEMPHIS, APR. 6 - 9, 1992, vol. 1 - 2 - 03, 1 January 1992 (1992-01-01), INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, pages 520 - 532, XP000344720 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2319937A (en) * | 1996-11-29 | 1998-06-03 | Nec Corp | Multi-integrated agent system |
GB2319937B (en) * | 1996-11-29 | 2001-06-27 | Nec Corp | Multi-integrated agent system |
US6308174B1 (en) | 1998-05-05 | 2001-10-23 | Nortel Networks Limited | Method and apparatus for managing a communications network by storing management information about two or more configuration states of the network |
DE10251906A1 (en) * | 2002-11-07 | 2004-05-19 | Siemens Ag | Making inventory of components connected to network involves sending inventory request message from requesting component to all other connected components, which send inventory response messages |
DE10251906B4 (en) * | 2002-11-07 | 2006-03-02 | Siemens Ag | Method and arrangement for the inventory of network components connected to a network |
Also Published As
Publication number | Publication date |
---|---|
AU700957B2 (en) | 1999-01-14 |
EP0868800A1 (en) | 1998-10-07 |
DE69623127D1 (en) | 2002-09-26 |
US5734642A (en) | 1998-03-31 |
DE69623127T2 (en) | 2003-05-15 |
EP0868800B1 (en) | 2002-08-21 |
AU1335997A (en) | 1997-07-17 |
ATE222672T1 (en) | 2002-09-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5734642A (en) | Method and apparatus for network synchronization | |
WO1997023974A9 (en) | Method and apparatus for determining the status of a device in a communication network | |
US7017082B1 (en) | Method and system for a process manager | |
US6009274A (en) | Method and apparatus for automatically updating software components on end systems over a network | |
US9529878B2 (en) | System and method for supporting subnet manager (SM) master negotiation in a network environment | |
US6097718A (en) | Snapshot routing with route aging | |
US5287103A (en) | Method and apparatus for providing local area network clients with internetwork identification data | |
US7415519B2 (en) | System and method for prevention of boot storms in a computer network | |
US6983397B2 (en) | Method, system, and program for error handling in a dual adaptor system where one adaptor is a master | |
US6941350B1 (en) | Method and apparatus for reliably choosing a master network manager during initialization of a network computing system | |
US9270482B2 (en) | Method for activating a network component of a vehicle network system | |
US6389129B1 (en) | Interface for interfacing client programs with network devices in a telecommunications network | |
JPH10313329A (en) | Fault permission communication method/system | |
US7308700B1 (en) | Network station management system and method | |
JP3312595B2 (en) | Terminal connection control method and system in communication processing system composed of multiple processes | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals | |
Cisco | Using Terminals |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TR TT UA UG UZ VN AM AZ BY KG KZ MD RU TJ TM |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
COP | Corrected version of pamphlet |
Free format text: PAGES 1/7-7/7,DRAWINGS,REPLACED BY NEW PAGES 1/6-6/6;DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1996944845 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP Ref document number: 97523764 Format of ref document f/p: F |
|
WWP | Wipo information: published in national office |
Ref document number: 1996944845 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWG | Wipo information: grant in national office |
Ref document number: 1996944845 Country of ref document: EP |