JPH07212361A - Distribution system of fault information - Google Patents

Abstract

PURPOSE:To make it possible to easily cope with the change of a system to be a controlled object by adding a control origin address to fault information, transmitting the information from a system to a center and transferring fault information to a control origin or directly transmitting fault information to the control origin from the center. CONSTITUTION:A control origin address 23 is added to the fault information 22 collected by a system 21 and the information is transmitted to a center 11. When the center 11 receives this, the center transfers the fault information 22 to the control origin 31 of a set control origin address 23. When the device within the system 21 is moved to other system, the control origin address is delected from the system 21 of a moving origin and the address is added to a moving destination system. When the fault generation system 21 is in a communication abnormality state and is not capable of performing a transmission to the center 11, the fault information 22 is directly transferred or transmitted to the control origin 31. Thus, the change of the device of the system to be a controlled object can be easily coped with and fault information can be directly communicated with the control origin when a line is abnormal.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a fault information distribution system for notifying a management source of fault information from a system to be managed via a line. With the recent expansion of the scale of electronic computer systems, it is required by the support department to promptly acquire fault information of devices. For this reason, it is desired to quickly and easily distribute the failure information of the device to the management source having jurisdiction.

[0002]

2. Description of the Related Art When a failure occurs in any one of a plurality of managed systems (the same applies to computer systems hereinafter), the failed system sets failure information via a line, as shown in FIG. The collected packets to the center 41
Then, the center 41 refers to the address file 45 and transfers the packet to the management source. The configuration and operation of FIG. 12 will be briefly described below.

FIG. 12 shows an explanatory view of the prior art. Figure 1
2, the system 1 and the system 2 are the systems to be managed, and when the failure occurs, the failure information is set in the packet and transmitted to the center 41. These systems 1 and 2 are DASD (disk device) and MT.
(Magnetic tape device) and the like.

The center 41 receives a packet in which failure information is set from a plurality of managed systems 1 and 2 and transfers the packet to the management sources 1, 2, ... It is composed of a management function 42 and the like.

The network management function 42 manages the network and transfers the packet received from the line to the management source, and the node name management function 4
3, address management function 44, and address file 4
5 and the like.

The node name management function 43 uses the node name (for example, NODE 1, 2, ...) From the packet received via the line.
.. or n) is determined. The address management function 44 refers to the address file 45 to find the management source address of the failure information set in the packet, based on the node name notified from the node name management function 43. The received packet is transferred to the found management source address.

The address file 45 is a file for registering the management source addresses of all the devices of the systems 1, 2, ... The management sources 1, 2, ... N are management sources that maintain the failed systems 1, 2 ,.

Next, the operation will be briefly described. (1) When a fault occurs in any of the systems 1, 2, ..., Fault information is set in a packet and transmitted to the center 41 via the line.

(2) The node name (NODE1) at which the center 1 receives the packet transmitted in (1) and the node name management function 43 constituting the network management function 42 of the center 1 transmits the failure information by the packet. 2,
··· Determine any node name of n).

(3) The address management function 44 that has received the notification of the node name determined in (2)
5, the management source address is extracted. Then, the packet received toward this management source address is transferred through the line.

(4) The management source which received the packet transferred in (3) recognizes that a failure has occurred in the system managed by itself. Then, the fault information set in the packet is obtained, and the corresponding action (for example, maintenance personnel goes out to repair) is taken.

[0012]

FIG. 12 of the related art described above.
Under the above configuration, since the management source address for transferring the failure information is centrally managed in the center 41, when the device is added, changed, or removed from the system to be managed, the address can be changed during the operation of the center 41. There is a problem that the corresponding node name and management source address in the file 45 must be added, changed, and deleted, which makes the operation complicated and must be remembered. Further, when a line abnormality occurs between the managed systems 1, 2, ... And the center 41, failure information is set in a packet and cannot be transmitted to the center 41, and it is directly transmitted to the management source. However, there was a problem that the management address could not be sent because it was unknown. Further, it is necessary to register all management source addresses of a large number of devices to be managed in the systems 1, 2, ... In the address file 45 of the center 41, which causes a problem that the amount of information becomes huge.

The present invention solves these problems.
The management source address is stored in advance in the system to be managed, and when a failure occurs, the management source address is added to the failure information and sent to the center. The center transfers the failure information to the added management source address, The managed system directly sends the failure information to the management source address, and it is possible to easily deal with changes, additions, removals, etc. of devices of the managed system, and the failure information is directly managed by the management source when a line error occurs. Intended to be sent to.

[0014]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the center 1
1 corresponds to the notification of the failure information 22 and the management source address 23 from a plurality of managed systems 21 and transfers the failure information 22 to the management source 31 of the management source address 22. It is a thing.

The system 21 adds the management source address 23 to the failure information 22 collected when a failure occurs and transmits it to the center 11 via the line or directly to the management source address 23.

The management source 31 receives and maintains the fault information 22 transmitted from the center 11 or directly.

[0017]

According to the present invention, as shown in FIG. 1, the management source address 23 stored in advance is added to the failure information 22 collected by the system 21 when a failure occurs, and the center 1 is connected via the line.
Fault information 22 sent to the center 1 and sent to the center 11
The management source address 23 is received, and the failure information 22 is transferred to the management source 31 of the set management source address 23.

Further, the system 21 adds the management source address 23 of the relevant device stored in advance to the fault information 22 collected for each device when a fault occurs, and transmits it to the center 11 via the line. Received the failure information 22 and the management source address 23 for each device,
Management source 3 of management source address 23 set for each device
The failure information 22 is transferred to each item.

Further, when a device in the system 21 is moved to another system 21, the management source address 23 of the device is deleted from the source system 21 and the device management source is set in the destination system 21. The address 23 is added.

When the system 21 in which a failure has occurred cannot send the failure information 22 and the management source address 23 to the center 11, the management source address 2 is sent via the line.
The failure information 22 is directly transmitted to the third node.

Therefore, the management source address 23 is set in advance in the system 21 to be managed, and when the failure occurs, the management source address 23 is added to the failure information 22 and transmitted to the center 11. The center 11 is added with this. Management source address 23
The failure information 22 is transferred to the management source 31 of the
The failure information 23 can be easily dealt with by transmitting the failure information 23 to the management target system 21, and the failure information 23 can be directly sent to the management source 31 when the line is abnormal. It becomes possible to do.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be sequentially described in detail with reference to FIGS.

FIG. 1 shows a block diagram of an embodiment of the present invention.
In FIG. 1, the center 1 receives a packet storing failure information 22 and a management source address 23 from a plurality of systems 21 and causes a failure in the management source 31 of the management source address 23 stored in the packet. The information 22 is transferred, and is composed of a transmission / reception device, a network management function 12, and the like.

The transmitter / receiver is connected to the system 21 via a line.
To and from the management source 31 via a line.
The network management function 12 manages the network, and is composed of a node name management function 13 and an address management function 14 here.

The node name management function 13 manages the node name, and based on the packet received via the line, the node name of the sender of the packet (system 21
The node name uniquely assigned to is determined.
Here, the system (1) determines NODE1, the system (2) determines NODE2, and so on.

The address management function 14 extracts the management source address set in the packet and determines the destination address of the packet. The system 21 is a system to be managed, and includes a plurality of devices (for example, DASD (magnetic disk device) shown in the figure, MT
(Magnetic tape device) and the like) are managed systems. Here, the management source address 23 is stored in the system 21 in advance. Then, the management source address 23 is added to the failure information 22 collected when the failure occurs to create a packet, and the packet is transmitted to the center 11 via the line.

The management source 31 manages the system 21. Here, the management is performed for each system 21 or each device of the system 21 (for example, each DASD, each MT).

Next, the operation of the configuration of FIG. 1 will be described in detail in the order shown in the flowchart of FIG. In FIG. 2, S1 causes a failure. This causes a failure in the system (1) (NODE1) of FIG. 1, for example.

In step S2, failure information is collected. this is,
Since a failure has occurred in S1, the system 21 collects failure information. In S3, the configuration information is searched and the center address and the management source address are retrieved. For example, the system configuration information of FIG. 3A is searched to retrieve, for example, the center address: 1001 and the management source address: 0001. Here, the center address is the address of the center 11 that transmits the failure information 22 via the line. The management source address 23 is an address of the management source 31 that notifies the failure information 22 and performs maintenance and the like.

In step S4, a packet is created. Here, a packet storing: own system address, management source address, failure information, for example, the packet of FIG. 3B is created.

S5 is transmitted. This sends the packet created in S4 to the center address via the line.
In S9, the center 11 receives the packet transmitted in S5.

In step S10, the packet is recreated. Here, a packet storing management source address and failure information, for example, the packet shown in FIG. 3C is created.

At step S11, the data is transmitted. This sends the packet created in S10 to the management source address 23 via the line. In S12, the management source 31 receives the packet transmitted in S11.

In step S13, the packet is saved. S14
Displays information. This displays the fault information of the contents of the packet saved in S13, and informs the CE (system engineer) of the fault content in the system to be maintained by displaying it on the display.

In S6, the transmission in S5 is OK or NG.
Determine whether. If it is OK, the process ends. In the case of NG, since the transmission in S5 could not be performed due to the communication abnormality, the process proceeds to S7.

In step S7, a packet is created. Here, a packet storing management source address and failure information, for example, the packet shown in FIG. 3C is created. Since the system 21 tried to send the packet to the center 11 but could not send it for some reason, it is created to directly send the packet to the management source 31.

At step S8, the data is transmitted. This sends the packet created in S7 to the management source address 23 via the line. As a result, the failure information can be directly transmitted to the management source 31 using a public line or the like without passing through the center 11.

As described above, when a failure occurs in the system 21, the packet in which the own system address, the failure information 22 and the management source address 23 are set is transmitted to the center 11 via the line, and the center 11 sets the packet. The system 21
Directly transmits the fault information 22 to the management source address 23 when the packet cannot be transmitted to the center 11 via the line due to a communication error. As a result, even if the system 21 and the center 11 cannot communicate with each other, the system 21 can directly transmit the packet in which the failure information 22 is set to the management source 31 via a public line or the like.

FIG. 3 is a diagram (No. 1) for explaining the operation of the present invention. FIG. 3A shows system configuration information. This is the configuration information that the system 21 of FIG. 1 has, and here is: center address: 1001 management source address: 0001. The center address is the address of the center 11 that transmits a packet to the system 21 when a failure occurs. The management source address 23 is an address of a management source that delivers a packet to the system 21 when a failure occurs.

FIG. 3B shows a packet data structure (system (1) → center). This is the data structure of a packet to be transmitted from the system (1) in which a failure has occurred to the center 11. Here, as shown below, the own system address management source address data NODE1 0001 failure information is set in the packet. Since the management source address is set in the packet, the center receiving the packet transfers the packet to the management source 31 based on the management source address without referring to the conventional address file 45 of FIG. It becomes possible.

Next, the configuration and operation of another embodiment of the present invention will be described in detail with reference to FIGS. FIG. 4 shows a block diagram of another embodiment of the present invention. Here, the center 11
Is the same as the center 11 of FIG.

In FIG. 4, each device in the system 21 stores a management source address in association with a machine number as shown in the figure. Here, as shown below, machine number # 01: management source address 0001, machine number # 02: management source address 0002, machine number # 03: management source address 0003 are stored in advance.

The management source 31 is a management source provided for each device, such as a DASD management source, a printer management source, and an MT management source. Next, the operation of the configuration of FIG. 4 will be described in detail according to the order shown in the flowchart of FIG.

In FIG. 5, a failure occurs in S21.
This causes a failure in the system (1) (NODE1) of FIG. 4, for example. In S22, failure information is collected. This is because a failure has occurred in S21, so the system collects failure information for each device number.

In step S23, the configuration information is searched to retrieve the device name and number, and the management source address. Here, the device name and number are the name and number of the device in which the failure has occurred. The management source address is the address of the management source 31 that notifies the failure information 22 and performs maintenance and the like.

In step S24, a packet is created. Here, a packet in which: -system address-management source address-machine number-device name and number-fault information is stored, for example, the packet shown in Fig. 6B is created.

S25 is transmitted. This sends the packet created in S24 to the center address via the line. In S29, the center 11 receives the packet transmitted in S25.

In step S30, the packet is recreated. Here, a packet storing management source address, machine number, device name and number, and fault information, for example, the packet shown in FIG. 6C is created.

In step S31, the data is transmitted. This sends the packet created in S30 to the management source address 23 via the line. In S32, the management source 31 receives the packet transmitted in S31.

In step S33, the packet is saved. S34
Displays information. This displays the failure information of the contents of the packet saved in S33, and informs the CE (system engineer) of the failure content of the system to be maintained by displaying the failure content on the display.

In S26, whether the transmission in S25 is OK,
Determine if it is NG. If it is OK, the process ends. In the case of NG, because the transmission of S25 could not be done due to communication error,
Proceed to S27.

In step S27, a packet is created. Here, a packet storing management source address, machine number, device name and number, and fault information, for example, the packet shown in FIG. 6C is created. Since the system 21 tried to send the packet to the center 11 but could not send it for some reason, it is created to directly send the packet to the management source 31.

At step S28, the data is transmitted. This sends the packet created in S27 to the management source address 23 via the line. As a result, the failure information can be directly transmitted to the management source 31 using a public line or the like without passing through the center 11.

As described above, when a failure occurs in the system 21, a packet in which its own system address, machine number, device name and number, failure information 22 and management source address 23 are set is transmitted to the center 11 via the line. , Center 1
1 is transferred to the management source address set in the packet, or directly when the system 21 cannot transmit the packet to the center 11 via the line due to a communication error, the machine number and device name are directly added to the management source address 23. And the fault information 22 are transmitted. As a result, even if the system 21 and the center 11 cannot communicate with each other, the system 21 directly sends a packet in which the machine number, the device name and the number, and the failure information 22 are set to the management source 31 via a public line or the like. It becomes possible to send.

FIG. 6 is a diagram (No. 2) for explaining the operation of the present invention. FIG. 6A shows system configuration information. This is the configuration information that the system 21 of FIG. 4 has, and here is the device number device name and number management source address # 01 DASD # 1 0001 # 02 printer # 1 0002 # 03 MT # 1 0003. The device name and number are the name and number of the device that has failed. The management source address 23 is a management source address for each device that delivers a packet to the system 21 when a failure occurs.

FIG. 6B shows a packet data structure (system (1) → center). This is the data structure of a packet to be transmitted from the system (1) in which a failure has occurred to the center 11. Here, as shown in the figure, its own system address management source address machine number device name and number data NODE1 0001 # 01 DASD. # 1 Set the fault information in the packet. Since the management source address is set in the packet, the center receiving the packet transfers the packet to the management source 31 based on the management source address without referring to the conventional address file 45 of FIG. It becomes possible.

Next, the configuration and operation of another embodiment of the present invention will be described in detail with reference to FIGS. FIG. 7 shows a block diagram of another embodiment of the present invention. Here, the center 11
Is the same as the center 11 of FIG.

In FIG. 7, each device in the system 21 stores the management source address in association with the device name and number as shown in the figure. Here, as shown below, DASD and number # 1: 0001, printer and number # 1: 0002, DASD and number # 1: 0003 are stored in advance.

The management source 31 is a management source provided for each device, such as a DASD management source, a printer management source, and an MT management source. Next, the operation of the configuration of FIG. 7 will be described in detail according to the order shown in the flowchart of FIG.

In FIG. 8, a failure occurs in S41.
This causes a failure in the system (1) (NODE1) of FIG. 7, for example. In step S42, failure information is collected. Since the failure has occurred in S41, the system collects the failure information of the device name and number of the device.

In step S43, the address file is searched for the management source address. In S44, a packet is created. Here, a packet storing: own system address, management source address, device name and number, fault information, for example, the packet of FIG. 9A is created.

S45 is transmitted. This sends the packet created in S44 to the center address via the line. In S49, the center 11 receives the packet transmitted in S45.

In step S50, the packet is recreated. Here, a packet storing management source address, machine number, device name and number, fault information, for example, the packet of FIG. 9B is created.

S51 is transmitted. This sends the packet created in S50 to the management source address 23 via the line. In S52, the management source 31 receives the packet transmitted in S51.

The step S53 stores the packet. S54
Displays information. This displays the failure information of the contents of the packet saved in S53, and informs the CE (system engineer) that the failure has occurred in the device of the system to be maintained and the failure content is displayed on the display.

In S46, whether the transmission in S45 is OK,
Determine if it is NG. If it is OK, the process ends. In the case of NG, because the transmission of S45 could not be performed due to communication error,
Proceed to S47.

In step S47, a packet is created. Here, a packet storing management source address, machine number, device name and number, fault information, for example, the packet of FIG. 9B is created. Since the system 21 tried to send the packet to the center 11 but could not send it for some reason, it is created to directly send the packet to the management source 31.

At S48, the data is transmitted. This sends the packet created in S47 to the management source address 23 via the line. As a result, the failure information can be directly transmitted to the management source 31 using a public line or the like without passing through the center 11.

As described above, when a failure occurs in the system 21, a packet in which its own system address, device name and number, failure information 22 and management source address 23 are set is transmitted to the center 11 via the line, and the center 11 Is transferred to the management source address set in the packet, or the system 21 sends the packet to the center 11 via the line.
When the transmission fails due to communication error, the device name and number, the failure information 22, and the management source address are directly transmitted to the management source address 23. With these, the system 21 and the center 1
Even if the communication with the device 1 is not possible, the system 21 can directly transmit the packet in which the device name and number and the failure information 22 are set to the management source 31 via a public line or the like.

FIG. 9 is a diagram for explaining the operation of the present invention (No. 3). FIG. 9A shows a packet data structure (system (1) → center). This is the data structure of a packet to be transmitted from the system (1) in which a failure has occurred to the center 11. Here, as shown in the figure below, its own system address management source address device name and number data NODE1 0001 DASD # 1 failure information. Is set in the packet. Since the management source address is set in the packet, the center receiving the packet transfers the packet to the management source 31 based on the management source address without referring to the conventional address file 45 of FIG. It becomes possible.

FIG. 9B shows a packet data structure (system (1) → management source). This is the data structure of a packet that is directly transmitted from the system (1) to the management source 31 because a packet cannot be transmitted to the center 11 due to a failure. Address Device name and number Data 0001 DASD # 1 Fault information is set in the packet. Since the management source address is set in the packet, the center receiving the packet transfers the packet to the management source 31 based on the management source address without referring to the conventional address file 45 of FIG. It becomes possible.

Next, the operation when the apparatus is moved will be described in detail with reference to FIG. FIG. 10 shows an explanatory view of another embodiment of the present invention. FIG. 10A shows the contents of the address file before moving. In this example, it is registered in the address file as shown below in association with the device.

System (1) Device Address (Management Source Address) DASD 0001 Printer 0002 MT 0003 System (2) Device Address (Management Source Address) Printer 0004 MT 0005 (b) of FIG. Indicates the content. In this example, since the DASD of the system (1) is removed and moved to the system (2), the DASD is moved as indicated by the arrow in the figure and registered in the address file as follows.

System (1) device address (management source address) printer 0002 MT 0003 system (2) device address (management source address) printer 0004 MT 0005 DASD 0006 As described above, the DASD of the system (1) is removed. Then, when the system (2) is moved to the system (2), the DASD is deleted from the address file of the system (1) of the transfer source, and the DASD and its management source address are registered in the address file of the system (2) of the transfer destination. As a result, the DASD which is the device to be managed is moved from the system (1) to the system (2).

FIG. 11 shows a block diagram of another embodiment of the present invention. This is an example in which the system 21 tries to transmit the packet in which the fault information is set to the center 11, but when the packet cannot be transmitted for some reason, the fault information is directly set in the packet and transmitted to the management source. . Here, as the failure information, there are the following items shown in the figure, which are set in a packet and transmitted to the management source.

-Self system address: NODE1 for example-Management source address: 0001-Fault information-Device number-Device name and number

[0077]

As described above, according to the present invention,
The management source address 23 is set in advance in the system 21 to be managed, and when the failure occurs, the management source address 23 is added to the failure information 22 and transmitted to the center 11. Since the failure information 22 is transferred to the management source 31 and the system 21 directly sends the failure information 23 to the management source 31 with the management source address 23, the device of the system 21 to be managed is Changes, additions, removals, etc. can be easily dealt with, and failure information 23 can be directly sent to the management source 31 when a line error occurs.
Can be sent reliably. With these, even if a device is added or replaced in the system, it can be easily dealt with by simply changing the management source address associated with the device, and the failure information can be directly notified to the management source directly when a communication line error occurs. can do.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a flowchart (No. 1) for explaining the operation of the present invention.

FIG. 3 is an operation explanatory diagram (1) of the present invention.

FIG. 4 is a configuration diagram of another embodiment of the present invention.

FIG. 5 is a flowchart (No. 2) for explaining the operation of the present invention.

FIG. 6 is an operation explanatory diagram (2) of the present invention.

FIG. 7 is a configuration diagram of another embodiment of the present invention.

FIG. 8 is a flowchart (No. 3) for explaining the operation of the present invention.

FIG. 9 is an operation explanatory diagram (3) of the present invention.

FIG. 10 is an explanatory view of another embodiment of the present invention.

FIG. 11 is a configuration diagram of another embodiment of the present invention.

FIG. 12 is an explanatory diagram of a conventional technique.

[Explanation of symbols]

 11: Center 12: Network Management Function 13: Node Name Management Function 14: Address Management Function 21: System 22: Failure Information 23: Management Source Address 31: Management Source

Claims (4)

[Claims] 1. A fault information distribution system in which a center, which has been notified of fault information via a line from a plurality of management target systems, transfers the fault information to a management source, the fault information (22) collected when a fault occurs. ) To which a management source address (23) stored in advance is added and transmitted to the center (11) via a line, and failure information (2) transmitted from this system (21).
2) and the management source address (23), the failure information (2) is sent to the management source address (23) that has been set.
2) and the fault information (2) transmitted from this center (11).
A fault information distribution system comprising: a management source (31) for receiving 2). 2. A failure information distribution system in which a center, which has received notification of failure information from a plurality of managed systems via lines, transfers the failure information to a management source, and a failure collected for each device when a failure occurs. A system (21) that adds the management source address (23) of the device stored in advance to the information (22) and sends it to the center (11) via a line, and a system (21) Received the failure information (22) and management source address (23) for each device,
A center (11) for transmitting failure information (22) to the management source address (23) set for each device
And the fault information (2) transmitted from this center (11)
A fault information distribution system comprising: a management source (31) for receiving 2). 3. When a device in the system (21) is moved to another system (21), the source system (2)
Delete the management source address (23) of the device from 1),
The fault information distribution system according to claim 2 or 3, wherein a device management source address (23) is added to the destination system (21). 4. The management source address (23) via a line when the system (21) in which the failure has occurred cannot transmit the failure information (22) and the management source address (23) to the center (11). The fault information distribution system according to any one of claims 1 to 3, wherein the fault information (22) is directly transmitted to the.