Network management device, method and program

Abstract

To properly determine an impact associated with a failure that occurs in a network.SOLUTION: A network management device according to one embodiment includes a storage device in which information indicating a connection relationship between a plurality of communication devices and communication paths in a network configuration and hierarchy information indicating hierarchy levels of the plurality of communication devices are stored, and a determination unit that determines, when a failure occurs in the communication devices, communication devices affected by the failure that has occurred as a failure affected range on the basis of the information stored in the storage device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] An embodiment of the present invention relates to a network management apparatus, a method, and a program. [Background technology]

[0002] There is a technology (see, for example, Patent Document 1 and Non-Patent Document 1) that uses a technology to display in a common manner regardless of changes in the type and protocol of the NW device when retaining and displaying the configuration of the physical layer and logical layer of a network (network (NW)) realized by multiple network devices, and a technology to identify the relevant range of NW services related to the fault location and to grasp the affected users affected by the fault in a common manner regardless of the type of physical layer and logical layer (see, for example, Non-Patent Document 2).

[0003] For example, in the conventional method for determining the impact on services, devices connected to both ends of a network connection (NC) that is affected by a failure are uniformly determined to be affected devices. NC indicates end-to-end connectivity between two devices.

[0004] In other words, only the devices connected to both ends of the NC affected by the failure are determined to be affected devices. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2018-078523 [Non-patent literature]

[0006] [Non-Patent Document 1] Masataka SATO, Kazuaki AKASHI, Shingo HORIUCHI, Tadashi KOTANI, "Study of Variable Management Architecture for Diverse Networks," IEICE Technical Report, vol. 116, no. 324, ICM2016-31, pp. 37-42, November 2016. [Non-Patent Document 2] Kimihiko FUKAMI, Kenji MURASE, Masataka SATO, Kenichi TAYAMA, "Study on Method of Identifying Service Influence Occurred by Network Fault," IEICE Technical Report, vol. 118, no. 483, ICM2018-51, pp. 13-18, March 2019. Summary of the Invention [Problem to be solved by the invention]

[0007] First, the above technology does not take into account the hierarchical relationship of devices (hereinafter referred to as device hierarchy), and both devices connected to both ends of the affected NC are uniformly determined to be affected devices. However, in reality, among the devices connected to both ends of the NC, devices at higher levels (hereinafter sometimes referred to as higher level devices) are not necessarily affected.

[0008] Secondly, if a device determined to be affected is connected to a device at a lower level (hereinafter sometimes referred to as a lower-level device) or a device at the same level (hereinafter sometimes referred to as a peer device), the impact will also spread to this device. Third, in the conventional technology, the impact is determined without taking into account the redundancy configuration due to the device hierarchy. In reality, however, a lower-level device is often configured with two upper-level devices in a redundant configuration, and even if one of the upper-level devices fails, the lower-level device can still communicate with the other upper-level device, so the lower-level device operates in a single system and should be judged as a single system outage.However, with conventional technology, it is not possible to judge the impact taking into account the redundant configuration, so it is judged as a total outage. As a result, it is not possible to accurately grasp the impact, which means it takes time to grasp the impact in monitoring and maintenance operations, and it is not possible to quickly recover when a disaster occurs.

[0009] The present invention has been made in light of the above-mentioned circumstances, and has as its object to provide a network management device, method, and program that are capable of appropriately determining the impact of an occurring failure. [Means for solving the problem]

[0010] A network management device according to one embodiment of the present invention includes a storage device in which information indicating connection relationships between a plurality of communication devices and communication paths in a network configuration, hierarchical information indicating a hierarchy of the plurality of communication devices, and information defining (1) relationships between objects in a physical layer, (2) relationships between objects in a logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer is stored, and a determination unit is configured to determine, when a failure occurs in the communication device, communication devices affected by the failure that has occurred as a failure impact range based on the information stored in the storage device, including the hierarchical information and the information defining (1) relationships between objects in the physical layer, (2) relationships between objects in the logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer. When a failure occurs in the communication device, the determination unit determines, based on the information stored in the storage device, communication paths connected to the communication device where the failure has occurred. and compares hierarchical information of the communication device where the failure has occurred with hierarchical information of other communication devices connected to the communication path indicated in the acquired information, and when a result of the comparison indicates that the other communication devices are communication devices in a lower hierarchical level of the communication device where the failure has occurred, determines the communication path indicated in the acquired information and the other communication devices as the failure affected range, wherein the network configuration includes a redundant configuration in which a plurality of communication devices in a higher hierarchical level including the communication device where the failure has occurred are connected via communication paths to the communication device in the lower hierarchical level determined as the failure affected range, and the determination unit determines the communication device in the lower hierarchical level determined as the failure affected range in the redundant configuration as the failure affected range as one-way disconnection when some of the communication devices in the higher hierarchical level in the redundant configuration are the communication devices in which the failure has occurred, and communication is possible between the communication device in the lower hierarchical level determined as the failure affected range in the redundant configuration and other communication devices in the higher hierarchical level in the redundant configuration.

[0011] A network management method according to one embodiment of the present invention is a method performed by a network management device having a storage device in which information indicating connection relationships between a plurality of communication devices and communication paths in a network configuration, hierarchical information indicating hierarchical levels of the plurality of communication devices, and information defining (1) relationships between objects in a physical layer, (2) relationships between objects in a logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer are stored, the method comprising: determining, when a failure occurs in the communication device, a communication device affected by the occurrence of the failure as a failure impact range by a determination unit of the network management device based on the information stored in the storage device, including the hierarchical information, and the information defining (1) relationships between objects in the physical layer, (2) relationships between objects in the logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer; and determining, when a failure occurs in the communication device, a communication device affected by the occurrence of the failure as a failure impact range by a determination unit of the network management device based on the information stored in the storage device. the communication device of the lower hierarchical level determined as the failure affected area includes a communication device of the lower hierarchical level connected to the communication path indicated in the acquired information; comparing hierarchical information of the communication device in which the failure has occurred with hierarchical information of another communication device connected to the communication path indicated in the acquired information; and, when a result of the comparison indicates that the other communication device is a communication device of a lower hierarchical level of the communication device in which the failure has occurred, determining the communication path indicated in the acquired information and the other communication device as the failure affected area, wherein the network configuration includes a redundant configuration in which a plurality of communication devices of a higher hierarchical level including the communication device in which the failure has occurred are connected via communication paths to the communication device of the lower hierarchical level determined as the failure affected area, and the determining includes, when a part of the communication devices of the higher hierarchical level in the redundant configuration is the communication device in which the failure has occurred and communication is possible between the communication device of the lower hierarchical level determined as the failure affected area in the redundant configuration and another communication device of a higher hierarchical level in the redundant configuration, determining the communication device of the lower hierarchical level determined as the failure affected area in the redundant configuration as the failure affected area as one-way disconnection. Effect of the Invention

[0012] According to the present invention, it is possible to appropriately determine the effect of a failure that occurs in a network. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an application example of a network management device according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram showing an example of the definition of network equipment information in a table format. [Diagram 3] FIG. 3 is a flow chart showing an example of a processing operation by the network management device according to the first embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating an example of a connection relationship between devices and communication paths. [Diagram 5] FIG. 5 is a diagram showing an example of stage information in each device. [Figure 6] FIG. 6 is a diagram illustrating an example of an influence path. [Figure 7] FIG. 7 is a diagram showing an example of a device that is affected by a failure. [Figure 8] FIG. 8 is a diagram showing an example of a determination result of an effect caused by a failure. [Figure 9] FIG. 9 is a diagram showing an application example of a network management device according to the second embodiment of the present invention. [Figure 10] FIG. 10 is a flowchart showing an example of a processing operation performed by the failure spread determining unit of the network management device according to the second embodiment of the present invention. [Figure 11] FIG. 11 is a diagram illustrating an example of a connection relationship between devices and communication paths. [Figure 12] FIG. 12 is a diagram showing an example of a device that is affected by a failure. [Figure 13] FIG. 13 is a diagram illustrating an example of a communication path affected by a failure. [Figure 14] FIG. 14 is a diagram showing an example of a device that is affected by a failure. [Figure 15] FIG. 15 is a diagram showing an example of a determination result of an effect caused by a failure. [Figure 16] FIG. 16 is a diagram illustrating an application example of a network management device according to the third embodiment of the present invention. [Figure 17] FIG. 17 is a flowchart showing an example of a processing operation by the redundant configuration acquisition unit of the network management device according to the third embodiment of the present invention. [Figure 18] FIG. 18 is a flowchart showing an example of a processing operation by the redundant configuration determination processor of the network management device according to the third embodiment of the present invention. [Figure 19] FIG. 19 is a diagram illustrating an example of a connection relationship between devices and communication paths. [Figure 20] FIG. 20 is a diagram illustrating an example of a path that is affected by a failure. [Figure 21] FIG. 21 is a diagram showing an example of a device that indicates a one-line disconnection. [Figure 22] FIG. 22 is a diagram showing an example of a determination result of an effect caused by a failure. [Diagram 23] FIG. 23 is a block diagram showing an example of the hardware configuration of a network management device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. (First embodiment) First, a first embodiment of the present invention will be described. FIG. 1 is a diagram showing an application example of a network management device according to a first embodiment of the present invention. As shown in FIG. 1, a network management device 100 according to the first embodiment of the present invention includes a failure effect judgment processor 10, a Spec (Specification) DB (database) 20, and an Entity DB 30. The failure effect judgment processing unit 10 has an affected path calculation processing unit 11 and an equipment failure judgment processing unit 12. The equipment failure judgment processing unit 12 has an affected path acquisition processing unit 12a, an equipment information acquisition processing unit 12b, and an equipment stage judgment processing unit 12c.

[0015] Spec DB 20 stores network equipment information (Spec (Specification)). The Entity DB 30 stores network equipment information (entities). This equipment information defines (1) the relationships between objects in the physical layer, (2) the relationships between objects in the logical layer, and (3) the relationships between objects in the physical layer and objects in the logical layer.

[0016] The physical layer may be configured with entities (information objects) consisting of PS (Physical Structure), PD (Physical Device), PP (Physical Port), AS (Aggregate Section), PL (Physical Link), and PC (Physical Connector). The logical layer may be configured with entities consisting of TL (Topological Link), NFD (Network Forwarding Domain), TPE (Termination Point Encapsulation), NC (Network Connection), LC (Link Connect), and XC (Cross (X) Connect). By applying these entities, the physical layer and logical layer configurations can be held in a unified format.

[0017] The entity names in the physical layer can be classified into the above PS, PD, PP, AS, PL, and PC. The "Entity name: meaning: correspondence" for each entity name is as follows: PS: Facilities such as containment buildings and manholes: Equipment objects ·PD:Device:Device object PP: Communication port of the device (port): Port object AS: cable: media object PL: Cable core: Medium object PC: Cable connector: Media object

[0018] Entity names in the logical layer can be classified into the above TL, NFD, TPE, NC, LC, and XC. The "Entity name: meaning: correspondence" for each entity name is as follows: TL: Connectivity between devices (in the Logical Device Layer (sometimes called the LD Layer)): Line objects NFD: Transferable range within the device (in the Logical Device layer): Line or surface object · TPE: Communication End Point: Point object NC: End-end connectivity formed by LC (Link Connect) and XC (Cross (X) Connect) (within the communication layer): communication object LC: Connectivity between devices (in the communication layer): Line or surface object XC: Connectivity within the device (within the communication layer): Line or surface object

[0019] Next, the Spec (physical layer) of facility information will be explained. In the physical layer, attributes that are unique information such as device names or cable types are stored in the Spec DB 20 as information in which Spec classes (which define attributes that indicate characteristics) are instantiated. Specifically, the following Spec classes are defined:

[0020] The "Spec name: meaning" of the Spec class in the physical layer is as follows: PS Spec (Physical Structure Specification): Defines unique attributes for each PS PD Spec (Physical Device Specification): defines unique attributes for each PD PP Spec (Physical Port Specification): Defines unique attributes for each PP · AS Spec (Aggregate Section Specification): Defines unique attributes for each AS PL Spec (Physical Link Specification): Defines unique attributes for each PL PC Spec (Physical Connector Specification): defines unique attributes for each PC

[0021] Next, the Spec (logical layer) of facility information will be explained. In the logical layer, attributes specific to each layer (VLAN ID, IP address, wavelength number, etc.) are stored as information in which the respective Spec classes are instantiated in the Spec DB 20. Specifically, the following Spec classes are defined:

[0022] The "Spec name: meaning" of the Spec class in the logical layer is as follows: ·TL Spec (Topological Link Specification): Defines unique attributes for each TL NFD Spec (Network Forwarding Domain Specification): Defines unique attributes for each NFD · TPE Spec (Termination Point Encapsulation Specification): defines attributes unique to each TPE NC Spec (Network Connection Specification): Defines unique attributes for each NC ·LC Spec (Link Connect Specification): Defines unique attributes for each LC XC Spec (Cross(X) Connect Specification): Defines unique attributes for each XC In addition, the attributes common to the layers and their values ​​are stored in the Entity DB 30 when the Entity class is instantiated.

[0023] FIG. 2 is a diagram showing an example of the definition of network equipment information in a table format. The item names and values ​​of the equipment information stored in the Spec DB 20 are defined as shown in FIG. In the example shown in FIG. 2, an attribute is defined that indicates the stage information (skuNumber) of multiple devices (PD) in the same communication path. This device stage information can be arbitrarily assigned and modified by the user.

[0024] In the hierarchical information, a device with a smaller numerical value is defined as a device at a higher level (hereinafter, sometimes referred to as a higher-level device), and a device with a larger numerical value is defined as a device at a lower level (hereinafter, sometimes referred to as a lower-level device). In other words, the network equipment information in this embodiment includes hierarchical information of a plurality of communication devices that can communicate via a communication path.

[0025] In this embodiment, the device hierarchical information is taken into consideration, and a logic is realized in a unified manner that, among the devices corresponding to both ends of the NC, only the lower devices are affected when a failure occurs, and the higher devices are not affected, regardless of the service and NW configuration.

[0026] As a result, in a configuration in which the devices corresponding to both ends of the NC have a higher-level and lower-level relationship, the impact of a failure can be calculated more accurately, reducing the work of understanding the impact in monitoring and maintenance operations and enabling faster recovery in the event of a disaster.

[0027] FIG. 3 is a flowchart showing an example of a processing operation by the network management device according to the first embodiment of the present invention. 3, the impact path calculation processing unit 11 of the failure impact determination processing unit 10 calculates an object in the logical layer corresponding to an object related to a failure location in the physical layer as a basic path affected by the failure, based on the facility information stored in the Entity DB 30. Here, when a failure (breakdown) occurs in one device in the physical layer, multiple NCs corresponding to this device on the logical layer are calculated as basic paths affected by the failure. In the following description, it is assumed that the device and the NC corresponding to this device on the logical layer have a connection relationship.

[0028] Next, the following S11 is executed as the affected path acquisition process: The affected path acquisition processor 12a acquires, in the form of an array, a list of basic paths that are affected by the failure, calculated as described above, from facility information of the network (S11).

[0029] Next, the following S21 and S22 are executed as device acquisition processing. If there are any unprocessed elements in the subsequent processing among the NCs that are elements of the array acquired in S11 (Yes in S21), the device information acquisition processing unit 12b acquires one of the unprocessed elements, that is, a device connected to one end of the basic path, from the network equipment information as information on a starting device, and acquires information on a device connected to the other end of the basic path from the network equipment information as information on a terminal device (S22).

[0030] Next, the following steps S31 to S35 are executed as the device stage determination process. The device stage determination processing unit 12c acquires the stage information of the start point device and the stage information of the end point device indicated by the information acquired in S22 from the facility information of the network (S31).

[0031] If the value of the stage information of the starting device is equal to or greater than the value of the stage information of the ending device (Yes in S32), the device stage determination processing unit 12c determines that the starting device indicated by the information acquired in S22 is a device that will be affected by the occurrence of a failure (S33).

[0032] If the answer is No in S32, or after S33, if the value of the stage information of the above-mentioned termination device is equal to or greater than the value of the stage information of the above-mentioned start-point device (Yes in S34), the device stage determination processing unit 12c determines that the termination device indicated by the information acquired in S22 is a device that will be affected by the occurrence of a failure (S35).

[0033] If the answer is No in S34 or after S35, the process returns to S21. If there is another unprocessed element in S22 and after, the process in S22 and after is performed for this element, NC. If the answer is No in S21, that is, when the processes from S22 onwards have been carried out for all elements of the array obtained in S11, the series of processes ends.

[0034] Next, an example of processing for a specific configuration will be described. Fig. 4 is a diagram showing an example of the connection relationship between devices and communication paths. Here, as shown in FIG. 4, it is assumed that device A is housed in building "A Building", device B is housed in building "B Building", device C is housed in building "C Building", and device D is housed in building "D Building". One end of object NC1 in the logical layer is connected to device A, the other end of object NC1 is connected to device B, one end of object NC2 in the logical layer is connected to device B, the other end of object NC2 is connected to device C, one end of object NC3 in the logical layer is connected to device C, and the other end of object NC3 is connected to device D.

[0035] 5 is a diagram showing an example of the level information in each device. As shown in FIG. 5, in the above configuration, the value of the level information of each device is defined as follows. ·Device A: 10 ·Device B:20 ·Device C:30 ·Device D:40 That is, this hierarchical information indicates that device A is the highest hierarchical device, device B is a higher hierarchical device, device C is a middle hierarchical device, and device D is the lowest hierarchical device.

[0036] In S11, a process of acquiring paths affected by the failure of device B is executed, and an affected path, which is a list of basic paths affected by the failure, is acquired in the following array. Influence path: NC2, NC1

[0037] Fig. 6 is a diagram showing an example of an affected path, in which device B shown in bold corresponds to the device where the failure occurred, and NC1 and NC2 shown in bold correspond to the affected paths. In S22, for the first affected path NC2, the start point device and the end point device are acquired as follows. Starting device: Device B End point device: Device C

[0038] In step S31, the value of the stage information of the start device and the value of the stage information of the end device are obtained as follows. Starting point device: Device B (Stair information: 20) End point device: Device C (Stair information: 30)

[0039] Since the value "20" of the stage information of device B, which is the start point device, is not greater than or equal to the value "30" of the stage information of device C, which is the end point device (No in S32), the process proceeds to S34.

[0040] Since the value of the stage information of device C, which is the end device, "30", is greater than or equal to the value of the stage information of device B, which is the start device, "20" (Yes in S34), in S35, device C, which is the end device, is determined to be a device that will be affected by the failure. Fig. 7 is a diagram showing an example of a device that is affected by a failure. Device C shown in bold in Fig. 7 corresponds to a device that is affected by a failure. The remaining NC, NC1, obtained in S11 is also subjected to the processes from S22 onwards. As a result of this process, device B connected to NC1 is determined to be a device that is affected by the failure.

[0041] Since this device B is the device where the failure occurred, the other device C that was determined to be affected is the final result of the determination of devices that are affected by the failure that occurred in device B. In addition, the other devices A and D are determined to be devices that are not affected by the failure.

[0042] In other words, the locations of failures in devices A, B, C, and D and the impact of the failures are as follows: Device A: No impact due to failure Device B: Error occurred Device C: Impact due to failure Device D: No impact due to failure Fig. 8 is a diagram showing an example of the determination result of the influence due to the failure. Fig. 8 shows that the presence or absence of the influence due to the above failure in devices A, B, C, and D has been determined as described above.

[0043] Second embodiment Next, a second embodiment will be described. Detailed descriptions of parts of this embodiment that overlap with those of the first embodiment will be omitted. FIG. 9 is a diagram showing an application example of a network management device according to the second embodiment of the present invention. As shown in FIG. 9, in a network management device 100 according to the second embodiment of the present invention, compared to the configuration described in the first embodiment, the device fault determination processing unit 12 of the fault impact determination processing unit 10 further has a fault spread determination processing unit 12d.

[0044] In the second embodiment, the device hierarchical information is taken into consideration, and when a lower-level device or a device of the same level is connected to a device that has been determined in the first embodiment to be affected by a failure, logic is implemented in a unified manner to determine that the connected device is also affected by the failure, regardless of the service and network configuration.

[0045] This allows the impact of a failure to be determined more accurately in a configuration in which another device is connected to devices connected to both ends of the NC, which is the affected path, and further reduces the work of understanding the impact in monitoring and maintenance operations.

[0046] In the second embodiment, logic is implemented in which the effects of a failure of a higher-level device propagate to subordinate devices, and it can be determined that the failure will have an effect even on devices that are not directly connected to the failed device.

[0047] FIG. 10 is a flowchart showing an example of a processing operation performed by the failure spread determining unit of the network management device according to the second embodiment of the present invention. After the processing described in the first embodiment, the failure spread determination processing unit 12d acquires information on the device in which the failure has occurred and on the device determined to be affected by the failure from the facility information of the network (S41). If there are any unprocessed elements in the subsequent processing among the devices that are elements of the array indicated by the acquired information (Yes in S42), the fault spread determination processing unit 12d acquires, for each device corresponding to this element, information on the NC connected to the device in question from the network equipment information in the form of an array (S43).

[0048] If there are any elements, NCs, that are elements of the array indicated by the information obtained in S43 that have not been processed in the subsequent processing (Yes in S44), the NCs indicated by the information obtained in S43 that have been processed once in S47 or later will not be subject to subsequent processing (S45→S46), and the process returns to S45.

[0049] For the NCs other than the processed NCs among the NCs indicated by the information acquired in S43, the fault spread determination processing unit 12d acquires information of the counterpart device connected to the NC for each NC (S47). This counterpart device is a device connected to the other end of the NC indicated by the information acquired in S43 when one end of the NC indicated by the information acquired in S41 is connected to the device indicated by the information acquired in S43.

[0050] The fault spread determination processing unit 12d acquires the stage information of both devices, i.e., the device indicated in the information acquired in S41, and the stage information of the opposite device for this device, and if there is an "NC to which these devices are connected when the affected device is higher (including the same level) than the opposite device," it selects this NC from the NCs indicated in the information acquired in S43 and retains the information indicating this NC in internal memory (S48). If there is an NC held in S48 (Yes in S49), the failure influence determination processing unit 12d determines that the NC held in S48 is an NC to which the influence of the failure has influenced (S50).

[0051] Then, the failure impact determination processing unit 12d newly determines that the opposing device connected to this NC is a device that is affected by the failure (S51). The failure influence determination processing unit 12d sets the device determined to be affected in S51 as the target of the processing from S43 onward (S52), and returns to S43. The processing from S43 onward is performed on the set device.

[0052] Next, an example of processing for a specific configuration will be described. Fig. 11 is a diagram showing an example of the connection relationship between devices and communication paths. As shown in FIG. 11, in the second embodiment, in addition to the above-mentioned devices A to D described in the first embodiment, a device E accommodated in a building "E building" is provided. Then, the above devices A, NC1, device B, NC2, device C, NC3, and device D are connected as described in the first embodiment, and one end of object NC4 in the logical layer is connected to device D, and device E is connected to the other end of this object NC4. It is also assumed that the values ​​of the stage information of devices A to D are the same as those explained in the first embodiment, and the value of the stage information of device E is 40, the same as the value of the stage information of device D.

[0053] In this configuration, the locations of failures in devices A, B, C, D, and E and the presence or absence of effects associated with the failures are determined as follows, by the processes described in the first embodiment. Device A: No impact due to failure Device B: Error occurred Device C: Impact due to failure Devices D and E: No impact due to failure

[0054] Fig. 12 is a diagram showing an example of a device affected by a failure. Device B shown in bold in Fig. 12 corresponds to a device in which a failure has occurred, and device C shown in bold in Fig. 12 corresponds to a device determined to be affected by a failure in the first embodiment.

[0055] In S41, the failure spread determination processing unit 12d acquires information on the device in which the failure has occurred and information on the device determined to be affected by the failure, as follows. Device where the failure occurred: Device B Device affected by the failure: Device C

[0056] In S43, the failure spread determination processing unit 12d acquires, for each device indicated by the acquired information, information indicating the NC connected to this device. Here, the process related to device C will be explained as an example. In S43, the failure spread determination processing unit 12d acquires information indicating NC2 and NC3, which are NCs connected to the device C indicated in the information acquired in S41.

[0057] In S47, the fault spread determination processing unit 12d obtains information indicating device B, which is the opposing device via NC2 as indicated by the information obtained in S43, from the perspective of device C, which is the first device as indicated by the information obtained in S41.

[0058] Also, in S47, the fault spread determination processing unit 12d acquires information indicating device D, which is the opposite device via NC3 as indicated by the information acquired in S43, from the perspective of device C, which is the second device indicated by the information acquired in S41.

[0059] In S48, the fault spread determination processing unit 12d compares the value of the stage information of device C, 30, indicated in the information obtained in S41 with the value of the stage information of the opposing device B, 20, via NC2, indicated in the information obtained in S43, as viewed from device C. Since device C, which is affected by the fault, is at a lower stage than the opposing device B, the information indicating NC2 is not retained in S48.

[0060] On the other hand, when the fault spread determination processing unit 12d compares the value of the stage information of device C, 30, indicated in the information obtained in S41 with the value of the stage information of the opposing device D, 40, via NC3, indicated in the information obtained in S43, as viewed from device C, it is found that device C, which is affected by the fault, is at a higher stage than the opposing device D, and therefore the information indicating NC3 is retained in S48.

[0061] In S50, the failure influence determination processing unit 12d determines that NC3 indicated by the information held in S48 is an NC affected by the failure. Fig. 13 is a diagram showing an example of a communication path affected by the failure. In Fig. 13, NC3, which is an NC affected by the failure, is indicated by a thick line.

[0062] In S51, the failure influence determination processing unit 12d determines that the device D, which is the opposite end via NC3, indicated by the information held in S48, from the perspective of the device C indicated by the information acquired in S41, is a device affected by the failure. Fig. 14 is a diagram showing an example of a device affected by the failure. In Fig. 14, the device D affected by the failure is shown in bold. In S52, the failure influence determination processing unit 12d sets the device D, which has been determined in S48 to be affected by the failure, as a target for the processes in S43 and thereafter.

[0063] With this setting, in S43, the failure spread determination processing unit 12d acquires information indicating NC3 and NC4 that are connected to the device D that was set in S48.

[0064] In the determination of S45, NC3, which is the first NC among the NCs indicated in the information acquired in S43, is an NC for which processing from S47 onwards has been performed, and is therefore not subject to the subsequent processing. On the other hand, NC4, which is the second NC indicated in the information acquired in S43, is not an NC for which processing from S47 onwards has been performed. For this reason, in S47, the failure spread determination processing unit 12d acquires information indicating device E, which is the counterpart via NC4 indicated in the information acquired in S43, as viewed from device D set in S52.

[0065] The value of the stage information of device D set in S52 is 40, and the value of the stage information of the opposing device E via NC4 indicated in the information acquired in S43 from the viewpoint of device D is the same as that of device D. In other words, device D has the same stage as the opposing device E, so in S48, the fault spread determination processing unit 12d holds the information indicating the above NC4.

[0066] In S50, the failure spread determination processor 12d determines that NC4, which is indicated by the information stored in S48, is a device that is affected by the failure. In S51, the failure spread determination processing unit 12d determines that the opposite device E via NC4, which is indicated by the information held in S48, from the device D set in S52 is a device affected by the occurrence of the failure.

[0067] Furthermore, for all other devices acquired in S41, here device B, the processes from S42 onwards are also carried out, and the final determination result of the impact due to the failure is as follows. FIG. 15 is a diagram showing an example of the determination result of the impact due to the failure. The determination result shown in FIG. 15 differs from the case where the processes described in the first embodiment are carried out in that devices D and E are determined to be devices affected by the failure. In other words, compared to the first embodiment, the spread of the impact to lower-level devices is determined. Device A: No impact due to failure Device B: Error occurred Devices C, D, and E: Impacted by failure

[0068] (Third embodiment) Next, a third embodiment will be described. Detailed descriptions of parts of this embodiment that overlap with those of the second embodiment will be omitted. FIG. 16 is a diagram illustrating an application example of a network management device according to the third embodiment of the present invention. 16, in comparison with the configuration described in the second embodiment, a network management device 100 according to the third embodiment of the present invention has a failure impact determination processor 10 that includes a redundant configuration determination processor 13, and the network management device 100 includes a prior data processor 40 in addition to the failure impact determination processor 10. The prior data processor 40 includes a redundant configuration acquisition processor 41.

[0069] In the third embodiment, the hierarchical information of the device is taken into consideration, and the logic for determining the redundant configuration and the logic for determining whether a lower-level device in the redundant configuration is one-way or completely disconnected are realized in a unified manner regardless of the service and network configuration.

[0070] This enables the impact of a failure to be determined more accurately in a configuration in which a redundant configuration is set up between a higher-level device and a lower-level device, further reducing the work involved in understanding the impact in monitoring and maintenance operations.

[0071] FIG. 17 is a flowchart showing an example of a processing operation by the redundant configuration acquisition unit of the network management device according to the third embodiment of the present invention. First, the redundant configuration acquisition processing unit 41 acquires information on a plurality of devices that are connection destination devices for the NC in the basic path list from the network equipment information (S61).

[0072] The redundant configuration acquisition processor 41 compares the values ​​of the stage information of each device indicated in the information acquired in S61, and if there is a lower-level device, acquires information about this device from the Entity DB 30 (S62). If information about the lower-level device has been acquired in S62 (Yes in S63), the redundancy configuration acquisition processing unit 41 acquires information about other NCs connected to the lower-level device indicated in the information acquired in S62 from the network equipment information (S64).

[0073] If there are any unprocessed NCs in the subsequent processing (Yes in S65), the redundant configuration acquisition processing unit 41 compares (S66) the value of the hierarchical information of the device indicated in the information acquired in S62 for the NC indicated in the information acquired in S63 with the value of the hierarchical information of the device opposite this device via the NC.

[0074] If the result of this comparison is that the opposing device is a higher-level device than the device indicated in the information acquired in S62 (Yes in S67), the redundancy configuration acquisition processing unit 41 determines that the NC indicated in the information acquired in S61 and the NC indicated in the information acquired in S63 form a redundant configuration, and retains the NCs that form the redundant configuration in the external definition, which is the definition of the network equipment information related to each NC (S68). After S68, or if the result in S67 is No, the process returns to the determination in S65. If the result in S63 or S65 is No, the series of redundant configuration acquisition processes ends.

[0075] FIG. 18 is a flowchart showing an example of a processing operation by the redundant configuration determination processor of the network management device according to the third embodiment of the present invention. The redundancy configuration determination processor 13 acquires information indicating NCs affected by a device failure from the entity DB 30 (S71).

[0076] The redundancy configuration determination processing unit 13 obtains from the external definition the NC indicated in the information obtained in S71 and the NC determined in the redundancy configuration acquisition processing to have a redundant configuration between this NC, and obtains this as a redundant configuration list (S72).

[0077] If the condition that all of the NCs indicated in the redundant configuration list obtained in S72 are "totally down" is not met, that is, if the NCs indicated in the redundant configuration list include an NC that is not completely down, the redundant configuration determination processing unit 13 determines that one of the NCs in the redundant configuration is down, and adds information indicating this NC to the list of basic paths affected by the failure (S73).

[0078] The redundant configuration determination processing unit 13 deletes information indicating a NC that is "totally disconnected" from the list of basic paths affected by the failure, among the NCs indicated in the redundant configuration list acquired in S72 (S74). This ends the redundant configuration determination process.

[0079] Next, an example of processing for a specific configuration will be described. Fig. 19 is a diagram showing an example of the connection relationship between devices and communication paths. As shown in FIG. 19, in the third embodiment, it is assumed that devices A, B, and C described in the first embodiment are provided. It is also assumed that the above-mentioned devices A, NC1, B, NC2, and C are connected as described in the first embodiment. Also, the values ​​of the stage information of device A and the stage information of device B are the same as those described in the first embodiment, but the value of the stage information of device C is 10, the same as the value of the stage information of device A.

[0080] In S61 of the redundant configuration acquisition process, the redundant configuration acquisition processor 41 acquires information indicating device A and device B which are connection destination devices of NC1 indicated by the basic path. In S62, the redundant configuration acquisition processing unit 41 compares the value of the stage information of one device A, "10", indicated in the information acquired in S61, with the value of the stage information of the other device B, "20", and acquires information indicating the lower-level device B, which has the larger value.

[0081] In S64, the redundant configuration acquisition processor 41 acquires information indicating another NC 2 connected to the lower-level device B indicated in the information acquired in S62. In S66, the redundant configuration acquisition processing unit 41 compares, for NC2 indicated in the information acquired in S64, the value of the stage information of device B indicated in the information acquired in S62, which is "20," with the value of the stage information of device C, which is the counterpart via NC2 from device B, which is "10."

[0082] In this comparison, since the opposing device C is a higher-level device compared to the device B indicated in the information obtained in S62, in S68 the redundancy configuration acquisition processing unit 41 determines that NC1 indicated in the information obtained in S61 and NC2 indicated in the information obtained in S63 form a redundant configuration, and holds information indicating NC2 that forms a redundant configuration with NC1 in the external definition of NC1, and holds information indicating NC1 that forms a redundant configuration with NC2 in the external definition of NC2.

[0083] In S71 of the redundant configuration determination process, the redundant configuration determination processor 13 acquires information indicating NC1, which is a communication path that will be affected by the failure when device A indicated by the basic path fails. Fig. 20 is a diagram showing an example of a path that will be affected by the failure. Fig. 20 shows that device A has failed, as described above, and that NC1 is a communication path that will be affected by the failure.

[0084] In S72, the redundancy configuration determination processing unit 13 obtains information indicating NC1 indicated in the information obtained in S71 and NC2 that forms a redundant configuration with this NC1 from the external definition, and obtains this as a redundant configuration list indicated by the obtained result.

[0085] If the condition that all NC1 and NC2 shown in the redundant configuration list acquired in S72 are "totally disconnected" is not met, then in S73, the redundant configuration determination processing unit 13 determines that NC2, which forms a redundant configuration with NC1, is one-side disconnected, and adds information indicating this NC to the list of basic paths affected by the failure. Fig. 21 is a diagram showing an example of a device showing one-side disconnection. Fig. 21 shows that NC2 has been determined to be one-side disconnected as described above.

[0086] In S74, the redundant configuration determination processing unit 13 deletes information indicating NC1, which is "totally disconnected" among the NCs indicated in the redundant configuration list acquired in S72, from the list of basic paths affected by the failure. The processing described in the first and second embodiments can be performed on the result after this deletion.

[0087] As a result of the above processing, the final judgment result of the impact due to a failure is as follows: Fig. 22 is a diagram showing an example of the judgment result of the impact due to a failure. In this result, for NC2, the first embodiment judges that the upper device A is not affected by the breakdown (failure) of device A, and the lower device B is affected by the failure, and the second embodiment judges that there is no particular repercussion of this impact. Device A: Error occurred Device B: Impacted by failure (one system down) Device C: No impact due to failure

[0088] FIG. 23 is a block diagram showing an example of a hardware configuration of a network management device according to an embodiment of the present invention. 23, the network management device 100 according to the above embodiment is configured, for example, by a server computer or a personal computer, and has a hardware processor 111A such as a CPU. A program memory 111B, a data memory 112, an input / output interface 113, and a communication interface 114 are connected to this hardware processor 111A via a bus 120.

[0089] The communication interface 114 includes, for example, one or more wireless communication interface units, and enables transmission and reception of information to and from the communication network NW. As the wireless interface, for example, an interface that adopts a low-power wireless data communication standard such as a wireless LAN (Local Area Network) is used.

[0090] An input device 50 and an output device 60 for an operator, which are attached to the network management device 100, are connected to the input / output interface 113. The input / output interface 113 takes in operation data input by an operator through an input device 50 such as a keyboard, a touch panel, a touchpad, or a mouse, and outputs output data to an output device 60 including a display device using liquid crystal or organic EL (Electro Luminescence), etc., for display. The input device 50 and the output device 60 may be devices built into the network management device 100, or may be input devices and output devices of other information terminals that can communicate with the network management device 100 via a network NW.

[0091] The program memory 111B is a non-transient tangible storage medium that is a combination of a non-volatile memory that can be written to and read from at any time, such as a hard disk drive (HDD) or a solid state drive (SSD), and a non-volatile memory such as a read only memory (ROM), and stores programs necessary for executing various control processes according to one embodiment.

[0092] The data memory 112 is a tangible storage medium that is a combination of, for example, the above-mentioned nonvolatile memory and a volatile memory such as a RAM (Random Access Memory), and is used to store various data acquired and created during various processing steps.

[0093] A network management device 100 according to one embodiment of the present invention can be configured as a data processing device having a failure impact determination processing unit 10, Spec DB 20, and Entity DB 30 as shown in FIG. 1 or FIG. 9 as a software-based processing function unit, or as a data processing device having a failure impact determination processing unit 10, Spec DB 20, Entity DB 30, and advance data processing unit 40 as shown in FIG. 16.

[0094] The Spec DB 20 and the Entity DB 30 can be configured by using the data memory 112 shown in Fig. 23. However, these areas are not essential components within the network management device 100, and may be areas provided in, for example, an external storage medium such as a Universal Serial Bus (USB) memory, or a storage device such as a database server located in the cloud.

[0095] The above-mentioned failure effect determination processing unit 10 and the processing function units in each unit of the advance data processing unit 40 can all be realized by reading and executing a program stored in the program memory 111B by the above-mentioned hardware processor 111A. Note that some or all of these processing function units may be realized in various other forms, including integrated circuits such as an application specific integrated circuit (ASIC (Application Specific Integrated Circuit)) or an FPGA (Field-Programmable Gate Array).

[0096] The methods described in each embodiment may be stored as a program (software means) that can be executed by a computer on a recording medium such as a magnetic disk (floppy disk, hard disk, etc.), an optical disk (CD-ROM, DVD, MO, etc.), or a semiconductor memory (ROM, RAM, flash memory, etc.), and may be distributed by transmitting the program via a communication medium. The programs stored on the medium include a setting program that configures the software means (including not only execution programs but also tables and data structures) that the computer executes. The computer that realizes the present device reads the program recorded on the recording medium, and in some cases, configures the software means by the setting program, and executes the above-mentioned processing by controlling the operation of the software means. The recording medium in this specification is not limited to a recording medium for distribution, but also includes a storage medium such as a magnetic disk or semiconductor memory provided inside the computer or in a device connected via a network.

[0097] The present invention is not limited to the above-mentioned embodiment, and can be modified in various ways without departing from the gist of the present invention. The embodiments may be combined as appropriate, and in that case, the combined effect can be obtained. Furthermore, the above-mentioned embodiment includes various inventions, and various inventions can be extracted by combinations selected from the multiple components disclosed. For example, if the problem can be solved and the effect can be obtained even if some components are deleted from all the components shown in the embodiment, the configuration from which the components are deleted can be extracted as an invention. [Explanation of symbols]

[0098] 10...Failure impact judgment processing unit 11...Influence path calculation processing unit 12...Device fault determination processing unit 12a...Affected path acquisition processing unit 12b...Device information acquisition processing unit 12c...Equipment ladder judgment processing unit 12d…Fault propagation determination processing section 13...Redundancy configuration determination processing unit 40...Preliminary data processing section 41...Redundancy configuration acquisition processing unit

Claims

1. a storage device for storing information indicating connection relationships between a plurality of communication devices and communication paths in a network configuration, hierarchical information indicating hierarchical levels of the plurality of communication devices, and information defining (1) relationships between objects in a physical layer, (2) relationships between objects in a logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer; a determination unit that, when a failure occurs in the communication device, determines a communication device affected by the failure as a failure impact range based on the hierarchical information and information stored in the storage device, the information including information defining (1) the relationship of each object in the physical layer, (2) the relationship of each object in the logical layer, and (3) the relationship between each object in the physical layer and each object in the logical layer; and Equipped with The determination unit is When a failure occurs in the communication device, information indicating a communication path connected to the communication device in which the failure occurs is obtained based on the information stored in the storage device; comparing the staging information of the communication device where the failure occurred with staging information of other communication devices connected to the communication path indicated by the acquired information; When the result of the comparison indicates that the other communication device is a communication device at a lower level of the communication device where the failure has occurred, the communication path indicated by the acquired information and the other communication device are determined to be the failure impact range; the network configuration includes a redundant configuration in which a plurality of communication devices in a higher hierarchy including the communication device in which the failure has occurred are connected via a communication path to a communication device in a lower hierarchy determined as being within the range of the failure; The determination unit is When a part of the communication devices of the higher hierarchy in the redundant configuration is a communication device in which the failure has occurred, and communication is possible between the communication device of the lower hierarchy determined as the failure affected range in the redundant configuration and another communication device of the higher hierarchy in the redundant configuration, the communication device of the lower hierarchy determined as the failure affected range in the redundant configuration is determined as the failure affected range as one-way system disconnection. Network management device.

2. A method performed by a network management device having a storage device storing information indicating connection relationships between a plurality of communication devices and communication paths in a network configuration, hierarchical information indicating hierarchical levels of the plurality of communication devices, and information defining (1) relationships between objects in a physical layer, (2) relationships between objects in a logical layer, and (3) relationships between objects in the physical layer and objects in the logical layer, comprising: when a failure occurs in the communication device, a determination unit of the network management device determines, as a failure impact range, the communication device affected by the failure that has occurred based on information stored in the storage device, including the hierarchical information and information defining (1) the relationship of each object in the physical layer, (2) the relationship of each object in the logical layer, and (3) the relationship between each object in the physical layer and each object in the logical layer; The determining step comprises: When a failure occurs in the communication device, acquiring information indicating a communication path connected to the communication device in which the failure occurs based on information stored in the storage device; comparing the staging information of the communication device where the failure occurred with staging information of other communication devices connected to the communication path indicated by the acquired information; When the result of the comparison indicates that the other communication device is a communication device at a lower level of the communication device where the failure has occurred, determining the communication path indicated by the acquired information and the other communication device as the failure impact range; the network configuration includes a redundant configuration in which a plurality of communication devices in a higher hierarchy including the communication device in which the failure has occurred are connected via a communication path to a communication device in a lower hierarchy determined as being within the range of the failure; The determining step comprises: when a part of the communication devices of the higher hierarchy in the redundant configuration is a communication device in which the failure has occurred and communication is possible between the communication device of the lower hierarchy determined as the failure affected range in the redundant configuration and another communication device of the higher hierarchy in the redundant configuration, determining the communication device of the lower hierarchy determined as the failure affected range in the redundant configuration as the failure affected range as one-way disconnection, Network management methods.

3. A network management processing program that causes a processor to function as each unit of the network management device according to claim 1.

Images