JP2017098741A - Network system, and network management method and device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to rapidly execute fault recovery and operation setting change while reducing a processing load for the setting change, in the case that a fault has occurred at part in a network, for example.SOLUTION: A plurality of second networks 420 are constructed on a first network 410; a network management device 1 comprises an input device, output device, processing device, and storage device. The storage device retains a plurality of network groups obtained by grouping the second networks and network setting information that corresponds to each combination of the network groups and is used to change a resource of the first network. The processing device, in the case of determining that a failure has occurred in network groups on the basis of information obtained from the input device, is capable of changing the resource of the first network by selecting network setting information on the basis of a combination of the network groups in which the failure has occurred before notifying a communication device of the selected network setting information by using the output device.SELECTED DRAWING: Figure 4

Description

  The present invention relates to network management.

  In recent years, communication networks have played an important role in daily life and business by providing connection services to the Internet and connections to cloud services. Therefore, when a failure occurs in a part of the communication network due to a device failure or a major disaster, it is desired to quickly recover from the failure.

  As a background art in this field, there is a technique described in Patent Document 1. In this document, it is an object to enable high-speed switching / returning of a surface (communication path) at the time of network failure or network maintenance. Further, as a means for solving the problem, there is a communication path changing method, in which the switch A (first router) and the switch B (second router) constitute one virtual router protocol group, and both routers are active routers. In a communication system that can be dynamically changed to the standby router or from the standby router to the active router, the first port of the switch A is opened to communicate with the switch C (first device) so that the switch C can communicate with the switch C. When the second port of the switch B being closed is closed, the second port having a higher priority as the virtual router than the first port and having a lower evaluation value as the communication path to the switch C than the first port is opened. , And is described.

  As another background art, there is a technique described in Patent Document 2. This document provides a communication network system that can combine the three features of being able to recover from a failure as fast as the protection method, recovering a path even for multiple failures, and using network resources efficiently. It is an issue. Further, as a means for solving the problem, a communication network system including a path database and a path switching unit can solve the problem. The path database stores grouping data for grouping one working path and another working path protected by an alternative path into the same group. It is described that the path switching unit refers to the grouped data when a failure occurs in one working path and switches to another working path belonging to the same group as the one working path. Yes.

  As another background art, there is a technique described in Patent Document 3. In this document, when a failure occurs in a physical network in a slice constructed by a unique network technology that does not depend on the technology of the physical network, the virtual server that configures the slice can detect the network failure. It is an issue. In addition, as a solution, in a virtual network using virtual server and tunnel technology, a failure notification device that notifies a network failure to the virtual server detects the failure of the network on the route through the tunnel and detects the failure. In this case, the virtual server that uses the tunnel is identified, the virtual switch that connects the tunnel in which the failure is detected and the virtual server are identified, and the link between the virtual switch and the virtual server is down. Is described.

  As another background art, there is a technique described in Patent Document 4. In this document, when a failure occurs in a communication system, it is an object to reduce a setting load for quickly restoring an existing setting path. In addition, as a means for solving the problem, the network management server generates an appearance pattern for each occurrence pattern of a failure occurrence area where a failure of a communication device in the own area has occurred among a plurality of areas passing through the transmission path. And a storage device that associates and stores information that specifies a recovery plane that is a set of recovery paths corresponding to the information and information that specifies a communication device that passes through the recovery path. The network management server identifies which failure occurrence pattern corresponds to a failure in any of multiple areas, and is a recovery path set corresponding to the identified failure occurrence pattern It is described that information for specifying a surface is acquired from a storage device, and information for specifying the acquired recovery surface is notified to a communication device via a recovery path included in the recovery surface.

JP 2006-148497 A JP 2010-166328 A JP 2013-207341 A Japanese Patent Laying-Open No. 2015-97331

  However, the technique described in Patent Document 1 discloses a method of preparing two operation surfaces (A surface and B surface) and quickly changing a communication path at the time of a network failure or maintenance. Even if a failure occurs in a part of the plane, and there are many active routers in the A plane, the operation plane is changed to the B plane, and there is a problem that a large number of network settings need to be changed.

  In the technique described in Patent Document 2, a group of a plurality of active paths and alternative paths is grouped, and failure recovery is performed using network resources shared within the group. There is a problem that cannot be done. In addition, in order to be able to recover a failed active path with an alternative path to another active path, both end points of the active path to be grouped and the alternative path must be the same. There are challenges.

  Furthermore, the technique described in Patent Document 3 has a problem that recovery after detecting a network failure in a slice cannot be performed quickly.

  On the other hand, the technique described in Patent Document 4 has a problem that a virtual network configured on a physical network is not considered.

  Therefore, the present invention has been made in view of the above-described problems, and in the case where a failure occurs in a part of the network, the failure recovery and operation setting change can be quickly performed while reducing the processing load for setting change. It is intended to be executable.

  One aspect of the present invention that solves the above-described problems is a network system that includes a network including a plurality of communication devices and a network management device that manages the network. In this network, a plurality of second networks are configured on the first network, and the network management device includes an input device, an output device, a processing device, and a storage device. The storage device holds a plurality of network groups obtained by grouping the second networks, and network setting information for changing the resources of the first network corresponding to each combination of the network groups. If it is determined that a failure has occurred in the network group based on the information obtained from the device, the network setting information is selected based on the combination of the network group in which the failure has occurred, and the output device By notifying the selected network setting information, the resource of the first network can be changed.

  Another aspect of the present invention is a network management method for managing a network including a plurality of communication devices by a network management device. In this method, the network management device uses a part of the resources of the first network to set a plurality of second networks, and bundles a plurality of second networks to group them together. A grouping step for forming a group, a network management device corresponding to each combination of network groups, a recovery setting calculating step for calculating network settings for changing resources of the first network, and network management When the apparatus determines that a failure has occurred in the network group, a selection step of selecting the calculated network setting corresponding to the combination of the network groups in which the failure has occurred, and the network management apparatus Notification notification to notify the selected network settings Comprising a-up, communication device, based on the notified network configuration, a recovery step of changing the resources of the first network.

  Still another aspect of the present invention is a program for managing a network composed of a plurality of communication devices by a network management device, and a recording medium storing the program. The program includes a path setting step for setting a plurality of second networks using a part of the resources of the first network in the network management apparatus, a plurality of second networks being bundled and grouped, and a plurality of networks A grouping step for forming a group, a network management device corresponding to each combination of network groups, a recovery setting calculating step for calculating network settings for changing resources of the first network, and network management When the apparatus determines that a failure has occurred in the network group, a selection step of selecting the calculated network setting corresponding to the combination of the network groups in which the failure has occurred, and the network management apparatus To notify the selected network settings A method, communication device, based on the notified network configuration to execute a recovery step of changing the resources of the first network.

  Still another aspect of the present invention is a network management device that manages a network, which includes a plurality of communication devices, and a plurality of second networks configured on a first network. The network management device includes an input device, an output device, a processing device, and a storage device. The storage device includes a plurality of network groups in which the second networks are grouped, and a first corresponding to each combination of network groups. Network setting information for changing network resources is stored, and when the processing device determines that a failure has occurred in the network group based on information obtained from the input device, the processing device Based on the combination, the network setting information is selected, and the selected network setting information is notified to the communication device by the output device.

  The meaning of the network group includes a case where there is one second network as a component of the group. The meaning of the combination of network groups includes the case where there is one network group as a component of the combination.

  According to the present invention, when a failure occurs in a part of the network or when the network operation setting is changed according to a time division such as maintenance, the failure can be quickly recovered while reducing the processing load for changing the setting. And operational settings can be changed.

It is an example of the network system block diagram in the 1st Embodiment of this invention. It is an example of the network system block diagram after the working path | pass setting in the 1st Embodiment of this invention. It is an example of the network system block diagram after the protection path setting in the 1st Embodiment of this invention. It is an example of the network system block diagram after the operation surface change path setting in the 1st Embodiment of this invention. It is an example of the sequence diagram which shows the flow of the preset process for failure recovery in the 1st Embodiment of this invention. It is an example of the sequence diagram which shows the flow of the recovery process by the protection recovery in the 1st Embodiment of this invention, and an operation surface change path. It is an example of the sequence diagram which shows the flow of the recovery process by the 2nd operation surface change path in the 1st Embodiment of this invention. It is an example of the communication failure determination table which shows the relationship between the communication apparatus failure and the group network failure which generate | occur | produces in the 1st Embodiment of this invention. It is an example of the protection failure determination table which shows the relationship between the communication device failure in the 1st Embodiment of this invention and the protection failure with respect to the group network which generate | occur | produces. It is an example of the group corresponding | compatible recovery setting table which shows the path | pass setting for a recovery with respect to the communication apparatus for a failure network group and recovery in the 1st Embodiment of this invention. It is an example of the identifier corresponding | compatible recovery setting table which shows the path | pass recovery setting for every communication apparatus with respect to the recovery identifier F1 in the 1st Embodiment of this invention. It is an example of the identifier corresponding | compatible recovery setting table which shows the path | pass recovery setting for every communication apparatus with respect to the recovery identifier F2 in the 1st Embodiment of this invention. It is an example of the identifier corresponding | compatible recovery setting table which shows the path | pass recovery setting for every communication apparatus with respect to the recovery identifier F3 in the 1st Embodiment of this invention. It is an example of the network group recovery setting table (communication device corresponding recovery setting table) which shows the path recovery setting with respect to every communication apparatus in the 1st Embodiment of this invention. It is an example of the network group recovery setting table (communication device corresponding recovery setting table) which shows the path recovery setting with respect to every communication apparatus in the 1st Embodiment of this invention. It is an example of the network group recovery setting table (communication device corresponding recovery setting table) which shows the path recovery setting with respect to every communication apparatus in the 1st Embodiment of this invention. It is an example of the network group recovery setting table (communication device corresponding recovery setting table) which shows the path recovery setting with respect to every communication apparatus in the 1st Embodiment of this invention. It is a figure which shows the structural example of the communication apparatus in the 1st Embodiment of this invention. It is a figure which shows the structural example of the network management server in the 1st Embodiment of this invention. It is an example of the flowchart which shows the failure recovery process in the 1st Embodiment of this invention. It is an example of the flowchart which shows the failure recovery process in the 2nd Embodiment of this invention. It is an example of the risk determination table which shows the generation | occurrence | production risk of the failure with respect to the communication apparatus in the 3rd Embodiment of this invention.

  Embodiments will be described in detail with reference to the drawings. However, the present invention is not construed as being limited to the description of the embodiments below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or the spirit of the present invention.

  In the structures of the invention described below, the same portions or portions having similar functions are denoted by the same reference numerals in different drawings, and redundant description may be omitted.

  In the present specification and the like, notations such as “first”, “second”, and “third” are attached to identify the components, and do not necessarily limit the number or order. In addition, a number for identifying a component is used for each context, and a number used in one context does not necessarily indicate the same configuration in another context. Further, it does not preclude that a component identified by a certain number also functions as a component identified by another number.

  The position, size, shape, range, and the like of each component illustrated in the drawings and the like may not represent the actual position, size, shape, range, or the like in order to facilitate understanding of the invention. For this reason, the present invention is not necessarily limited to the position, size, shape, range, and the like disclosed in the drawings and the like.

  Hereinafter, examples will be described with reference to the drawings. In this example, when a failure occurs in a part of the network, or when changing the network operation settings according to the time division such as maintenance, the settings of only the relevant part are not changed without changing the settings of the entire network. To enable efficient use of network resources, reduce the processing load for setting changes, and enable quick failure recovery and change of operation settings.

  In this embodiment, a virtual network (second network) for each user is configured on a physical network (first network), a plurality of virtual networks are combined to form a network group, and a combination of network groups is determined. An example in which the resources of the physical network to be used can be changed will be described. In this embodiment, an example in which a communication system forms a packet transport network will be described.

  FIG. 1 is an example of a network system configuration diagram in the first mode for embodying the present invention (Example 1). The network system of this embodiment includes a network management server 1, communication devices n11 to n14, n21 to n22, n31 to n33, n41 to n43, n51 to n53, n61 to n64, and terminals TA1, TA2, TB1, TB2, and TC1. , TC2, TD1, and TD2. In addition, although not a terminal but a server, another communication apparatus, and a network may be sufficient, in this example, it demonstrates as a terminal as an example. In FIG. 1, the network management server 1 is connected only to the communication device n14 for convenience, but is connected to other transmission devices via a management network (not shown).

  FIG. 2 is an example of a network system configuration diagram after setting an active path in the first embodiment of the present invention. At the operation start stage, the network management server 1 sets an active transmission path 201 (a1 of 201a to 201f connected to the terminal TA2 via the terminal TA1, the communication devices n11, n31, n41, n51, and n61). . Also, the active transmission path 202 (b1 of 202a to 202f connected to the terminal TB2 via the terminal TB1, the communication devices n12, n32, n42, n52, and n62) is set. Similarly, the active transmission path 203 (c1 of 203a to 203d connected to the terminal TC2 via the terminal TC1, the communication devices n41, n42, and n43) is set. Further, the active transmission path 204 (d1 of 204a to 204d connected to the terminal TD2 via the terminal D1, the communication devices n51, n52, and n53) is set.

  FIG. 3 is an example of a network system configuration diagram after the protection path is set according to the first exemplary embodiment of the present invention. The protection path is a redundant path set in advance, and when a failure occurs in the working path, the protection path is switched to restore the service. Path recovery using a protection path is called protection recovery. Such a recovery method is called a protection method or a protection method.

  The network management server 1 sets a protection path 301 (301a to 301f connected to the terminal TA2 via the terminal TA1, the communication devices n13, n33, n43, n53, and n63) for the active path 201. Also, a protection path 302 (302a to 302f connected to the terminal TB2 via the terminal TB1, the communication devices n13, n33, n43, n53, and n63) is set for the working path 202. Similarly, a protection path 303 (303a to 303d connected to the terminal TC2 via the terminal TC1, the communication devices n31, n32, and n33) is set for the active path 203. Further, a protection path 304 (304a to 304d connected to the terminal TD2 via the terminal TD1, the communication devices n31, n32, and n33) is set for the working path 204. As described above, one protection path is secured for one working system path. A plurality of protection paths may be secured for one working path.

  The terminal TA1 constantly monitors whether or not there is communication with the active transmission path 201 by transmitting and receiving inspection data to and from the terminal TA2. If the terminal TA1 determines that there is no communication with the terminal TA2 in the active transmission path 201, the terminal TA1 continues to communicate with the terminal TA2 using the protection path 301. That is, the terminal TA1 transmits data to the communication device n11 before the failure occurs, but after detecting the failure, the terminal TA1 switches instantaneously to transmit data to the communication device n13.

  The TB 1 constantly monitors whether or not there is communication with the active transmission path 202 by transmitting and receiving inspection data to and from the terminal TB 2. If the terminal TB1 determines that there is no communication with the terminal TB2 in the active transmission path 202, the terminal TB1 continues to communicate with the terminal TB2 using the protection path 302. In other words, the terminal TB1 transmits data to the communication device n12 before the occurrence of the failure. However, after detecting the failure, the terminal TB1 switches instantaneously to transmit data to the communication device n13.

  Similarly, the terminal TC1 constantly monitors whether or not there is communication with the active transmission path 203 by transmitting / receiving inspection data to / from the terminal TC2. If the terminal TC1 determines that there is no communication with the terminal TC2 in the active transmission path 203, the terminal TC1 continues to communicate with the terminal TC2 using the protection path 303. That is, the terminal TC1 transmits data to the communication device n41 before the failure occurs, but after detecting the failure, the terminal TC1 switches instantaneously to transmit data to the communication device n31.

  Further, the terminal TD1 constantly monitors whether or not there is communication with the active transmission path 204 by transmitting and receiving inspection data to and from the terminal TD2. If the terminal TD1 determines that there is no communication with the terminal TD2 in the active transmission path 204, the terminal TD1 continues to communicate with the terminal TD2 using the protection path 304. That is, the terminal TD1 transmits data to the communication device n51 before the occurrence of the failure. However, after detecting the failure, the terminal TD1 switches instantaneously so as to transmit data to the communication device n31.

  FIG. 4 is an example of a network system configuration diagram after setting the operation side change path in the first embodiment of the present invention. The network management server 1 analyzes the set active transmission paths 201 to 204, and manages the transmission paths having high similarity by grouping them. Transmission paths with high similarity tend to have a common cause of failure. At the same time, there is a tendency for failures to occur. For this reason, it is possible to effectively deal with a failure by collecting transmission paths having high similarity.

  For example, in the transmission path route, the larger the number or ratio of sharing communication devices, the higher the similarity. Alternatively, in the transmission path route, the higher the number or ratio of using parallel communication devices, the higher the similarity. In the present embodiment, in the path of the transmission path, for example, transmission paths sharing three or more communication devices or transmission paths using three or more parallel communication devices are grouped. Specifically, the active transmission path 201 and the transmission path 202 are grouped and managed as a network group 1 (410).

  On the other hand, as another index, the grouping may be determined using the overlapping degree of shared links as an index. For example, communication devices that constitute a transmission path, or devices that have a large degree of link overlap are grouped. Further, when there is a network that is a subset with respect to a certain network, these networks may be grouped. That is, when a topology constituting a certain transmission path becomes a subset of the topology constituting another transmission path, these are grouped. A network group may be configured based on the connectivity of networks having a data flow with a data transmission amount of a predetermined number (for example, 10 Gbit / second) or more.

  Similarly, the active transmission path 203 and the transmission path 204 are grouped and managed as a network group 2 (420). The network groups may have overlapping portions as shown in FIG. The grouping need only be considered for the transmission path of the active system, and need not be considered for the protection path.

  The network management server 1 calculates, in advance, a change in operation setting for the combination of the grouped network group 1 and network group 2. That is, the network setting for recovery when a failure has occurred in the network group 1 (410) is calculated in advance. Further, the network settings for recovery when a failure has occurred in the network group 2 (420) are calculated in advance. Further, the network settings for recovery when a failure occurs simultaneously in the network group 1 and the network group 2 are calculated in advance.

  In the present embodiment, the network management server 1 assumes a case where a failure has occurred in the network group 1 and calculates operation settings for recovery in advance. That is, the transmission path 401 for changing the operation plane for the active paths 201 and 202 constituting the network group 1 (401a to 401d connected to the terminal TA2 via the terminal TA1, the communication devices n14, n22, and n64), and 402 (402a to 402d connected to the terminal TB2 via the terminal TB1, the communication devices n14, n22, and n64) is calculated in advance, and the identifier F1 is assigned and managed.

  In addition, the network management server 1 transmits the operation path change transmission path 403 for the working paths 203 and 204 constituting the network group 2 (403a to 403a connected to the terminal TC2 via the terminal TC1, the communication devices n21 and n22). 403c) and 404 (404a to 404c connected to the terminal TD2 via the terminal TD1 and the communication devices n21 and n22) are calculated in advance, and are managed with the identifier F2.

  Similarly, the network management server 1 calculates a recovery operation setting in advance assuming that a failure occurs simultaneously with a combination of network groups. In the present embodiment, recovery operation settings are calculated assuming that a failure occurs simultaneously in the network group 1 and the network group 2. Specifically, recovery transmission paths for the active paths 201, 202, 203, and 204 are calculated. In this embodiment, 401, 402, 403, and 404 are calculated as recovery transmission paths, and are managed by assigning F3 as an identifier for operation setting change. In the present embodiment, the recovery transmission paths are calculated in the same way when a failure occurs individually in each of the network group 1 and the network group 2 and when a failure occurs at the same time, but they are the same. There is no need. Further, the number of recovery transmission paths is not limited to the above example, and a large number or a small number of paths may be provided.

  In the present embodiment, all the network connections have been described on the assumption that the same network is used. However, the network connecting the terminal and the communication device may be set to have a different type from the network connecting the communication devices. For example, the network connecting the communication devices may be an MPLS-TP (Multi-Protocol Label Switching-Transport Profile) network, and the network connecting the terminal and the communication device may be an IP (Internet Protocol) network.

  FIG. 5 is an example of a sequence diagram illustrating a flow of failure recovery pre-setting processing according to the first embodiment of this invention. The network management server 1 calculates the working transmission path route based on the working path setting input from the network administrator or the like, and executes the working path setting to the related communication device (steps S501-1 to S501). -5).

  The network management server 1 calculates a protection path (FIGS. 3, 301a, 302a, 303a, and 304a) for the set active transmission path, and executes settings for the related communication devices (steps S502-1 to S502-5). ).

  The network management server 1 compares the calculated paths of the plurality of active paths, and groups and manages transmission paths having high similarity (see FIGS. 4, 410, and 420) (step S503).

  The network management server 1 creates a communication failure determination table (detailed later in FIG. 8) indicating the relationship between the communication device in which the failure has occurred and the affected network group (step S504).

  The network management server 1 creates a protection failure determination table (detailed later in FIG. 9) indicating the relationship between the communication device in which the failure has occurred and the protection path for the affected network group (step S505).

  The network management server 1 calculates a recovery transmission path setting for each combination of network groups (step S506). In this calculation, a recovery transmission path (FIGS. 4, 401, 402, 403, and 404) that avoids a working path and a protection path that are affected by a failure is generated using available resources. The generated recovery transmission path is stored in a group correspondence recovery setting table (detailed later in FIG. 10) indicating the relationship between the failure group network and the recovery setting.

  The network management server 1 calculates a recovery transmission setting for each device from the recovery transmission path setting for each combination of network groups (step S507). Here, the meaning of “for each combination” is for all combination patterns including the case of one element. For example, as described in FIG. 10 described later, a combination including one group such as a network group 1 (1010) and a combination including two groups such as a network group 1 and 2 (1012) Including the case where one group is included, it is expressed as “for each combination”.

  The calculated result is stored in the network management server 1 as an identifier corresponding recovery setting table (which will be described in detail later with reference to FIGS. 11 to 13) indicating the path recovery setting for each communication device with respect to the recovery identifier. Further, it is stored in the network management server 1 as a network recovery group recovery setting table (communication device corresponding recovery setting table) (which will be described in detail later with reference to FIGS. 14A to 14D) indicating path recovery settings for each recovery identifier for the communication device.

  The network management server 1 notifies each device of the transmission settings for restoration in the calculated devices, and each communication device holds the received transmission settings for restoration together with the identifier (steps S508-1 to S508-3). . The received result is stored in each communication device as a network group recovery setting table (communication device corresponding recovery setting table) (which will be described in detail later with reference to FIGS. 14A to 14D) indicating path recovery settings for each communication device.

  The network management server 1 notifies the terminals TA1, TB1, TC1, and TD1 that the notification of the transmission path settings for data transmission and recovery has been completed to each device (step S509).

  The terminal TA1 transmits data to the terminal TA2 via the communication devices n11, n31, n41, n51, and n61 and starts communication confirmation (steps S510-1 to S510-6).

  The terminal TB1 transmits data to the terminal TB2 via the communication devices n12, n32, n42, n52, and n62 and starts communication confirmation (steps S511-1 to S511-6).

  The terminal TC1 transmits data to the terminal TC2 via the communication devices n41, n42, and n43 and starts communication confirmation (steps S5121 to S512-2).

  The terminal TD1 transmits data to the terminal TD2 via the communication devices n51, n52, and n53 and starts communication confirmation (steps S513-1 to S513-2).

  FIG. 6 is an example of a sequence diagram illustrating an example of the flow of recovery processing according to the protection recovery and operation side change path according to the first embodiment of the present invention. After data transmission / reception is started between the terminals, a failure occurs in the communication devices n11 and n12 (step S601).

  The terminals TA1 and TB1 detect that a failure has occurred in data transmission / reception (step S602).

  After detecting that a failure has occurred in data transmission / reception through the working path, the terminal TA1 transmits data to the terminal TA2 using the protection path (steps S603-1 to 603-6).

  After detecting that a failure has occurred in data transmission / reception through the working path, the terminal TB1 transmits data to the terminal TB2 using the protection path (steps S604-1 to 604-6).

  The terminal TA1 notifies the network management server 1 that a failure has occurred in the communication device n11 (step S605).

  Further, the terminal TA1 notifies the network management server 1 that the failure has been recovered by the protection path (step S606).

  The terminal TB1 notifies the network management server 1 that a failure has occurred in the communication device n12 (step S607).

  Further, the terminal TB1 notifies the network management server 1 that the failure has been recovered by the protection path (step S608).

  Subsequently, a failure occurs in the communication devices n31, n32, and n33 (step S609).

  The communication device n13 notifies the network management server 1 that a failure has occurred in the communication device n33 (step S610).

  The communication device n41 notifies the network management server 1 that a failure has occurred in the communication device n31 (step S611).

  The communication device n42 notifies the network management server 1 that a failure has occurred in the communication device n32 (step S612).

  The network management server 1 determines the network group in which the failure has occurred based on the received failure occurrence information of the communication device, and identifies the recovery identifier (ID) (step S613).

  The network management server 1 notifies the communication devices n14, n22, and n64 of the recovery ID in order to recover the data transmission failure that has occurred (steps S614, S615, and S616).

  The network management server 1 notifies the terminals TA1 and TB1 to change the data transmission destination (steps S617 and S618).

  The terminal TA1 transmits data to the terminal TA2 via the communication devices n14, n22, and n64 (Steps S619-1 to S619-4).

  The terminal TB1 transmits data to the terminal TB2 via the communication devices n14, n22, and n64 (Steps S620-1 to S620-4).

  FIG. 7 is an example of a sequence diagram showing a flow of recovery processing by the second operation side change path in the first embodiment of the present invention. Following the state described in FIG. 6, it is assumed that a failure has occurred in the communication devices n41, n42, n51, and n52 (steps S701-1 to S701-2).

  The terminal TC1 notifies the network management server 1 that a failure has occurred in the communication device n41 because the data transmission failure cannot be recovered by protection (step S702).

  The terminal TD1 notifies the network management server 1 that a failure has occurred in the communication device n51 because the data transmission failure cannot be recovered by protection (step S703).

  The communication device n43 notifies the network management server 1 that a failure has occurred in the communication device n42 (step S704).

  The communication device n42 notifies the network management server 1 that a failure has occurred in the communication device n52 (step S705).

  The network management server 1 determines the network group in which the failure has occurred based on the received failure occurrence information of the communication device, and identifies the recovery identifier (ID) (step S706).

  The network management server 1 notifies the communication devices n21 and n22 of the recovery ID in order to recover the data transmission failure that has occurred (steps S707 and S708).

  The network management server 1 notifies the terminal TC1 and the terminal TD1 to change the data transmission destination when the setting change notification to the communication device for recovering the data transmission failure that has occurred is completed (step S1). S709, S710).

  The terminal TC1 changes the data transmission destination from the communication device n41 to the communication device n21, and transmits data to the terminal TC2 via the communication device n22 (steps S711-1 to S711-2).

  The terminal TD1 changes the data transmission destination from the communication device n51 to the communication device n21, and transmits data to the terminal TD2 via the communication device n22 (steps S712-1 to S712-2).

  5-7, the operation setting for change is distributed to each communication device in advance, and the network management server notifies each communication device of an identifier for changing the operation setting. Explained how to change. On the other hand, when the network management server holds the operation settings and changes the operation settings, the operation settings may be changed by notifying each communication device of the operation settings for the change.

  FIG. 8 is an example of a communication failure determination table that is created in step S504 of FIG. 5 and that is held by the network management server 1 according to the first embodiment of the present invention and indicates a relationship between a communication device failure and a group network failure that occurs. is there. A network group affected by a communication device failure is configured and managed from a communication device failure 801 and a list of affected network groups (802, 803,...).

  The communication device failure 810 assumes that a failure has occurred in the communication device n11, and indicates that data transmission affects the network group 1 but does not affect the network group 2. Similarly, the communication device failure 811 assumes a state in which a failure has occurred in the communication device n12, and shows that the data transmission affects the network group 1 but does not affect the network group 2. Yes. Further, in the communication device failures 812 to 815, it is assumed that failures occur in the communication devices n13, n14, n21, and n22 in order, and the data transmission affects both the network group 1 and the network group 2. It shows that it does not receive.

  On the other hand, the communication device failure 816 assumes that a failure has occurred in the communication device n31 and does not affect the network group 1 as data transmission, but indicates that the network group 2 is affected. Similarly, in the communication device failures 817 to 824, it is assumed that a failure has occurred in the communication devices n32, n33, n41, n42, n43, n61, n62, and n63 in order. 2 indicates whether or not there is an influence.

  FIG. 9 is a protection failure determination table created in step S505 of FIG. 5 and held by the network management server 1 according to the first embodiment of the present invention and indicating the relationship between the communication device failure and the protection failure for the group network that occurs. It is an example. Protection for a network group affected by a communication device failure is configured and managed from a communication device failure 901 and a protection list (902, 903,...) Of the affected network group.

  The communication device failure 910 assumes a state in which a failure has occurred in the communication device n11, and indicates that no protection path of the network group 1 or the network group 2 is affected as a detour. That is, it means that the communication device n11 is not used for any protection path of the network group 1 and the network group 2.

  The communication device failure 911 assumes a situation in which a failure has occurred in the communication device n12, and indicates that no protection path of the network group 1 and the network group 2 is affected as a detour.

  On the other hand, the communication device failure 912 assumes a situation in which a failure has occurred in the communication device n13 and affects the protection path of the network group 1 as a detour, but does not affect the protection path of the network group 2. It shows that it does not affect. Further, the communication device failure 913 assumes a situation where a failure has occurred in the communication device n14, and shows that no protection path of the network group 1 and the network group 2 is affected as a detour. Yes.

  On the other hand, the communication device failure 914 assumes a situation in which a failure has occurred in the communication device n21, and does not affect the protection path of the network group 1 as a detour, but affects the protection path of the network group 2. It shows that Similarly, in the communication device failures 915 to 924, it is assumed that the failure occurs in the communication devices n22, n31, n32, n33, n41, n42, n43, n61, n62, and n63 in order. It shows whether the protection path of 1 and the protection path of network group 2 are affected.

  FIG. 10 is an example of a group correspondence recovery setting table showing the recovery path setting for the failed network group and the communication device for recovery, which the network management server 1 according to the first embodiment of the present invention has. The path setting for recovery is configured and managed by a combination 1001 of failure networks, a recovery identifier 1002, a path identifier 1003, a recovery setting 1004, and a recovery setting validity 1005.

  When a failure has occurred in the network group 1, the recovery setting 1010 indicates that management is performed with the recovery identifier = F1. The designation of the restoration identifier F1 indicates that the path (a1) from the terminal TA1 to the terminal TA2 is restored by a path that passes through the communication devices n14, n22, and n64. Further, it is shown that the path (b1) from the terminal TB1 to the terminal TB2 is restored by a path passing through the communication devices n14, n22, and n64.

  In the case where a failure has occurred in the network group 2, the recovery setting of 1011 is managed by the recovery identifier = F2. The designation of the restoration identifier F2 indicates that the path (c1) from the terminal TC1 to the terminal TC2 is restored by a path passing through the communication devices n21 and n22. In addition, the path (d1) from the terminal TD1 to the terminal TD2 is restored by a path that passes through the communication devices n21 and n22. Further, when a failure has occurred in the network groups 1 and 2, the recovery setting 1012 indicates that management is performed with the recovery identifier = F3. According to the designation of the recovery identifier F3, the failure recovery is executed according to the transmission path 1004 calculated in advance. However, in a situation where a failure has occurred in any of the communication devices necessary for the recovery setting, the validity 1005 is managed as invalid (0) instead of valid (1), and whether or not the recovery setting can be used. Is managed.

  In the validity 1005, when the state is managed as invalid (0), failure recovery in this setting is invalid, and a path for recovery is calculated separately. In this embodiment, the recovery settings for the path a1 and the path b1 are the same, but different paths may be used. Further, the recovery settings of the paths (a1, b1, c1, d1) managed by the recovery identifier = F3 are the same as the recovery settings managed by the recovery identifier = F1 and the recovery identifier = F2, but are different. Recovery settings may be used.

  Although the present embodiment shows an example in which the paths a1 and b1 belonging to the network group 1 are set to be restored using the same route, that is, the same route via the communication devices n14, n22, and n64, the network There are cases where not all paths can be recovered due to lack of resources. In such a case, it may be set to restore preferentially according to the priority of the network to be used. Further, when network resources are insufficient, a path with a large network bandwidth to be used may be preferentially restored and set, or a path with a small network bandwidth to be used may be preferentially restored and set.

  FIG. 11 is an example of an identifier corresponding recovery setting table showing path recovery settings for each communication device with respect to the recovery identifier F1 according to the first embodiment of the present invention. Recovery when a failure occurs in the network group 1 is identified by a recovery identifier F1. The recovery path setting for the recovery identifier is configured and managed by a recovery identifier (ID) 1301, a target communication device 1302, a path identifier (ID) 1303, and connection destinations 1304 and 1305, which are lists of connection destinations. .

  In the recovery identified by the recovery identifier F1, the communication devices 1311 to 1313 are targeted for recovery control. In the communication device n14, for the path a1, a setting for transmitting data received from the terminal TA1 to the communication device n22 is shown. In the communication device n14, for the path b1, the setting for transmitting the data received from the terminal TB1 to the communication device n22 is shown. In the communication apparatus n22, the setting which transmits the data received from the communication apparatus n14 with respect to bus | bath a1 and b1 to the communication apparatus n64 is shown. In communication apparatus n64, for path a1, data received from communication apparatus n22 is transmitted to terminal TA2, and for path b1, data received from communication apparatus n22 is transmitted to terminal TB2. Yes. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  FIG. 12 is an example of an identifier corresponding recovery setting table showing path recovery settings for each communication device for the recovery identifier F2 in the first embodiment of the present invention. Recovery when a failure occurs in the network group 2 is identified by a recovery identifier F2. The recovery path setting for the recovery identifier is configured and managed by a recovery identifier (ID) 1301, a target communication device 1302, a path identifier (ID) 1303, and connection destinations 1304 and 1305, which are lists of connection destinations. .

  In the recovery identified by the recovery identifier F2, the communication devices 1411 to 1412 are targeted for recovery control. In the communication device n21, the setting for transmitting data received from the terminal TC1 to the communication device n22 is shown for the path c1. In the communication device n21, for the path d1, a setting for transmitting data received from the terminal TD1 to the communication device n22 is shown. In the communication device n22, for the path c1, the setting is such that data received from the communication device n21 is transmitted to the terminal TC2, and for the path d1, the data received from the communication device n21 is transmitted to the terminal TD2. Yes. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  FIG. 13 is an example of an identifier corresponding recovery setting table showing the path recovery setting for each communication device for the recovery identifier F3 in the first embodiment of the present invention. Recovery when a failure occurs in the network groups 1 and 2 is identified by a recovery identifier F3. The recovery path setting for the recovery identifier is configured and managed by a recovery identifier (ID) 1301, a target communication device 1302, a path identifier (ID) 1303, and connection destinations 1304 and 1305, which are lists of connection destinations. .

  In the recovery identified by the recovery identifier F3, the communication devices 1511 to 1515 are targeted for recovery control. In the communication apparatus n14, a configuration is shown in which the data received from the terminal TA1 is transmitted to the communication apparatus n22 for the path a1, and the data received from the terminal TB1 is transmitted to the communication apparatus n22 for the path b1. Yes. In the communication apparatus n22, the setting which transmits the data received from the communication apparatus n14 with respect to bus | bath a1 and b1 to the communication apparatus n64 is shown. In communication apparatus n64, for path a1, data received from communication apparatus n22 is transmitted to terminal TA2, and for path b1, data received from communication apparatus n22 is transmitted to terminal TB2. Yes. In the communication device n21, a setting for transmitting data received from the terminal TC1 to the communication device n22 for the path c1 and transmitting data received from the terminal TD1 to the communication device n22 for the path d1 is shown. Yes. In the communication device n22, for the path c1, the setting is such that data received from the communication device n21 is transmitted to the terminal TC2, and for the path d1, the data received from the communication device n21 is transmitted to the terminal TD2. Yes. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  14A to 14D are examples of a network group recovery setting table (communication device corresponding recovery setting table) showing path recovery settings for each communication device according to the first embodiment of the present invention. The setting of the recovery path for the communication device is configured and managed by a target communication device 1601, a recovery identifier (ID) 1602, a path identifier (ID) 1603, and a connection destination list 1604 and 1605. .

  FIG. 14A shows a recovery path setting for each recovery identifier for the communication device n14, which is a database calculated and held in the network management server 1 and also held in the communication device n14. In the communication device n14, path setting is performed in a recovery setting (recovery identifier F1) 1611 when a failure occurs in the network group 1 and a recovery setting (recovery identifier F3) 1612 when a failure occurs in the network groups 1 and 2. Indicates that a change is required.

  In the communication device n14, when the recovery identifier F1 is received, the data received from the terminal TA1 is transmitted to the communication device n22 for the path a1, and the data received from the terminal TB1 is transmitted to the communication device n22 for the path b1. The setting to transmit to n22 is shown.

  When the recovery identifier F3 is received, the data received from the terminal TA1 is transmitted to the communication device n22 for the path a1, and the data received from the terminal TB1 is transmitted to the communication device n22 for the path b1. Shows the settings. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  FIG. 14B shows a recovery path setting for each recovery identifier for the communication device n22, which is a database calculated and held in the network management server 1 and also held in the communication device n22. In the communication device n22, a recovery setting (recovery identifier F1) 1621 when a failure occurs in the network group 1, a recovery setting (recovery identifier F2) 1622 when a failure occurs in the network group 2, and the network groups 1 and 2 In the recovery setting (recovery identifier F3) 1623 when a failure occurs, it is indicated that the path setting needs to be changed.

  In the communication apparatus n22, when the recovery identifier F1 is received, the setting which transmits the data received from the communication apparatus n14 to the communication apparatus n64 with respect to the paths a1 and b1 is shown.

  When the recovery identifier F2 is received, the data received from the communication device n21 is transmitted to the terminal TC2 for the path c1, and the data received from the communication device 21 is transmitted to the terminal TD2 for the path d1. Is shown.

  When the recovery identifier F3 is received, the settings for transmitting the data received from the communication device n14 to the communication device n64 are shown for the paths a1 and b1. In addition, for the path c1, data received from the communication device n21 is transmitted to the terminal TC2, and for the path d1, a setting for transmitting data received from the communication device 21 to the terminal TD2 is shown. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  FIG. 14C shows a recovery path setting for each recovery identifier for the communication device n64, which is a database calculated and held by the network management server 1 and also held by the communication device n14. In the communication device n64, path setting is performed in a recovery setting (recovery identifier F1) 1631 when a failure occurs in the network group 1 and a recovery setting (recovery identifier F3) 1632 when a failure occurs in the network groups 1 and 2. Indicates that a change is required.

  When the recovery identifier F1 is received in the communication device n64, the data received from the communication device n22 is transmitted to the terminal TA2 for the path a1, and the data received from the communication device n22 is transmitted to the terminal for the path b1. The setting to transmit to TB2 is shown.

  When the recovery identifier F3 is received, the data received from the communication device n22 is transmitted to the terminal TA2 for the path a1, and the data received from the communication device n22 is transmitted to the terminal TB2 for the path b1. Shows the settings. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  FIG. 14D shows a recovery path setting for each recovery identifier for the communication device n21, which is a database calculated and held by the network management server 1 and also held by the communication device n21. In the communication device n21, path setting is performed in a recovery setting (recovery identifier F2) 1641 when a failure occurs in the network group 2 and a recovery setting (recovery identifier F3) 1642 when a failure occurs in the network groups 1 and 2. Indicates that a change is required.

  In the communication device n21, when the recovery identifier F2 is received, the data received from the terminal TC1 is transmitted to the communication device n22 for the path c1, and the data received from the terminal TD1 is transmitted to the communication device n22 for the path d1. The setting to transmit to n22 is shown.

  When the recovery identifier F3 is received, the data received from the terminal TC1 is transmitted to the communication device n22 for the path c1, and the data received from the terminal TD1 is transmitted to the communication device n22 for the path d1. Shows the settings. For bidirectional data communication, although not shown, data transmission setting information in the reverse direction is separately held.

  As described above, by distributing a set of recovery identifier and recovery path setting information to each communication device in advance, the network management server can perform recovery settings for each communication device only by notifying the recovery identifier. .

  FIG. 15 is a diagram illustrating a configuration example of a communication device according to the first embodiment of the present invention. The communication device 1700 includes network interfaces 1701-1 to 1701-n, a switch 1701, a table management unit 1703, a data transfer table 1704, a usage table control unit 1707, and a protection management unit 1708.

  Further, the data transfer table 1704 includes a table 1705 indicating path settings for the active system, and a network group recovery setting table (communication device corresponding recovery setting table) 1706 indicating settings for recovering a failure in units of group network combinations. Composed. The network group recovery setting table 1706 is the table shown in FIGS. 14A to 14D and is sent from the management server 1 for each communication device.

  The communication device 1700 receives the data for path setting and the setting for recovery via the network interface 1701, and transmits / receives data for confirming the operation status of the set transmission path. When receiving the transfer data, the switch 1702 switches the data to the output destination network interface according to the data transfer table 1704. When the received data is data for path setting and path setting for recovery, the switch 1702 switches the received data to the table management unit 1703. When the data for confirming the operation status of the transmission path is received, the switch 1702 transfers the data to the protection management unit 1708. When the operation status confirmation data is received from the protection management unit 1708, the switch 1702 transfers the operation status confirmation data to an appropriate interface toward another communication device in accordance with the transmission destination identifier.

  The table management unit 1703 updates the working table 1705 when the received data is the working path setting. When the received data is a path setting for recovering a failure for a combination of network groups, the network group recovery setting table 1706 is updated. When the received data is a recovery identifier (ID) that specifies a path setting for recovery, the table management unit 1703 notifies the usage table control unit 1707 of the received recovery identifier (ID). The usage table control unit 1707, according to the recovery identifier (ID) received from the table management unit 1703, sets the setting information used for the received data transfer by the switch 1702 and the recovery path setting indicated by the recovery identifier (ID) in the network group. The data is selected from the recovery setting table 1706 and the data in the active system table 1705 is updated.

  For example, referring to FIG. 14A showing the network group recovery setting table 1706 indicating the setting of the communication device n14, when the communication device n14 receives “F1” as the recovery identifier 1602, n14 is a path identifier corresponding to “F1”. In accordance with 1603 and the connection destinations 1604 and 1605, the data in the active system table 1705 is updated and a recovery path is set. That is, in order to form the path a1, the terminal TA1 and the communication device n22 are connected.

  As for the physical configuration of the communication device shown in FIG. 15, the protection management unit 1708 and the table management unit 1703 execute a program stored in a storage device (not shown) by a processor (not shown) to perform other processes determined. Realized in cooperation with hardware. In this specification, a program executed by a computer, its function, or means for realizing the function may be referred to as “function”, “means”, “unit”, “unit”, “module”, or the like.

  Various programs may be installed in each computer by a program distribution server or a computer-readable storage medium. In this case, the program distribution server includes a processor and a storage resource, and the storage resource further stores a distribution program and a program to be distributed. When the processor executes the distribution program, the processor of the program distribution server distributes the distribution target program to other computers.

  In addition, in the embodiment, functions equivalent to functions configured by software can be realized by hardware such as FPGA (Field Programmable Gate Array) and ASIC (Application Specific Integrated Circuit). Such an embodiment is also included in the scope of the present invention.

  The data transfer table 1704 is stored in the storage device. In the present specification, the configuration is described using expressions such as “˜table”, “˜list”, “˜DB (Database)”, “˜queue”, “information”, etc., as long as these are equivalent information. , Tables, lists, DBs, queues, and other data structures.

  Further, in describing the contents of each information, the expressions “identification information”, “identifier”, “name”, “name”, and “ID (IDentification)” are used, but these can be replaced with each other. .

  The above applies similarly to the network management server of FIG. FIG. 16 is a diagram illustrating a configuration example of the network management server according to the first embodiment of the present invention. The network management server 1 includes a CPU 1801 that is a processor (processing device), a memory 1802 and storage 1803 that are storage devices, and network interfaces 1804 (1804 to 1804-n) that are input devices and output devices. They are connected to each other via a bus 1800. Further, an input / output device (not shown) such as a keyboard or an image display device may be provided.

  The CPU 1801 operates as various functional units by loading various programs stored in the storage 1803 into the memory 1802 and executing the programs. The functions of the network management server 1 can be realized by the CPU 1801 executing the program. The memory 1802 stores a program executed by the CPU 1801 and data necessary for executing the program. Specifically, the program is configured to be able to execute the processing described below with reference to FIG. A network interface 1804 is an interface for connecting to one or more external networks. Further, the memory 1802 or the storage 1803 stores various tables described in FIGS. 8 to 14 as necessary. The configuration of this embodiment may be configured by a single computer as shown in FIG. 16, or any part of the input device, output device, processing device, and storage device may be connected via a network. The computer may be configured.

  FIG. 17 is an example of a flowchart showing the failure recovery processing in the first embodiment of the present invention. The network management server 1 starts by loading the failure recovery management program into the CPU (step S1100).

  The CPU 1801 of the network management server 1 calculates the working transmission path route and the protection path route based on the working path setting input from the network manager or the like, and sends the working system and protection to the related communication device via the interface 1804. A path is set (step S1101). The setting is set in the protection management unit 1708 and the active system table 1705 of each communication device.

  The CPU 1801 of the network management server 1 compares the calculated paths of a plurality of active paths (each user's network), groups highly similar transmission paths, stores them in the memory 1802, and manages them (step S1102). .

  The CPU 1801 of the network management server 1 includes a communication failure determination table indicating the relationship between the communication device in which the failure has occurred and the network group affected by the failure, and a protection failure determination table indicating the relationship between the protection paths of the network group (FIG. 8 and FIG. 8). 9) (step S1103). These tables are also stored in the memory 1802. The CPU 1801 of the network management server 1 assigns an identifier (ID) to each combination pattern of network groups in which a failure occurs in data transmission, calculates a recovery path setting, and sets a group correspondence recovery setting table. (See FIG. 10) is configured (step S1104). This table is also stored in the memory 1802.

  The CPU 1801 of the network management server 1 divides and configures the recovery transmission path setting calculated for each combination pattern of the network group for each communication device, and generates a network group recovery setting table (see FIGS. 14A to 14D) (steps). S1105).

  The CPU 1801 of the network management server 1 distributes the configured network group recovery setting table for each communication device together with the recovery identifier (ID) to each communication device via the interface 1804 (step S1106). Each communication device 1700 registers the data transfer table 1704 as the network group recovery setting table 1706 under the control of the usage table control unit 1707.

  The above processing is a preparation stage, and the network is ready to execute the failure recovery processing of this embodiment up to step S1106. The following step S1107 and subsequent steps are processing when a failure occurs. Steps up to step S1106 and steps after step S1107 may be performed by the same network management server 1 or may be performed by different servers.

  The CPU 1801 of the network management server 1 starts monitoring whether a failure has occurred in the network. A conventional technique can be applied to the monitoring method. For example, failure information from each communication device is collected. With reference to the protection failure determination table (FIG. 9), using the identifier of the communication device in which the failure has occurred as a key, it is determined whether or not the protection failure has occurred (step S1107).

  If it is determined in step S1107 that no protection is not possible, the CPU 1801 continues the process in step S1107. If no protection failure has occurred, even if there is a failure, the failure can be recovered by switching the path using the conventional protection method.

  If it is determined in step S1107 that recovery is impossible due to protection, a network group that cannot be recovered by the protection method is specified from the protection failure determination table (FIG. 9). Based on the identified network group, the recovery identifier corresponding to the combination pattern of the network group in which the failure has occurred is identified from the group-corresponding recovery setting table (FIG. 10), and the recovery identifier is set via the interface 1804. The communication device is notified of the recovery ID (step S1108).

  As described above, when a failure occurs in a communication device, if recovery is possible using a protection path, data transmission is instantaneously recovered using the protection path. In addition, when recovery of data transmission failure by the protection path is impossible, by using the data transmission path for recovery calculated in advance for the network group that has failed in data transmission due to communication device failure, Data transmission is restored quickly.

  That is, according to the present embodiment, it is possible to quickly recover from a failure that occurs in a virtual network configured on a physical network. In addition, it is possible to quickly change the network operation setting in response to a change in some network settings for maintenance or a change in the network operation setting according to the time division. By preparing the operation settings to be prepared in advance for a combination of network groups that are summarized according to the similarity of the set networks, it is possible to change the settings of networks that are likely to be changed simultaneously. Become. Also, by configuring a network group that is grouped according to the similarity of the set networks, it is possible to reduce the number of operation setting patterns to be prepared. In addition, if recovery using a protection path is possible, recovery can be performed using protection, and if recovery using a protection path is not possible, a configuration that uses operational settings for changes prepared in advance can be used. Disaster recovery and operational setting changes can be performed quickly.

  FIG. 18 is an example of a flowchart showing failure recovery processing in the second mode for embodying the present invention (Example 2). In the first embodiment, the failure recovery processing for the network group is executed by using the failure recovery possibility by protection as a trigger. In this embodiment, however, the failure recovery processing for the network group is performed after accumulating and holding the generated failure for a certain time. It is determined whether or not to execute. Note that steps S1100 to S1106 described in FIG. 11 are the same processing, and thus description thereof is omitted. The network management server 1 monitors whether or not a communication device failure has occurred (step S1201).

  If it is determined in step S1201 that no failure has occurred in the communication device, the processing in step S1201 is continued. If it is determined in step S1201 that a failure has occurred in the communication device, a timer for storing failure information is started (step S1202).

  The network management server 1 records the received communication device failure information (step S1203).

  Subsequently, the network management server 1 determines whether or not a predetermined time (for example, 1 second) has elapsed in the timer that is activated upon receiving the failure occurrence notification (step S1204).

  If it is determined in step S1204 that the predetermined time has not elapsed, the process of step S1203 is executed. If it is determined in step S1204 that a predetermined time has elapsed, a failure pattern for the network group is determined from all the stored failure information, and if a failure has occurred for the network group, recovery is performed. Identifier (ID) is identified, and the recovery identifier is notified to the communication device related to the failure recovery (step S1205).

  On the other hand, if no failure has occurred in the network group, the process of step S1201 is executed without executing any special process.

  As described above, a recovery data transmission path calculated in advance is used for a network group in which a data transmission failure has occurred based on failure information of a communication device that has occurred during a predetermined time. As a result, data transmission is quickly restored. After accumulating and maintaining the failure occurring as in the second embodiment for a certain period of time, it is determined whether or not the failure recovery processing for the network group is executed, so that the accuracy of the determination is increased and the reliability of the system is increased. be able to.

  In the first embodiment, the networks are grouped and managed according to the set network similarity. However, in this embodiment, an example of performing network grouping considering the risk of failure occurrence will be described.

  FIG. 19 is an example of a risk determination table indicating the risk of failure occurrence with respect to a communication device according to the third mode for embodying the present invention (Example 3). The risk of failure occurrence for a communication device is configured and managed by a communication device 1901, a manufacturing date 1902, a failure occurrence risk 1903, and a communication device group 1904. As an example, the failure occurrence risk 1903 is determined by the date on which the communication device was manufactured. Specifically, a large failure occurrence risk (identifier 1) is set for an apparatus whose manufactured date is 10 years or older.

  Subsequently, adjacent communication devices are grouped with respect to communication devices having a high risk of failure occurrence. In this embodiment, since the communication devices n11 and n12 are adjacent to each other, the communication device group 1 is configured. Further, since the communication devices n43 and n53 are adjacent to each other, the communication device group 2 is configured. Subsequently, networks including communication devices belonging to the communication device group 1 are grouped.

  That is, the network group 1 is configured for the network between the terminals TA1 and TA2 and the network between the terminals TB1 and TB2 shown in the first embodiment. Similarly, network group 2 is configured for the network between terminals TC1 and TC2 and the network between terminals TD1 and TD2. As for the operation setting for change, as described in the first embodiment, the setting change is calculated in advance for the change of the network group 1, the change of the network group 2, and the simultaneous change pattern of the network groups 1 and 2.

  In this embodiment, the risk of failure occurrence is determined based on the date of manufacture. However, other methods, for example, the date of installation of the communication device or the communication with the higher failure occurrence frequency as a past case. The risk of failure occurrence may be determined by a device or the like. As in the third embodiment, by including only a network that uses a communication device having a relatively high probability of a failure in the network group, it is possible to focus on the failure and increase the efficiency of the system. be able to.

  The present invention is not limited to the embodiments described above, and includes various modifications. For example, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. Further, it is possible to add, delete, and replace the configurations of other embodiments with respect to a part of the configurations of the embodiments.

1 network management server n11, n12, n13, n14 communication device n21, n22 communication device n31, n32, n33 communication device n41, n42, n43 communication device n51, n52, n53 communication device n61, n62, n63, n64 communication device TA1, TA2, TB1, TB2 terminal TC1, TC2, TD1, TD2 terminal

Claims (15)

A network system comprising a network composed of a plurality of communication devices and a network management device for managing the network,
The network includes a plurality of second networks on the first network,
The network management device includes an input device, an output device, a processing device, and a storage device,
The storage device
Grouping the second network into a plurality of network groups, holding network setting information for changing the resources of the first network corresponding to each combination of the network groups,
The processor is
When it is determined that a failure has occurred in the network group based on information obtained from the input device, the network setting information is selected based on a combination of the network groups in which the failure has occurred, and the output device By notifying the selected network setting information to the communication device by
Making the resource of the first network changeable;
Network system. The network management device includes:
As the network setting information, it has a recovery identifier that identifies a combination of the network groups, and notifies the communication device of the recovery identifier by the output device,
The communication device
Holding the recovery identifier and recovery setting information corresponding to the recovery identifier, and when receiving the recovery identifier, changing the resources of the first network according to the corresponding recovery setting information;
The network system according to claim 1. Allowing the plurality of network groups to share the same communication device;
The network system according to claim 1 or 2. The network group is
Grouping the plurality of second networks according to the degree of similarity between the second networks;
The network system according to claim 1 or 2. The network group is
Grouping the plurality of second networks according to the duplication degree of the communication device constituting the second network or the link provided in the communication device;
The network system according to claim 1 or 2. The network group is
Grouping the plurality of second networks when the topology constituting the second network is a subset of the topology constituting the other second network;
The network system according to claim 1 or 2. Including only the second network using a communication device having a relatively high probability of failure in the network group;
The network system according to claim 1 or 2. The network management device includes:
3. The network system according to claim 1, wherein a protection path for the second network is set, and when the recovery by the protection path is determined to be impossible, the network setting information selected is notified to the communication device. The processing device of the network management device is:
When determining that a failure has occurred in the network group based on the information obtained from the input device, the communication device failure information obtained from the input device is accumulated and added for a certain period of time, and then the occurrence of the failure is determined. Determine the presence or absence,
The network system according to claim 1 or 2. A network management method for managing a network composed of a plurality of communication devices by a network management device,
A path setting step in which the network management device sets a plurality of second networks by using a part of the resources of the first network;
A grouping step of bundling and grouping a plurality of the second networks to form a plurality of network groups;
A recovery setting calculating step in which the network management device calculates a network setting for changing the resource of the first network corresponding to each combination of the network groups;
When the network management device determines that a failure has occurred in the network group, a selection step of selecting the calculated network setting corresponding to the combination of the network groups in which the failure has occurred;
A notification step in which the network management device notifies the communication device of the selected network setting;
The communication device comprises a recovery step of changing resources of the first network based on the notified network setting.
Network management method. After the restoration setting calculation step and before the selection step,
A distribution step in which the network management device assigns an identifier to the network settings corresponding to each of the combinations of the network groups, and distributes to each of the communication devices;
The communication device comprises a holding step of holding the distributed network setting and the set of identifiers in advance.
The network management method according to claim 10. The path setting step includes:
A protection path setting step for setting a protection path for the second network;
The selection step includes
When it is determined that recovery by the protection path is impossible, the network setting is selected.
The network management method according to claim 10 or 11. A network management device for managing a network, comprising a plurality of communication devices, wherein a plurality of second networks are configured on a first network,
Input device, output device, processing device, storage device,
The storage device
Holding a plurality of network groups obtained by grouping the second networks, and network setting information for changing the resources of the first network corresponding to each combination of the network groups;
The processor is
When it is determined that a failure has occurred in the network group based on information obtained from the input device, the network setting information is selected based on a combination of the network groups in which the failure has occurred, and the output device To notify the communication device of the selected network setting information,
Network management device. As the network setting information, having a recovery identifier that identifies a combination of the network groups,
The storage device
Holding a communication device identifier for identifying the communication device, the recovery identifier associated with the communication device identifier, and device setting information for changing the setting of the communication device associated with the recovery identifier;
The processor is
Distributing the set of the recovery identifier and the device setting information associated with the communication device identifier to the communication device specified by the communication device identifier,
The processor is
If it is determined that a failure has occurred in the network group based on the information obtained from the input device, the recovery identifier is selected based on the combination of the network group in which the failure has occurred, and the output device Notifying the selected recovery identifier to the communication device;
The network management device according to claim 13. The storage device
Communication failure determination information for maintaining a correspondence relationship of which of the network groups the failure of the communication device affects;
Protection failure determination information that retains a correspondence relationship of which of the protections that are alternative routes of the network group is affected by the failure of the communication device;
Store
When a failure of the communication device affects both the specific network group and the protection of the specific network group,
Notifying the selected network setting information to the communication device by the output device;
The network management device according to claim 13 or 14.

Images