Method and apparatus for monitoring the status of non-pollable devices in a computer network

• US 5,812,750 A
• Filed: 03/27/1997
• Issued: 09/22/1998
• Est. Priority Date: 09/17/1990
• Status: Expired due to Term

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Cabletron Systems Incorporated (Extreme Networks, Inc.)
• Inventors: Dev, Roger H., Nelson, Mark H.
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US08/824,492
• Time in Patent Office: 544 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 395/180, 395/182.02, 395/182.19, 395/183.01, 395/183.06, 395/183.13, 395/200.01, 395/200.02, 395/200.1, 395/200.11, 395/200.3 , 395/200.5, 395/200.54, 395/200.56, 395/200.59
• US Class Current: 714/4.12
• CPC Class Codes: B63B 5/06 Decks; Shells
• CPC Class Codes: G06F 11/2257 using expert systems
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3041 where the computing system component is an input/output interface interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00
• CPC Class Codes: G06F 11/3048 where the topology of the computing system or computing system component explicitly influences the monitoring activity, e.g. serial, hierarchical systems
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3096 wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
• CPC Class Codes: G06F 11/32 with visual or acoustical indication of the functioning of the machine
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/88 Monitoring involving counting
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time
• CPC Class Codes: H04L 41/0609 based on severity or priority
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/0677 Localisation of faults
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/0695 the faulty arrangement being the maintenance, administration or management system
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/40 : using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 43/00 : Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/065 : related to network devices
• CPC Class Codes: H04L 43/0811 : by checking connectivity
• CPC Class Codes: H04L 43/0817 : by checking functioning
• CPC Class Codes: H04L 43/0829 : Packet loss
• CPC Class Codes: H04L 43/10 : Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/103 : with adaptive polling, i.e. dynamically adapting the polling rate
• CPC Class Codes: H04L 43/16 : Threshold monitoring
• CPC Class Codes: Y10S 706/916 : Electronic or computer, internal or network, circuit

Abstract

A network management system includes a user interface, a virtual network and a device communication manager. The virtual network includes models which represent network entities and model relations which represent relations between network entities. Each model includes network data relating to a corresponding network entity and one or more inference handlers for processing the network data to provide user information. The system can poll or communicate with certain network entities and can infer the status of network connectors and other network entities for which polling is impossible or impractical. The system performs a fault isolation technique wherein the fault status of a network device is suppressed when it is determined that the device is not defective. User displays include hierarchical location views and topological views of the network configuration. Network devices are represented on the displays by multifunction icons which permit the user to select additional displays showing detailed information regarding different aspects of the corresponding network device.

Claims

1. A system for determining a contact status in a computer network, the computer network including a plurality of interconnected network entities including communicating network entities and at least one non-communicating network entity, the system including:

a virtual network machine comprising models of the network entities and model relations representing relations between the network entities, each model including a number of attributes and one or more inference handlers, the attributes being data which define characteristics of the network entity being modeled, and the one or more inference handlers having a means for performing a process on the data upon an occurrence of predetermined events in the model which trigger the inference handler, the attributes including a contact status for a corresponding network entity;

a device communication manager connected to the network and to the virtual network machine for communicating with the communicating network entities to obtain operational information as to the status of the communicating network entities and updating a corresponding contact status attributes in corresponding models; and

the one or more inference handlers having means for using the operational information as to the communicating network entities and the model relations between the at least one non-communicating network entity and the communicating network entities to infer the contact status of the at least one non-communicating network entity and updating its contact status.

2. The system of claim 1, wherein the means for using the operational information monitors the contact status of models of communicating network entities having a predetermined relation to the at least one non-communicating network entity.

3. The system of claim 1, wherein the device communication manager includes means for polling the communicating network entities at predetermined intervals.

4. The system of claim 1, further including a user interface connected to the virtual network machine for providing the contact status of the at least one non-communicating network entity to a user.

5. The system of claim 1, wherein the means for using the operational information infers a lost contact status of the at least one non-communicating network entity when all network entities connected to the at least one non-communicating network entity have a lost contact status.

6. The system of claim 1, wherein the means for using the operational information infers an established contact status of the at least one non-communicating network entity when at least one network entity connected to the at least one non-communicating network entity has an established contact status.

7. The system of claim 1, wherein the means for using the operational information infers an initial contact status of the at least one non-communicating network entity when all network entities connected to the at least one non-communicating network entity have an initial contact status.

8. The system of claim 1, wherein the means for performing a process updates the models and model relations when a network entity is added to or removed from the network.

9. The system of claim 1, wherein the operational information obtained by the device communication manager includes a status of ports in a ported network entity and updates the corresponding contact status attributes.

10. The system of claim 1, wherein the models and model relations include network devices, geographical locations of network devices, topological groupings of network devices, and software applications being executed on network devices.

11. The method of claim 1, wherein the model relations represent connections between network entities and hierarchial relationships between network entities.

12. The system of claim 1, wherein the means for performing a process are triggered by predetermined events including a change in attributes in the same model, a change in attributes in a different model, and predefined events or changes in the models or model relations.

13. The system of claim 1, wherein the means for performing a process generates an alarm condition when the model attributes meet a predetermined criteria.

14. The system of claim 1, wherein the device communication manager automatically receives operational information without polling.

15. The system of claim 1, wherein the models include location models which represent portions of the network geographically associated with a building, country, floor, panel, rack, region, room, section, sector, site, or the world.

16. The system of claim 1, wherein the models include topological models which represent network devices that are topologically associated with a local area network or subnetwork.

17. The system of claim 1, wherein the models include models that represent components of network devices including circuit boards and ports.

18. The system of claim 1, wherein the models include models of software applications including data relay, network monitor, terminal server, and end-point operations.

19. The system of claim 1, wherein the attributes include an attribute flag which indicates that the data is maintained in the network entity being modeled.

20. The system of claim 1, wherein the one or more inference handlers produce an output including one or more of attribute changes, creation or destruction of models, and alarms.

21. The system of claim 1, wherein an inference handler in one of the models of the network entities includes means for monitoring an attribute in another model of the models of the network entities.

22. The system of claim 1, further including a user interface connected to the virtual network machine and an icon manager for automatically communicating a change of attribute data to the user interface.

23. The system of claim 1, wherein the virtual network machine is a programmed digital computer.

24. The system of claim 1, further comprising a user interface connected to the virtual network machine, the user interface including means for, in response to user selections, providing topological views of interconnections between the network entities in the network, the topological views having a hierarchial relationship.

25. The system of claim 1, further comprising a user interface connected to the virtual network machine, the user interface including means for, in response to user selections, providing location views of locations of the network entities in the network, the locations views having a hierarchial relationship.