Apparatus and method for managing network and computer-readable recording medium thereof

[0001] 1. Field of the Invention

[0002] The present invention generally relates to apparatuses for managing a network, methods for managing the network and computer-readable recording media having a program recorded thereon for causing a computer to manage the network, and more particularly to an apparatus for managing a network, a method for managing the network and a computer-readable recording medium having a program recorded thereon for causing a computer that monitor devices connected to the network to manage the network.

[0003] 2. Description of the Related Art

[0004] Conventionally, in order to handle problems of a distributed system, an agent, which is a program for monitoring computers and network devices (such as a router, a hub or the like) that are connected to a network, is provided to each device in the network. A management server collects configuration information from each agent and displays a map based on the configuration information. The management server receives a problem event, such as a SNMP (Simple Network Management Protocol) trap, sent by the agent when a problem has occurred. Then, the management server blinks an icon indicating the configuration information corresponding to the device where the problem event occurred, so as to notify an administrator of the problem with that device.

[0005] Thus, in a case in which a plurality of devices (routers, hubs, computers, and the like) are connected to a network, a problem occurring at a single device may influence other devices. As a result, an icon indicating by the configuration information corresponding to each of the other devices ends up blinking. This makes it difficult to distinguish which device originally caused the problem. Since special knowledge is required to specify which device originally caused the problem, it is difficult to immediately deal with the problem.

[0006] Further, the network structure and connected devices (routers, hubs, computers, and the like) to be managed may change. It is desired to recognize this change and automatically specify a problem device.

[0007] It is a general object of the present invention to provide an apparatus for managing a network, a method for managing the network and a computer-readable recording medium having a program recorded thereon for causing a computer to manage the network in which the above-mentioned problems are eliminated.

[0008] A more specific object of the present invention is to provide an apparatus for managing a network, a method for managing the network and a computer-readable recording medium having a program recorded thereon for causing a computer to manage the network, which can notify an administrator of a device actually causing a problem in the network.

[0009] The above objects of the present invention are achieved by an apparatus for monitoring devices connected to a network, including: a relationship object maintaining part maintaining dependent information for each relationship between devices connected to the network, the dependent information indicating how one device influences another device when the one device causes a problem; an event table maintaining part maintaining device information, which identifies a device in the network, indicated by an event received from the device; an event collecting part collecting each event received from the devices and controlling the event table maintaining part to maintain the device information when the event indicates a problem; and a problem alarm notifying part determining, based on the dependent information maintained by the relationship object maintaining part, whether or not each of the devices identified by the device information maintained by the event table maintaining part influences another device by the problem, and specifying which device is causing the problem in accordance with a result of the determination.

[0010] According to the present invention, the device that actually causes a problem can be specified and it is possible to inform the administrator which device causes the problem.

[0011] The above objects of the present invention are achieved by a method for managing a network, including the steps of: (a) maintaining dependent information for each relationship between devices connected to the network, the dependent information indicating how one device influences another device when the one device causes a problem; (b) maintaining device information, which identifies a device in the network, indicated by an event received from the device; (c) collecting each event received from the devices and executing the step (b) to maintain the device information when the event indicates a problem; and (d) determining, based on the dependent information maintained in the step (a), whether or not each of the devices identified by the device information maintained in the step (b) influences another device by the problem, and specifying which device is causing the problem in accordance with a result of the determination.

[0012] According to the present invention, it is possible to provide the method for managing a network in that the device that actually causes a problem can be specified and it is possible to properly inform the administrator which device causes the problem.

[0013] The above objects of the present invention are achieved by a computer-readable recording medium having a program recorded thereon for causing a computer to manage a network, including the codes of: (a) maintaining dependent information for each relationship between devices connected to the network, the dependent information indicating how one device influences another device when the one device causes a problem; (b) maintaining device information, which identifies a device in the network, indicated by an event received from the device; (c) collecting each event received from the devices and executing the code (b) to maintain the device information when the event indicates a problem; and (d) determining, based on the dependent information maintained by the code (a), whether or not each of the devices identified by the device information maintained by the code (b) influences another device by the problem, and specifying which device is causing the problem in accordance with a result of the determination.

[0014] According to the present invention, it is possible for the computer that installed the program from computer-readable recording medium to specify the device actually causing a problem and properly inform the administrator which device causes the problem.

[0029] An embodiment including operations of an apparatus for managing a network according to the present invention will now be described with reference to FIG. 1 through FIG. 12.

[0030] FIG. 1 is a diagram of a system configuration according to an embodiment of the present invention.

[0031] In FIG. 1, a server 1, as an apparatus for managing a network according to the present invention, monitors routers, hubs, and machines connected to network as devices to be managed and includes a relationship information generating part 2, a configuration information collecting part 3, an event correlating part 4, an event collecting part 5 and a relationship information generating rule 6.

[0032] The server 1 loads programs stored in a recording medium (not shown in FIG. 1) in to a main memory such as a RAM and then executes the program concerning each process described later.

[0033] The relationship information generating part 2 is used to generate relationship information between the devices to be managed (for example, routers, hubs and machines). The relationship information generating part 2 further stores the relationship information as a relationship object 9 of an object database (object DB).

[0034] The configuration information collecting part 3 collects configuration information of the devices to be managed that are connected to the network and further registers the collected configuration information as a management object 8 of an object database (object DB).

[0035] The event correlating part 4 is used to check and select a relationship between events. That is, the event correlating part 4 refers to the relationship object 9 corresponding to each event sent from agents 21 shown in FIG. 2 under management control, and checks and selects the relationship between the events.

[0036] The event collecting part 5 is used to collect the events from the agents 21 managing the devices.

[0037] The relationship information generating rule 6 is a rule for automatically generating relationship information between the devices to be managed (Refer to FIG. 8).

[0038] The object DB 7 is used to register and manage objects. That is, the object DB 7 registers and manages the management objects 8 and the relationship objects 9.

[0039] The management object 8 is used to register and manage the configuration information of each device to be managed (Refer to FIG. 10A and FIG. 10B).

[0040] The relationship object 9 is used to register relationship information between the devices to be managed (Refer to FIG. 10C).

[0041] An event table 10 stores events received from the agents 21 managing the devices (Refer to FIG. 11 and FIG. 12). Operations of the server 1 will be now described.

[0042] The event collecting part 5 receives and collects the events sent from the agents 21 shown in FIG. 2. The event correlating part 4 refers to a dependent relationship stored in the relationship object 9 and distinguishes a problem event indicating that a device is actually causing a problem. Thereafter, the event correlating part 4 outputs the problem event (for example, an icon representing the device is blinked at a display unit to indicate where the problem is occurring).

[0043] When the server 1 is notified that a device to be managed is changed or additionally provided, information in the management object 8 is changed or information of the additional device is provided as an additional management object 8. Also, the relationship information generating part 2 changes information in the relationship object 9 or generates an additional relationship object 9 based on the relationship information generating rule 6 corresponding to the device that is changed or additionally provided.

[0044] Furthermore, while information in the management object 8 is changed or information of the additional device is provided as the additional management object 8 when the server 1 is notified that a device to be managed is changed or additionally provided, the relationship information generating part 2 displays devices registered as the management objects 8. The relationship information generating part 2 changes information in or generates an additional relationship object 9 when a dependent relationship between the devices displayed is registered by selecting one of various types of the dependent relationship.

[0045] Accordingly, by providing the management object 8 managing the device and the relationship object 9 managing the dependent relationship between the devices, it is possible to add or change the device to be managed, and also specify and display the device actually causing a problem based on the events.

[0046] FIG. 2 is a diagram illustrating a display according to the present invention. In FIG. 2, a large display window as a main display window displays icons representing a router 11, hubs 12 and 14, and machines 13 and is based on configuration information for each device to be managed (for example, routers, hubs, machines and the like) in the management object 8. The main display window further displays arrows indicating dependent relationships based on the relationship object 9.

[0047] A small display window positioned at a lower left side is a sub-display window for indicating a dependent relationship between the devices to be managed. In this case, when the hub 12 indicated by a letter (a) and the machine 13 indicated by a letter (b) are clicked and selected by a user, the hub 12 and the machine 13 are displayed as a left icon and a right icon, respectively, in the sub-display window as indicated by dotted lines from the main display window. The user selects any one of the following settings for “INFLUENCE ON THE LEFT DEVICE WHEN A PROBLEM OCCURS AT THE RIGHT DEVICE” at an upper part of the sub-display window:

• • [0048] CRITICAL
  • [0049] LESS CRITICAL
  • [0050] NO INFLUENCE
    In this case, it is assumed that “NO INFLUENCE” is selected. Similarly, the user selects any one of the following settings for “INFLUENCE ON THE RIGHT DEVICE WHEN A PROBLEM OCCURS AT THE LEFT DEVICE” at a lower part of the sub-display window:
  • [0051] CRITICAL
  • [0052] LESS CRITICAL
  • [0053] NO INFLUENCE
    In this case, it is assumed that “CRITICAL” is selected. Information selected as shown in the sub-display window is registered as a hub-machine instance (the relationship object 8) as shown in FIG. 10C described later. By this selection, an arrow (c) indicated by a solid line from the hub 12 to the machine 13 is displayed in the main display window in FIG. 2.

[0054] As described above, the icons representing the devices connected to the network and being managed can be displayed on the main display window based on the configuration information of the management object 8. Moreover, the sub-display window can be displayed by selecting two icons for the devices being managed and displayed in order to define the dependent relationship between the two devices. By indicating the dependent relationship (defined as any one of “CRITICAL”, “LESS CRITICAL” and “NO INFLUENCE”) between two devices, the indicated dependent relationship is registered in the relationship object 9 and can be displayed on the main display window by a directed arrow.

[0055] It should be noted that each agent 21 in FIG. 2 is a program that is provided in each device to be managed and sends an event indicating a problem occurrence to the server 1.

[0056] FIG. 3 is a diagram for explaining objects according to the present invention. In FIG. 3, a status is shown in which the management objects 8 and the relationship objects 9 are registered for the devices shown on the left side of the main display window in FIG. 2. Dotted squares show the management objects 8 and the relationship objects 9 automatically generated when a hub 14 and a machine 15 in FIG. 2 are additionally provided.

[0057] As described above, the configuration information of each of the devices connected to the network to be managed (routers, hubs, machines and the like) is registered as a management object 8. Therefore, as shown in the left side of FIG. 2, it is possible to display each device to be managed in a hierarchical structure and each dependent relationship showing a dependent direction by an arrow. Further, when additional devices to be managed are provided, additional management objects 8 and relationship objects 9 are generated. Then the hub 14, the machine 15, the arrow showing the dependent relationship between the hub 12 and the hub 14, and the arrow showing the dependent relationship between the hub 14 and the machine 15 in FIG. 2 are additionally displayed. That is, it is possible to dynamically display added devices. Details thereof will now be described.

[0058] FIG. 4 is a flowchart for explaining operations according to the present invention. FIG. 4 shows steps for generating a relationship object by using the main display window and the sub-display window in FIG. 2.

[0059] In a step S1 of FIG. 4, a user clicks on an icon.

[0060] In a step S2, a process menu is displayed. That is, in response to the click on the icon, the process menu (including a relating process in this case) is displayed.

[0061] In a step S3, it is checked whether or not the relating process is selected from the process menu displayed in the step S2. When the relating process is selected (YES), a step S4 is executed. When the relating process is not selected (NO), another process that is selected by the user is executed in a step S8.

[0062] In the step S4, a destination device to be related is selected. That is, the user selects devices to be managed in order to create the relationship object 9 by clicking on, for example, the icon of the hub 12 indicated by the letter (a) and the icon of the machine 13 indicated by the letter (b).

[0063] In a step S5, the sub-display window is displayed for the relationship information. That is, the two devices selected in the step S5 to be managed (in this case, the icon of the hub 12 indicated by the letter (a) and the icon of the machine 13 indicated by the letter (b)) are displayed, and the following information is displayed for the user to indicate the dependent relationship.

• • [0064] for “INFLUENCE ON THE LEFT DEVICE WHEN PROBLEM OCCURS AT THE RIGHT DEVICE”
    • [0065] CRITICAL
    • [0066] LESS CRITICAL
    • [0067] NO INFLUENCE
  • [0068] for “INFLUENCE ON THE RIGHT DEVICE WHEN PROBLEM OCCURS AT THE LEFT DEVICE”
    • [0069] CRITICAL
    • [0070] LESS CRITICAL
    • [0071] NO INFLUENCE

[0072] In a step S6, the dependent relationship is selected. With regard to the above two directions (left to right and right to left) displayed in the sub-display window on the lower left side, it is assumed that “CRITICAL” and “NO INFLUENCE” are selected for “INFLUENCE ON THE LEFT DEVICE WHEN PROBLEM OCCURS AT THE RIGHT DEVICE” and “INFLUENCE ON RIGHT DEVICE WHEN PROBLEM OCCURRED AT LEFT DEVICE”, respectively.

[0073] In a step S7, an instance for a hub-machine class is generated. That is, an instance (a relationship object 9) for a hub-machine class described in FIG. 10C is generated.

[0074] As described above, after the relating process is selected from the process menu, devices to be managed (for example, the hub 12 indicated by the letter (a) and the machine 13 indicated by the letter (b)) are selected to define a relationship. Then, the sub-display window in FIG. 2 is displayed. Thus, the dependent relationships can be selected on the sub-display window (in this case, “CRITICAL” and “NO INFLUENCE” are selected for “INFLUENCE ON LEFT DEVICE WHEN PROBLEM OCCURRED AT RIGHT DEVICE” and “INFLUENCE ON THE RIGHT DEVICE WHEN PROBLEM OCCURS AT THE LEFT DEVICE”). Then, it is possible to generate a relationship object 9 such as shown in FIG. 10C described later.

[0075] FIG. 5 is a flowchart for explaining a rule process for providing an additional node. FIG. 5 shows steps for automatically generating a relationship object 9 in response to an addition of a device to be managed.

[0076] In a step S11 of FIG. 5, a rule for adding a node is executed.

[0077] In a step S12, a hub having the same MAC (Media Access Control) address as the additional node is searched for. For example, when a user wishes to add the machine 15 of FIG. 2, the rule process starts to search for a hub having the same MAC address as the machine 15 that is the additional node. It is assumed that a port of the hub 14 is directly connected to the machine 15. Thus, the port maintains the same MAC address as the machine 15.

[0078] In a step S13, it is checked whether or not the same MAC address is found. In this case, it is determined that the same MAC address is found (YES) since the hub 14 has the same MAC address as the machine 15. In a step S14, an instance of a hub-machine class (the relationship object 9 described later in FIG. 10C) is automatically generated in accordance with steps S21 through S24.

[0079] In a step S21, an object ID=02 for a hub is substituted for an object ID1. That is, the object ID=02 for the hub 14 as a parent in FIG. 2 is input in a column of the object ID1 (parent) of the relationship object 9 in FIG. 10C so that the object ID=02 is registered.

[0080] In a step S22, an object ID=03 for a machine is substituted for an object ID2. That is, the object ID=03 for the machine 15 as a child in FIG. 2 is input in a column of the object ID2 (child) of the relationship object 9 in FIG. 10C so that the object ID=03 is registered.

[0081] In a step S23, “CRITICAL” is substituted for a dependence 1->2. That is, in accordance with a rule for automatically creating an instance (relationship object 9), for example, a hub-machine instance in FIG. 8 described later, “CRITICAL” is substituted for the dependence 1->2. That is, “CRITICAL” is input in a column of the dependence 1->2 so that a dependent relationship from the hub 14 as a parent to the machine 15 as a child in FIG. 2 is “CRITICAL”.

[0082] In a step S24, “NO INFLUENCE” is substituted for a dependence 2->1. That is, in accordance with the rule for automatically creating the instance (relationship object 9), for example, the hub-machine instance in FIG. 8 described later, “NO INFLUENCE” is substituted for the dependence 2->1. That is, “NO INFLUENCE” is input in a column of the dependence 2->1 so that a dependent relationship from the machine 15 as a child to the hub 14 as a parent in FIG. 2 is “NO INFLUENCE”.

[0083] As described above, when devices to be managed (routers, hubs, machines or the like) are additionally provided, in accordance with a corresponding rule (for example, when a machine is additionally connected to a hub, the rule in FIG. 8 described later is used), it is possible to automatically create a relationship object 9 for registering a dependent relationship between the additional device and another device to be managed.

[0084] FIG. 6 is a flowchart for explaining a process for generating the relationship object according to the present invention.

[0085] In a step S31 of FIG. 6, a management object 8 for registering a device detected in another process is created. That is, for example, the process creates a management object 8 (such as a management object 8 in FIG. 10A or FIG. 10B) indicating that the configuration information of a device to be managed, which device is additionally provided and detected in the network, is registered.

[0086] In a step S32, additional information is received. That is, the process receives additional information (such as a MAC address and the like) necessary for creating a relationship object 9 from the agent 21 arranged for monitoring the devices.

[0087] In a step S33, a class is distinguished. That is, the process distinguishes a class for the detected device and another device creating the dependent relationship.

[0088] In a step S34, a rule is searched for. That is, the process searches for a rule applying to the class distinguished in the step S33. For example, a rule in FIG. 8 applying to the class for a hub and a machine is retrieved.

[0089] In a step S35, the rule is executed. That is, a relationship object 9 is automatically created by the rule applying to the class, which rule was found in the step S34. For example, the relationship object 9 shown in FIG. 10C is created in accordance with the rule in FIG. 8. Then, the steps S34 and S35 are repeated to complete all relationship objects 9.

[0090] As described above, when a management object 8 is detected, a rule for a device corresponding to the management object 8 and another a device directly connected thereto is applied and then dependent relationship between the two devices is generated as a relationship object 9.

[0091] FIG. 7 is a diagram showing a class structure according to the present invention. At least the following information as shown in FIG. 7 is registered.

• • [0092] Hub class:
    • [0093] Object ID
    • [0094] Port No[ ]
    • [0095] MAC Address[ ]
  • [0096] Hub-MachineRel class:
    • [0097] Object ID1
    • [0098] Object ID2
    • [0099] Dependency (dependent relationship)
  • [0100] Machine class:
    • [0101] Object ID
    • [0102] MAC Address[ ]
      It should be noted that the information described above is shown in FIG. 7.

[0103] Therefore, the class structure is used. Instances of the hub class and the machine class (for example, see FIG. 10A and FIG. 10B) are defined as the management objects 8 (for example, see FIG. 10A and FIG. 10B) and the instance of the Hub-MachineRel class is defined as the relationship object 9 (for example, see FIG. 10C).

[0104] FIG. 8 is a diagram showing a rule for generating relationship according to the present invention. The rule is used to automatically generate a relationship object 9 between a hub and a machine. The first few lines:

• • [0105] CLASS 1 OF MANAGEMENT OBJECT TO BE MANAGED:
    • [0106] Hub CLASS
  • [0107] CLASS 2 OF MANAGEMENT OBJECT TO BE MANAGED:
    • [0108] Machine CLASS
      define a generating rule for a relationship object 9 for the Hub class and the Machine class. In the same way, another relationship object 9 for other classes is defined.

[0109] A condition is defined as follows:

• • [0110] CLASS OF RELATIONSHIP OBJECT TO BE GENERATED WHERE A MAC Address PROPERTY FOR CLASS 1 IS THE SAME AS A MAC Address PROPERTY FOR CLASS 2.

[0111] When the condition above is true, a Hub-MachineRel class is generated. Properties of the relationship object 9 are registered as follows:

• • [0112] Dependency PROPERTY<-INSTANCE OF CLASS 2 DEPENDS ON INSTANCE OF CLASS 1
  • [0113] Dependency PROPERTY<-INSTANCE OF CLASS 1 DOES NOT INFLUENCE INSTANCE OF CLASS 2

[0114] In accordance with the rule shown in FIG. 8, the relationship object 9 where the hub and the machine are mutually connected is generated. For example, the relationship object 9 shown in FIG. 10C can be automatically created.

[0115] FIG. 9 is a flowchart for explaining a process for additionally providing a hub according to the present invention.

[0116] In a step S41 of FIG. 9, a rule for additionally provide a hub is executed.

[0117] In a step S42, a hub having the same MAC address is searched for. That is, for example, when the hub 14 in FIG. 2 is additionally provided, a hub having the same MAC address as the hub 14 is searched for. In the case of FIG. 2, the hub 12 indicated by the letter (a), which is above the hub 14, is found. The same MAC address as the hub 14 additionally provided is searched for from port information managed in the management object 8 of the hub 12 indicated by the arrow (a) where any one of ports is connected to the hub 14.

[0118] In a step S43, it is judged whether or not the hub having the same MAC address as the hub 14 is found. When it is judged that the hub having the same MAC address as the hub 14 is found (YES), the process advances to a step S44. On the other hand, when it is judged that the hub having the same MAC address as the hub 14 is not found (NO), the process is terminated since there is no hub having the same MAC address as the hub 14.

[0119] In the step S44, an instance for a hub—hub class is generated. A relationship object 9 for a dependent relationship between hubs is generated by executing steps S51 through S54.

[0120] In a step S51, an object ID of a parent hub is substituted for an object ID1 (parent). Similarly to the relationship object 9 in FIG. 10C, the object ID of the parent hub is input in a column of the object ID1 (parent) of the instance (relationship object 9) of the hub—hub class so as to be registered.

[0121] In a step S52, an object ID of a child hub is substituted for an object ID2 (child) Similarly to the relationship object 9 in FIG. 10C, the object ID of the child hub is input in an column of the object ID2 (child) of the instance (relationship object 9) of the hub—hub class so as to be registered.

[0122] In a step S53, “CRITICAL” is substituted for the dependence 1->2. That is, “CRITICAL” is substituted for the dependence 1->2 in accordance with a rule for generating the instance (relationship object 9) of the hub—hub class that is similar to a rule for automatically generating an instance (relationship object 9) of the hub-machine class in FIG. 8. In other words, the dependent relationship from the parent hub to the child hub is defined as “CRITICAL”, similarly to the column of the dependence 1->2 of FIG. 10C.

[0123] In a step S54, “NO INFLUENCE” is substituted for the dependence 2->1. That is, similarly to the column “DEPENDENCE 2->1” in FIG. 10. Therefore, when a device (hub) to be managed is additionally provided to connect to another device (hub) to be managed, it is possible to automatically generate a relationship object 9 to register a dependence relationship between the device (hub) to be managed and another device (hub) to be managed, in accordance with a rule corresponding to a class of the two devices.

[0124] In a step S45, a machine having the same MAC address X is searched for.

[0125] In a step S46, it is judged whether or not the machine having the same MAC address X is found. When the machine is found (YES), the process advances to a step S47. On the other hand, when the machine is not found (NO), the process is terminated.

[0126] In the step S47, an instance (relationship object 9) of a hub-machine class is generated in a similar method to the steps S21 through S24 of FIG. 5 (see FIG. 10C).

[0127] As described above, when the hub 14 and the machine 15 in FIG. 2 are additionally provided, based on the management objects 8 where the configuration information of the additional hub 14 and machine 15 is registered, it is possible to automatically register the dependent relationship between hubs and the dependent relationship between the hub and the machine as the relationship objects 9, respectively.

[0128] FIG. 10A is a diagram showing an instance (management object 8) of a hub. In FIG. 10A, the instance (management object 8) of the hub shows a registration of the configuration information described therein.

• • [0129] hub ID: hub 0
  • [0130] object ID: 02
  • [0131] destination MAC address per port or its own MAC address

[0132] As described above, a function of the hub automatically registers (learns) the MAC address of a destination device (hub, router, machine or the like) to be managed per port in the management object 8 for the hub. Thus, as described in flowcharts of FIG. 5 and FIG. 9, it is possible to automatically determine that two devices are mutually connected when the MAC address of the destination device to be managed corresponds to that maintained in the hub. Also, it is possible to automatically generate the relationship object 9 where the dependent relationship between the two devices is registered.

[0133] FIG. 10B is a diagram showing an instance (management object 8) of a machine. The configuration information is registered in the instance (management object 8) of the machine.

• • [0134] hub ID: machine 0
  • [0135] object ID: 03
  • [0136] MAC address: Mac1

[0137] As described above, the object ID and the MAC address are registered in the management object 8 of the machine. Based on the MAC address such as described in flowcharts of FIG. 5 and FIG. 9, it is possible to automatically determine that two devices are mutually connected when the MAC address of the device to be managed corresponds to that maintained in the destination hub. Also, it is possible to automatically generate the relationship object 9 where the dependent relationship between the two devices is registered.

[0138] FIG. 10C is a diagram showing an instance (relationship object 9) of a hub-machine class. In FIG. 10C, the instance (relationship object 9) between the devices described in FIG. 10A and FIG. 10B shows a registration of the configuration information described therein.

• • [0139] hub ID: hub-machine 0
  • [0140] object ID1 (parent): 02 (object ID for a device to be managed as a parent)
  • [0141] object ID2 (child): 03 (object ID for a device to be managed as a child)
  • [0142] dependence 1->2 (dependent relationship from the parent to the child): “CRITICAL”
  • [0143] dependence 2->1 (dependent relationship from the child to the parent): “NO INFLUENCE”

[0144] As described above, the dependent relationship from the parent to the child and the dependent relationship from the child to the parent are automatically registered in accordance with the rule. In FIG. 11 and FIG. 12 described later, when a problem event is sent from the agent 21 being managed to the server 1, influence of events can be suppressed by the dependent relationship. Thus, it is possible to make only an icon of FIG. 2 representing a device actually causing a problem to blink on the main display window in FIG. 2 so as to inform the administrator of that problem.

[0145] FIG. 11 is a flowchart for explaining a process for monitoring the devices according to the present invention.

[0146] In a step S61 of FIG. 11, an event from the agent 21 is received. That is, the event collecting part 5 included in the server 1 in FIG. 1 receives the event including information about a problem or the like of the device being managed, which event is sent from the agent 21.

[0147] In a step S62, it is checked by searching for a relationship object 9 whether or not a related management object exists. That is, information (such as an object ID), which is included in the problem event, of the device is registered. For example, it is checked whether or not the relationship object 9 such as described in FIG. 10C exists.

[0148] In a step S63, an event of the management object 8 related to the relationship object 9 is searched for.

[0149] In a step S64, it is checked whether or not the event is found. When it is determined that the event is found (YES), a suppress-flag for the event is set to “ON” in an event table 10 such as shown in FIG. 12, in step S65. On the other hand, when it is determined that the event is not found (NO), the process is terminated.

[0150] As described above, in a case in which the process finds the relationship object 9 as shown in FIG. 10C including information of the device (object ID), which is included in the event received in the step S61, it is determined based on the dependent relationship determined in the relationship object 9 whether or not the event for the registered management object 8 is defined in the event table 10 in FIG. 12. When the event is defined, the suppress-flag is set to “ON” so that an alarm for the icon of the device corresponding to the event is suppressed. When the dependent relationship in the relationship object 9 is “CRITICAL” and another event for another device in a connection direction has been previously received and registered in the event table 10 in FIG. 12, the suppress-flag is set to “ON” so as not to display the alarm. Therefore, it is possible to make an alarm based on an event extracted from all events received, which event indicates where the problem is actually caused.

[0151] FIG. 12 is a diagram showing an event table according to the present invention. Every event sent from the agents 21 connected to the network is registered in the event table 10. In accordance with the flowchart in FIG. 11, when an event is registered, based on the registered relationship object 9 of the management object 8 defined in the received event, the suppress-flag of the event of the management object 8 for an influenced device is set to “ON” so as not to make an alarm. On the other hand, an icon representing a device for which the suppress-flag is set to “OFF” is blinked on the main display window in FIG. 2. Accordingly, only an icon representing a device actually causing a problem is blinked so that the administrator can easily realize and specify the device causing the problem.

[0152] FIG. 13 is a block diagram of a hardware configuration that implements the server as the apparatus for managing a network according to the present invention.

[0153] The server 1 includes a CPU 11, a memory unit 12, an output unit 13, an input unit 14, a display unit 15, a storage unit 16, a CD-ROM driver 17 and a communication unit 18 which are mutually connected by a bus B. The CPU 11 controls the entire system in accordance with a program resident in the memory unit 12. In addition, the CPU 11 executes the process for defining a relationship between two devices, the rule process for providing an additional node and for monitoring the devices that are described above. The memory unit 12 includes a ROM and a RAM. Also, the memory unit 12 temporarily stores programs, events sent from the agents 21, various data and the like during the execution of the processes. The output unit 13 includes a printer or the like. The input unit 14 includes a keyboard and a mouse for the administrator to input information into the system, for example, in order to setup the network system, but is not limited to only these input devices.

[0154] The display unit 15 displays the main display window, the sub-display window, results of various processes, or the like.

[0155] The storage unit 16 includes a hard disk unit and stores various data and programs. Also, the storage unit 16 is used for the object DB 7 and the event table 10 in FIG. 1. In accordance with instructions from the CPU 11, the CD-ROM driver 17 reads information from a CD-ROM 20 set in the CD-ROM driver 17 and then provides the information to the storage unit 16. For example, various programs according to the present invention are provided by the CD-ROM 20. That is, the programs read from the CD-ROM 20 are installed in the storage unit 16 through the CD-ROM driver 17. It should be noted that a recording medium is not limited to a CD-ROM, but other computer-readable recording media such as a magnetic disk, a magnetic tape, an optical disk, a magneto optical disk, a semiconductor memory or the like may be used.

[0156] The communication unit 18 is used to receive or send information concerning events from or to the agents 21.

[0157] As described above, according to the present invention, the management object 8 for managing the information related to the devices connected to the network and the relationship object 9 for managing the dependent relationships between the devices are provided. The processes for additions and changes of the devices are dynamically executed. Moreover, the device that actually causes a problem can be specified and the alarm is displayed so as to inform the administrator that the problem is occurring at the device. Therefore, even in the distributed network system where a device configuration is dynamically changed or a device is additionally provided, it is possible to specify a device (a router, a hub, or a machine), which actually causes a problem, based on the events sent from the devices being managed and to inform the administrator of the problem on the display.

[0158] The present invention is not limited to the specifically disclosed embodiments, variations and modifications, and other variations and modifications may be made without departing from the scope of the present invention.

[0159] The present application is based on Japanese Priority Application No. 11-306365 filed on Oct. 28, 1999, the entire contents of which are hereby incorporated by reference.