JP2006094283A - Method and device for monitoring network - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently monitor a device, in which various connecting modes connected to a network are monitored, from a remote place. <P>SOLUTION: In a method for monitoring the network of a network monitor system, a plurality of the devices 11 to 13 or the like to be monitored connected to the network 100 are monitored concentrically from the remote place. In the method, each discriminating information of the devices to be monitored (such as 11 or 13) previously made to inform from each device to be monitored 11 to 13 and another device to be monitored (such as 12) connected to the devices to be monitored is related mutually and stored in a memory 35. In the method, the presences of relations are decided according to the related informations of the memory in trouble informations with their own discriminating informations from each device to be monitored 11 to 13 or the like, and the related trouble informations are related and given to a monitor 50. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a network monitoring method and apparatus, and more particularly, to a network monitoring method and apparatus in which a support member monitors a monitored apparatus (such as a server and its connection apparatus) connected to a network via a remote network monitoring apparatus. .

  FIG. 10 is a diagram for explaining the prior art. A typical network monitoring system in which a support person monitors a plurality of customer systems 20a and 20b connected to a network via a remote maintenance center (corresponding to a network monitoring device) 60. Is shown. In this example, the servers A and C and the storage B are monitoring target devices. Hereinafter, these devices are also referred to as monitored devices.

  In the customer system 20a, the servers A and C and the server D of another company are connected to a network (not shown) such as the Internet or a dedicated line, while referring to the storage B, providing network services such as content distribution and Perform customer management. The server C also references another company's storage E. In this state, each detection unit detects an abnormality of a plurality of layers in hardware and software in the own device, and the detection unit of the servers A and C also detects an abnormality related to access to the storage B. The detected abnormality is notified to the remote maintenance center 60 via the router, and is monitored by a support person who operates the monitoring monitors 70a and 70b.

In such a network monitoring system, even if there is only one major cause of abnormality, the maintenance center 60 is notified of a plurality of faults by a plurality of routes, so it is difficult for support personnel to analyze and isolate the cause. It was. Specific examples will be described below.
(1) When an abnormality occurs in the storage B accessed by the server A, the abnormality is detected in the server A and the storage B and notified to the maintenance center 60.
(2) When an abnormality occurs in the storage B accessed by the servers A and C, the abnormality is detected in the servers A and C and the storage B and notified to the maintenance center 60.
(3) Even if there is only one major failure, an abnormality is detected in a plurality of layers (kernel, OS, middleware, application, etc.) due to the hierarchical structure of hardware and software, and is notified to the maintenance center 60 separately.
(4) It is necessary to constantly monitor whether or not the connection path (router or the like) between each monitored device and the maintenance center is usable. As a monitoring method, a notification periodically sent from the monitored device to the maintenance center is confirmed by the maintenance center, or the maintenance center periodically accesses each monitoring device for confirmation. In any case, if an abnormality occurs in the infrastructure of the connection path, all monitored devices related to this cannot be monitored from the maintenance center. At this time, the maintenance center 60 detects an abnormality for each of the monitored devices A to C.
(5) When the monitored devices A to C are installed in one room, if a failure occurs in the shared equipment (such as an air conditioner), a temperature abnormality occurs in the monitored devices A to C. Notifies the maintenance center 60 of the abnormality separately.

  For this reason, it is not only difficult to analyze and isolate the cause by support personnel, but also when a maintenance center is monitored by multiple support personnel, multiple support personnel may respond to a single failure. Even when one support person handles, it is necessary to check the system configuration of the monitored device every time a failure notification is received, and determine whether the connected device is abnormal, etc. It was.

In this regard, conventionally, there has been shown a failure message display device that makes it easy to analyze the cause of a failure detected at multiple locations or multiple layers within a single device, based on a hierarchical structure between predefined components. (Patent Document 1).
Japanese Patent Laid-Open No. 2001-256032 (summary, figure)

  However, the above-described method is only for assisting in identifying the cause of the failure by means of a unique solution incorporated in the device in advance, and cannot be employed when monitoring a variety of monitored devices via a network. In addition, when a high-level failure determination means is provided on the monitored device side, the monitored device is expensive and complicated, and applying and operating a common rule for monitored devices provided by various vendors, It is extremely difficult in practice.

  The present invention has been made in view of the above-described problems of the prior art, and the object of the present invention is to provide a network monitor capable of efficiently and remotely monitoring monitored devices having various connection modes connected to a network with a simple configuration. It is to provide a method and apparatus.

  The above problem is solved by the configuration of FIG. That is, the network monitoring method of the present invention (1) is a network monitoring method of a network monitoring system that remotely monitors a plurality of monitored devices 11 to 13 connected to the network 100 from the remote, Storing each identification information of the monitored device (for example, 11 or 13) notified from ˜13 etc. and other monitored devices (for example, 12) connected thereto in the memory 35 in association with each other; The failure monitor with its own identification information from the devices 11 to 13 and the like is determined based on the association information of the memory, the presence / absence of association between the identification information is determined, and the failure notification determined to be related is associated with each other to monitor monitor 50 ( And a step of providing to a support member who refers to it).

  According to the present invention (1), each monitored device may notify in advance the identification information of the own device and other monitored devices connected to the own device. It can be easily applied to a wide variety of monitored devices connected to the network. Further, since the failure notifications from each monitored device are associated with each other according to the association information of the memory and provided to the monitoring monitor, failure notifications issued from a plurality of devices can be monitored remotely and efficiently.

  The network monitoring device of the present invention (2) is a network monitoring device of a network monitoring system for remotely monitoring a plurality of monitored devices connected to a network from the remote device, and the monitored devices notified from each monitored device in advance. And configuration information processing means for associating each identification information of other monitored devices connected thereto with each other and storing them in the memory, and a failure notification accompanied by identification information from each monitored device according to the association information of the memory Monitoring information processing means for determining presence / absence of association between identification information and providing a monitoring monitor in association with failure notifications determined to be associated with each other is provided.

  In the present invention (3), in the above-mentioned present invention (2), the configuration information processing means may be configured such that the identification information of another monitored device connected to the first monitored device is connected to the second monitored device. By matching the identification information of the monitored device, the identification information of the first and second monitored devices and the other monitored devices connected thereto are stored in the memory in association with each other. Therefore, even complicated connection relationships can be easily extracted and associated.

In the present invention (4), in the present invention (2) or (3), the monitoring information processing means accepts designation information of a failure notification providing destination specifying a certain monitored apparatus from the outside in advance, According to the association information, a failure notification from each monitored device determined to be associated with the specified monitored device is provided to the designated monitor for monitoring the failure notification. Therefore, even if the support staff does not know the connection configuration of each monitored device, the failure notification reflecting the connection configuration can be efficiently monitored.

  According to the present invention (5), in any one of the above-mentioned present inventions (2) to (4), there is provided group ID setting means capable of setting a desired group ID to a plurality of monitored devices by external setting, The processing means receives failure notification providing destination specifying information specifying a certain monitored device from the outside, and has a group ID set to the specified monitored device, so that it is the same as the group ID. A failure notification from each monitored device to which a group ID is set is provided to the designated monitor for monitoring the failure notification. Therefore, even if the support staff does not know the installation status of each monitored device, the failure notification reflecting the installation environment can be efficiently monitored.

  As described above, according to the present invention, it is possible to monitor remotely a variety of monitored devices connected to a network efficiently from a remote location, which greatly contributes to improving the efficiency of network monitoring.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of the invention will be described in detail with reference to the accompanying drawings. Note that the same reference numerals denote the same or corresponding parts throughout the drawings.

  FIG. 1 is a diagram showing a configuration of a network monitoring system according to an embodiment, and collects and manages configuration information (component information, connection information with peripheral devices) of each monitored device on the network monitoring device side by a simple method. In addition, a case is shown in which notification processing from each monitored device can be efficiently performed based on the information.

  In the figure, 100 is a network such as the Internet or a dedicated line, 10a and 10b are connected to the network 100, and customer systems a, b, and 11 for providing various network services such as content distribution and managing customers at financial institutions. , 13 are servers A and C connected to the network 100, 12 is a storage B as a peripheral device connected to the servers A and C, and 15A to 15C are configuration information about the monitored devices A to C (including connection information), respectively. Is detected and notified to the network monitoring device, and a detection unit that detects an abnormality caused by hardware or software of the monitored devices A to C and notifies the network monitoring device, 200 is the monitoring network, and 14 is the monitoring network 200 Router for connection, 30 is network monitoring of customer systems 10a, 10b, etc. A network monitoring device to perform, 32 is a configuration information processing unit that collects and manages configuration information (including connection information) from monitored devices A to C, and 31 is a network monitoring information from monitored devices A to C ( Monitoring information processing unit that collects and manages (including failure information) and provides it to support personnel, 33 is a storage device such as an HDD that stores various files and data, 34 is a monitoring information file that accumulates network monitoring information, and 35 is A configuration information table for recording and managing the configuration (component) information of the monitored device and the information of the connected device, 36 is a router, and 50a and 50b are monitor devices for support personnel to monitor the monitoring information.

  The monitored devices A to C collect the identification information for identifying the device itself, the component configuration of the device itself, and the identification information of the peripheral device connected to the device (hereinafter also referred to as a connection device) and collect it in the network monitoring device 30. A function for notifying, and a function for detecting an abnormality of the own apparatus and, in some cases, an abnormality of the connection apparatus and notifying the network monitoring apparatus 30 of the abnormality.

  That is, the detection units 15A to 15C detect and collect the component configuration of the own device and the connection status with the connection device periodically or when the configuration of the own device is changed, and create a configuration information file. At the same time, this is packetized and notified to the network monitoring device 30. Further, when an abnormality (failure) of the own device or an abnormality when accessing the connection device is detected, information regarding the abnormality is packetized and transmitted to the network monitoring device 30. The detection unit 15 detects abnormalities in a plurality of hardware and software locations and a plurality of layers, and notifies the network monitoring device 30 each time.

  FIG. 8A shows a packet file format of an example notified to the network monitoring device 30 (when the attached file is component information and connection device information). In the figure, the “monitored device identification information” column contains identification information of the monitored device that is the packet transmission source. In the “message” column, a message indicating whether this packet has a configuration information file or monitoring information (including failure information) is mounted. In the “component information” column, component information related to notification of configuration information and failure information is mounted. If the configuration information is mounted in the message, component information and connection device information constituting the configuration information are mounted thereafter. Further, when the monitoring information is mounted in the message, the attached file is mounted with the monitoring information in which the contents representing the status of the apparatus are mounted. In the “connection information” column, identification information of the peripheral device B connected to the monitored devices A and C is loaded. Note that “component information” and “connecting device information” are also attached to a message in the sense that they are attached to a message.

  FIG. 8B shows the file format of the component information, and FIG. 9 shows a simple description (specific example) of the component information column.

  Returning to FIG. 1, when receiving the configuration information packet from the monitored device, the configuration information processing unit 32 of the network monitoring device 30 creates the configuration information table 35 based on the component information of the device and the information of the connected device. Or update.

  FIG. 7 shows the format of the configuration information table. The configuration information table includes a monitored device identification information column, a component information column, and a connected device identification information column, and the network monitoring device 30 performs efficient network monitoring by referring to these pieces of information. Storage information storage flags for monitoring information, a group ID for identifying a monitored device in a common environment, and support information for monitoring the device are provided. These details will become clear from the following description.

  The monitoring information processing unit 31 associates the monitoring information (including failure information) sent from each monitored device according to the configuration information table 35 and provides it to a predetermined monitoring monitor 50. The support staff monitors the notification provided by the network monitoring device 30 on the monitor 50, analyzes the contents when the notification is detected, identifies the cause, and performs component replacement, setting change, etc. if necessary. Hereinafter, the network monitoring method according to the embodiment will be described in detail.

  FIG. 2 is a flowchart of the configuration information table creation / update process according to the embodiment. When the network monitoring device 30 receives the configuration information notification packet from the monitored device, the configuration information table is input to this processing of the configuration information processing unit 32. In step S11, the configuration information table 35 is searched with the identification information of the monitored device. In step S12, it is determined whether or not there is a corresponding device column. If there is, the content of the corresponding column of the configuration information table 35 is updated with the component information of the attached file and the connected device information if present in step S13, and the process is exited. If there is no corresponding device column in the determination in step S12, a line of identification information of the monitored device is added to the configuration information table 35 in step S14, and the component information of the attached file is present in the corresponding column. In this case, the connected device information is recorded, and the process is exited.

  FIG. 7 shows the recorded contents of the configuration information table 35 when the configuration information notification packet is received and processed. The identification information of the server A is “A001”, and the OS product name “XOS” is recorded in the control information column. Although not shown, other columns such as CPU are also recorded in the same manner. Furthermore, the storage B is connected to the server A, and the identification information “B001” of the storage B is recorded in the connected device information column. Similarly, the identification information of the server C is “C001”, and “ZOS” is recorded in the component information column. Furthermore, the storage B is also connected to the server C, and “B001” is recorded in the identification information column. The same applies to the storage B. However, in this example, the storage device B, which is a peripheral device, notifies only the component information and does not notify the connection device information. In this way, the configuration information table 35 is created and updated.

  In FIG. 7, connection device information (“A001”) and (“B001”) with parentheses are recorded in the connection device information column of storage B, but these are added by the processing of FIG. 3 described below. Is.

  FIG. 3 is a flowchart of the connection device information column adjustment processing according to the embodiment. When the recorded content of the configuration information table 35 is changed or periodically, this processing of the configuration information processing unit 32 is input. In step S21, connection device identification information {thing without () in FIG. 7} is extracted from the connection device information column in the configuration information table 35. In step S22, the monitored device identification information column of the configuration information table 35 is searched with the extracted identification information. In step S23, it is determined whether or not there is a corresponding device column. If there is, the monitored device identification information in the column in which the connected device (not marked) is extracted in step S21 is added to the connected device column of the corresponding device in step S24. If it is determined in step S23 that there is no corresponding device column, the process in step S24 is skipped. In step S25, it is determined whether or not the above processing has been completed for all connection device information (unmarked) in the configuration information table 35. If not, the process returns to step S21. Also, when the process is completed, the process is exited.

  A specific example of the connection device information column adjustment process will be described with reference to FIG. First, the storage B identification information “B001” is extracted from the connected device information column of the server A, which matches the storage B identification information “B001” in the monitored device identification information column. As a result, the identification information (“A001”) of server A is marked and added to the connected device information column of storage B. Next, the storage B identification information “B001” is also extracted from the connected device information column of the server C, and this also matches the storage B identification information “B001” in the monitored device identification information column. As a result, the identification information (“C001”) of the server C is marked and added to the storage device connection device information column.

  4 and 5 are flowcharts (1) and (2) of the network monitoring process according to the embodiment, and FIG. 4 is a monitor that collects and edits monitoring information (including failure information) notified from each monitored device. The network monitoring process notified to the side is shown.

  There are three modes “0” to “2” in the notification mode to the monitor side. In mode “0”, failure notifications are accumulated for a predetermined period from the beginning, and are collectively notified to the monitor side. In mode “1”, the first notification is sent to the monitor side, the subsequent notifications are accumulated for a predetermined period, and then these are collectively notified to the monitor side. In mode “2”, the first notification is sent to the monitor side, the subsequent notifications are accumulated for a predetermined period, and these are not notified to the monitor side thereafter.

In FIG. 4, when the network monitoring device 30 receives a monitoring (including failure) packet from the monitored device, the monitoring information processing unit 31 inputs this packet. In step S31, the configuration information table 35 is searched with the identification information of the monitored device included in the notification. In step S32, it is determined whether or not there is a corresponding device column. If there is, it is further determined in step S33 whether or not there is connected device information, and if there is, in step S34 it is determined whether or not the monitoring information accumulation flag is “1”. If the accumulation flag is not “1”, it means that the latest first failure notification packet has been received from the monitored apparatus, so the accumulation flag of the related apparatus is set to “1” in step S35. This setting basically sets both the monitored device that has received the failure notification and the accumulation flag of the connected device to “1”.

  Some of these setting patterns will be specifically described with reference to FIG. First, when a failure notification from the server A is first received, both the storage flags of the server A and the storage B are set to “1”, thereby associating the failure information of the server A and the storage B. When a failure notification is first received from the server C, both storage flags of the server C and storage B are set to “1”. In this case, failure information of the server C and storage B is associated. On the other hand, when a failure notification is first received from the storage B, the three storage flags of the storage B and the servers A and C are both set to “1”. In this case, the storage B and the servers A and C Fault information is associated.

  In addition, when a failure notification is received from the server C or A after receiving a failure notification from the server A or C, the failure of the servers A and C and the storage B also occurs because these are connected to the common storage B. Information is associated.

  Note that when the connection of the storage B is detected when the failure notification from the server A is first received, the presence of the server C can be further detected from the connection information column of the storage B. The failure information of the servers A and C and the storage B may be associated with each other. In this way, it is possible to efficiently associate the failure information of the system having a complicated connection relationship. In FIG. 7, the accumulation flag of the server C in this case is indicated by “(1)”.

  At the same time, when the accumulation flag is set between other monitored devices and the failure information is associated, the accumulation flags are grouped so that they can be distinguished.

  Returning to FIG. 4, in step S36, a timer for a predetermined time (several seconds to several minutes) associated with the setting process in step S35 is started corresponding to the group. In step S37, it is determined whether or not the notification mode to the monitoring monitor 50 is “0”. If it is not “0”, the notification content attached to the fault packet in step S38 is stored in the corresponding buffer of the monitoring information file 34. To do. That is, when the notification mode is “0”, accumulation starts from the first failed packet. Then, this process is exited.

  If it is determined in step S37 that the notification mode is not “0”, the notification content of the fault packet is provided to the predetermined monitoring monitor 50 in step S39. That is, when the notification mode is not “0”, the first failure packet is notified to the predetermined monitoring monitor 50. Note that the predetermined monitoring monitor means that it is provided to the monitoring monitor set by default when there is no other designation, and is provided to the designated monitoring monitor when there is designation. Details of this will be described later.

  If it is determined in step S34 that the accumulation flag is already "1", the process proceeds to step S38, where the notification content is accumulated in the corresponding buffer, and the process is exited. That is, the second and subsequent failure notifications are temporarily stored in the corresponding buffer without being immediately notified to the monitoring monitor.

If there is no corresponding device column in the determination in step S32, or if there is no connection device information in the determination in step S33, the notification content is provided to the monitor in step S39, and the process is exited. That is, for monitored devices without connection devices, failure information seems to be relatively simple, so these are provided to the monitor without being collected.

  FIG. 5 shows a timer time-out process. When the timer started in step S36 times out, an interrupt is input to this process. In step S41, the storage buffer corresponding to the timer is extracted. In step S42, it is determined whether or not the notification mode to the monitor side is “2”. If it is not “2”, the notification contents collected in the corresponding accumulation buffer are provided to a predetermined monitor. In step S44, the contents of the storage buffer are saved in the storage memory, and the process is exited. If the notification mode is “2” in the determination in step S42, step S43 is skipped and the process proceeds to step S44. That is, in this case, the contents of the storage buffer are not provided to the monitoring monitor.

  FIG. 6 is a flowchart of the monitoring information notification destination setting process according to the embodiment. A support member specifies a desired monitored device and specifies a monitoring information notification destination by a predetermined operation including the monitored device. This shows the case where the monitored devices can be efficiently monitored.

  When a monitored person identifies a monitored apparatus and designates a monitoring information notification destination (monitoring monitor 50 or supporter identification information), the monitoring information processing unit 31 inputs this information. In step S51, the identification information of the support member is set in the support member information column of the specified monitored device in the configuration information table 35. In step S52, it is determined whether or not any group ID is recorded in the group ID column of the configuration information table 35. The case where it is recorded will be described later.

  If not recorded, it is further determined in step S53 whether the monitored information includes connection device information. If there is, the same supporter information is set in the supporter information column of the related monitored device in step S54, and the process is exited. Here, each related monitored device can be extracted by the same method as described in step S35. If there is no connection device information in the determination in step S53, the process skips step S54 and exits this process.

  Referring to FIG. 7, in this example, support staff α specifies server C (inputs identification information) and designates a notification destination, so that not only server C but also server A and storage related thereto are stored. Support member information α is also added to B. As a result, the support staff α can efficiently monitor the server A and the storage B related to the server C with a simple operation of simply specifying the desired server C. Note that the support staff information α is associated with the monitoring monitor 50a, for example.

  Incidentally, in the network 100, the servers A and C and the storage B are installed in the same room, or the servers A and C and the storage B are not connected to the servers A and C and the storage B. May use a common network infrastructure (for example, the same router 14 or line), and a certain relationship is recognized between these monitored devices in terms of network monitoring. On the other hand, there are many cases where the support staff wants to monitor a group of monitored devices under various installation environments collectively.

  Therefore, in this embodiment, multiple monitored devices can be grouped as desired so that failure notifications from a group of monitored devices in various installation environments can be notified to a single support member by a simple operation. It can be done. That is, in FIG. 7, a group ID column is provided in the configuration information table 35 so that monitored device groups having a certain relationship can be identified by the same group ID.

  The group ID is added in consideration of various circumstances of customers and systems. The group ID setting may be added or changed manually by the network monitoring device 30 (extracting and setting the relevant information from the contract when a support contract is made), or depending on the monitored device At the time of maintenance center registration work, etc., the group ID is also input, and the detection unit 15 creates an attached configuration file including the group ID and notifies the network monitoring device side, which is analyzed by the network monitoring device 30 side. Alternatively, it may be added to the configuration information table.

  Returning to FIG. 6, if any group ID is recorded in the group ID column of the monitored device in the determination in step S52, the process proceeds to step S55, and the group ID column of the configuration information table 35 is set by the group ID. While searching, a monitored device having the same group ID is extracted. In step S56, information on the support member is set in the support member information column of the extracted monitored device, and the process is exited.

  Although the above describes the case where a support member (notification destination) is set, it is also possible to delete a support member. In this case, the settings in steps S51, S53, and S56 are changed to deletion. For example, the notification destination in the case of deletion is returned to the default.

  In the above embodiment, the monitoring-dedicated network 200 is provided, but the present invention is not limited to this. Obviously, the monitoring network may be constructed using the main signal network 100.

  Further, although the preferred embodiment of the present invention has been described, it goes without saying that various changes in the configuration, processing, and combination of each part can be made without departing from the spirit of the present invention.

    (Supplementary note 1) A network monitoring method for a network monitoring system for remotely monitoring a plurality of monitored devices connected to a network from a remote location, the monitored devices notified from each monitored device in advance, and other connected devices A step of storing each identification information of the monitored devices in association with each other and storing a failure notification accompanied with the identification information from each monitored device according to the association information of the memory, Providing a monitoring monitor in association with fault notifications determined to be related to each other.

    (Supplementary Note 2) A network monitoring device of a network monitoring system for remotely monitoring a plurality of monitored devices connected to a network, the monitored devices notified from each monitored device in advance and other devices connected thereto Configuration information processing means for associating each identification information of the monitored devices with each other and storing them in the memory, and a failure notification accompanied by its own identification information from each monitored device, whether or not the identification information is related according to the association information of the memory A network monitoring device comprising: a monitoring information processing unit that determines and relates failure notifications determined to be related to each other and provides them to a monitoring monitor.

    (Supplementary Note 3) The configuration information processing means is configured so that the identification information of the other monitored device connected to the first monitored device matches the identification information of the other monitored device connected to the second monitored device. The network monitoring device according to appendix 2, wherein identification information of the first and second monitored devices and the other monitored devices connected to the first and second monitored devices are stored in a memory in association with each other.

(Supplementary note 4) The supplementary information 2 or 3, wherein the monitoring information processing means accumulates each failure notification determined to be relevant in a buffer for a predetermined time and then provides them together to a predetermined monitoring monitor. Network monitoring equipment. By collecting related failure notifications, the support staff can be alerted, and failure analysis becomes easier.

    (Supplementary Note 5) The monitoring information processing means provides the first failure notification in a certain period among the failure notifications determined to be related to a predetermined monitoring monitor, and is determined to be related within the following predetermined time. 4. The network monitoring apparatus according to appendix 2 or 3, wherein each failure notification is stored in a buffer and then provided to the predetermined monitoring monitor. By providing the first failure notification to the monitoring monitor, it is possible to quickly cope with the occurrence of the failure.

    (Supplementary note 6) The network monitoring device according to supplementary note 5, wherein the failure notification accumulated in the buffer is not provided to the monitoring monitor.

    (Supplementary note 7) The monitoring information processing means accepts failure notification providing destination specifying information that specifies a certain monitored device from the outside in advance, and is related to the specified monitored device according to the association information of the memory 7. The network monitoring device according to any one of appendices 2 to 6, wherein the determined failure notification from each monitored device is provided to a monitoring monitor of the designated failure notification providing destination.

    (Supplementary Note 8) A group ID setting unit capable of setting a desired group ID to a plurality of monitored devices by external setting is provided, and the monitoring information processing unit specifies a failure notification providing destination specifying a certain monitored device from the outside In addition to receiving information, a certain group ID is set for the specified monitored device, so that a failure notification is sent from each monitored device set with the same group ID as the group ID. The network monitoring device according to any one of appendices 2 to 7, wherein the network monitoring device is provided to a monitoring monitor of a notification providing destination.

    (Supplementary note 9) A monitored device connected to the network described in supplementary note 2, and periodically detects a change in its component configuration or a monitored device connected to itself. A monitored apparatus, comprising: configuration information notification means for notifying the network monitoring apparatus of the configuration and / or identification information of the monitored apparatus to which it is connected. Since such a configuration information notification means has a simple function and structure, it can be easily installed in a variety of long name monitored devices.

It is a figure which shows the structure of the network monitoring system by embodiment. It is a flowchart of the structure information table creation / update process by embodiment. It is a flowchart of the connection apparatus information column adjustment process by embodiment. It is a flowchart (1) of the network monitoring process by embodiment. It is a flowchart (2) of the network monitoring process by embodiment. 6 is a flowchart of monitoring information notification destination setting processing according to the embodiment. It is a figure explaining the structure information table by embodiment. It is a figure (1) explaining the various file formats by embodiment. It is a figure (2) explaining the various file formats by embodiment. It is a figure explaining a prior art.

Explanation of symbols

10a, 10b Customer system a, b
11, 13 Server A, C
12 Storage B
15A to 15C Detection unit 14, 36 Router 30 Network monitoring device 31 Monitoring information processing unit 32 Configuration information processing unit 33 Storage device 34 Monitoring information file 35 Configuration information table 50a, 50b Monitor device 100 Network 200 Monitoring network

Claims (5)

A network monitoring method for a network monitoring system for remotely monitoring a plurality of monitored devices connected to a network,
Storing each identification information of the monitored device notified from each monitored device in advance and other monitored devices connected thereto in a memory in association with each other;
A failure notification accompanied by identification information from each monitored device is determined based on the association information of the memory, and whether or not the identification information is related is determined, and the failure notification determined to be related is provided to the monitoring monitor in association with each other. A network monitoring method comprising the steps of: A network monitoring device of a network monitoring system for centrally monitoring a plurality of monitored devices connected to a network remotely,
Configuration information processing means for associating each identification information of the monitored device notified from each monitored device in advance with other monitored devices connected to the monitored device in a memory,
A failure notification accompanied by identification information from each monitored device is determined based on the association information of the memory, and whether or not the identification information is related is determined, and the failure notification determined to be related is provided to the monitoring monitor in association with each other. A network monitoring device comprising monitoring information processing means. The configuration information processing means matches the identification information of the other monitored device connected to the first monitored device with the identification information of the other monitored device connected to the second monitored device. 3. The network monitoring apparatus according to claim 2, wherein each of the identification information of the second monitored apparatus and the other monitored apparatus connected to the second monitored apparatus is associated with each other and stored in a memory. The monitoring information processing means accepts designation information of a failure notification providing destination that specifies a certain monitored device from the outside in advance, and determines each related to the specified monitored device according to the association information of the memory 4. The network monitoring device according to claim 2, wherein a failure notification from the monitored device is provided to a monitoring monitor of the designated failure notification providing destination. A group ID setting unit capable of setting a desired group ID for a plurality of monitored devices by external setting is provided, and the monitoring information processing unit receives designation information of a failure notification providing destination specifying a certain monitored device from the outside. When a certain group ID is set for the specified monitored device, a failure notification from each monitored device set with the same group ID as the group ID is sent to the specified failure notification providing destination. The network monitoring apparatus according to claim 2, wherein the network monitoring apparatus is provided to a monitoring monitor.

Images