JP2003281001A - Network failure monitoring device, network failure monitoring and reporting system, network failure monitoring and reporting method, and program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To avoid an increase in the burden of an operating manager of a fault monitoring system in applying an automatic notification technology to a server for a plurality of customers, a data center necessary to monitor a network or the like. <P>SOLUTION: The contact address of results obtained by a fault monitor is stored in a database device 30 in a customer unit. The fault monitor 40 is provided with a notification destination retrieval function 26 of acquiring the contact address of the monitoring results from the database device 30, and an automatic notification requesting function 28 for exporting the contact address information of the monitoring results of the customer unit stored in the database 30 to an automatic notifying device 40 and also requesting the automatic notifying device 40 to notify the contact address acquired by the notification destination retrieval function 26 of the monitoring results. The automatic notification device 40 imports the contact address information of the customer unit exported from the fault monitor 20 to store the contact address information in storage devices 42 and 43 and is provided with an automatic notification function 41 of notifying the monitoring results requested from the fault monitor 20 on the basis of the stored contact address information. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure monitoring technology for a network and a device such as a server or a router connected to the network (hereinafter, simply referred to as "network failure"), and more particularly to a network for a plurality of customers. The present invention relates to a network fault monitoring and reporting technique suitable for a case where it is necessary to change the reporting destination according to the source of the occurrence or the work content in a monitoring data center or the like.

[0002]

2. Description of the Related Art A failure that occurs in a network device such as a server (computer) or router is "SNMP (Si, p, p
le Network Management Protocol) Trap ”and other notification functions are used to send to the management manager.

In the management manager, for example, Japanese Patent Laid-Open No. 2000-2000
A command for cooperating with the automatic notification system described in Japanese Patent No. 261572 is defined for each failure type and each occurrence source. With this definition and the notification function of the automatic notification system, it becomes possible to notify the content of the failure to a predetermined system administrator by telephone or e-mail.

However, when such a conventional automatic notification technique is applied to a data center or the like that needs to monitor servers and networks of a plurality of customers, the cause of failure, the type of failure, and the failure content for each business content. Since different parties are notified, the management manager must have settings that define the notification destination according to the source and type of failure. As a result, the burden on the administrator who operates the failure monitoring system increases.
For example, in order to use the automatic notification system, the management manager needs to add information (ID) for identifying a contact defined in the automatic notification system.

[0005]

The problem to be solved by the prior art is that, in the conventional technology, when the automatic notification technology is applied to a data center or the like which needs to monitor servers and networks of a plurality of customers, the occurrence source and the failure are reported. Since the person who notifies the failure content differs depending on the type of business and the business content, the management manager must have settings that define the notification destination according to the source of the failure and the type of failure. This is a heavy burden.

An object of the present invention is to solve these problems of the prior art and to share the definitions relating to the notification of a failure in the management manager, thereby making it possible to reduce the load on the operation manager and at the same time the occurrence of a failure. It is to simplify the operation construction work that occurs at the time of introducing a new customer, by collectively managing the information about the report destination at the time in the customer information database.

[0007]

To achieve the above object, in the present invention, a database for managing customer information is provided, and the customer information database (31, 31a) holds the IP addresses of servers and routers. Information (monitoring target node tables 34, 34a) and contact information (contact table 36, 36a) when a failure occurs are registered.
Further, management information (business group tables 35, 35a) for grouping the customer system by business type.
Also register. And the management manager (23,
23a), the notification destination search function (26, 26) that retrieves the corresponding contact information by searching the customer information database (31, 31a) from the source IP address of the failure.
26a) is provided, and the notification destination search function (26, 26a) is provided.
Then, based on the contact information obtained from the customer information database (31, 31a), the automatic notification request function (28, 28)
a) is activated, and an automatic notification device (40, 40
Realize the automatic notification in a). Here, the operator is
The management manager (23, 23a) has a notification destination search function (2
6,26a) add a common definition for all types of failures. As a result, it is possible to operate the management manager (23, 23a) without being aware of the customer or the notification destination for each work. As a result, the operator in charge only has to add the definition when the type of failure is added and maintain the customer information database (31, 31a).

[0008]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing a configuration example of a network fault monitoring and reporting system according to the present invention, FIG. 2 is a flowchart showing a first processing operation example of the fault monitoring apparatus in FIG. 1, and FIG. , A flow chart showing a second processing operation example of the fault monitoring apparatus in FIG. 1, and FIG.
It is explanatory drawing which shows the process operation example of the network failure monitoring and reporting system in FIG.

The network fault monitoring and reporting system shown in FIG. 1 is for operating and managing servers and networks of a plurality of customers. 10a to 10d are monitored devices, 20 is a fault monitoring device, 21 is a display device, and 22 is an input. Device, 30
Is a magnetic disk device, 40 is an automatic notification device, 42 is a magnetic disk device, and 50 is a communication line.

The monitored devices 10a to 10d are SNMP
It has an agent function and functions as a management agent capable of transmitting / receiving operation information based on MIB and transmitting fault information by SNMP Trap.

The fault monitoring device 20 has a function as a management manager, receives SNMP Traps from the monitored devices 10a to 10d (management agent), and sends MIB value acquisition request messages to the monitored devices 10a to 10d. Acquire operating data by sending.

The automatic notification device 40 is a fault monitoring device 20.
Based on the request from the (management manager), it will report to the contact network defined for each customer and business by telephone or e-mail.

When the conventional automatic notification technology is applied to such a system configuration for monitoring the network of a plurality of customers, since the source of the failure, the type of the failure, and the party to notify the failure content for each business content are different, The setting that defines the notification destination according to the source and the type of failure is the failure monitoring device 20.
(Administration manager) is required.

For example, in order to use the automatic notification system, in the fault monitoring device 20 (management manager),
Information that identifies the contact defined in the automatic notification system (I
D) needs to be added. As a result, the fault monitoring device 20
The burden on the administrator who operates the (administration manager) increases.

In order to solve such a problem and reduce the load on the operation manager, in this example, the fault monitoring device 20 (administration manager) uses a common definition relating to the fault notification, and the fault monitoring device 20 (administration manager) shares the same definition. Collectively manage information about report destinations in the customer information database.

Details of the network fault monitoring and reporting system of FIG. 1 which performs such an operation will be described below.

In FIG. 1, monitored devices 10a to 10a are shown.
Each of the d, the fault monitoring device 20, and the automatic notification device 40 includes computer components such as a CPU (Central Processing Unit) and a main memory, and is recorded in a storage medium such as a CD-ROM via an optical disk drive device or the like. The programs and data are loaded into the memory and processed by the CPU to configure and execute each processing function.

For example, in the fault monitoring device 20, each processing function of the management manager 24 including the fault monitoring function 24 and the automatic action function 25, the notification destination search function 26, the contact table export function 27, and the automatic notification request function 28 is provided. The automatic notification device 40 is provided with an automatic notification function 41.

Each of the monitored devices 10a to 10d is connected to the fault monitoring device 20 via the communication line 50, and the fault monitoring device 20 displays the magnetic disk device 30 for storing customer information and the fault information. Display device 21 for
It also has an input device 22 for operating customer information. The automatic notification device 40 also has a magnetic disk device 42 which is connected to the failure monitoring device 20 via the communication line 50 and stores a notification destination when a failure occurs.

The fault information 60 from the monitored devices 10a to 10d is received via the communication line 50 by the fault monitoring function 24 of the management manager 23 operating in the fault monitoring device 20. The failure monitoring function 24 is used for the magnetic disk device 3
Refer to the automatic action definition 32 saved in 0,
If an automated action definition is set here,
The failure information 60 is passed to the automatic action function 25.

The automatic action function 25 activates the notification destination search function 26 using the source IP in the fault information 60 as an activation argument. The notification destination search function 26 includes a customer information database 31 stored in the magnetic disk device 30.
The notification ID (identifier) is acquired from the monitored node table 34 (described as “customer information DB” in the figure) and the business group table 35, and the automatic notification request function 28 is started using this notification ID (startup argument).

The automatic notification request function 28 calls the automatic notification function 41 of the automatic notification device 40 via the communication line 50 and sets the contact address corresponding to the notification ID to the magnetic disk device 4
It is extracted from the report destination table 43 stored in No. 2, and the contact is notified by telephone or email.

Further, the fault monitoring device 20 includes an input device 22.
Is used to edit the customer information database 31 in the magnetic disk device 30. After editing, the contact table export function 27 of the fault monitoring device 20 is used to make a contact table 36 in the customer information database 31.
Are exported in CSV format, for example.

The CSV file thus exported is transferred via the communication line 50 and imported into the contact table 43 stored in the magnetic disk device 42 of the automatic notification device 40.

Next, referring to FIG. 2, the fault monitoring function 24 and the automatic action function 25 in the fault monitoring device 20.
The processing operation will be described.

When the failure monitoring function 24 receives the failure information 60 from each of the monitored devices 10a to 10d via the communication line 50 (step 201), it refers to the automatic action definition 32 of the customer information database 31 in the magnetic disk device 30. (Step 202).

If there is a screen display instruction in the automatic action definition 32 (step 203), the failure information is displayed on the display device 21 (step 204). Also,
If there is an automatic action definition in the automatic action definition 32 (step 205), the automatic action function 2
5, the activated automatic action function 25 activates the notification destination search function 26 (step 206). At this time, the issuer IP address in the failure information 60 is added to the command execution argument.

The processing operation of the notification destination search function 26 activated in this way will be described with reference to FIG.

In the activated notification destination search function 26, the source IP address is acquired from the argument at the time of activation (step 30
1) Using the source IP address as a key, a query is issued to the monitored node table 34 in the customer information database 31 of the magnetic disk device 30 (step 302).

As a result of the query, if there is no matching IP address (step 303), a mail of unregistered IP information is sent to the system administrator (step 305).
However, if there is a matched record, the business group ID is acquired from the monitored node table 34 (step 304), and the business group table 3 is used as a key.
The notification ID is acquired from step 5 (step 306).

Then, the obtained notification ID is added to the argument at the time of activation, the automatic notification request function 28 is executed, and the automatic notification when a failure occurs is realized (step 307).

Thus, in this example, the customer information database 31 stores the contact network at the time of occurrence of a failure for each customer and for each business (monitored node table 34, business group table 35, contact table 36), These tables are referred to prior to automatic notification when a failure occurs, and the notification destination contact network is determined from the IP address of the source,
By exporting the contact network held in the customer information database 31 (contact address table 36) to the automatic notification device 40 in a format that can be imported (here, CSV format), the network of the monitored devices 10a to 10d to be operated Even when the configuration is changed, it is not necessary to change the setting of the management manager 23, and the automatic notification at the time of failure can be performed only by importing the contact network into the automatic notification device 40.

As described above, the definition relating to the notification of a failure is made common, and the information about the notification destination when a failure occurs is collectively managed in the customer information database 31, so that, for example, the operation construction work that occurs when a new customer is introduced can be simplified. Can be realized.

Next, the processing operation of the network failure monitoring and reporting system in FIG. 1 will be specifically described based on FIG. 4 while specifically showing the configuration of each table in the customer information database 31.

In FIG. 4, each table in the customer information database (described as "customer information DB" in the figure) 31a,
That is, the fault information 60 from each of the monitoring target devices 10a to 10d and the fault monitoring device 2 based on the specific contents of the customer information table 33a, the monitoring target node table 34a, the business group table 35a, and the contact table 36a.
The relationship with the customer information database 31 managed by 0 is shown.

In the customer information database 31a, the customer information table 33a holds information on contracted customers, the monitored node table 34a holds the configuration of monitored devices, and the business group table 35a stores business group information. The contact table 36a holds the import information of the automatic notification device 40.

Specifically, in the customer information table 33a, customer IDs ("0001", "0001" for identifying each customer for each of a plurality of customer names ("ABC Systems", "DEF Trading", ...). Are registered in association with each other, and in the monitoring target node table 34a, the monitoring target node names (“A001”, “A00” are associated with each customer ID (“0001”, “0002”, ...).
2 ”, ...) and its IP address (“ 192.168 ..
159.1 "," 192.168.159.2 ", ...)
And the business group ID ("0001-1", "000"
2-1 ", ...) Is stored.

In the monitored node table 34a, the monitored devices (monitored node names "A001", "A002", ...) Used by each customer are practically used.
Alternatively, the IP address (“192.168.159.
1 ”,“ 192.168.159.2 ”, ...) For each of the identification information (“ 0001
−1 ”,“ 0002-1 ”, ...) Are associated and registered.

In the business group table 35a, each business group ID ("0001-1", "00").
02-1 ”, ...) And a business group name (“ A business ”,“ D business ”, ...) And a notification ID (“ 1000 ”,
"1001", ..., And, in the contact table 36a, each customer ID ("0001", "0002",
...) corresponding to the business group ID (“0001-
1 ”,“ 0002-1 ”, ..., And the notification ID (“ 100
0 ”,“ 1001 ”, ...), Notification target person (“ A ”,
"B", ...), notification order ("1", "2", ...), notification means ("Tel", "mail", ...), contact ("090"
-XXX-XXX "," xxx@yyy.yyy ",
...) is stored.

In practice, the business group table 3
In 5a, identification information of each business (business group ID
For each “0001-1”, “0002-1”, ..., Identification information of the contact network (notification ID “1000”, “1001”,
...) are associated and registered, and the contact table 36a is registered.
In the contact network (notification ID "1000", "100
1 ”, ...) included in the contact information (“ 090-XXX-XX
X ”,“ xxx@yyy.yyy ”, ... At least customer identification information (each customer ID“ 0001 ”,“ 000 ”).
2 ”, ..., and business identification information (business group ID“ 00
01-1 ”,“ 0002-1 ”, ...) Are registered in association with each other.

In the figure, 401 and 402 are SNMP Trs.
This is failure information acquired from the monitored devices 10a to 10d by ap.
"Oid", "Extended Trap number", "Issuer IP",
Corresponding items to "argument 1" and "argument 2",
In the failure information 402, specific data (“.1.
"3.6.1.4.189.0.6", "6", "19"
2.168.159.6 ”,“ threshold exceeded occurrence ”,“ (>
70%) ”) is registered.

Using the management data of each table in the customer information database 31a, the notification destination search function 26a of the failure management device 20a acquires the corresponding notification ID from the source IP address, and the automatic notification request function 28a ,
By setting the notification ID acquired by the notification destination search function 26a in the start argument and executing the processing, the automatic notification device 40a
The automatic notification function 41a in FIG.

For example, the address of the "source IP" in the fault information 401, 402 is "192.168.15."
9.6 ”, and the notification destination search function 26a first refers to the monitoring target node table 34a and assigns the business group ID“ 0003-1 ”corresponding to this IP address“ 192.168.159.6 ”. Then, the business group ID “00” is extracted by referring to the business group table 35a.
The notification ID “1002” corresponding to “03-1” is extracted.

Then, the notification destination search function 26a passes the extracted notification ID "1002" to the automatic notification request function 28a, and the automatic notification request function 28a receives the notification ID "1002".
The contact table 36a is searched using "2" as a key, and the corresponding notification target persons "E", "F", notification order "1",
"2", notification means "Tel", contact information "090-XXX"
-XXX "is read out and the information is sent to the automatic notification device 4
The request is sent to the automatic notification function 41a of 0a.

As described above with reference to FIGS. 1 to 4, in the network failure monitoring and reporting system of this example, a database (customer information databases 31, 31a) for managing customer information is provided, and this customer information database ( Three
1, 31a), configuration information holding the IP address of the server or router (monitored node table 34, 34a)
And contact information at the time of failure (contact table 36, 3
6a) is registered. Further, management information (business group tables 35, 35a) for grouping the customer system by business type is also registered.

Then, it is started from the management manager 23, and the monitoring target node tables 34, 34 of the customer information database 31, 31a are started from the source IP address of the failure.
a and a business group table 35, 35a are searched to provide a notification destination search function 26, 26a for obtaining the corresponding contact information. In the notification destination search function 26, 26a, the contact information retrieved from the customer information database 31, 31a is provided. Based on the destination information, the automatic notification request function 28, 28a is activated, and the processing of the automatic notification request function 28, 28a (the automatic notification device 40,
Exporting the contact table 36, 36a to 40a and requesting notification) realizes automatic notification when a failure occurs.

The operation manager adds a common definition for causing the management manager 23 to activate the notification destination search functions 26, 26a to all types of faults, and manages without being aware of the notification destination for each customer or job. It is possible to operate the manager. As a result, the operator must only add the definition when the type of failure is added and maintain the customer information database.

That is, when the automatic notification technology is applied to a data center or the like that needs to monitor servers and networks of a plurality of customers as in the conventional technology, the failure occurs according to the origin, failure type, and business content. Since the person to be notified of the contents is different, the management manager needs to set the notification destination depending on the source and the type of failure, which increases the burden on the administrator who operates the failure monitoring system. It can be resolved.

The present invention is not limited to the examples described with reference to FIGS. 1 to 4, and various modifications can be made without departing from the scope of the invention. For example, in this example,
Export / import the registered contents of the contact table 36, 36a in the customer information database 31, 31a in CSV format to the contact table 43, 43a stored in the magnetic disk device 42, 42a of the automatic notification device 40, 40a. However, export in other formats
You can also import it.

Further, the monitored devices 10a to 10 of the present example.
d, failure monitoring device 20, 20a, automatic notification device 20, 2
The computer configuration of 0a may be a computer configuration without an optical disk drive device. Further, in this example, the optical disk is used as the recording medium, but the FD
(Flexible Disk) or the like may be used as the recording medium. Further, regarding the installation of the program, the program may be downloaded and installed via the network via the communication device.

[0052]

According to the present invention, a notification destination search function is provided in which notification destination information that differs for each customer or business is managed in common in a customer management database, and a notification destination is extracted by referring to this management information. Since the management manager can be operated without being aware of a plurality of notification destinations, failure monitoring of the server / network of a plurality of customers can be realized without burdening the operation staff. In addition, the export function of the notification destination data allows you to centrally manage the notification destination information in the customer management database, so even when changing the notification destination according to the origin or business content It is possible to minimize human error as compared with the case where the notification destination is set in.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration example of a network fault monitoring and reporting system according to the present invention.

FIG. 2 is a flowchart showing a first processing operation example of the fault monitoring apparatus in FIG.

FIG. 3 is a flowchart showing a second processing operation example of the fault monitoring device in FIG.

FIG. 4 is an explanatory diagram showing a processing operation example of the network fault monitoring and reporting system in FIG.

[Explanation of symbols]

10a to 10d: monitored device, 20: failure monitoring device,
21: display device, 22: input device, 23: management manager, 24: fault monitoring function, 25: automatic action function,
26: notification destination search function, 27: contact table export function, 28: automatic notification request function, 30, 30a: magnetic disk device, 31, 31a: customer information database, 40: automatic notification device, 41: automatic notification function.

   ─────────────────────────────────────────────────── ─── Continued front page    F-term (reference) 5B089 GB02 KA12                 5K033 AA06 BA08 BA12 BA13 DA01                       DB20 EA03 EA07 EB03

Claims (8)

[Claims] 1. A network failure monitoring apparatus for requesting an automatic notification apparatus connected via a network to perform failure monitoring of the network status of a plurality of customers and report the monitoring result to a predetermined contact. Means for storing the contact of the monitoring result in the storage device for each customer, notification destination searching means for reading the contact of the monitoring result from the storage device, and contact for the monitoring result of the customer stored in the storage device A network characterized by having information exported to the automatic notification device and automatic notification requesting means for requesting the automatic notification device to report the monitoring result to the contact read by the notification destination search means. Fault monitoring device. 2. The network failure monitoring device according to claim 1, wherein the storage device is associated with identification information of a task using the monitored device for each monitored device used by a customer. The registered monitoring target node table, the business group table in which the identification information of the contact network is registered in association with the identification information of the business, the contact information included in the contact network, at least the identification information of the customer and the business And a contact table registered in association with the identification information of the contact information, and the notification destination search means refers to the monitored node table and the business group table, and the contact network including the contact of each monitoring result. Identification information of the contact network, the automatic notification requesting means exports the contact table to the automatic notification device, and A network failure monitoring device characterized by notifying identification information and requesting notification of the monitoring result. 3. A fault monitoring device for fault monitoring of a network condition of a plurality of customers, and a fault monitoring device connected to the fault monitoring device via a network, wherein a monitoring result of the fault monitoring device is predetermined based on a request from the fault monitoring device. A network fault monitoring and reporting system comprising an automatic reporting device for reporting to a designated contact, wherein a database device is provided for storing the contact information of the monitoring result of the fault monitoring device in a storage device for each customer, and the fault monitoring is provided. The device exports the contact information of the monitoring result for each customer stored in the database device from the database device to the notification destination search means for obtaining the contact information of the monitoring result to the automatic notification device, and The notification device has automatic notification requesting means for requesting notification of the monitoring result to the contact acquired by the notification destination searching means, and The automatic notification device imports the contact information of each customer exported from the failure monitoring device and stores it in the storage device, and based on the stored contact information, notifies the monitoring result requested by the failure monitoring device. A network fault monitoring and reporting system characterized by having reporting means for performing. 4. The network fault monitoring and reporting system according to claim 3, wherein the database device associates identification information of a business using the monitored device with each monitored device used by the customer. The registered monitoring target node table, the business group table in which the identification information of the contact network is registered in association with the identification information of the business, the contact information included in the contact network, at least the identification information of the customer and the business And a contact table registered in association with the identification information of the contact information table, and the notification destination search means of the fault monitoring apparatus refers to the monitored node table and the business group table to refer to the contact of each monitoring result. And acquiring the identification information of the contact network, the automatic notification requesting means of the fault monitoring device exports the contact table to the automatic notification device. A network fault monitoring and reporting system characterized by notifying the contact network identification information acquired by the notification destination search means of the fault monitoring device and requesting notification of the monitoring result. 5. A failure monitoring device for monitoring a failure of a network condition of a plurality of customers, and a failure monitoring device which is connected to the failure monitoring device via a network and determines a monitoring result of the failure monitoring device in advance based on a request from the failure monitoring device. A network fault monitoring and reporting method of a network fault monitoring and reporting system comprising an automatic reporting device for reporting to a designated contact, wherein the contact information of the monitoring result of the fault monitoring device is stored for each customer through a database device. Procedure, in the fault monitoring device, a procedure for obtaining the contact information of the monitoring result from the database device, and a procedure of exporting the contact information of the monitoring result for each customer stored in the database device to the automatic notification device And a method for requesting the automatic notification device to report the above-mentioned monitoring result to the contact information obtained from the above database device. And a procedure for importing the contact information of each customer exported from the failure monitoring device and storing it in a storage device in the automatic notification device, and the failure monitoring device based on the stored contact information. And a procedure for reporting a monitoring result requested by the network failure monitoring and reporting method. 6. The network failure monitoring and reporting method according to claim 5, wherein the database device is associated with identification information of a business using the monitored device for each monitored device used by the customer. Monitoring node table,
A business group table in which the identification information of the contact network is associated with each piece of identification information of the business, and a contact table in which the contacts included in the contact network are associated with at least the identification information of the customer and the identification information of the business. And a procedure for storing identification information of a contact network including a contact of each monitoring result by referring to the monitored node table and the business group table in the fault monitoring device, Network fault monitoring characterized by having a procedure for exporting the destination table to the automatic notification device and a procedure for notifying the automatic notification device of the acquired identification information of the contact network and requesting notification of the monitoring result. How to report. 7. The computer according to claim 5, or
A program for executing each procedure in the network failure monitoring and reporting method according to claim 6. 8. The computer according to claim 5, or
A computer-readable recording medium having recorded therein a program for executing each procedure in the network fault monitoring and reporting method according to claim 6.