JP2015133545A - Network management system, management device, control device, management method, control method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a network management system, a management device, a control device, a management method, a control method and a program, which can confirm availability of a change destination path when performing path control.SOLUTION: A network management system including a control device for controlling some of a plurality of packet transfer devices which transfer a packet in a network and a management device for managing the control device comprises: a specifying part for specifying the packet transfer device which requires a change in setting of the path for transferring the packet and specifying the control for controlling the specified packet transfer device; and a notification part for notifying the control device specified by the specification part of changed contents of the path.

Description

  The present invention relates to a network management system, a management device, a control device, a management method, a control method, and a program.

In a network composed of switches such as a layer 2 (L2) switch and a layer 3 (L3) switch, packets are transferred using a MAC (Media Access Control) address. Further, in a network constituted by routers, packets are transferred using an IP (Internet Protocol) address. Specifically, for example, in a network (IP network) composed of routers, packets are transferred according to route information stored in a routing table held by each router.
Usually, the route information is optimally held by the learning function of the routing protocol or network device.
In recent years, with the spread of communication networks, traffic flowing through the network has increased, and as a result, overload may occur in some sections of the network. For this reason, the traffic in the section that is overloaded is temporarily moved to another section, and route control that equalizes the load on the entire network and route control that gives priority to specific services are flexible and dynamic. The need for efficient routing is increasing.

  However, normally, in a network device such as a switch or a router, there is only one packet transfer path according to a specific transfer rule. Therefore, in order to change the packet transfer route, it is necessary to change the routing table of the network device. In addition, since the communication of the route change destination can be confirmed after changing the route information in the routing table, the communication of the route change destination route cannot be confirmed in advance. Here, the specific transfer rule is a condition indicated by network information such as an IP address or a MAC address.

  In a ring network to which MPLS (Multi-Protocol Label Switching) is applied, a failure avoidance technique similar to the standard UPSR system and BLSR system is proposed in the SDH / SONET technology. Among them, in the BLSR method in which a packet is routed to a backup path set in the reverse direction on the ring when a failure occurs in the working path, the validity of the backup path cannot be confirmed in advance. Has been proposed for a packet transfer device or the like that can be confirmed during network operation. For example, in the technique described in Patent Document 1, a test packet is identified by a packet transfer apparatus, and a backup path is used without affecting the working path by using a failure avoidance path and a backup path set in advance in the packet transfer apparatus. This is to confirm the communication.

JP 2012-129733 A

  However, the technique disclosed in Patent Document 1 is based on the premise that a preset working path and protection path, a protection path and a working path are switched, and a packet transfer apparatus in which the working path and the protection path merge. There is no consideration for switching routes. In recent years, attention has been focused on SDN (Software Defined Networking) for centrally controlling a network, and there is a movement to expand the application area from a narrow area network to a wide area network. For this reason, in a network where there are an infinite number of possible routes, the backup path is switched to another path that is not the working path, or the packet transfer device that joins the working path and the protection path again. There is a problem that the effectiveness of the change destination route cannot be confirmed when performing route control such as branching the route.

  Therefore, the present invention has been made in view of the above problems, and a network management system, management device, control device, management method, and control method capable of confirming the effectiveness of a change destination route when performing route control. It is an object to provide a program.

  (1) The present invention has been made to solve the above problems, and one aspect of the present invention is a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network; A network management system including a management device that manages the control device, wherein the packet transfer device that requires a change in setting of a route for transferring a packet is identified, and the control device that controls the identified packet transfer device is identified A network management system comprising: a specifying unit configured to perform notification; and a notification unit configured to notify the control device specified by the specifying unit of the change contents of the route.

  (2) One aspect of the present invention is the network management system described above, wherein the control device sets a route in the packet transfer device based on the received content of the route change. Network management system.

  (3) Moreover, one aspect of the present invention is any one of the network management systems described above, wherein the specifying unit classifies the packet transfer device from the current route and the destination route, and outputs the classification result. The network management system is characterized in that, based on the packet transfer device, the route setting needs to be changed.

  (4) Moreover, one aspect of the present invention is any one of the network management systems described above, wherein the specifying unit includes a connection relation between the control device and the packet transfer device, and the control device for the packet transfer device. The network management system is characterized in that the control device that controls the packet transfer device is specified based on the change authority.

  (5) Moreover, one aspect of the present invention is any one of the network management systems described above, wherein the acquisition unit acquires control information, and the service is used based on the control information acquired by the acquisition unit. Each of the packet transfer devices has a packet transfer rule of the same or the same type as the transfer rule used after changing the route without affecting the transfer of the service packet in the route used by the service packet. And a setting unit for setting to a network management system.

  (6) According to another aspect of the present invention, there is provided a management apparatus that manages a control apparatus that controls a part of a plurality of packet transfer apparatuses that transfer packets in a network. The packet transfer device that needs to be changed in the setting of the transfer route is specified, a specifying unit that specifies the control device that controls the specified packet transfer device, and the control device specified by the specifying unit And a notification unit that notifies the contents of change.

  (7) According to another aspect of the present invention, there is provided a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network, and obtains control information. And, based on the control information acquired by the acquisition unit, without affecting the transfer of the service packet in the route used by the service packet used in the service and after being changed And a setting unit configured to set a packet transfer rule of the same type or the same type as the transfer rule in each of the packet transfer devices.

  (8) According to another aspect of the present invention, there is provided a management method for managing a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network. Identifying the packet transfer device that needs to be changed in the setting of a route to be transferred, identifying a control device that controls the identified packet transfer device, and specifying the control device identified by the identifying step to the control device And a notification process for notifying the contents of change.

  (9) One embodiment of the present invention is a control method for controlling a part of a plurality of packet transfer apparatuses that transfer packets in a network, and obtains control information. And after changing the route without affecting the transfer of the service packet in the route used by the service packet used in the service, based on the control information obtained by the obtaining step And a setting process for setting a packet transfer rule of the same type or the same type as the transfer rule used in each of the packet transfer apparatuses.

  (10) One embodiment of the present invention is a program, a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network, a management device that manages the control device, Identifying the packet transfer device that needs to be changed in the setting of the route for transferring the packet to the management device or the computer of the control device of the network management system including the control device, and specifying the control device that controls the identified packet transfer device A program comprising: a specifying step; and a notifying step of notifying the control device specified in the specifying step of the change contents of the route.

  According to the network management system, management device, control device, management method, control method, and program of the present invention, it is possible to confirm the effectiveness of a change destination route when performing route control.

It is the schematic which shows an example of a structure of the network management system assumed in the 1st Embodiment of this invention. It is the schematic which shows an example of a structure of the network management system which concerns on the 1st Embodiment of this invention. It is a schematic block diagram which shows an example of a structure of the management apparatus which concerns on the 1st Embodiment of this invention. It is a schematic block diagram which shows an example of a structure of the control apparatus which concerns on the 1st Embodiment of this invention. It is the schematic which shows an example of the entry information for prior confirmation which concerns on the 1st Embodiment of this invention. It is a flowchart which shows an example of the network management process in the network management system which concerns on the 1st Embodiment of this invention. It is the schematic which shows an example of the correspondence information which the management apparatus which concerns on the 1st Embodiment of this invention hold | maintains. It is the schematic which shows an example of the classification information which the management apparatus which concerns on the 1st Embodiment of this invention produces | generates. It is the schematic which shows an example of the entry information for prior confirmation which concerns on the 1st Embodiment of this invention. It is the schematic which shows an example of the entry information for prior confirmation transmitted to each control apparatus which concerns on the 1st Embodiment of this invention. It is the schematic which shows an example of the entry for prior confirmation with respect to the isolated packet transfer apparatus which the entry generation part for prior confirmation based on the 1st Embodiment of this invention produces | generates. It is the schematic which shows an example of the entry for prior confirmation with respect to the different point packet transfer apparatus which the entry production | generation part for prior confirmation based on the 1st Embodiment of this invention produces | generates. It is the schematic which shows an example of a structure of the network management system which concerns on the 2nd Embodiment of this invention. It is explanatory drawing which shows an example of the information for branching to the separation point, another point, common, and confluence | merging with respect to the prior confirmation packet which concerns on the 2nd Embodiment of this invention. It is the schematic which shows an example of the correspondence information which the request generation part which concerns on the 2nd Embodiment of this invention acquires, and the classification information which a request generation part produces | generates. It is the schematic which shows an example of the entry information for prior confirmation which concerns on the 2nd Embodiment of this invention. It is the schematic which shows an example of the entry information for prior confirmation transmitted to each control apparatus which concerns on the 2nd Embodiment of this invention. It is the schematic which shows an example of the prior confirmation entry information for the confluence packet transfer apparatuses which the control apparatus which concerns on the 2nd Embodiment of this invention produces | generates. It is the schematic which shows an example of a structure of the network management system which concerns on the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention. It is the schematic which shows an example of the entry information for every packet transfer apparatus concerning the 3rd Embodiment of this invention.

(First embodiment)
Hereinafter, a first embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a schematic diagram showing an example of the configuration of the network management system S1 assumed in the first embodiment of the present invention.
The network management system S1 includes the host system Sys1, the management device 100, the communication path confirmation device 200, the control devices 300-1 and 300-2, and the packet transfer devices 401, 402, 403, 404, 405, 406, and 407. , 408, 409, 410, 411, 412.

  In the following description, the description of the control device 300 is a general term for the control devices 300-1 and 300-2. The description of the packet transfer device 400 is a generic name including the packet transfer devices 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412 and the like.

  Each packet transfer apparatus 400 is arranged in a confirmation target network NW1 that is a target network for performing prior confirmation, and is interconnected with at least one other packet transfer apparatus 400 among the packet transfer apparatuses 400. The packet transfer device 400 is, for example, an open flow switch. Each packet transfer device 400 is controlled by one of the control devices 300 and transfers a packet based on a request from the control device 300. For example, the packet transfer devices 401, 402, 403, 404, 405, and 406 are controlled by the control device 300-1, and the packet transfer devices 407, 408, 409, 410, 411, and 412 are controlled by the control device 300-2. Is done.

  Here, there are two types of packets transferred by the packet transfer apparatus 400: an in-service call and a prior confirmation call. An in-service call is a packet used in service. The prior confirmation call is a packet for confirming communication of the route after the change when the route of the in-service call is changed to another route.

  The control device 300 generates entry information for prior confirmation based on the prior confirmation request received from the management device 100 and transmits the prior confirmation request to the communication path confirmation device 200. Each control device 300 controls each subordinate packet transfer device 400 and transmits a request to each packet transfer device 400. The control device 300 is, for example, an open flow controller.

  The management device 100 manages each control device 300 that controls each packet transfer device 400. The management device 100 transmits a prior confirmation request to each control device 300 based on an instruction transmitted from the higher system Sys1.

  The communication path confirmation apparatus 200 confirms the normality of communication on the changed path according to the prior confirmation request received from the control apparatus 300. The prior confirmation call is generated as a packet that is transferred according to the transfer rule of the confirmation target network NW1 designated by the higher system Sys1, and includes information that is not used by the in-service call or a combination of tuples. The prior confirmation method may be any method for confirming the communication path using the prior confirmation call.

  The host system Sys1 manages the topology information of the confirmation target network NW1. The topology information is information related to the connection relationship between the packet transfer apparatuses 400. The host system Sys1 includes, for example, a display device, and can display the topology information of the confirmation target network NW1 on the display device or can specify advance confirmation of a route change by an operator. The host system Sys1 displays the result of the prior confirmation received from the management device 100 on the display device.

  In the present embodiment, the management device 100, the communication path confirmation device 200, the control device 300, and the packet transfer device 400 are described as separate devices, but two or more of these devices are mounted on the same device. May be.

FIG. 2 is a schematic diagram showing an example of the configuration of the network management system S2 according to the first embodiment of the present invention.
In the present embodiment, description will be made using a network management system S2 obtained by simplifying the network management system S1 shown in FIG.
In this embodiment, the transfer rule of the confirmation target network is the same in each packet transfer device 400 (one transfer rule of the confirmation target network included in the prior confirmation request), and there is no joining packet transfer device to be described later. An example of the case will be described.
A packet transfer device 400 is arranged in the confirmation target network NW2. For example, the packet transfer apparatus 400 includes packet transfer apparatuses 401, 402, 403, 404, 405, 406, 407, and 408. The identifiers (ID: Identifier) of each packet transfer apparatus 400 are A, B, C, D, E, F, X, and Y in order. The packet transfer device 401 is interconnected with the packet transfer devices 402 and 407, the packet transfer device 403 is interconnected with the packet transfer devices 402, 407, and 404, and the packet transfer device 405 is mutually connected with the packet transfer devices 404 and 406. Connected, the packet transfer device 408 is interconnected with the packet transfer devices 404 and 406.

In FIG. 2, each “#a, #b, #c, #d, #e, #f, #x, #y, #z” indicates output port information of each packet transfer device 400, for example, an output port number. Represent.
Further, for example, the packet transfer device 401 is connected to the network NW3 of “192.168.a.a / 16”, and the packet transfer device 406 is connected to the network NW4 of “192.168.b.b / 16”. ing. Here, it is assumed that a PC (Personal Computer) belonging to the network NW3 communicates with a PC belonging to the network NW4. In the following description, a PC belonging to the network NW3 that is a transmission source (Src: Source) is referred to as SrcPC. A PC belonging to the network NW4 that is a destination (Dst: Destination) is referred to as DstPC. For the communication from SrcPC to DstPC, the confirmation target network NW2 is used.

FIG. 3 is a schematic block diagram illustrating an example of the configuration of the management apparatus 100 according to the first embodiment of the present invention.
The management apparatus 100 includes a system cooperation unit 101, a classification unit 102, a request generation unit 103, a transmission unit 104, and a management unit 105.
The system cooperation unit 101 communicates with the higher system Sys1. The system cooperation unit 101 receives a prior confirmation request from the higher system Sys1. The system cooperation unit 101 outputs a prior confirmation request to the classification unit 102. Further, when receiving the confirmation information from the control device 300, the system cooperation unit 101 transmits the received confirmation information to the upper system Sys1.

The prior confirmation request includes a transfer rule of the confirmation target network, route information before change that is route information before the route is changed, and route information after change that is route information after the route is changed.
Here, the transfer rule of the confirmation target network is packet identification information when a packet is transferred from one packet transfer apparatus to the next packet transfer apparatus in the confirmation target network. Specifically, it is tuple combination information that can be set for each packet transfer apparatus 400. For example, DstIP = 192.168..DstIP that is a destination IP (Internet Protocol). b. b / 16, information such as protocol = udp as a protocol. Here, udp stands for User Datagram Protocol. In other words, different (exclusive) confirmation target network transfer rules are set in the packet transfer device, and the packet transfer device that is the transfer destination is changed for each packet that matches the transfer rule of each confirmation target network. The route can be changed.

  The pre-change route information includes information that uniquely defines each packet transfer device 400 before the route change, input port information and output port information of each packet transfer device 400, or port information such as input port information or output port information. That is. For example, information used by each control device 300 to uniquely identify each packet transfer device 400 includes information on a data path ID (Datapath ID).

  The post-change route information includes information that uniquely defines each packet transfer device 400 after the route change, input port information and output port information of each packet transfer device 400, or port information such as input port information or output port information. That is. For example, information used by each control device 300 to uniquely identify each packet transfer device 400 includes information on a data path ID (Datapath ID).

  When the prior confirmation request is input from the system cooperation unit 101, the classification unit 102 sets each packet transfer device 400 as a point packet transfer device (point-off OFS), a point packet transfer device (point OFS), or a common packet. It is classified into either a transfer device (common OFS) or a join packet transfer device (joint OFS). The classification unit 102 outputs the classified result, the transfer rule of the confirmation target network included in the prior confirmation request, and the changed route information to the request generation unit 103.

The off-point OFS is each packet transfer device 400 that exists in common between the pre-change route information and the post-change route information, and each packet transfer device 400 having different output port information between the pre-change route information and the pre-change route information. That is.
Another point OFS is each packet transfer apparatus 400 that exists in the post-change path information and that does not exist in the pre-change path information.
The common OFS is a packet transfer device 400 that exists in common between the pre-change route information and the post-change route information, and each of the packet transfer devices 400 having the same transfer rule and output port information of the confirmation target network. is there.
The merged OFS is each packet transfer device 400 that exists in common between the pre-change route information and the post-change route information, and the transfer port information of the packet transfer devices 400 that have the same transfer port information but the same transfer port information. That is.

  When the classification result, the transfer rule of the confirmation target network, and the changed route information are input from the classification unit 102, the request generation unit 103 acquires the correspondence information held by the management unit 105 from the management unit 105, and sets the classification result as the classification result. Based on this, each control device 300 that controls the separation point OFS, the separate point OFS, the common OFS, and the merged OFS is specified. In the correspondence information, the identification information of each control device 300 that controls each packet transfer device 400 is associated with the identification information of each packet transfer device 400. The request generation unit 103 generates entry information for prior confirmation for each identified control device 300. Specifically, the request generation unit 103 generates classification information by adding the classification result classified by the classification unit 102 to the correspondence information. The classification information generated by the request generation unit 103 is obtained by associating, for example, the classification result of each packet transfer device 400, the identification information of each packet transfer device 400, and the identification information of each control device 300.

  Then, the request generation unit 103 generates prior confirmation entry information to be transmitted to each packet transfer device 400 controlled by each control device 300. Specifically, the request generation unit 103 generates matching information and Instructions for the classification information and generates pre-confirmation entry information. The Matching Field is an area in which information for determining a packet to be executed for Instructions is stored. In the following description, the stored information is also referred to as matching information. That is, the transfer rule of the confirmation target network is one piece of matching information. Instructions are instruction contents corresponding to each matching information. The request generation unit 103 outputs the generated prior confirmation entry information, the transfer rule of the confirmation target network, and the changed route information to the transmission unit 104.

The transmission unit 104 sends the packet transfer device 400 that requires entry information to be changed to the entry information for prior confirmation, the transfer rule of the confirmation target network, and the changed route information for all the control devices 300 input from the request generation unit 103. It transmits to one of the control apparatuses 300 to control. Here, it is assumed that the transmitting control device 300 is the control device 300 on the Src side.
The management unit 105 holds correspondence information. The correspondence information is information representing the correspondence relationship between each packet transfer device 400 and each control device 300 that controls each packet transfer device 400. The correspondence information may be set manually, or information on the connection relationship between each packet transfer apparatus 400 and each control apparatus 300, and information on the setting change authority of each control apparatus 300 for each packet transfer apparatus 400. It may be automatically set based on the collected information.

FIG. 4 is a schematic block diagram showing an example of the configuration of the control device according to the first embodiment of the present invention.
The control device 300 includes a cooperation unit 301, a confirmation unit 302, a prior confirmation entry generation unit 303, and a transmission unit 304.

When the cooperation unit 301 receives the prior confirmation entry information, the transfer rule for the confirmation target network, and the changed route information from the management device 100, the cooperation unit 301 manages the packet transfer device 400 on the Src side in the changed route information. The prior confirmation entry information is output to the prior confirmation entry generation unit 303. Further, the cooperation unit 301 transmits the prior confirmation entry information to each of the other control devices 300. When the cooperation unit 301 receives completion notifications from all the other control devices 300, the cooperation unit 301 outputs the transfer rule of the confirmation target network and the changed route information to the confirmation unit 302 as a communication route confirmation request.
On the other hand, when the prior confirmation entry information is received from another control apparatus 300 (Src-side control apparatus 300), a response indicating that the prior confirmation entry information has been received is sent to the transmission source control apparatus 300. Send. Then, the linkage unit 301 outputs the received prior confirmation entry information to the prior confirmation entry generation unit 303.

  Note that the cooperation unit 301 of the control device 300 that manages the packet transfer device 400 on the Src side may transmit the prior confirmation entry information to each of the other control devices 300, and among the plurality of control devices 300, for example, The prior confirmation entry information may be transmitted to only one control apparatus 300 and transmitted so that the control apparatus 300 that has received the prior confirmation entry information propagates to the other control apparatuses 300.

  The confirmation unit 302 transmits the transfer rule and the changed route information of the confirmation target network input from the cooperation unit 301 to the communication route confirmation device 200, and receives the confirmation result confirming the normality of communication from the communication route confirmation device 200. To do. The confirmation unit 302 transmits the received confirmation result to the management apparatus 100.

  When the prior confirmation entry information is input from the cooperation unit 301, the prior confirmation entry generation unit 303 generates a prior confirmation entry to be set in the packet transfer apparatus 400 based on the prior confirmation entry information. The prior confirmation entry generation unit 303 outputs the generated prior confirmation entry to the transmission unit 304. Details will be described later.

  The transmission unit 304 is, for example, an OpenFlow protocol stack. When the advance confirmation entry is input from the advance confirmation entry generation unit 303, the transmission unit 304 transmits the advance confirmation entry to each packet transfer device 400. In addition, when the transmission unit 304 of each control device 300 that has received the advance confirmation entry information from the control device 300 on the Src side transmits the advance confirmation entry to each packet transfer device 400, the transmission unit 304 transmits the advance confirmation entry to each packet transfer device 400. A completion notification indicating completion of entry setting is transmitted to the control device 300 on the Src side.

Before describing the advance confirmation of the route in more detail, a configuration example of the advance confirmation entry information table will be described with reference to FIG.
FIG. 5 is a schematic diagram illustrating an example of entry information for prior confirmation according to the first embodiment of the present invention.
The prior confirmation entry information is set in the packet transfer apparatus 401 in FIG. Similar entry information for prior confirmation is also set in each packet transfer apparatus 400, but illustration and description thereof are omitted.

Tables T5, T6, T7, and T8 are two-dimensional tabular tables having item columns of Matching Field and Instructions.
The table T5 is a table for branching the in-service call and the prior confirmation call. In the Matching Field, matching information for identifying a prior confirmation call or a packet other than the prior confirmation call is stored. The identification information of the prior confirmation call may be information that is not used by the in-service call and can be used as a tuple or a combination of tuples. For example, ECN = 2 is used as matching information for identifying the prior confirmation call. . In Instructions, instruction contents corresponding to each matching information are stored. For example, in the first line, Matching Field is ECN = 2, Instructions is GotoTable: T6, and in the second line, Matching Field is Any, and Instructions is GotoTable: T7.

  Here, in the Matching Field, ECN = 2 in the first line represents identification information of a prior confirmation call, and Any in the second line represents identification information of a packet other than the identification information of the prior confirmation call. In Instructions, GotoTable: T6 on the first line indicates an instruction to refer to the table T6 when the call is a prior confirmation call, and GotoTable: T7 on the second line indicates a table T7 when the call is not a prior confirmation call. Indicates an instruction to refer to.

  The table T6 is a transfer table for branching the prior confirmation call into transfer tables according to the classification of the off-point OFS, the different-point OFS, and the merged OFS. In the Matching Field, matching information of the prior confirmation call for the off-point OFS or matching information of the prior confirmation call for each of the other packet transfer apparatuses 400 is stored. Instructions corresponding to the matching information are stored in Instructions. For example, in the first line, Matching Field is Any and Instructions is GotoTable: T7. That is, in the case of matching information for a prior confirmation call in each packet transfer apparatus 400 other than the off-point OFS, it indicates an instruction for referring to the table T7.

  Table T7 is a transfer table for in-service calls. In the Matching Field, in-service call matching information (transfer rule) is stored. In Instructions, an instruction such as an output port number is stored. For example, in the first line, the Matching Field is Dst = 192.168. b. b / 16, and Instructions is Action = output: #b. That is, DstIP is 192.168 .. b. For an in-service call of b / 16, an instruction to output from port number #b is shown.

  Table T8 is a transfer table for a prior confirmation call in the off-point OFS. In the Matching Field, matching information (transfer rule) of the prior confirmation call is stored. Instructions stores instruction contents corresponding to matching information. Details will be described later.

Next, the generation process of the prior confirmation entry by the prior confirmation entry generation unit 303 will be described.
The prior confirmation entry generation unit 303 generates a prior confirmation entry based on the prior confirmation entry information.

<In case of off-point OFS>
The prior confirmation entry generation unit 303 generates a prior confirmation entry for branching to the table T8 in FIG. 5 for the table T6 in FIG. Further, the prior confirmation entry generation unit 303 uses the same information as the entry applied to the in-service call in the table T7 in FIG. 5 after changing the route for the prior confirmation entry generated in the table T8 in FIG. Generate.
Thereby, before changing the route, it is possible to make a prior confirmation using the same entry as the entry used after changing the route.
The prior confirmation entry generation unit 303 may write the prior confirmation entry to be written in the table T8 in FIG. 5 which is the forwarding table for the prior confirmation call into the table T6 in FIG. 5 which is the branching table for the prior confirmation call. Good.

<If it is another point OFS>
The prior confirmation entry generation unit 303 generates a prior confirmation entry for the table T7 in FIG. 5 in a state applicable to the in-service call after the route is changed.
Thereby, when changing a route, the entry used for the prior confirmation can be applied as it is without performing any control on each packet transfer apparatus 400.
In the common OFS, the prior confirmation entry generation unit 303 does not generate the prior confirmation entry because the prior confirmation is performed using the in-service call entry existing in the table T7 of FIG.

FIG. 6 is a flowchart showing an example of network management processing in the network management system S2 according to the first embodiment of the present invention.
In step ST101, the system cooperation unit 101 of the management apparatus 100 receives a prior confirmation request from the higher system Sys1. For example, among the routes from the network NW3 in the network management system S2 shown in FIG. 2 to the network NW4 via the confirmation target network NW2, the identifiers of the packet transfer apparatuses 400 are A, B, C, D, E, The packet transfer apparatuses 401, 402, 403, 404, 405, and 406 that are F are routed through the packet transfer apparatuses 401, 407 that have identifiers A, X, C, D, Y, and F, respectively. , 403, 404, 408, and 406, the transfer rule of the confirmation target network included in the prior confirmation request received from the higher system Sys1 is DstIP = 192.168 .. b. b / 16. The pre-change path information included in the prior confirmation request received from the host system Sys1 includes A (output = # b), B (output = # c), C (output = # d), and D (output = # e). ), E (output = # f), and F (output = # z). Further, the post-change route information included in the prior confirmation request received from the host system Sys1 includes A (output = # x), X (output = # c), C (output = # d), and D (output = # y). ), Y (output = # f), and F (output = # z).

  In step ST102, the classification unit 102 of the management apparatus 100 classifies each packet transfer apparatus 400 based on the prior confirmation request. Specifically, the classification unit 102 calculates a difference between the pre-change route information and the post-change route information, and classifies each packet transfer apparatus 400 based on the difference. For example, the classification unit 102 uses a packet transfer device having different output port information for the pre-change route information and the post-change route information as an off-point OFS, and among the packet transfer devices existing in the post-change route information, A packet transfer apparatus that does not exist is another point OFS, a packet transfer apparatus in which the input port information and the output port information are the same in both the pre-change path information and the post-change path information, and the common OFS, the pre-change path information and the post-change path The packet transfer apparatuses having different input port information and the same output port information are classified as merged OFS.

For example, in the example illustrated in FIG. 2, the packet transfer apparatus 401 with the identifier A and the packet transfer apparatus 404 with the identifier D are classified as the off-point OFS, and the identifier is the packet transfer apparatus 407 with the identifier X. The packet transfer device 408 that is Y is classified as a different point OFS, and the packet transfer device 403 that has an identifier C and the packet transfer device 406 that has an identifier F are classified as a common OFS.
In this embodiment, since the transfer rules of the confirmation target network are the same, there is no packet transfer apparatus 400 classified as a merged OFS.

In step ST103, the request generation unit 103 of the management apparatus 100 specifies each control apparatus 300 that controls each classified packet transfer apparatus 400. This will be described in more detail with reference to FIGS.
FIG. 7 is a schematic diagram illustrating an example of correspondence information of each control device 300 held by the management device 100 according to the first embodiment of the present invention.
The table T9 shown is held as correspondence information by the management unit 105 of the management apparatus 100.
The table T9 is a two-dimensional table format table having item strings of OFS identification information and OFC identification information. The OFS identification information is identification information of each packet transfer apparatus 400. The OFC identification information is identification information of each control device 300.
For example, in the first line, OFS identification information is A, OFC identification information is OFC-1, and in the second line, OFS identification information is B, OFC identification information is OFC-1, and the last line The OFS identification information is Y and the OFC identification information is OFC-2.
OFC-1 is the control device 300-1, and OFC-2 is the control device 300-2.
In the illustrated example, there is one control device 300 that controls each packet transfer device 400, but when each packet transfer device 400 is controlled by a plurality of control devices 300, OFC identification information And a control device that can be set for the corresponding packet transfer device among the plurality of control devices 300 may be selected.

FIG. 8 is a schematic diagram illustrating an example of classification information generated by the management apparatus 100 according to the first embodiment of the present invention.
The request generation unit 103 generates classification information based on the classification result classified by the classification unit 102 and the correspondence information as shown in FIG. Then, the request generation unit 103 generates prior confirmation entry information based on the generated classification information.
First, the classification information will be described.

  As illustrated in FIG. 8, the table T <b> 10 is a two-dimensional tabular table having item columns of OFS classification information, OFS identification information, and OFC identification information. The table T10 is an example of classification information. The OFS classification information is a classification result of each packet transfer apparatus 400 classified by the classification unit 102. The OFS identification information is identification information of each packet transfer apparatus 400 and output port information of the packet transfer apparatus 400. The OFC identification information is identification information of each control device 300.

For example, in the first line, the OFS classification information is the departure point, the OFS identification information is A (output = # x), and the OFC identification information is OFC-1. In the second line, the OFS classification information is a departure point, the OFS identification information is D (output = # y), and the OFC identification information is OFC-2. In the third line, OFS classification information is another point, OFS identification information is X (output = # c), and OFC identification information is OFC-1. In the fourth line, OFS classification information is another point, OFS identification information is Y (output = # f), and OFC identification information is OFC-2.
In this way, the request generation unit 103 generates the classification information by adding the correspondence information to the classification result based on the classification result classified by the classification unit 102 and the correspondence information held by the management unit 105.

Returning to FIG. 6, in step ST <b> 104, the request generation unit 103 of the management apparatus 100 generates prior confirmation entry information for all the control apparatuses 300 that control the identified packet transfer apparatus 400.
For example, the request generation unit 103 generates prior confirmation entry information based on the generated classification information. This will be described in detail with reference to FIG.
FIG. 9 is a schematic diagram illustrating an example of entry information for prior confirmation according to the first embodiment of the present invention.
The table T11 is a two-dimensional table format table having item columns of OFC identification information, OFS classification information, OFS identification information, Matching Field, and Instructions. Since the OFC identification information, OFS classification information, and OFS identification information are the same as those in the table T10 of FIG. Also, Matching Field and Instructions are the same as the table T7 in FIG.

For example, in the first line, the OFC identification information is OFC-1, the OFS classification information is a departure point, the OFS identification information is A, and the Matching Field is DstIP = 192.168.168. b. b / 16, and Instructions is Action = output: #x. In the second line, the OFC identification information is OFC-1, the OFS classification information is another point, the OFS identification information is X, and the Matching Field is DstIP = 192.168.168. b. b / 16, and Instructions is Action = output: #c. In the third line, the OFC identification information is OFC-2, the OFS classification information is a departure point, the OFS identification information is D, and the Matching Field is DstIP = 192.168. b. b / 16, and Instructions is Action = output: #y. In the fourth line, the OFC identification information is OFC-2, the OFS classification information is different, the OFS identification information is Y, and the Matching Field is DstIP = 192.168.168. b. b / 16, and Instructions is Action = output: #f.
In this way, the request generation unit 103 adds the DstIP representing the destination and the output port information of the corresponding packet transfer apparatus to the classification information, and generates the prior confirmation entry information.

Returning to FIG. 6, in step ST <b> 105, the transmission unit 104 of the management device 100 transmits all of the advance confirmation entry information generated to any one of the control devices 300.
For example, the transmission unit 104 transmits all the prior confirmation requests to the respective control devices 300 to the control device 300-1 that controls the packet transfer device 401 on the Src side in the changed route information.

In step ST <b> 106, upon receiving advance confirmation entry information from the management apparatus 100, the cooperation unit 301 of the Src-side control apparatus 300 transmits advance confirmation entry information to each control apparatus 300.
For example, the control device 300-1 that controls the packet transfer device 401 on the Src side is the control device on the Src side, and the control device 300-1 transmits entry information for prior confirmation to the control device 300-2. The prior confirmation entry information transmitted to each control device 300 will be described with reference to FIG.

FIG. 10 is a schematic diagram illustrating an example of entry information for prior confirmation transmitted to each control device 300 according to the first embodiment of the present invention.
The table T12 is entry information for prior confirmation of the control device 300-1 that is a control device on the Src side, and the table T13 is entry information for advance confirmation transmitted from the control device 300-1 to the control device 300-2. It is an example.
Tables T12 and T13 are two-dimensional tabular tables having respective item columns of OFC identification information, OFS classification information, OFS identification information, Matching Field, and Instructions. Each item is the same as the table T11 in FIG.
In the tables T12 and T13, the prior confirmation entry information for all the control devices shown in the table T11 of FIG. 9 is arranged for each control device. When receiving the prior confirmation entry information for all the control apparatuses 300 from the management apparatus 100, the control apparatus 300-1 generates the prior confirmation entry information for each control apparatus 300, and for the prior confirmation of each of the generated control apparatuses 300. The entry information is transmitted to another control device 300, for example, the control device 300-2.

  Returning to FIG. 6, in step ST107, the prior confirmation entry generation unit 303 of each control device 300 performs the prior confirmation entry based on the prior confirmation entry information received from the management device 100 or the control device 300 on the Src side. Is generated. The prior confirmation entry generated by the prior confirmation entry generation unit 303 will be described with reference to FIGS.

FIG. 11 is a schematic diagram illustrating an example of a pre-confirmation entry for the packet transfer device 401 that is a point-separated packet transfer device generated by the pre-confirmation entry generation unit 303 of the control device 300 according to the first embodiment of the present invention. It is. FIG. 12 shows an example of a prior confirmation entry for the packet transfer apparatus 407, which is another point packet transfer apparatus generated by the prior confirmation entry generation unit 303 of the control apparatus 300 according to the first embodiment of the present invention. FIG.
For example, the prior confirmation entry generation unit 303 generates a prior confirmation entry as shown in the first row and T17 of the table T15 shown in FIG. 11 for the packet transfer apparatus 401 that is the off-point OFS. At this time, it is assumed that the second row and T16 of the tables T14 and T15 shown in FIG. 11 are set in the packet transfer apparatus 401 before the prior confirmation. Tables T14, T15, T16, and T17 are two-dimensional tabular tables having item columns of Matching Field and Instructions. The item sequence is the same as the tables T5, T6, T7, and T8 shown in FIG.

In the first row of the table T14, Matching Field is ECN = 2, Instructions is GotoTable: T15, and in the second row, Matching Field is Any, and Instructions is GotoTable: T16.
In the first row of the table T15, Matching Field has DstIP = 192.168.168. b. b / 16, Instructions is GotoTable: T17, and in the second line, Matching Field is Any, and Instructions is GotoTable: T16.
The first line of the table T16 has a Matching Field of Dst = 192.168.2. b. b / 16, and Instructions is Action = output: #b.
In the first row of the table T17, Matching Field has DstIP = 192.168.168. b. b / 16, and Instructions is Action = output: #x.

As described above, the prior confirmation entry generation unit 303 generates the same prior confirmation entry as the entry to be applied to the in-service call after changing the route in the table T17. Further, the prior confirmation entry generation unit 303 generates a prior confirmation entry for branching to the table T17 for the table T15.
The prior confirmation entry generation unit 303 does not generate the prior confirmation entry for branching to the table T17 in the table T15, and stores the prior confirmation entry to be applied to the in-service call in the table T15 after changing the route. It may be generated.

Further, for example, the prior confirmation entry generation unit 303 generates prior confirmation entries such as a table T20 illustrated in FIG. 12 for the packet transfer apparatus 407 that is another point OFS. At this time, it is assumed that the tables T18 and T19 shown in FIG. 12 are set in the packet transfer apparatus 407 before the prior confirmation is performed.
In the first row of the table T18, Matching Field is ECN = 2, Instructions is GotoTable: T19, and in the second row, Matching Field is Any, and Instructions is GotoTable: T20.
In the first row of the table T19, Matching Field is Any, and Instructions is GotoTable: T20.
The first line of the table T20 has a Matching Field of Dst = 192.168.168. b. b / 16, and Instructions is Action = output: #c.
In the table T21, “Matching Field” and “Instructions” are blank.
In this way, the prior confirmation entry generation unit 303 generates a prior confirmation entry that is in a state that can be directly applied to the in-service call with respect to the table T20.

  That is, the prior confirmation entry generation unit 303 generates prior confirmation entries as shown in FIGS. 11 and 12 for each packet transfer apparatus 400, and the generated prior confirmation entries are stored in each table of prior confirmation entry information. Store.

Returning to FIG. 6, in step ST108, the cooperation unit 301 of the control device 300 on the Src side receives the prior confirmation entries from all of the control devices 300 that have received the prior confirmation entry information including its own device. When a completion notification indicating that the data has been transmitted to 400 is received, a communication path confirmation request is output to the confirmation unit 302.
For example, when the cooperation unit 301 of the control device 300-1 that is the control device on the Src side receives completion notifications from all of the control devices 300 that have received the pre-confirmation entry information including its own device, the cooperation unit 301 checks the confirmation target from the confirmation unit 302. The network transfer rule and the changed route information passing through the packet transfer devices 401, 407, 403, 404, 408, and 406 in this order are transmitted to the communication route confirmation device 200 as a communication route confirmation request.

In step ST109, when the communication path confirmation device 200 receives the communication path confirmation request, the communication path confirmation device 200 confirms the normality of communication in the communication path confirmation request, and sends the confirmation result to the control device 300 (Src side) that has transmitted the communication path confirmation request. Control device 300). Then, the confirmation unit 302 of the control device 300 on the Src side transmits confirmation information indicating the received confirmation result to the management device 100. The system cooperation unit 101 of the management apparatus 100 transmits the received confirmation information to the higher system Sys1.
Then, the network management process according to FIG. 6 ends.

  Thus, according to the present embodiment, a network including the control device 300 that controls a part of the plurality of packet transfer devices 400 that transfer packets in the network, and the management device 100 that manages the control device 300. The network management system is a management system that identifies a packet transfer device 400 that needs to be changed in setting a route for transferring a packet, and identifies a control unit 300 that controls the identified packet transfer device 400 (request generation) Unit 103) and a notification unit (transmission unit 104) that notifies the control device 300 identified by the identification unit (request generation unit 103) of the change contents of the route.

  As a result, in a network where there are an infinite number of routes that can be taken, not only the backup path and the working path, but also the path control for switching the route to an arbitrary path, or the packet transfer device that joins the working path and the protection path Even when the path control such as branching the path again is performed, the effectiveness of the change destination path can be confirmed. In addition, when changing the communication route, it is not necessary to manually check the communication of the route after the change, it can be automatically confirmed, and even when performing automatic route change control, due to a setting error, etc. Control can be reliably performed without causing communication interruption. In addition, since the network transfer rule set when the communication path is checked in advance and the network transfer rule set when actually used in the service are the same or the same type, Minimal changes in settings when changing routes

(Second Embodiment)
Hereinafter, a second embodiment of the present invention will be described in detail with reference to the drawings.
In the present embodiment, an example will be described in which the transfer rule of the confirmation target network differs depending on each packet transfer apparatus 400 and there is a junction.
FIG. 13 is a schematic diagram showing an example of the configuration of the network management system S3 according to the second embodiment of the present invention.
The network management system S3 includes a host system Sys1, a management apparatus 100, a communication path confirmation apparatus 200, control apparatuses 300-1 and 300-2, and packet transfer apparatuses 401, 402, 403, 404, and 405. Consists of.
In the present embodiment, the description of the control device 300 includes both of the control devices 300-1 and 300-2, and the description of each control device 300 is either one of the control device 300-1 or the control device 300-2. Represents something. The description of the packet transfer device 400 is a generic name including the packet transfer devices 401, 402, 403, 404, 405 and the like, and the description of each packet transfer device 400 is one of these packet transfer devices. Represents that.
The operations of the host system Sys1, the management apparatus 100, the communication path confirmation apparatus 200, the control apparatus 300, and the packet transfer apparatus 400 are the same as those of the network management system S1 in the first embodiment, and thus the description thereof is omitted. The description will focus on the different parts.

A packet transfer device 400 is arranged in the confirmation target network NW5. For example, the packet transfer device 400 includes packet transfer devices 401, 402, 403, 404, and 405. The identifiers (ID: Identifier) of each packet transfer device 400 are A, B, C, D, and X in order. The packet transfer apparatus 401 is interconnected with the packet transfer apparatuses 402 and 405, the packet transfer apparatus 403 is interconnected with the packet transfer apparatuses 402, 405, and 404, and the packet transfer apparatus 404 is interconnected with the packet transfer apparatus 403. The
The control device 300-1 controls each of the packet transfer devices 401, 402, and 405. The control device 300-2 controls each of the packet transfer devices 403 and 404.

Further, for example, the packet transfer device 401 is connected to the network NW6 of “192.168.a.a / 16”, and the packet transfer device 404 is connected to the network NW7 of “192.168.b.b / 16”. ing. Here, it is assumed that communication is performed from a PC belonging to the network NW6 to a PC belonging to the network NW7. In the following description, a PC belonging to the network NW6 that is a transmission source (Src: Source) is referred to as SrcPC. A PC belonging to the network NW7 that is a destination (Dst: Destination) is referred to as DstPC. For the communication from SrcPC to DstPC, the confirmation target network NW5 is used, and the packet transfer device identifiers “A, B, C, D” are passed through the packet transfer devices 401, 402, 403, 404. Assume that an entry is set in the packet transfer apparatus 400.
In the illustrated example, #z is designated as input port information and #b and #x are designated as output port information in the packet transfer device 401, and #a is designated as input port information and #a is designated as output port information in the packet transfer device 402. c is specified, and #a is specified as input port information and #c is specified as output port information in the packet transfer apparatus 405. Similarly, the input port information and the output port information are specified for each of the other packet transfer apparatuses 400, but the description thereof is omitted.

For example, when input port information is specified as a transfer rule in each packet transfer apparatus 400, the packet is set in a table for use in in-service call transfer in each packet transfer apparatus 400 even in the same network. Different Matching Field information.
Specifically, referring to FIG. 14 for a table used for in-service call transfer in the packet transfer apparatuses 401, 402, 403, and 404 whose packet transfer apparatus identifiers are “A, B, C, and D”. I will explain.

FIG. 14 is an explanatory diagram showing an example of information used for transferring an in-service call according to the second embodiment of the present invention.
The table corresponds to the Matching Field such as the table T7 in FIG. 5, the table T16 in FIG. 11, and the table T20 in FIG. 12, and is a collection of information on the Matching Field for each packet transfer apparatus 400.

The table example T22 is a table example in a two-dimensional tabular format having each item column of OFS and Matching Field. OFS represents the identification information of each packet transfer apparatus 400. For example, OFS-A represents the packet transfer apparatus 401 whose identifier is A. The Matching Field is the same as that shown in FIGS. 5, 11, and 12, and the description thereof is omitted.
In the first line, OFS is OFS-A, and Matching Field is DstIP = 192.168.168. b. b / 16, input = # z. In the second line, OFS is OFS-B and Matching Field is DstIP = 192.168.16. b. b / 16, input = # a. In the third line, OFS is OFS-C, and Matching Field is DstIP = 192.168.168. b. b / 16, input = # b. In the fourth line, OFS is OFS-D and Matching Field is DstIP = 192.168.16. b. b / 16, input = # a.

  In the example of the first line, the Matching Field in the table for transferring the in-service call to the packet transfer apparatus 401 is DstIP = 192.168.168. b. b / 16, input = # z. That is, in the packet transfer apparatus 401, the packet is input from the input port number #z, and the DstIP of the packet is 192.168 .. b. b / 16. In the example of the second line, the Matching Field in the table for transferring the in-service call to the packet transfer apparatus 401 is DstIP = 192.168.168. b. b / 16, input = # a. The same applies to the other rows. The table example T22 is a summary of information used to transfer the in-service call of each packet transfer apparatus 400. Since the table other than the table for transferring the in-service call to each packet transfer apparatus 400 is the same as the entry information for prior confirmation in the first embodiment, the description thereof is omitted.

Next, the management apparatus 100 according to the present embodiment will be described.
Since the configuration of the management device 100 according to the second embodiment is the same as the configuration of the management device 100 according to the first embodiment, the description thereof will be omitted, and description will be made focusing on different portions in this embodiment.
The system cooperation unit 101 communicates with the higher system Sys1. The system cooperation unit 101 receives a prior confirmation request from the higher system Sys1. The system cooperation unit 101 outputs a prior confirmation request to the classification unit 102. In addition, when receiving the confirmation information from the control device 300, the management device 100 transmits the received confirmation information to the higher system Sys1.
The prior confirmation request includes the transfer rule of the confirmation target network, pre-change route information, and post-change route information. The transfer rule for the confirmation target network includes a transfer rule for the network before change before changing the route and a transfer rule for the network after change after changing the route.

  Here, from the route of the pre-change route information passing through the packet transfer devices 401, 402, 403, 404 whose identifiers are “A, B, C, D” in the network management system S3 shown in FIG. Consider a case where the packet transfer device is changed to the route of the changed route information via the packet transfer devices 401, 405, 403, and 404 whose identifiers are “A, X, C, and D”.

  For example, the transfer rule of the pre-change network of the packet transfer apparatus 401 whose identifier is A is DstIP = 192.168 .. b. b / 16, input = # z. Further, the transfer rule of the pre-change network of the packet transfer apparatus 402 whose identifier is B is DstIP = 192.168 .. b. b / 16, input = # a. Further, the transfer rule of the pre-change network of the packet transfer apparatus 403 whose identifier is C is DstIP = 192.168 .. b. b / 16, input = # b. Further, the transfer rule of the pre-change network of the packet transfer apparatus 404 with the identifier D is DstIP = 192.168 .. b. b / 16, input = # a.

  For example, the post-change network transfer rule of the packet transfer apparatus 401 whose identifier is A is DstIP = 192.168 .. b. b / 16, input = # z. Further, the transfer rule of the changed network of the packet transfer device 405 whose identifier is X is DstIP = 192.168 .. b. b / 16, input = # a. Further, the transfer rule of the changed network of the packet transfer apparatus 403 whose identifier is C is DstIP = 192.168 .. b. b / 16, input = # x. Further, the transfer rule of the changed network of the packet transfer apparatus 404 whose identifier is D is DstIP = 192.168 .. b. b / 16, input = # a.

  The pre-change route information is information that uniquely defines each packet transfer device 400 before the route change, port information such as input port information and / or output port information of each packet transfer device 400, and the like. For example, the pre-change route information is A (output = # b), B (output = # c), C (output = # d), and D (output = # x). Here, each of A, B, C, and D represents an identifier of the packet transfer apparatus. For example, it indicates that the output port information of the packet transfer apparatus 401 whose identifier is A is #b.

  The post-change route information is information that uniquely defines each packet transfer device 400 after the route change, port information such as input port information and / or output port information of each packet transfer device 400, and the like. For example, post-change route information is A (output = # x), X (output = # c), C (output = # d), and D (output = # x). Here, each of A, X, C, and D represents an identifier of the packet transfer apparatus. For example, this indicates that the output port information of the packet transfer device 405 whose identifier is X is #c.

  When the prior confirmation request is input from the system cooperation unit 101, the classification unit 102 classifies each packet transfer apparatus 400 as one of the separated point OFS, the different point OFS, the common OFS, and the merged OFS. For example, the classification unit 102 classifies each packet transfer apparatus 400 after changing the route based on the transfer rule of the confirmation target network, the pre-change route information, and the post-change route information. Specifically, in the example illustrated in FIG. 13, the classifying unit 102 classifies the packet transfer device 401 whose packet transfer device identifier is A into the off-point OFS, and the packet transfer device whose packet transfer device identifier is X. 405 is classified as another point OFS, the packet transfer apparatus 404 whose packet transfer apparatus identifier is D is classified as a common OFS, and the packet transfer apparatus 403 whose packet transfer apparatus identifier is C is classified as a merged OFS. The classification unit 102 outputs the classified result, the transfer rule of the confirmation target network included in the prior confirmation request, and the changed route information to the request generation unit 103.

When the classification result, the transfer rule of the confirmation target network, and the changed route information are input from the classification unit 102, the request generation unit 103 acquires the correspondence information held by the management unit 105 from the management unit 105, and sets the classification result as the classification result. Based on this, each control device 300 that controls the separation point OFS, the separate point OFS, and the merged OFS is specified. In the correspondence information, the identification information of each control device 300 that controls each packet transfer device 400 is associated with the identification information of each packet transfer device 400.
The correspondence information acquired by the request generation unit 103 will be described with reference to FIG.

FIG. 15 is a schematic diagram illustrating an example of correspondence information acquired by the management apparatus 100 request generation unit 103 and classification information generated by the request generation unit 103 according to the second embodiment of the present invention.
The table T23 is a two-dimensional table format table having item strings of OFS identification information and OFC identification information. The OFS identification information is identification information of each packet transfer apparatus 400. The OFC identification information is identification information of each control device 300 that controls each packet transfer device 400.

For example, in the first line, the OFS identification information is A, the OFC identification information is OFC-1, the second line is the OFS identification information X, the OFC identification information is OFC-1, and the third line The first is that OFS identification information is C and OFC identification information is OFC-2.
OFC-1 is the control device 300-1, and OFC-2 is the control device 300-2.
As described above, the request generation unit 103 acquires correspondence information corresponding to each of the separated point OFS, the different point OFS, and the merged OFS based on the classification result of the classified unit 102, and the separated point OFS, the different point OFS, the merged point. Each control device 300 that controls each OFS is specified.

Next, the request generation unit 103 generates prior confirmation entry information for each identified control device 300. Specifically, the request generation unit 103 generates classification information by adding the classification result classified by the classification unit 102 to the correspondence information. This will be described with reference to the table T24 in FIG.
The table T24 is a two-dimensional tabular table having item columns of OFS classification information, OFS identification information, and OFC identification information. The table T24 is an example of classification information. The OFS classification information is a classification result of each packet transfer apparatus 400 classified by the classification unit 102. The OFS identification information is identification information of each packet transfer apparatus 400. The OFC identification information is identification information of each control device 300 that controls each packet transfer device 400.

For example, in the first line, the OFS classification information is the departure point, the OFS identification information is A, and the OFC identification information is OFC-1. In the second line, OFS classification information is another point, OFS identification information is X, and OFC identification information is OFC-1. In the third line, OFS classification information is merged, OFS identification information is C, and OFC identification information is OFC-2.
In this way, the request generation unit 103 generates the classification information by adding the correspondence information to the classification result based on the classification result classified by the classification unit 102 and the correspondence information held by the management unit 105.

  Then, the request generation unit 103 generates prior confirmation entry information to be transmitted to each packet transfer device 400 controlled by each control device 300. Specifically, the request generation unit 103 generates matching information and Instructions for the classification information and generates pre-confirmation entry information. This will be described in more detail with reference to FIG.

FIG. 16 is a schematic diagram illustrating an example of entry information for prior confirmation according to the second embodiment of the present invention.
The table T25 is a two-dimensional table format table having item columns of OFC identification information, OFS classification information, OFS identification information, Matching Field, and Instructions. Since OFC identification information, OFS classification information, OFS identification information, Matching Field, and Instructions are the same as those in the table T11 in FIG.

For example, in the first line, the OFC identification information is OFC-1, the OFS classification information is a departure point, the OFS identification information is A, and the Matching Field is DstIP = 192.168.168. b. b / 16 Input = # z, and Instructions is Action = output: #x. In the second line, the OFC identification information is OFC-1, the OFS classification information is another point, the OFS identification information is X, and the Matching Field is DstIP = 192.168.168. b. b / 16 Input = # a, and Instructions is Action = output: #c. In the third line, the OFC identification information is OFC-2, the OFS classification information is merged, the OFS identification information is C, and the Matching Field is DstIP = 192.168. b. b / 16 Input = # x, and Instructions is Action = output: #d.
In this way, the request generation unit 103 adds the DstIP representing the destination and the input port information to the classification information and the output port information of the corresponding packet transfer device, and generates the prior confirmation entry information. The request generation unit 103 outputs the generated prior confirmation entry information, the transfer rule of the confirmation target network, and the changed route information to the transmission unit 104.

  The transmission unit 104 transmits the pre-confirmation entry information, the transfer rule of the confirmation target network, and the changed route information to all the control devices 300 input from the request generation unit 103 to the control device 300 on the Src side.

Next, the configuration of the control device 300 according to the present embodiment will be described.
When the configuration of the control device 300 according to the second embodiment is compared with the configuration of the control device 300 according to the first embodiment, since the configuration is the same, the description thereof will be omitted, and different parts in the second embodiment will be described. The explanation is centered.

  When the cooperation unit 301 receives the prior confirmation entry information, the transfer rule for the confirmation target network, and the changed route information from the management device 100, the cooperation unit 301 manages the packet transfer device 400 on the Src side in the changed route information. The prior confirmation entry information is output to the prior confirmation entry generation unit 303. Further, the cooperation unit 301 transmits the prior confirmation entry information to each of the other control devices 300. This will be described in detail with reference to FIG.

FIG. 17 is a schematic diagram illustrating an example of prior confirmation entry information transmitted to each control device 300 by the control device 300-1 according to the second embodiment of the present invention.
The table T26 is entry information for prior confirmation of the control device 300-1 that is a control device on the Src side, and the table T27 is entry information for advance confirmation transmitted from the control device 300-1 to the control device 300-2. It is an example.
Tables T26 and T27 are two-dimensional tabular tables having respective item columns of OFC identification information, OFS classification information, OFS identification information, Matching Field, and Instructions. Each item is the same as the tables T12 and T13 in FIG.
In the tables T26 and 27, the prior confirmation entry information for all the control devices shown in the table T25 of FIG. 16 is arranged for each control device. When receiving the prior confirmation entry information for all the control apparatuses 300 from the management apparatus 100, the control apparatus 300-1 generates the prior confirmation entry information for each control apparatus 300, and for the prior confirmation of each of the generated control apparatuses 300. The entry information is transmitted to another control device 300, for example, the control device 300-2.

When the cooperation unit 301 receives completion notifications from all the other control devices 300, the cooperation unit 301 outputs the transfer rule of the confirmation target network and the changed route information to the confirmation unit 302 as a communication route confirmation request.
On the other hand, when the prior confirmation entry information is received from another control device 300 (Src-side control device 300), a response indicating that the prior confirmation entry information has been received is sent to the transmission destination control device 300. Send. Then, the linkage unit 301 outputs the received prior confirmation entry information to the prior confirmation entry generation unit 303.

  Note that the cooperation unit 301 of the control device 300 that manages the packet transfer device 400 on the Src side may transmit the prior confirmation entry information to each of the other control devices 300, and among the plurality of control devices 300, for example, The prior confirmation entry information may be transmitted to only one control apparatus 300 and transmitted so that the control apparatus 300 that has received the prior confirmation entry information propagates to the other control apparatuses 300.

  When the prior confirmation entry information is input from the cooperation unit 301, the prior confirmation entry generation unit 303 generates a prior confirmation entry based on the prior confirmation entry information. The prior confirmation entry generation unit 303 outputs the generated prior confirmation entry to the transmission unit 304. This will be described in detail with reference to FIG.

FIG. 18 is a schematic diagram illustrating an example of a prior confirmation entry for the packet transfer apparatus 403 that is a confluence packet transfer apparatus generated by the prior confirmation entry generation unit 303 of the control apparatus 300 according to the second embodiment of the present invention. is there.
For example, the prior confirmation entry generation unit 303 generates a prior confirmation entry as illustrated in the second row of the table T30 illustrated in FIG. 18 for the packet transfer apparatus 403 that is the merged OFS. At this time, it is assumed that the first row of the tables T28, T29, and T30 illustrated in FIG. 18 is set in the packet transfer device 407 before the prior confirmation.
Tables T28, T29, T30, and T31 are two-dimensional tabular tables having item columns of Matching Field and Instructions. The item sequence is the same as the tables T14, T15, T16, and T17 shown in FIG.

In the first row of the table T28, Matching Field is ECN = 2, Instructions is GotoTable: T29, and in the second row, Matching Field is Any, and Instructions is GotoTable: T30.
In the first row of the table T29, Matching Field is Any, and Instructions is GotoTable: T30.
In the first row of the table T30, Matching Field has Dst = 192.168.168. b. b / 16 input = # b, Instructions is Action = output: #d, and in the second line, Matching Field is Dst = 192.168. b. b / 16 input = # x, and Instructions is Action = output: #d.
In the table T31, “Matching Field” and “Instructions” are blank.

As described above, the prior confirmation entry generation unit 303 generates the same prior confirmation entry as the entry applied to the in-service call after changing the route in the table T30. In addition, in the table T30, the advance confirmation entry generation unit 303 includes both the in-service call transfer entry and the advance confirmation transfer entry before the route change.
Further, since the separation point OFS, the different point OFS, and the common OFS are the same as those in the first embodiment, the description thereof is omitted.

  Thus, according to the present embodiment, a network including the control device 300 that controls a part of the plurality of packet transfer devices 400 that transfer packets in the network, and the management device 100 that manages the control device 300. The network management system is a management system that identifies a packet transfer device 400 that needs to be changed in setting a route for transferring a packet, and identifies a control unit 300 that controls the identified packet transfer device 400 (request generation) Unit 103) and a notification unit (transmission unit 104) that notifies the control device 300 identified by the identification unit (request generation unit 103) of the change contents of the route.

  As a result, in a network where there are an infinite number of possible routes, even if the transfer rule of the same network includes a different network for each packet transfer device, the route is not limited to the backup path and working path, but is routed to any path The effectiveness of the change-destination route is improved even when performing route control such as switching the route, or when performing route control such as branching the route again at the packet transfer device where the working path and protection path join. Can be confirmed. In addition, when changing the communication route, it is not necessary to manually check the communication of the route after the change, it can be automatically confirmed, and even when performing automatic route change control, due to a setting error, etc. Control can be reliably performed without causing communication interruption. In addition, since the network transfer rule set when the communication path is checked in advance and the network transfer rule set when actually used in the service are the same or the same type, Setting changes when changing routes are minimized.

(Third embodiment)
Hereinafter, the third embodiment of the present invention will be described in detail with reference to the drawings.
In the third embodiment, there is no management device 100 or control device 300 as in the first and second embodiments described above, and each packet transfer device 400 performs packet discrimination and operation on the packet. Therefore, an example in which each packet transfer apparatus 400 has a plurality of tables will be described. In this case, each packet transfer apparatus 400 acquires entry information for prior confirmation set in the plurality of tables as control information, and sets the entry information for prior confirmation in the plurality of tables.

FIG. 19 is a schematic diagram showing an example of the configuration of a network management system S4 according to the third embodiment of the present invention.
The network management system S4 includes packet transfer devices 401, 402, 403, 404, 405, and 406.
Also in this embodiment, the description of the packet transfer device 400 is a generic name including the packet transfer devices 401, 402, 403, 404, 405, 406, and the like.

  The identifiers of the packet transfer apparatuses 400 are A, B, C, D, X, and Y in order. The packet transfer device 401 is interconnected with the packet transfer devices 402 and 405, the packet transfer device 403 is interconnected with the packet transfer devices 402 and 404, and the packet transfer device 406 is interconnected with the packet transfer devices 405 and 404. The

  Further, for example, the packet transfer apparatus 401 is connected to the network NW8 of “192.168.a.a / 16”, and the packet transfer apparatus 404 is connected to the network NW9 of “192.168.b.b / 16”. ing. Here, it is assumed that communication is performed from a PC belonging to the network NW8 to a PC belonging to the network NW9. In the following description, a PC belonging to the network NW8 that is a transmission source (Src: Source) is referred to as SrcPC. A PC belonging to the network NW9 that is a destination (Dst: Destination) is referred to as DstPC. It is assumed that communication from SrcPC to DstPC goes through each packet transfer device 400.

At this time, DstIP = 192.168. b. As communication for b / 16, the route through which the current packet passes through each of the packet transfer devices 401, 402, 403, and 403, and each of the packet transfer devices 401, 405, 406, and 404 as the change destination route of the route are used. Consider another route through.
At this time, the entry information of each packet transfer apparatus 400 is set as follows. This will be described in detail with reference to FIGS.

  20 to 25 are schematic diagrams illustrating examples of entry information for each packet transfer apparatus according to the third embodiment of the present invention. FIG. 20 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 401. FIG. 21 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 402. FIG. 22 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 403. FIG. 23 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 404. FIG. 24 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 405. FIG. 25 is a schematic diagram illustrating an example of entry information for the packet transfer apparatus 406.

  Tables T40 to T43, T50 to T53, T60 to T63, T70 to T73, T80 to T83, and T90 to T93 are two-dimensional tabular tables having item columns of Matching Field and Instructions. Each item string is the same as the table T5 to T8 degrees in FIG.

Here, the ECN included in the matching information in the tables T40, T50, T60, T70, T80, and T90 is identification information for identifying the packet of the preliminary test call. The identification information can be any information as long as it can be specified by a tuple and is not used by an in-service call.
This will be described with reference to the example of FIG. The in-service call does not meet the condition of ECN = 2 in the first row in the table T40 in the packet transfer device 401, and therefore corresponds to Any in the second row, and transitions to the table T42. In the table T42, DstIP = 192.168.168. b. Since it corresponds to b / 16, it represents that it is output from the output port of output port information #b.

On the other hand, since ECN = 2 is assigned as identification information to the prior confirmation call, the condition of ECN = 2 in the table T40 is met, and the table transitions to the table T41. In the table T41, DstIP = 192.168.168. b. Since it corresponds to b / 16, it changes to table T43. Also in the table T43, DstIP = 192.168 .. b. Since it corresponds to b / 16, it is output from the output port of the output port information #x.
In this way, by making settings for each packet transfer device 400 and inflowing prior confirmation calls into the network in order, the communication confirmation of the change destination route is made without affecting the route through which the current packet flows. Can be implemented.
The same applies to FIG. 21 to FIG.
The entry information of the change destination route to be written in the tables T43, T53, T63, T73, T83, and T93 of the off-point OFS may be written in the tables T41, T51, T61, T71, T81, and T92.

  As described above, according to the present embodiment, the network management system S4 includes a plurality of packet transfer apparatuses that transfer packets in a network. The packet transfer apparatus 400 acquires control information, and based on the acquired control information. The packet transfer rule is the same or the same type as the transfer rule used after changing the route without affecting the transfer of the service packet in the route used by the service packet used in the service. Set for each device 400.

  As a result, the transfer rule set when performing prior confirmation of the communication route and the transfer rule set when actually using the service are the same or the same type. Configuration changes are minimized. In addition, in a network with an infinite number of routes, route control that switches routes to any path, as well as backup paths and working paths, is performed, and routes are routed again with a packet transfer device that joins the working path and protection path. Even when route control such as branching is performed, the effectiveness of the change destination route can be confirmed.

  In each of the above-described embodiments, an example in which the network management system includes a plurality of control devices has been described. However, the network management system may include only one control device.

  A program for executing each process of the management device 100, the control device 300, and the communication path confirmation device 200 according to each embodiment of the present invention is recorded on a computer-readable recording medium and recorded on the recording medium. The above-described various processes related to the management apparatus 100, the control apparatus 300, and the communication path confirmation apparatus 200 may be performed by causing the computer system to read and execute the program.

  Here, the “computer system” may include an OS and hardware such as peripheral devices. Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used. The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

  Further, the “computer-readable recording medium” refers to a volatile memory (for example, DRAM (Dynamic) in a computer system serving as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. Random Access Memory)) that holds a program for a certain period of time is also included. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  As mentioned above, although embodiment of this invention was explained in full detail with reference to drawings, a specific structure is not restricted to this embodiment. Each configuration in each embodiment, a combination thereof, and the like are examples, and the addition, omission, replacement, and other changes of the configuration can be made without departing from the spirit of the present invention. Further, the present invention is not limited by the embodiments, and is limited only by the scope of the claims.

Sys1 Host system 100 Management device 200 Communication path confirmation device 300, 300-1, 300-2 Control device 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412 Packet transfer device 101 system cooperation unit 102 classification unit 103 request generation unit (specification unit)
104 Transmission unit (notification unit)
105 Management unit 301 Cooperation unit (acquisition unit)
302 Confirmation Unit 303 Prior Confirmation Entry Generation Unit 304 Transmission Unit (Setting Unit)

Claims (10)

A network management system including a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network, and a management device that manages the control device,
Identifying the packet transfer device that needs to be changed in the setting of a route for transferring a packet, and specifying a control unit that controls the identified packet transfer device among the control devices;
A notification unit that notifies the control device specified by the specifying unit of the change of the route;
A network management system comprising: The network management system according to claim 1, wherein the control device sets a route in the packet transfer device based on the received change content of the route. The specific part is:
3. The packet transfer device is classified from a current route and a destination route, and the packet transfer device that requires a change in route setting is specified based on a classification result. The network management system described in 1. The specifying unit specifies the control device that controls the packet transfer device based on a connection relationship between the control device and the packet transfer device and a change authority of the control device with respect to the packet transfer device. The network management system according to any one of claims 1 to 3. An acquisition unit for acquiring control information;
Based on the control information acquired by the acquisition unit, a transfer rule that is used after changing the route without affecting the transfer of the service packet in the route used by the service packet used in the service A setting unit that sets a packet transfer rule of the same or the same type in each of the packet transfer devices;
The network management system according to any one of claims 1 to 4, further comprising: A management device that manages a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network,
A specifying unit for specifying the packet transfer device that needs to be changed in setting a route for transferring a packet, and for specifying a control device for controlling the specified packet transfer device;
A notification unit that notifies the control device specified by the specifying unit of the change of the route;
A management apparatus comprising: A control device that controls a part of a plurality of packet transfer devices that transfer packets in a network,
An acquisition unit for acquiring control information;
Based on the control information acquired by the acquisition unit, a transfer rule that is used after changing the route without affecting the transfer of the service packet in the route used by the service packet used in the service A setting unit that sets a packet transfer rule of the same or the same type in each of the packet transfer devices;
A control device comprising: A management method for managing a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network,
A specifying process for specifying the packet transfer device that needs to be changed in setting a route for transferring a packet, and specifying a control device for controlling the specified packet transfer device;
A notification process of notifying the control device identified by the identification process of the change of the route;
The management method characterized by having. A control method of a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network,
An acquisition process for acquiring control information;
Based on the control information acquired by the acquisition process, the transfer rule used after changing the route without affecting the transfer of the service packet in the route used by the service packet used in the service A setting process for setting a packet transfer rule of the same or the same type in each of the packet transfer devices
A control method characterized by comprising: A network management system including a control device that controls a part of a plurality of packet transfer devices that transfer packets in a network, and a management device that manages the control device, or a computer of the control device,
A specifying step of specifying the packet transfer device that needs to be changed in the setting of a route for transferring a packet, and specifying a control device that controls the specified packet transfer device;
A notification step of notifying the control device specified by the specifying step of the change of the route;
The program characterized by having.

Images