JPH0318153A - Fault information notification method in complex network system - Google Patents

Abstract

PURPOSE:To quicken the countermeasure against a fault by allowing each network equipment to send fault information detected by itself to a management equipment and using an integrated management equipment to select other network automatically when a fault takes place in a composite network system where some subnetworks are combined. CONSTITUTION:Subnetworks 131-133 are managed respectively by subnetwork management equipments 121-123 and the equipments 121-123 connect to an integrated management equipment 101 via a message conversion processing section 140. Each of the subnetworks 131-133 incorporates a network equipment 190 provided with a network address and when a fault takes place in any of the equipments 190, the information is outputted from one of output devices 150a-150e to report the state to one of the equipments 121-123. Then a fault detection device 170 built in each of the subnetworks 131-133 diagnoses a fault and the resulting information 160 is sent to the integrated management equipment 101 to select the other network.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a failure information notification method in a complex network system that combines networks with single functions such as data, image, and audio, and particularly relates to a system for notifying fault information in a wide area and This paper relates to a failure information notification method suitable for complex network systems with complex configurations.

[Conventional technology]

The conventional failure information notification method is disclosed in Japanese Patent Application Laid-Open No. 6-2-8 463.
As described in Publication No. 6, fault information detected within the network is collected in each management device and outputted only to the output device (printer, etc.) connected to the management device, thereby collectively managing the information. The ability to output fault information is only available in the management equipment installed at the center, so if a fault occurs at a remote location, it is necessary to communicate the fault information between that location and the center (management equipment location). there were.

It was also necessary to install another means of communication to communicate failure information.

[Problem to be solved by the invention]

In the above conventional technology, the output function of fault information (fault detection information + fault diagnosis results) detected in the network is as follows:
It is only available at the management device installed at the center {management device installation base}, and if a failure occurs at a remote base, the failure information must be communicated between the base and the center, which may cause delays in responding to the failure, This was a major cause of confusion.

Furthermore, it was necessary to install another communication means for communicating the failure information, which was very inconvenient.

An object of the present invention is to provide a composite network system that combines several subnetworks having a certain single function and management devices of the subnetworks, and has an overall management device that collectively manages these management devices. The purpose of this system is to automatically notify failure information of the subnetwork management device to the base where the failure has occurred.

Another object of the present invention is to automatically select the most effective other network device to output fault information within the base when a network device that notifies fault information is inoperable or does not have an output function. and to notify the other network devices of the failure information.

Still another object of the present invention is to automatically select another most effective base for outputting fault information when there is no network device capable of outputting fault information within a base to which the fault information is to be notified. The purpose is to provide information.

Still another object of the present invention is to automatically select another subnetwork and send fault information through a management device of the subnetwork when there is no base capable of reporting fault information in a subnetwork to which fault information is to be notified. The purpose is to notify you.

Still another object of the present invention is to facilitate the selection of a fault information notification subnetwork by a central management device.

Still another object of the present invention is to enable easy selection of fault information output network equipment.

Still another object of the present invention is to easily select a subnetwork to be used for notification of fault information when the connection relationship between each subnetwork cannot be grasped by the central management device.

Still another object of the present invention is to easily select another base to which failure information is to be notified when a failure information notification destination base within the network is unable to output failure information in a composite network system.

Still another object of the present invention is to easily select a network device that notifies failure information when a plurality of network devices exist in a base and a failure information notification destination network device in the base cannot output failure information. There is a particular thing.

Still another object of the present invention is to facilitate connection of various subnetwork management devices to a general management device.

Still another object of the present invention is to notify each subnetwork of failure information from the overall management device.

Still another object of the present invention is to notify failure information from a subnetwork management device to a network device to which failure information is to be notified.

Still another object of the present invention is to provide failure information to a faulty base in the above-mentioned composite network system without a central management device.

The above and other objects and novel features of the present invention will become apparent from the description of this specification and the accompanying drawings.

[Means to solve the problem]

A brief overview of typical inventions disclosed in this application is as follows.

In order to achieve the above purpose, each management device is provided with a function to notify failure information to its own network devices, and the central management device is provided with a function to instruct each sub-network management device to notify failure information. This allows failure information to be automatically notified not only to the center but also to the base where the failure occurred.

In addition, if a network device that notifies failure information is inoperable or does not have an output function, the subnetwork management device is used to select the most effective other network device to output failure information within the site. Inter-device priority information and sub-network organization information are provided, and fault information output network devices can be automatically selected based on the inter-site priority information.

Furthermore, if there is no network device capable of outputting fault information within the base that notifies the fault information, in order to select another base that is most effective for outputting fault information,
Inter-site priority information is provided in the central management device, and a failure information output site can be automatically selected based on this information.

Furthermore, if there is no base that can notify failure information within the subnetwork where failure information is to be notified, subnetwork priority information is stored in the central management device in order to select another subnetwork to notify failure information. The fault information notification subnetwork can be automatically selected based on this information.

Furthermore, in order to facilitate the fault information notification subnetwork selection by the general management MW, connection information of each network device with other subnetworks is added to the subnetwork configuration information, and the connection information is included in the fault information. The subnetwork management device communicates with the central management device for use.

Furthermore, in order to easily select a fault information output network device, the subnetwork configuration information includes a flag indicating whether each network device has a fault information output function, and each subnetwork management device refers to the flag. It was designed to do so.

Furthermore, if the connection relationship between each subnetwork cannot be grasped by the central management device and the failure information notification subnetwork cannot be determined, the subnetwork priority information in the central management device is referred to, and the subnetwork used for notification of failure information is This allows you to easily select a network.

Furthermore, in a complex network system, if a failure information notification destination base within the network is unable to output failure information, in order to easily select another base that can output failure information, the priority order of alternative bases is determined between bases. This is to refer to priority information.

Furthermore, when multiple network devices exist in a base and the network device to which failure information is to be notified within the base is unable to output failure information, in order to easily select the network device that will notify the failure information, This system refers to inter-device priority information that determines the priority of alternative devices.

Furthermore, in order to facilitate the connection between various subnetwork management devices and the central management device, message consistency is established between the central management device and each subnetwork management device within the central management device or within each subnetwork management device. This system is equipped with a message conversion processing section that takes the following steps.

Furthermore, in order to notify failure information to each subnetwork by the central management device, subnetwork priority information for selecting the subnetwork to be notified of failure information, and bases for determining the priority for determining the alternate failure information notification destination base. The overall management device is provided with a subnetwork command processing unit that issues priority order information and a fault information notification command to the subnetwork management device.

Furthermore, in order to notify the fault information to the fault information notification destination network devices, the sub-network management device uses a message conversion processing unit for connecting with the central management device, inter-device priority information, and sub-network configuration information. The subnetwork management device is provided with a failure information notification processing unit that selects notification network devices and notifies them of failure information.

Furthermore, even if there is no central management device in the above-mentioned complex network system, each subnetwork management device can be interconnected by a common interface between subnetwork management devices in order to notify failure information to the base where the failure occurred. , which enables failure information to be exchanged between each management device.

[Effect]

In a composite network system that combines several subnetworks, when a failure occurs, each network device transmits the failure detection information detected by itself to each subnetwork management device. The transmitted fault detection information is diagnosed by a fault diagnosis processing unit in the subnetwork, and a fault diagnosis result and fault detection information (these may be collectively referred to as fault information in this specification) are output.

The fault information is transmitted from the subnetwork management device directly to the network device or site where the fault has occurred, or via another subnetwork via the central management device. Therefore, when a fault occurs, fault information reaches the fault location almost simultaneously with the center side, making it possible to respond quickly and accurately at the fault site.

If the network device that reports failure information is inoperable or does not have a failure information output function, the subnetwork management device automatically selects the optimal network device based on inter-device priority information and subnetwork configuration information. Therefore, failure information can be notified to the base where the failure has occurred.

In addition, if there is no network device capable of outputting fault information within the base where the fault information is to be notified, the central management device automatically selects the most suitable base based on inter-base priority information. Fault information can be notified to bases near the occurrence base.

In addition, if there is no base that can notify failure information within the subnetwork, the central management device automatically selects the most suitable subnetwork based on the subnetwork priority information and the subnetwork connection information included in the failure information. There is no problem because it selects and commands notification of failure information.

In addition, subnetwork connection information is set in the subnetwork configuration information, and is added to the fault information when fault information is notified to the central management device, and is added to the fault information to determine the connection relationship between each network device and other subnetworks. This shows that.

In addition, the fault information output function flag in the subnetwork structure information indicates the presence or absence of the fault information output function, and indicates the presence or absence of the fault information output function. This makes it easier to decide on the container.

Further, the subnetwork priority information facilitates determination of a failure information notification subnetwork when the overall management device cannot grasp the connection relationship between each subnetwork.

Furthermore, the inter-base priority information facilitates the determination of an alternative failure information notification base when the failure information notification destination base is unable to output failure information.

Further, the inter-device priority order information facilitates determination of an alternative failure information notification network device when the failure information notification destination network device is unable to output.

Further, the message conversion processing section matches messages between the subnetwork management device and the overall management device.

In addition, the central management device can redirect failure information from each subnetwork management device to another subnetwork management device, so even if the failure information notification subnetwork becomes inoperable, it can be transferred to another subnetwork. If there is, it becomes possible to notify failure information to the base where the failure occurred or to bases in its vicinity.

In addition, in the above-mentioned complex network system, since each subnetwork management device is interconnected by a common interface between subnetwork management devices that enables the sending and receiving of fault information, even if there is no central management device, fault information can be transmitted to other devices. This makes it possible to notify failure information to the location where the failure occurred via the sub-network.

[Example 1] Hereinafter, one embodiment of the present invention will be described in detail.

Fig. 1 is an overall configuration diagram of an example in which the present invention is applied to an actual complex network system, Fig. 2 is a format of fault information exchanged within the network, and Fig. 3 is a diagram showing the overall management device and sub-systems. A block diagram showing the structure of the network management device, Fig. 4 shows the sub-network structure or format of notifications, Fig. 5 shows the sub-network priority information, Fig. 6 shows the priority order information between bases, and Fig. 7 shows the information between the devices. Format of priority information, FIG. 8 is a flowchart showing the processing procedure of the subnetwork management device, FIG. 9 is a flowchart showing the processing procedure of the overall management device, and FIG. 10 is a processing overview diagram of the message conversion processing section.

First, an overview of the complex network and its fault notification processing in the first embodiment of the present invention will be explained with reference to FIG.

The embodiment shown in FIG. 1 is a case of a composite network system (hereinafter sometimes abbreviated as composite net) that combines subnetworks (hereinafter sometimes abbreviated as subnet) 131 to 133. Each sub-lift 131 to 133 is
``They are each managed by subnetwork management devices 121 to 123. Further, each of the subnetwork management devices 121 to 123 is connected to the overall management device 101 via a message conversion processing section 140.

In each of the subnets 131 to 133, various network devices 190 are installed, and these network devices 190 have network addresses (hereinafter abbreviated as NWA) respectively represented by ■ to ■ in the first diagram. has been granted.

If a failure occurs in any of the network devices 190, information representing the failure can be output from suitable output devices 150a to 150b.

For example, assume that a failure occurrence 180 is detected in the network device 190 of NWA ■ in the subnet 133. The failure occurrence 180 is detected by the NWA as failure detection information 170.
is reported to the subnetwork management device 123.

The subnetwork management device 123 stores the failure detection information 17
0 performs fault diagnosis and outputs fault information 160 to device 1.
50 aj is sent and outputted from the output device 150a. According to the present invention, the fault information 160 can be further output to the output device 150b of the NWA in which the fault has occurred, and if the output device 150b is unable to output, the output device of the NWA in the same base 150c. In addition, if the network device at base A in subnet 133 cannot output, the failure information 160 is sent via the central management device 101, for example, from the subnetwork management device 122 to the output device 1 at base 8 in subnet 132.
Furthermore, if there is no network device that can output the failure information 160 at base 8 of this subnet 132, it can be output to another base, for example, the output device 150e of base B of subnet 132. It is also possible to output.

Furthermore, in the first embodiment, if output from the output device 150e is not possible, the output can be sent from the NWA ■, ■, or ■ to another output device (not shown), and the failure information 160 can be output from that output device. .

Furthermore, if there is no output device that cannot output in the NWA of the base B, the output can be sent to the NWA ■ or ■ of the base C, for example, and the failure information 160 can be output from there.

Next, details of the failure information 160 will be explained with reference to FIG.

There are three types of failure information 160: failure information 1.201 to 3.203. Fault information 3,203 is fault detection information 17
0 and the fault diagnosis result 204, which is used inside the sub-network management devices 121 to 123 and from the sub-network management device to the network device to which the fault information is notified. Fault information 2, 202 is different from fault information 3, 203 in that fault information 2, 202 is
WA205, failure point 2'06, subnet NO. 20
7 has been added, and this is from the network device or overall management device 101 to the sub-network management devices 121 to 123. Failure information 1.20
1 specifies the subnet number of another subnet to which the faulty network device is connected within the same base as the upper subnet number in response to the fault information 2.202. 208, lower subnet} No., and 209.

This is from the subnetwork management devices 121 to 123 to the overall management device 101.

Note that when dividing subnets into upper and lower subnets, it is generally better to place the core subnet at the upper level.

Next, the subnet structure information 371 and inter-device priority information 372, which are built in the subnetwork management devices 121 to 123, will be explained with reference to FIGS. 4 and 7.

As shown in FIG. 4, the subnetwork configuration information 371 includes network device configuration information 401 representing the configuration of network devices, upper subnet No. 401 representing the connection of the network device with other subnets within the same base, 208,
209, and a fault information output function flag 402 indicating whether the network device has a fault information output function. In this embodiment, the fault information output function flag 402 is defined as "OO" indicating that the output function is present, and "11" indicating that the output function is not present.

Note that this flag can also be used, for example, to display the output function level of failure information, and can be used to display the output function level of the subnetwork management devices 121 to 12.
It is also possible to change the format of the failure information from 3 to suit its output function.

Also, upper subnet} No. 208, lower subnet N
o, 209 is added to the fault information 1.201 and communicated to the central management device.

Next, the inter-device priority information 372 will be explained with reference to FIG.

In this embodiment, the inter-device priority information 372 is a matrix table as shown in FIG. The way to read the matrix table (the same applies to Figures 5 and 6) is that in Figure 7, 'I
The alternative priority order for the ``0'' side is expressed by numerical value for each item on the ``0'' side.

As understood from FIG. 7, inter-device priority information 37
2 is the inter-device priority order 70 of the alternative network device NWA 701 with respect to the failed network device NWA 205.
0 can be derived.

Similarly, regarding the subnate/priority information 321 and inter-site priority information 322 built into the central management device,
This will be explained with reference to FIG. 5 and FIG. 6, respectively.

First, as shown in FIG. 5, the subnet iI priority order information 321 is the subnet of the alternative subnet }NO, 501 for the subnet }NO, 207 where the failure was detected} fl
A ranking of 500 can be derived.

Similarly, as shown in FIG. 6, inter-site priority information 322 can derive inter-site priority 600 of alternate site 601 relative to failed site 206. Here, the inter-base subnetwork connection information 602 represents the connection status of all subnets included in the entire composite network, and
Position and Subnet} No. is made to correspond, and it indicates that the subnet No. corresponding to the bit position where “l” is set is connected to the corresponding base. This connection information 602 facilitates selection of an alternative subnet.

Next, according to FIG. 10, the subnet management device 121.1
An overview of the processing of the message conversion processing unit 140 that performs message conversion processing between the message conversion processing unit 22 and the central management device 101 will be described.

Fault information 1, 20 created by the subnet management device 121
1 is added with various control information and is input to the message conversion processing unit 140 as a subnet management device failure information message format}1001. The message conversion processing unit 140 converts the subnet management device failure information message format}10 according to the message conversion information 373.
01 to the central management device failure information message format 1
000 and contact the central management device 101.

Similarly, the overall management device failure information message format 1000 from the overall management device 101 is the message conversion process 1% 14 of the subnetwork management device 122.
According to the message conversion information 373, the message conversion processing unit 140 converts the general management device failure information message format}1000 to the subnet management device 1.
The message format is converted into a subnet management device failure information message format l002 suitable for 22.

Next, Figures 3 and 8. The processing of the subnet management devices 121 to 123 and the central management device 101 will be explained with reference to FIG.

First, the subnetwork management devices 121 to 123 detect a fault in the network equipment, and the fault detection information 17
0 to the subnet management devices 121 to 123 (Step 801), the fault diagnosis processing unit 362 performs fault diagnosis (802), and notifies the fault detection information 170 and the fault diagnosis result 204 as fault information 203. The processing unit 361 is notified.

Here, the process of this failure information notification processing unit 361 (802
) will be explained.

First, refer to the subnetwork configuration information 371 (80
4) Determine whether the fault information output network device is operable based on the configuration information and fault information 3.203 (80
5). Operation - Possible, failure information output function flag (F) 4
If 02 is “11” and output function is available (8 0 6)
, Notify the failure information to the relevant network device (807
). The fault information notified at this time is fault information 3.203. Then, if this failure information is a notification command from the central management device 101 (808), the central management device
A notification completion report is made (809) and the process is completed.

In addition, failure information output malfunction equipment is inoperable (80
5), or if it is operable but does not have an output function (
805, 806), determines whether there is any other network device in the base (810), and if that network device is "available", refers to the inter-device priority information 372 (811), and Alternative network equipment 7 based on information
In step 01, the network device with the highest priority is automatically selected (8 1 2), and the process returns to subnetwork configuration information reference (804).

On the other hand, there are no other network devices within the base (81
0), if it is not a fault information notification command from the central management device 101 (808), the fault information 1, 20 is sent to the central management device.
1 (8 1 3), and in the case of a failure information notification command from the central management device (808), the central management device 1
01 that failure information notification is not possible and ends the process.

Furthermore, when a failure information notification command is received from the general management device (815), the process is performed by failure information notification processing (80
3).

Next, regarding the processing in the general management device 101, the ninth
As shown in the figure, subnetwork management device 350
When fault information is received from (901), subnetwork command processing (902) looks at the upper subnetwork No. 208 of fault information 1, 201 (903).
, if there is an upper subnetwork, it commands failure information notification to the subnetwork (904), and if a notification completion report is received from the subnetwork (905).
>, the process ends.

Next, if notification is not possible from the subnetwork or there is no upper subnetwork, the lower subnetwork NO. of failure information 1,201. Look at 209 (9 0 6)
,Similarly, if there is a lower sub-network, it instructs the sub-network to notify the failure information (907), and if a notification completion report is received from the cough sub-network (
908), the process ends.

In addition, if notification is not possible from the subnetwork or there is no lower subnetwork, the subnetwork priority information is referred to (9 0 9) and it is determined whether there is a subnetwork that can output other failure information (910). , if there is not, output a message that the failure information cannot be output (9 1
4) End the process. If there is, the failure information notification subnetwork is determined from the cough subnetwork priority information (911), and the inter-base priority information is referred to (911).
2).

Then, based on the priority information between core bases, it is determined whether there is a base that can output failure information within the subnetwork (913
), if there is none, refer to the subnetwork priority information again (909) and repeat the process. If there is no such base, the failure information notification base is determined based on the priority information between the bases (9
15) issues a command to notify the failure information to the relevant subnetwork (916). Then, if there is a failure information notification completion report from the relevant subnetwork (917), the process ends, and if there is not, the process is repeated by referring to the subnetwork priority information (909) again.

The above is the process of failure detection, failure information notification, etc. in this embodiment 1.

[Embodiment 2] Next, according to another embodiment of the present invention, an embodiment of a means for notifying fault information to a fault occurrence base even without a general management device is shown in FIGS. 11 and 12. This will be explained based on FIG. 13.

FIG. 1l is a diagram showing the overall structure of one embodiment of the fault information notification means.

The major difference between the notification means in the first embodiment described above and the notification means in the second embodiment is the way in which failure information is conveyed to other subnetwork management devices.

That is, in the failure information notification means in the first embodiment described above, information is sent from the subnetwork management devices 121 to 123 to other subnetwork management devices 121 to 123 via the message conversion processing unit 140 and the central management device 101.
However, according to the fault information notification means of this embodiment, there is no central management device, and each of the subnetwork management devices 121 to 123 communicates with each other through a common interface 1100 between subnetwork management devices. By connecting to and passing through the interface 1100, the fault information 160 can be mutually transmitted to the other subnetwork management devices 121 to 123.

Here, the inter-subnetwork management device common interface 1100 converts individual message formats of each subnetwork management device 121 to 123 between each subnetwork 131 to 133 in the same way as the message conversion processing unit 140 in the first embodiment described above. It converts to a common format.

Next, FIG. 2 is a block diagram showing the structure of the subnetwork management device 350 in the second embodiment. In the first embodiment, inter-base priority information 322, sub-network priority information 321, sub-network command processing unit 3
22 was placed in the overall management device 101, but in the second embodiment, since there is no overall management device, all the information is placed in the subnetwork management device 350. Furthermore, failure information 1200 for other subnetworks and failure information 1201 from other subnetworks are all processed via the subnetwork management device common interface 11OO.

Next, processing steps such as fault detection and fault information notification in the second embodiment will be explained based on FIG. 13.

That is, the processing flow in this embodiment is exactly the same as in the above-described embodiment 1 regarding the subnetwork command processing 902. In addition, regarding the failure information notification processing unit 803, the process 813 of the first embodiment described above is eliminated, and the process 813 of the first embodiment is eliminated.
08 to 1301, 814 to 1304, 809 to 13
02, 815 has been replaced with 1304, and the overall management device has been replaced with another subnetwork management device. In other respects, the second embodiment is carried out in the same manner as the first embodiment.

As above, the invention made by the present inventor has been specifically explained based on Examples, but it should be noted that the present invention is not limited to the Examples and can be modified in various ways without departing from the gist thereof. Not even.

〔Effect of the invention〕

Since the present invention is designed as explained above, it has the following effects. First, (1): When a fault occurs, fault information is automatically communicated to the fault location, which eliminates the need for a process of checking the fault information, and enables quick and accurate fault handling.

(2). Further, even if the fault information notification destination network device is unable to output fault information, the most effective other network device is automatically selected, so fault information can be notified.

(3). Further, if there is no network device capable of outputting fault information within the base to which the fault information is to be notified, the most effective other base is automatically selected, so that the fault information can be notified.

(4). Furthermore, if there is no base capable of reporting failure information within the subnetwork to which failure information is to be notified, the most effective other subnetwork is automatically selected, so that failure information can be notified.

(5). Furthermore, since the connection status between each network device and other subnetworks is added to the configuration information of the subnetwork, it becomes easy to select a subnetwork.

(6)5 Furthermore, since the configuration information of the subnetwork includes a flag indicating whether or not each network device has a failure information output function, it becomes easy to determine whether failure information can be output.

(7). Furthermore, since it has subnetwork priority information, it becomes easy to select an alternative subnetwork for fault information notification.

(8). Furthermore, since it has inter-base priority information, it becomes easy to select an alternative base for failure information notification.

(9). Furthermore, since it has inter-device priority information, it becomes easy to select an alternative network device for failure information notification.

OL Furthermore, since there is a message conversion processing section between the central management device and the subnetwork management device, various subnetwork management devices can be easily connected to the central management device.

01). Furthermore, by having the subnetwork priority information, the inter-site priority information, and the subnetwork command unit in the overall management device, it is possible to notify the subnetwork management device of failure information.

α one. Further, by having a message conversion processing unit, inter-device invasion ranking information and failure information notification processing unit in the subnetwork management device, it is possible to notify failure information to network devices.

α one. In addition, a common interface between subnetwork management devices is provided for each subnetwork management device,
Since each subnetwork management device is connected to each other via the interface to enable notification of failure information, notification of failure information is possible even without a central management device.

[Brief explanation of the drawing]

Fig. 1 is an overall configuration diagram of a composite network system according to an embodiment of the present invention, Fig. 2 is a format of fault information exchanged within the network, and Fig. 3 is a general management device and subsystem according to an embodiment of the present invention. FIG. 4 is a block diagram showing the structure of the network management device; FIG. 4 is the format of sub-network structure information; FIG. 5 is the format of sub-network priority information; FIG. 6 is the format of inter-base priority information; 8 is a processing flowchart of the subnetwork management device, FIG. 9 is a processing flowchart of the central management device, FIG. 10 is a processing overview diagram of the message conversion processing unit, FIG. 11 is a diagram showing the overall configuration of a composite network system according to another embodiment of the present invention, FIG. 13 is a processing flowchart of the subnetwork management device based on FIG. 13 and FIG. 12. FIG. 101... General management device, 121... Subnetwork management device, 122... Subnetwork management device, 123... Subnetwork management device, 131...
・Subnetwork, 132...Subnetwork,
133...Subnetwork, 140...Message conversion processing unit, l50a to 150e...Output device, 1
60... Failure information, 170... Failure detection information, 18
0... Failure occurred, 190... Network equipment, ■
~■...NWA (network address), 201
...Fault information 1, 202...Fault information 2, 203.
...Fault information 3, 204...Fault diagnosis result, 205.
...Faulty network equipment NWA, 206...Faulty base, 207...Subnetwork No., 208...
Upper sub-network No., 209... Lower sub-network No., 311... Sub-network command processing section, 312... Central management device output section, 321... Sub-network priority information, 322... Between bases Priority information, 331... Failure information output, 361...
Fault information notification processing unit, 362...Fault diagnosis processing unit, 3
63...Subnetwork management device output section, 371.
... Subnetwork structure information, 372 ... Inter-device priority information, 373 ... Message conversion information, 381
... Fault information output, 401... Network device configuration information, 402... Fault information output function flag, 500
...Subnetwork priority, 50l...Alternative subnetwork No., 600...Inter-base priority, 6
01...Alternative base, 602...Inter-base subnetwork connection information, 700...Inter-device priority order, 701.
...Alternative network device NWA, 1000...General management device failure information message format, 1001.
...Subnetwork management device failure information message format, 1002...Subnetwork management device failure information message format, 1l00...Common interface between subnetwork management devices, l200.
...Failure information for other subnetworks, 1201...
Fault information from other subnetworks. 206 Figure 2

Claims (1)

[Scope of Claims] 1. Several subnetworks with a single function, a subnetwork management device that manages the subnetworks, and an overall management device that manages these subnetwork management devices in an integrated manner. A failure in a composite network system characterized in that each sub-network management device notifies a failure occurrence site of failure detection information and failure diagnosis results detected and collected by each subnetwork management device. Information notification method. 2. If the network device that notifies failure information at a certain base is inoperable or does not have an output function, the most effective network device will be automatically selected to output other failure information within the base. 2. The fault information notification method in a composite network system according to claim 1, wherein the fault information is notified to the network device. 3. If there is no network device capable of outputting fault information within the base where the fault information is to be notified, the system automatically selects another most effective base to output the fault information and notifies the fault information. 3. A failure information notification method in a composite network system according to claim 1 or 2. 4. If there is no base in the subnetwork that can notify failure information, another subnetwork will be automatically selected and failure information will be notified through the management device of the other subnetwork. 4. A failure information notification method in a complex network system according to claim 1, 2 or 3. 5. A complex network system consisting of a combination of several subnetworks and subnetwork management devices that manage the subnetworks, in which each subnetwork management device is connected to each other through a common interface between the subnetwork management devices, and each A failure information notification method in a complex network system, characterized in that failure information can be exchanged between subnetwork management devices.